Incorrect wattage with 7.50 and Faver BePro pedals

Hi Andrea,

i was in contact with people from Favero and also with some guy who worked for garmin, at the moment there is no real solution avaliable but a workaround to avoid that problem, but it's not a final solution because you have to execute that procedure before every start.

You have to set a different crank lenght before each start, for example 160mm with your garmin, and after that the correct crank lenght, then the power should be displayed correctly, but it's not for sure at all, you have to try yourself, best would be to put your bike on a taxc neo trainer or somethink else to be sure you get the working workaround. ;-)

@ Garmin: When do you think to solve that problem (1030 with Favero BePro powerpedals) ???

I have for month's incorrect wattage displayd because of changes in SW versions above 6.30, the ball is at your side, don't think i sell my pedals and switch to vectorś, before that happens i give back my edge and take a wahoo,

My patience is really reaching the end of the scale.

Thank's in advance!

I have passed my findings on to both Garmin and Favero. Looking at the radio logs the issue appears to a corruption of the crank length values stored on the pedals for some reason. The Edge does not send a change crank length value by default.

It does send a get capabilities message, which the bePro pedals don't support so I don't know if it handling that message incorrectly.

If you manually change the crank length on the Edge then the crank lengths get corrected on the pedals, but if you do nothing then the values on the pedals appear in some cases to get corrupted to 180 mm left, 208 mm right

aweatherall, thank you again for your kind support, i'm sure you did everything you can do, now the ball is at Garmin/Favero SW engeneers, and i really hope they will solve that problem as soon as possible.

The problem is, also with that workaround you never can be sure you've correct watts on display, i don't know exactly why, but last race i had, i didn't have correct values although i set crank length manually to t160 and after that to 180.

With BePro pedals You never get correct power values. It is one of the worst power meter on the market... :) all is overreport the power by default (in static position), you have to decrease the scale factor with 5-15% (weight calibration needed) . If it is done, you must install it absolute precisely and fix the pedals even with loctite, because the spindle could rotate easily (due to a sprint, a harder effort or not perfect installation with 40nm), and if it's rotated, even a tiny micron or mm  (and there is no dynamic backwards calibration immediately, btw, You must do dynamic calibration weekly ...), it overreports the power again. (The Assiomas have much better firmware and design, and eliminate these absurd issues.) . So the best what i could recommend You (if You wanna see RELIABLE power values) to sell these BePros to a "blind" and get a serious power meter ... 

BR,

Andras (a power meter expert)

Same problem here. 1030 with 7.50 sets crancklength to 208 and gives false data.

with an old 520 no problem.  Sent a request to garmin on july 22, no response yet. 

Garmin. Wake up please

Thank you Luko79 for your input:

For your explanation: This problem has nothing to do with the mounting of the pedals or their behaviour you mentioned, the problem is that the edge send's some incorrect crank lengths to the pedals which results in wrong watt values displayed on the edge.

And yes, i also used some loctite to fix the pedals and they worked really good until that FW update from garmin, and also very accurate! But of course i agree, the Assiomas are much better, maybe the best power pedals on the market. (i own the assiomas too on my other bike)

So Garmin wake up please, it's your turn!

Nothing in the message exchange from the 1030 changes the crank length. All the Edge does is send a get crank length message request.

The only difference between the 520 and 1030 is that the 1030 also sends a get capabilities message request. The bePro pedals do not appear to handle the request correctly. It should either just ignore it or respond to it. What it appears to do is to incorrectly try and process it as a set crank length message.

The ANT spec only allows a single crank length value to passed. For the crank lengths to be different it has to be an error on the bePro side.

If you have a contact name at Favero let me know. I have passed this information, but got no response.

Hi,

Which fields in the FIT file are relating to the crank_length?

This is my device  record

device_info
 * ant_network: antplus
 * antplus_device_type: bike_power
 * battery_status: ok
 * battery_voltage: 3.83984375
 * cum_operating_time: 2999352
 * device_index: 5
 * hardware_version: 6
 * manufacturer: favero_electronics
 * product: 1
 * serial_number: 7155
 * software_version: 10.15
 * source_type: antplus
 * timestamp: 2019-08-07 06:44:07
 * unknown_13: None
 * unknown_15: 3
 * unknown_16: None
 * unknown_24: 84614131
 * unknown_29: (None, None, None, None, None, None)
 * unknown_30: None
 * unknown_31: None
 * unknown_8: None
 * unknown_9: None

kind regards,

Joris Weijters