@brad_olwin absolutely agree with you. My experiences from Germany are roughly the same. As soon as you have the ticket from support to send it back / to Suunto miracles happen.
Touchscreen in Spartan Sport WHR without function - sent to Finland, repaired and returned to my place in only 4 days, free of charge. Button no longer woirk ed on my 6d - 4 days, repaired and returned free of charge, writing for the buttons for scratched (too easily) of the watch - repaired and returned free if charge. Best support for hardware ever.
Parts of the support staff to communicate with at the beginning seem rather at least a little bit overwhelmed and not too knowledgeable about details after their helpfile/database ends.

@sartoric said in [Watch] Instant HR on new firmware 2.0.40 (spartan):

@yannis-belouris
30 sec is (maybe was ?) the time frame needed to have a valid HR sampling.

If I remember well (I don’t have one) it’s the same for hr belt

My opinion is that we are mistaking a valid engineering limitation (30 secs) with a possible solution like sampling every minute and displaying this until a valid current HR sample.
We need to strive for an excellent customer experience despite hardware limitations

@RiphRaph @Claymore Well, it took almost two weeks, but when I checked Movescount today the run had finally uploaded. All’s well that ends well. ☺

@soojong-moon Honestly, I don’t know. Since I’ve learned that watch is supposed to show 16 closest POIs (or 16 whichever POIs), I always tried to keep the amount lower than 16. So when I move to the location where I need new POIs, I delete the “old ones” from my watch. I am for sure limited by this relatively low number, but at least my watch seems to be predictable now and all my POIs are shown correctly.

I can test larger amount in different location during the weekend though 🙂

@Dimitrios-Kanellopoulos
I guess there’s something we never found before about this issue. So, maybe it’s something new/recent.

Today, I started a new trekking activity navigating a route already on watch and selected before starting. At a certain point I’ve seen that the graph was frozen. What a mystery!

While on the summit I decided to switch to a brand new route, so i created it, transferred it to the watch, did the BC trick and resumed the activity.
The graph was working as expected, but when my pal wanted to extend a bit the trip, we took a detour and at that point I’ve got the usual “off route” message and after a bit I’ve noticed that the graph froze.

So I reminded that at the beginning we took a shortcut so we went “off route” for a while.

My suspicion is that, if we stay for some time “off route” the altitude graph get stuck even if we go back on track.
The BC trick obviously works

@Fenr1r I never tried other GPS in the parking lot. I wasn’t used to running there. I only did it recently because of the Corona Virus.

But it’s an interesting thing to try!

Same model, same issue! Any bug fix available?

@DirkM ☹ ok, than - of course - that can’t be the reason at all …

@TELE-HO
I just mean “feeling chart” 😄

I think I will be leaving the Zwift Runpod as a footpod. Accuracy today was even better. Watch reported 3.74 miles on my run today. Typically I measure 3.70 to 3.73.

One both good and bad detail about my run today was (the bad first) the GPS reception cut out on my spartan halfway through. Not sure of the cause, but it never came back during the run. However (the good part) the zwift footpod carried on, pace/distances constantly refreshed and were typically what I expect to see. The only thing I’m missing in strava is the full GPS track.

One other note, I updated the firmware for the Runpod using the zwift app on my iPad. Not sure if that made a difference yet for better or worse.

@Shrek3k thanks for the info!

@lord_ru_1979 Have you tried it on a different laptop? I have had issues with one of my PCs and found a different HW solved it.

@ze-stuart yup afaik

@oli_ver I agree 🙂

This is happening with my Spartan Sport with the new Polar Verity Sense. The wait it out workaround works, but would very much like to have this fixed. I now the Spartan line is no longer being enhanced and I’m fine with that, but please release a patch for this one issue.

Well, as my previous post says I tried all ways now and it’s no good, the run is just LOST cannot save the poor thing.

Sadly this is now becoming very annoying as due COVID I’m doing a challenge with friends and this will now NOT appear on Strava.

@Viking1291 we are all here to learn from our heroes, don’t worry 🙂

@Egika I get your point and yes that makes sense, I’m just not sure if they took it far enough to solve the problem. Making sure erroneous data isn’t in the users experience is a worthwhile effort, however giving them reasonable proxies (something is better than nothing) might be more worthwhile.

Moreover, the only time that you would use these battery modes would presumably be longer efforts where less GPS accuracy doesn’t matter as much, as in all day hikes at a slow rate …but those activities if in mountains would be scenarios in which having a little error that accumulates over hours for ascent values would be preferred to 0m elevation gain reported which over a day is likely to be more ‘wrong’ than the error-ridden ascent value. In either case one can correct these in Strava or Runalyze or other 3rd party sites after the fact so I’m not concerned with the after the fact, just the day-of utility of the measure. There could also be something to 5 second or 10 second full power rate versus 1 sec low power rate if power setting is more impactful to vertical accuracy than rate of connection, although having not had a watch that had those I don’t know if those had any better (if more coarse) ascent values possible.

Those are just my thoughts on it, I bought the watch as a running/hiking watch so I guess I should have done more research before purchase when the longer duration battery settings come with such heavy caveats…

@fritzbt2013 That’s exactly right!

@Yannis-Belouris
Did you already open a ticket ?

I suppose this has also something to do to high cal evaluation during activity

By the way, re-flashing didn’t solved the issue.

@Brad_Olwin I have done similar races with my Spartans. It was ok until this Saturday with “only” 6 hours of running:) So it definitely isn’t something that would bother me all the time. Except the previous FW Spartan issue (when the watch was randomly showing “arrow of death”) I’ve had no big problems with my watch. I love them and use them every day. So it really surprised me, when it randomly restarted during the race. But maybe it won’t happen again. And maybe the new FW will fix that. Who knows 🙂

@Brad_Olwin said in Training program/planned moves:

@Roox911 said in Training program/planned moves:

@sartoric
got it to work with the mc app (found it on the web)

Basically you have to unpair it from SA and pair with MCapp - then let it sync the planned training days - then reverse the pairing/un-pairing.

Works perfectly (well… i mean its cludgy and unnecessarily silly, but it works!)

Currently have about 2 months of my training plan synced… will probably finish up till end of summer after dinner tonight.

edit: well, ok… its not seamless, turns out i lost all of my custom exercises, which is a bit of a pain in the ass. Guess i’ll have to fix that tonight as well.

Every time you sync with MC app you will lose the custom sport modes in SA. I simply do not customize in SA. The routes work just fine.

Well not entirelly true. I use Movescount (WEB) and I use SA. I have custom sport modes and heart rate graph on some sports (from SA). I sync watch with cable to movescount (routes, moves, settings) and I sync watch wirellesly with SA
(moves only not setting and routes). Works perfect, jou just need 20 minutes to configure this settings. One note, I if have to edit sport modes i need to fully connect to SA and disconect from Movescount, than forget pairing with SA and connect to movescount again and partially connect to SA (no sport customization, only connection)

@chaichaichai
Are you sure ?
https://www.suunto.com/en-gb/Products/Heart-Rate-Belts/suunto-smart-heart-rate-belt/

Maybe it’s temporarily unavailable somewhere,

@Dimitrios-Kanellopoulos said in Suunto Spartan Sport GPS drift:

https://electronics.stackexchange.com/questions/130256/sgee-vs-cgee-vs-a-gps

Very interesting.

Fortunately the battery drained faster than I expected and after charging the watch is back to normal operation.
I don’t know whether it was the cause but I ended up deleting movescount app from my mobile, though I never had any problem with using both…