@margusl The MC download link finally reached my mailbox today

@margusl I managed to sync! I sent details to chat.

@pavel-samokha thanks for investigation now it is correct(same) in profile and diary

@andrasveres I can confirm, it works now as expected, many thanks!

@markytarky Well at least you can use 1 Suunto plus feature and 1 navigation feature at the same time.

@vagabondelvis RunGap on iOS is your best friend

@starrysky , PHP is not quite my thing and it has been a while, but I’d start by checking phpinfo() to see if sqlite module is loaded and if it’s not, you probably need to edit your php.ini Is there a particular problem you are trying to solve with mocking a service?

@pavel-samokha Ok, it was just a side-by-side comparison. The settings are there in Movescount web interface even without a bike pod. So maybe SuuntoLink is being a bit smarter by only offering this when paired. I did wonder if these were simply forgotten about for the Ambit. Similarly for “Automatic bike power calibration” and “Training Program”. All other settings seem to be present as far as I can see.

GPX files from Suunto App are quite heavily processed, some datapoints are dropped while others are added through interpolation, so when calculating speed from resulting GPX-points, that level of noise is kind of expected. Though what I find interesting and bit unexpected is that level of granularity - how points are gathered around 3-2 values and forming vertical parallel lines on a chart. The way you calculate speed makes this more prominent - time difference between most points is 1 s, so if speed is calculated only by considering time & distance between current and previous point, it’s basically a dataset of distance differences between points. When calculating speed at point n through points n-1 and n+1, output would be smoother and granularity does not pop out that much, though it’s still there. Had to see if this is something specific for GPX-generator used by SuuntoApp / SportsTracker, but GPX from 9P was only one with such a strong granularity. Nothing to worry about ofc, just interestingaf and I’m sure it’s more visible in GPX than FIT exports. Your gpx with few different takes on calculating speed, speed_between_prev is basically same approach that you took, seg_get_speed uses n-1 & n+1 for speed at n and and speed_rollin_15_mean is centered rolling average over 15 points: [image: 1640433297400-71745508-45ff-411c-b179-5c5f9f6260d5-image.png] vs my F6 (ice skating, lot of stops, “smart” recording; gpx from Suunto App): [image: 1640433434891-4101a754-e70b-4ae7-8efc-5a0155e36d70-image.png] vs Ambit3P (bike commute, note those 40+ km/h artefacts; gpx from Suunto App ) : [image: 1640433538020-abecdbd8-0d6f-43ef-91e5-f1834e509b1c-image.png] vs same A3P activity but taking speed directly from fit-file (and x is point index instead of time): [image: 1640433728322-2ebf689c-aa29-4bc6-93e7-268aeec2efae-image.png] Notebook, works in Colab - https://gist.github.com/marguslt/166fb2856bf1a16b279f4c89c14b0fbf If I’d be interested in “raw” data, I’d certainly look for ways getting closer to dataset generated by the watch itself. So either a fit-export or perhaps a json data that’s used as an input for SuuntoApp service and stored at <internal storage>/Android/data/com.stt.suunto/files/smlzip/ on your phone. Any relatively recent installation of gpsbabel should handle fit 2.0 just fine, at least 1.7.0 works or me with SA fit-files and it was released more than a year ago. Though for up to date reference tools one should head to https://developer.garmin.com/fit/download/ , SDK includes FitCSVTool.jar for converting fit to csv. And there are at least 2 perl modules for fit with at least some userbase. But why aren’t those in cpan, I have no idea nor interest to find out. Though popularity curve for the language during past 10-15 20 years might have some role in this …

@pavel-samokha Thank for the offer! I am now in contact with the American support (started by the chat, now by mail). They have not been able to fix the problem yet, but they are on it. I’ll post here when they have a solution.

@juancarlos700591 we are not sure about that https://forum.suunto.com/topic/5298/ambit-apps-showdown/34

@peter-juvan , POIs and routes are included in Data Export - https://www.movescount.com/settings#export . It was rather slow when I used it last time about a month ago, took days (if not week+) to get the download link, but I’m sure you’ll receive it eventually. If you need those right now and would rather leave hacky ways aside (a’la https://gist.github.com/marguslt/4ad715ae43475cd90031c29f9ff1f039 , which should still work), there’s also a chrome extension for MC POIs - https://chrome.google.com/webstore/detail/movescount-helper/cebfemegbnobfibklpbbkaiblcmjgebf

@chris49 , mine are syncing fine. You are using Suuntolink for that, right? You can create new routes and POIs for Ambit (1,2,3) and Traverse watches with the help of the Suunto app and sync them to your watch via SuuntoLink. https://www.suunto.com/en-gb/Support/faq-articles/transition/how-do-i-sync-routes-and-pois-to-the-watch-for-ambit-123-and-traverse/

@wanderinghead , yes it’s a meta-data. There are cases where it can be still useful as it’s also a main source for notes and tags. For example if one chooses to forward all FIT activities exported from Movescount to some other service and that service happens to have a (semi)open API, it’s possible to transfer at least some of that extra content.

@brad_olwin Thanks to you and @isazi, using SuuntoLink worked perfectly. In fact, it was already on my PC, so once it had updated itself the latest moves were transferred and appear on my app. And yes, the USB lead is the same as the one recommended for Ambit. A bit pricey at £25 to be honest, but currently half price. https://www.suunto.com/en-gb/Products/Other-accessories/USB-Power-Cable/ Much appreciated.