Siemens SIMATIC MV500, Operating Instructions Manual, Page: 227 / 294

Service and maintenance
10.1 Error and diagnostics messages
SIMATIC MV500
Operating Instructions, 03/2021, C79000-G8976-C494-05
227
Error mes-
sage
Value
Onboard
PROFINET
Value
TCP/IP
and
RS232
Value
Ident pro-
file
(STATUS)
Description Corrective measures
No message -- -- E4FE84 Error in last command se-
quence
Note:
No diagnostic interrupt is
sent to the I/O controller.
May occur if triggering is too
fast. The Ident profile can only
process one command at a time
before a new command can be
executed.
No message -- -- E6FE01 A user with the "Take con-
trol" right has logged in via
WBM and has taken over
exclusive control from the
automation system.
Make sure that no user with the
"Take control" right logs in to the
reader during ongoing opera-
tion.
The automation system has
not been assigned any con-
trol rights.
Assign control rights to the au-
tomation system (Settings >
Communication > Use > Connec-
tion).
Self-acknowledging connection errors
The following connection errors are self-acknowledging:
•
Error "TCP communication"
• Error "Archiving/MMI communication"
• Error "PROFINET IO connection error"
• Error "PROFINET IO controller status 'Stop'"
As soon as the connection is re-established after an interruption, the optical reader exits the
error state. The optical reader returns to the mode prior to the occurrence of the error, for
example, back to processing mode.
The occurrence of these errors and their automatic acknowledgment are stored in the
diagnostic data records. Stored error messages are not overwritten by newer errors.
If there are error entries, a corresponding note appears in the WBM during processing mode
("Start") in the "Program > Info statistics" area.
Note
PROFINET IO error / OB 86 not programmed
Note that the occurrence of a PROFINET IO error in a SIMATIC S7 controller causes OB 86 (rack
failure OB) to be called. If you have not programmed OB 86, the controller goes to the "STOP"
state.