Hi,
I was competing in the WEMBO 24hr Solo World Champs over the weekend. Around 15 laps in i noticed my average speed was dropping when i wasnt going that much slower, and then i noticed that the GPS was saying i was down on one of the first climbs when i was at the top of the main climb. I tried pausing and resuming and couldnt get it to start working again so just used my computer as a glorfied heart rate monitor for the remaining laps.
Weirdly enough it continued to accumulate elevation just not distance.
Super disappointing as I geek out on ride data and now I have a dodgy set of data from one of my top 2 biggest rides. 
2 Likes
First, NOICE!
Second, in my experience, if tech is gonna crap out on you, it’s gonna crap out on you when you want it the most. Had a PM die 15 kms in on my longest ever gravel event in Kansas, had my head unit (a Garmin Edge 5something at the time) glitch out during a basecamp Evereresting on a tiny hill that needed 300 reps.
Third, it might be worth contacting support to see if the data is in there somewhere and just isn’t showing up for you
Congrats on your massive ride! I’m assuming you weren’t able to dual record on your phone during the event?
1 Like
I’ve seen many a Knighthood Do go up in flames on Mount Sufferlandria because of technology failures. BTW, this isn’t the only thing that is affected. One person was going for a Grand Fondo (120 km). Computer died halfway through and wouldn’t revive. The key: Prepare for and double record if possible. Phones are great for this. Strava can be your friend, sometimes. Also, there’s the Wahoo App.
I seem to have had exactly the same problem yesterday. 193 km ride but only 35 are recorded. Looks like a bug. Really disappointing.
I had the same thing happen on Saturday albeit on a much shorter ride - around 45km.
About 11Km into the ride I noticed the map was no longer moving. I think speed had gone to “–” rather than zero. Cadence, HR and gradient were all showing OK. I ended the navigation, ended the ride and then rebooted the Roam. Restarted the route and completed the ride without issue.
Ended up with two rides on Wahoo Cloud with a small gap between the end of one and the strat of the next.
Did a 55Km ride yesterday and navigation was flawless.
Has anybody raised a support ticket for this already? I’m happy to raise one.
I raised a support incident today. Navigation continued to work for me but the recording captured only a fraction of the data (distance btw was 49.000 km ). Towards the end of the route the navigation showed me a negative value for the distance to go. Is this the same problem?
No, apologies, what I had sounds quite different.
Navigation had basically failed - my position on the map was fixed although as I continued to ride the map was “turning” in line with my direction. I noticed the error within a Km of it happening and a reboot cleared it and allowed me to carry on. The recording up to the point of failure was correct as was the recording after the reboot.
Hopefully mine was just a one of glitch - ages ago I had a ride where I “rode off the edge of the map” presumably an error with the next tile not loading properly because everything recorded properly. Never happened since!
I had ROAMv1 for 2 years. I rode a lot of ultra marathons. It also froze for me and my friends after exceeding 300-600 km. I wrote to wahoo but there was nothing they could do about it. They did not admit to the unit’s fault, because they explained that ROAM is for max 200 km (what) or 15 hours of riding. This is a memory issue. Design flaw. From what I have found, the fault is the memory unit’s fault, which cannot be fixed by software. When the memory is full, the recording of activity is suspended even though it still shows the current speed. It has ruined my race more than once. So if you are going to ride another longer route, be aware that this problem will occur after a longer route. I currently have ROAM v2 and I have not noticed such a problem so far.
4 Likes
If it can be reproduced, it is a software problem.