Quick update to let everyone know that (finally!!) fit files from Garmin devices should work properly with ka72.com
Existing uploaded tracks have been marked as unprocessed and will have their stats recalculated when viewed on the track overlay page.
Please let me know if you spot any strange results. Only limited testing has been done so far.
Dylan
That's great, thanks!
I uploaded a few test files which would previously have failed, but can now be processed:
- Garmin Forerunner 255 + APPro app
- Garmin Fenix 7 Pro Sapphire Solar + APPro app
- COROS APEX 2 Pro in speedsurfing mode which records HDOP, sats, etc.
I noticed one slight oddity. The FR 255 track is reporting a max 2 secs which is 3 knots faster than GPSResults + GPS Speedreader. I can't figure out how / why this has happened, so it might be specific to KA-72.
The track is a very light wind wingfoil session - www.ka72.com/Track/t/536108
@decrepit. I could have sworn that I'd checked the non-Doppler results, but it is indeed the reason for this issue.
When setting up the DataField, I get the option to choose between GPS Only, All Systems, All + Multi-Band, Auto Select and Ultra Track.
If I select GPS Only and go for a run, When I look in FIT File Viewer I get this.
mode GPS only.
If I then set the logger up with All + Multi-Bandand go for a run, FIT File Viewer shows this
So we know it's been set up in All + Multi Band.
But do you know what the UltrTrac Trigger is doing, and what are mode 3 and 25?
The Datafield itself cannot see the GNSS information, but the Activity automatically saves it to the FIT file. That is how KA72 is reading the "All +Multiband" setting. This is now operational in KA72.
The Activity type is also recorded in the standard FIT file. So we have all the information needed.
And KA72 has this.
decrepit
Olive Reserve, WA, AU - Tuesday, December 17, 2024
Location Distance Top Speed Olive Reserve, WA, AU 0.05km 5.432 GPS Type Firmware Time Zone Number of Points
Garmin.Fr255Music Full + Multi-band
7.5 57
MeasureResult 2 Second Peak (kts):5.432 5x10 Average (kts):0.765 Top 5 5x10 speeds: (1)3.825 Total Distance (km):0.051
I was curious about what the mode values represent, so I decided to figure out the bit structure. This information is only going to be of interest to very few people, but I have documented what I discovered.
logiqx.github.io/gps-details/devices/garmin/developer/gps-events.html
It is worth noting the difference between native activities and Connect IQ apps. This will almost certainly be QZSS, based on the capabilities of the Airoha and the content of the protocol specification.
Great job K888 decoding that. Once I worked out that 'ALL + Multiband' was 15571. I lost interest and moved on. But it is great to have your documented description.
Thanks.
Great investigation K888. I was not looking forward to having to take the gps out in the field once with each setting to try and determine all the possible values.
Auto select could be a problem. At the moment ka72 will effectively only report the last GPSEvent value, as normally there is only one. If SatIQ throws multiple events that needs some extra thought (though of course we probably want to avoid that mode since it will only use multiband in locations where presumably windsurfing is quite challenging, like in the middle of cities.)
AS far as the GPSTC is concerned, if it isn't locked into "all + Multi-Band" it's an invalid file.
And Dylan, if you need a hand testing different iterations, I'm more than happy to be involved.
Yes I believe the advisory panel is considering allowing certain modern Garmin watches that have multifrequency technology.
For example the Garmin 255.
Initial testing is showing that these modern watches are considerably more accurate than the older models, providing they are set up correctly.