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

New Edge 530 Public Beta 9.26 Now Available

A new Beta software for the Edge 530 has been released. Full change log, instructions, and software for installing the beta can be found in the link below.

Edge 530: https://www8.garmin.com/support/agree.jsp?id=14953 

Notes:

  • For any issues that you encounter please fill out the form included in the download and attach it to an email to [email protected]. Please note that you may not get a response to the email unless we need more information on the issue you report.
  • Although this software is believed to be reliable, it has not yet been released for production and should be used at your own risk.

Changes made from version 9.24 to 9.26:

  • Fixed software crashes caused by encrypted CIQ programs that are no longer valid.
  • Fixed a couple of device stability issues.

Changes made from version 9.22 to 9.24:

  • Fixed automatic maximum heart rate detection.
  • Added the ability to perform the FTP test with power data coming from a trainer.

Changes made from version 9.20 to 9.22:

  • Changed gear battery data field to display percentage remaining if available, which affects Shimano Di2 single-battery systems.
  • Updated sensor low battery prompts to differentiate between low and critical status.
  • Fixed issue where distance could stop accumulating.
  • Fixed issue where text message sender names would display incorrectly.
  • Does it fix the issue with power dropouts?

  • Strava Live segments fail to download...

    No segments on device and Strava Segment list on Connect.com disappears again.

  • Still no fix for sensor radar 0:9 issue WearyWearyWeary

    it’s a shame!

  • That was my hope too. I am disappointed but not surprised given Garmin’s track record of bugs over the years. 

  • I also had my cadence sensor drop out and reconnect constantly for about 20 minutes during my last ride.
    Very strange and exceptionally annoying the beeping from the device. 

  • I run 4III power, various generations of Garmin sensors (Speed, cadence, HR), DI2, Edge Remote & Giant Ridesense with my E530 which I have has since shortly after launch.  I swap between bikes with different combinations.   Like when using the 520+ before I do see an occasional reconnect of a sensor during a ride but it's few and far between and has never impacted me the way it does some given the passion of some posters on the topic.  I've also had Varia RTL radar for many years and have never seen the errors that others are posting about.  I don't doubt that these are a real annoyance for those being impacted by them but suspect these are edge cases that could be down to hardware or other environmental issues that are not common given how many of these devices are sold.   I think it would need Garmin to identify some of those users encountering these issues and do a deep-dive into their specific configurations and usage to try to diagnose root cause.

  • That's been happening to me with both GA and Beta releases for more than a year. Honestly have learned to tune it out, but it is a real poor experience.

  • I've been effected for a while, and it has slowly gotten worse (more dropouts and for longer periods of time). For every edge case effecting people, there will be an equivalent number of people having the opposite experience - like you who have almost zero dropouts. Quality Assurance is a thing for a reason, and maybe something hasnt been installed properly, a chip isnt up to spec (but passes QA) or a whole host of other software/hardware issues related to specific use cases and scenarios. I've tried to work with Garmin on dropouts and gotten very little feedback, and many subsequent versions of software have never listed an item addressing dropouts. Yes, there are probably more people having zero issues than there are having issues, but regardless of it being an edge case, hardware or other environmental issues - it is an issue and it does detract from an otherwise good product.

    Just because you're not having an issue, dont discount those who are.

  • I specifically wrote “ I don't doubt that these are a real annoyance for those being impacted by them” which is the opposite of discounting anyone.   

  • You also wrote (in amongst the general tone of your post) - "never impacted me the way it does some given the passion of some posters on the topic".

    Read the room...