rruff wrote:
I've seen data from the Notio and Velocomp devices, and have not been impressed. Also the mounting location alone is a dead giveaway that they aren't intended for serious testing, since the influence of the rider+bike on airflow is too great.
Aren't you placing an anemometer in the same location ?
rruff wrote:
If you are computing CdA on the fly and not using laps, then you have to determine elevation to high precision. How do you do this? GPS isn't good enough, and neither is barometric pressure. Velocomp uses a calibrated accelerometer, but it's influenced by the tilt of the device relative to the road, which is going to vary depending on weight shifts, bumps, and vibration. Ordinarily they calibrate the tilt based on 5 min of barometric data. For instance if the accelerometer says your elevation change over the last 5 min is zero but the barometric sensor says otherwise, the tilt will be recalibrated to match the barometric data. Obviously this isn't ideal because the barometric pressure changes over time, plus airspeed tends to affect it on any of the devices I've used. On the Aeropod they stopped doing calibrations when in CdA mode, but that just reverts to the old way of doing things (iBike days) where you run with the initial (imprecise) tilt calibration and call it good.
There are was to get very high precision elevation change using sensor fusion algorithms. Using 5min of barometric data to calibrate an accelerometer is pretty primitive. Gyroscopes, accelerometers, magnetometers, barometric pressure and position can be used to correct each other. Drones and quad copters have been doing it for a while. How well Velocomp and Notio do it, I don't know.
rruff wrote:
nother one is the airspeed measurement. Let's say you've calibrated it really well, and airspeed will be accurate regardless of the conditions to +-1% (which would be extremely good IMO). That still translates to a +-2% error range for CdA, which is more than is acceptable for testing, and we haven't even looked at all the other variables we have to contend with.
Both of these issues can be dealt with using an out-back lap protocol. Elevation zeros out by crossing the same points, and your runs are used to perform the airspeed calibration.
Yes, an out and back helps a lots with overall/average CDA It also helps to calibrate your airspeed. I would further argue ii's not enough to calibrate your airspeed. There are other techniques to achieve equal or better results BTW, once calibrated I think you are overstating the impact of minor changes like hand position. Yes, go from 0 to 20 degree extension angle and you will need to calibrate, but not minor changes.
rruff wrote:
s much as I'd like to mount a simple unobtrusive device on my bike and get CdA values that are good enough for position and equipment evaluation and optimization... by just riding wherever I want... it isn't happening. Getting good actionable values outdoors in variable environmental conditions is tough even if you are using the most precise and accurate methods possible.
There ate still limitations of how to ride for calibration But you are not restricted to riding closed loops all the time.
Riding loops will always be better. But riding in a variety of configurations brings out data you don't always get in closed loop testing