Blevo - Detailed Data from SL Ride

[BioWheel]

All - Thought I would post my Blevo numbers from a recent ride. Found the battery numbers particularly interesting. And the rider power vs motor power. Really amazing how much info generated. Vado SL 4 non-EQ. I weigh 145lbs (66kg). Think the app is worth it.

-----------------------------------------
BLEvo v3.9.6

Jul 10, 2021 1:57:48 PM

- Movement time: 1:03:52
- Total miles: 17.54 mi (▲ 1.7 mi | ▼ 1.4 mi | = 14.5 mi)
- Average speed: 16.5 mph
- Total ascent: +452 ft
- Battery consumed: 23% (77Wh)
- Average consumption per MI: 4.66 Wh/mi
- Percentage of average assistance: 35.7%
- Wh ride: 226.2Wh
- Biker: 66.0% (149.2Wh)
- Battery: 34.0% (77Wh)

------------------------------------------------------

FULL STATISTICS:

Firmware: 0.4.17
Bike parameters:
Profiles 1 - 30/50/100 PP 35/60/100 ACC 0% Shuttle 0%

Percentage of average assistance: 35.7%
- ECO: 30.0%
- TRAIL: 50.0%
- TURBO: 100.0%
Manual assistance changes: 10
- ECO: 4
- TRAIL: 5
- TURBO: 1

Date time:
- Start: Jul 10, 2021 1:57:48 PM
- End: Jul 10, 2021 3:02:24 PM
- Total time: 1:04:36

Movement time: 1:03:52
- ECO: 48:16 (75.6%)
- TRAIL: 14:57 (23.4%)
- TURBO: 00:38 (1.0%)

Movement time: ▲ 0:06:47 | ▼ 0:04:27 | = 0:52:37
- ECO: ▲ 0:04:47 | ▼ 0:03:29 | = 0:40:00
- TRAIL: ▲ 0:01:49 | ▼ 0:00:58 | = 0:12:10
- TURBO: ▲ 0:00:11 | ▼ 0:00:00 | = 0:00:27

Total miles: 17.54 mi
- ECO: 12.56 mi (71.6%)
- TRAIL: 4.75 mi (27.1%)
- TURBO: 0.22 mi (1.3%)

Total miles: ▲ 1.7 mi | ▼ 1.4 mi | = 14.5 mi
- ECO: ▲ 1.1 mi | ▼ 1.0 mi | = 10.4 mi
- TRAIL: ▲ 0.5 mi | ▼ 0.3 mi | = 3.9 mi
- TURBO: ▲ 0.1 mi | ▼ 0.0 mi | = 0.2 mi

Total miles with assistance: 16.53/17.54 mi (94%)
- ECO: 11.67/12.56 mi (92%)
- TRAIL: 4.66/4.75 mi (98%)
- TURBO: 0.20/0.22 mi (92%)

Battery:
- Start: 100% (330Wh)
- End: 77% (253Wh)
- Consumed: 23% (77Wh)
- ECO: 12.0% (40Wh)
- TRAIL: 10.1% (33Wh)
- TURBO: 0.9% (3Wh)

Average consumption per MI: 4.66 Wh/mi
- ECO: 3.45 Wh/mi
- TRAIL: 7.23 Wh/mi
- TURBO: 14.99 Wh/mi

Range: 54 mi (▲ 1485 ft)
- ECO: 73 mi (▲ 1986 ft)
- TRAIL: 34 mi (▲ 839 ft)
- TURBO: 16 mi

Battery temperature:
- Min: 86°F
- Max: 95°F
- ∅ : 89°F

Motor temperature:
- Min: 89°F
- Max: 129°F
- ∅ : 112°F

Average speed: 16.5 mph
- ECO: 15.6 mph
- TRAIL: 19.1 mph
- TURBO: 20.8 mph

Average speed: ▲ 15.1 mph | ▼ 18.2 mph | = 16.5 mph
- ECO: ▲ 13.8 mph | ▼ 17.7 mph | = 15.6 mph
- TRAIL: ▲ 17.8 mph | ▼ 20.1 mph | = 19.2 mph

