Filter
Top Products
Appendix D. Logging ACS Robotics Motion 607
1st ed., 6/30/04 - 312579601
The HSC also makes a log entry for each permanent error, codes and indicates whether or
not the errors are considered permanent errors.
The record format used to log a hard fail to SYS1.LOGREC is shown in Table 68. This
record is a valid ‘‘Motion Hard Fail Software Error Record’’ only under the following
conditions:
• if the Record Type Field (bytes 642-643) has a value of X’6501’,
• the StorageTek identifier (X’FEEDFACE’ at bytes 644-647) is present, and
• the character ‘H’ appears at the byte 113 location.
124-127 LSM 9 Temporary motion error counts (binary)
128-131 LSM 10 Robotic motions started (binary)
132-135 LSM 10 Temporary motion error counts (binary)
136-139 LSM 11 Robotic motions started (binary)
140-143 LSM 11 Temporary motion error counts (binary)
144-147 LSM 12 Robotic motions started (binary)
148-151 LSM 12 Temporary motion error counts (binary)
152-155 LSM 13 Robotic motions started (binary)
156-159 LSM 13 Temporary motion error counts (binary)
160-163 LSM 14 Robotic motions started (binary)
164-167 LSM 14 Temporary motion error counts (binary)
168-171 LSM 15 Robotic motions started (binary)
172-175 LSM 15 Temporary motion error counts (binary)
176-641 Reserved
642-643 Record type X’6506’
644-647 StorageTek identifier X’FEEDFACE’
648-651 Timestamp Table
Table 67. Format for Total Motions and Temporary Error Counts (Continued)
Initiated and Temporary Error Motion Software Error Record
BYTE # Description of Field