Open capitaineflam25 opened 4 years ago
And it may be 8102 instead of 8086 for a"Cadence only" sensor (not tested, i don't have one)
I had the same problem with the same speed sensor, but it's 8118 for speed sensor according to the doc that you mention (same version as you). Using 8118
fixed the problem for me, but not 8188
. Can you confirm that it's a typo in your message?
I just did a bit more debug to know what was happening:
scan
mode, we can receive all the messages no matter the period, so we can get the data without problemssensor
mode with the wrong period I was receiving EVENT_RX_FAIL
messages which mean
A receive channel missed a message which it was expecting. This happens when a slave is tracking a master and is expecting a message at the set message rate.
And after a few seconds I receive a detach
event and some variables are reset silently and it will never try to recover anymore after that.
Hi,
(Thanks for this project, it is so great ! It's working perfectly with my Favero Assioma power pedals)
i wasn't able to received any data with my Garmin Speed sensor.![image](https://user-images.githubusercontent.com/985702/81708363-7433f980-9471-11ea-9192-c35adbe35805.png)
Then i read the documentation (D00001163_-_ANT+_DeviceProfile-_Bicycle_Speed_and_Cadence_2.1.pdf) and realised that the period of the speedSensor is different that the one for Speed+Cadence.
By changing the period to 8188 i'm getting the datas. (maybe your speed-sensors.js was created after copying speed-cadence-sensors.js
Regards