Choose from several deployment approaches based on application requirements, prototyping or production environment, and your current phase of the development process. If want to run fast, standalone simulations, such as batch or Monte Carlo simulations on your development computer, build an executable program with the rapid simulation (RSim) target. Another method of accelerating simulations is to generate an S-function block for use in another model. In addition to improving simulation speed, this approach reuses code and protects intellectual property. If code reuse or intellectual property protection is a primary goal, build a shared library (.dll, .so, or .dylib) to deploy.

With an external mode simulation, you create a communication channel between your development computer and a target processor that runs the executable file created by the code generation and build process. Through the communication channel, you can modify parameter values for the target program, and monitor and store signal data from the target program.

If real-time response is critical, build and deploy an executable program. Build the program from a component that controls a system or from a model that represents a system being controlled. In the component case, you build, deploy, and tune code as it runs on a real-time simulator or microprocessor. For a test environment, you build and download an executable program to a hardware-in-the-loop (HIL) simulation platform. After setting up the environment, run the executable program to validate the system or control unit in real time.

You also have the option of building an executable program that you can download to target hardware for real-time rapid prototyping or production. The executable program can be a standalone program that you integrate with an external real-time executive or operating system. Standalone executable programs require minimal updates to adapt to target hardware.