Troubleshooting Connected I/O

Description

Simulink^® timer is very slow while running Connected I/O simulation.

Action

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.

Description

Build issue due to space in temp directory while running Connected I/O.

Action

Absolute path of the temp directory should not contain any white space. Enter the following MATLAB command to know the path of temp directory:

tempdir

Description

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.

Action

See Also

Communicate with Hardware Using Connected IO

Related Topics

• Getting Started with Connected IO