Siemens SIMATIC S7-400 Equipment Manual page 99

Event No. Event
(05)0EH
• Invalid message frame length
or
• The configured end-of-text characters did not oc‐
cur within the maximum permissible length.
(05)17H Transmission length > 400 bytes (see chapter "Over‐
view of the Function Blocks (Page 73)") is too large
for the CP.
(05)1DH Send/receive job interrupted by:
• Communication block reset
• Parameter reassignment
(05)22H A new SEND job has been started, although the old
job has not yet been completed.
Event No. Event
(07)01H With 3964(R) only:
Sending 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 partner
within acknowledgment delay time.
(07)04H With 3964(R) only:
Termination by partner:
During current send operation, one or more charac‐
ters were received by partner.
(07)05H With 3964(R) only:
Negative acknowledgment during sending
Point-to-point connection CP 440 Installation and Parameter Assignment
Equipment Manual, 03/2022, A5E00057742-AE
Event Class 5 (05H): "Error processing a CPU request"
Event Class 7 (07H): "Send error"
Diagnostics with the CP 440
8.3 Diagnostics Messages of the Function Blocks
To correct or avoid errors
• The message frame is > 400 bytes (see chapter
"Overview of the Function Blocks (Page 73)"). Se‐
lect 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.
To correct or avoid errors
A repetition is not an error, however, it can be an indi‐
cation that there are disturbances on the transmission
line or a malfunction of the partner device. If the mes‐
sage frame has still not been transmitted after the
maximum number of repetitions, an error number de‐
scribing the first error that occurred is output.
Check for malfunctioning of the partner device, possi‐
bly 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. Iden‐
tify the malfunctioning of the partner device, possibly
by using an interface test device switched into the
transmission line.
Check whether the partner is also showing an error,
possibly because not all transmission data has arrived
(e.g. due to break on line) or due to serious faults or
because the partner device has malfunctioned. Identi‐
fy the malfunction, possibly by using an interface test
device switched into the transmission line.
Check if the partner is also showing an error, possibly
because not all transmission data has arrived (e.g. due
to a break in the send line) or due to serious faults or
because the partner device has malfunctioned. Identi‐
fy the malfunction, possibly by using an interface test
device switched into the transmission line.
99