Version 8.5 brings timers into the state diagram. A transition can now say when it fires, the generated C and C++ code handles the timers, and the built-in editor simulates them. New in this version:
- Time triggers, C and C++: a transition can say when it fires:
after(200ms)once,every(1s)periodically, and named timers such ascookTimer: after()that keep their time from one state to the next and can be changed by the model. The generated code starts and stops the timers itself, through a small timer service. A reference service and services for FreeRTOS and Trampoline (AUTOSAR OS) are available with examples on GitHub — see Time Triggered Events. - Timeouts as events: with
TimeoutsAsEvents=yeseach timer has an event of its own, which suits an RTOS task that waits on its queue — see how the timeout reaches the machine. - Simulation of timers in the built-in editor: the timers of the model run on a model
clock that can be paused, run slower or faster, or jump to the next timeout. A timer list
shows the time left of each timer, and a timer can be fired by hand. Values the simulation
cannot know, such as a duration given by a variable, are set under Timer values. When the
simulation needs a decision, for example at a choice after a timeout, a banner asks for it.
Watch the film of the timer simulation
(1.5 minutes, with sound). The old
@@@timer comments are no longer simulated. - Built-in editor: a button switches between a light and a dark theme at once. The editor starts without a model file, with an empty model; it saves the model before it generates code from it; and it keeps the positions of its split panes — see Built-in Visual Editor.
- Diagrams as SVG:
-l svgnow also draws UML state machines, laid out as in the built-in editor — see Drawing the State Machine. - Showing a running target: with
-Vthe diagram shows the states a running target reports;-Saccepts event strings again — see Show a running target. - State tables and test routes: the Excel state table is written as
.xlsxin three layouts with a legend, and as CSV. The path-coverage routes are also written as CSV beside the workbook. - Build scripts: the generator exits with status 1 when the generation of a UML model
fails, so
makestops there. - Bug fixes: astah activity diagrams with a flow final node generate again; the Handler Signature dialog names the machine as the generated code does and takes typed values at once; multi-line transition actions are drawn one line per action.
The manual (PDF) describes all of it in detail.