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

bug with Campagnolo EPS

AndreaA
over 4 years ago

Hello from Campagnolo EPS support. I'm Andrea Armellini, I work in Campagnolo in EPS division.

I think I found a bug in 830 and 530 devices (and I suppose with all x30 devices) with our Campagnolo groupset.

The bug is related to activity registration and fit file exported that don't have the right data concernig the gear sensor. In our app we use API to Garmin Connect to retrieve registered session to analyze gear data, and i found incoerent data.

Scenario:

I'm going to register activity with Fenix 5, Garmin Edge 530, Garmin Edge 830, Garmin Edge 520, Wahoo Elemnt Bolt. In all deviced I add the gear sensor using ANT+ protocol (i'm testing with our Campagnolo 12 EPS groupset, updated with the last firmware).

In the gear option page, in all Garmin devices (except the wahoo that doesn't have this option) I configure the sensor details as following:

Front Gears (2): Gear 1 (36), Gear 2 (52)

Rear Gears (12):  Gear 1 (32), Gear 2 (28), Gear 3 (25), Gear 4 (22), Gear 5 (19), Gear 6 (17), Gear 7 (16), Gear 8 (15), Gear 9 (14), Gear 10 (13), Gear 11 (12), Gear 12 (11)

Details correspond to chainring teeth

During registration I tried different combination and multishifting.

I than connected all devices to my pc to export fit file of the registered activity.

I converted fit files to CSV using the appropriate tool from Fit SDK and i opened with excel. I searched in the raw for the event "gear_change_data" and look at the results

Garmin Edge 520, Fenix 5 and Wahoo exhibit the same behavior. I had values from 1 to 12 from "rear_gear_num" and the corrispondence with assigned theeth numbers. I had values from 1 to 2 from "front_gear_num" with assigned theeth numbers (36 or 52)

Garmin Edge 530 and Garmin edge 830 show different values: they use different scale of values. Rear_gear_num going from 0 t o11, and front_gear_num going from 0 to 1 (in some rare case I had dirty values from 0 to 2).

The problem appears after front derail.

As you see, we get front_gear_num = 0 (it would be 2) and front_gear = 255 (both on 530 and 830), and they are inverted in 530 and 830 (it show 52, but I'm on 36)

In the hud in Garmin 530 and 830 in relative page fiedl and graph data and position correspond to the reality

Data 3 event timestamp 959425468 s gear_change_data 604050948 event 43 event_type 3 rear_gear_num 4 rear_gear 22 front_gear_num 1 front_gear 36
Data 3 event timestamp 959425472 s gear_change_data 4278195716 event 42 event_type 3 rear_gear_num 4 rear_gear 22 front_gear_num 0 front_gear 255

In 520, Fenix:

Data 2 event timestamp 959425468 s gear_change_data 872551173 event 43 event_type 3 rear_gear_num 5 rear_gear 19 front_gear_num 2 front_gear 52
Data 2 event timestamp 959425472 s gear_change_data 604050181 event 42 event_type 3 rear_gear_num 5 rear_gear 19 front_gear_num 1 front_gear 36

In wahoo io have same data as 520 and Fenix, but in different column. It report the right front_gear_num, 1 and 2

Please could you check if there is a sort of bug in Garmin x30 devices with ANT+ broadcast message and Campagnolo groupset?

  • 0 over 4 years ago

    What build are you using on the Edge. There was a fix in build 5.50 that made changes for front gear position info for units paired over the ANT+ Shifting spec.

  • 0 over 4 years ago in reply to aweatherall

    I'm on 5.10: in Garmin express it was the last firmware. I just download the 5.50 firmware and installed on my 830. I'm going to make a test and update you soon.

    Thank you

  • 0 over 4 years ago in reply to aweatherall

    I confirm, with 5.50 the bug is resolved

  • 0 over 4 years ago in reply to AndreaA

    Glad to see it resolved, but:

    Garnin is barely taking note of this forums. If you encounter problems, try business channels. I mean, your company is no small shop but a remarkable so it should be possible to give you some phone number when you call support. 
    Otherwise: in the Beta files is a eMail address where you can reach the devs (seems to be 99% one-way communication). 

    The Forum is end-User to end-user assistance. 

  • 0 over 4 years ago in reply to BeneGi

    Sincerely I don't understand your comment.
    I don't want to argue, but first of all I am an end user too.
    Happy to know that there is a business support, but I believe that this channel and the response received was quick and efficient, perhaps more efficient than looking for an email address in a beta version.
    Among other things, our business is to produce groups and wheels, not to test cycle computers or try beta versions. In this case it was little bug and as technician I try to give you more details than normal user