
Eliminating errors
104275_en_c00
PHOENIX CONTACT
5-9
201
Interface receives data
–
The specified serial port receives
data. Previously for at least one
minute no data was received.
–
202
No more collisions on the
RS-485 interface.
–
Previously, there were collisions
on the specified serial port. Since
one minute no more collisions
were detected.
–
203
No more parity errors.
–
Previously, there were parity errors
on the specified interface. Since
one minute no more parity errors
were detected.
–
204
No more stop bit errors.
–
Previously, there were stop bit er-
rors. Since one minute no more
stop bit errors were detected.
–
205
No overloading of the
SHDSL line anymore.
–
Previously, data loss has occurred
due to the overload of a SHDSL
line. Since one minute no more
data loss was detected.
–
206
Data is received from the
SHDSL port.
–
Data is received from the specified
SHDSL port and sent to the serial
interface. For at least one minute,
this has not been the case.
–
207
No more inconsistent de-
vice configuration de-
tected.
–
Previously, an inconsistent device
configuration has been detected.
For one minute, this could not be
detected any more.
Cause: probably link termination.
–
208
No more noise.
–
Previously, noise has been de-
tected on a serial port. Since one
minute there was no more noise
detected.
–
209
No protocol violations on
the serial interface any-
more.
–
Previously, protocol violations
were found on a serial interface.
Since one minute there were no
more protocol violations detected.
–
210
No overflow of the buffer
detected.
–
Previously, an overflow in the soft-
ware buffer has occurred. Since
one minute there was no overflow
detected.
–
Table 5-1
Diagnostic IDs
No.
Meaning
LED
Possible cause(s)
Remedy