User`s guide

12 Execution Modes
Restrictions In
troduced by Polling Mode
As explained abo
ve, polling mode ex ecutes the Simulink-based target
application in r
eal time exclusive ly. While the target application is executin g
in polling mode
, all background tasks, including those for host-target
communication
, target screen updating, and UDP transfers, are inactive.
This is becaus
e all interrupts of the target PC are fully disabled during the
execution of t
he target application. On one hand this ensures the highest
polling perfo
rmance; on the other hand, as a consequence the background
tasks are not
serviced.
The followin
g topics li s t all relevant restrictions of poll ing mode, which are
otherwise a
vailable i n the default interrupt m ode.
Host-Target Communication Is Not Available During the
Execution of the Target Application
If the target application execution is started in polling mode, e.g., wi th
start(tg)
host-target communication is disabled throughout the entire run, or in other
wordsuntilthestoptimeisreached.Eachattempttoissueacommandlike
tg
leads to a communication-related error mes sage. Even the start( tg)
command to start polling mode execution returns such an error message,
because the host side does not receive the acknowledgment from the target
before timing out. The error message when executing
start(tg) is not
avoidable. Subsequently, during the entire run, it is best not to issue any
target-related commands on the host, in order to avoid displaying the same
error message over and over again.
As a consequence, it is not possible to issue a
stop(tg) command to stop the
target application execution from the host side. The target application has to
reach its set stop time for polling mode to be exited. You can use
tg.stoptime=x
before starting the execution, but once started the application executes until
the stop time is reached.
12-10