IR lap timer code

The race tells you which timer is on the gate. Set the same one here. iLap, ArciTimer and ERLT do not share codes. A code that is right for one system is invisible to the others.

Off is a real choice, not an empty box. Use it when this quad should not answer a timer. The IR LED sends nothing, and the gate will not count a lap for this craft.

The code in the box is the code the timer software prints, as hex. You do not type raw bytes. For iLap, copy the 12 characters from the timer. Letters can be upper or lower case. Anything that is not 0-9 or A-F is refused, and the field will not accept more than 12 characters.

Give each quad its own code when several craft fly the same gate. Two quads on the same iLap code, the same ArciTimer ID, or the same ERLT ID look like one aircraft to the timer. The tab stores one code for this board, so a second quad needs its own ID in its own firmware.

iLap is 6 bytes, shown as 12 hex characters. The help under the field says to enter all 12. Until those 12 are there, the code is not saved as a valid iLap code. The demo opens on iLap with the code E00370FC0FFE, so you can see a complete code before you paste your own.

ArciTimer is 9 bytes, shown as 18 hex characters. You do not type them. The list is ID 1 through ID 9, and each row is the code that timer hands out. ID 1 is E00370FC0FFE07E0FF. Choosing ArciTimer from another system starts on ID 1.

ERLT is 1 byte, shown as two hex characters. The list is ID 0 through ID 63. ID 0 is 00, ID 10 is 0A, and ID 63 is 3F. Choosing ERLT from another system starts at 00.

Switching back to the system that was already saved puts that saved code back. Switching to a different system starts from that system's first code, not from a mix of the old bytes.

The footer on the tab says an IR LED on the quad sends this code so the race timer can count laps, and the flight controller restarts after saving. Expect the board to drop off and come back. That reboot is the save, not a failed flash.

Off is saved as the timing system alone, with no code bytes after it. iLap saves 6 bytes, ArciTimer saves 9, and ERLT saves 1. A save with the wrong length is refused, which is why the iLap field will not leave a short code in place.

Some Betaflight builds leave the transponder out. The tab then says this firmware was built without transponder support, and it tells you to rebuild Betaflight with the Transponder option to use an IR lap-timing LED. There is no code to edit until that build is on the board.

This LED is infrared, for the gate. It is not the addressable LED strip, and it is not the video transmitter channel. Colour, rainbow and Raceband live on those other pages. A dark LED strip does not mean the transponder is off, and a VTX channel does not give you a lap code.

Chrome or Edge connects over USB or Bluetooth. Android adds Wi-Fi. iPhone uses Bluetooth or Wi-Fi and has no USB host. The transponder tab needs a Betaflight board. INAV does not show it.

Read the code back after the board reconnects. The timing system should still be the one you saved, and the iLap field, ArciTimer ID, or ERLT ID should match. If it came back as Off, the save did not land. Open the tab again once the board is up, rather than saving a second time while it is still rebooting.

The demo includes Off, iLap, ArciTimer and ERLT, and it starts on iLap. A real board replaces that with the code saved in its firmware. Props can stay on for this tab, because it does not spin motors. Still save only when you mean to reboot the board.