Table of Contents
Advertisement
VIPA System 300S
Event class 08h "Receive error"
Event class / number Description
08 05h
08 06h
08 08h
08 0Ah
08 0Ch
08 0Dh
08 15h
HB130 | CP | 341-1CH01 | en | 18-40
With 3964(R) only
Logical error during receiving:
After DLE was received, a further random code (other than DLE or ETX).
Remedy: Check whether partner DLE in message frame header and in data string is always in
duplicate or the connection is released with DLE ETX. Check for malfunction at partner device,
possible by using interface test device switched into the transmission line.
Character delay time (ZVZ) exceeded:
Two successive characters were not received within character delay time or
n
With 3964(R) only
n
1. character after sending of DLE during connection setup was not received within char-
acter delay time.
Remedy: Partner device faulty or too slow. Use an interface test device switched into the trans-
mission line to check.
With 3964(R) only
Error in block check character (BCC):
Internally calculated value of BCC does not match BCC does not match BCC received by
partner at end of connection.
Remedy: Check whether connection is badly damaged; in this case you may also occasionally
see error codes. Check for malfunction at partner device, possible by using interface test device
switched into the transmission line.
There is no free input buffer available.
Remedy: The FB P_RCV_RK must be called more frequently.
Transmission error:
n
Transmission error (parity error-, stop bit error or overflow error) detected.
With 3964(R) only
n
If faulty character is received in idle mode, the error is reported immediately so that distur-
bances on the transmission line can be detected early.
n
If this occurs during send or receive operation, repetitions are initiated.
Remedy: Disturbances on the transmission line cause message frame repetitions, thus low-
ering user data throughput. Danger of an undetected error increase. Correct fault by changing
system setup or line installation. Check connecting cable of communications partner or check
whether both devices have same setting for baud rate, parity and number of stop bits.
BREAK
Receive line to partner is interrupted.
Remedy: reconnect or switch partner on again.
Check and change the connector pin assignment of the 2-wire receiving line R(A), R(B).
Discrepancy between settings for transfer attempts at CP a communication partner.
Remedy: Parameterize same number of transfer attempts at communication partner as at CP.
Check for malfunction at partner device, possible by using interface test device switched into
the transmission line.
Diagnostics and error behavior
Diagnostics via FB STATUS
97
Advertisement
Table of Contents
