AeroPod, PowerPod and Newton

During your ride, watts show as expected in the iBike screen. However, when your ride is downloaded the watts do not appear, and NaN appears for Crr in the main window. Or, watts appear in the screen, but when the command "Tools/Analyze Power..." is executed, the watts disappear.

A bug that we are working on now is the cause of this problem.

For Gen III units with this symptom, there is an incorrect number (zero weight) that has been mysteriously stored in the iBike's profile. We don't yet know why the value "zero" happens and we are investigating.

The profile stored in the iBike is downloaded automatically with each ride file. When the Analyze Power... command is executed, either manually in the "Tools/Analyze Power..." command, or automatically by the "Auto Fine Tune" preference, the power numbers disappear because of the zero weight bug.

We are working on a fix for this bug. In the mean time, here is how to fix the NaN problem without waiting for our bug fix.

1) Do NOT erase the ride file on your iBike that is causing you the NaN problems. If you already have erased this ride file, then do another short ride to get new ride data. This ride file, too, will have the bug in it.

2) Launch iBike 3. Go to the command Edit/Preferences... Uncheck the box that says "Auto Fine Tune Ride Data". When this box is checked your ride files are auto-analyzed. We do NOT want the files to be auto analyzed. Click the Accept button.

3) Now, download from your iBike the ride file that is causing problems. You should see your power data in the graph.

4) Go to the command Profiles/Edit Profiles...

5) Click the button in the lower left of the window that says "Extract". This command will extract the (defective) profile that is stored in your iBike.

6) You might get a message saying that this profile is already stored in iBike 3. If you get this message, then increase your friction number very slightly so you can store the profile. Click Accept. The Profile window will appear.

7) In the Profile Note, put the message "Repaired NaN profile". Give your profile name a slightly different name too.

8) In the Profile window, note the number that is in the Total Weight box.

9) Click the "Advanced Profile Settings..." button. A new window will appear.

10) In the new window, look at the Weight number in the top right corner. It will be zero; this is the source of the NaN problem and no watts problem. In fact, this number should be the same weight that you see in the main Profile screen.

11) Highlight the "0" in the Weight box, then type in the Weight you noted from the main Profile window. IMPORTANT: click the "Accept" button in the Advanced Profile window. The Advanced Profile Window will disappear.

12) In the main profile window, click the "Send to iBike" command. This will send the corrected profile to your iBike and get rid of the NaN problem for future rides.

13) To save the "fixed" profile, give it a different name in the Profile Name box. IMPORTANT: Click the "Accept" button to save this profile.

The steps above will get rid of the NaN problem for future rides, even when the rides are auto-fine tuned.

The NaN problem occurs when the "Tools/Analyze Power..." command is executed with a defective profile (i.e. zero weight). This command is executed automatically when the "Auto Fine Tune..." preference is set.

For your "defective" ride file, you can now use the Analyze Power command with the fixed profile you created. Use the command "Tools/Switch Profile After the Ride", select the profile that was created in the steps above, then click the Accept" button. When the Tools/Analyze Power... command is executed, you will no longer get NaN for watts.

We hope to squash this bug very soon and will keep you posted.

John,

I just had this bug today for the first time. Last weekend there were no problems and the only thing I did this week was try to use the iBike on the rollers inside on Tuesday. So, the only thing I did differently was turn the Trainer Mode On and then Off after the ride, maybe that caused the profile to have a problem. Just thought I would pass it along. Thanks.

Thanks, this is a very important clue!

I have seen this happen twice.

The first time it was NOT my first ride with trainer mode off after being in trainer mode. There were two days of outdoor rides following coming out of trainer mode where the iAero and iB3 worked normally post-ride. The one oddity about the ride where the profile changed is I was running short of memory and switched from 1 sec to 5 sec logging in mid ride (caused a trip reset and split the ride into two rides).

The second time it was my first day outdoors after being in trainer mode. The oddity about that ride was I did a fitness test in the middle of the ride. So I ended up with a warmup ride recorded, a small file of 14 seconds where the fitness test occurred (didn't fully record) and then a third ride where I finished out the session. If going in and out of fitness test mode is similar to a trip reset, then that is what I see as common between these occurrences.

These happened about 2.5 weeks apart (last one on Jan 10) and it has not occurred since.

PJBoyle

another thing that seems to cause that is when you change the tire with to anything outside the preset tire widths (I have tubulars so I was trying to manually set for 700x20).

When I had chosen one of the regular tire widths, the analysis went without a hitch.

This seemed to fix my issue as well. In addition to correcting the weight in the extracted profile, I also had to set the riding tilt back to what it was in the original profile, which meant that I had to use the weight from the original profile (not the ride) to get the correct CRR.

I'm assuming that "Auto Fine Tune" (auto-analyze) will work on future rides because of the newly stored profile, but it will never work on the old rides that are still stored in the iBike. Correct?

You can always analyze old rides.

If you want to change profiles for older rides use the Tools/Switch Profile after Ride... command.

I experienced a similar problem after installing 3.08. Followed the fix and it worked. I also had the trainer mode on before 3.08 and turned in off after installation.