Siemens SIMATIC CP 440 Manual page 125

Table 8-2 Event Classes and Event Numbers, continued
Event No.
(05)01H Current job aborted as a result of CP
restart.
(05)02H Job not permitted in this operating mode of
the CP (e.g. device interface not
parameterized).
(05)0EH Invalid message frame length
or
The parameterized end-of-text
characters did not occur within the
maximum permissible length.
(05)17H Transmission length > 200 bytes is too
large for the CP
(05)1DH Send/receive job interrupted by:
Communication block reset
Reparameterization
(05)22H A new SEND job has been started,
although the old job has not yet been
completed.
Event No.
(07)01H With 3964(R) only:
Transmission of the first repetition:
An error was detected during
transmission of the message frame, or
The partner requested a repetition by
means of a negative acknowledgment
code (NAK).
(07)02H With 3964(R) only:
Error during connection setup:
After STX was sent, NAK or any other code
(except for DLE or STX) was received.
(07)03H With 3964(R) only:
Acknowledgment delay time exceeded:
After STX was sent, no response came
from the partner within acknowledgment
delay time.
Point-to-point connection CP 440 Installation and Parameter Assignment
A5E00057742-02
Event Class 5 (05H):
"Error while processing CPU job"
Event
Event Class 7 (07H):
"Send error"
Event
Diagnostics with the CP 440
Remedy
No remedy is possible at POWER ON. When
reparameterizing the CP from the
programming device, before describing an
interface you should ensure there are no
more jobs running from the CPU.
Parameterize the device interface.
The message frame is > 200 bytes in
length. Select a shorter message frame
length.
or
Add the end-of-text characters at the
place you want in the send buffer.
Split the job up into several shorter jobs.
Repeat the call for the communication block.
Only start the new SEND job when the old
job has been completed with DONE or
ERROR.
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
still has not been transmitted after the
maximum number of repetitions, an error
number describing the first error that
occurred is output.
Check for malfunctioning of the partner
device, possibly using an interface test
device switched into the transmission line.
The partner device is too slow or not ready
to receive, or there is a break on the send
line, for example. Identify the malfunctioning
of the partner device, possibly by using an
interface test device switched into the
transmission line.
8-7