Files
powertrain-build/docs/target_link/state_flow.md
Henrik Wahlqvist 1f388f1d2d Add docs about TargetLink
Change-Id: I027ec3815c741022d3860820e8ac8c521506c1c8
2024-10-04 10:00:48 +02:00

31 lines
1.2 KiB
Markdown

# TargetLink Configuration of State Flow
-----------------------------------------
[TOC]
## TargetLink Configuration of Ports in State Flow
If ports and locals are not properly configured in State Flow, the signals may end up as Float64, which is not a native data type.
Do not choose data type double, this will result in Float64 as data type.
![sf_double.png](../images/target_link/sf_double.png)
Do not choose "Inherit: Same as Simulink" either as this may also result in Float64.
It is best to choose single as Datatype for inputs or boolean for logical signals.
![sf_inherit.png](../images/target_link/sf_inherit.png)
The above configurations can also be done in the *TargetLink Property Manager*.
In the property manager, TL classes can also be set, see below.
The TargetLink properties can be configured by choosing *TargetLink -> Property Manager* in the menu.
![propertyman.png](../images/target_link/propertyman.png)
![propertyman_2.png](../images/target_link/propertyman_2.png)
A properly configured outport is marked by blue in the picture below.
The outport marked by red can cause the undesired behavior.
![stateflow_wiki.png](../images/target_link/stateflow_wiki.png)