For a better experience on, enable JavaScript in your browser. Thank you!

Modeling Function Variants in TargetLink

In practical Simulink/TargetLink projects one often has to model functional variants, i.e. different realizations for certain features that can be switched. Function variants may be needed to support optional functionality or different vehicle configurations.
Binding of variants can be realized during code generation, during compilation, or at runtime. If binding takes place during code generation, variant-specific code is generated. Binding of variants at compile time can be realized by pre-processor definitions in the code. For binding of variants at runtime calibration variables can be used.

This application note describes methods and techniques to realize function variants with TargetLink. It also gives background information about related TargetLink principles as well as hints and suggestions to overcome common problems. Demo models for the TargetLink versions TargetLink 2.3.1 and TargetLink 3.0.1 (in combination with The MathWorks Release R2007b or newer) are included as examples.

Please note

This material is available for registered customers with additional permission for TargetLink Support Information only. If you are already registered please logon with your mydSPACE ID and passphrase in order to download this material. If you are not yet registered, use these links for registration and managing your permissions

Date 2012-06-15
Software-Typ Software für Seriencode-Generierung
Produkt TargetLink
Informationstyp Application Notes
Informationskategorie Arbeiten mit
dSPACE Release 2018-A, 2017-B , 2017-A, 2016-B, 2016-A, 2015-B, 2015-A, 2014-B, 2014-A, 2013-B, 2013-A, Bis 2013-A