RFID Reader Configuration

The CloudBox supports several compatible RFID readers, allowing for flexible deployment across a variety of timing scenarios. Whether you're timing dense race starts with hundreds of participants or monitoring sparse checkpoints, selecting the right RFID reader is crucial for ensuring accurate and reliable performance.

In this article, we'll dive deeper into the differences between the compatible RFID readers and their ideal applications. We’ll also discuss configuration requirements, status notifications, and best practices for ensuring proper connectivity and performance.

Reader Configuration Requirements

For the CloudBox to communicate properly with a connected RFID reader, the following settings must be in place:

• IP Address: The RFID reader must be set to a fixed IP address of 10.0.0.2. This is necessary to maintain reliable communication between the CloudBox and the reader.

• Port: The port used for communication can vary depending on the reader model. This setting is configurable within the CloudBox Configuration Interface.

Compatible RFID Readers (Firmware Version 1.0.16)

As of firmware version 1.0.16, the following RFID readers are compatible with the CloudBox:

1. Zebra FX9600 w/APP (via One4All app)

   • This model works with a dedicated application (One4All app) and offers high performance for dense timing points. It is ideal for events with high participant volumes, such as marathons and triathlons.

2. Zebra FX9600 (via LLRP)

   • This version operates via LLRP (Low-Level Reader Protocol) and is also highly recommended for high-density race events. Its robust design and high read rate make it ideal for start and finish lines with large groups of participants.

3. Zebra FX9500 (via LLRP)

   • The FX9500 is an older model but still reliable for medium-density timing points. It is suitable for checkpoint readings where there is moderate tag density.

4. Impinj R220 (via LLRP)

   • The Impinj R220 is recommended for low-density applications, such as individual checkpoints or smaller events. This reader is efficient but limited in terms of the number of tags it can handle simultaneously as it only has 2 antenna ports.

5. Impinj R420 (via LLRP)

   • The R420 is a more powerful version of the R220, suited for medium to high-density applications. It provides a balance between performance and cost and can handle larger numbers of participants than the R220 because it has 4 antenna ports.

6. Chainway UR4

   • The Chainway UR4 is a versatile and budget-friendly option for low- to medium-density race checkpoints. It offers reliable performance for events that do not require ultra-high tag read rates.

Reader Status Notifications

The CloudBox continuously monitors the status of the connected RFID reader and will provide real-time feedback through the user interface and notifications sent to connected clients.

1. RFID Reader Not Found:

   • This status indicates that the reader is either not configured or not present. The CloudBox will attempt to connect to the reader every 10 seconds.

   • The Start LED on the CloudBox will blink every 250 ms continuously, and a notification will be sent to all connected web clients.

2. RFID Reader Present:

   • Once the reader is correctly configured and detected, the CloudBox will enter standby mode, checking the reader's status every 60 seconds to ensure it remains connected.

   • The system will notify connected clients that the reader is present and ready for use.

3. RFID Reader Connection Lost:

   • If the reader was previously connected but loses connection, the CloudBox will display this status. It will attempt to reconnect every 10 seconds.

   • The Start LED will blink every 250 ms continuously, and a notification will be sent to connected clients informing them of the connection loss.

Choosing the Right RFID Reader for Your CloudBox

Depending on the specific needs of your event, different RFID readers will be more or less suitable. Here are some recommendations based on timing point density:

1. High-Density Timing Points (Start and Finish Lines for Large Events):

   • Recommended readers:

     • Zebra FX9600 (w/APP or LLRP)

     • Impinj R420

   • These readers offer high read rates and can handle large numbers of tags in quick succession, ensuring accurate detection at busy start or finish lines.

2. Medium-Density Timing Points (Checkpoint Events or Mid-Sized Races):

   • Recommended readers:

     • Zebra FX9500

     • Impinj R420

     • Chainway UR4

   • These readers offer a balance of performance and affordability for events with moderate participant volumes.

3. Low-Density Timing Points (Individual Checkpoints or Smaller Races):

   • Recommended readers:

     • Impinj R220

     • Chainway UR4

   • For less dense timing points, these readers are effective and cost-efficient, handling fewer tags without sacrificing accuracy.

Power and Connectivity Considerations

1. Power Requirements:

   • Ensure that the RFID reader is receiving the correct power supply, as provided by the CloudBox. The CloudBox’s built-in power connectors are designed to work seamlessly with the RFID readers listed above.

2. Ethernet and Power Connections:

   • The CloudBox is equipped with two connection cables for the reader:

     • Ethernet Cable: Used for transmitting data between the CloudBox and the reader.

     • Power Cable: Used for powering the RFID reader. Ensure that both connections are properly secured for reliable operation.

Summary

Configuring an RFID reader with the CloudBox requires setting a fixed IP address and selecting the appropriate reader model based on the event's timing requirements. Whether you're managing a high-volume race start or a low-density checkpoint, the right RFID reader will ensure that your timing data is accurate and reliable.

Always monitor the Reader Status through the CloudBox interface and ensure that both the Ethernet and power connections are properly configured. By following these guidelines, you can ensure a smooth and efficient race timing experience.