Speed jumps to 146mph

Former Member over 10 years ago

I've noticed on a few of my recordings that the speed jumps from 0 to 146mph for no reason a few times.

Normally when I'm stationary & at the first few minutes of a ride.

I use a 3rd party speed/cadence sensor and have checked that I'm not just rolling the magnet quickly past the sensor if I'm stopped.

My Garmin Edge 800 is also synced with my sensor and this speed jump has never appeared on it.

Anyone shed some light on this

Cheers

0 mick.t2 over 10 years ago

I have had the problem of 146mph maximum speed readings ever since I bought the Virb elite back in June 2014. I use the Garmin speed/cadence sensor. I have tried with the sensor turned off and still get this error. I turn on the Virb before starting my ride and leave it on for about 15 minutes for the altitude reading to settle to something believable. I then slide the record lever forward and off I go. I notice that the segment with the 146mph is between turning the unit on and starting the record. Its annoying but I've learned to live with it and wait while Garmin come up with a fix, probably in their next model so I will have to upgrade (yet again). I'm going to contact Garmin and see if I can set up a direct debit from my bank account to pay for all the investments I have in their equipment.

0 Former Member over 10 years ago

Did my first recording of a ride for awhile and after updating to the latest FW4.0 ( after a Hard reset and re pairing of my connected devices) I'm STILL getting the 146mph jumps a good 4 mins + into a ride then settled down to normal speeds after a few mins. I noticed that I was close to a high sided wall but my speed should only be from my sensor not gps so I would think not effected.

Also seems o happen when I stop cycling (0mph) for a short time, it jumps to 146mph and stays there sometimes too

Was this bug corrected in this update or still ongoing?

0 Former Member over 10 years ago

We are aware of the issue, but it has not been fixed in 4.00 yet unfortunately.

I have strong hopes that the next major firmware version will indeed fix this.

Sorry for not having better news.

0 Former Member over 10 years ago

We are aware of the issue, but it has not been fixed in 4.00 yet unfortunately.

I have strong hopes that the next major firmware version will indeed fix this.

Sorry for not having better news.

Thanks for the update :) :cool:

0 Former Member over 10 years ago

High speeds in fit file.

Reported this in different thread and FALAGAR confirmed it is fit file corruption. Apparently they will look at arranging for virb edit to have option of using GPX file instead of fit file as well as virb firmware fix. I found that Dashware program has similar features to virb edit but allows you to select the GPX file and solves the problem. I hadn't realised that this issue had been known about since Feb and not fixed!