Section 8.4.1 of the Bicycle Power Profile describes how a display should interpret zero speed from time or event-synchronous systems through page 0x11. Unfortunately, I don't see consistency with SimulANT+ and some other software we have been testing with and I just want to be sure we're doing the right thing.
Our system is inherently time-synchronous, but if we continue to increment the event count and do not increment accumulated wheel period nor wheel ticks as per the guidance, the SimulANT+ tool displays INFINITY for speed and NaN for average watts.
When we test from 2 USB keys using the SimulANT+ tool (one as Sensor, one as Display), the behavior is of an event synchronous system. The result of setting the sensor to 0 speed is that the event count does not increment and the display still shows the speed prior to when we set to 0 when it should show 0?
The same is true if we do not increment our event count, the older ANT+ Display Simulator shows stopped correctly, as does some other software, however the SimulANT+ tool (and some other software) continues to display the last speed / power before it went to 0.
The solution seems to be a hybrid approach which is to send a few messages with the event count incremented, but no accum wheel period nor wheel tick increments and then stop event count increments. This still results in the SimulANT+ tool reporting INFINITY and NaN, but seems to cover both cases in all the software we've tested with.
Is the INFINITY/NaN from SimulANT+ a bug or could we be doing something wrong?
Thank you.
