Prerequisites

Before you being, ensure that port 80 and port 5000 are open to the device on your network. Port 80 will need to be open to access the web interface which will allow you to install the embedded application. The embedded application will communicate with the EOS tool on port 5000.

Installing the Embedded App

Navigate to the reader's web interface by typing the IP address of the reader in your web browser (i.e. http://<reader_ip>). Once you hit the reader's web page, you should see a login prompt asking you to enter in a username and password. The default credentials are as follows:

Username: root

Password: impinj

Once you are properly authorized, you should see the following page. Installing the embedded app is the same process as upgrading the firmware. Under the reader upgrade section, click on the browse button next to "Select Upgrade File". Navigate to the firmware file to upload found in EOS/Embedded/Speedway/v5/EOS.upg.

Once uploaded, please wait until the reader has installed the application and returns the message "Ready to Reboot" next to the reader status. Once the device is ready to restart, click on the "Reboot" button in the Reboot section and wait for the device to come back online. Once the embedded app has been successfully installed, the "LLRP Status" in the Reader section should say "Connected".

Configuring the Embedded App

The included ZIP comes with an EOS tool to configure the embedded app by sending appropriate JSON commands to the reader. The app is located under "EOS Tool/EOSTool.exe". Run the app, then specify the IP address of the reader and click connect. Once you successfully connect, you will see a command listing in the very left hand pane. Once you click on a command, you will see two other panes: in the middle you'll see the request pane containing the JSON payload of the selected command to send to the reader and to the right you'll see the notifications pane which shows the response of the command once executed along with any subscribed notifications sent by the embedded application.

Installing the License

Once the app is initially installed, first you will have to set the license before you can send any other commands to configure the device. In the included package, you should see a license JSON file containing the appropriate license to send to the reader located at the root of the package. In the command pane, you should see a command called "UpdateLicense". Click on that command which will open up the request JSON in the middle pane. Open up the license file in your text editor and copy the license value string. Go back to the EOS tool then paste the license value string into the middle pane so the update license request looks like:

{

"UpdateLicense": {

"License": "ABC...XYZ"

}

}

Once the license is defined in the request pane, click on the execute button to send the command to the reader. If successful, you should see an appropriate response in the right hand response pane.

Updating the Configuration

In the command listing, click on the UpdateConfiguration command. This will open up the reader configuration JSON in which you can update how the embedded app configures how to get and send reads. The included package comes with a sample UpdateConfiguration.json file which has a configuration that will work with SAM. It is configured to have the device send HTTP notifications to the server with the TagReads with a five second period. Open the UpdateConfiguration.json file in your text editor and copy the JSON into the request pane, then hit execute to update the device with the appropriate configuration.

Testing Tag Reads

Once you have the device configured, you will then need to start the reads by clicking on and executing the "StartReading" command and clicking submit. Only after you run this command will the antennas be active. To ensure the reader is picking up tag reads, you can subscribe to the tag read notifications by running the "SubscribeTagReads" command. This will have the embedded app send the tag read notifications to the EOS tool as well which will show the tag reads in the right hand response pane when they are read in accordance with the UpdateConfiguration settings.

If you are successfully seeing tag read notifications and the HTTP notifications are configured in the UpdateConfiguration as noted in "Updating the Configuration", then these same notifications should also be sent to the SAM server for processing. If the RFID reader in SAM is properly setup with the pertinent Serial Number, then you should be seeing the tag reads in the RFID Log for the project in which the RFID reader is defined.