-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement Long ID sensor #12
Comments
The extended ID puts the top nibble (4 bits) of the ID into the top nibble of the transmission type - see https://www.thisisant.com/developer/resources/tech-bulletin/pairing-to-devices-with-extended-device-numbers |
I had the same problem |
I use the same method as you |
What sensor do you use and how you connect it to the raspi? |
The doc linked by @dhague says
I understand we don't need to "implement long ID", we can just use the 2 bytes device number and disregard the extra 4 bits of the "extended device number".
Tried to adapt the logic at https://github.com/dhague/vpower/blob/master/SpeedCadenceSensorRx.py#L22-L23 as suggested but with any value other than 0 for transmission_type I get no readings from speed sensor.
Tried the 4 options in bits 0-1 |
pi@raspberrypi:~ $ cd /boot/vpower |
Are you using Python 3? |
I'm using Python 3.9.2 on PC, Python 3 on raspberry and latest raspbian full version. |
Please open another issue since this is not related to long sensor ID and post the full traceback. |
Hi, I use new speed sensor and they have long ID but in the vpower.cfg file we must use short ID, have you a solution for me ?
Thanks for your help
The text was updated successfully, but these errors were encountered: