Version 4.3 (R14SP3) Real-Time Workshop Embedded Coder Software :: Real-Time Workshop Embedded Coder Release Notes (Real-Time Workshop® Embedded Coder™)

Learn more about Real-Time Workshop Embedded Coder

Version 4.3 (R14SP3) Real-Time Workshop Embedded Coder Software

This table summarizes what's new in Version 4.3 (R14SP3):

New Features and Changes	Version Compatibility Considerations	Fixed Bugs and Known Problems	Related Documentation at Web Site
Yes Details below	Yes—Details labeled as Compatibility Considerations, below. See also Summary.	Bug Reports Includes fixes	No

New features and changes introduced in this version are

Data Type Replacement

This release provides the ability to replace built-in data type names with user-defined replacement data type names in the generated code for ERT target models.

As in previous releases, you can register user-defined data types and specify their associated header files using mechanisms described in Managing Data Definitions and Declarations With the Data Dictionary of the Real-Time Workshop Embedded Coder documentation. User-defined data types can be automatically created as Simulink.AliasType objects in the base workspace.

This release augments the existing mechanisms for registering user-defined data types by adding:

The Data Type Replacement pane, a new subpane under the Real-Time Workshop pane of the Configuration Parameters dialog box. This pane provides an improved user interface for mapping built-in data types to user-defined replacement data types.
Consistency checks to ensure that your specified data type replacements are consistent with your model's data types.
Many-to-one data type replacement, the ability to map multiple built-in data types to one replacement data type in generated code. For example, built-in data types uint8 and boolean could both be replaced in your generated code by a data type U8 that you have previously defined.

Data type replacement is available for code generated using Real-Time Workshop Embedded Coder, whether from Simulink, Stateflow charts, or Embedded MATLAB blocks.

For details on specifying replacement data types for a Simulink model, see Replacing Built-In Data Type Names in Generated Code in the Real-Time Workshop Embedded Coder documentation. For limitations that apply, see Data Type Replacement Limitations in the Real-Time Workshop Embedded Coder documentation.

HeaderFile Property Now Optional as Part of GetSet Data Object

In previous releases, a Simulink.Signal or mpt.Signal object of custom storage class GetSet was required to specify its HeaderFile property. The specified header file was then added as an #include in the generated code.

This release makes it optional to specify the HeaderFile property on data objects of the GetSet custom storage class. This accommodates users who prefer to use a model's custom code options to include header files.

Note If you omit the HeaderFile property for a GetSet data object, you must specify a header file by an alternative means, such as the Header file field of the Real-Time Workshop/Custom Code pane of the Configuration Parameters dialog box. Otherwise, the generated code might not compile or might function improperly.

Data Object Wizard Enhancements

The Data Object Wizard has been enhanced with new search options for including or omitting the following types of data objects for searches:

Alias types

Block outputs

Data stores

Parameters

Root inputs

Root outputs

States

For details on these enhancements, see Data Object Wizard in the Simulink documentation.

Global Data Stores Can Be Initialized Using mpt.Signal Object's RTWInfo.InitialValue Property

Global data stores may be defined in the base workspace using mpt.Signal objects (as well as Simulink.Signal objects or any of the subclasses of Simulink.Signal). In Release 14SP3, you can use the RTWInfo.InitialValue property of the mpt.Signal object to initialize a global data store.

If you set the RTWInfo.InitialValue property of the mpt.Signal object to a nonempty value, the value of that property becomes the initial condition of the global data store. If the InitialValue property of the object is empty ([]), the initial value of the global data store remains 0 (for example, false for Boolean data).

ERT Automatic Configuration Changes

If you generate code for ERT-based models that use the automatic model configuration feature, you should be aware of the following auto-configuration related changes in this release. If you supply your own script for ERT auto-configuration, you should consider modifying your code to take advantage of these changes.

The ert_config_opt auto-configuration function that is invoked at the 'entry' hook during code generation now additionally runs at target selection time (that is, when you use the Real-Time Workshop pane of the Configuration Parameters dialog box to select an auto-configuration target).
To support this dual invocation, the ert_config_opt function now takes variable input arguments. The second argument still specifies 'optimized_fixed_point' or 'optimized_floating_point' as before, but the first argument now specifies either a model name, for 'entry'-hook invocation, or a configuration set handle, for target-selection invocation. (The function is located in the file matlabroot/toolbox/rtw/targets/ecoder/ert_config_opt.m.)
The 'entry' hook in the example hook file ert_make_rtw_hook.m has added code to report changes in the configuration set caused by invoking ert_config_opt (via gateway routine ert_auto_configuration) during code generation. (The example 'entry' hook is located in the file matlabroot/toolbox/rtw/targets/ecoder/ert_make_rtw_hook.m.)

Compatibility Considerations

If you supply your own auto-configuration script in place of the default version of ert_config_opt, your auto-configuration code will continue to be invoked and execute at the 'entry' hook. However, to additionally run your code at target selection time, you must modify your script to support the variable input arguments in the manner shown in ert_config_opt.m.

Documentation Enhancements

The following areas of the Real-Time Workshop Embedded Coder documentation have been corrected or improved:

'Basic Tutorial' in the Module Packaging Features documentation
'Comparison of a Template and Its Generated File' in the Module Packaging Features documentation
'mpt Parameter and Signal Properties' in the Module Packaging Features documentation

Version 4.4 (R2006a) Real-Time Workshop Embedded Coder Software

Version 4.2.1 (R14SP2+) Real-Time Workshop Embedded Coder Software

Related Products & Applications

Get Simulink trial software

Learn more about Simulink through this collection of videos, articles, technical literature and the Getting Started with Simulink Guide.

Get this Simulink Kit