The actions to be executed are stored in one of two files:
Archive system actions are stored in roboter_cmds
(action type RC
), e.g.
:*:RC005:H '<####,EJ , ,FFFF,1,r, ,vvvvvv, ,AAAAAAAA,BBBBBBBB,UUUUUUUUU>'
Non-archive system actions are stored in message_resp
(action type MR
), e.g.
:*:MR760: TYPE % ROB7060 VOLUME EJECTED (TSN=tttt / VSN=vvvvvv) :*:MR300: RESPONSE tttt.
Every action code has a 3-digit number suffixed to the action type (RC005
, MR760
, MR300
).
Processing steps and error handling
In the message_xref
file a number of actions can be defined for each message code. Actions separated by ',' belong to the same processing step.
An archive system error code can be specified in angle brackets at the beginning of a processing step. In this case, control will branch to this processing step only if the corresponding error has occurred.
The end of a processing step is indicated by ';'.
If an error occurs during the execution of an action, ROBAR-SV branches either to the processing step with the corresponding error code or to the next processing step without an error code.
Actions which are to be executed in the event of particularly serious errors, such as robot failure, are defined in the error_defines
file. The keywords ATOP
, EXIT
and STOP
are available for this purpose. They are described on "File error_defines".
Example
For a console message with the message code MF999
(for example):
:*:MF999: RC005,MR760,MR300;\ <N301>MR765,MR320;\ <N302>MR765,MR320;\ MR765,MR330
the following actions are to be executed:
Archive system action
RC005
BS2000 actions
MR760
andMR300
If both actions have been successfully executed, processing of the console message terminates here.
If the first action (RC005
) is acknowledged by the archive system with error code N301
or N302
, the actions following <N301>
or <N302>
, i.e. actions MR765
and MR320
, are executed. If no error occurs, processing of the console message is complete.
All other negative acknowledgments will cause actions MR765
and MR330
to be executed.