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

Pace effected by 'Cadence' rate??

I have noted on quite a few runs that my pace is very jumpy at times on the garmin connect site when looking things over after a run... but it was during times of fairly average pace.

I then notice that my cadence during those moments also dropped for a moment (from 190/180 to 80/100) (coinciding with pace dropping by 1-3min pace). I know cadence on the 235 can set the pace/distance (indoor running, or while in tunnel(?) mid outdoor-run). Is this my watch trying to cross check my GPS-speed with the cadence even while outside in open skies mid run???? Like it is doing a GPS+Glonass+Cadence calculation of some sort for distance/pace? Of course it could be that I am in fact fluctuating a bit in pace (while I was thinking/working on my stride...or switching from path to grass...but doubt it)

This was in my normal running areas... well into the run so reception should have been at or near 100% strength.

Is there a way to see strength somewhere, the little bars always goes to full green pretty quick, would be great to have a % strength reading up at the top (or number of satellites like old handheld gps's)? I typically stand out at the corner (warming up a bit) for a minute maybe even if it said GPS locked right away.

Any insight or tips ?

0 Max556 over 8 years ago

I've just recently noticed (last couple weeks) that my pace graph starts waaay low and jumps around for the first 5 or so minutes on some runs, then it corrects itself. My first lap is often my best pace time. My lap pace times seem correct and I feel that my pace remains fairly constant. It seems the graph isn't reading/displaying the data correctly perhaps?

Max

0 Josip7 over 8 years ago

The thing I noticed from 4.20 is that pace definitely wrong, both on the watch and later online. For instance, on 1 km stretch it showed pretty much constant 4:20 but looking at lap time it's 4:05. It's seems to be a bug that I warned about couple of months ago and that got fixed. Sadly it reappeared in 4.20.