Technical data

Table Of Contents
SFBs for Compact CPUs
System Software for S7-300/400 System and Standard Functions - Volume 2/2
28-70
A5E00739858-01
Error in the SFB parameter configuration"
W#16#090D
Only for RK 512:
Up to now there is no
restart at the partner.
Restart the partner PLC or set the operating
mode selection switch to RUN.
W#16#090E
Only for RK 512:
Received unknown
error number in the response message
frame.
Check whether the error is the result if
disturbances or faulty partner behavior. Prove
this with the help of an interface tester you
hook up into the data link.
"The CPU has detected errors in the response message frame of the partners"
Event class
Error code
Event Remedy
W#16#0A02
Only for RK 512:
Error in the structure
of the received response message
frame
(1. Byte not 00 or FF)
Prove the faulty behavior of the partner, if
required, by hooking up an interface tester to
the data link.
W#16#0A03
Only for RK 512:
received response
message frame contains too many or
insufficient data.
Prove the faulty behavior of the partner, if
required, by hooking up an interface tester to
the data link.
W#16#0A05
Only for RK 512:
No response
message frame from the partner within
the monitoring time.
Is the partner a very slow device?
Quite often this error is also displayed as a
result of a previous error. For example,
receive procedure errors (event class 8) can
be displayed after a FETCH message frame
was transmitted.
Reason: The response message frame could
not be received due to disturbances, the
watchdog time expires. This error might also
occur if the partner is restarted before it was
able to respond to the last received FETCH
message frame.
"Warnings"
Event class
Error code
Event Remedy
W#16#0B01 Input buffer loaded over 2/3 of its
capacity
Call the receive block more frequently in order
to avoid an input buffer overflow.