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

MARQ - 5.64 Beta Release

Hello MARQ customers,

The newest MARQ beta software is now available for your upcoming adventures!

MARQ Adventurer: https://www8.garmin.com/support/download_details.jsp?id=15170
MARQ Athlete
https://www8.garmin.com/support/download_details.jsp?id=14864
MARQ Captainhttps://www8.garmin.com/support/download_details.jsp?id=14868
MARQ Commander: https://www8.garmin.com/support/download_details.jsp?id=15182
MARQ Driverhttps://www8.garmin.com/support/download_details.jsp?id=14870
MARQ Expeditionhttps://www8.garmin.com/support/download_details.jsp?id=14872

Instructions for installation are available below the change log on each of the above pages.


5.64 Change Log Notes:

  • Fixed an issue where the map would intermittently stop updating during an activity.
  • Fixed an issue with data fields editing.
  • Brought in improvements and bug fixes for music. 
  • Made other bug fixes and code improvements.

Current beta peripheral software version numbers below. New versions are indicated in red.

GPS: 2.60
Wi-Fi: 2.60
Sensor Hub: 3.10
ANT/BLE/BT: 4.30

Please note, the beta updates released on these forums are not suitable for APAC region devices.

Please send all bug reports to [email protected], and indicate which model of the MARQ Collection you have in the subject line.

  • For those of you who have encountered issues with Optical Heart Rate accuracy:

    As you can see from the change log notes, this version is only implementing fixes for indoor cycling. We have also been working on additional improvements for other use-cases, which should be available in the next few weeks.

    We’d love for this feature to be as accurate as possible. If you are still experiencing accuracy issues with Optical Heart Rate after installing this beta update, we would like to collect some information from you to investigate further. Please email the following details to [email protected]. Please note that we may not respond to your email unless we have further questions for you.

    • Please make the subject of the email: MARQ - HR Feedback - your first name
    • Under what circumstances did you encounter poor HR performance?
      • e. indoor cycling activity, all-day tracking, hiking, etc.
    • Please attach the following files to your email
      • The relevant activity .fit file, if the issue occurred during an activity
      • The GarminDevice.xml from the Garmin folder
      • The Settings.fit file from Garmin\Settings
      • All files in the Garmin\Monitor folder
      • Any pictures/screenshots/links to information in Garmin Connect that help explain the issue
    • Please also let us know if we have permission to access your Garmin Connect account. This will allow us to investigate your report faster, if we identify that other data is necessary for investigating. You do not have to grant us this permission, but doing so will allow us to be as thorough as possible in our investigation.

    Thanks,
    Mel
    Outdoor Software Quality Team

  • It it a complete update from 5.30 , or do we hve to install all previous beta ?

  • Just installed the 5.64 beta and did a short try of the map bug (not updating). It worked in this case. Will test more tomorrow. 

  • Have done a couple of sessions now. Both with GPS and without. A stuctured training session in SkiErg (no problems), weight session (no problems), bike (short commute, 8km) using an earlier activity for navigation. No problems.

    But as I used a route for navigation and paused with resume later, the watch failed to re-calculate ETE and ETA, but everything else worked (altitude curve, distance left, map updating). Probably not a bug, but an indicator of GPS re-acquisition after a pause would be appreciated.

    Last find: there is no stress data for quite some time after a training session. Also - and this probably relates to Connect - I have no updates of VO2max since a month back, although I have new data in the watch.

    Will keep an eye on battery draw, and BT connection. As I have my BT Jabra sport elite connected to my phone, the MARQ looses connection occasionally. A BT flip off/on is required.

  • I am afraid I found another possible bug, as I try different use cases.

    The watch fails to calculate a proper altitude curve, as I use the Navigate/go-to function. Everything else seems to work, TBT is generated, re-routing works as I go off the initial route, ETE, distance and ETA works even after pausing and "resume later", but the projected altitude curve is basically flat, with much too low ascend numbers.

    But to be fair, I have only tried this twice during my short daily bike commute to and from the office, and once just calculating the route.

    In a few weeks I will be able to try out skiing modes, both downhill and XC, with rapid and high shifts in altitude. I understand from elsewhere on the forum, that some users have problems relating to altitude. Will be nice to check out the ski map as well.