Siemens SIMATIC RF600 Series Configuration Manual page 249

Hide thumbs Also See for SIMATIC RF600 Series:
Table of Contents

Advertisement

"ER"
XML/
PLC block
LED
LED
(hex)
(hex)
2 Hz
0xC1
0xE4FE81
2 Hz
0xCA
0xE4FE8A
2 Hz
0xCB
0xE4FE8B
--
0xCC
0xE4FE8C
2 Hz
0xCD
0xE4FE8D
2 Hz
0xCE
0xE4FE8E
2 Hz
0x51
0xE5FE01
--
0x52
0xE5FE02
SIMATIC RF600
Configuration Manual, 11/2018, C79000-G8976-C386-07
Error description
The specified tag field of the transponder is unknown.
General error
No or bad configuration data/parameters were transferred.
Possible cause:
You are accessing a read point that is not configured.
Communication error between Ident profile and communications module. Handshake
error.
UDT of this communications module is overwritten by other program sections
Check parameter settings of communications module in the UDT
Check the Ident profile command that caused this error
Start "INIT" after correcting the error
Backplane bus / PROFIBUS DP / PROFINET error occurred
This error is only indicated when access monitoring has been enabled in the
PROFIBUS configuration.
Backplane bus / PROFIBUS DP / PROFINET bus connection was interrupted (wire
break on the bus; bus connector on the communications module was briefly un-
plugged)
Backplane bus / PROFIBUS DP / PROFINET master no longer addressing commu-
nications module
Execute "INIT"
The communications module has detected a frame interruption on the bus. The
backplane bus, PROFIBUS or PROFINET may have been reconfigured (e.g. with
HW Config or TIA Portal)
Firmware error
Possible cause: The firmware update was not run completely.
Internal communications error of the communications module/reader
Connector contact problem on the communications module/reader
Hardware of the communications module/reader has a defect; → Send in communi-
cations module/reader for repair
Start "INIT" after correcting the error
Internal monitoring error of the communications module/reader
Program execution error on the communications module / reader
Turn the power supply of the communications module/reader off and on again
Start "INIT" after correcting the error
The current command was aborted by the "WRITE-CONFIG" ("INIT" or "SRESET") com-
mand for the bus connector was pulled.
Possible causes:
Communication with the transponder was aborted by "INIT".
This error can only be reported if there is an "INIT" or "SRESET".
Incorrect sequence number order (SN) on the reader/communications module.
Incorrect sequence number order (SN) in the Ident profile
Service and maintenance
13.2 Error messages
249

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents