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.29 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.28 to 9.29:

  • Fixed an ANT burst-mode issue.

Changes made from version 9.26 to 9.28:

  • Added support for Connect IQ System 5.
  • Improved map turn review zoom level when approaching roundabouts at slow speeds.
  • Fixed issue where very long course names resulted in routing calculation failure.
  • Fixed issue where activities could be hidden from history.

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.
  • you can't miss it and displayed forever until you press 'back' button

  • OK, I've definitely not that seen pop-up, that would annoy anyone!!!   I just checked and see that I have recorded >450 rides since I bought the RTL510.  If I were Garmin would start by collecting serial numbers of the RTL units that have seen the error and look for a pattern.   I've been in IT hardware and software for 40 years and my spidey-sense points to a batch of units with a part that is occasionally out of spec.    If it were software, with such a large population of devices I would expect there to be a lot more reports.  Such a failure mode would also make it very difficult to diagnose without getting a batch of suspect units recalled.   Back in the day I worked for a company that had $1m+ computers randomly rebooting.  It turned out to be memory chips from one manufacturer that were not error corrected and had bits flipped randomly by cosmic rays - I kid you not!  Hats off to the engineer that determined root cause for that one!  It cost many millions to resolve but was handled openly and resulted in increased customer loyalty - maybe Garmin could learn a lesson?