62
Programming manual for Meca500 (for firmware 9.2.x)
TCP/IP COMMUNICATION
2.6. Management of errors and hardware stops
2.6.1 Errors detected by the robot
The robot goes into
error mode
when it encounters an error while executing a command (see
or a hardware problem (e.g., a torque limit has been exceeded). It then changes to 1 the value of es
(error state) in the response [2007][
as
,
hs
,
sm
,
es
,
pm
,
eob
,
eom
] of the
GetStatusRobot
. Recall that you
can also receive this message over the monitoring port (see Section
In addition, if you send other
commands to the robot, it will respond with the
[1011][The robot is in error.] message.
When the robot is in error move,
all pending motion commands are canceled (i.e., the motion queue is
cleared), the robot stops and ignores subsequent commands (but responds with the [1011] message)
until it receives a
ResetError
command. The robot will then execute all request commands and start to
accumulate motion commands in its motion queue. However, the commands in the motion queue will
be executed only once the
ResumeMotion
command is received by the robot.
2.6.2 P-Stop 2
As soon as the externally wired P-Stop 2 is activated (see the
), the robot motion is
stopped and the response [3032][1] is sent by the robot. The motors and the EOAT are still active (i.e.
the brakes are not applied) but remain immobilized until the P-Stop 2 is reset. The rest of the trajectory
is deleted (i.e., the motion queue is emptied).
If a motion command is sent to the robot while the P-Stop 2 signal is still on (and the robot is still
activated and homed), the command will be ignored and the message [3032][1] will be sent again by
the robot. If the P-Stop 2 signal is removed, and another motion command is sent, the command will be
ignored and the message [3032][2] will be sent.
Finally, to reset the P-Stop 2, you must remove the P-Stop 2 signal, and then send the command
ResetPStop
. The robot will respond with the message [3032][0].
2.6.3 E-Stop and P-Stop 1
Currently, the Meca500 cannot detect the difference between the ESTOP button on the power supply,
an externally wired E-Stop (pins E-Stop on the D-SUB connector) or an externally wired protective stop
(pins P-Stop 1), as explained in the
. Hence, for simplicity, in the remainder of this
section, we will only refer to the ESTOP button.
In release 3 of the Meca500, the ESTOP completely shuts down the robot. In release 4, when the ESTOP
is activated, the robot is decelerated to a full stop, the brakes are applied, power to the motors and the
EOAT connected to the robot's tool I/O port is cut, and the robot is deactivated. The robot then sends
the message [3070][1], in addition to the messages [2044] [The motion was cleared.] and [2004] [Motors
deactivated.]. The only way to reactivate the motors (and the EOAT) is to first press the RESET button
or activate the external Reset (pins Reset), which will produce the message [3070][0]. Then, you need to
re-activate the robot with the
ActivateRobot
command. If the Meca500 R4 was already homed, you do
not need to home the robot again, except if an MEGP 25* gripper was connected to the robot's tool I/O
port.
After an E-Stop, all settings (parameters) that are not persistant, such as the definitions of the
TRF and the WRF, and the desired turn of joint 6, will be set to their default values.