Maximum speed: 25.0 mph
- ECO: 22.7 mph (14:57:50 - mi 16.40)
- TRAIL: 25.0 mph (14:54:25 - mi 15.26)
- TURBO: 22.6 mph (14:57:08 - mi 16.16)

Average cadence: 71 rpm
- ECO: 70 rpm
- TRAIL: 76 rpm
- TURBO: 81 rpm

Maximum cadence: 100 rpm
- ECO: 91 rpm (14:40:15 - mi 11.40)
- TRAIL: 100 rpm (14:52:13 - mi 14.51)
- TURBO: 89 rpm (14:57:06 - mi 16.15)

Kcal consumed: 583 Kcal
- ECO: 424 Kcal
- TRAIL: 150 Kcal
- TURBO: 9 Kcal

Average Biker Power: 148 Watt
- ECO: 145 Watt
- TRAIL: 154 Watt
- TURBO: 222 Watt

Maximum biker power: 323 Watt
- ECO: 318 Watt (14:12:11 - mi 3.56)
- TRAIL: 323 Watt (14:52:25 - mi 14.57)
- TURBO: 300 Watt (14:57:03 - mi 16.13)

Average Motor Power: 74 Watt
- ECO: 52 Watt
- TRAIL: 130 Watt
- TURBO: 284 Watt

Maximum motor power: 298 Watt
- ECO: 155 Watt (14:20:47 - mi 6.03)
- TRAIL: 209 Watt (14:49:40 - mi 13.64)
- TURBO: 298 Watt (14:57:00 - mi 16.11)

Total Wh biker: 149.2 Wh
- ECO: 108.5 Wh (72.8%)
- TRAIL: 38.3 Wh (25.7%)
- TURBO: 2.3 Wh (1.6%)

Total Wh motor: 73.9 Wh
- ECO: 38.6 Wh (52.3%)
- TRAIL: 32.4 Wh (43.8%)
- TURBO: 2.9 Wh (4.0%)

Maximum altitude: 52 ft
Minimum altitude: 0 ft

Total ascent: +452 ft
- ECO: +315 ft (69.9%)
- TRAIL: +111 ft (24.8%)
- TURBO: +24 ft (5.4%)

Total descent: -442 ft
- ECO: -327 ft (74.0%)
- TRAIL: -115 ft (26.0%)
- TURBO: -0 ft (0.0%)

Uphill altitude gain per hour: 3998.7 ft/h
- ECO: 3962.9 ft/h

Downhill altitude gain per hour: 5969.4 ft/h
- ECO: 5643.9 ft/h

Maximum gradient: 5.5%
- ECO: 5.5% (15:01:25 - mi 17.36)
- TRAIL: 3.1% (14:57:31 - mi 16.29)
- TURBO: 2.0% (14:57:25 - mi 16.26)

Minimum gradient: -4.0%
- ECO: -4.0% (14:04:58 - mi 1.56)
- TRAIL: -2.8% (14:49:43 - mi 13.66)

 

[jimk]

Thanks for the data post. Can Mission Control and Blevo run at the same time?

 

[Rincon]

Thanks for the data post. Can Mission Control and Blevo run at the same time?

I've never been able to use them both at the same time. Give it a try.

 

[Stefan Mikes]

Thanks for the data post. Can Mission Control and Blevo run at the same time?

Not. Both Mission Control and BLEvo rely on Bluetooth connection, and only one application can use Bluetooth at a time.
BLEvo offers far more capability than MC. For that reason I stopped using MC completely.

 

[Calcoaster]

I just used Blevo for the first time with my Vado SL and have a few questions:
Is there an auto pause setting? It seems that I started the app and waited a few minutes to start my ride. The app ran during that time and calculated my averages with that down time as part of them.
I paired my heart rate monitor (polar oh1) but blevo didn’t record it during the ride. I use my garmin 130 during rides and that pairs with my hr monitor. supposed to pair with multiple devices.

