New 6.0 software

[GWPOS]

i looked at the new version and it is really nice if you understand the different aspects of the IBike power meters. There is one problem though now. If I analyze my ride/route it more than doubles mu average power. It went from 220 or so to over 400watts. I f I check the calibration using the new feature it only changes a few watts. Again it is just the analyze route feature that is doing such a drastic change.

iBike_10_04_2011_1740_30_Miles.csv

(1.63 MiB) Downloaded 439 times

[travispape]

We just discovered that there was a nasty bug introduced in 6.0.0 for those who do not have cadence data. Customers with cadence data are ok--this only affects those without cadence data, both GenIII and iDash +Power.

(I know the ride file you posted above has cadence data, but it must have been acquired with a different device and merged into the iBike file. That doesn't get around the bug.)

Note that this actually doesn't have anything to do with the new Check Calibration feature.

I will try to get a build out within the next 24 hours to fix this.

Travis

[GWPOS]

You are right, I merged my Garmin file to the IBike file. Another thing I have been having a problem with since a few upgrades ago is that if I merge data from my Garmin it will not show my HR/Cadence data in the IBike software until I go and click on the show button and then change it to show HR in small or big (depending what it was on previously). I then can hit ok and my data will show on the screen. I told John about this a few months ago, maybe even longer.

[travispape]

I fixed a bug related to this recently. Are you sure it is still a problem?

[GWPOS]

Yes it still does it. I just tried again to make sure. I have attatched a Garmin file and the IBike file that goes with it for you to try.

iBike_10_04_2011_1740_30_Miles.csv

(1.37 MiB) Downloaded 479 times

10_4_2011 5_39_24 PM_history.tcx

(846.8 KiB) Downloaded 507 times

[travispape]

Yes it still does it. I just tried again to make sure. I have attatched a Garmin file and the IBike file that goes with it for you to try.

Ok, the bug is squashed for the next release. Also, it won't bother you about adding cadence data when the original data does not contain cadence data.

Travis

[GWPOS]

Sounds good to me. Thanks.

[lorduintah]

Possible subtle bug regarding elevation corrections.

When is the right time in an analysis to correct for elevation?

If I go and adjust the iBike settings of a ride - and change the starting elevation to correct for an improper value, the plots get corrected.

Then say, I go and get a barometric correction. The elevation readings (on the plot) go back to the original ride AND I do not seem to be able to set the elevation to the corrected starting point again. When I bring up the iBike settings screen, the right (changed to) value is what I had modified the altitude to, but he plots refuse to update. I believe that correcting the barometric pressure FIRST allows the elevation to be changed. So I suspect that both logic flows were not accounted for in programming.

Perhaps Travis can take a look at the code logic and see if there is a bug.

Tom

[still-chasing]

Can someone please explain the new feature "check for calibration"? should the needle on the "significance in profile" more to the left or right?

I input my information in the "startup wizard" and did a cal ride right after as the video suggested. I got a "bad cal" on the first try so I did another and another a total of 3 each producing a "bad cal". Did a tilt calibration and wind cal before doing the cal ride. Any suggestions?