Why do I randomly receive a communication error when executing my model in external mode using Real-Time Windows Target 2.5.1 (R14SP1)?

When I connect to my target in external mode using Real-Time Windows Target 2.5.1 (R14SP1), the model will often execute for several seconds and then stop. The following error is displayed:

 Error occurred while executing External Mode MEX-file 'rtwinext':

 Incomplete packet in communication buffer.

The error is intermittent since it does not occur all of the time. When it does occur, the error is returned at different times during the simulation. For example, sometimes it is returned at 2.5 seconds, while other times it appears at 8.1 seconds of simulation time.

Answer 1

[MathWorks Support Team]

This bug has been fixed in Release 2007a (R2007a). For previous product releases, read below for any possible workarounds:

There is a bug in Real-Time Windows Target 2.5.1 (R14SP1) in the way that the Real-Time Windows Target kernel handles Hyper-Threading. This error is returned during communication between the Real-Time Windows Target kernel and Simulink external mode when Hyper-Threading is enabled.

The only work around for this issue, is to disable Hyper-Threading in the BIOS setup of the target machine (if the Target Machine BIOS setup allows this).