User`s guide

12 Execution Modes
The Only Rapid-Prototyping Feature Available Is Data Logging
Because host-target communication and target screen updating are disabled
during the entire run, most of the common rapid-prototyping features of the
xPC Target product are not available in polling mode. T hese include
• Parameter tuning — Neither through the command-line interface nor
through Simulink external mode
• Through scope objects — Not through the following types of s cope objects:
- host (xPC Target Explorer or scripts)
- target (scopes on the target screen if property Enable target scope
is enabled)
- file (xPC Targ et Explorer, scripts, or blocks, on target PC s that have
file systems)
• Signal monitoring — You cannot run a GUI interface on the h ost PC using
an environment that depends on communication between the host and
target computers.
• App lications using the xPC Ta r get API
• The Internet browser interface
• Other utilities like
xpctargetspy
The only rapid-prototyping feature available is signal logging, because the
acquisit ion of signal data runs independently from the host, and logged data
is retrie ved only aft er the execution is stopped. Nevertheless, being able
to log data allows gathering good enough informat ion about th e behavior
of the target application. Signal logging becomes a very important feature
in polling mode.
Multirate Simulink Mod els Cannot Be Executed in Multitasking
Mode on the Target PC
Because of the polling mode e xecution scheme, executing Simulink-based
target applications in m ultitasking mode is not possible. The modeling
of function-call subsystems to handle asynchronous events (interrupts) is
not possible either. This can be a hard restriction, especially for multirate
systems. Multirate system s can be executed in single-tasking mode, but
because of its sequential execution scheme for all subsystems with different
12-12