Bug: AXS functions error after configuring AXS blip combo press

hoyhoy
1 month ago

Someone already filed this bug, but it's still a bug and still not fixed after nearly a year later...

forums.garmin.com/.../bug-ant-control-function-5-and-up

I narrowed it down to when I map the blips "combination" function.  The Edge 1050 mistakenly allows you to configure a "long press" for a combo blip press which isn't supported by AXS blips.  When I try to configure anything on the Edge 1050 firmware after adding the blip combo, the firmware won't allow.

The other issue is if you map functions out of order, the Garmin doesn't see the new functions.  For instance, if I map AXS Function 1, 2, and 4.  The Edge 1050 will show Function 1, 2, 3, 4 when no "Function 3" exists.

There seem to be a number of bugs here.

(1) configuring a blip combo mistakenly allows a "long press" configuration

(2) after a blip combo is mapped to AXS function, the Edge 1050 glitches out and won't persist any changes to the function mapping.

(3) previous AXS functions can't be reconfigured after the blip combo function.  They can be changed, but if you load them again, they'll revert back to the previous values.

I went as far as clearing out my AXS pairing, and then re-pairing every component with the new firmware.  But, the Edge 1050 still glitches out after I configure the blip combo function.

  • 0 1 month ago

    I just setup another set of blips with updated firmware.  The combination press is broken on the bonus buttons and the blips.  is there a fix for this coming?  Seems like a trivial bug to fix in the firmware, but nothing ever seems to get fixed...

  • 0 30 days ago in reply to hoyhoy

    Thanks for your post!

    One other post does not constitute a "bug" that has not been fixed. Here is a forum post by a Hammerhead user describing the same symptoms: https://support.hammerhead.io/hc/en-us/community/posts/26028982215451-SRAM-AXS-Blips-Long-Press-and-Combo-not-working

    Given that you can reproduce this behavior with multiple sets of SRAM hardware, this may be a limitation rather than something not working as designed, and I am bringing this to my team to investigate further.

    SRAM likely uses the standardized ANT+ sensor profile for 'Controls', part of how this will function depends on how SRAM/the user configures the shifters, part will be what the Edge can do with the message it receives.

    Is there an advantage to mapping the functions "out of order" or is this resolved by pairing "in order"?
    Can you provide more specifics about what is happening when the Edge "glitches out"?

    We'll test this internally and follow up with more info when available. 

  • 0 30 days ago in reply to Garmin-Clayton

    The main bug is that the combo presses on the blips and bonus buttons can’t be configured at all (possibly only if you have blips).  You can set the combo function on the Edge 1050, but if you look at the function again, it will reset.  I’ll make a video of it.

    Also, the Edge 1050 allows you to set a “long press” for the blip combo which isn’t something that SRAM supports with blips.  Blips only support short press.  That’s 100% an Edge 1050 firmware bug.  That’s I’m wondering if  the blip implementation on the Edge firmware is fundamentally wrong.

  • 0 30 days ago in reply to hoyhoy

    For the second pair of blips, I updated all the firmwares on the shifters, derailleur and the blips before I connected them to the Edge.  The only way you can configure blips with the Edge 1050 that works right now is to map all the single press functions first.  The combo presses can’t be mapped to Edge functions at all.

  • 0 29 days ago in reply to hoyhoy

    SRAM removed some of the capabilities from the bonus buttons in one of their software updates. Someone posted a message from SRAM about this on the forum. I will see if I can find it.

  • 0 29 days ago in reply to aweatherall

    It maybe worth contacting SRAM and see what functionality they say they support from buttons and the blips.

  • 0 29 days ago in reply to aweatherall

    I can map the blip combination press to an AXS function using the SRAM AXS app.  The Edge 1050 won’t save anything after I attempt to map the AXS blip combo function to a Garmin function.  It doesn't appear to be a SRAM AXS app issue.  Both the blip combo and bonus button combo functions always seem to get mapped to start/stop ride after mapping them.  I would guess it's another Edge 1050 firmware bug among the infinite list of Edge 1050 bugs that will never be fixed.