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

Forerunner 945 Beta 2.72 is available

The download for this beta can be found here

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 2.70 to 2.72:

  • Added ability to enable wrist-based heart rate for swimming (pool and open water). This feature is enabled by default. To enable/disable this feature: 1. Open Menu 2. Scroll to 'Wrist Heart Rate' and enter menu 3. Scroll to 'While Swimming' and toggle to 'On'
  • Fix swimming cadence/stroke rate
  • Improvements to PulseOx settings
  • Various fixes for ConnectIQ

Installation Instructions

  1. Connect your Forerunner 945 to your computer using the USB cable.
  2. Download and unzip Forerunner945_272Beta.zip. Place the GUPDATE.GCD file in the \GARMIN folder of your device's internal storage drive.
  3. In Forerunner945_272Beta, go to the RemoteSW folder. Place the GUP3114.GCD file in the \GARMIN\REMOTESW folder of your device's internal storage drive.
  4. Disconnect your device from the computer, approve the update on the watch, and wait for the update to finish.
  5. If you would like to revert to the last public release software, place the GUPDATE-270.GCD file in the \GARMIN folder. Rename GUPDATE-270.GCD to GUPDATE.GCD before disconnecting your device. To revert the RemoteSW, place the RemoteSW\Downgrades\GUP3114-230.GCD in the \GARMIN\REMOTESW folder. NOTE: If you revert to an older version of software, all of your settings will be reset to defaults.
  • It'd be interesting to see her HR not using WHR on the bike, I've not found it good at all. In fact last night on a indoor turbo, my Polar OH1 was reading 121, the wrist 80 bpm!!

  • Golf auto shot tracking very unreliable again with this firmware :( gone backwards. 

  • I have found this to be the case for me as well. I use the HRM-Tri almost exclusively. On the rare occasions that I have used OHR for swim, bike, or run I have found that for the bike the numbers are either wildly high or very low depending on my position on the bike. Running, the numbers from the OHR are generally correct but slow to react to changes. Swimming seems to be the closest between the HRM-Tri and OHR for me, probably because I tend not to do too many varying speed workouts and therefore I don't see the lag in HR variation from changes in exertion. I have not yet tried to record one activity with the HRM-Tri while simultaneously recording with the 945 OHR. Maybe I'll try that in an open water swim today... should be interesting if nothing else.

  • Has she done a pool or bike workout with a chest strap? Comparing a pool swim OHR to a bike workout OHR is problematic at best, even without considering the possible inaccuracy of the OHR sensor. For me the bike OHR is the absolute worst for accuracy and I can get a huge change in the reading just from shifting my grip on the handlebars. By huge shift I mean it will go from 120bpm to ~225bpm (my max HR is ~185bpm). Also Max HR and percieved exertion between disciplines is pretty variable depending on the person as well... 

  • Former Member
    0 Former Member over 5 years ago in reply to Damian.Holt
    2 things, 1 it's still in beta, 2, if it doesn't work for you disable it and move on.

    1.  I'm aware it's still in beta.  I installed it.  2.  Disable it and move on from what?  Testing it?  Isn't that the point of adding it to the beta?

  • Former Member
    0 Former Member over 5 years ago in reply to Chabier
    What  option do you prefer, a graph with a 170 bpm when reality is 160 or nothing at all?

    You make it sound as if it's as simple as selecting your example and it isn't.  In the test I've conducted my HR wasn't "slightly" high.  It was 25-30 bpm higher.  Secondly, I don't have to settle for nothing at all because I'm fully aware that my Tri will give me fairly accurate results.  I understand the oHRM works well and poorly for different people in all activities.  It obviously works better for you while swimming then it does for me, but that doesn't mean the results are slightly off for everyone.  Isn't the purpose of adding it to the beta so everyone can test it and post their results?   Shouldn't Garmin hear all the results and decide if it's a permanent feature before people respond with "if you don't want it, turn it off" since Garmin clearly ask in the notes that if there are any issues found to notify them?  

  • And because of that, I quoted the word slightly. Wink

    I know beta is not perfect (obviously, it´s a beta) and it have to be adjusted, but equal I can´t say it´s perfect because for me works right, you can´t say is useless because for you doesn´t work. Here we are in the same team and want this feature to work properly. 

  • Former Member
    0 Former Member over 5 years ago in reply to Chabier
    you can´t say is useless because for you doesn´t work

    I think you misunderstood me. I said I find the data useless because my HR records 25-30 bpm higher.  Personally I wouldn't define that as slightly off.  For me, HR could be showing me I'm in zone 5 when I'm actually in zone 2.  I also said I understand it works well for others. I'm speaking for myself and not a generalization.  I would love to ditch my Tri while swimming, but at this point the oHRM isn't doing it for me.  Too further comment on your statement that you disagree that off data is useless.  You're looking at it from your perspective.  If the HR reads 10-15 bpm off for you, that may be acceptable to you.  But the oHRM for swimming is not for swimmers alone.  What about someone who's trying to lose weight and they're incorporating swimming in their training?  Better yet, what about a wrestler or boxer who needs to maintain or cut weight for their weight class and they also swim while training?  Counting calories is very important to them.  If their HR zones are set correctly, 15 bpm will change HR zones and give false data for calories burned.  The longer the duration of their swimming workout, the larger the discrepancy.  In a case like this, that data would be useless.  

  • What about someone who's trying to lose weight and they're incorporating swimming in their training?  Better yet, what about a wrestler or boxer who needs to maintain or cut weight for their weight class and they also swim while training?

    Well, in both cases, before the beta they couldn´t obtain no data at all, which in my opinion is worst. If my readings are 150 and I know that this data is over rated in 10-15 bpm, I can guess what kind of results I have obtained with the swim session. If I have no data, I´d don´t have a clue. 

    This is not a battle for who is right or wrong. I know is not perfect, but I prefer that than nothing. And that is my personal opinion. Other person may think that for that kind of performance maybe is better to turn it off. Or simply, don´t pay attention to data. I just think that having the feature is better than don´t have it.

  • Former Member
    0 Former Member over 5 years ago in reply to Chabier
    Well, in both cases, before the beta they couldn´t obtain no data at all, which in my opinion is worst

    We agree that we both want the oHRM to work with swimming.  There's no disagreement there.  We'll disagree that off data is better then no data.  This is based on personal preference.  For you, data that may be off is acceptable.  Others, like myself, are stickler's when it comes to their data.  Let me give you an analogy.  Lets say you're driving your car down a 10 mile stretch of road and the speed limit is 40 mph.  Your speedometer is off.  Please convince me; the traffic cop who's a stickler for the law and is writing you a ticket for speeding, that your off speedometer wasn't useless and it was better than not having a speedometer at all.  If the readings on the oHRM were a definitive and a constant (let's say always 10 bpm higher) then people could work with that and adjust those readings.  But that's not the case.  Sometimes the readings are close and other times they're way off for many.  I don't see the consistency I do when wearing my Tri.  If I were the driver in my scenario, I wouldn't know if I were travelling at 45, 50 or 55 mph in that 40 mph zone.  You've said several times, prior to the betas, there was no data at all.  This isn't entirely true.  Data could be obtained using a HRM-Swim or Tri and the same HR data you're receiving now with the beta could be obtained using the "other" activity profile.  These were available on the 945 from day 1.