Robot failure

Only the following action operands should be specified in the error_defines file: ATOP, EXIT, AEXIT, STOP, ASTOP and TIME.

If a robot fails, the operator must mount the MTCs on the appropriate devices. Make sure that there are no inconsistencies arising in the archive record. The following options are available:

• The operator responds to the display of the devices by mounting the MTCs and placing them in the archive system input unit once they have been unloaded. When the archive system has started up, the archive system command INSERT is issued manually to “tidy up” the MTCs.

  Disadvantage
  The running ROBAR processes must be terminated and the MTCs just mounted must be added to the archive record by hand.

• The operator responds to the display of the devices by mounting the MTCs on the devices and, once they have been unloaded, returning them to their original location. It is not necessary to update the archive record in this case.

  Disadvantage
  Here, too, the running ROBAR processes must be terminated (STOP menu). When the archive system is restarted, the MTCs just mounted must be added to the archive record entry by hand.

Operator intervention is not always required if a robot fails for a short period only, since cumulated BS2000 console messages of type ? are fetched using ROBAR and processed by ROBAR after the RESTART.