Very cool blevo map display - I can scroll through my ride and see the instantaneous data at every point.

 

[Stefan Mikes]

I just used Blevo for the first time with my Vado SL and have a few questions:
Is there an auto pause setting? It seems that I started the app and waited a few minutes to start my ride. The app ran during that time and calculated my averages with that down time as part of them.
I paired my heart rate monitor (polar oh1) but blevo didn’t record it during the ride. I use my garmin 130 during rides and that pairs with my hr monitor. supposed to pair with multiple devices.

Very cool blevo map display - I can scroll through my ride and see the instantaneous data at every point.

Yes, there is auto-pause. BLEvo transfers both moving and elapsed time to Strava. These are two different data fields that can be selected to the dashboard.

You need to define your Polar OH1 somewhere in the BLEvo Configuration menus. Look for the icon of heart. OH1 works for me with BLEvo perfectly!

 

[Calcoaster]

Which option do you recommended for accuracy, use gps, or use bike data? I read the instructions for using bike data requires us to set the wheel size in blevo, which then resets it to a different size in mission control based on the speed limit we select. Sounds like trouble to me, but wheel size seems like it would be more accurate than gps for speed, except for the speed limit issue. I don’t understand why blevo changes the true wheel size in mission control. Can someone explain it?

 

[Stefan Mikes]

Which option do you recommended for accuracy, use gps, or use bike data? I read the instructions for using bike data requires us to set the wheel size in blevo, which then resets it to a different size in mission control based on the speed limit we select. Sounds like trouble to me, but wheel size seems like it would be more accurate than gps for speed, except for the speed limit issue. I don’t understand why blevo changes the true wheel size in mission control. Can someone explain it?

Use the GPS data instead of e-bike data.

The BLEvo wheel size setting mostly affects the users who have changed their e-bike tyre size. Let me explain it in some detail:

The accuracy of the speed and distance measurement by e-bike depends on the actual wheel circumference, and on the wheel circumference value set in the bike firmware. There are three distinct situations:

• The wheel circumference set in e-bike firmware has been wrong from the very beginning. For instance, Specialized have set the wheel circumference for the "big" Vado to be 2155 mm (for Electrak 2" tyres), and they then started mounting 1.75" tyres on these e-bikes, forgetting to change the wheel circumference value in the firmware. (Only the LBS can change that parameter), or
• You have changed your tyres to another size, or
• The inflation pressure of your wheels is different than assumed, making slightly different speed and distance measurement that accumulates with the distance ridden.

Several EBR Vado/Como users have measured their wheel circumference, visited their friendly LBS and have had the wheel circumference value modified in the firmware. After several visits, these users could discover the e-bike measured speed/distance was still wrong. Manipulating the value of the wheel size in BLEvo gives confusing outcome, too.

• Vado SL 4.0 EQ with Nimbus II 38-622 tyres inflated to the middle allowable pressure gives 100% perfect match between e-bike data and GPS
• The same Vado SL with Schwalbe Smart Sam 37-622 tyres gives almost perfect match (Schwalbe made their tyre to have the same wheel circumference as standard 38-622 tyre)
• Vado 6.0 with 51-622 (2") tyres gives the perfect match.
• The same Vado with 47-622 (1.75") tyres reports far too big speed and distance ridden
• Giant Trance E+ 2 Pro reports wrong speed/distance with its stock tyres (Giant has forgotten to update the firmware).

The bottom line is: As long as your GPS works properly, and you are concerned with recording your rides in the most honest way, always use the GPS data instead of e-bike data.

My longest ride ever on Vado 5.0/6.0 with 1.75" tyres was 177 km based on e-bike data but only 168 km based on GPS/map.

 

[Stefan Mikes]

There are two things that are not perfect with BLEvo:

• The Range estimate doesn't take the fact the batteries cannot be discharged below 5% into account. Beware: You might be caught pedalling powerless on last miles!
• The Elevation Gain reported to Strava by BLEvo is totally wrong, at least in my case. I always need to "Correct Elevation" in Strava.