UHF Gen 2 RFID Speedway Reader (IPJ-R1000) Octane 3.0 User Guide 950110126000000469 Firmware Release: Octane 3.0, Doc Rev 1.5 10-08 www.impinj.com Copyright © 2008, Impinj, Inc. Impinj, Speedway, Octane, and GrandPrix are either registered trademarks or trademarks of Impinj, Inc.
Octane 3.0 User Guide Copyright © 2008, Impinj, Inc.
Octane 3.0 User Guide Overview The EPCglobal™-certified Speedway™ IPJ-R1000 reader is a stationary, UHF Gen 2 RFID tag reader that provides network connectivity between tag data and enterprise system software.
Octane 3.0 User Guide Federal Communications Commission (FCC) Compliance This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a commercial environment.
Octane 3.0 User Guide Industry Canada (IC) Compliance Operation is subject to the following two conditions: (1) this device may not cause interference and (2) this device must accept any interference, including interference that may cause undesired operation of the device. This device has been designed to operate with the antenna(s) listed in Section 2.6 that have a maximum gain of 6 dB. Antennas not included in this list or having a gain greater than 6 dB are strictly prohibited for use with this device.
Octane 3.0 User Guide iv Copyright © 2008, Impinj, Inc.
Octane 3.0 User Guide Table of Contents 1 Regions of Operation ......................................................................................................... 1 1.1 Operation in North America ......................................................................................... 1 1.2 Operation in Europe ...................................................................................................... 2 1.3 Operation in China ..................................................................
Octane 3.0 User Guide 6.3 Operation Screen—Filters .......................................................................................... 39 6.4 Inventory Filter Screen ............................................................................................... 40 6.5 Tag Access Screen ...................................................................................................... 42 7 Firmware Upgrade .............................................................................................
Octane 3.0 User Guide 8.5.4.5 config network ntp Command .......................................................................... 72 8.5.4.6 config network trace Command ........................................................................ 72 8.5.5 config rfid Command ............................................................................................. 73 8.5.5.1 config rfid resetstats Command ........................................................................ 73 8.5.5.
Octane 3.0 User Guide Appendix B Appendix C Appendix D Appendix E Command Line Editing in Rshell ............................................................... 129 Software Compatibility Matrix .................................................................. 130 .............................................................................. LLRP Basic Capabilities 131 LLRP Default Configuration .......................................................................
Octane 3.0 User Guide 1 Regions of Operation The Speedway reader has been designed to work in various regions with differing frequency requirements. This document covers operation in North America, Europe, China, and Taiwan. Important In each region, the reader is locked to only operate in the specific frequencies listed in the respective frequency plan tables (Table 1-1 through Table 1-6). 1.
Octane 3.0 User Guide 1.2 Operation in Europe For European operation, the Speedway reader supports the frequency plan listed in Table 1-2 and operates under EN 302-208 using listen-before-talk (LBT). An optional setting allows use of a third-party controller for deployment where readers share channels. Consult the manufacturer of compatible controllers for details on how to setup and deploy. Table 1-2 Frequency Plan for Europe Transmit Channel Number Center Frequency (MHz) 4 865.7 7 866.3 10 866.
Octane 3.0 User Guide Table 1-3 Frequency Plan for China Transmit Channel Number Center Frequency (MHz) 10 922.375 11 922.625 12 922.875 13 923.125 14 923.375 15 923.675 16 923.875 17 924.125 18 924.375 Table 1-4 Default Frequency Plan for China Copyright © 2008, Impinj, Inc. Transmit Channel Number Center Frequency (MHz) 3 920.625 7 921.625 11 922.625 15 923.
Octane 3.0 User Guide 1.4 Operation in Taiwan The Speedway reader supports the frequency plan listed in Table 1-6 for operation in Taiwan. The NCC stipulates frequency hopping across the Taiwanese spectrum allocated to UHF RFID (922928 MHz, with hopping occurring between 922.25–927.75 MHz in 500 KHz steps). Table 1-5 Frequency Plan for Taiwan Transmit Channel Number Center Frequency (MHz) 1 922.25 2 922.75 . . . . . . 11 927.25 12 927.75 1.
Octane 3.0 User Guide 2 Setting Up the Speedway Reader The Speedway reader unit requires a power supply module with 24 VDC output. Ensure that power supply module has one of the following part numbers: For regions other than Japan, CUI, Inc., ETS240250U-P11P-DB-IM (power brick) with one of the following power cords: AC1 for North America AC2 for European Union AC4-1 for China For any region, including Japan, CUI, Inc.
Octane 3.0 User Guide 2.2 System and Equipment Requirements Table 2-1 summarizes the supported operating environments. Table 2-1 Operating Environments Interface Protocol Recommended Tools Microsoft® Windows Linux Mac/Other Compatible with common browsers Microsoft® Internet Explorer® (6+) and Mozilla® Firefox® (1.5+)a Web Interface HTTP Remote Login SSH/Telnet Putty SSH or Telnet Terminal Serial RS-232 Hyperterminal Minicom N/A a.
Octane 3.0 User Guide 2.3 Speedway Reader I/O Ports & Status Refer to Figure 2-1 for the location of the Speedway reader's major ports, connectors, and status indicators, which are clearly indicated on the unit. The Speedway reader is equipped with the following ports: • RJ-45 Ethernet port (labeled 10/100 BASE-T) • Female DB-9 connector for serial communication (SERIAL) • Female DB-25 connector with user I/O capability (GPIO) The GPIO contains: RS-232 serial interface, four 3.
Octane 3.0 User Guide Table 2-2 DB-25 Connector Pin-Out (continued) Caution Pin I/O Pin I/O Pin I/O 5 RS-232 RTS 14 GPOUT0 23 GPOUT7 6 No connect 15 GPOUT1 24 No connect 7 Signal Ground 16 GPOUT2 25 No connect 8 No connect 17 GPOUT3 9 No connect 18 GPOUT4 Pins listed in Table 2-2 as “No connect” must be left unconnected.
Octane 3.0 User Guide Figure 2-2 DB-25 Female Connector The labeled LEDs indicate Power, Status, and antenna activity. The LEDs that correspond to the connected antenna(s) (labeled 1, 2, 3, and 4), only light green when active (transmitting). A description of the status LED states appears in Table 2-4.
Octane 3.0 User Guide 2.4 Mounting the Speedway Reader When securing the unit with #10 screws via the four mounting holes, the Speedway reader may be mounted horizontally or vertically on a stable surface where it will be safe from disturbance. Keep the unit away from direct sunlight, high humidity, extreme temperatures, vibration, and sources of electromagnetic interference, as any combination of these conditions may degrade performance or shorten the life of the unit. 2.
Octane 3.0 User Guide • Cushcraft model number S9028PCL/R (left- or right-hand CP), with integrated 8 foot pigtail to RP-TNC male connector; 6 dBi composite gain • Impinj model number IPJ-A0301-USA (Mini-Guardrail) with SMA female connector; -15 dBi gain • Impinj model number IPJ-A0310-USA (Threshold-T Antenna) with 12 inch integrated pigtail to BNC male connector, 6 dBi composite gain.
Octane 3.0 User Guide • Cushcraft Model Number S8658PCL/R (left- or right-hand CP) with integrated pigtail to RPTNC male connector; 3.85 dBd gain • Impinj Model Number IPJ-A0400-EU1, CSL CS-777-1 (Brickyard) with 7 foot integrated pigtail to RP-TNC male connector; 0 dBd composite gain • MTI MT-242032/NLH (left-hand CP) or MT-242032/NRH (right-hand CP) with N-type female connector (antennas available in IP54 or IP67 ratings); 1.85 dBd gain • Sensormatic Electronics Corp.
Octane 3.0 User Guide 3 Connecting to the Speedway Reader There are four ways of communicating with the Speedway reader: the Web-based interface, the command line interface (or “rshell”), the Mach1 interface, and the LLRP interface. The Web-based interface is a means of configuring the reader, obtaining status, and demonstrating RFID operation. The command line interface is an alternate way to configure the reader and obtain status if not using the Web interface.
Octane 3.0 User Guide 3.1.2 Hardware Connections Connect the reader to your network via the Ethernet port (see Figure 3-1). E th e rn e t PC E th e rn e t Figure 3-1 Ethernet Connectivity 3.1.3 Zero-configuration Networking Option The Speedway reader supports zero-configuration networking. Zero-configuration networking is a term used to indicate devices that have included software in their design to enable automatic discovery of other devices on IP networks.
Octane 3.0 User Guide Selecting this icon will bring up a menu along the left side of the browser with all discovered devices. See Figure 3-3. Speedway readers will be identified by a hostname of the word “Speedway” concatenated with the last three bytes of the unit’s MAC address (printed on the Speedway reader enclosure and expressed in hexadecimal, e.g., MAC 00:16:25:00:02:2E, see Section 2.1), separated by “-” (e.g., Speedway-00-02-2E).
Octane 3.0 User Guide : Figure 3-4 Firefox Browser URL 3.2 Preparing Serial Connectivity Serial communication with the reader can be used to configure the reader. The serial interface may be necessary to establish initial communications with the Speedway reader (via the command line interface) if your network equipment is not compatible with the default network configuration of the reader (DHCP).
Octane 3.0 User Guide Figure 3-5 Serial Port Configuration 3.3 Manual Network Setup After establishing serial connectivity and logging in (see Section 3.2), the network may be configured for the Speedway reader using the Rshell command line interface (see Section 8 for detailed information). 3.3.1 Essential Configuration Commands Shown here are the essential configuration commands; for complete information on how to configure this interface, see Section 8.5.4 and Section 8.6.5.
Octane 3.
Octane 3.0 User Guide 4 Speedway Reader Web Interface—Status Navigate to the Speedway reader's Status landing Web page (see Figure 4-1) by selecting the Status link from the navigation bar at the top left of the Web interface screen. This page of the Web interface provides network statistics and logging information through menu selections on the left side of the page. Figure 4-1 Reader Status Landing Page 4.
Octane 3.0 User Guide • Bootloader (BIOS) version—current version of the boot loader used to start the reader from reset 4.
Octane 3.0 User Guide By selecting the Advanced link under the Network Statistics menu, much more detailed information may be displayed, including IP, TCP, UDP, and ICMP statistics. For complete descriptions of each parameter, see reference MIB-2 RFC 1213 (see Section 10). 4.3 RFID Status Page Selecting “RFID Statistics” under the Status menu will bring up a window (see Figure 4-3) that displays the RFID statistics.
Octane 3.0 User Guide GPI Statistics This section provides a tabulation of RFID statistics, using one column for each general purpose input (GPI) interface. 4.4 Logging Events Status Page The Logging Events Status page (see Figure 4-4) provides a listing of all events logged into the local syslog file. This page also displays the current level setting of the syslog logging severity.
Octane 3.0 User Guide 5 Speedway Reader Web Interface—Configuration Navigate to the Speedway reader's hosted Web page (see Section 3.1 for instructions on how to access the reader from your network). From the navigation bar at the top left of the screen, select Configuration. A page similar to that shown in Figure 5-1 should appear. This initial landing page provides network summary and system information.
Octane 3.0 User Guide System Information The Description, Contact, Name, and Location dialog boxes allow for entry of strings to further identify the reader. Note Quotes are not accepted as part of strings for System Information. Strings entered with quotes will be displayed with all quote marks stripped. 5.1 Network Configuration Selecting Network from the menu along the left side of the screen (see Figure 5-1) will bring up a screen as illustrated in Figure 5-2.
Octane 3.0 User Guide DNS Configuration • To add a static DNS server, enter an IP address into the box labeled “Add static server” and select “Apply.” • To add a static domain, enter a domain name into the box labeled “Static Domain” and select “Apply.” NTP Configuration • To add a static NTP server, enter an IP address or a hostname into the box labeled “Add static server” and select “Apply.” • Multiple NTP servers may be configured for time synchronization that is more reliable.
Octane 3.0 User Guide 5.2 RFID Configuration Selecting the RFID link under Configuration will bring up a window (see Figure 5-4) that displays a summary of the RFID application settings. Figure 5-4 RFID Configuration Page RFID Summary The administrative status of three types of RFID connections can be set through their respective checkboxes. Connection Status This section consists of two parts: The upper part of the screen displays the information of any active connection.
Octane 3.0 User Guide 5.2.1 Low Level Reader Protocol (LLRP) Configuration Selecting “LLRP” under Configuration/RFID will bring up a page that provides an interface to display and set the LLRP configurations, as shown in Figure 5-5. Figure 5-5 Low Level Reader Protocol Configuration Page LLRP Summary This section displays the LLRP protocol revision implemented by the reader, and the regulatory region within which the reader operates.
Octane 3.0 User Guide “Active.” Select the specification(s) to be downloaded via the column of checkboxes, labeled “Select.” Download the selected specifications as one XML file via the “Download” button. Use the “Refresh” button to obtain the latest information about the Reader Operation or Access specifications. Reader-initiated Connection Configuration This section displays a reader-initiated LLRP connection configuration.
Octane 3.0 User Guide 5.2.2 Mach1 Protocol Configuration Selecting “Mach1” under Configuration/RFID will bring up a window (see Figure 5-6) that displays the Mach1 protocol configuration. Figure 5-6 Mach1 Protocol Configuration The summary of Mach1 protocol configuration includes: • “Protocol Revision,” which is the Mach1 protocol revision implemented by the reader. • The administrative state of the connection, which is displayed on the “Service” row as either “Enabled” or “Disabled.
Octane 3.0 User Guide 5.3 SNMP Configuration Selecting the SNMP link under Configuration will bring up a window (see Figure 5-7) that allows each aspect of the SNMP feature to be set. Figure 5-7 SNMP Configuration Page 5.3.1 General SNMP Configuration The front page of the SNMP configuration menu provides interfaces for displaying and setting the generic SNMP configuration. SNMP Summary • • • • Use the checkbox labeled “SNMP Service” to globally enable or disable the SNMP feature.
Octane 3.0 User Guide Information about the currently active trap receivers, if any, is displayed under the heading “Trap Receivers.” Each trap receiver is characterized with “Host” (hostname or the IP address), the port number, and the community string for receiving traps. • Mark a trap receiver for deletion by selecting the “Delete” checkbox next to it. • To add a trap receiver, enter the host, port, and community information for the receiver into the respective dialog boxes on the row labeled “Add.
Octane 3.0 User Guide 5.4 Network Logging Selecting the Logging link under Configuration will bring up a window (see Figure 5-9) that allows each aspect of the internal logging to be set (in increasing order of severity) via pulldown menus. (Debug is the least severe level and Emergency is the most severe.) The internal log is only stored in the RAM file system and is capable of high-speed, real-time logging of internal events. The syslog setting may also be configured via this window.
Octane 3.0 User Guide Figure 5-10 Firmware Configuration Page Firmware Summary This section of the firmware upgrade Web page is a summary of the primary (currently running) and secondary (backup) system images (firmware versions). For details on the upgrade method, see Section 7). Upgrade Status The Upgrade Status section of the Firmware Upgrade Web page displays the status of an upgrade. If no upgrade is in progress, the status will be “Idle.
Octane 3.0 User Guide Firmware Upgrade Under the window labeled “Firmware Upgrade,” the name of a network-accessible local upgrade image file may be entered or located by browsing through the local file system. This file is uploaded to the reader for upgrade by clicking the “Apply” button. 5.5.1 Advanced Firmware Upgrade Selecting “Advanced” under Configuration | Firmware will bring up a window (see Figure 5-11) where upgrades using either the pull or push methods may be initiated.
Octane 3.0 User Guide Reboot The upgraded firmware image will not be activated unless the reboot command is issued by selecting the button labeled “Reboot” at the bottom of the page (see Figure 5-12). Figure 5-12 Advanced Firmware Configuration Page (scrolled down) Copyright © 2008, Impinj, Inc.
Octane 3.0 User Guide 6 Speedway Reader Web Interface—RFIDemo 6.1 Settings Navigate to the Speedway reader's RFID demonstration (RFIDemo) Web page. (Note that the actual Web interface appearance may vary from that shown in this User’s Guide.
Octane 3.
Octane 3.0 User Guide "A" or "B." Any time a tag is read, this flag is switched from A to B, or B to A. The Gen 2 protocol further requires that B-flagged tags automatically revert (decay) to A-flagged tags after a period of time that depends on the Gen 2 session being used. The Gen 2 sessions and associated decay times are shown in Table 6-2. Table 6-2 Session Definitions Session A -> B Energized1 A -> B Not Energized Application Characterization of the read zone.
Octane 3.0 User Guide Tags being read are displayed in white fields, which fade to blue after not being seen by the reader within the last ~10 seconds. To see all tags and their status, simply scroll the screen. As tags are read, their EPC numbers appear in the primary window of the Operation screen. If the Read TID button on the Operation screen has been enabled, the logo of the tag silicon manufacturer corresponding to the TID will also be displayed.
Octane 3.0 User Guide Act Once The Act Once button, if enabled, directs the reader to execute the action indicated in the Tag Access Action setting (read, write, lock, kill, etc.) only one time (see Section 6.5). If the operation is successful (see ‘Last Status’ column in the primary read window), the reader will continue the inventory or halt operation, depending on the status of the Auto Continue setting.
Octane 3.0 User Guide Mem Bank 00 (0): Reserved (cannot select filter on this bank) Mem Bank 01 (1): EPC Mem Bank 10 (2): TID Mem Bank 11 (3): User Successive Selects may apply to different memory banks. The Bit Offset and Bit Length fields are used to target a specific portion of the tag memory on which to perform the filtering, while the Pattern field contains the comparison bits of interest. Note that the Bit Length must be non-zero.
Octane 3.
Octane 3.0 User Guide The menu item Tag Access (see Figure 6-8) adds a Mask field to the filtering operation, which allows the user to mask individual "don't care" bits or segments of the matching pattern, where "1" identifies a bit of interest and "0" represents a masked bit. Tag Access differs from the Inventory Filter operations in several respects.
Octane 3.0 User Guide 7 Firmware Upgrade The Speedway reader provides methods for managing the firmware image that include: • Upgrade to a new image • Fallback to a previous valid image • Restore to factory default settings These operations can be performed without disturbing the current operation of the reader. The user may manage the upgrade process through the steps described in this section.
Octane 3.0 User Guide The three partitions in each image are: • Partition 0, the System OS Partition (SOP). This partition contains the Linux OS image, file system, and Impinj reader application. • Partition 1, the System Configuration Partition (SCP). This partition contains the Impinj reader application configuration and other general configuration data. • Partition 2, the Custom Application Partition (CAP). This partition may contain a custom application.
Octane 3.0 User Guide reboots), it will find that no upgrade is needed because in the absence of any change in the metafile on the server, the image version the reader is running is the same as that specified in the metafile. 7.2 Preparing the Upgrade Image The path and permission of the image file on the server should be set properly to allow file retrieval via the method as specified by the upgrade-file-uri field of the metafile or by the image URI. 7.
Octane 3.0 User Guide Table 7-1 Upgrade Configuration Definition (continued) Field Name Field Value Argument Parameter Value Description This field indicates how the image should be activated. immediate The image should be activated immediately after the upgrade is complete, causing an immediate reboot after programming is complete. wait-4-cmd The image should be activated by a reboot command from the user.
Octane 3.0 User Guide Table 7-1 Upgrade Configuration Definition (continued) Field Name Field Value Argument Parameter Value Description dl-retryperiod Time to wait (seconds) before retrying a download. upgradefile This field is used as a delimiter. It means all data fields after this one, up to the next delimiter or end of metafile apply to the upgrade file indexed by the number in the field value .
Octane 3.0 User Guide • The user can invoke the Rshell command config image metafile to instruct the reader to enter pull mode, download a metafile from the specified URI, and perform an upgrade based on the metafile. Regardless of the upgrade status, the reader remembers the URI for future use. See Section 8.5.2.3 for details. • The user can invoke the Rshell command config image retrievemode to manually set the retrieve mode of the reader.
Octane 3.0 User Guide > > config image upgrade ftp:// username:password@server1.mydomain.com/binaries/sop-2_4_0.upg Status=0,'Success' # command accepted > > show image summary # Query status Status=0,'Success' UpgradeStatus=Downloading # Reader determines upgrade is needed and starts download # Current image info primaryImageType=2 primaryImageSystemVersion='2.4.0.144' primaryImageConfigVersion='255.255.255.255' secondaryImageType=2 secondaryImageSystemVersion='2.4.0.128' secondaryImageConfigVersion='255.
Octane 3.0 User Guide # when status LED comes back on as solid green, the reader will be running from # the new image 7.7 Metafile Example Below is an example of a complete metafile (note that the metafile may contain comment lines that start with a pound sign #): ## This is an example upgrade config metafile.
Octane 3.0 User Guide ftp://user:password@ftpserver.mydomain.com/speedway/images/image-sop-scp-cap-2.1.1.upg As with any remote file retrieval, the servers should be properly configured such that the files are accessible either anonymously or by the specified user from the client (the reader). 7.9 Detailed Upgrade Behavior 7.9.
Octane 3.0 User Guide In the forced upgrade mode, an upgrade will happen as long as at least one partition in the upgrade file has a different version from the primary image. If the config image upgrade command is used, the upgrade is always performed regardless of version numbers or image type. 7.9.4 Partition copy-over The upgrade image file does not necessarily contain all the partitions.
Octane 3.0 User Guide 7.9.6 Scheduled reboot time As shown in Table 7-1, when commit-mode is set to scheduled , a reboot time must be specified using either the time or wctime parameters. There are two formats in specifying time, the fullyspecified format: .yyyy:mm:dd:hh:mm:ss and the wildcard format: .*.hh:mm:ss For readers with system image version (SOP partition) lower than 2.6.
Octane 3.0 User Guide 8 Rshell Command Line Interface The Speedway reader’s Rshell Command Line Interface (CLI) is accessed via serial, Telnet, or SSH connectivity. Important The CLI is meant to be a machine interface. As such, Impinj supports backward compatibility for this interface—no existing inputs will change, no existing outputs will change but new commands may be added or new optional arguments may be added to existing commands, always at the end. 8.
Octane 3.0 User Guide show - Submenu of elements that may have their configuration or status shown. - Submenu of transfer commands. transfer Menu navigation and the help keyword (or ?) can be combined on the same line to list all the commands available for that menu. For example: > show ? Commands: access exit help . ? - Show users and their access level. Exit this submenu and return to the parent menu. Displays this help message. Exit this submenu and return to the parent menu.
Octane 3.0 User Guide > show ? image metafile metafile - Command to display upgrade metafile info. Usage: image metafile 8.2 Response Format The first line of every response has the following format: Status=errorCode,’error string’ where errorCode is a numeric value and ‘error string’ is a single-quoted, human-readable error code. The error codes are defined in Table 8-1.
Octane 3.0 User Guide Table 8-1 Error Codes (Continued) Error Code Error String Description 9 Previous-Command-InProgress The command was rejected because a previous command is still in progress such that this one could not be processed 10 Command-Being-Processed The command cannot be finished right away; it is being processed.
Octane 3.0 User Guide > show network summary Status=0,'Success' ipAddressMode=dynamic ipAddress=10.0.10.155 ipMask=255.255.0.0 gatewayAddress=10.0.0.10 broadcastAddress=10.0.255.
Octane 3.0 User Guide 8.5.1 config access Command The config access command changes the password for a given access level. There are three levels of access: root, operator, and monitor. The root access level consists of only the root user. The root user is allowed all adminsitrative access and cannot be deleted. Only the root user may create other user accounts. The operator access level allows all administrative functions except for creating or altering user accounts (i.e., a read and write user).
Octane 3.0 User Guide Table 8-4 "config access" Command Parameters Argument Options Format Root N/A Factory established and may not be deleted. Selectable String one to eight alphanumeric characters N/A Root level is factory established and may not be deleted. Root has all administrative authority and is the only level that may create other user accounts.
Octane 3.0 User Guide 8.5.2 config image Command The config image commands provide configuration options for image and upgrade configurations. It contains direct subcommands only, no sub-menus. These commands will not take effect until the reader is rebooted. Detailed explanation of how to upgrade images is given in Section 7. 8.5.2.
Octane 3.0 User Guide upgrade is successful, how the new image is activated depends on the commit-mode specified in the metafile (see Table 7-1). If the reader is in pull mode during the execution of this command, it is possible that the reader is currently retrieving the metafile or performing an upgrade. In these instances, this command may return “Previous-Command-In-Progress.” 8.5.2.
Octane 3.0 User Guide If the upgrade is successful, the new image is not activated until the user reboots the system. If the reader is in pull mode during the execution of this command, it is possible that the reader is currently retrieving the metafile or performing an upgrade. In these instances, this command may return “Previous-Command-In-Progress.
Octane 3.0 User Guide Internal log Logging Data Logging Data Syslog emergency alert critical error warning notice info debug emergency alert critical error warning notice info debug Internal log Syslog emergency alert critical error warning notice info debug emergency alert critical error warning notice info debug Severity Levels Figure 8-1 Relative Severity Level Logging Transfer 8.5.3.
Octane 3.0 User Guide Table 8-6 "config logging internallog set" Command Parameters Argument Option Format Emergency | Alert | Critical | Error | Warning | Notice | Info | Debug level String Description Configures the level at and above which logs are sent to the log database. Listed in decreasing order of severity.
Octane 3.0 User Guide Table 8-7 "config logging syslog" Command Parameters (Continued) Command Argument Format Emergency | Alert | Critical | Error | Warning | Notice | Info | Debug level Description Set the syslog security level. Only logs at or greater in severity than this level will be forwarded to syslog. Levels listed in order of decreasing severity. String Removes all archived syslog messages. reset Sample commands are shown below: > config logging syslog add 10.0.10.
Octane 3.0 User Guide Table 8-8 "config network domain" Command Parameters (Continued) Command hostname lla mdns Argument host-name enable | disable enable | disable Format Description String Configures the current hostname for the reader. Parameters returned from DHCP will override this value. String Enable/disable the link local address protocol. With LLA enabled, the reader will automatically choose an IP address in the linklocal image range (169.254.*.
Octane 3.0 User Guide 8.5.4.1 config network dhcp Command The config network dhcp command allows the user to modify the DHCP client configuration. Command parameters are shown in Table 8-9. Table 8-9 "config network dhcp" Command Parameters Command Argument Sendhostname on | off Userclass Format Description String Turn the “send hostname” on/off in the DHCP client configuration String Sets the value for the “send userclass” option of the DHCP client configuration.
Octane 3.0 User Guide 8.5.4.3 config network dnssd Command The config network dnssd enables or disables service discovery of the HTTP (Web), RFID (Impinj proprietary), and LLRP (low level reader protocol) services. When service discovery is enabled on the reader, another device on the network with DNS-Service-Discovery (DNS-SD) capability can automatically discover the reader.
Octane 3.0 User Guide 8.5.4.4 config network ip Command The config network ip command allows the user to statically configure IP settings, or configure the reader to use DHCP. Command parameters are shown in Table 8-12: Table 8-12 "config network ip" Command Parameters Command Argument Format Configures the network for dynamic address resolution using the DHCP protocol. dynamic static Description IpAddress Configure the network for static address resolution.
Octane 3.0 User Guide hostname=speedwayc11 > 8.5.4.5 config network ntp Command The config network ntp command allows the user to statically configure NTP servers. These servers are in addition to any provisioned through DHCP.
Octane 3.
Octane 3.0 User Guide 8.5.5.2 config rfid llrp Command The config rfid llrp command enables the user to configure the LLRP implementation. This menu provides the following subcommands: Table 8-15 “config rfid llrp” Command Parameters Command Description connclose Supports manual closing of the current LLRP connection factory Resets the LLRP configuration to its factory defaults. This action resets only in-band configuration, not configuration items controlled by rshell or the Web interface.
Octane 3.0 User Guide 8.5.5.2.2 config rfid llrp outbound Command The config rfid llrp outbound command leads to a submenu of reader-initated connection configuration commands, as shown in Table 8-17. Table 8-17 “config rfid llrp outbound” Command Parameters Command add Argument hostname | <:port> Format String | Integer Description Add a new host to which the reader will attempt reader-initiated LLRP connections. This host is mandatory, but the port number is optional.
Octane 3.0 User Guide Table 8-17 “config rfid llrp outbound” Command Parameters (Continued) Command retry service timeout 76 Argument seconds enable | disable seconds Format Description Integer Configure the frequency in seconds at which reader-initiated connections are attempted. This number represents the minimum time between a failed connection attempt and the next connection attempt by the reader.
Octane 3.0 User Guide 8.5.5.3 config rfid mach1 Command The config rfid mach1 command leads to a submenu of client-initated connection configuration commands, as shown in Table 8-18 Table 8-18 “config rfid mach1” Command Parameters Command Argument enable | disable service Format Description Enable or disable client-initiated Mach1 connections to the reader. Disabling this service will cause an active client-initiated connection to be terminated and all future connection attempts to be refused.
Octane 3.0 User Guide 8.5.6.1 config snmp access Command The config snmp access command supports setting of SNMP access configuration. The command parameters are shown in Table 8-20.
Octane 3.0 User Guide 8.5.6.3 config snmp trap Command The config snmp trap command supports setting of SNMP write capability. The command parameters are shown in Table 8-22.
Octane 3.0 User Guide Table 8-23 "config snmp trap receiver" Command Parameters (Continued) Command Argument Format host: IP address or hostname host | [port | community] del port: Integer community: String delall None Description Delete a trap receiver. port and community are optional parameters. When they are present, the trap receiver(s) with the specified port and/or community are deleted. When they are absent, the trap receiver matching host is deleted regardless of port and community.
Octane 3.0 User Guide Status=0,'success' 8.5.6.4 config snmp epcg Command The config snmp epcg command supports the setting of objects in the EPCglobal RM MIB. There are no direct subcommands and only one submenu, device, for this command. 8.5.6.4.1 config snmp epcg device Command This submenu permits configuration of the snmp egcg device role. The command parameters are shown in Section 8-25.
Octane 3.0 User Guide Table 8-26 “config system” Command Parameters (Continued) Command Important Format Description name String Configure the system name. Any ASCII characters are allowed, except for single and double quotes; double and single quotes may only be used as leading and tailing characters if the string has white space time MMDDhhmmCCYY MM.DD-hh:mm:ss CCYY.MM.DD-hh:mm:ss CCYY.MM.DD-hh:mm hh:mm:ss hh:mm Configure the system time.
Octane 3.0 User Guide 8.6 Show Command The show command has seven submenus, as shown in Table 8-27, and described in the succeeding sections. Table 8-27 “show” Command Parameters Command Description access displays a list of the configured user accounts showing the account name and the access level (root, operator, or monitor) for each account. Also displayed are the name and access level of the current user.
Octane 3.0 User Guide are not displayed. The response of the command is the concatenation of all the static entries from the following four categories: network, system information, upgrade agent, and logging. Each category is preceded with a delimiter field. The entire collection of possible parameters is listed in Table 8-28. Note that some parameters are present only when set and applicable.
Octane 3.0 User Guide Table 8-28 "show all config" Response Parameters (Continued) Argument Format Description on | off Indicates if the “send hostname” option of DHCP client configuration is turned on userclass String Displays the user-class option of the DHCP client configuration. String is empty if this option is not set.
Octane 3.0 User Guide Table 8-28 "show all config" Response Parameters (Continued) Argument 86 Format Description LLRPOutboundServer String The server and port number for outbound LLRP connection. is the index.
Octane 3.0 User Guide Table 8-28 "show all config" Response Parameters (Continued) Argument Format Description epcgRmMibRevision String The EPCglobal Reader management MIB revision, e.g.
Octane 3.0 User Guide Table 8-28 "show all config" Response Parameters (Continued) Argument Format Description SysContact String The system contact SysName String The system name SysLocation String The system location SysTime String A time in UTC ConfigCategory UpgradeAgent Delimits the upgrade agent category MetafileUri String The URI of the upgrade metafile RetrieveMode pull | push The upgrade agent‘s metafile retrieve mode RetrievePeriod Integer The retrieve-period in minutes.
Octane 3.0 User Guide Table 8-28 "show all config" Response Parameters (Continued) Argument Format Description SeverityLevel Same as above The syslog logging severity level as set by the “config logging syslog level” command. This determines what will be passed from internal to syslog logs (see Section 8.5.3) SyslogServerAddress1 IP Address or hostname String The first syslog server as set by the “config logging syslog add” command.
Octane 3.
Octane 3.0 User Guide Table 8-29 "show image metafile" Response Parameters (Continued) Argument Format Description immediate | scheduled | wait-4-cmd The commit mode if metafile is currently available CommitTime String The schedule commit time, present only if commit mode is scheduled. Its format is , where time zone is the readers time which is gmt.
Octane 3.0 User Guide Table 8-30 "show image summary" Response Parameters Argument Format Description The upgrade status of the last executed upgrade UpgradeStatus 92 Idle | The reader is idle in terms of upgrade. Contacting Server Reader is contacting server for file download. Downloading File is being downloaded. Download Failed Failed to download either the metafile or the upgrade image. Bad Config The upgrade configuration metafile is invalid. Bad Image The image downloaded is invalid.
Octane 3.0 User Guide Table 8-30 "show image summary" Response Parameters (Continued) Argument Format UpgradeStatus, continued Failed Description Any other failures not covered above. Usually explained by Reason field This supplements the UpgradeStatus field to give a reason for the status Unknown Host Download failed because of an unknown host. Unsupported Scheme Download failed because of unsupported URI scheme (only FTP, HTTP and TFTP are supported). Syntax Error Metafile has a syntax error.
Octane 3.0 User Guide Table 8-30 "show image summary" Response Parameters (Continued) Argument Format Reason, continued 94 Description Missing SOP Metafile does not contain SOP partition while SCP is present. Duplicated Partition Upgrade failed because either the metafile or the upgrade file has a duplicated partition in it. Incompatible Upgrade/Downgrade Path Upgrade failed because upgrading/ downgrading to the intended SOP version or type is not allowed by current image.
Octane 3.0 User Guide Table 8-30 "show image summary" Response Parameters (Continued) Argument Format secondaryImageConfigVersion Description The version string of the secondary image configuration partition String 8.6.4 show logging Command The show logging command is used to display the logging parameters for the system and for displaying the log information in text form. The commands are described in Table 8-31. Log entries are reported from most recent to oldest.
Octane 3.0 User Guide An example show logging internallog command is shown below: > show logging internallog 1 Status=0,'Success' Event1=1156073965.
Octane 3.0 User Guide Status=0,'Success' Event3=Aug 20 11:39:25 (none) ntpd[625]: bind() fd 4, family 2, port 123, addr 10.0.10.231, in_classd=0 flags=1 fails: Address already in use Event2=Aug 20 11:39:26 (none) thttpd[631]: socket :: - Address family not supported by protocol Event1=Aug 20 11:39:54 (none) dhclient: receive_packet failed on ixp0: Network is down 8.6.5 show network Command The show network menu contains commands to display networking parameters and statistics.
Octane 3.0 User Guide Table 8-35 "show network dhcp" Response Parameters Argument sendHostname UserClass Format Description on|off Indicates the current setting for sending the hostname during DHCP negotiation. String Displays the current setting for the user class DHCP option. If this string is empty, the user class option is not sent via DHCP. Otherwise the value indicates the string that is sent.
Octane 3.
Octane 3.
Octane 3.
Octane 3.
Octane 3.
Octane 3.0 User Guide Table 8-42 "show network ntp" Response Parameters (Continued) Argument Format Description NtpServer1DynReach Octal integer The reachability register of the first NTP server … … … NtpServerAddressDyn String Address of the last NTP server obtained from DHCP server a.
Octane 3.
Octane 3.0 User Guide Table 8-46 "show network trace" Response Parameters Argument Active Format String Description “Yes” or “No,” to indicate if a net trace is currently active. 8.6.6 show rfid Command The show rfid menu contains commands to display RFID parameters and statistics. Submenu commands are shown in Table 8-47. Table 8-47 “show rfid” Command Parameters Command Description stat Display RFID statistics for reader.
Octane 3.0 User Guide Table 8-48 “show rfid stat” Response Parameters (Continued) Argument AntennaOperationalStatus Format enabled | disabled | unknown Description Indicates if an antenna is physically connected to the reader and operating properly. If no RFID operation has been performed, and no in-band (Mach1 or LLRP) checks on antenna status have been performed, the reader will assign unknown to this statistic.
Octane 3.
Octane 3.0 User Guide 8.6.6.2 show rfid llrp Command The show rfid llrp command provides statistics on the llrp interface and has the subcommands listed in Figure 8-49. Table 8-49 “show rfid llrp” Command Parameters Command accessspec Argument id Format integer Description Displays a specific AccessSpec capabilities Displays the LLRP capabilities. config Displays the LLRP configuration.
Octane 3.0 User Guide 8.6.6.3 show rfid mach1 Command The show rfid mach1 command provides a submenu of Mach1 status commands as shown in Table 8-50. Table 8-50 “show rfid mach1” Command Parameters Command Description inbound Displays the Mach1 external client-initiated connection settings stat Displays the Mach1 statistics summary Displays a summary of the Mach1 information 8.6.
Octane 3.0 User Guide Table 8-52 "show snmp summary" Response Parameters (Continued) Argument Format Description WriteEnabled=true enabled | disabled Indicates whether SNMP write is enabled NonRFIDTrapEnabled true | false Indicates whether non RFID traps are enabled TrapReceiver String Trap receiver(s) currently configured. is an index starting from 0.
Octane 3.
Octane 3.
Octane 3.
Octane 3.0 User Guide Table 8-57 “show system summary” Response Parameters (Continued) Argument Format Description SysLocation String A system location—defaults to ‘unknown’ SysTime String A time in UTC 8.7 Transfer Command The transfer command has two subcommands, as shown in Table 8-58.
Octane 3.0 User Guide Table 8-59 “transfer status“ Command Response Argument TransferStatus Reason Format Description Unknown | Contacting Server | Transferring | Transfer Failed | Done> The status of the transfer. Unknown means there is no outstanding transfer command. Unknown Host | Access Denied | File Not Found | Timeout | Invalid URI Format | Invalid URI Format (username:password@host) Reason for failure of transfer.
Octane 3.0 User Guide 9 Troubleshooting This section comprises a set of guidelines to enable the user to troubleshoot and isolate common configuration problems that may occur when using Speedway readers. It provides a series of basic tests that will enable the reader to either correct a problem with the Speedway reader, or determine that the reader must be returned for factory repair. 9.1 Test Instrumentation & Software Requirements 9.1.1 Power/Cabling • 24V Power Adapter: CUI, Inc.
Octane 3.0 User Guide 9.2 Basic Test Setup Figure 9-1shows the basic reader test configuration. A serial connector enables connection from the DB9 port on the computer to the serial port on the reader. If your computer does not have a DB9 port, you can obtain a USB-to-serial adaptor, which is commonly available at office supply or computer stores. If you intend to operate the reader with DHCP configuration, it must be connected to a router. This configuration will provide a network address to the reader.
Octane 3.0 User Guide 9.3 Troubleshooting Flowcharts To simplify the troubleshooting process, this guide will focus on four major areas: • Reader power up • Reader network communication • Running reader applications, including the factory-installed Java applet • RF-related issues including tag communication, antenna problems, and sensitivity issues. 9.3.1 Reader Power Up The flow chart in Figure 9-2 shows the basic steps to verify that the reader powers up correctly.
Octane 3.0 User Guide 9.3.2 Reader Network/Test Configuration Section 9.3.2.1 through Section 9.3.2.4, and the flowchart in Figure 9-3 describe how to identify and reconfigure the reader network configuration. At the end of Section 9.3.2, you will have verified network connectivity and will have the reader’s current IP address. This address is required to run reader application programs. 9.3.2.1 Reader Serial Configuration to Monitor and Configure Reader 1.
Octane 3.0 User Guide 3. llaStatus should be enabled. (Enabling llaStatus provides an autonomous address mode if DHCP is not available.) • If llaStatus is not enabled, at the command line type: > config network lla enable • The reader will respond with: > Status=0,'Success' 4. Mdns must be enabled to use Bonjour (discussed later) for reader identification and communication • At the prompt, type: > config network mdns enable • The reader will respond with: Status=0,'Success' 5.
Octane 3.0 User Guide C o n n e c t S e ria l C a b le b e tw e e n R eader and C o m p u te r S e t u p T e rm in a l P ro g ra m o n C o m p u te r (S e c tio n 9 .3 .2 .1 ) L o g o n to R e a d e r. A t “> ” P ro m p t, Type: Show N e tw o rk S u m m a ry YES D e s ire d N e tw o rk C o n fig ? NO DHCP F ix e d IP R e c o n fig u re R e a d e r fo r F ix e d IP (S e c tio n 9 .3 .2 .3 ) R e c o n fig u re R e a d e r fo r D H C P (S e c tio n 9 .3 .2 .
Octane 3.0 User Guide 9.3.3 Using Apple Bonjour to Find and Connect to Networked Reader If the reader has been installed on a network, Bonjour can be used to find and connect to it. In order to use this application, the reader must have mdns and lla modes enabled (refer to Section 9.3.2.2). After installing the Bonjour for Windows application, open a web browser. The Bonjour Icon, , should appear on the toolbar.
Octane 3.0 User Guide 9.3.4.1 Running the Application After verifying that your computer has Java installed, open a Web browser (Microsoft Internet Explorer Version 7 is recommended) and enter the reader IP address (that you noted from Section 9.3.2.4) in the browser address window. The home page of the reader application should open on the computer. Follow the instructions in Section 3 and Section 5 to configure and operate the reader application. 9.3.4.
Octane 3.
Octane 3.0 User Guide 10 References Table 10-1 References Reference 126 Description MIB-2 RFC 1213 Management Information Base for Network Management of TCP/IP-based internets:MIB-II. K. McCloghrie, M. Rose. March 1991. RFC 3986 Uniform Resource Identifier (URI): Generic Syntax. T. Berners-Lee, R. Fielding, L. Masinter. January 2005. RM Standard v. 1.0.1 Reader Management Standard defines version 1.
Octane 3.0 User Guide Appendix A Impinj Factory Default Configuration Detailed below are the factory default configuration settings for the Speedway reader. Except for the username and password, all entries are shown when the “show all config” command is issued on a Speedway reader in its factory default configuration.
Octane 3.0 User Guide system name: 'speedway-nn-nn-nn' system Location: 'unknown' # same as default hostname Upgrade Agent Category MetafileUri: Empty RetrieveMode: push Logging Category ApplicationLevel: emergency ConfigurationLevel: emergency MgmtLevel: emergency NetworkLevel: emergency RFIDParameters Level : emergency RFIDSingulation Level: emergency RFIDAccess Level: emergency System Level: emergency syslog severityLevel: error static syslog server: none 128 Copyright © 2008, Impinj, Inc.
Octane 3.0 User Guide Appendix B Command Line Editing in Rshell Key Sequence Action Insert character at cursor position then move cursor right one. Printable char KEY_LEFT Control-B, \033[D Move cursor left one. Sticks at begin-of-line. KEY_RIGHT Control-F, \033[C Move cursor right one. Sticks at end-of-line. KEY_HOME Control-A, \033[1~ Move cursor to begin-of-line. KEY_END Control-E, \033[4~ Move cursor to end-of-line KEY_DELETE Control-D, \033[3~ Delete character at cursor position.
Octane 3.0 User Guide Appendix C Software Compatibility Matrix The table below provides compatibility information of the Speedway® reader firmware with MultiReader™ and Mach1™. If you do not see your Speedway reader firmware version below or have additional questions, please contact your sales representative. 130 Speedway Firmware Version Mach1 Version DLL Version MultiReader Version 1.4.6 2.0.4 2.0.4 2.1.4 2.0.2 2.2.0 3.0.1 2.4.4 2.2.4 2.4.0 3.2.0 3.2.4 2.4.X 2.6.0 3.4.0 4.1.X 2.6.
Octane 3.0 User Guide Appendix D LLRP Basic Capabilities The Table 11-1 shows the LLRP capabilities supported. Where relevant, these capabilities are reported via the LLRP GET_READER_CAPABILITIES_RESPONSE message.
Octane 3.0 User Guide Table 11-1 LLRP Basic Capabilities Feature 132 Capacity Notes Maximum InventoryFilters per InventorySpec 2 See footnote 1 Truncate flag support No Must be 0 Maximum number of AccessSpecs 64 Maximum number of OpSpecs per AccessSpec 8 ClientOpSpec support No Number of Gen 2 modes 5 Can set Tari No Buffer overflow warnings Yes Optional Can control events and reports upon reconnect Yes By default, HoldEventsAndReports is False.
Octane 3.0 User Guide Table 11-1 LLRP Basic Capabilities Feature Capacity Notes Can set Gen 2 session per antenna No See footnote 1 Can set estimate population and time in field per antenna No See footnote 1 Disconnected operation support Yes Reader will continue to execute ROSpecs and AccessSpecs when disconnected.
Octane 3.0 User Guide Appendix E LLRP Default Configuration The following shows the LLRP default values for Speedway firmware release 3.0. An LLRP factory default will reset the unit to these settings. The definitions below are instances of llrp.xsd, which is an abstract representation of the LLRP protocol available at http://www.sourceforge.net/ projects/llrp-toolkit/.
Octane 3.0 User Guide RO Reporting: The following is the default report data for LLRP tag reports.
Octane 3.
Copyright © 2008, Impinj, Inc. All rights reserved. Notices The information contained in this user guide is confidential and proprietary to Impinj, Inc.
