The rapid accelerator mode creates a Rapid Accelerator standalone executable from your model. This executable includes the solver and model methods, but it resides outside of MATLAB® and Simulink®. It uses external mode to communicate with Simulink.
MATLAB and Simulink run in one process, and if a second processing core is available, the standalone executable runs there.
Rapid Accelerator mode does not support:
Targets written in C++.
Interpreted MATLAB Function blocks.
Noninlined MATLAB language or Fortran S-functions. You must write S-functions in C or inline them using the Target Language Compiler (TLC) or you can also use the MEX file. For more information, see .
Debugger or Profiler.
Run time objects for Simulink.RunTimeBlock and Simulink.BlockCompOutputPortData blocks.
Model parameters must be one of these data types:
You cannot pause a simulation in Rapid Accelerator mode.
If a Rapid Accelerator build includes referenced models (by using Model blocks), set up these models to use fixed-step solvers to generate code for them. The top model, however, can use a variable-step solver as long as the blocks in the referenced models are discrete.
In certain cases, changing block parameters can result in structural changes to your model that change the model checksum. An example of such a change is changing the number of delays in a DSP simulation. In these cases, you must regenerate the code for the model. See for more information.
For root inports, Rapid Accelerator mode supports only base as the
For root inports, when you specify the minimum and maximum values that the block should output, Rapid Accelerator mode does not recognize these limits during simulation.
In Rapid Accelerator mode, To File or To Workspace blocks inside function-call subsystems do not generate any logging files if the function-call port is connected to Ground or unconnected.