Real-Time Windows Target

Plots Not Visible in Simulink Scope Block

For data to plot correctly in a Simulink Scope block, you must specify the following:

• rtwinext as the MEX-File for external interface on the External Target Interface dialog box
• External selected from the Simulation menu
• Connect to target selected from the Simulation menu
• Select one or more signals for capture (designated with "X") in the External Signal & Triggering dialog box
• Duration * Fixed Step Size close to or less than the X range in the Scope block
• Correct mode (one-shot vs. normal)
• Appropriate signal levels to allow triggering
• Y range on Simulink Scope block axes large enough to span the signal amplitude
• X range
• Arm when connect to target in the External Data Logging Configuration dialog box or arm in the External Data Logging Control Panel
• Start real-time code selected from the Simulation menu

If you are unable to see signals plotted in your Simulink Scope blocks after all of the above items have been selected, failure to obtain time responses in Scope blocks may be due to insufficient CPU time. To determine CPU utilization, type rtwho. The rtwho command returns information about MATLAB performance. The value returned is an indicator of how much loading your model places on the CPU. If Scope blocks fail to plot, this may be an indication that insufficient time is available between sample intervals to allow data to be transferred back to the MATLAB environment where the plotting is performed. To test for this condition, you can run one of the demonstration models, or you can try running your model at a significantly slower rate to determine whether this is the cause. We recommend that MATLAB performance does not fall below 80%.

Troubleshooting

Compiler Error Message