@Cuba1hr @Dimitrios-Kanellopoulos I think Polar simply looks at your heart rate distribution and uses established equations on fat/carbs as primary fuel source based on intensity.

The fun part is: if you rely on default heart rate zones set by Polar or yet another age-based formula, this number is probably off, and by a lot. You need to be below your aerobic threshold to use fat as a primary fuel and in a steady state activity. Go harder than necessary, or in an interval stop-go fashion, and you’ll be relying on alactic or anaerobic pathways.

Check out Uphill Athlete. They have multiple ways to test for aerobic and anaerobic thresholds. Once you have these, set your Suunto 9 heart rate zones based on their recommendation and do long runs or bike sessions (working up to 90-120 minutes a pop, longer sessions being really good at forcing your body to rely on fats and conserve carbs) below your aerobic threshold. That would build up an aerobic base and force all sorts of metabolism enhancing adaptations.

Between consistent exercise and clean, reasonable diet, you’d be in decent shape in no time.

@sky-runner I think there similar points raised before and suunto probably knows about it. Let’s see what the future will unfold!

@hel790 said in ANGEL MODE... When your watch detect you are lost and are out of route:

direct path back to route

Hello hell790, direct path back to route was my very very fist idea when I wrote this post as I was like you thinking that it will allow me to retreive the road I put on Komoot.

But …

It is a FALSE GOOD idea.

Why ?

it is precisely in a direct pass that you risk to need a machete with you, nothing garantee you that this direct pass there is no jungle, no crocodile, or no crevasses or hard cliff.

On purpose, when you enter into a “Angel mode” the idea is not to be driven by the noose by the watch and walk into a place that you may have no idea which difficulties you will face (remember you are lost) but in reverse to allow you to position your self very precisely.

If you really walk in “engaged” situation you will bring with you an IGN Topo 25 map, so the top most important is to allow you to locate yourself.

This is why having the directions to the 2 soles fix points that both you and the watch knows should be considered and they are the BEGIN and the END.

There is another interest to show the BEGIN, it may happen (it was my case) that you are even not on the track straight from the beginning, so having the capacity to join the begining of your trip is not useless.

The direct path back to route will never allow you to locate yourself on a map simply because this famous nearest point totally depends where you are, so it"s a moving target.

@freeheeler Hello, I was on a tour today and the values ​​were right (reset the clock to the factory settings), there was a deviation of 10m on the first summit, 1m on the second and 5m on the third !! Thank you for your support! Best regards, Rony

@dimitrios-kanellopoulos

so just to keep you updated. Ran today with the belt and TP as suunto+ and the Vo2 is working just fine. I guess my bad OHR readings were the result of missing Vo2. Ever since I’ve been using belt all is working flawlessly. Thanks. I will try OHR on another run and if something changes will inform. Take care!

@vimegar
sorry… GPS only… this also effects FusedAlti of course

@luís-pinto 😂

@pikeviewer thanks for the info, I might downgrade mine on the weekend.
Unfortunately “snap to route” is a nice function …

I’ve preformed hard reset of the watch and now it’s working normally. Duuno why it happened in the first place and I hope it won’t repeat.
Thanks all for suggestions.

@daveve
did you receive your grit x pro already?
how’s your impression?

@isazi oops…wrong thread.
Was meant for the SV hotfix thread

@nassosc I am transferring to Movescount by RunGap on iOS so I am not directly sending data to MC but via a 3rd party.

Done it
Emailed suunto

The more research I did when deciding to get a running/hiking watch, the more it pushed me in the direction of deliberately getting one without built-in HR. My dainty and hairy wrists ultimately tilted me to the Spartan Ultra, and I don’t regret that decision at all. There was no sense for me to spring for an extra feature that would probably never work well on my wrist.

Ironically I’ve ended up using an optical HR monitor for workouts, and I have total trust in it now, but it’s worn against my upper arm on an elastic band. Optical HR can be very reliable; the problem is the wrist is pretty much the worst place to put a monitor, but that’s where watches have to be worn.

@zadow
And i’m happy for you too. If it was under warranty in January, sure, then the watch is under warranty now as well.

And also great for spare watch and especially for your training. I have one of the 1406 jewels too and I love it, it’s a beautiful watch!

@freeheeler I think that it will have to be done, but it is not easy. Maybe at first the log will be able to tell something?

This is the move planning request: https://forum.suunto.com/topic/164/planning-moves

@Dimitrios-Kanellopoulos Just a small update/test after the latest firmware update:

I exported the FIT files of two moves from Runalyze and used GPXSee to analyze the fit files. The tool has 2 ways to calculate the speed: “By distance/time” or “Recorded by device”

Unfortunately the speed with GPS only didn’t improved very much after the latest firmware update if I calculate the speed by distance/time:
1.png

If I calculate the speed by “Recorded by device” it started to look a bit better:
2.png

The move with GPS+GLONASS however looks much cleaner if the speed is recorded by distance/time. Especially the second half
3.png

Is this because of a better/stronger signal if I combine GPS+GLONASS?

So it looks like the firmware update solved the speed wobble a little bit, but not quite like the Ambit 3 Peak. The speed spikes are also visible on the watch screen during the move, so it isn’t only the FIT file.

Before that I had the default value of 60 bpm. Above are some pictures what I got then for resources.

@sky-runner I can’t recall which version it was exactly but this problem was fixed a while ago. If I remember correctly the device does not do a full sync everytime now.