Checksum error mid way through ride (Cadence magneto) about fortiusant HOT 11 CLOSED

Sorry for this inconvenience, @iainhay , the Zwifting does not come easy for you.

• Crash was caused by a coding error, which is resolved in new version antDongle.py
• We got in this error, because of the incorrect buffer with an incorrect checksum
  Question now is why this incorrect buffer was there in the first place.

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.
I will upload the new code.

Regarding Cadence sensor, check all connections first. Loose connections will not trigger an error but cause unexpected results.

from fortiusant.

@WouterJD thanks - I'll pull the latest and check back if it happens again 👍

from fortiusant.

Took a spin jut now and this no longer happens.

It did crash with the error:

terminated by signal SIGSEGV (Address boundary error)

But I just restarted and Zwift carried on - so that is fine for now!

Thanks again

from fortiusant.

https://www.strava.com/activities/3369991133
I see your ride!
Software layers do not seem to be stable :-(
I wanted to ask for the logfile but since I did not flush it in the past, it would miss the last part...
Does python stop execution or does it crash itself?

from fortiusant.

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.

from fortiusant.

from fortiusant.

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

from fortiusant.

Good idea. Cadence comes in same call as other parts, so hardware is the likely cause.
Can you still get a trainer-wired cadence sensor, otherwise ANT+ part must be activated

from fortiusant.

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!!

from fortiusant.

@iainhay how are things going?

from fortiusant.

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

from fortiusant.