Garmin Vivoactive
15 watchers
Feb 2020
1:59pm, 5 Feb 2020
649 posts
|
Dibble
Thanks G. It's the VA3 I have so been looking through the screens. I guess it's the Auto Lock during Activity that would be best to use. Only disadvantage then seems to be that can't record manual laps. However that always was fiddly (having to double tap screen). |
Feb 2020
2:09pm, 5 Feb 2020
34,090 posts
|
HappyG(rrr)
No, I just lock mine from start. My logic is, if I'm manual lapping, then I'm going quicker, which means I don't have a jacket that hits the screen. Just rain drops don't activate it. It's a flapping sleeve, in my experience. If I am doing a long or easy run, in the peeing rain, I don't care about a few extra seconds at start or end!  G
|
Feb 2020
6:26pm, 5 Feb 2020
124 posts
|
fazmo
Thanks for the replies. G, I think its always short. I set it to GPS + Galileo yesterday. I did the 1st experiment today, 7 laps of 600 ish metre triangle ... manual-lap at the same point each time round (at a street sign) ... results are below and I think its a very poor level of consistency. It was a bit of a recovery run after a boot camp, so I was plodding at a very level pace which is reflected in the lap times. BUT LOOK AT THE VARIATION IN DISTANCE. There was no tree cover and houses all have front gardens ... so no interference. Ignore this ... just jogged to start 1) 0.06km - 21(6:06/km) 3cal 9.83/10.25kmph 2) 0.74km - 4:10(5:39/km) 59cal 10.61/11.08kmph 3) 0.85km - 4:14(5:00/km) 60cal 11.99/13.57kmph 4) 0.77km - 4:14(5:32/km) 57cal 10.85/12.56kmph 5) 0.7km - 4:16(6:06/km) 55cal 9.83/11.08kmph 6) 0.66km - 4:12(6:22/km) 54cal 9.44/10.85kmph 7) 0.7km - 4:15(6:06/km) 56cal 9.84/10.75kmph 8) 0.71km - 4:15(6:01/km) 58cal 9.97/11.22kmph Gonna do another multilap run tomorrow. |
|
Feb 2020
6:36pm, 5 Feb 2020
125 posts
|
fazmo
Cheers Chunky. I reboot the watch after every full charge, via the menu, which is about every 4 or 5 days depending on use. G ... it loses the signal. Today I ran an imaginary line which can't have varied by more than a foot but the trace is all over the place - each lap different. Because it loses the signal it tends to cut corners and so shortens the run. |
Feb 2020
6:48pm, 5 Feb 2020
10,253 posts
|
larkim
I’d agree on a 600m lap, variations from 850m to 660m does seem a little extreme! How long before setting off did you give the watch to get a good lock? Maybe worth an experiment with giving it a long period first, just to rule out signal acquisition issues. Is it obvious from looking at the trace where the errors are creeping in? I don’t think we can see your logs (not that it would help diagnose the issue I don’t think, but it would be interesting to see). Do you take any other electronics with you when you run? Back in about 2001 I had a camcorder which completely swamped my GPS receiver (an old Garmin eTrex yellow) if it was switched on within about 5m. I suppose it’s not entirely out of the question that a phone or something else could be interfering? |
|
Feb 2020
7:08pm, 5 Feb 2020
126 posts
|
fazmo
Cheers Larkim ... today I gave it about 90 seconds after getting the green screen as I was chatting coming out of boot camp. At races and parkruns I always have it on green for ages ... several minute ... because as an old FR110 user I've been conditioned!! No other devices. Using Google earth, instead of a map, I can see where its cut corners, lining up at some points and having me running through houses and brick walls elsewhere. Other than corners, 1 side of the triangle has all 7 laps overlaid quite well, but the other 2 show 7 separate routes, despite me pretty much treading in my footprints. I didn't leave the pavement but the width of my routes is several times the width of the entire road. |
|
Feb 2020
7:29pm, 5 Feb 2020
34,093 posts
|
HappyG(rrr)
OK, it's faulty dude! In a straight line it should show a straight line, unless there are buildings or trees like megaliths around you! No GPS tracker works right on a 400m track. They normally measure LONG. There's a great paper that explains why. But if you are on a 400m track you don't need GPS. You use a stopwatch. Old school! Also GPS devices will be less accurate the more slowly you go. For instance, take it to extreme, the level of error is infinite when you are stationary (i.e. any distance that it measures, and it always will because of perturbations in the signal) is something divided by correct distance, which is nothing = infinity! Does it do it wherever you are or only in certain parks / locaions? There is a bit on the canal by me where mine always loses signal, but my old 305 and 310xt used to as well. I think it's some kind of GPS dead spot. Anyhoo, good luck. G
|
|
Feb 2020
7:32pm, 5 Feb 2020
127 posts
|
fazmo
Cheers G ... I'll contact the retailer. I'm sure you can guess ... it does it everywhere!
|
|
Feb 2020
9:44pm, 5 Feb 2020
10,254 posts
|
larkim
(mine is pretty damned accurate even on 400m tracks, hg, surprisingly so in fact. Though I'd still manually lap just to be safe)
|
Feb 2020
10:39pm, 5 Feb 2020
15,729 posts
|
Chrisull
fazmo - I've seen similar issues on mine, and I've seen other VA3 users with similar issues, so something is definitely wrong in one batch / sub category of model or whatever at the least. Mine *always* cuts corners. I've done the whole update and use Galileo, and changed the resampling to be much more frequent, but nothing much changes. Long straight, flat runs without tree/house coverage it does well with. Cornwall doesn't have many of those :-(.
|
Related Threads
-
Garmin
Apr 2024
-
From Garmin connect to Fetch...
Nov 2023
-
Garmin 405
Jul 2023
-
Garmin Upload broken or just me?
Jun 2023
-
Garmin advice
Sep 2022
-
Garmin link to fetch issues?
Nov 2021
-
Garmin connect & Fetch
May 2021
-
Back to Garmins...
Mar 2021
-
Garmin forerunner 10
Mar 2021
-
Garmin 735xt problem
Jan 2021
