Siemens SIMATIC CP 440 Manual page 127

Installation and parameter assignment
Table of Contents

Advertisement

Table 8-2
Event Classes and Event Numbers, continued
Event No.
(07)0BH
With 3964(R) only:
Initialization conflict cannot be solved
because both partners have high priority.
(07)0CH
With 3964(R) only:
Initialization conflict cannot be solved
because both partners have low priority.
Event No.
(08)01H
With 3964(R) only:
Expectation of the first repetition:
An error was detected on receipt of a
message frame, and the CP requests a
repetition by means of negative
acknowledgment (NAK) at the partner.
(08)02H
With 3964(R) only:
Error during connection setup:
In idle mode, one or more random
codes (other than NAK or STX) were
received, or
After an STX was received, the partner
sent more codes without waiting for
response DLE.
After POWER ON of the partner:
While the partner is being activated, CP
receives an undefined code.
(08)05H
With 3964(R) only:
Logical error during receiving:
After DLE was received, a further random
code (other than DLE or ETX) was
received.
(08)06H
Character delay time exceeded:
Two successive characters were not
received within the character delay
time, or
With 3964(R) only:
1st character after sending of DLE
during connection setup was not
received within the character delay
time.
Point-to-point connection CP 440 Installation and Parameter Assignment
A5E00057742-02
Event
Event Class 8 (08H):
"Receive error"
Event
Diagnostics with the CP 440
Remedy
Change the parameterization.
Change the parameterization.
Remedy
A repetition is not an error, but it can be an
indication that there are disturbances on the
transmission line or that the partner device is
behaving incorrectly. If the message frame
has still not been transmitted after the
maximum number of repetitions, an error
number describing the first error that
occurred is output.
Identify the malfunction on the partner
device, possibly by using an interface test
device switched into the transmission line.
Check whether the partner DLE in message
frame header and in data string is always in
duplicate or the connection is cleared down
with DLE ETX. Identify the malfunction on
the partner device, possibly by using an
interface test device switched into the
transmission line.
Partner device faulty or too slow. Identify the
malfunction, possibly by using an interface
test device switched into the transmission
line.
8-9

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents