1. Impinj Support Portal
  2. Readers
  3. Learning Center - App Notes, Sample Code, and Tips

Troubleshooting Reader Connectivity Issues

Avatar
Daniel Cohen
Follow
R700 Speedway Revolution and Gateways

Overview

The purpose of this article is to discuss techniques for troubleshooting and resolving connectivity with the Impinj R700 RAIN RFID reader. Each one of the troubleshooting steps mentioned are grouped into their appropriate section and can be done individually.

Table of Contents

  

Physical Connection

You can connect to the reader via the Ethernet port utilizing a PoE injector.

Several different applications can help you connect to your readers and gateways. A program named Putty (You can download and install PuTTY from http://www.putty.org/) on Windows based systems or ssh commands on UNIX based ones are a few examples. 

There are also system configuration settings that should be setup correctly for on-reader applications to work with outbound communications:

  1. Via DNS
  2. Via NTP

Connecting to the reader or gateway via the Ethernet port.

Basic Troubleshooting Steps

#
Troubleshooting Steps
Details
1 Ping the reader/gateway
  1. Open a Command prompt.
  2. Ping the reader over the network via their hostname and ip address.
  3. Consider pinging both IPv4 and IPv6 addresses if on a dual IPv4/IPv6 network. E.g.
    1. ping -4 impinj-XX-XX-XX
    2. ping -6 impinj-XX-XX-XX

        Note: Please remember to replace the XX-XX-XX with the last three (3) HEX characters of the MAC address. (If the MAC address is 00:16:25:11:FA:E1 then the hostname will be impinj-11-FA-E1)

        Note: Please try adding ".local" or ".local.<tld>" to the end of the reader hostname if the pings do not work.

        Note: If the ping command does not initially succeed, flush the DNS cache per the directions further down this page.

        Note: We are assuming your network is configured with a router, DHCP and DNS server.
2 SSH to the reader or gateway
  1. Launch PuTTY. If prompted, run it as administrator.
  2. In a WINDOWS environment, setup a SSH connection in Putty to your reader's hostname or IP address on port 22. It will look like the example shown belowmceclip2.png
  3. Or In a UNIX environment, you will issue the command:
         ssh -l root <READER HOSTNAME OR IP>
  4. Login as user root with the default password of "impinj" (unless it was previously changed to something else)

mceclip1.png
3 Check DNS on the network
  1. In Windows Command prompt, issue:

> nslookup impinj-XX-XX-XX,

> nslookup <reader/gateway IP address>.

Both commands should resolve correctly to each other.
4 Disable PC Wifi

The PC may be attempting to access the reader via its' wireless (WiFi) port instead of its' Ethernet port

1. Turn off PC's WiFi port, remove Ethernet cable and then re-insert allowing the “Acquiring Network Address” message (in lower, right-side Windows toolbar) to time out and then re-attempt

2. Once connection is established, you can re-enable WiFi

Note: Here is a link to a Microsoft article on how to change the network adapter priority to eliminate the need for turning off the Wi-Fi connection:

https://support.microsoft.com/en-us/help/2526067


Cannot connect when directly connecting a single reader or gateway to the Host PC via Ethernet:

#
Troubleshooting Steps
Details
5 Re-install Bonjour

Adobe Bonjour is an open source implementation of zero-configuration networking software.  Adobe Bonjour checks to see whether the DNS server configured on your computer supports service discovery.

  1. Uninstall Bonjour from your machine
  2. Download Bonjour print services if not already done
  3. Install Bonjour print services on your PC
  4. Make sure Bonjour is installed on the PC via Control Panel > Add or Remove Programs.

Note: If you are unable to use Bonjour, please configure a host to have a 169.254.1.x (255.255.255.0 mask) ip address and then access the reader via 169.254.1.1.

Note: Please make sure your host machine has configured the ethernet to a dynamic ip address.  Otherwise, communication with the reader will NOT be possible
6 Check .local name

Bonjour is used to access the reader/gateway by hostname when you are directly connected to it, but it may not help when the reader/gateway is on the network.

  1. Add .local to the end of the reader/gateway host name. For example, try pinging impinj-XX-XX-XX.local
  2. Note: Using .local depends on the tld assigned for your company. For instance, tld could be .local.tld, or something else.
  3. Note: We recommend that you register DNS names for the top-most internal and external DNS namespaces with an Internet registrar.
7 Check the default IP Address

If your network does not support DHCP, the reader/gateway defaults to the following fixed IP address: 169.254.1.1.

If this address is already in use, the reader/gateway will select a random fixed IP address in the 169.254.xxx.xxx link local address range.

  1. Connect to 169.254.1.1
  2. If the prior step does not work, scan for other readers/gateways on 169.254.xxx.xxx
    • Commands like "arp" can assist with this search.



Cannot connect when using Ethernet through a router, switch or hub:

#
Troubleshooting Steps
Details
8 Use Wireshark to determine network issues
  1. Download and Install Wireshark from https://www.wireshark.org/.
  2. Run wireshark,
  3. Select the appropriate network connections,
  4. Filter by "llrp"
  5. Watch the messages as you try to connect to the reader/gateway.

The messages should give an indication of what is wrong with the connection.

Note: We are assuming your network is configured with a router, DHCP and DNS server.
9 Flush the DNS cache on the PC

http://www.tech-faq.com/how-to-flush-dns.html

 

Cannot connect when using Windows Virtual Machine:

From time to time we get connectivity issue questions from customers using Windows Virtual Machines to run ItemTest.

#
Troubleshooting Steps
Details
10

Verify the Windows Virtual Machine network settings are setup properly.

 

Try using different network settings until it works. Here is an example of how that might look in Virtual Box when selecting a Bridged Adapter:

It should be roughly the same in similar applications.

 

 

RShell related checks:

You may be able to access the reader either via ssh or console cable. If so, it is important to run thru the following RShell activities: 

#
Troubleshooting Steps
Details
11 Ensure Dynamic (DHCP) mode set
  1. RShell (SSH or via serial/console cable) into the reader and issue these commands:
    1. show network summary
  2. If ipAddressMode does not equal ‘Dynamic’, issue the following RShell commands:
    1. config network ip dynamic
    2. reboot
  3. Check to see if the ip address is specified.
    1. The following would be a sign that the reader has not been assigned an IP address via DHCP, or assigned itself a link-local address (169.254.xxx.xxx).

  1. You can also get this information hitting the Impinj IoT Restful Interface with curl command:

    curl -f --insecure --header "Content-Type: application/json" --location --request GET http://root:impinj@<reader hostname/ip>/api/v1/system/network/interfaces

    Note: replace <reader hostname/ip> with the hostname or ip of the R700.
    Note: change root:impinj to the root:<password> of the reader if it is different.

  2. The following would be a sign that the reader did receive the ip address from dhcp


Notice how an ip address is actually specified.
12 Setup the reader/gateway with a static IP address

1. Ensure the IP address of the reader/gateway is using same subnet mask as the PC
2. Check for duplicate IP addresses assigned on the same network. One way to do this is to turn off the reader/gateway and ping the ip address to see if another system is using it.

  1. RShell (SSH or via serial/console cable) into the reader
  2. Find out the reader's IP address by typing the following at the RShell prompt:
    • show network summary

  3. The results (as shown below) indicate a couple of things:
    • ipAddressMode = 'Dynamic' means this reader is set to acquire its IP address via DHCP. If this reader was set to a static IP address, it would say 'Static'.
    • ipAddress = '192.168.0.20' indicates this is the IP address for this reader.

6.png

4. To change the IP address, type the following at the RShell prompt:

    1. config network ip static xxx.xxx.xxx.xxx

      ("xxx"s are values between 1 and 255. For example, "config network ip static 192.168.0.20")

      Or use the following format:
    2. config network ip static xxx.xxx.xxx.xxx  xxx.xxx.xxx.xxx  xxx.xxx.xxx.xxx  xxx.xxx.xxx.xxx

      (for example, if you type:

      > config network ip static 192.168.0.20 255.255.255.0 192.168.0.1 192.168.0.255

      you are configuring the IP address, Netmask, Gateway, and Broadcast Address respectively, separated by a space character)
      NOTE: consult the RShell Reference Manual for additional details.

5. Reboot the reader with RShell command:

      • reboot
13 Check the logs

An explanation for how to acquire the reader/gateway logs can be found here: https://support.impinj.com/hc/en-us/articles/202756238-How-do-I-capture-logging-events-from-my-reader-

  1. If you encounter an "Assert" error message in the logs this most likely means one of the reader/gateway programs has crashed and could be the reason the port is not open.
    1. Here is an example message from the logs that may occur:

Event9='May  9 14:07:10 (none) MC4: Layer1: Assert - File: /mnt/work/firmware/reader/apps/mc4/layer1/spaceman/rfmux_common.c, Function: RFMux_updateFirmware, Line: 1308'


2. These type of issues would require you to send the logs to support@impinj.com so they can determine what is going on and check whether your reader/gateway is still under warranty.
14 Check port configuration settings

1. Run the following RShell commands to see if the configurable ports are enabled:

show network ssh

show network http

show network sftp
 

2. Now that you know what is enabled or disabled, configure the system for what you need using the following commands:

 

config network ssh enable

config network http enable

 

Note: ftp was removed with Impinj Firmware 8.0
15 Disable rfid llrp outbound

The LLRP Port will be disabled when the rfid llrp outbound feature is enabled. Please disable the outbound feature by issuing rshell command:

    config rfid llrp oubound service off

A reboot may be required afterwards.

 

Cannot connect when using either Ethernet setup:

#
Troubleshooting Steps
Details
16 Check whether the reader/gateway ports are responding.

There are multiple ways to accomplish this activity. One such way is Putty on Windows based systems (Shown below) or ssh commands on UNIX based ones.

  1. Launch PuTTY. If prompted, run it as administrator.
  2. Enter the reader/gateway address.
  3. Try connecting with putty to port 5084 and 5085 and send us the output?  It should look like:

A working system would output something similar to:
17 Perform a factory reset on the reader/gateway https://support.impinj.com/hc/en-us/articles/202756458-Performing-Factory-Reset-on-the-Speedway-Revolution-Reader-VIDEO-
18 Try connecting via POE
  1. If you are currently powering the reader/gateway via a power adapter to the wall and have the capability to power the reader/gateway over POE, then try switching the reader/gateway to POE.
19 Change Switch/Router Ports
  1. When connected via POE, please move the current port on the switch/router the reader/gateway is connected to a different one.
20 Disable PoE on the Switch

The reader/gateway specification dictates that when both the power adapter and Ethernet cable with PoE are connected to the reader, the reader then uses the power adapter to draw power and uses the Ethernet for network communication.

We've received reports in the past where if customers were using a certain type of Cisco switch and the network communication did not work.

The Cisco switches have a behavior of disabling port operation if the PoE device doesn’t draw any current. The following Cisco support page explains the details of configuring PoE :

http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst4500/12-2/31sg/configuration/guide/conf/PoE.html

  1. When the reader/gateway is plugged into both power (wall.. aka brick) and PoE port, then disable PoE on the switch/router.
    • One possible way to do this is:

(In this example slot 5, port 2 is being set to PoE = “never”.)

Switch# configure terminal 
Switch(config)# interface fastethernet 5/2

Switch(config-if)# power inline never

Switch(config-if)# end
21 Confirm power capabilities of PoE switch
  1. Confirm that you are not exceeding the power capabilities of the PoE switch.
    1. The Speedway Revolution draws 11.5W max so be sure that the switch supports the number of connected readers and any other powered devices. 
      1. Note: If the power level is too low, the reader will begin rebooting if not powering down.
    2. The xArray has been measured to draw 13.6W
      1. Note: If the power level is too low, the gateway can become highly erratic without rebooting or show the red fault LED remaining lit perpetually.

Note: All of our readers and gateways are compliant with the PoE 802.3af standard maximums of 15.4 watts. All PoE ports should be configured to support the maximum current draw.

Note: Most PoE switches will have a maximum power budget that can be exceeded if there are too many PoE devices connected.
22 Check the PoE cable length
  1. Confirm that the Ethernet cable run from PoE source to reader does not exceed 100m (~330 feet).
23 Swap readers/gateways
  1. Swap known good readers/gateways with the one(s) that might not be working.
24 Swap Ethernet cables
  1. Swap known good cables with the one(s) that might not be working. This will identify any Defective Ethernet (RJ45) cable(s).

 

Cannot connect when another Ethernet connection already exists

#
Troubleshooting Steps
Details
25 Uninstall existing on reader/gateway applications.

Visit https://<reader/gateway name or ip address>/

  1. Check what interface is being used:

mceclip3.png

Is the case above, the LLRP Interface is selected.  If the "Impinj IoT Device Interface" is selected, then the LLRP port would NOT be available.

    2. Check "CAP Version" in the "Firmware" section of the reader Web UI

mceclip4.png

  • Note: If "CAP Version" is missing, then nothing is installed on the reader/gateway.

   3. If an on reader application is taking over the LLRP port, you can uninstall an on-reader application by issuing the following RShell command:

         config image removecap
26 Check for other applications connected to this reader/gateway
  1. Assuming the LLRP Interface is used, RShell (SSH or via serial/console cable) into the reader and issue these commands:

    "show rfid llrp summary"

mceclip5.png

  • In the case above, nothing is connected to the reader and you should be able to connect to the reader via port 5084.

If an application was connected, you would see the host ip address is connected to the LLRP Port.

1. Locate this system and get the application terminated.

2. Rebooting the reader/gateway may also be an option.

 

"Connection Denied" Errors:

#
Troubleshooting Steps
Details
27 Update the firewall rules

If a firewall is between your host and reader/gateway, it is highly likely the communication is being prevented from there.

  1. Add the reader/gateway IP address and/or host name to your firewall program as “safe” or “allowed”.

    • Alternatively, add the following ports for communication to the firewall:

Port

Description

 Direction

22

SSH (RShell) Port

 To Reader

80

Speedway Reader Web UI

 To Reader

123

Reader NTP Protocol

 From Reader
162*
 UDP Port for SNMP Trap From Reader

443 

Speedway Reader Web UI

 To Reader

5084  *

Unsecurred LLRP Port

 To Reader

5085  *

Encrypted LLRP Port

 To Reader

 These can be enabled and disabled
* These ports are changeable
28 Ensure you have the latest and appropriate region firmware installed.

Visit https://<reader/gateway name or ip address>/

  1. Check to make sure you have the latest installed (8.0.1.240 as of 2/19/2022):

mceclip7.png

Impinj Partners can get the latest firmware here: https://support.impinj.com/hc/en-us/articles/202755438-Octane-Firmware-for-Readers

     2. Check to make sure the Regulatory Region is correct:

mceclip8.png
29 Make sure the port is setup properly.

When using the LLRP Interface, the default llrp address to connect to the reader is on port 5084.  However, it can be changed and you will not be able to connect to the reader on the default port.  You can check the current setting by issuing command:

    show rfid llrp inbound

Can you please change it back to 5084 by issuing command:

    config rfid llrp port 5084

Another command to run in case llrp encryption is enabled on port 5085 is:

     config rfid llrp inbound security none

 

Connecting to the reader or gateway via the micro usb to Console port.

Basic Troubleshooting Steps

#
Troubleshooting Steps
Details
30 Confirm the Console cable is in the right port

Connecting to the reader console port requires a USB cable with a micro-USB connector
31 Check modem settings are correct
  1. Expect the following settings to be used:
    • Bits per second = 115200
    • Data bits = 8
    • Parity = None
    • Stop Bits = 1
    • Flow Control = None
32 Connect to the Reader or Gateway
  1. Here is an example of how to connect using Putty on a Windows Environment:
    mceclip2.png
  2. After you click the "Open" button, you should get an RShell login prompt.
    mceclip4.png
  3. If you see a blank screen, hit the "Enter" key once to get the login prompt.
  4. Type the following login and password information:
    a) Login: root
    b) Password: impinj
        (the password may not be shown as you type them)
33 Find the COM port number

How to find COM port number

  1. Press the Windows key and R at the same time. Run dialog opens.
  2. Enter devmgmt.msc and click OK button. If prompted, choose Yes.
  3. In Device Manager, expand Ports (COM & LPT).
  4. Find "USB Serial Port (COMx) entry. Use this COM port number in PuTTY's serial connection (in the example below, it is COM4).2.png

 

Communication issues from the reader to the outside:

You may be able to access the reader either via ssh or console cable but there are issues with on-reader applications from communicating with the outside world. If so, it is important to run thru the following RShell activities: 

#
Troubleshooting Steps
Details
34

Make sure dns is setup properly

 

When switching to Static IP it has been brought up that on-reader applications cannot reach remote systems.

  1. Make sure your dns settings are correct.

    show network dns

  2. If not, add (and/or remove) the dns servers.

    config network dns add <ip of dns server>
    config network dns del <ip of dns server>

  3. reboot

  4. Another check is to see if the on-reader application can connect to the remote systems via IP Address.
35 Make sure ntp is setup properly

For NTP, it is important to understand that the time does not change immediately, and the rate of change is influenced by how big the time difference is between the current reader time and the timestamp provided by your NTP server; the bigger the difference, the more gradual the change. This is to limit any errors that might occur in the system by a rapid time change (log file timestamps, for example).

  1. Make sure your ntp settings are correct.

         show system summary

         show network ntp

a. Note: If the NTP Reach metric (NtpServerStatic1Reach) is zero then the reader has been unable to reach an NTP server at the IP address you have specified.

2. if not, add (and/or remove) the ntp servers.

          config network ntp disable

          config network ntp add <ip of ntp server>

          config network ntp del <ip of ntp server>

          config network ntp enable

3. reboot
36 Update your application to use 127.0.0.1 instead of “localhost”

It is a good idea to set the ip address to 127.0.0.1 instead of localhost in case localhost resolves to another system on the network.

 

Cannot obtain DHCP-assigned IP address

If you connect R700 to the network where DHCP is enabled and cannot obtain a DHCP-assigned IP address, please try the following:

# Troubleshooting Steps Details
43 Check if there is a midspan PoE injector which supports only 100Mbps on the network

If you find the midspan PoE injector which supports only 100Mbps on your network, please try either of the following:

1. Configure your network to use 100Mbps.

2. Use a gigabit capable PoE injector.


Some less frequent issues:

1) Routing table issue
2) ARP cache is corrupt
3) Most modern PCs have an auto-crossover network card so that you can connect directly between your PC and the reader/gateway. However, if using an older PC or have tried everything else, you should try either connecting through a switch, hub or router or else use an Ethernet cross-over cable.
4) DNS server cache not updated issue. 

5) Perform a Windows Update.  We had a case where the OS wasn't on the latest updates.  Once the updates had taken place, ItemTest was able to start and connect to the Impinj R700 Reader

Was this article helpful?
4 out of 4 found this helpful

Comments

0 comments

Article is closed for comments.

Articles in this section

See more