1. Resonate RFID Reader Management User Guide
  2. Troubleshooting Application and RFID Reader Issues
  3. Determining the Root Cause of RFID Reader Issues
  • Resonate RFID Reader Management 2.0 User Guide
Determining the Root Cause of RFID Reader Issues
View content for :
Platform:

Determining the Root Cause of RFID Reader Issues

The
Resonate RFID Reader Management web interface
 displays notifications on the
Infrastructure
Devices
 page to provide information on RFID reader health. You can also access the RFID readers' logs from this page. Use this information to know the health of your readers, and if there is an issue, to help you determine the root cause of the issue, possibly remediating the issue before escalating it to Zebra support.

Troubleshooting RFID Reader Issues

If an RFID reader is experiencing an issue, the device grid displays warning and/or error alerts in the
Alerts
 column, as shown below.
Devices Page with an Alert
Screenshot of the Devices page with an alert.
Screenshot of the notification icon on the Devices page.
The following are the possible notification icons:
Device State
Icon
Description
Healthy
Healthy icon
The RFID reader is reporting no issues.
Warning
Warning icon
The RFID reader is reading and transmitting tag read data, but the reader is experiencing an issue (for example, it is starting to disconnect or overheat).
Critical
Critical/Error icon
The RFID reader is reading and transmitting tag read data, but the reader is experiencing an issue that is more serious than one that warrants just a warning (for example, it is overheating). You might also obtain this alert if the reader is not responding, so its status is unknown.
Error
Critical/Error icon
The RFID reader is experiencing a real-time, immediate problem (for example, after you send it a command, something fails).
Hover over the icon to see more details about the alert or error; refer to Available Alerts on how to resolve the issue.
For more information on an error, view the RFID reader's logs; to access the logs, select Device Settings
Device Settings
Logs
 at the far right of the reader's row. The
Logs
 dialog opens. After a few seconds, the reader's different logs load. You should typically start with the Application log for a general indication of what is happening with the Resonate Agent; then, click on one of the other logs based on your specific error.
  • Application Log
    : Records general events and errors related to Resonate Agent.
  • System Log
    : Records events and errors related to transport or management.
  • Directionality Log
     (if applicable): Records events and errors related to the portal or directionality.
  • Radio Log
    : Records events related to the radio.
Example Application Log
Screenshot of an example application log.
After viewing the logs accessible from the
Devices
 page, you should then look at the
reader adapter
 logs on the
Resonate server
. To do this, log in to a cluster node as
trif-user
, and retrieve the name of the device manager pods using the command: 
kubectl get pods -n zebra-reader-management | grep iotc-adapter-fixreader
This displays information about the reader adapter pod. Ensure the pod is in a
Running
state.
Retrieve the detailed status of the pod by running:
kubectl describe pods -n zebra-reader-management <pod name from above>
Retrieve the logs of the pod by running: 
kubectl logs -n zebra-reader-management <pod name from above>
The
Resonate RFID Reader Management
 Software Installation Guide provides additional commands to further troubleshoot issues. If you need to escalate the issue to another team, the best practice is to include the application logs and other device logs (if applicable), along with the reader adapter log.

Troubleshooting Issues between
Resonate
 and RFID Readers

Follow similar steps as for device errors.
Check for specific errors in the application logs of the device.
Attempt to correlate these errors with the reader adapter log.
If no issues are found in the reader adapter log, retrieve the name of the mqtt pod using the command: 
kubectl get pods -n zebra-reader-management | grep mqtt
Retrieve the logs of the mqtt pod by running:
kubectl logs -n zebra-reader-management <pod name from above>