Select the transport layer that external mode uses to exchange data between the host computer and the target hardware.
XCP on TCP/IP
Run external mode in a background thread
Force the external mode task in the generated code to execute in a background thread.
When external mode runs in the model thread, external mode executes after each execution step of the model and collects data at the base rate of the model. When model code consumes most of the thread execution time in each time step, external mode execution overruns into the next time step. This overrun delays the start of the next model execution step and degrades the real-time behavior of the deployed model.
You can configure external mode to run in a background thread. When external mode runs in a background thread, it executes in the time between the end of model code of one time step and the start of the next time step. By not blocking the model step, external mode can be used in systems that require real-time execution. This configuration enables direct observation of the deployed model on the hardware board as it would behave in standalone operation.
When model code consumes most of the execution time for each time step, external mode in the background thread starves for execution time. Without sufficient time to collect and transmit data from the hardware board to the host computer, data packets drop. This case results in gaps in the data logging.
To help avoid dropped data packets in deployed models where real-time execution takes priority over data logging, configure external mode to operate as a background task.
Run external mode in a background thread parameter is not recommended for models that use a very small time step or that might encounter task overruns. These situations can cause Simulink® to become unresponsive.
Enter the port for the IP address of the hardware board.
To view the external mode execution progress and updates in the Diagnostic Viewer or in the MATLAB® command window, select this check box.