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

crank arm length and Favero Bepro

MACKANG
over 5 years ago

Hi.

Every time I power up my edge 530 and it connects to my Bepro pedals it will change the crank arm length to 180mm for both pedals ore even what you  see in the picture can happen. 180mm left pedal and 208mm for right pedal. I went back from fw3.50 to fw3.20 but the same happens. If I look at the sensor details on the edge it says 172.5, but when I connect the pedals to my desktop and run the bepro program it is chanced to 180mm every time. I have used the pedals with my edge 520 from December 2016 and never had this problem. I can't test it on my 520 any more because of a cracked screen, but if I test with my old edge 500 there is no problem with crank length.

I swore to my self not to by another gramin when I couldn't use my 520 any more, to bad I didn't listen. 

  • 0 over 5 years ago

    There is another thread on this where I looked at the ANT traffic. The issue appears to be on the pedal end. The radio traffic shows that the Edge is correctly sending the crank length. 

    My best guess would be that earlier software builds on other units were not actually sending the crank length to the Favero pedals, but when Garmin added the public Cycling Dynamic support for some Favero pedals they also started sending the crank length, which the Beprto is not handling correctly. The Assioma works correctly so it does point to a Bepro issue.

  • 0 over 5 years ago in reply to aweatherall

    Sorry, I don't buy that.

    If the edge is sending the crank length correctly when it connects to the pedals, why can I in the sensor details menu on the edge unit, set crank length, and the pedals gets that command correctly? Should not those two commands be the same?

  • 0 over 5 years ago in reply to MACKANG

    I can only conclude that the Bepro is not decoding the "set" crank length message sent over ANT correctly.The app is communication over BLE so uses a different message format.

    I have checked what the Edge is sending with the ANT+ Power spec and the Edge is correctly defining the value, which is expressed as an offset from 110 mm in 0.5 mm increments.

    If you want send me Private Message and I will give you instructions on how to collect the ANT radio traffic.

  • 0 over 5 years ago in reply to aweatherall

    What app and BLE? Bepro are ant+ only. When connecting to my desktop I use USB cables.

    Please read what I wrote again.

    When my EDGE 530 connects to my pedals it messes up the numbers for crank length.  Il check that with my desktop computer.The EDGE still reports 172,5 mm but on my computer, with the bepro program and pedals connected with USB cables reports 180,0mm for both pedals or 180,0mm for left and 208,0mm for right pedal.

    I disconnect cables and connect my EDGE to the pedals with ant+. In the crank length menu on my EDGE I change length to ex. 165 and send that command. Connecting pedals to my desktop again, and the bepro program reports crank length to 165mm. I have successfully sent a "set" crank length message to my pedals, with my EDGE, with ant+.

    By reading the change log for beta 3,55 fw we know Garmin have some problems on the software part.

  • 0 over 5 years ago in reply to MACKANG

    I think what he is saying is that there is a standard Ant+ protocol. He looked at the data coming from the head unit and it was the correct data. For your model pedals to be the only ones with this happening points to it being a power meter side issue. Have you contacted Favero about this issue yet to see what they say? What about Garmin support? 

  • 0 over 5 years ago in reply to Browner40

    I have passed my findings on to Favero. This only impacts the Bepro pedals not their other model.

    I have no heard back from them.

    Sorry I missed you were using a USB cable to read the settings off the pedal I had incorrectly assumed that the communication was over BLE.

    If you want me to look at the ANT message that is passed over let me know.

  • 0 over 5 years ago in reply to Browner40

    Yes I know there is a standard Ant+ protocol.But there are many brands of head units on the market that say they use the same standard Ant+ protocol, and there is no problems on those head units. Including edge 520.

    I have contacted Favero about this but not Garmin. I need serial number of my unit to contact Garmin, and I will do that as soon as I get home from this business trip.

  • 0 over 5 years ago in reply to aweatherall

    As you wrote in your first message, I to believe this has something to do with support of public cycling dynamics. I don't doubt that "set" crank length message is sent correctly, but there is probably other "set" messages sent to the pedals when they connect to the EDGE.I believe the problem is there, with those commands. (I'm guessing)

    Will be back tomorrow with some question. I'ts almost 1 AM here and I need my beauty sleep.

  • 0 over 5 years ago in reply to MACKANG

    Crank parameters are accessed through a single page (get/set)

    D00001086_ANT+_Device_Profile_-_Bicycle_Power_Rev_5.0.pdf

  • 0 over 5 years ago in reply to Browner40

    ANT+ powermeter profile latest update is 5.0 November 2016. No cycling dynamics in that revision.

    My head unit do support cycling dynamics Favero just released an update for their assioma pedals to include cycling dynamics, and it works.

    Follow the link below to dcrainmaker. Scroll down to message #43

    https://www.dcrainmaker.com/2019/07/favero-assioma-cycling-dynamics-released.html

    Conclusion:

    Garmin is not using the latest approved power meter profile.

    I wonder where my problem origin, in my Garmin head unit or in bePRO pedals. Hmmmm