Recent changes to feature-requests

Stateflow: update transition evaluation semantics

Kai Harth — Thu, 17 Feb 2011 17:03:24 -0000

Mathworks has apparently relaxed their transition evaluation semantics in an undocumented way.

Example: A state "A" has two outgoing transitions, both of which are bare (no guard condition). The guard condition occurs downstream on another transition, after going through a junction.

While this makes sense it was originally not allowed under a stricter evaluation of the published semantics... Transition "2" would be shadowed by transition "1".

Oddly enough, if such a chart is compiled in Simulink with the chart set to use implicit transition ordering (without actually resulting in a different order), a coder warning is generated by simulink...
"Chart #1056 has an unconditional transition #1062 that shadows
the following transitions: #1063 #1064"
but the generated RTW code is correct despite that warning.

Stateflow: add flowgraph loop capability

Kai Harth — Thu, 17 Feb 2011 16:57:35 -0000

The current UCGN/Simulink can not handle flowgraph loops in Stateflow, but this would be a strong feature to have.

Add support for Simulink enumerated data types

Kai Harth — Tue, 01 Feb 2011 19:32:19 -0000

The newer releases of Simulink support the use of true enumerated type definitions. These should be available for UCGN/Simulink as well...

Add support for user explicit transition ordering

Kai Harth — Tue, 02 Nov 2010 11:43:48 -0000

Currently for Stateflow only the implicit (automatic) ordering of transitions si supported.
Consider adding support for using the user explicit ordering of transitions.
(originally this limitation was intentionally, because user explicit ordering of transition evaluation reduced the readability of charts... but Stateflow has improved the visibility of those ordering choices)

Forward inlining for BusCreator members

Kai Harth — Mon, 19 Jul 2010 12:40:04 -0000

Provide forward inlining capability for BusCreator members.

Forward inlining is when a downstream entity is used upstream, instead of creating an intermediate variable:

Currently:

GBL_Types_Double OutputValue;

MySubsystemCall(Input1, Input2, &OutputValue);

BusCreator.Value = Outputvalue;

Desired:

MySubsystemCall(Input1, Input2, &(BusCreator.Value));

Stateflow: History connector

Anonymous — Thu, 24 Jun 2010 00:45:44 -0000

Add History connector capabilities to Stateflow model transformation

Add For and While Iterator Subsystems

Kai Harth — Wed, 23 Jun 2010 15:06:16 -0000

Add capability to process and generate output for For and While Iterator Subsystems

Add Enabled and Triggered Subsystems

Kai Harth — Wed, 23 Jun 2010 15:05:12 -0000

Add the capability to process and generate output for Enabled Triggered Subsystems