Critical events are designated with a STOP sign icon. Expand the event for more information, as
shown in Figure 103.
Figure 103 Critical event details
.
• The time stamp is in the format hours : minutes : seconds. The hours are in 24–hour clock format.
For example, in this case 14 is 2 p.m.
• The date is in the format year/month/day.
• The event ID is the number on the header line, 0x006E in this example. It uniquely maps to an
error code.
• HE designates a hard error. The STOP sign icon and the word Crit before the event ID also in-
dicate a hard error.
• The text description in the header (“robotic controller error” in this example) is the simple text de-
scription of the main error code.
• The main error code (0x83) is displayed in parenthesis as the Global error code. The error codes
are described in Main error codes. The text after the main error code (Robotic controller
generic problem in this example) is the text description for the error code.
• The error sub-code (0x02) is displayed in parenthesis as the Module error code. The error sub-
codes are described in Error sub-code descriptions. The text after the error sub-code (Robotic:
connection to slave robotic failed in this example) is name of the component followed
by the text description of the error sub-code.
• The Current command provides information for factory use only.
Troubleshooting184
To Next Page
Loading...
Need help?
General
