@pavelsamokha
Ok, i didn’t know, good thing to know.
@david-hirst ,
would you test it, and confirm if support accept to do this ?

@TELE-HO Don’t think either of those would be much of a concern for me personally, thanks for the heads up though

… no need to upgrade the watch 🙂

I used to see the trend indicator when I was charging my Ambit3 Run too, however I considered as a software bug because I saw dual time indicator too even if it wasn’t turned on for me.

@andrasveres it seems, that new strap helped, I made a exercise and HR didn’t jump out of the range I think is OK, thank you for your advice
@isazi I can confirm, that new belt arrived with white area around the connector

@Tom-Z , are you sure it happened after watch firmware update and it’s not related to MC app version or moving to Suunto App?

Latest FW is 2.4.17, released on 2017-06-26, one before was 2.4.1, released on 2016-12-01 . I wouldn’t be so sure if anything older than those two would even work with latest MC app or current SA, even stepping down to 2.4.1 might introduce some issues with mobile apps (though it does work with Suuntolink, tested). And downgrading to anything older would also mean loosing of quite a few features - https://moveslink.static.movescount.com/release_notes/SuuntoAmbit3_ReleaseNotes.html

But technically there’s no problem forcing a FW downgrade itself. Just be ready for update notifications in Suuntolink & Moveslink2 and possibly in mobile apps as well.
a51335e1-7a24-4a0e-8159-78d405f987a6-image.png 7292e169-6b68-421f-9354-2bcdc9e2f203-image.png

Here’s a generic URL for A3P FW files:
https://uiservices.movescount.com/devices/Emu/69.4.17414/<rev>/binary?appkey=<appkey>

Replace <rev> with one from release notes (“2.4.17”,“2.4.1”, “2.2.16”, …) , you also need to provide required <appkey> yourself. If you are using Suuntolink on Windows, you’ll find it in %appdata%\Suuntolink\suuntoapp.log . Or look for production.json at Suuntolink installation folder.

Suuntolink uses a certain naming convention for FW files when it downloads those (e.g. uiservices.movescount.com-Emu-69.4.17414-2.4.17.sfi ), but it doesn’t seem to really matter. Once you have the file you just drag-n-drop it onto drop area somewhere in lower portion of Suuntolink window, you’ll notice when you’ve found it. And as always, use it at your own risk, yada yada yada …

@Mi_chael said in Ambit 3 vs Garmin Edge 530:

@André-Faria

Sympa la ballade…

😉

Oui très bien 😃
In fact, I just moved this year to Lille, and I am discovering around.

@Dimitrios-Kanellopoulos thanks

It seems it’s now back as it used to be.
2020-12-02.png

@bartdev today evening it works :-).

@pavel-samokha
Thank You for Your help. See my reply to Egika.

@saketo-nemo grazie mille per il chiarimento

@neptunejason I had a similar Problem. Here is my solution: https://forum.suunto.com/topic/4533/movescount-app-crashes-after-move-sync
The lesson I learned is, that for big moves (>5h) I use the cable to sync the moves.

@andré-faria yes, with the new suunto link 3.4.5 now works. just found out myself thanks to this forum

@Luis-Silva you could also export the FIT file from SA and import it in quantified-self to check if there is something wrong with how the file is generated, or is just Strava.

@Chris-Wittwer , navigation works fine when recording is paused.
I had somewhat similar situation this weekend, used my A3P for nav during a race and had to glance at it quite often, at some point noticed it was on pause. Didn’t loose more than 15 minutes out of 30+ hours, but it still reminded me to lock those buttons - for me it’s really easy to accidentally hit a pause button when riding with gloves.

@isazi said in Sync your moves. Memory almost full:

@awinkel there is a circular buffer, so space will be reclaimed when needed. I don’t have an ambit, so let’s wait for ambit users to chime in, but I’m pretty confident this is the case.

Is there going to be a firmware update or other way to suppress this annoying, unnecessarily alarming message? The problem is that if you DO NOT sync to the Suunto App, the message IS meaningful, but there is no way for the user to differentiate between real and false-positive messages!

@margusl good to know. I always thought PTE is a function of time in HR zones and activity class.

@mlakis That’s not the issue in my case at least. I’m talking about cycling through the navigation screens using the lower left button. The behaviour of mine is identical to that in the query, including the double button press. It’s as if the watch has moved to the next screen but not actually displayed it.

@jurjen agreed, but have to remember that recovery doesn’t necessarily mean stop don’t do any more, it just means take it easy, as can still do recovery runs etc, trick is just not putting out too much effort.

I connected another watch the same model and it works. The question is, can I have two hours connected at a time, according to the system of using one once and another the next? This goes smoothly on the cable. I wouldn’t want to lie for an hour, but to use both alternately.

Ouch, apparently that now did the trick! Stupid me…
Many thanks for your help!

Cheers, Sven

In some post someone has said that the 4 first digits of the serial number are the year and week of production, I mean if the serial number is 1734XXXXXX… means that was produced the week 34 of 2017. Maybe you should keep the newer.

Okay, so out of nowhere it started to show notifs as I expected. Only change I’ve made since last try, I used Clear Data option in service mode and that’s it.