for internal group transitions in eTrice you need to add a TransitionPoint. You can choose between a plain one which leaves the
history, executes all exit codes and enters the history again while executing all entry codes.
On the other hand the 'handler' TransitionPoint (which is a concept we added to ROOM) just leaves and enters the history without
executing entry and exit codes.
See attached screen shot.
Hope that helps,
Am 16.11.2012 23:59, schrieb Tim Born:
> I was modeling group transitions using OT5.2 User Guide p. 218 as my example.
> It shows three different kinds of group transitions.
> The group transition out of a substate works fine.
> The group transition out/in a substate works fine.
> I'm have a little trouble modeling a group transition on the top level of the behavior.
> Looking at the syntax for the text of the ROOM model, it's not clear how I refer to the top level enclosing "state" for an FSM. Does it have a name? The editor didn't let me draw it.
> I suppose there is a work around for this is I start my model with a single state and stuff everything inside of that ....
You guys are outstanding! Thanks for the quick response. I was able to implement and verify all three of the group transitions found in the OT example, plus a group transition at the top level to answer a query "what state am I in?", which I used to construct some simple verification tests. You guys have done a great job with eTrice. Thanks very much.