Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Incorrect wattage with 7.50 and Faver BePro pedals

prideracer
over 6 years ago

Since some weeks my edge 1030 shows paired with the Favero BePro pedals too high watteges, for example same hill with same intensity are now 400 W instead of 330 W.

I also saw each time i calibrate the pedals with the edge /zero caliblration, -not dynamic) ...the crank lenght in the pedals gets changed. ( i can see that after connecting the pedals via USB with the PC and the BePro updater SW from Favero)

I am nearly sure there must be some issue in the garmin SW.

ON my second bike i have the newer Favero Assioma pedals and they still work in a good way with correct wattage values.

@ Gamin Please check this, it's really annoying all the problems i had with that device, blue halo, a lot of SW bugs during the lust year aso...

  • 0 over 5 years ago in reply to jweijters

    It is not the settings.fit , that contains the crank length. the activity fit doesnt. 

  • 0 over 5 years ago in reply to Luko79

    Ok,

    I checked my Bepro's connecting them to my laptop. The crank length was 208

    Then I checked the Settings.fit file, the crank_length: 237.0 mm (254)

    I connected my Bepro's to my Garmin, and manualy set the cranklength to 175.

    Then I disconnected them from the garmin, and connected them to my laptop: the cranklength was 180

    I reconnected the Bepro's to my Garmin, and set the length to 172.5. then I checked the length with my laptop, the crank length was 172.5

    Then I turned off my Garmin, and powerd it on again. I connected my sensors, and powered off my Garmin. I checked the cranklenth in my Bepro's, it was empty.

    It looks like something goes wrong saving the cranklength in the Settings.fit file, and updating the cranklength after powering up.

    in the Settings.fit file, the crank_lenth stays at 237.0 mm (254)

    kind regards,

    Joris Weijters

  • 0 over 5 years ago in reply to jweijters

    Nice! :)  Btw, there is an Android app, IPSensorman, if You have ANT+ capable mobile, You can read out the crank length (and much more data) from sensor details , You dont need to connect the pedals to the Favero PC app . (btw, As i remember, i had almost similar issue with Edge 500 or 520plus /dont remember exactly/, the PC app showed different crank length after cable connection than what it was before checked via IPSensorman, so the PC app neither a stable thing ... )

  • 0 over 5 years ago in reply to Luko79

    The swapping between bikes still takes time and would probably be done way too many times in the season which wears out the threads.

    Power pedals are in theory superior as the strain gauges are placed closest to the power source and additional data such as cycling dynamics is possible. The only way power cranks are better is superior battery life and possibly better resistance to damage.

  • 0 over 5 years ago in reply to rob-tech

    and better error filtering (no false high spikes on rough terrain or in dh), reliable autozero calibration (with P2M or now with Quarq), more accurate cadence , so in total, more accurate pmeters. 

  • 0 over 5 years ago in reply to Luko79

    I have been working with someone who has been having the bePro crank length issue and they have been working with Favero. Favero gave them a software update that appears to have fixed the problem. Hopefully Favero will make this software update generally available for their bePro customers.

  • 0 over 5 years ago in reply to aweatherall

    Alan, You are so diplomatic! ;)  Great job! :)

  • 0 over 5 years ago in reply to aweatherall

    O.k. i think it must not stay a seret, i received some new FW from favero yesterday and first impression is very good, crank length is now saved correctly garmin - bepro aso..., but last test is not done now, yesterday it was raining here but i am planning to make a short test ride today and i am nearly sure the problem is solved now with that new FW.

    After my ride today i will write favero my experience and i am pretty sure they will make the new FW avaliable for all bepro users,

    Stay tuned.... :-)

  • 0 over 5 years ago in reply to prideracer

    Favero also sent me their new firmware 1016.

    tested it with a ride and worked fine. Crancklenght stayed at 175.0 with normal output readings.

    good support from favero!

  • 0 over 5 years ago in reply to Bas-Meerman

    Same situation here! Everything works fine now, thanks to Favero and aweatherall who analyzed the problem and helped us!