This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Edge 530 Training load spikes into the 10k range

Has anyone else experienced this and figured out what's causing it, it's only been occurring since the latest SW update, and seems to only happen in workouts that have power targets well above FTP. I'm using an Edge 530, Wahoo Kickr V5, Wahoo tickr HRM. While the workout is running on Systm, I'm also recording my workout directly with the Edge using ANT+ connections. Though looking through my data, it doesn't seem like any odd spikes in what's recorded, but how the Edge's algorithms are processing that data.

There have been other users experiencing the same issue over on a reddit forum with the 830:

Connect statistics going crazy since using Edge 830 : Garmin (reddit.com)

0 GWilicers over 2 years ago

After my ride today I noticed a new anomaly, until today Garmin had not updated my cycling VO2 max since I pushed the SW update (16 days, its never gone more than 5 without calculating a new one before) and it also tanked from 57 to 53 (I haven't seen a drop like that since I had Covid).

0 mattpeters81 over 2 years ago

I noticed the exact same thing! I saw a spike from a training load around 1200 to 15000(??!!) back to 1400 and just like you said it occured on the same day I had a workout featuring ~800w for like 10 seconds. Mine was recorded via Zwift (on a Wahoo Kicker Core) in Erg mode also with a Tickr HRM. I did not record the ride to my Edge 530, just Zwift (and obviously it synced later). I haven't noticed an issue with VO2 Max though. I'm not sure if it really affected anything (other than making a messy graph) but unless we get a Garmin response maybe time to submit via email or other ways as obviously this is a bug?

0 Kyle J over 2 years ago in reply to GWilicers

Yes I'd say definitely worth reporting the Load spike issue to Garmin support, that's certainly not normal. And what's also weird is that it disappears again the next day, which a real "7-day load" obviously wouldn't do until a week had passed since the spike.

As for the VO2 max, I'm not so sure that's abnormal, at least for Garmin Edges. In my experience it's not unusual for quite a bit of time to pass between VO2 max updates. It depends on the type of activities I've been doing. It also seems like it's "slower" to drop than it is to rise. The algorithm also seems to have limitations, and depends very much on the type of activity effort. If it doesn't see the "right kind of efforts" then there can be quite a bit of scatter in its extrapolation to VO2 max.

0 mattpeters81 over 2 years ago

I wound up submitting a request to Garmin support. The initial diagnosis is: "It looks like this bug is caused by 3rd party activities (Zwift) not syncing some HR-based data to Garmin Connect correctly, and I will notify you as soon as I have an update." I know you were using Systm (what's up with Wahoo dropping "e"s?? :-P) but I'd guess its something similar (and since I think VO2 needs HRM data that also might explain that issue too). Hopefully they'll fix this soon!