-
-
Notifications
You must be signed in to change notification settings - Fork 78
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
Checksum error mid way through ride (Cadence magneto) #66
Comments
Sorry for this inconvenience, @iainhay , the Zwifting does not come easy for you.
After the crash, restarting is causing problems which makes me think that those problems caused the incorrect buffer. All I can say from this distance is reboot the whole thing (power down dongle) and restart. Regarding Cadence sensor, check all connections first. Loose connections will not trigger an error but cause unexpected results. |
@WouterJD thanks - I'll pull the latest and check back if it happens again 👍 |
Took a spin jut now and this no longer happens. It did crash with the error:
But I just restarted and Zwift carried on - so that is fine for now! Thanks again |
https://www.strava.com/activities/3369991133 |
What do you mean don't seem to be stable? It crashed itself - will check if it happens again though. The cadence doesn't work on my trainer, so I think Zwift estimates it from the power? No other app picks up cadence at all - even FortiusANT, and my understanding is that Zwift uses this for the speed - which would make sense because when I hit a hill and I keep my power the same, Zwift says my cadence drops (which it doesn't) and so the speed drops. E.g. today I hit a hill and speed dropped to like 5kph and it took me ages to get up the hill, even though the cadence hadn't dropped at all. |
A ANT+ FE-C device sends power,cadence,speed and heart rate to Zwift.Zwift does not use heart rate because it expects a separate device.Zwift does not use speed but calculates the speed based upon the received power and the internal knowledge of slope, rider weight and internal formula's. Do realize that the wheel speed is irrelevant and direct drive trainers do not even have a wheel.
I do not know if there is no cadence what Zwift would do (never tried).
Met vriendelijke groeten Wouter Dubbeldam
On Wed, Apr 29, 2020 at 5:54 PM +0200, "Iain Hay" <[email protected]> wrote:
What do you mean don't seem to be stable?
It crashed itself - will check if it happens again though.
The cadence doesn't work on my trainer, so I think Zwift estimates it from the power? No other app picks up cadence at all - even FortiusANT, and my understanding is that Zwift uses this for the speed - which would make sense because when I hit a hill and I keep my power the same, Zwift says my cadence drops (which it doesn't) and so the speed drops. E.g. today I hit a hill and speed dropped to like 5kph and it took me ages to get up the hill, even though the cadence hadn't dropped at all.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Will grab a cadence and see how that goes, nothing is picking up cadence, not rouvy, tacx software, trainer road or FortiusANT - all the other results seem okay |
Good idea. Cadence comes in same call as other parts, so hardware is the likely cause. |
Was just taking a look, the pedal attachement is plastic, and open on one end so it looks like the magnet has fallen out... Will order a new magnet just to see if thats the cause, if not a ANT+ one - someone is really making it difficult for me to ride!! |
@iainhay how are things going? |
Hey @WouterJD My new cadence sensor arrived yesterday, it connects etc and will go for a ride today. Haven't got this error since either so happy for you to close. I saw the posts about the CYCPLUS dongles too, haven't had a chance to catch up but will have a look today too! Thanks again |
* #363 st7789b added; Waveshare 1.3 LCD with different pin layout * PR#365 define waveshare pins * PR #365 Waveshare reset pins * Collector first version; write to FitnessMachineControlPoint fails * bleClient.py working on Raspberry pi0W raspbian 10 (buster) * bleClient.py works on rpi0W with raspbian v10 buster * bleClient.py works on rpi0W with raspbian v10 buster * Server still under editing * bleBleak.py works on rpi0W with raspbian v10 buster * bleBleak.py works on rpi0W with raspbian v10 buster * FortiusAnt now works with bless library, ready for fieldtest * spaces removed * bless implementation works on Windows & Raspberry * General Access Profile, further tests * Made available to bless as example * Code cleanup * logfile improvements * Improved error handling and Changed access rights * -dall activates all debug options * -d log activates all logging but not json * -d all and -d log code improvement * manual for #366 and problem solved for #373 * #379 fonts-dejavu added in install * #366 install bless library from development branch * Version 6.4 candidate for merge * Small manual update * Release BLE/bless, version 6.5 * Last manual update for release of BLE/bless
Hey @WouterJD
Adding this as a new issue, couldn't find anything similar and I have a couple of questions.
Now I'm connected (wahoo!) I was trying out my first proper ride (see strava here). Mid way through I noticed power was constant at 135W regardless or stopping, or increasing my output. Checking terminal I got the following message:
You can see this on the power in strava too.]
So, 2 questions:
Is there something I need to do differently to avoid that error? After this error I FortuisANT showed no results so the error basically ended my ride
I tried to exit FortiusANT and restart, unplug the dongles but Zwift wouldn't pair when paused - I would need to end the ride and restart Zwift. Is there a way to get this reconnected to resume the rise?
Side note - I'm not convinced cadence is working properly as it doesn't seem to match my input - but this FortiusANT doesn't pick up Cadence so I think this is somthing with the trainer - will try and get that working of buy a new Cadence sensor to confirm.
The text was updated successfully, but these errors were encountered: