Simulink Supported Block Details
From UcgnWiki
(→Subsystems) |
(→Misc) |
||
| Line 18: | Line 18: | ||
== Discrete == | == Discrete == | ||
[[File:Simulink_SupportedBlocksDiscrete.jpg]] | [[File:Simulink_SupportedBlocksDiscrete.jpg]] | ||
| + | |||
| + | * Discrete-time Integrator | ||
| + | ** The following integration methods are supported: Integrator Forward and Backward Euler and Integrator Trapezoidal (Accumulator not supported) | ||
| + | ** Reset input has to be scalar | ||
| + | ** State port and Saturation port not supported | ||
| + | ** Simplified initialization not supported | ||
== Logical & Bit == | == Logical & Bit == | ||
| Line 24: | Line 30: | ||
== Signal Routing == | == Signal Routing == | ||
[[File:Simulink_SupportedBlocksSignalRouting.jpg]] | [[File:Simulink_SupportedBlocksSignalRouting.jpg]] | ||
| + | |||
| + | * The MultiportSwitch does not support the two-input usage as a selector, indexing into an array. Please use the Selector block instead | ||
| + | * The code generated from the MultiportSwitch will rely on a utility function (in GBL_Saturation.c, located in the Sources folder of the distribution) to guard the selecing input | ||
| + | * Both the Switch and MultiportSwitch currently support only the switching of basic (and enumerated) types, not bus types | ||
| + | * From/Goto block are useful tools to structure a complex design which would otherwise have many crossing signal lines. But, From/Goto blocks can only be used with a local scope. They are basically non-functional, simply hiding a signal line from view. From/Goto blocks with global scope would have to be represented by global variables. Such a concept is not supported by design, as this would open alternative data paths to the current paradigm that data flow across hierarchy levels will follow an equivalent procedure call hierarchy. | ||
| + | * Data Store Memory, Read and Write | ||
| + | ** Local scope only (same rationale as Goto/From, see above) | ||
| + | ** Currently only basic type support | ||
== Lookup == | == Lookup == | ||
[[File:Simulink_SupportedBlocksLookup.jpg]] | [[File:Simulink_SupportedBlocksLookup.jpg]] | ||
| + | |||
| + | The lookup, interpolation and interpolation using pre-lookup blocks will result in generated code that uses utility functions located in GBL_Interpolation.c (provided in the Sources folder of the distribution) | ||
== Sinks & Sources == | == Sinks & Sources == | ||
[[File:Simulink_SupportedBlocksSinksSources.jpg]] | [[File:Simulink_SupportedBlocksSinksSources.jpg]] | ||
| + | |||
| + | * For all Inports at top-level (model as well as library system) data type and dimension have to be set to fixed values at generation time. Simulinks ability to determine a model's types and dimensions at run-time does not translate into source code. Furthermore, since library systems are intended to result in truly reusable pieces of source code, all instances of a library system have to use the same fixed interface. | ||
== Misc == | == Misc == | ||
[[File:Simulink_SupportedBlocksMisc.jpg|450px]] | [[File:Simulink_SupportedBlocksMisc.jpg|450px]] | ||
| + | The code generated from the Saturation block will rely on utility functions in GBL_Saturation.c, which is located in the Sources folder | ||
---- | ---- | ||
