recently I discovered some strange “issues” with the HR tracking on my Ambit 3 Peak. I uploaded an activity on the Movescount app what was than synchronised with the Suunto app. Afterwards later my bluetooth connection was left on, and I opened the Suunto app and it have synchronised with the watch as well. The move was duplicately in my history. I checked both, and there was a completely different HR graph, with a completely different max and mins, and HR zones although the average was the same. The first one was from the movescount and the second from the Suunto app. The max HR with 212bmp is obviously a wrong measurement, in the Suunto app, but its a bit strange that from the same measuremnts the two applications read differently the data.
Do you have any explanation for this? Have somebody had a same issue?
Thanks in advance,
Well, yes, but the category should be self explanatory
D’oh. Of course! Momentary idiocy attack here. Apologies.
On the other … the OP’s title was pretty precisely about bearing rather than heading in compass degrees, hence the workaround process, so I wasn’t quite sure what you meant by “it” being visible in compass mode.
but it’s strange that the third generation watch is less accurate than the first
It’s the missing antenna bump.
I wondered if that was why. Still OK for most purposes, my sport doesn’t allow GPS navigation (rightly in my view - route finding and navigation is part of the skill set) so the record is accurate enough for what I need.
Hi, you should sync your watch to MC via the moveslink2 link (cable to PC) then control ALL your watch functions through MC, as people have said linking MC to ST (sport tracker) is the best option, well works fine for me.
In MC there is sports already for TELEMARK SKIING / SKI TOURING if you want something different you can copy one of those and edit to suite what you want.
I made a mistake because I did not replace Moveslink2. This time I repeated the whole process of changes and tested the operation, the matter also works with the transfer to Strava. It will take me a while to get used to it.
Thanks for the help that helped me a lot.
@pavel-samokha Thanks a lot Pavel, following the instructions you sent me everything worked for me I could configure my Ambit3 Sport perfectly.
Thanks @isazi , @cosmecosta , @Brad_Olwin for your time and support as well. Have a nice weekend and enjoy.
@ElTron-ElTron , everyone has different priorities (just look at the post above yours), I have only few apps that are built for logging, all the rest are for real-time guidance. You could just keep using Movescount as long as its data import & analysis are still available. And once the Move upload gets disabled, you still have an option to fall back to Moveslink2 cable sync & SML files and parse those yourself to plot app data. Moveslink2 is happy generate those SMLs for you while working offline, with no Movescount connectivity. Or look into Openambit, there now seems to be Windows support.
Of course trashing your watch is an option like any other, from Suunto’s point of view this is almost the best thing you could do - by unplugging the unit from their ecosystem for good (not selling it / passing it on), you release small yet measurable amount of their resources.
Just saying that I personally wouldn’t bet on anything Ambit-specific to be added into Suunto App. I’m happy to change my stance on this once there’s some progress with much simpler and more generic issues like data from powermeters. Oh heck, just any visible change towards Ambits might do, last one was over 16 months ago.
So it’s either adapting or moving on.
BTW, I was dead-serious on SML-files, there’s something oddly satisfying about processing those, especially when going through data that’s normally not sent out to MC & SA services.
Ok, thanks. I did know Openambit yet but I was thinking that they only gave support for Linux user. Perhaps if now there also for Windows I will take a look.
I know were slm flies are located. They are at:
The difficult thing is how to put in a readable form all the information contained in these files.
Another thing is that the program given by GitHub for Openambit are not compiled and I don’t know how to obtain an executable program.
Thanks for all feedback. Useful info re the ‘off route’ tolerance. I’ve realised, however that the repeated beeping is linked to the ‘better HR zones’ app I have installed on the watch. This gives double beeps on the threshold of HR zones, so if I’m hovering between zone 1 and 2, for example, it beeps repeatedly as I cross in and out of each zone. Case closed!
@cosmecosta Thanks for your reply. Even though it’s considerably cheaper than the Polar OH1, I’ve decided not to faff about anymore with the Coospo and it’s been returned for credit. I’m biting the bullet and splashing out £££ on an OH1 as, thanks to you, I now know it works with Ambit 3 Peak.🤞👍
@margusl thank you. I will try the converter. Are there any Suunto reps that frequent here? I’ve tried to email suunto but I only see phone numbers. I’ve called and the reps that answer supposedly take notes and pass on the request to be able to plot and synch with the app, but I’m not holding my breath.
please also check, you’ve got 2 different tone settings, one is for buttons, the other one is for notification.
If you think it is broken, you can ask Suunto service for support. They are fast and offer a great service.
You can also check if it is still within warranty. ✊
Just to add some references from the manual for clarity: The “Find back” feature basically uses your starting point as POI and navigates to it the same way as used for POIs generally. So this might give you some clue:
Those marks at the top are indeed meant to be used together with the arrow as a sight on a compass or a gunsight on a gun = when the arrow is in the middle of those marks, the watch points exactly towards the starting point (or POI).