Technical data

SFBs for Compact CPUs
System Software for S7-300/400 System and Standard Functions - Volume 2/2
A5E00739858-01
28-67
Error in the SFB parameter configuration"
W#16#070C
Only for 3964(R):
Initialization conflict cannot be solved
because both partners are set to low
priority.
Change the parameters.
"Receive error"
Event class
Error code
Event Remedy
W#16#0801 Only for 3964(R):
Expecting the first repetition:
An error was detected when the
message frame was received and the
CPU requested a repetition with a
negative confirmation (NCC) from the
partner.
A repetition does not represent an error.
However, it can be an indication of disruptions
on the data link or of a faulty behavior of the
partner. If the message frame is not
transmitted within the maximum number of
repetitions an error number is reported which
describes the error that first occurred.
W#16#0802 Only for 3964(R):
Error while establishing the connection
• One or several characters (except
NCC or STX) were received when
idle
• After having received the STX the
partner transmitted more
characters without waiting for the
response DLE.
After the partner is powered ON:
• The CPU receives an undefined
character while the partner is
switched on.
Prove the faulty behavior of the partner if
required by hooking up an interface tester to
the data link.
W#16#0805 Only for 3964(R):
Logical receive error:
After receiving the DLE another
character was received (except DLE,
ETX).
Check whether the partner doubles the DLE in
the message frame header and in the data
string or if the connection is established via
DLE ETX. Prove the faulty behavior of the
partner if required by hooking up an interface
tester to the data link.
W#16#0806 Character Delay Time (CDT) was
exceeded:
• Two subsequent characters were
not received within the CDT.
Only for 3964(R):
• 1. The character was not received
within the CDT after sending the
DLE when the connection was
established.
The partner device is too slow or disrupted.
Prove the faulty behavior of the partner if
required by hooking up an interface tester to
the data link.
W#16#0807 Illegal message frame length:
A message frame with 0 length was
received.
Receiving a message frame with 0 length
does not represent an error.
Check why the communication partner
transmits message frames without user data.
W#16#0808 Only for 3964(R):
Block Check Character error BCC:
The internally generated value for the
BCC does not correspond with the BCC
received by the partner at the end of
the communication link.
Check whether the communication is
seriously disrupted. In this case you can also
see occasional error codes. Prove the faulty
behavior of the partner if required by hooking
up an interface tester to the data link.