Spartan update complains

DRezvoff

@Mff73 if there are no other options. then yes. hard reset only
and reconfigure hours, workouts, and more…: (

sartoric

@DRezvoff
I would start with a soft reset first.
I never had that kind of problem, maybe once in years.

DRezvoff

@sartoric well, I have to do a sotf reset all the time a month… :(((

Mff73

@DRezvoff
just to check : your issue is that your watch is blocked at the saving workout step ? Like never ending saving ?
If so, do you have enabled the “feeling” option ? it was a workaround for such issues if i remember well.
If already enabled, you still can try to connect it to SA right after soft reset and send logs to suunto (i guess).

DRezvoff

@Mff73 The feeling option is enabled.
if the problem is known and it is clearly a clock software problem, why is there no bug fix update???

sartoric

@DRezvoff
Did you contacted suunto support ? I would do it

DRezvoff

@sartoric I hope Suunto technicians read this forum and are aware of the problem…
if there are no changes, I will contact support directly

isazi

@DRezvoff better contact support, Suunto is not really monitoring this forum for bugs. There are a couple of developers here in the forum, sure, but it is better to let Suunto know.

DRezvoff

@isazi The Russian support service could not help me… they give a standard set of actions that are written on the Suunto website.
The clock began to lie at a climb of 20-50 m… that’s a lot. I have repeatedly thought about changing the clock to Garmin, they release updates regularly.

isazi

@drezvoff does your watch has a barometer? I don’t know the specifics it. Also, yes Garmin releases many updates, not too many for watches that are as old as yours though.

Mi_chael

@drezvoff

My fenix have many update but too many bugs…!!!

DRezvoff

@isazi no, my watch model without a barometer

DRezvoff

@mi_chael I compare climbing readings with other athletes who use Polar or Garmin watches. The total difference in climbing at a distance of 17km differs by 100-200m… That’s a huge difference.

DRezvoff

We all ran the same distance together…

Here’s the data from my watch, climbing 573m
https://www.strava.com/activities/5778881853

Here are the data from the clock Polar, climbing 838m
https://www.strava.com/activities/5778881853

Here is the data from the watch Garmin, climbing 825m
https://www.strava.com/activities/5779198526

The difference in climb is almost 300 m!!! And this is in an open area, without a forest.

Dimitrios Kanellopoulos

@drezvoff non baro devices have this issue on not constant climbs.

DRezvoff

yesterday’s training, the difference in climbing 339m per 30km…

Suunto Spartan Sport WHR
https://www.strava.com/activities/5984088835

Polar Vintage M
https://www.strava.com/activities/5984102067

sartoric

@drezvoff
Your watch still has no barometer, I don’t think you’ll see any big improvement keep posting your stravaS

eg. https://www.reddit.com/r/Polarfitness/comments/jidk6x/polar_vantage_m_altimeter_measurement_completely/

A Former User

@drezvoff said in Spartan update complains:

yesterday’s training, the difference in climbing 339m per 30km…

Suunto Spartan Sport WHR
https://www.strava.com/activities/5984088835

Polar Vintage M
https://www.strava.com/activities/5984102067

As others said, that device has no barometer. The readings may not be very precise.
You can read more about it here or here
Also spartan line is kinda known to not have more updates.
I think your best bet is to use altitude correction on the platform you use to see your trainings.
Also, there will be always difference between brands.

DRezvoff

@sartoric I hope that the developer will make new software and update the clock. Processing algorithms given from satellites change, accuracy, etc…
in the new clock, new algorithms…

DRezvoff

@andré-faria the difference between brands is normal.
But when the difference in determining the climb is 300-400m, it’s a lot…
software update and it is necessary to apply new modern data processing algorithms in the clock… Suunto did not update the early models, but simply stopped supporting them…