Event Mode Data Acquisition


To acquire event mode data rather than polling data, note the following guidelines:

  • Set the priority of the xcpserver block to the lowest possible. See suggested priority values in Setting Up and Building the Model.

  • The Simulink® Real-Time™ software generates events at the base sample rate; this execution rate is the fastest possible. If you are tracing a signal that is updated at a slower rate than the base sample rate, you must decimate the data to match the actual execution. (The Simulink Real-Time software generates the event name with the ASAP2 generation during model code generation.)

  • You can associate signals with the event generation through the Vector CANape® graphical user interface.

See the Vector CANape documentation for further details on associating events with signals.


The event mode data acquisition has the following limitations:

  • Every piece of data that the Simulink Real-Time software adds to the event list slows down the real-time application. The amount of data that you can observe depends on the model sample time and the speed of the target computer. It is possible to overload the target computer CPU to the point where data integrity is reduced.

  • You can only trace signals and scalar parameters. You cannot trace vector parameters.

Was this topic helpful?