Eeprom-Failure - HARTING Ha-VIS RFID RF-R400 System Manual

Ha-VIS RFID RF-R400 – System Manual
112
Hex-value Transponder Status
0x05 Wrong transponder type:
• This command is not applicable at the transponder:
• A special command is not applicable to the transponder.
0x08 Authent error:
• If access password is wrong
Hex-value Parameter Status
0x10

EEPROM-Failure:

• The EEPROM of the reader is not able to be written on.
• Before writing onto the EEPROM a faulty checksum of parameters has been detected.
0x11 Parameter-Range-Error:
• The value range of the parameters was exceeded.
0x13 Login-Request:
• Configuration access without having logged in to the reader before.
0x14 Login-Error:
• Login attempt with wrong password.
0x15 Read Protect:
• The configuration block is reserved for future use.
0x16 Write Protect:
• The configuration block is reserved for future use.
0x17 Firmware activation required:
The firmware must be activated first using Ha-VIS RFID Config demo program and the
command "Set Firmware Upgrade". The update code must be ordered by HARTING
Technology Group.
1. Read the Device-ID using the command [0x66] Firmware version (Mode 0x80)
2. Send the Device-ID and the serial number of the reader to HARTING Technology Group
3. Write the upgrade code into the reader using the command [0x5F] Set Firmware Update
0x18 Wrong Firmware:
• Mismatch between RFC Firmware and Hardware
Hex-value Interface Status
0x80 Unknown Command:
• The reader does not support the selected function.
0x81 Length-Error:
• The selected function has the wrong number of parameters.
0x82 Command not available:
• A Host command was sent to the reader in the Buffered Read Mode.
• A Buffered Read Mode protocol was sent to the reader in the standard mode.
• The command with more bit does not correspond with the last command.
0x83 RF communication error:
• This error indicates that there is an error in communication between the transponder and
the reader. Reason for this can be:
• Timeout for transponder communication. "Transponder-Response-Time" in 7.2. CFG1:
Interface and Mode is too short.
• The collision handling algorithm was not continued until no collision is detected, reasons
for the break.
HARTING IT Software Development GmbH & Co. KG