The SFlag column in the Timing tab contains some additional information about the passing which was transmitted by the transponder. This allows easier identification of problematic setups.
SFlag messages may include a number before the message, this is how many times the error occured before the transponder was able to send the passing information. Multiple messages may also appear together if there were multiple errors or messages.
Below are the possible SFlag messages:
SFlag Message |
Explanation / Possible Causes |
Possible Solutions |
CH BUSY |
- 2.4Ghz Channel was busy and the transponder could not communicate with Active Device.
- High interference from outside sources on 2.4Ghz Channel
- Too many transponders in field transmitting on 2.4Ghz (May occur if tracking is enabled on the transponders on the same channel as timing setup)
|
- If possible change the channel of active device. The channel inspector on the decoder or through the timing module for USB Timing Boxes will show the best channel to use.
- Move source of interference (such as Microphones, drones, wireless access points)
|
NO ACK |
- Transponder did not receive acknowledgement from the active device when sending passing information.
- Poor connection quality on 2.4Ghz channel.
- No clear line of sight between transponder and active device or interference from metal structures.
|
- Ensure the receiving antenna is in clear space with clear line of sight to transponders.
- Raise the antenna above anything which may reduce line of sight or use a range extender to raise the 2.4Ghz antenna.
- Check transponder position for optimal line of sight.
|
STORE |
- The passing was saved as a stored passing on the transponder.
- If a transponder cannot send the passing information due to CH BUSY or NO ACK then the passing will be stored.
- Loop Box set to Store mode.
|
- If this was intended then no action needs to be taken.
- See fixes for CH BUSY and NO ACK above to reduce the chance of a passing being stored by the transponder.
|
DS/WARN |
- The Transponder was woken from Deep Sleep mode OR
- A V3 Transponder issued a warning, most likely due to EMI exposure
|
|