Introduction
RunScore connects to transponder and chip/tag timing systems. It reads a bib or chip number automatically as a runner crosses a mat, antenna, or ear. All chip devices are configured through the same Initialize External Timers dialog used for clock-based timers — see Initialize External Timers for menu paths. Data can arrive over a serial port, TCP/IP, or from a file the vendor's middleware produces.
ChronoTrack
ChronoTrack tags carry the runner's bib number directly — RunScore does not look up a chip ID, unlike ChampionChip. Data reaches RunScore through ChronoTrack's middleware (SimpleClient, CCSLite, or the newer Fusion), either live over TCP/IP or from a file the middleware produces.
MyLaps / ChampionChip
RunScore connects to ChampionChip, MyLaps ProChip, and MyLaps BibTag decoders through MYLAPS middleware over TCP/IP. All three devices share the same protocol — ProChip and BibTag are ChampionChip variants that hit the same code path.
iPico Sport / ChipTiming
iPico Sport and ChipTiming (from Brazil) are unrelated chip systems, but RunScore is set up identically for both, so they're documented together. Both can send live data over TCP/IP or be read back from a saved file.
RunScore Open
RunScore's Open Interface lets any third-party middleware feed bib or chip reads into RunScore over TCP/IP or a serial port. The middleware translates whatever protocol the decoder speaks into the comma-delimited RSBCI/RSBI/RSCI format documented below. It then streams those lines to RunScore.
Timing a Chip/Tag Race
Once the hardware is set up and tested, data flows into RunScore as runners cross the mats. Device cabling and ports are on the individual pages under Chip/Bib Timing.
Event Routing
When chip/tag data arrives in RunScore, each read must be assigned to a RunScore event (TIME, SPLIT, CHIP, etc.).
Chip Fields and Miscellaneous
Multiple chip fields