Tutaj garminowski poradnik jak zakladac i dbac o czujnik pomaru.
Oraz ostatnie zdjecie pokazuje test na biezni z uzyciem GPS, glonass, zapisu co 1s i oszczednego zapisu. (To nie ja wykonalem tych pomiarow)
Opis jest taki.
GPS modes: GLONASS "ON" or "OFF"? UltraTrac: use or not?
Data recording: "Smart" or "Every second"?
Attached image will tell you. But consider, that those images slightly "boosted", in real life you will have wiggly track in most cases (trees, buildings, shaking wrist, watch not sighting whole sky! :P )
- try to use glonass more often. Yes, it will eat more battery.
- use "smart" in noisy/hard places. Use "1s" for detailed track. I am using always 1s/glonass ON.
- use UltraTrac only with footpods or just for "sightseeing logging", you probably won't get normal speed/distance from that mode.
░░ DATA RECORDING:
First: "Smart/1s" data recording is not related to GPS. That is the way watch post-process data points, simplifies/averages and softens (or not: i.e. tries to be smart
GPS still records "Every second" or "UltraTrac", and then softened (simplified) in "Smart" mode. It's about simplifying and recording less track points where watch thinks it should (it just in real gives bigger segments, and less data points). That makes smaller size for recorded tracks (not a modern problem, for most).
Will track be more accurate or less accurate with Smart/1s? No, not more accurate / nor less accurate. But in better GPS coverage in 1s you will have better resolution for real track, and in worse GPS coverage you will have more wiggling track in 1s mode (i.e. errors won't be softened by "smart").
Q> Does this affect 24/7 whr data also?
no, this only about recording ACTIVITIES (even non-gps, might be affected, but this need to be checked by someone
On my tests in most cases GPS+GLONASS gave better results for Fenix 3, I will improve this experience with Fenix 5.
more info about GLONASS:
Let's say "its presence increases probability to have more better track". But only _probability_.
With it you just will have more satellites on sky, so watch may choose those which signal stronger, that will help in harder areas or when GPS satellite closer to horizon (so gives bigger error).
There opposite "knowledge" (it is not!) by some rumors in style "I heard" and unprofessional analysis by some owners, who run one bad GPS day with GLONASS and another good GPS day without GLONASS, what make them think so that was glonass error (read this too: https://en.wikipedia.org/wiki/Apophenia
+ links below).
Also, some old obsolete articles about glonass errors from those years given as "modern advices" (I saw 2008 article, which was put as explanation why adding glonass is bad).
And more: some watch models / other brands have own GLONASS algorithm calculation errors, which give shifts, but no need to spread those issues on all GPS+GLONASS pair.
And more: investing in complicated algorithms of combining those methods by major companies and chipset developers without visible improvement: why?!
Watch turns on GPS once per two minutes for some time, tracks some seconds, and hibernates with GPS.
This is very dirty track mode, not recommended if you need SPEED or DISTANCE to be measured (not just "where you was + to return").
But together with footpod (and STRYD as most accurate device for speed/distance for now) you can record dirty tracks in UltraTrac, but have real distance/speed from footpod.
I will do tests on Fenix 5: we have gyroscope in F5 so I am also curious how it will look comparable to that "X? seconds each 2 minutes recording", which was performed by Fenix 3.
TRICK not related to UltraTrac: keep in mind that you can select separately to have instant speed/pace and/or distance from footpod.
Wysłane z mojego SM-T113 .