Community
Participate
Working Groups
eTrice supports event driven state machines. But there are many embedded applications which employ data driven state machines. The state machine is called on a periodic base and trigger conditions are evaluated using data. So the language should distinguish those two kinds using a keyword, e.g. [data_driven] StateMachine In data driven state machines the TriggeredTransitions would have to be replaced with GuardedTransitions (can be checked by validation) For data driven state machines the generator model construction will need a second algorithm to collect triggering transitions (in this case guarded ones).
introduced with ac22bffec20d960c48cb76c97b9c12d8465657b5
closed resolved bug