Webscorer with RFID Race Timing Systems Ultra

[Race Pros Sports]

Summary:  Even when using decimal encoded chips containing only the numbers 0-9, the RFID Ultra box needs to be set to Hexadecimal output to read correctly.   If you don't use the Hex output setting on the Ultra, Webscorer sees chip 782 as 1922, 783 as 1923, 760 as 1888, etc. I'm not sure this is an issue with Webscorer or the RFID Race Timing Systems Ultra firmware. Both are the latest versions, although the Ultra firmware hasn't been updated in years. 

Webscorer settings:

·        Chip Timing System: Ultra/Echo

·        RFID readers: 192.168.1.90 (main box IP; do not use the individual Impinj reader IP addresses of 192.168.1.190 & 192.168.1.191)

RFID Race Timing Systems Ultra Settings:

·        Main Menu/Other/Comms Protocol/LLRP

·        Main Menu/Other/Chip Output Type/Hexadecimal (even tough your chips are encoded using decimal format). Now the chips read correctly (e.g. 782 is read as such & not 1922).

I just thought others might like to know this if they are trying to use the Ultra with Webscorer.

The other option is to use the Ultra timing box as 2 individual Impinj 420 readers with a built-in switcher. In this instance you can leave the chip output type as  Main Menu/Other/Chip Output Type/decimal  in the Ultra. I've done this by using the IP addresses of these two readers in Webscorer/Any Reader with LLRP. The problem with this setup is the switcher is a bit slow, and you don't get any rewind data (logs from the timing box).

Is anyone out there using the Ultra successfully with Webscorer? If so, do you have any other tips and have you had similar experiences?

Cheers from Canada,

Lyndon

Race Pros Sports

[Vesa Suomalainen]

How have you configured Webscorer?  Are you testing chips without a start list, or are you try to map the chip ID to match bib numbers?  If the latter, which encoding did you select on Webscorer?

There are a handful of organizers using RFID Timing Ultra reader with Webscorer:

https://www.webscorer.com/readysetgo

https://www.webscorer.com/109055

https://www.webscorer.com/LRCevents

https://www.webscorer.com/TROT

https://www.webscorer.com/50306

Example raceids:

406931 (6-day ultra run, happening now)

404637 (uses attached settings with Chip ID = Bib & Chip ID encoding = Decimal)

[Race Pros Sports]

The screenshot is the way I have it set up: Webscorer is set to expect decimal tags. But this only works when the Ultra is set for hexadecimal tags. When the Ultra is set to decimal, the tags come out wrong in Webscorer. I thought this was strange so I made the post.

Thanks for letting me know other timers who are using the Ultra with Webscorer.

[Vesa Suomalainen]

If you do a test with an empty start list using an Impinj reader - and detect the same chip, what’s the chip ID shown on the fast-tap list?

On Oct 2, 2025, at 8:17 PM, Race Pros Sports <racepro...@gmail.com> wrote:

The screenshot is the way I have it set up: Webscorer is set to expect decimal tags. But this only works when the Ultra is set for hexadecimal tags. When the Ultra is set to decimal, the tags come out wrong in Webscorer. I thought this was strange so I made the post.

Thanks for letting me know other timers who are using the Ultra with Webscorer.

On Thu, Oct 2, 2025 at 8:08 PM Vesa Suomalainen <ve...@webscorer.com> wrote:

How have you configured Webscorer?  Are you testing chips without a start list, or are you try to map the chip ID to match bib numbers?  If the latter, which encoding did you select on Webscorer?

There are a handful of organizers using RFID Timing Ultra reader with Webscorer:

https://www.webscorer.com/readysetgo

https://www.webscorer.com/109055

https://www.webscorer.com/LRCevents

https://www.webscorer.com/TROT

https://www.webscorer.com/50306

Example raceids:

406931 (6-day ultra run, happening now)

404637 (uses attached settings with Chip ID = Bib & Chip ID encoding = Decimal)

<Screenshot 2025-10-02 at 7.00.20 PM.png>