Orthogonal stm regions block each other

Moderator: Moderators

Orthogonal stm regions block each other

Postby maximilian.von-arnim@airbus.com » Fri Mar 08, 2019 7:43 am


I've ran into the problem that parallel states in different regions are not fully independent. In the attached example, the signal "GenericSignal" in region 1 will not be consumed while the entry activity "act_timer" in region 2 is still executing. So it will remain in SubState1_1. Neither will the signal "Signal" in region 2 be consumed. Both regions are free to do whatever they want only after the activity has run to completion.
Is this intended? I would expect both regions to operate independently. Is there a way to solve this problem?

This is particularly an issue when the activity takes significant time to execute, e. g. when it contains a timer, as is the case in this example.

Using MD with CST, SysML plugins in version 18.4 SP1.

You do not have the required permissions to view the files attached to this post.
Forum Newbie
Forum Newbie
Posts: 4
Posts Rating:0
Joined: Thu Jan 10, 2019 2:59 am
Full name: Maximilian von Arnim

Return to Cameo Simulation Toolkits

Who is online

Users browsing this forum: No registered users and 0 guests