Will the HRM-Run Strap help with BAttery life?
Will the HRM-Run Strap help with BAttery life?
This make me think, should I remove the wallet then.
It's my understanding the sensor light stays on only if you enter your Garmin Pay pin code. This is a safety precaution, so if the watch…
Yes, power consumption of the ANT+ connection is less than running the OHR.
But given the battery life of the 945 is pretty massive anyway, I wouldn't have thought this was a necessity or significant advantage…
power consumption of the ANT+ connection is less than running the OHR
Confirming this: on the Fenix 6 line (soon to be 945), power-management modes let you test the effect of different settings…
power consumption of the ANT+ connection is less than running the OHR
Confirming this: on the Fenix 6 line (soon to be 945), power-management modes let you test the effect of different settings.
Switching wrist-optical-HR (OHR) OFF and external sensors ON results in slightly better battery life. Full discussion on the F6 power modes: https://forums.garmin.com/outdoor-recreation/outdoor-recreation/f/fenix-6-series/212945/power-modes-vs-ultratrac-vs-expedition
Given chest-strap HRMs have >1-year of battery life on a CR2032 and are significantly more accurate than OHR, I tolerate wearing one for anything beyond a stroll in the park.
This make me think, should I remove the wallet then.
It's my understanding the sensor light stays on only if you enter your Garmin Pay pin code. This is a safety precaution, so if the watch is removed, you must re-enter the pin to use Garmin Pay again. It shouldn't keep the sensor on if the pin isn't entered unless something has changed in a past update.
An HRM-RUN will cause higher battery use on a Garmin device than a normal HR strap without running dynamics. To calculate stride length (amongst other things) the watch has to transmit speed data to the HRM-RUN (or RD pod) on ANT+. This will use more battery than using ANT+ in receive mode only.
What data-screens are people using when running with an HRM-Run?
A theory: it's not the data from the RD data that's causing higher power draw but having a dynamic data field like GCT or balance.
Try the it with nothing but time and distance up on the screen, see how it fares.