FR970 crashed at the half marathon mark of my marathon (fw 18.29). Do you keep a map data screen in your race profile, or only when navigating?
Hi all,
my Forerunner 970 (software 18.29) crashed during the Cologne Marathon yesterday, almost exactly at the half marathon mark. I got the triangle, the watch rebooted and then kept recording, but I lost about 1:40 min of elapsed time and roughly 350 m of distance. Pacing the second half was pretty much guesswork after that.
Some details:
- Course loaded from Garmin Connect (race event), with "Auto Lap by Timing Gates" so laps triggered at the official km markers - that was very nice, even though the "last lap" on my datafield was the actual last km by GPS.
- No external sensors, no Connect IQ data fields, battery at 85%
- recovery_mode_log.txt shows "RTL Trap detected, errnum: 0x6e5d8035" at the moment of the crash
- No RAM dump in GARMIN/Debug/Dump
- After the reboot, laps were triggered by GPS distance, no longer by the timing gates
- In the FIT file, course point alerts sometimes fired 20 to 34 times in a row, once per second
I've reported it to Garmin support. Two questions for you. The last one is more important:
Has anyone else had crashes on 18.29, especially during long runs or races with a course loaded?
What do your data screens look like for running and racing? Do you keep the map as a permanent data screen, or do you leave it off and only rely on it while navigating? And does the FR970 force the map screen back in when you start a course, even if you removed it from the profile?
I'm considering a separate race profile without the map screen but still using the course for the timing gates. Curious how others handle this.
Thanks!