Troubleshooting the ANT+ module
No entity ever appears
Cause. Either DeviceID was never set to a real device (it defaults to 0, which no real
heart rate strap uses), or the configured device number is not currently broadcasting.
Fix. Open the module settings and pick a device from the DeviceID dropdown; it only lists
devices the module can currently see. If the dropdown is empty, the USB ANT stick itself is not
being found; confirm Windows enumerates it (Device Manager) before HEAT Capture starts.
The reading was there, then disappeared
Cause. The configured device stopped broadcasting: out of range, powered off, or a dead battery. This module clears the reading immediately on loss, unlike some other biometric modules that keep republishing the last value:
Device {deviceId} lost. Waiting for reconnection.Fix. Nothing to configure: the module rescans every 100 ms and resumes automatically once the device is back in range and broadcasting. If it never comes back, check the strap’s battery and that it is actually on.
The dropdown is empty while another ANT+ device is visible
Cause. The setting scan waits until any ANT+ device is discovered, but only returns heart-rate devices. A bike, cadence or other ANT+ sensor can end the wait before the heart-rate monitor appears.
Fix. Wake the intended heart-rate monitor first, then refresh DeviceID. The dropdown only
returns heart-rate devices; other ANT+ device types are never selectable.
The USB ANT stick was power-cycled or reset mid-session
Cause. The module listens for the radio’s own startup notification and rescans automatically when it sees one, so a stick that resets (for example, after being briefly unplugged) does not need the module restarted.
Fix. No action needed beyond waiting for the reconnect logic described above; if the device still does not reappear, treat it as a lost-connection case.