Skip to main content

Chip Fields and Miscellaneous

Multiple chip fields​

By default, RunScore searches one chip field when matching an incoming chip read to a database record. Some race scenarios need more than one:

  • Cross-country — a chip on each foot for more accurate timing.
  • Relay — each team member has a different chip, all stored under the same team record.

Setup​

Add a second chip search field in the Design Screen right after the first chip field. Give it a different name (for example, CHIP2).

Then tell RunScore how many chip fields to search. Set this in entries.ini:

entries.ini
Chip fields         2

RunScore searches each chip field in order. If the chip code is not found in the first field, it tries the second field before reporting the chip as unmatched or adding a new record.

Per-race setting

Chip fields is set only in entries.ini, so it applies per race — you might want two chip fields for cross-country but only one for a road race.

Multiple bib tags​

If you need to assign more than one bib tag to each runner (for example, one tag on the front and one on the back), there are two approaches.

Approach 1: Second BibTag search field​

  1. Add a BibTag search field right after the bib field in the Design Screen. (The bib field must remain the first search field.)
  2. In Tools → Chip Options, check Bib ID.

With Bib ID enabled, RunScore treats the incoming data as a bib number and searches the bib tag fields. If you set Chip ID instead, the data is not processed as a MyLaps tag.

Approach 2: Use ChampionChip device mode​

If you are using MyLaps BibTag hardware, you can configure the device slot as ChampionChip instead of MyLaps BibTag:

  1. Add multiple tag fields after the bib field in the Design Screen.
  2. In the Initialize External Timers dialog, select ChampionChip as the device.

RunScore will search the first tag field for a match. This bypasses the BibTag-specific logic and uses the chip-based lookup instead.

Runner-owned chips​

When a runner shows up with their own chip (not one you issued), store it in the second chip field and leave the first chip field blank.

  1. Open the runner's record in Enter/Edit Names.
  2. Leave the first chip field empty (reserved for race-issued chips).
  3. Enter the runner's personal chip code in the second chip field.
  4. Save the record.

RunScore searches both fields when multiple chip fields are configured, so the personal chip will still be matched on race day.

Non-returned chips​

Tracking which chips were not returned after the race is a common logistics task. RunScore handles this through a listing file.

Procedure​

  1. After the race, collect all returned chips (including unused ones).
  2. Scan them into a placeholder event — a temporary event created just for this purpose (for example, an event named RETURNED).
  3. Run a listing file that finds runners who have a chip but are not in the placeholder event.

Sample listing file​

NotReturned.lst
* Find names of those who did not return chips
Did Not Finish
event              RETURNED
select             no.
NE
field              no.
field              first name
field              last name
field              phone
field              e-mail

This listing selects everyone whose bib number is Not Equal to any bib in the RETURNED event. In other words, it finds everyone who did not have a chip scanned back in. The output gives you their contact information for follow-up.

Bib or Chip per race​

The Bib ID / Chip ID toggle in Chip Options applies globally (per-profile). To override it for a single race, add a Bib or Chip line to entries.ini:

ValueEffect
bibTreat incoming IDs as bib numbers
chipTreat incoming IDs as chip codes (default)