I got a good ride in with this yesterday. Calibration followed by out and back laps across the 520 floating bridge.
https://www.strava.com/activities/2017137357
Here are the numbers it gave me for slope and ground wind speed for 4 laps across the bridge.
Slope values are % grade (+ is uphill)
Ground Wind speed is in mph (+ is headwind, - is tailwind)
The delta between the measured slope riding eastbound vs westbound (on the floating bridge which is as flat as it gets) should tell me how well it is calibrated and should give an indication of its accuracy and repeatability.
Lap Slope East Slope West Wind East Wind West
1 +.07 +.29 +3.4 -2.9
2 +.10 +.13 +2.8 -3.7
3 +.15 +.17 +1.1 -0.5
4 +.17 +.19 +0.3 -2.5
It shows me going uphill in both directions, so clearly not zeroed out.
This was my first time calibrating it and it is quite sensitive. I expect it to be better next time. There is a definite learning curve involved.
On lap 1 I stopped to take a picture of a bald eagle perched on a DOT camera pole. Not good for aero testing! But this clearly shows up in the slope data (see charts below).
The HR plot on the charts below show the encoded cda data: cda = HR * 4 / 1000.
e.g. for a HR value of 80 the calculated cda = 0.320
This is kind of a hack, but Velocomp currently has to do this because ANT+ and BLE do not support an aero data channel, so they transmit aero data using the HR channel. This is likely to change in the next year or two as there are a number of companies that want this.
Below is the data recorded for lap 1 eastbound on the floating part of the bridge:
Below is the data recorded for lap 1 westbound (this is where I stopped to take a picture).
And this is how the AeroPod is mounted on the V20:
What I learned:
Mounting the sensor below the crank (just in front of the front wheel) is bad. Turbulence from the spinning wheel fouls the static pressure sensor port and makes the data useless. I tested this 2 days ago and it thought I had a constant 20mph tailwind.
Mounting the sensor on the boom as I did for this ride appears to be a good location aerodynamically. No indication that pedaling significantly disturbs the air flow.
Cda is not calculated when you are not pedaling (such as coasting downhill, even when coasting 30 mph) or when going slow uphill.
You can see this in the cda values (in the HR data plot) when the value is completely flat and does not change at all.
Testing at 20 - 22 mph for 2 or 3 minutes is not good enough to reveal subtle changes in cda. Being adjacent to the 520 freeway is not good for wind consistency either. Maybe I should test during rush hour when the cars are moving at less than 15 mph.
Max slope values that you see in GPS data should be completely ignored.
For example, rides in Strava based on GPS data show that the climb at the east end of this bridge peaks at 15%.
I now know that the max slope of this climb is only 8.8%. Shut-up legs
The initial calibration ride calculated my cda as 0.351 m^2. This is surprisingly high for a V20 but I compared it to what CyclingPowerLab estimates from this ride data and they both agree pretty well.
I can only hope it is correct. If correct, there is lots of room for improvement and I can only get faster!
Apparently, a floppy wool shirt, loose fitting shorts, sandals, 32-spoke wheels (and who knows what else) slow you down more than you can possibly imagine!