Troubleshooting Connected I/O
Simulink® timer is very slow while running Connected I/O simulation.
This is due to presence of blocks with very less sample times. There is a two-way communication between Simulink and the Autopilot while running Connected I/O simulation. This introduces an inherent time overhead for a particular block execution. To resolve the issue, set the sample time of blocks to more than the block execution time for connected I/O simulation.
Build issue due to space in temp directory while running Connected I/O.
Ensure temp directory does not have any space in the full path.
The scope data may not match exactly with the real-time data as it depends on SCI baud rate, simulation speed, and number of tasks performed in step function.
Ensure the SCI baud rate is configured correctly.
Turn on the simulation pacing.