Chip File

Depending on your setup and type of transponders used it may be necessary to assign transponders to participants to ensure timing data is assigned to the correct participant. 

By default, when using Passive RACE RESULT Transponders where the bib number is equal to chip number then it is not necessary to use a chip file or any transponder assignment. In most cases, when working with passive transponders the chip number (or chip code) is the same as bib number and so times are automatically allocated. 

When working with reusable transponders such as the RACE RESULT HuTag or the Active Transponders, or when chip number is NOT equal the bib number then you will need to use a chip file or alternative transponder assignment method. 

A chip file can be entered or imported in Main Window->Chip File. Simply enter chip code and bib number in the table, or import an Excel, TXT or CSV file with the corresponding Bib and Chip Code fields. 

You can also search the chip file by Chip Code or Bib to lookup specific participants. 

If you are using passive transponders with a chip file and need to map a different chip and bib numbers then you should pay attention to the Chip File Settings.

You can also create a two-step mapping for transponders which may be pre-labelled but where chip label is not necessarily equal to bib number. 

Chip File Settings

There are 3 options for Chip File settings which affect how the chip file or Transponder1 / Transponder 2 fields are used.

 

"Use chip file or transponder fields only for Transponder Codes (e.g., DHANX23). Chip Codes (e.g., 1423) cannot be used in the chip file or transponder fields. Normal passive transponders programmed with the bib number can also be used. [Recommended for most events]"

This is the most common option, it allows you to use Transponders with alpha-numeric codes (Active Transponders, HuTags, Reusable ShoeTags or A-Z Transponders) or assumes that if a numerical chip code is received then Chip Number = Bib Number

Below this are 2 options for how transponder codes are then mapped to a participant.

"Search bib from chip file table in field bib no. [default]" - The bib number in the chip file table will be matched against the bib field of the participants.

Chip Code -> Bib Number
(for example: ZDXED44 -> 44)

Alternatively, you can create a two-step mapping using "Search bib from chip file table in transponder fields [caution]"

Chip Code -> Chip Number -> Bib Number
(for example: ZDXED44 -> 744 -> 44)

The chip ZDXED44 has a sticker with its chip number 744. ZDXED44 and 744 will be entered in the chip file table. In the participants Transponder 1 or Transponder 2 field the chip number should be entered. In the example above, bib number 44 has chip number 744.

The main advantage is that you can more easily assign chip numbers to participants. Instead of handling complex chip codes such as ZDXED44, you only need to enter 744.

 

"Transponder Codes (e.g., DHANX23) or Chip Codes (e.g. 1423) can be used in the chip file or transponder fields. Normal passive transponders programmed with the bib number can also be used."

In this mode you can use transponders with alpha-numeric codes, and can also map non-matching bib and chip codes. In this mode if a passive transponder with a chip number is scanned it is first checked against the chip file, and assigned to the corresponding bib, if there is no mapping for this chip to a bib then it is assumed that for this chip the Chip Number = Bib Number. 

 

"Transponder Codes (e.g., DHANX23) or Chip Codes (e.g., 1423) can be used in the chip file or transponder fields. Normal passive transponders programmed with the bib number will not be recognized unless they appear in the chip file or transponder fields! In other words, with this option you must use either a chip file or the transponder fields for every participant in the event."

In this mode you can use transponders with alpha-numeric codes, but if you use normal passive transponders then the chip code must be mapped to a bib number. Any chips which are not allocated in the chip file or transponder fields will be treated as unknown transponders.

 

Methods to Assign Transponders

There are three options to assign transponders to participants, the handling of all options is identical and multple methods may be used simultaneously. 

Chip File

The chip file is the simplest way to assign transponders when you have a known, pre-allocated transponder for each bib. 

Transponder1 / Transponder2 Fields

The default transponder fields can be enabled in the Participant Data default fields. When enabled these fields will then be displayed in the participants window. 

Values for these fields may be imported with your participant data or may be assigned using a check-in kiosk for example. 

Additional Fields - Transponder Type

If you require multiple transponder assignments for participants you can create any number of Additional Fields with the type Transponder.

Values for these fields may be imported with your participant data or may be assigned using a check-in kiosk for example.