|
Re: State machine animation [message #1784450 is a reply to message #1784430] |
Wed, 28 March 2018 07:05   |
|
Hi Steve,
do you have the Moka components installed?
And there is an issue starting the simulation working with the Moka debug perspective.
Please try to start the simulation within the Papyrus perspective and switch to the Moka perspective after the animation is running.
/Carsten
|
|
|
|
|
|
|
|
Re: State machine animation [message #1804279 is a reply to message #1797928] |
Thu, 21 March 2019 17:20   |
Jesús Gorroñogoitia Messages: 5 Registered: July 2018 |
Junior Member |
|
|
Hi Steve,
I've been also struggling with Moka simulation for both activity and state machine diagrams. If you clone the Moka source code from its Eclipse Git repository:
git clone git://git.eclipse.org/gitroot/papyrus/org.eclipse.papyrus-moka.git
You can find therein in the directory ./bundles/core/engines/org.eclipse.papyrus.moka.fuml.statemachines/resources/tests/ the Papyrus model PSSM_TestSuite.di, which contains dozens of valid activity/statemachine test models.
I've tested those in model folder Behavior. You can run all them by executing the activity BehaviorTests or by individual cases. For both, create a Moka run configuration that uses as execution engine the org.eclipse.papyrus.moka.fuml.statemachines . To select the element to be executed you cannot rely on the drop-down combo box, since the huge number of behaviors in the model makes Eclipse to collapse, but you can transverse this list using the arrow keys up/down until you find the activity you want to simulate. Remember to have opened beforehand the activity/state machine models you want to visualized. It is not working the automatic opening of models option that you can configure in the Moka Animate view.
Hope this helps!.
Yosu
[Updated on: Thu, 21 March 2019 17:22] Report message to a moderator
|
|
|
|
|
|
|
Re: State machine animation [message #1806233 is a reply to message #1805982] |
Mon, 06 May 2019 15:47   |
|
Hello,
It seems that your model is not conform to the norm since you want to run a standalone state machine which is not active.
According to the PSSM norm, if the state machine is not active then the there is no object activation for this element and there is no way to receive events. This is a known bug that Moka should provide better error messages or at lease validate the model.
So to fix your problem, it seems that you should set the field "isActive" of your state machine to true.
HTH,
Pauline
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.02663 seconds