Siemens SIMOTION SCOUT Configuration Manual page 179

● SUSPENDED (TASK_STATE_SUSPENDED)
Task suspended by function _suspendTask.
Use _resumeTask
at which it was interrupted.
● WAITING (TASK_STATE_WAITING)
Task is waiting due to function _waitTime or WAITFORCONDITION.
● WAITING_FOR_NEXT_CYCLE (TASK_STATE_WAIT_NEXT_CYCLE)
TimerInterruptTask waiting for start trigger.
● WAITING_FOR_NEXT_INTERRUPT (TASK_STATE_WAIT_NEXT_INTERRUPT)
SystemInterruptTask or UserInterruptTask is waiting for the triggering event to occur. When
an interrupt occurs, the SystemInterruptTasks are started and executed once. Up to eight
incoming interrupts can be stored in the buffer. If another interrupt occurs, the buffer
overflows and the CPU goes into STOP operating state.
● LOCKED (TASK_STATE_LOCKED)
Task locked by function _disableScheduler.
This status prevents the activation of all user tasks (except the IPOSynchronousTask and
IPOSynchronousTask_2) until command _enableScheduler is called. It does not, however,
affect system tasks. The time watchdog for cyclic tasks is not suspended.
Note
This also prevents the activation of the SystemInterruptTasks and UserInterruptTasks.
Controlling MotionTasks
It is possible to control MotionTasks via SIMOTION SCOUT without a user program that has
been created by the user. Consequently, you can test programs and influence MotionTask
sequences in a very specific way.
Selected MotionTasks can be stopped, and locked or restarted for the sequence.
This means that programs in MotionTasks can also be downloaded in RUN mode. If you have
made changes to sources and want to reload them in RUN mode, an active MotionTask can
prevent this. You can then terminate specific MotionTasks with SIMOTION SCOUT and then
carry out the download in RUN mode.
Additional references
Further information on downloading in RUN mode can be found in:
SIMOTION Basic Functions Function Manual
●
SIMOTION SCOUT Task Trace Function Manual
●
SIMOTION SCOUT
Configuration Manual, 11/2016
(name ) to cancel this command. The task then resumes from the point
Diagnostics
9.3 Device diagnostics
179