Garmin - Powertap Users

[Jakkals.]

Hi guys, from reading a bit, the new firmware update V2.7 doesn't have the auto zero function any more.

 

would you recommend updating to this version? How would this affect powertap readings?

 

Thanks

[V12man]

Hi guys, from reading a bit, the new firmware update V2.7 doesn't have the auto zero function any more.

 

would you recommend updating to this version? How would this affect powertap readings?

 

Thanks

 

Which Garmin version are you using?

[Jakkals.]

I will let you know tonight.

[Jakkals.]

V2.60

[Helpmytrap]

From what I understand, if Auto Zero is on, it doesn't full bring down your average power when you freewheel. It might be the other way around...

 

I'm not 100% sure as I only received my Powertap this evening and haven't checked it all out yet.

[Agteros]

Auto zero = reset when no power is applied. I am not sure whether this is done feet on (trace pressure) or off pedals (no pressure)

Exclude zeroes = does not bring zero readings into calculation for averages - Makes you feel and look better than you are

 

810 is on v2.8

510 is on v2.8

800 is on v2.7

500 is on v3.2

[V12man]

Auto zero = reset when no power is applied. I am not sure whether this is done feet on (trace pressure) or off pedals (no pressure)

Exclude zeroes = does not bring zero readings into calculation for averages - Makes you feel and look better than you are

 

810 is on v2.8

510 is on v2.8

800 is on v2.7

500 is on v3.2

 

I am using 3.2 on a garmin 500 - takes a few moments longer to acquire satellite links, but (although unscientific) I think the battery life is better than 3.0 which I was using before - and for powertap users it's a bit cleverer than 3.0 - it asks you if you want to calibrate the PM when you start it up - previously you had to navigate the menu to calibrate - which is a PITA.

 

There are recommendations on the settings to be used in one of the many books I have on the subject - but the key one is to include zeros in your data - otherwise your averages go out - and they do...

 

There is a way to check your garmin calibration here - if you are really interested in accuracy...

http://www.cyclepowe...-check-76-c.asp

 

The settings I have in mine are:

 

Cadence - non-zero average on - I only use instant cadence on the screen, so average display is meaningless to me

