Closed laberning closed 2 years ago
This happens because in the FTMS protocol implementation we set the value for pace (in seconds) to the highest possible value (0xFFFF) if one does not row.
Technically thats the most correct value that we could use (closest to infinity). But that does not seem to play nicely with applications such as MyHomeFit.
The diagram for pace in the logbook entries of MyHomeFit do not look very nice, because rowing pauses are shown as huge spikes in the diagram. These spikes cause the axis axis for pace in seconds to go up way to 70000s / 500m.