Ticket Created
over 4 years ago

WERETECH-10039

ANT+ Battery Status

The latest in the saga for Battery Status. I used an ANT+ dongle on my Windows Laptop, and paired it with the Eclipse Simulator. I tried both an older Garmin Cadence Sensor, and a brand new one (the one that does both ANT and BT). Same outcome. In both cases, the CIQ data field immediately gets Device State info. After maybe 30-40 seconds, the ProductInfo.serial number comes thru. Just like in real life when paired to a real Garmin Edge computer. But in both cases, even after several minutes, the Battery Status remains null.

When I pair the new cadence sensor to my actual Garmin Edge computer, the Battery Status does come up as OK within 15 seconds or so and then maybe 30 seconds later the Serial # info comes through.

Any clue why the polling code isn't seeing the Battery Status?

Oh, also, the State Update Listener is triggering, but the BatteryStatusListener is not.

DaveBrillhart
Parents
  • over 4 years ago
    [quote userid="43945" url="~/developer/connect-iq/f/discussion/245190/ant-battery-status/1162509"]But the polling method "cadenceDeviceState.deviceNumber" returns some strange value [26107] that doesn't correlate to anything I can figure out. Any idea? Could this be an indication of why we're seeing the bug where the polling method doesn't return a valid battery voltage?[/quote] Hard to say, could be. I think I have never used DeviceState.deviceNumber, since it has not been AntId. However, it is not clear if this should be AntId, or some other deviceNumber. SDK says this:     deviceNumber     The current Device ID being tracked/searched for. but AntPlus.Message is like this:     deviceNumber     The Unique device number (ANT-id). So antplus is very specific it is AntId, but the other is not. Would make sense they'd be the same, so possibly a bug too. And who knows what side effects it would have.
Comment
  • over 4 years ago
    [quote userid="43945" url="~/developer/connect-iq/f/discussion/245190/ant-battery-status/1162509"]But the polling method "cadenceDeviceState.deviceNumber" returns some strange value [26107] that doesn't correlate to anything I can figure out. Any idea? Could this be an indication of why we're seeing the bug where the polling method doesn't return a valid battery voltage?[/quote] Hard to say, could be. I think I have never used DeviceState.deviceNumber, since it has not been AntId. However, it is not clear if this should be AntId, or some other deviceNumber. SDK says this:     deviceNumber     The current Device ID being tracked/searched for. but AntPlus.Message is like this:     deviceNumber     The Unique device number (ANT-id). So antplus is very specific it is AntId, but the other is not. Would make sense they'd be the same, so possibly a bug too. And who knows what side effects it would have.
Children
No Data