rruff wrote:
I've been playing with VE with the addition of wind. I currently guess a wind speed and direction and tweak that so the elevations match reality. I have to use a constant wind for the whole run though, which isn't ideal.
I suppose you could use the iBike airspeed for that and see how it works out. You'll need to tweak it so that the distance averaged wind cancels out, but it should more accurately account for fluctuations.
I used my iBike with Powertap for VE back around 2007-2008. The problem is that the iBike data is so coarse that it really doesn't get you very much. It didn't really help me narrow down CdA/Crr pairs; about all it helped for was clearly indicating when a run should be thrown out due to wind.
If iBike had provided the abilty to download raw data for post-processing, some of these difficulties could have been avoided. I asked them about that, and their response was ridiculous; along the lines of "if we allow that people will figure out what our proprietary algorithms are". Yeah, those algorithms which everyone who's had Physics 101 already knows.
One of their other big failings was that they never provided any information on the yaw response of the iBike. I had a rough idea, just from turning the mount on the bars, but a controlled test should've been done by iBike. This was another issue that I asked them about with no substantive response.
And of course they should've added another DP sensor to provide 2-axis wind data. It would've been so easy for them to do it, and that would've been hugely helpful for VE work. And yeah, this was suggested to them and never got traction.
They seem to be more interested in marketing hype than real performance, and this final campaign is the evidence of that. It's sad to see all that potential wasted.