Solution, Fault_write_passed_lock_failed – 403h, Cause – ThingMagic Micro Hardware User Manual

Page 80: Fault_protocol_no_data_read – 404h, Fault_afe_not_on – 405h

Advertising
background image

Protocol Faults

A D I V I S I O N O F T R I M B L E

Appendix A: Error Messages

75

Solution

This value is invalid or this version of SW does not support the protocol value. Check the
documentation for the correct values for the protocols in use and that you are licensed for
it.

FAULT_WRITE_PASSED_LOCK_FAILED – 403h

Cause

During a Write Tag Data for ISO18000-6B or UCODE, if the lock fails, this error is
returned. The write command passed but the lock did not. This could be a bad tag.

Solution

Try to write a few other tags and make sure that they are placed in the RF field.

FAULT_PROTOCOL_NO_DATA_READ – 404h

Cause

A command was sent but did not succeed.

Solution

The tag used has failed or does not have the correct CRC. Try to read a few other tags to
check the HW/SW configuration.

FAULT_AFE_NOT_ON – 405h

Cause

A command was received for an operation, like read or write, but the AFE was in the off

state.

Solution

Make sure the region and tag protocol have been set to supported values.

Advertising