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

Ant+ needs a restart

Happened again tonight.. Ant+ sensors won't connect unless I restart the watch. It then works fine for a week or do, then I notice again that I need to repeat the restart. Anyone else getting this?

0 Dani over 5 years ago

yes, i notice the same, but it happens when i am wearing the HR for a long time before to start the exercise

0 Gregor A. over 5 years ago

Yes, the same here. I reported the problem already by email...

0 Former Member over 5 years ago

Yup. Reported to tech support. Was told it was a known bug.

0 Mirko_Italy over 5 years ago

It happened yesterday with the chest strap. Rebooted and then everything was fine.

0 jmto over 5 years ago

Yes. This is pretty nice HR GPS watch, which fails HR without reboot, and GPS with OWS :D

0 kaz911 over 5 years ago

It has been a bug since the watch launched - It has become better though. In the beginning it was EVERY time I started an activity I had to reboot to get ANT+ sensors.

0 gingerneil over 5 years ago in reply to kaz911

ouch - I didnt realise it had been going on that long! I've had mine for about a month and dont always use external HR. I only really notice when I am missing Runscribe data as the HR just defaults to the device HR!

0 2goBeyond over 5 years ago

This is new to me. I personally haven't had that problem...but I actually was coming to the forum to see if anyone was noticing a lag with ANT+ HR info during an activity, and then I saw this thread.

I had to take about a week off from working out (not hurt, other reasons) and before I did I downloaded the latest Beta. When I came back two days ago, I noticed that the reporting feels like is 7-10 seconds behind what is actually happening (I'm using an HRM Dual). Did a HIIT component to a routine yesterday and my HR after doing a section was the same at the end as it was when I started. It then began to rise during the cooldown and then started to drop again WHILE I was in the next phase?

Instead of not connecting for my watch (my second one, so mine might be a later built one?) I'm just getting a lag? It's almost moot to report it to Garmin as they're rolling out 2.80 as I type this.

0 Mirko_Italy over 5 years ago in reply to 2goBeyond

2goBeyond it seems that yours is another type of bug. Did you used maybe a "structured workout" using the "my workouts" function with "heart rate" as target? It could be that this lag is due to the interval heart rate gauge. You could have a look at the other thread

Bug in the interval workout screen with "pace" as target. The watch doesn't use instant pace.

where it seems to me that the interval workout is implemented in a strange way by Garmin (using lap pace and lap heart rate instead than instant pace and instant heart rate.

But in this case it could be not a bug, but a choice of Garmin by design

0 2goBeyond over 5 years ago in reply to Mirko_Italy

Mirko_Italy said:
Did you used maybe a "structured workout"

I hadn't been during the above-mentioned workouts, but thanks for posting that info, I wasn't aware of that.

Mirko_Italy said:
It could be that this lag is due to the interval heart rate gauge.

I AM using a CIQ HR data field and that's possible, but both Aerobic and Anaerobic also seem to be getting thrown off, In particular, Aerobic.

Mirko_Italy said:
But in this case it could be not a bug, but a choice of Garmin by design

I sure hope not, because it wasn't functioning like this on my watch before the beta and might be something changed on it.