
161
Intera 3.2
•
Error In (level): when true, the robot is stopped. The user will need to press the
run or reset button. The Error In signal can be asserted at any point in task exe-
cution, or even during training.
•
The Error In signal can be assigned to the task for each arm, but asserting
the signal on either task will stop both arms.
•
Pause (level): At any point during task execution, if the pause signal is asserted,
task execution will be paused until the pause signal is cleared.
•
Reset Count (edge): When the Reset Count pulse is detected, the task count will
be reset.
OUTPUTS
•
Done (level): true when the task is done, i.e., it has completed the number of
cycles specified by the count.
•
Goes to false immediately when the task is reset.
•
A task is only considered Done when it has completed the specified count
of cycles. If error conditions prevent the task from finishing then its count will
not increment and it will not be Done.
•
Increment Count (pulse): sent when the task has completed its last subtask and
the task count has been incremented.
•
If a subtask is unable to complete because of errors, then the task won’t
complete and this signal will not be sent.
•
If all subtasks are complete either because their count is done and has not
been reset or Skip is asserted, the task count will increment rapidly until a
subtask starts to run. In this case, the Task Increment Count signal won’t be
particularly useful.
•
Error Out (level): true when there is an error that prevents the task from running.
•
Error Out is asserted when there are alert stop messages from the UI includ-
ing EStop.
•
In a non-coordinated task, though the task for each arm has a separate
Error Out signal, they are usually both the same. (If Task Editor is used to set
the FailureStrategy to Stop, then an Action failure on one arm can assert Error
Out on that arm without asserting it on the other.)
•
If the Error Out signal is due to task-related causes such as failure to pick or
place, it will be reset when the task is reset. If the signal is due to hardware or
external errors, it will remain asserted through a reset until the error condition
itself is cleared.
•
For non-error conditions see Confusion below.
•
Confusion (level): true when the robot is showing confusion.