18. Revision History#
Different versions of Reactis for C are labeled as shown in Figure 18.1 and described below.
Fig. 18.1 Version labels begin with a “V” and include three parts: a year, a major release number, and a patch release number. The parts are numbers separated by decimal points. By convention, trailing zeros are omitted.#
- Major Releases.
A new version of Reactis for C is labeled by a “V” followed by the four-digit year (e.g., V2020). Each label for an intra-year release includes a suffix consisting of a decimal point followed by a major release number; for example V2020.1, V2020.2, etc. will label the releases during 2020 that follow V2020.
- Beta Releases.
RSI often makes beta releases available to customers interested in evaluating the newest features of Reactis for C. Beta releases do not undergo as much testing as major releases do. By convention, beta releases have odd numbered major release numbers. For example, V2020.1, V2020.3, … denote beta releases.
- Patch Releases.
Both stable and beta releases may be “patched.” The label for a patch release is constructed by extending the label for the major release to be patched with a suffix that includes a second decimal point and a patch release number. For example:
V2020.2.1 denotes the first patch release for V2020.2 V2020.0.2 denotes the second patch release for V2020
18.1. V2024 (5 June 2024)#
The V2024 release of Reactis for C includes all bug fixes in the V2023.0.1 and V2022.0.2 patch releases, plus the following new features.
18.1.1. Linking between model components and TargetLink-generated C code#
When generating C code for a model, dSPACE TargetLink adds comments to link the C code back to the model. Reactis processes these comments and uses them to build a map between the code and model components, which can then be used to explore and/or co-simulate a model and the C code generated from it. This feature is similar to the linking between a model and C code generated by Simulink Embedded Coder which was introduced in Reactis for C V2023.
If a TargetLink model is loaded in Reactis for Simulink and the corresponding C code (generated by TargetLink) is loaded in Reactis for C, a connection can now be established between the two. Once a connection is established, the following functions are provided:
Clicking on a block or Stateflow state or transition in the model will highlight corresponding C code comment(s).
Clicking on a comment mentioning a block in C code will highlight the corresponding block in the model
Clicking on a line of C code will highlight all model blocks mentioned in the comment above the C code line.
Enabling or disabling Reactis Simulator in either Reactis for Simulink or Reactis for C will automatically do so in the connected session.
Setting a breakpoint on a model block or Stateflow item will set breakpoints on the first line of code below each comment mentioning the block.
Setting a breakpoint on a line of C code will set a breakpoint on each block mentioned in the comment above the C code line.
18.1.2. Import Test Harness from TargetLink Model#
When testing C Code which was generated by TargetLink from a model which has been loaded in Reactis for Simulink, Reactis for C can now automatically import the test harness for the C code from the model. When creating a C test harness from an .rsi file, selecting Automatically match TargetLink names will create a harness in which each top-level port in the model is mapped to the corresponding variable in the C code. The imported harness makes it easy to exchange test suites between the model and code, which facilitates back-to-back testing of model vs. code behavior.
18.1.3. Synchronize Test Harness with RSI File#
When editing a test harness, the harness can be synchronized with an .rsi file. During synchronization, the type of each input, output, and configuration variable is changed to match the type of the corresponding input/output/configuration variable in the .rsi file. This allows test suites to be easily interchanged between the model and code. The synchronized harness makes it easy to exchange test suites between the model and code, which facilitates back-to-back testing of model vs. code behavior.
18.2. Previous Major Release Dates#
Major releases of Reactis for C prior to V2024 have occurred on the following dates:
Version |
Release Date |
|---|---|
V2023 |
December 22, 2023 |
V2022 |
June 22, 2022 |
V2021 |
July 9, 2021 |
V2020 |
December 18, 2020 |
V2019 |
June 14, 2019 |
V2018 |
February 9, 2018 |
V2016 |
October 21, 2016 |
V2015 |
November 18, 2015 |
V2014 |
April 10, 2014 |
V2011 |
March 21, 2011 |