Other Levo Pro 2022 & Garmin Edge speed/distance issues

[yoshimi]

Hi all, first post on here.

I have a Levo Pro Gen 3 and also use a Garmin Edge Explore 2, mainly for navigation but also so I get everything in Garmin Connect.

I understand that if you have a speed sensor (i.e. from the bike) then this overrides the GPS used for speed/distance. I had a few weird reults when I fgirst started using, with the distance showing much higher than I'd actually ridden. Thought I'd solved it by manually setting the wheel circumference.

Seemed to work ok for one ride but over the weekend I had the same issue....rode 20 miles but Garnmin said I'd done over 30miles. Elevation and route tracking were all ok.

Wondering if the 'bodge' fix is to unpair the speed sensor from the Garmin and then it'll just rely on the GPS - not ideal though.

Anyone else had this?

Thanks

 

[DJ57UMP]

Are you using the speed sensor from the Levo? Not that I have any constructive thoughts other than to wonder if you have the Levo de-restricted. Even then I guess I'd expect the speed to be half and so the distance shorter if anything?

 

[yoshimi]

HI, yes using the speed sensor from the Levo. Its totally stock, not derestricted. THe speed/distance recorded by the bike (in the Mission Control app) is correct but Garmin measures it much higher

Im using a Garmin Fenix 6 to broadcast heart rate, to the bike/Garmin Edge Explore, I record the ride through both Mission Control app and the Garmin Edge. Mission Conttrol is corect, but distance recorded on the Garmin is too high!!??

Thanks

 

[DJ57UMP]

From what I can read you're using three devices to record. If I were you I'd simplify things! If only for your sanity!

 

[CruJones]

When you connect a speedo to the Garmin it will try to auto-calibrate the wheel's circumference that is sending the speed data. To ensure the distance the Garmin thinks you've gone is correct you need to manually input the wheel's circumference in the Edge. You can either measure the circumference (usually via sidewalk/flat surface and a tape measure) or you can just use standard circumference based on your tire size that can be found online.

 

[Chicane]

Anyone know the wheel circumference you set the Garmin for mullet wheel set up? 29 x 2.3=2326.

 

[McInner1]

I have a 2019 Levo and had tested various methods to get data from bike to Garmin Edge.
I found, that using Levo as speedsensor does not work reliable, so I put a Garmin speed sensor to my front wheel hub.
Now all works flawlessly since years.
My configuration:
-speed from Garmin speed sensor on front wheel
-Levo as power sensor. Sends power and cadence.

 

[CruJones]

Anyone know the wheel circumference you set the Garmin for mullet wheel set up? 29 x 2.3=2326.

You'd use the circumference of the wheel with the sensor. If it's the front wheel then 2326 should be close. To get it most accurate you have to measure it manually.

Edge 830 Owners Manual - Wheel Size and Circumference

www8.garmin.com

 

[CruJones]

I have a 2019 Levo and had tested various methods to get data from bike to Garmin Edge.
I found, that using Levo as speedsensor does not work reliable, so I put a Garmin speed sensor to my front wheel hub.
Now all works flawlessly since years.
My configuration:
-speed from Garmin speed sensor on front wheel
-Levo as power sensor. Sends power and cadence.

Yeah, I use the Garmin speed sensor vs the speed as sent from the bike as well.

 

[yoshimi]

Thanks @CruJones and @McInner1

After getting the initial weird results, I read into in and did set my rear wheel circumference manually, its a 27.5" Maxxis DHR2 and I used a tape measure...2160mm

Last night, I rode 13.5miles but the Garmin said 18miles I then got wondering, could this be down to he rear wheel slipping. Its very muddy round here (north of England), lots of riding in slop, rear wheel "wheel spinning" in the mud might make Garmin (reading data from the rear wheel speed sensor) think I'm going faster than I was.....maybe Especially as when I rode the Peak Disrict last weekend, where its much more hardpack,. the results were correct

I think @McInner1 may have come up with the 'bodge' I need. Especially as yoou have these on your front wheels where theres less chance of wheel spinning Heading off to find a garmin speed sensor...although, does than mean that cadence won't be measured if I disable the bikes speed sensor and use a Garmin sensor on the front wheel!? I've gone down a rabbit hole with this.

Thanks again for the replies

 

[Chicane]

You'd use the circumference of the wheel with the sensor. If it's the front wheel then 2326 should be close. To get it most accurate you have to measure it manually.

Edge 830 Owners Manual - Wheel Size and Circumference

www8.garmin.com

I'm not using a speed sensor on this bike mullet, or my previous 29er. No need as the motor and Strava records the speed and it seems to be accurate enough.

On my previous 29, the distance was always pretty close with Strava, so not an issue like the OP is having. I have't used my Garmin on my new bike yet (Levo gives most needed info), but was curious to get the Garmin wheel size set correctly if I decide to use it.

 