Power - non zero average on (I don't use average power on the display - I find 3 sec works for me)

Data recording - Every second (this is a key setting to get data analysis correct)

 

You can see on Garmin connect if yo have it right - bottom left section on additional information:

Additional Information

http://static.garmincdn.com/apps/connect/image/devices/edge500.png Device: Garmin Edge 500, 3.30.0.0 Elevation Corrections

http://connect.garmin.com/api/activity/component/details/style/images/popup-tl.png http://connect.garmin.com/api/activity/component/details/style/images/popup-tr.png

• 
  What are Elevation Corrections?
  Elevation Corrections cross reference the horizontal position (latitude/longitude) provided by the GPS with elevation data that has been acquired by professional surveys. When corrections to elevation data are made, each trackpoint of your activity now contains the elevation from the web service, not the elevation provided by your GPS device.
  Garmin Connect selectively applies corrections to depict a more realistic representation of your elevation experience. Activities recorded from devices without a barometric altimeter are enabled with Elevation Corrections by default. Alternatively, activities recorded by devices with a barometric altimeter generally contain accurate elevation data and therefore Elevation Corrections are disabled by default. For those users who are familiar with the MotionBased Gravity service, this is the same service.
   
  

http://connect.garmin.com/api/activity/component/details/style/images/popup-bl.png http://connect.garmin.com/api/activity/component/details/style/images/popup-br.png :

Disabled http://connect.garmin.com/api/activity/component/details/style/images/loading-spinner.gif Power Average Calculations

 

http://connect.garmin.com/api/activity/component/details/style/images/popup-tl.png http://connect.garmin.com/api/activity/component/details/style/images/popup-tr.png

• 
  What is Power Average Calculations?
  We include zero-data power samples when calculating your average power. For example, if you go 50 seconds (providing 50 1-second power data samples), then pause for 10 seconds (providing 10 zero-data power samples), we divide the total power data by the total time (60 seconds) of your activity.
   
  

http://connect.garmin.com/api/activity/component/details/style/images/popup-bl.png http://connect.garmin.com/api/activity/component/details/style/images/popup-br.png :

 

Use Zeros Summary Data: Original

[Jakkals.]

I am using 3.2 on a garmin 500 - takes a few moments longer to acquire satellite links, but (although unscientific) I think the battery life is better than 3.0 which I was using before - and for powertap users it's a bit cleverer than 3.0 - it asks you if you want to calibrate the PM when you start it up - previously you had to navigate the menu to calibrate - which is a PITA.

 

There are recommendations on the settings to be used in one of the many books I have on the subject - but the key one is to include zeros in your data - otherwise your averages go out - and they do...

 

There is a way to check your garmin calibration here - if you are really interested in accuracy...

http://www.cyclepowe...-check-76-c.asp

 

Thanks, makes sense to include zero's. just worried that if the function isn't there to manually select, how would I know what setting is used.

[Helpmytrap]

That calibration value is obviously relevant to your specific power meter, so I take it that there is no right or wrong range for that value to fall in? Reason why I'm asking is because my neighbour's value is in the 500's and mine is 8112.

[The Anteater]

That calibration value is obviously relevant to your specific power meter, so I take it that there is no right or wrong range for that value to fall in? Reason why I'm asking is because my neighbour's value is in the 500's and mine is 8112.

This is true. Some PMs, like the Quarq and SRM report the torque offset (that's usually in the range of +-500). Others, like Powertaps just report the ANT+ serial number.

[Helpmytrap]

...

The settings I have in mine are:

 

Cadence - non-zero average on - I only use instant cadence on the screen, so average display is meaningless to me

Power - non zero average on (I don't use average power on the display - I find 3 sec works for me)

Data recording - Every second (this is a key setting to get data analysis correct)

...

Luckily I uploaded an activity to PowerAgent last night, while uploading it states that it cannot analyse the data because of inconsistent data recording methods produced by "Smart Recording." My Double Century comes up as a 4min ride time event.

 

So I will at least have the right settings (I hope) for my first PM ride.

[V12man]

Thanks, makes sense to include zero's. just worried that if the function isn't there to manually select, how would I know what setting is used.

 

As long as you have the data stored with zero's then you are ok (because the tools like training peaks etc recalculate the numbers for you) - this is different to the calibration auto zero feature (which I have never used)

 

When on the calibration screen on the 500, you can see the actual torque being applied, so I always calibrate the device with feet off and cranks horizontal.

[Jakkals.]

with so many power users, we should be getting that power tread going again.

[V12man]

Luckily I uploaded an activity to PowerAgent last night, while uploading it states that it cannot analyse the data because of inconsistent data recording methods produced by "Smart Recording." My Double Century comes up as a 4min ride time event.

 

So I will at least have the right settings (I hope) for my first PM ride.

 

Dump it into Garmin connect - you should get better results there - no perfect, but better.

[Helpmytrap]

As long as you have the data stored with zero's then you are ok (because the tools like training peaks etc recalculate the numbers for you) - this is different to the calibration auto zero feature (which I have never used)

 

When on the calibration screen on the 500, you can see the actual torque being applied, so I always calibrate the device with feet off and cranks horizontal.

I take this is your NP?

[Jakkals.]

As long as you have the data stored with zero's then you are ok (because the tools like training peaks etc recalculate the numbers for you) - this is different to the calibration auto zero feature (which I have never used)

 

When on the calibration screen on the 500, you can see the actual torque being applied, so I always calibrate the device with feet off and cranks horizontal.

 

Golden cheetah include zero's. which I prefer. it makes you realise how much coasting goes into a ride, which is training time wasted.