Capturing Debug Data

From time to time, your friendly Impinj support personnel may require more information than you are able to provide us in order to resolve whatever issue may be occurring. When this happens, we will ask you to make an RDD file and an FDD file, which are our Reader Debug Data files. The process below will walk you through three ways of obtaining these files.
Items required to perform these functions are:

  • A network connected Impinj Speedway reader
  • A network connected PC running ItemTest for Speedway

IMPORTANT NOTE:  The process of collecting these files results in a lot of data.  Both files will become quite large very quickly.  To minimize the file size, please only turn on the reader ("Start Inventory") for 10-15 seconds. We would also recommend keeping the capture window small, as to keep the file size reasonable.

Method 1 – ItemTest v2.0+ controlling reader

Step 1.
Start ItemTest and connect to the reader whose debug data you wish to capture. Once connected, click the reader's name from the left sidebar, under the section 'Data Sources', then choose the 'Diagnostics' tab, as shown below:

mceclip0.png


Step 2a.
In the Destination field in the Diagnostics tab, click the BROWSE button to select the folder
where ItemTest will store the capture data.

Note: ItemTest will create a master folder above the one you select, and the name of the containing
folder will be the device's hostname

Step 2b.
In the Prefix box, enter a string of text to prepend to the filenames created by ItemTest.

Note: Filenames after the prefix will be in the format MM-DD-YYYY_HHh-MMm-SSs.fdd for FPGA
debug data (FDD) and the same format with ‘.rdd’ as the filename extension for reader
diagnostic data (RDD)

Step 2c.

In Capture window, enter a numeric value for how long you want RDD and FDD logs to be
captured from the device.

Note: Specifies the duration in minutes you want to capture diagnostic data. For example, if 10
minutes is specified, then only the last 10 minutes of RDD capture will be saved; everything
before 10 minutes will be discarded.

Step 3:
On the Diagnostics tab, click the Start button to begin capturing and saving the diagnostic
streams

Step 4:
Start your application by selecting the Inventory type you are trying to perform from the left sidebar under 'Showcases', and then clicking the start button in the top header:

mceclip2.png

 

Step 5:

After capturing the event/issue, you will need to stop the inventory, and then stop the RDD collection from the reader's 'Diagnostic' tab. The RDD/FDD files will be stored in the file location you specified in earlier steps.

 

Method 2 – ItemTest v1.14.0 Controlling the Reader 

Step 1a.

Start ItemTest and connect to the reader whose debug data you wish to capture. Once connected, click the ‘Reader Settings’ tab and click ‘Configure’ next to the reader you would like to collect data from.

 

Step 1b.

In the new window that opens, select the ‘Utilities’ tab, and you should see a section labeled for ‘RDD Capture’. This section will have two fields, ‘RDD file name’ and ‘Capture Window’. The capture window will determine the amount of the data that the RDD and FDD files will contain, the default is set to one minute’s worth of data.

Step 1c.

Click the “Start RDD” button and the reader will begin to capture data. Once it has been started, you will need to start an inventory run using ItemTest by clicking the "Start" button on the main ItemTest window. You can see the RDD capture is active via a status message in the bottom right corner. You would then stop the inventory run after 10 seconds, or until you see the issue occur.

 


 

 
Step 2:

You will now want to stop collecting the data. To do this, you can either click the ‘Stop RDD’ button in the Utilities tab of the Reader Configuration (where you started the RDD capture), or by clicking the ‘Stop all RDD’ button on the main ItemTest window (this will only appear when RDD capture is running).




Method 3 – Other Application Controlling the Reader 

Step 1a.

Start ItemTest and connect to the reader whose debug data you wish to capture. Once connected, click the ‘Reader Settings’ tab and click ‘Configure’ next to the reader you would like to collect data from.

 

Step 1b.

Click on the ‘Utilities’ tab, and you will see a section for ‘RDD Capture’

 

Step 2:

Click ‘Start RDD’ to start the capture.

Step 3:

You will then want to start your application, outside of ItemTest. For example, you could run one of the SDK examples or your own application such as the one shown below:

Step 4:

After collecting debug data for 10 seconds, or up to seeing the issue occur, you will want to stop the RDD capture by clicking either the “Stop all RDD” button on the main ItemTest window, or from the ‘Stop RDD’ button in the same window as where you started the capture.

 

 

Once either of the three methods described here has been performed, send the .rdd and .fdd file to your Impinj Support professional for analysis. The .rdd and .fdd files will be saved under the 'rdd' folder of the ItemTest program directory.

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

Comments

0 comments

Article is closed for comments.