-
Notifications
You must be signed in to change notification settings - Fork 39
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
Polar (Vantage V) Support? #71
Comments
Gymnasticon behaves like a regular cadence and power sensor, where data is based on the simulated crank revolution. There isn't really such a thing as "sending too much messages". To make sure the communication between gymnasticon and watch is working, try to run gymnasticon in "bot" mode, e.g. with this config file:
That will make gymnasticon output a constant cadence of 95 rpm and power of 200 W. You can then check on your watch what you see and make sure it matches. |
These drops indicate a Bluetooth connection issue between the device running Gymnasticon and your Polar watch. What device are you running Gymnasticon on? Also check if the Polar watch supports ANT+. And alternative would be to use Gymnasticon with ANT+ for the watch. |
Gymnasticon is running on Pi Zero W. During the test the watch was less than 40 cm away. But WiFi is active, I will make tests with disabled WiFi. |
The Pi Zero W is OK, when it comes to Bluetooth + Wifi. I also use that platform without any issues. But I use it with a Garmin watch and an external ANT+ stick. Although that's working from 2-3 m away without any issues. Someone with more knowledge of the Bluetooth protocol might be able to look at log files and see what the issue with the Bluetooth dropouts is and if it can be fixed from Gymnasticon side. Can you collect some Bluetooth logs from Gymnasticon:
Once you see a few dropouts on your watch, you can kill the gymnasticon process and also btmon. |
Hi @Harti-801
It is possible to change the bot's power and cadence at runtime by sending it a JSON object over UDP. e.g.
Also, are you able to provide the raw data that graph is based on? e.g. a csv of "timestamp, power, cadence" ? |
@Harti-801 Btw, if you run the bot with cadence=60 do you still get dropouts? |
@ptx2 attached a csv file that contains the data of the graph. |
I created a log as recommended by @chriselsen Unfortunately I was not able to change the values over the UDP command. Maybe I make typos or something totaly wrong. I will try again. Christian_H_2021-03-10_08-42-52_polar-ble_3.ZIP |
Sorry, try adding Thanks for attaching the logs! |
Hi @Harti-801 are you still having issues with this? |
Hi @ptx2, sorry for no updates that long time. Yes, the issue is still the same. I am wondering if I am the only one using a Polar device. |
I did a first ride with my Peloton connected to a Polar Vantage V. So far this device was not mentioned as supported or rather tested device.
During my first test ride with the new setup two issues occured:
I could not find any issue like this, so I add this new one. Did anyone has experiences with a Polar Vantage V?
What I will do next is to double check with a Zwift setup or any kinde of BT app to make sure that my setup is working like expacted.
The text was updated successfully, but these errors were encountered: