Suunto Software update Q1 (2.53.42)
-
@Speed-Man in this forum I’ve already seen few people that use ZoneSense app and get crashes, maybe you should drop that one and see if it helps. I am just guessing but it might be related that ZS is now native and the app is not needed at all.
-
@aiv4r Thank you, I’ll give it a try
-
@Giorgio60 said in Suunto Software update Q1 (2.53.42):
Per quanto riguarda la ricarica della batteria sul mio suunto race 2, effettivamente ho notato anche io una certa scarica un po troppo veloce se blocco la ricarica sotto il 100%. Ma ho risolto caricando sempre al 100%
I see, you think you’re the funny guy here. I won’t comment on that any further, except for this: Even after several hours, the watch only reaches 99%
-
@tomtom73 said in Suunto Software update Q1 (2.53.42):
I’ve just lost 3% in 7h while not using the watch at all, no HR. It’s more than before the update
Try performing a soft reset. That usually solves the issue for me. Unfortunately, the problem tends to come back after a while.
-
@HonzaS said in Suunto Software update Q1 (2.53.42):
Why the magnetic declination compass value couldn’t be downloaded automatically while syncing the watch?
That’s what Garmin does.
Suunto: Ambit, Ambit 3 Peak, 9 Baro, Race S, Race Ti, Vertical 2 Ti
Garmin: Forerunner 210, Forerunner 610, Fenix 6X, Fenix 7X Ti -
@sky-runner From now on, a sensitivity of 0.1 should be entered for magnetic declination degrees in the next update. We enter either 6.0 or 6.5 instead of 6.3.
-
@safari when will you navigate with a watch at a precision higher than 1° anyway?
t6, S6, Elementum Terra, Ambit 3 Sapphire, Spartan Ultra Copper, Traverse Alpha, S7 Graphite LE, S9B Ambassador, S9P Titanium, S9PP Titanium, Vertical All Black, Race Titanium Charcoal, Race S Titanium Courtney, Run Lime, Race 2, Vertical 2 Titanium
-
@sky-runner I’ve seen you bring this up many times. Garmin is great-but why do you think everyone has to use Garmin?
If Suunto were exactly like Garmin, I wouldn’t use it either.
Don’t try to push others to be like someone else.
-
@Egika
Rest assured, there is a significant angle difference between 6.0 and 6.5. -
@safari There is not a “significant difference” in a 0.5° error for a sport watch, at all.
Lets say you are in a desert, and are planing a 50km walk in a single direction to reach the next oasis, and exclusively use the compass to orient yourself, you would have just, at most, 400m of error at the end.
Even for this highly un-realistic scenario (who tries to do that ? ever ? ) the error is way small enough to be like “oh, the Oasis is just right over here !”Lets kick things up a notch ! You are in Nianey, at the bottom edge of the Sahara desert, and want to go to Alger, at the Mediterranean sea border up south…with your slightly incorrect compass mounted on your GPS capable watch.
After 2500km of walking in the desert, you will arrive at Tessela El Merdja, just 22km in the suburbs of Alger, where anyone will be able to guide you to it.And, if you ever have this scenario, don’t forget that you can enter actual GPS coordinates in watch and be done with it.
EDIT: I took a 0.5° error, and should have been using 0.2°, so the error values are 160m and 8.8km
-
@Elipsus :)) That’s also true.
-
@Elipsus so you only check the direction at the start of the 50km hike?
-
@Gunnar I don’t check anything, I enter a GPS coordinate, and I’m following that !
But in the hypothetical scenario, I would be following a path along a 0.5° orientation error, so that’s how I got my rough calculation error (and I now realize I should have been using 0.2, which would be the highest rounding error between 6 and 6.5)