[Alexbn921]

The real size of your wheel is different from the reported sized based on the reported mileage from the bike.

If you want your Garmin to read correctly, ride with a phone set to speed or other Garmin on gps and and manually fix the setting to match.

 

[randycpu]

Anyone know the wheel circumference you set the Garmin for mullet wheel set up? 29 x 2.3=2326.

1 - The native Levo speed/distance "sensor" is on the rear wheel, not the front. So on a mullet, that would be a 27.5" wheel.
2 - I have the same problem (unreliable speed/distance) with my Garmin and my Levo Gen1. Garmin told me it was caused by glitches in the GPS data. I have a manually entered wheel circumference in my Levo.
The Garmin would show me going 110MPH and 25 miles when it should have been 1 mile.
Still no fix for me.

 

[CruJones]

1 - The native Levo speed/distance "sensor" is on the rear wheel, not the front. So on a mullet, that would be a 27.5" wheel.
2 - I have the same problem (unreliable speed/distance) with my Garmin and my Levo Gen1. Garmin told me it was caused by glitches in the GPS data. I have a manually entered wheel circumference in my Levo.
The Garmin would show me going 110MPH and 25 miles when it should have been 1 mile.
Still no fix for me.

That's weird you have odd speed data assuming the circumference is correctly entered. Also, the Edge is supposed to use the speedo vs the GPS to calculate the distance when you have the Garmin speedo connected (not sure if it does that when you use the speed from the bike's computer, but I think it's same case for that as well). You aren't trying to feed the speedo data from the bike's computer to the Edge are you? If so, I'm not sure you should be changing the wheel circumference if you are doing that. You should only be setting the wheel circumference if you're using a Garmin speed sensor vs the bike's speedo.

 

[randycpu]

That's weird you have odd speed data assuming the circumference is correctly entered. Also, the Edge is supposed to use the speedo vs the GPS to calculate the distance when you have the Garmin speedo connected (not sure if it does that when you use the speed from the bike's computer, but I think it's same case for that as well). You aren't trying to feed the speedo data from the bike's computer to the Edge are you? If so, I'm not sure you should be changing the wheel circumference if you are doing that. You should only be setting the wheel circumference if you're using a Garmin speed sensor vs the bike's speedo.

So, let me clarify a bit. The speed readings are normal until they are not. The speed jumps to crazy fast speeds. On a recent ride, the speed went from 14.7 to 109.9MPH (109.9 seems to be some digital limit) for 15 minutes, and 2,150 miles. Then it drops back to normal speed.

 

[DuncanDoughnuts]

if you using a Garmin, why don't you just use satellite distance and speed ? I do this for my Garmin as my bike will give a wrong reading as I have set the rear wheel to 2000 and using a 29er.

 

[CruJones]

So, let me clarify a bit. The speed readings are normal until they are not. The speed jumps to crazy fast speeds. On a recent ride, the speed went from 14.7 to 109.9MPH (109.9 seems to be some digital limit) for 15 minutes, and 2,150 miles. Then it drops back to normal speed.

If you're using the Garmin speed sensor, I'd suggest removing the battery and then putting in a fresh one. Could be something that silly.

 

[randycpu]

If you're using the Garmin speed sensor, I'd suggest removing the battery and then putting in a fresh one. Could be something that silly.

I have paired the Garmin (Edge 530) with the Levo's speed/cadence sensor, primarily to get the cadence data. I would like to only use the GPS to track course, distance, speed, etc. It appears once you pair the speed/cadence sensor you cannot select GPS.
I do not have a separate wheel speed sensor on this bike, but I do own several.

 

[CruJones]

I have paired the Garmin (Edge 530) with the Levo's speed/cadence sensor, primarily to get the cadence data. I would like to only use the GPS to track course, distance, speed, etc. It appears once you pair the speed/cadence sensor you cannot select GPS.
I do not have a separate wheel speed sensor on this bike, but I do own several.

Ok, so you're using the speedo from the bike. Hmm. Not sure what you can do about that. I don't see corrupt data coming from my Kenevo. Maybe it's related to your speed sensor on the bike? Maybe the magnet or sensor is loose?

 

[randycpu]

Ok, so you're using the speedo from the bike. Hmm. Not sure what you can do about that. I don't see corrupt data coming from my Kenevo. Maybe it's related to your speed sensor on the bike? Maybe the magnet or sensor is loose?

Again, Garmin customer service says its "glitchy GPS data".

 

[CruJones]

Again, Garmin customer service says its "glitchy GPS data".

If you are using the speedo from the bike I think that will override the distance/speed from the GPS (at least it does when you use a Garmin speedo). You could look at the .fit Garmin file and see what's going on there I guess.