| Real-Time Workshop Release Notes | |
Rapid Simulation Target Now Supports Variable-step Solvers
Executables generated for the Rapid Simulation (rsim) target are now able to use any Simulink solver, including variable-step solvers. To use this feature, the target system must be able to check out a Simulink license when running the generated rsim executable. You can maintain backwards compatibility (i.e., fixed-step solvers only, with no need to check out a Simulink license) by selecting Use RTW fixed step solver from the Solver Selection popup menu on the Rapid Simulation code generation options dialog. The default solver option is Auto, which will use the Simulink solver module only when the model requires it.
External Mode Support for Rapid Simulation Target
The Rapid Simulation target now includes full support for all features of Simulink external mode. External mode lets you use your Simulink block diagram as a front end for a target program that runs on external hardware or in a separate process on your host computer, and allows you to tune parameters and view or log signals as the target program executes.
External Mode Support for ERT
The Real-Time Workshop Embedded Coder now includes full support for all features of Simulink external mode. External mode lets you use your Simulink block diagram as a front end for a target program that runs on external hardware or in a separate process on your host computer, and allows you to tune parameters and view or log signals as the target program executes.
External Mode Supports Uploading Signals of All Storage Classes
Signals from all storage classes, including custom, can now be uploaded in external mode, as long as signals or parameters have addresses defined. For example, data stored as bitfields or #defines cannot be uploaded, but few other restrictions exist.
Expanded Support for Borland C Compilers
Real-Time Workshop supports version 5.6 of the Borland C compiler.
In addition, Release 13 reinstates support for Borland Version 5.2 "out-of-the-box" for all targets, except when importing Real-Time Workshop-generated S-functions. In such instances, you will need to designate the build directory where the S-function may be found via the make_rtw parameter USER_INCLUDES. For example, suppose you had generated S-function target code for model modelA.mdl in build directory D:\modelA_sfcn_rtw and were using that S-function in model modelB.mdl. In modelB.mdl, the Make command field of your Target configuration category should define USER_INCLUDES as follows:
| | Block-level Enhancements | TLC, model.rtw, and Library Enhancements | |