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.
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:
If I calculate the speed by “Recorded by device” it started to look a bit better:
The move with GPS+GLONASS however looks much cleaner if the speed is recorded by distance/time. Especially the second half
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.
For me, this is not a new function, but rather a correction/improvement.
The Suunto are able to be connect at sensor (power, speed, …), and sensors of indoor trainer are not detected. But detected by others (Garmin, Polar, Zwift, …).
@Bulkan I also use Zwift to do my training session, but not sure to do it all the time due to other simulator and also the price. I can also use Wahoo platform for one or two session as example.
I send data (90% of my activities) directly in Strava platform.
But at end the real and full tracking is done by Suunto.
I use the watch a lot, and navigate with waypoints normally for bike rides around 200k, shorter ones I know where I am going so don’t normally use a route and the atch is perfect.
Just these two walks one reversing a track and crashed at second waypoint, the other following it as plotted at second waypoint, the waypoints were around a 2km from each other. The only other thing I can think of that I had done different to normal was not use the top GPS tracking.
I’ll try and plot another route to the same spot and see if I can reproduce it.
After the Crash on Saturday, I think around 6km into a 42 km walk, after I restarted the watch it navigated perfectly for the remaining distance, and I did leave then return to the route a few times with no issue. This time I used top GPS tracking which was why I mentioned it. By the sounds of it a total coinsidence but both crashes were using the second tier tracking.
@paradize He promised an in-depth review of the Apple Watch 4.
He did all of the previous versions without much fanfare because to this date, Apple Watch remains kind of a marginal player as far as athletic endeavors are concerned. It’s the big boys like Garmin, Suunto, and Polar who get special attention. First look, unboxing, hand on, in-depth…
Also, I suppose the fact that Apple doesn’t send him a device a month or two before the release has something to do with the lack of early articles too 😅
Hey all, I don’t want to create new topic so I’ll write here if you don’t mind.
What if I have 2 different watches and two HR belts, if I pair one belt with one watch and second with second. Is there any option that first watch will read HR from second belt or it cannot happend? I just want to avoid situation that I’ll record HR’s partner