RobotStudio event

Stop/AllMoveTask instruction causes error state?

When using the Stop/AllMoveTask instruction in a multimove system it will enter an error state.  Should it be this way?  I would like to send a robot to a service position and stop the other tasks so the operator may enter the cell, but I'm also using the error state to turn on an alarm...kind of annoying when doing a scheduled robot service.  Any alternatives you can think of?

Thanks!

Comments

  • DanS
    DanS ✭✭
    "Stop" doesn't cause an error state, but "StopAllMoveTask" does?