@freenico Looking at these GPS tracks, it appears like the apple software draws a smooth best-fit curve through the recorded nodes whereas Suunto simply shows the recorded nodes and connects them with straight lines. One isn’t necessarily better than the other, it is just that the smooth line is prettier whereas I actually appreciate seeing the actual nodes (to get an idea of how accurate the recording is).
As for altitude sensor, I’ve used a Spartan but I think it is different (the one with the external GPS sensor, I think it is called “sport” or “trainer” or something) and it doesn’t have an altitude sensor. My Ambit 3 Peak has it, Suunto 9 has it but other than that? I though the other ones just derive the altitude by GPS data and maybe by using acceleration data. But maybe someone else can comfirm.
Edit: This said, some Spartan nodes clearly are off of course, with some of them being outside the water. There was a discussion elsewhere as someone had also a coarse resolution GPS track when swimming and even though mine was a bit coarse, it wasn’t as bad as his. We were both using the (regular) Suunto 5. Chances are it was because of swimming style. I was crawling, he was doing a breast stroke. So that might matter too, swimming style. But if you look up that discussion (which I won’t repeat here) GPS just isn’t good under water so getting a good recording is also a matter of luck. Same goes for GPS in the mountains or in a dense city. Maybe there are ways to tweak things to get better results. That’s what experts are doing with echo (to see tissue inside your body) or sonar (to scan under water). That’s a skill on its own. But maybe it just can’t be done with GPS because you’re not transmitting the signal hence can’t play with frequencies etc. Only advice I’ve seen is, if you want better GPS reception then you need to keep the sensor out of the water. So attach it to a buoy or something.
I just saw this thread now and want to second the “clean the living daylights outta that thing” posts on here.
I had a lot of problems with dodgy HR data from the Suunto HR belt and took the suggestions here: http://www.natharward.com/heart-rate-monitor-not-working/ and took them up a notch a few weeks ago. Since then I’ve had zero problems anymore.
I pop out the sensor and swab the metal posts of the sensor and the spots on the HR strap where it snaps into with a Q-tip and rubbing alcohol after every single time I use it. It only takes a few seconds. When I wet the belt before putting it on, I also squirt a drop of dish detergent on each electrode and scrub them good with my fingertip, then rinse them out. That only adds an extra couple seconds to wetting the strap, too.
Maybe it’s excessive, but I’ve abruptly gone from cursing that thing to no problems at all ever since I started doing that. Keep those ports, connectors and electrodes clean every time.
One other thing I do (I don’t know if it makes a difference or not). When I’m on the start exercise screen on my watch and it turns the heart icon green and starts displaying numbers, I give it 10 or so seconds before actually pressing start.
I still use my 2016 belt due to the above article.
Ok, I think I might know what the problem is. I can’t figure out the math, but I think it’s similar to how MyFitnesspal counts calories for steps taken along with your workout calories (which includes some of those steps taken). Basically it counts double calories. Anyone else thinks it might do this?
@Dimitrios-Kanellopoulos any update on calibration for the treadmill? I did a run today with my Suunto 9 baro on Treadmill activity. Steady state at 12k/h (5:00min/km pace).
After 55min, my watch read total distance of 15km and a 3:54’ pace. I never cranked the treadmill above 12km/h.
Any updates on a way to manually calibrate distance on the treadmill?
Spartan measure SLP correctly only if you entre your reference altitude under outdoor and also make sure that Auto adjust latitude is working by default to keep track of the changes in Altitude. I can confirm that my Spartan Hr Baro is always reporting 2hPa higher than my Traverse and local weather station. So a discrepancy of 2hPa is acceptable due probably the different sensors used in different watches however, anything below -/+ 5 hPa I would consider sending the watch away for fixing. I hope this helps
@slash 🙂 I use the quick release pins on straps designed for them, otherwise, if I like a band that is the non-quick release, say ostrich leather, or carbon fiber, something that’s not offered in quick release, I have the tools to remove the band if necessary. Just makes it easier to change more bands, is all. Either way, I’m good.
The altitude calibration from the GPS is never correct near by sea level. I am now actually at sea level for 1 mont and most devices report GPS altitude of -7.
To obtain the altitude check also some phone app about what GPS reports.
When you run the watch uses a feature called fused alti that calibrates constantly the altitude according to GPS reference combined with the readings of the pressure sensor.
When you start a move at the first 10 mins it tries to calibrate the altitude of the starting point. Eg like auto calibrating it your self , but actuality happening while running.
Thus you can have a different end point.
Also keep in mind the pressure sensor can be offset by many factors that’s why fused alti is there. To “peek” also from another altitude source.
Regarding the different gains , the barometric pressure change can affect it, however , also the route can.
That is why Suunto count ascent , at a -+3m threshold.
That means that if you don’t climb 3m in some minutes and you only climb 2 then it does not count.
So for example of you were runninh stairs up, and you did 2 stairs of 1m each it will not count. But if you did 1step again after doing the steps it would. This exists there to reduce noise, eg even arm movement that passes 1m etc etc.
I hope it helps.
PS to test your sensor , try to rub behind the watch , eg increase temp and see if altitude changes. Or if you are at the sea place , wear the watch , leave it aside, wear it again and you should have always the same altitude. That’s is how I detect those so far.
Hello and thank you for your explanation. I’m going to think about it.
Thanks, @Andriy-Zarteskyy , but not of those steps solves the issue at all. It still remains there. The only difference is that mine (my TWO watches, both SST) has the same issue no matter what you do. In my case, if I connect at 40% and watch changes battery to 12% (this really happends), it does not come back to 40% even after reboot the watch.
I know this is not my issue, and I’m pretty sure it’s a SST general issue with this firmware, but I don’t see a solution and months pass…