Test Tag Configuration

Test tags allow operators to verify the timing system is working without creating participant data. This page covers how to configure and manage test tags.

Purpose of Test Tags

A test tag:

  • Verifies the Time Machine is reading chips

  • Confirms data is flowing to RaceDay Scoring

  • Does NOT appear as a participant in results

  • Can be used repeatedly throughout the race

Test Tag Requirements

Hardware

You need timing chips that:

  • Are compatible with your Time Machine

  • Are programmed with a unique chip ID

  • Are clearly marked as TEST (coloured tag, label, etc.)

Software Configuration

The chip ID must be configured in RaceDay Scoring to be:

  • Recognized as a valid chip

  • Excluded from participant results

  • Visible in raw reads for verification

Configuration Options

There are several ways to handle test tags:

Option 1: Participant Type Flag

Create a participant type for test chips:

  1. Create a "Test" participant type in RaceDay Scoring

  2. Register your test tags as participants with this type

  3. Configure results to exclude "Test" type from public results

Option 2: Excluded Bib Range

Reserve a bib number range for test chips:

  1. Assign bib numbers like 9999, 9998 to test tags

  2. Configure results to exclude these bib numbers

  3. Document which bib corresponds to which test tag

Option 3: Unregistered Chip Monitoring

Do not register test tags at all:

  • Reads appear in Raw Reads

  • Shows as "Unmatched" which confirms read occurred

  • Simplest approach but requires monitoring Raw Reads

Recommended Approach

The recommended approach for most events:

  1. Use chips programmed with specific, documented chip IDs

  2. Do NOT register these chips as participants

  3. Train operators to check Raw Reads for their test tag chip ID

  4. Clearly label physical tags as "TEST - [Chip ID]"

This approach:

  • Requires no special RaceDay Scoring configuration

  • Works across all events without changes

  • Clearly distinguishes test reads from participant reads

  • Is simple for operators to understand

Test Tag Inventory

Maintain an inventory of test tags:

Tag Label Chip ID Assigned To Location

TEST-A

ABC12345

TM-01 Operator

Start Line

TEST-B

DEF67890

TM-02 Operator

Finish Line

TEST-C

GHI11111

Spare

Timing HQ

Operator Instructions

Provide operators with:

  1. Their assigned test tag

  2. The chip ID of their test tag

  3. Instructions to check Raw Reads for that chip ID

  4. Clear marking that this is a test device

Example operator instruction:

Your test tag is labelled "TEST-A" with chip ID "ABC12345". When you pass through the timing line with this tag, the Time Machine should flash, and you should see chip ABC12345 appear in Raw Reads within a few seconds.

Physical Identification

Clearly mark test tags to prevent confusion:

  • Use coloured tape or stickers

  • Write "TEST" prominently

  • Include the chip ID on the tag

  • Use a different form factor if possible (keychain vs shoe tag)

Pre-Race Distribution

Before race day:

  1. Assign test tags to each timing location

  2. Document assignments in your event plan

  3. Include test tag in equipment checklist for each location

  4. Brief operators on how to use their test tag

Post-Race Collection

After the race:

  1. Collect all test tags

  2. Verify all tags are returned

  3. Check for damage

  4. Store for next event

Troubleshooting

Test Tag Not Reading

  1. Verify tag is compatible with Time Machine

  2. Check tag for damage

  3. Try a different test tag

  4. The issue may be with the specific tag, not the system

Test Tag Appearing in Results

  1. Check participant registration for that chip ID

  2. Remove any registration for test chips

  3. Verify results filtering is configured correctly

Summary

A properly configured test tag system gives operators confidence that the timing system is working throughout race day. Invest time in setting this up correctly and training operators on its use.