Here we go again: Race crashes mid activity on trainer indoor ride. This is so sad!
-
@Dimitrios-Kanellopoulos yes. Why?
This H10 has two channels which are independent. Always works like this and didn’t give any problems prior and after.How can I see those logs myself?
-
@Olaf-Gottschalk said in Here we go again: Race crashes mid activity on trainer indoor ride. This is so sad!:
In every setup I run the specific H10 HR belt is used with its 2 BT channels.
Outdoors: Wahoo & Race
Indoors: PC & RaceFWIW, I use the exact same setup indoors and outdoors as you, i.e.,
- H10 + power meter pedals connected to both Race and Wahoo Roam (outdoors)
- H10 + power meter pedals connected to both Race and Zwift (indoor)
So far I have done 69 activities (mostly indoor) since getting the Race and have not experienced any reboots or problems during activities. The rides are usually between 1 to 3 hours.
This doesn’t really help you but I just wanted to share my (positive) experience with the same setup.
-
@Mads-Hintz-Madsen I was wondering if at this point all the problems are due to a defective unit–and he never wanted to send it in for service. gosh.
-
@Mads-Hintz-Madsen it helps a lot, Mads!
Because that’s exactly what I did since November - and I cannot understand what this should have to do with a crash according to the logs.
The H10 does not really care what’s connected to its 2 channels and the Race does not even know anything about a second channel…If like @Dimitrios-Kanellopoulos says this would be the reason for a crash… Would be horrifying.
-
@robis said in Here we go again: Race crashes mid activity on trainer indoor ride. This is so sad!:
@Mads-Hintz-Madsen I was wondering if at this point all the problems are due to a defective unit–and he never wanted to send it in for service. gosh.
Robis. I am developing software. Believe me, I do know what software issues are.
I’ve been bugged around by other companies with sending in perfectly fine units only to suffer A LOT by having to organize replacement watches for weeks ONLY to get back the same or a different unit and waiting for the next crash to happen weeks later.This is pure software.
If Suunto really strongly believes in the possibility that such things are hardware related, they should immediately send out a replacement upfront to minimize the impact to end users to almost no suffering.
-
So far I have done 69 activities (mostly indoor) since getting the Race and have not experienced any reboots or problems during activities. The rides are usually between 1 to 3 hours.
I am at 131 activities since November, up to 6 hours, and 2 crashes so far with the first one based on an issue fixed with an update…
But as I said: no crash is the only acceptable crash count…
-
@Olaf-Gottschalk BTW, are you using any Suunto+ apps?
These apps are adding additional real-time signal processing so I’m wondering if there is some risk that the CPU cannot keep up with certain computational heavy Suunto+ apps in addition to dealing with both external heart rate and power meter sensor. Just pure speculation as I have no idea if computational overload is even close to being an issue.
I’m personally using the Fat Burner and Training Peaks Ride apps with every activity.
-
@Mads-Hintz-Madsen This is what Support wrote me today when I contacted them to report the logs from my two crashes with the latest stable software (26.12 - hiking and 08.01 - walking):
-
@Mads-Hintz-Madsen thanks for asking. I’ve tried them for hiking and walking, but not for indoors rides - but it could very well be that there is a default app set by Suunto without any interaction by me. Let me check.
Yep. “HR zones duration”.I could disable this one…
But, in my opinion: the watch must be designed in a way to prevent any failing app from crashing the system. Like a sandbox. Otherwise the apps are completely and utterly dangerous stuff.It would be a totally weird way to tell customers “it’s your fault cause you use these apps”. Kind of sick.
Plus it never helps to restore my faith in the product for a random crash every few weeks. Because if I disable an app which I genuinely want - and it does not crash for the first time after disabling it, that’s not at all a proof we have the culprit.
So, consequently this answer by support simply states “never use any apps or if you do, it’s at your own risk”.
-
@Olaf-Gottschalk said in Here we go again: Race crashes mid activity on trainer indoor ride. This is so sad!:
This is pure software.
we shall see…
-
My first Suunto Race had this crashing issue, maybe 4-5 times within a span of 4 weeks. Sent it in locally to check but came back to me stating they cannot find any issue. In the end, I got a replacement watch for another reason - optical HR will sometimes not be responsive whenever you don’t wear it continuously. Now that I got a new replacement watch, this same issue of crashing just happened again during an activity . That really sucks. Even though the activity was saved, I had to start another one to continue to track. I never had such incidents for Garmin polar or COROS. I really love suunto but with these things happening, I think I may end up selling and going back to Garmin.
-
@leafs93 said in Here we go again: Race crashes mid activity on trainer indoor ride. This is so sad!:
I think I may end up selling and going back to Garmin.
Whatever you use tomorrow, Suunto community forum always welcome you.
-
@Olaf-Gottschalk Hmm - I am pretty close to your use level (24/7 an d10-15 hours a week recording. With an earlier device I would have issues near specific locations - not so much GPS issues, but total connectivity - I think folks in those areas had cell phone/RF blockers (illegal, but it was an interesting part of LA) and sometimes those are around LE or Mil installations. Do you issues crop up around the same geog area?
just a WAG from my own experiences.
