Smart sensor belt does not seem to pick up correct heart rate or sometimes nothing at all. Belt is about a year old. Is there a shelf life for these? The belt has been washed, I wet the patches before use and new battery in the sensor itself but still not working
It is the one with movesense area in black or grey?
On your later points, see @sartoric’s directions but as to on-board Topographic map - nope.
And FWIW, I also use the thing for hiking and would also like to share your beliefs about FusedAlti but it hasn’t been my experience (on hills) that it’s much better than the Baro on the old Vector. Weather change might require the Vector to be manually corrected (of course) while, regardless of weather, the GPS component of FusedAlti could introduce its own errors, overriding manual correction.
If your search yields simple, useful answers to your questions, please drop 'em back here and thanks in advance for the gleaning.
@lollo1982 Suunto will have a solution for Ambit owners as they have stated in their communication and as @TELE-HO stated, there is a ton of information on this. I would continue to use MC until it is shut down.
@isazi thank you very, very much - it looks like that has worked! It’s nothing like as straightforward as Garmin but hopefully I’ve got there in the end. The test will be on the openwater swim tomorrow!
I had the same issues with a 4iiii powermeter (left side only). I wrote an app in movescount which multiplies the bike power by 0.5 --> “RESULT = SUUNTO_BIKE_POWER_1 * 0.5;”. Unfortunately you get the original power values (so the doubled ones) if you export fit-files to e.g. trainingpeaks or golden cheetah. My solution was buying a bike head unit to get the correct values for the analysis.
Maybe you can configure half of the crank length with the app for the powermeter?
Thanks for the feedback. I will definitely look at the GPS Track Editor. I had the GPS Accuracy set to OK which meant there were times when it wasn’t picking up signalScreen Shot 2020-08-23 at 8.57.46 AM.png . The track looks very similar to what we did but I suspect it missed most of the corners and ups and downs especially where there wasn’t good GPS signal. Didn’t think it would miss that much but the difference was around 15km from what others who have done the loop before. I wasn’t sure if there was a way to go back and correct this on Suunto or Movescount. I will definitely not be running this again for a while so if I can’t edit it no big deal. As you said, the most important thing is that we know we did it. 🙂 Thanks again for your comments.
I usually run with a frined that uses an Ambit 3 Run and I use the S9B (GPS only), in my opinion and comparing both watches I found the following:
In trail runs (using custom trail running sport mode), with around 300 m ascent very 10 km and some trees the Ambit 3 has most of the times a perfect track, the S9B has a very good track but not as good as the A3 and falls short on distance comparing the A3. Examples: S9B: 21.12 km - A3: 21.35 / S9B: 13 km - A3: 13.10 / S9B: 11.02 km - A3: 11.12 km
In flat runs (using custom running mode), here the A3 has teh same or falls short on distance comparing with the S9B, tracks are quite similar. Examples: S9B: 11.43 km - A3: 11.31 km / S9B: 11.32 km - A3: 11.30 km
I do not know if there is any diference in the sports mode that can affect this, but what I explain I have noticed several times.