User's Guide
Table Of Contents
- THINGMAGIC M6e User Guide
- Introduction
- Hardware Overview
- Hardware Interfaces
- Digital/Power Connector
- USB Interface
- General Purpose Input/Output (GPIO)
- Power Requirements
- Special RF Power Output Requirements for the M6e-A
- Environmental Specifications
- Electro-Static Discharge (ESD) Specification
- Mounting Screw Clearance
- Assembly Information
- Antennas
- M6e Mechanical Drawing
- Authorized Antennas
- M6e-A Authorized Cables
- Firmware Overview
- New Features - Version 1.21.2
- Margin Read Support for Monza6 Tags
- NXP UCODE7 Configuration Support
- Gen2 Parameters in Metadata
- Support for Acura Gen2V2 Tags
- Support for GEN2V2 Embedded Tag Ops
- Gen2V2 Support
- Denatran Tag Support
- Configurable T4 for Gen2 Protocol
- Ability to “Read Data” Immediately After Sending a “Write EPC” or “Write Data” Command
- Decoupling Antenna Selection from AsyncOnTime
- Support for Additional Regions
- Support for Set/get Quantization Value and Minimum Frequency in Open Region
- Operational Notes
- Boot Loader
- Application Firmware
- Custom On-Reader Applications
- New Features - Version 1.21.2
- Communication Protocol
- Functionality
- Specifications
- Compliance and IP Notices
- Error Messages
- Getting Started – Development Kit and Carrier Board
- Environmental Considerations
ThingMagic M6e User Guide 52
www.JADAKtech.com
Protocol Fault Errors
Message Code Cause Solution
FAULT_NO_TAGS_FOUN
D
400h A command was received
(such as read, write, or lock)
but the operation failed. There
are many reasons that can
cause this error to occur,
including:
• No tag in the RF field
• Read/write power too low
• Antenna not connected
• Tag is weak or dead
Make sure there is a good tag in
the field and all parameters are
set up correctly. The best way to
check this is to try tags of the
same type to rule out a weak tag.
If none passed, then it could be
software configuration such as
protocol value, antenna, and so
forth, or a placement configuration
like a tag location.
FAULT_NO_PROTOCOL_
DEFINED
401h A command was received to
perform a protocol command
but no protocol was initially
set. The reader powers up
with no protocols set.
A protocol must be set before the
reader can begin RF operations.
FAULT_INVALID_PROTO
COL_SPECIFIED
402h The protocol value was set to
a protocol that is not
supported with the current
version of software.
This value is invalid or this version
of software 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 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.
Try to write a few other tags and
make sure that they are placed in
the RF field.
FAULT_PROTOCOL_NO_
DATA_READ
404h A command was sent but did
not succeed.
The tag used has failed or does
not have the correct CRC. Try to
read a few other tags to check the
hardware/software configuration.
FAULT_AFE_NOT_ON 405h A command was received for
an operation, like read or
write, but the AFE was in the
off state. This will also occur
for a M6e module if antenna
detection is enabled, but no
region has been selected.
Make sure the region and tag
protocol have been set to
supported values.
FAULT_PROTOCOL_WRI
TE_FAILED
406h An attempt to modify the
contents of a tag failed. There
are many reasons for failure.
Check that the tag is good and try
another operation on a few more
tags.
FAULT_NOT_IMPLEMEN
TED_FOR_THIS_PROTO
COL
407h A command was received
which is not supported by a
protocol.
Check the documentation for the
supported commands and
protocols.