User`s guide

Event Mode Da ta Acquisition
Event Mode Data Acquisition
In this section...
“Guidelines” on page 14-11
“Limitations” on page 14-11
Guidelines
To acquire event mode data rather than polling d ata, note the following
guidelines:
• Ensure that you have set the priority of the
xcpserver block to the lowest
possible . S ee suggested prio r ity valu e s in “Setting Up and B ui lding the
Model” on page 14-4.
• The x PC Target 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 d ecimate the
data to match the actual execution. (The xPC Target 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.
Limitations
The event mode data acquisition has the following limitations:
• Every piece of data that the xPC Target software adds to the event list
slows down the target application. The amount of data that you can observe
depends on the model sample time and the speed of the target PC. It is
possible to overload the target PC CPU to the point where data integrity
can no long er be guaranteed.
• You can only trace signals and scalar parameters. You cannot trace vector
parameters.
14-11