Oregon HR data

[KenF]

I've been going round and round with Garmin Tech support regarding some flakiness I'm experiencing with HR recording on an Oregon 550 . They, of course, have resorted to the knee-jerk "blame the non-Garmin" software approach even though, in the GPX fles on the unit (100% Garmin created), there are dropouts where no HR data appears. And that occurs  despite the HR being shown on a handlebar-mounted Foretrex at the same time.

But that brings up a question. 

The corresponding .gpx files I get from TF have an HR value of 255 at those dropout points.  So, I am really just curious, is that how TF is handling the non-existent Garmin data?

KF

[ScottMorris]

That's interesting about the data showing up on the concurrent Foretrex.  I've seen some flakiness with my HR and Dakota 20, but haven't paired up my forerunner at the same time to double check it.

255 is the value for 'no HR' in TF.  However, if it sees that value it shouldn't be writing it out, it should just not write out an HR value.  Are you seeing 255's in GPX files?

[KenF]

That's interesting about the data showing up on the concurrent Foretrex.  I've seen some flakiness with my HR and Dakota 20, but haven't paired up my forerunner at the same time to double check it.

Just to note -  If the Foretrex were doing its job and recording HR (Garmin says they're working on it), I would not have been carrying the Oregon as backup. 

255 is the value for 'no HR' in TF.  However, if it sees that value it shouldn't be writing it out, it should just not write out an HR value.  Are you seeing 255's in GPX files?

Yes, I have one file with over 5000 recorded 255's.

KF