Rockwell Automation 1770-KF2 Data Highway or Highway Plus Interface Module User Manual User Manual

Page 158

Advertising
background image

Error Reporting

Chapter 7

7Ć3

Prescan errors always cause the module to turn on the PROG light and
enter an error state. When the keylock is turned to PROGRAM, the
error state is exited; and the PROG light turned off.

For all prescan errors the upper two digits act as a pointer to the rung
containing the error. Rungs are numbered from 1 to 99, then wrap
around back to 0 through 99, and so on. The first rung after the header
rung is number 1.

If no prescan error is detected, the error code word is set to all zeros at
the end of the prescan.

Run-Time Errors: For all run-time errors the first two digits of the

code are a modulo 100 error counter. The first error is number 1.

Except as noted, the module continues operating after recovering from
a run-time error.

Run-time errors are divided into the following groups:

- Message Formatting: Numbered from 30 to 39. They are detected

as a message is being formatted and before it is sent. A few of these
errors result in the KA turning on the PROG light and entering the
error state.

- Reply Errors: Numbered between 50 and 59 and detected by the

local station when a reply is received.

- Remote Errors: Numbered from 80 to 89 and returned in the reply

message from the remote station as the result of errors in execution
of a message at the remote station. It should be noted that a Data
Highway module will continue to generate replies as long as it is
functioning properly. These errors are contained in the STS byte of
the reply message.

- Local Errors: Numbered 90 to 99 and detected by the local station;

they are the result of being unable to properly transmit on the
highway.

Error numbers are listed and explained below:

01 No longer used. In revisions previous to F for 1771ĆKA this code could be set as a result

of intermittent hard errors on the KA to PC cable.

02 The prescan aborted because the test codes in RACK 0 are bad. This error should

never occur; because if the test codes are ever bad, the PC should fault before the KA

ever gets to the prescan.

Advertising