Error messages
4.2 STEP 7 - error messages
Ident profile and Ident blocks, standard function for Ident systems
122 Function Manual, 10/2018, C79000-G8976-C387-04
If you have inserted the blocks and data types in your project and you encounter problems
during compilation, please check the following points:
● The block name, the block number and the data type name must not be changed.
● The content of the data types "IID_CMD_STRUCT" and "IID_HW_CONNECT" must not
be changed. The content may only be adapted when these have been linked into a data
block as variables.
● If you use the Ident blocks, the data types "IID_HW_CONNECT" and
"IID_CMD_STRUCT" and the block "Ident_Profile_1KB" must always exist in your project.
Errors from the communications module/reader
The causes of these errors can, for example, be as follows:
● Errors have occurred in communication between the CM and the reader or between the
reader and the transponder.
● The communications module is unable to process the command.
Byte 3 of the "STATUS" is not relevant for the error messages.
Table 4- 2 Error messages from communications module/reader or from the Ident profile via the "STATUS" output pa-
rameter
0xE1FE0100 Memory of the transponder cannot be written to
• Transponder memory is defective
• Transponder EEPROM was written too frequently and has reached the end of its service life
• Transponder is write protected (Memory Lock)
0xE1FE0200 Presence error: The transponder has moved out of the transmission window of the reader. The command
was executed only partially.
Read command: "IDENT_DATA" has no valid data.
Write command: The transponder that has just left the antenna field contains an incomplete data record.
• Operating distance from reader to transponder is not being maintained
• Configuration error: The data record to be processed is too large (in dynamic mode)
• With timeout: No transponder in the antenna field
0xE1FE0300 Address error
The address area of the transponder has been exceeded.
• Start address of the command start has been incorrectly set
• Transponder is not the correct type
• Attempted write access to write-protected areas
To Next Page
Loading...
