Current issues

-Running dynamics issues with massive gaps in the data recorded

If you have a look at my last post in the Owners thread, I'm having no problems with Running Dynamics from my HRM Run to my MARQ Athlete. So it may be worth getting a replacement HRM Run strap first (probably easier and less hassle than getting a whole MARQ unit replaced at the moment - given the relative availability at this time) and only if that doesn't work go down the replacement MARQ unit road.

-Watch and phone refusing to communicate, only thing that fixes it is unpairing and pairing again- I've had to do this 3 times in less than a week!!!

I seriously doubt your unit is defective if it does work most of the time. This happens across all my Garmin devices from time to time (the ones that I still have: MARQ Athlete, Fenix 5+, Fenix 5 and Fenix 3). I think it might actually be an iOS thing in my case, as sometimes it needs the Bluetooth to be turned off then on on my phone, or even a phone power cycle, to get things going again. I don't think this Bluetooth connection thing is perfect in any area yet; for example, it doesn't work flawlessly every time I get in to my year old BMW car either.

Crispin_Ellisdon I have a new HR strap on the way. Sending current one back.

As for Bluetooth, restarting my phone and or watch does nothing...

With regards the earphone thing, I get a perfect connection with my Aftershokz Trekz Air headphones, regardless of side. My (cheaper brand) Groov-e GV-BT800 headphones seem to get a few very short signal drops early on in a run, then work fine after a couple of minutes outside, even when the watch is on the left and the opposite side to the headphone's transmitter side (right); I get the same performance with my Fenix 5+. One thing that is worth noting is that different people will get different performance depending on their environment. For example, when I went running in Central Glasgow last year with the Fenix 5+ and the Groov-e headphones, I got a lot more cutouts than when I do at home; presumably because there is far more signal noise at the Bluetooth frequency in a busy central city location. So, unless the person with the 945 is running in a similar environment to you, it may not be as straight forward as 'it works for them, so the 945 is better'

I'll be interested to know what happens when you get a replacement HRM Run. If that doesn't work, then your concern there is some hardware issue with the internal antennae for BLE/ANT should rise up the likely cause of the issues list. I hope you get this sorted as I'm sure it's detracting from your experience of owning what is (for me) a cracking good sports watch.

If you have a look at my last post in the Owners thread, I'm having no problems with Running Dynamics from my HRM Run to my MARQ Athlete. So it may be worth getting a replacement HRM Run strap first (probably easier and less hassle than getting a whole MARQ unit replaced at the moment - given the relative availability at this time) and only if that doesn't work go down the replacement MARQ unit road.




I seriously doubt your unit is defective if it does work most of the time. This happens across all my Garmin devices from time to time (the ones that I still have: MARQ Athlete, Fenix 5+, Fenix 5 and Fenix 3). I think it might actually be an iOS thing in my case, as sometimes it needs the Bluetooth to be turned off then on on my phone, or even a phone power cycle, to get things going again. I don't think this Bluetooth connection thing is perfect in any area yet; for example, it doesn't work flawlessly every time I get in to my year old BMW car either.

Just did a run with a fresh battery on the HRM-Run and the result is the same. Still getting running dynamics dropouts left, right and centre.

https://connect.garmin.com/modern/activity/3621889343

I wonder if there is a connection between these dropouts and the Bluetooth earphones issue I'm having.
??????
I will be contacting my dealer first thing tomorrow but it is disappointing that I am seeing a hardware issue so early on...especially with it occurring across two different firmware versions.

Garmin's support team that I have been emailing from the start have been completely silent on this, which isn't reassuring.

So it's either that your HRM Run hardware is dodgy or there is a some sort of fault with your MARQ unit (hardware or software). Is there anyone you know who has a Garmin watch that works with a HRM Run that you could test your HRM Run unit with? That would either confirm or discount that there is a fault with the HRM Run. If it's not the HRM Run then you can start engaging with Garmin Support or Jura from a position of confidence. Something you could try that doesn't need anything beyond what you have with you right now, is a full Master Reset; If you're willing, I'd suggest the Secondary Master Reset described here https://support.garmin.com/en-GB/?fa...k926atAssdJYm9 (copied below) and then set everything up from scratch again afterwards (I know some people like to backup and restore some settings, but from the few times I've restored the settings on previous Garmin watches, it has just brought the error I'm trying to eliminate along with it). This may or may not fix your issues, but it's easy to do and at least it discounts that it's any kind of software issue (given the rest of us are fine on the same software and devices).

Secondary Master Reset

• Ensure the watch is powered off
  
• Press and hold the Down, Start, and Back buttons
  
• Power the watch on while holding these buttons
  
• After the first beep release the Start button
  
• After the second beep release the remaining buttons
  

Thanks Crispin_Ellisdon I will give it a go and perform a master reset. Not much to lose really...

Done- did a secondary reset, let's see what happens...

https://connect.garmin.com/modern/activity/3623061148

Quick run with a new HRM-Run battery after a secondary reset. Issues still persist

I don't suppose you have another ANT Heart Rate strap you know definitely works (doesn't have to be Garmin branded or have RD)? If you turned the WHR off completely in the settings and ensure the alternate strap is paired before going for a run, then the MARQ can only use the strap for heart rate and it would be pretty obvious if the MARQ drops the signal. If that works, then you know it's you're HRM Run that's broken, but if the MARQ drops that alternate strap's signal, then it's time to engage with Garmin Support and/or Jura.

I am getting a replacement heart rate strap today. Should that fail I will be requesting an exchange.