Newton+ wigged out on ride(s)

[rstrom]

Over the past two days my Newton+ seems to have been behaving a bit strangely.

Yesterday I saw some strange power readings while descending a pretty long and steep descent (approx. 3.25 miles; average slope -10.6%; average speed 36.5; max speed 49). Based on this selection (about 3:33:30 - 3:39:00 in the long ride file) my average speed was shown as 163.8w and max as 743w. That's pretty hard to believe when doing this kind of descent. I also noticed when I was heading for home that I thought I was going into a headwind but the Newton said that it was a tailwind. The ride file has had a "Repair Ride file for Bad Tilt" applied to it, I have not tried to revert to the original file yet to see what the difference might look like. But .. I do have today's file which is even more telling.

On today's file starting between 1:30 - 1:40 you'll see that the wind speed just levels off at about 11mph solid for the remainder of the ride (almost two more hours). I tried stopping on my way home and blowing into the wind port and doing a tilt calibration and wind calibration. On the wind calibration in a calm are the Newton read about 10mph wind consistently, no movement.

I have since come home, downloaded the ride, upgraded my Issac software to the most current version, done a hard reset of the Newton, done a tilt calibration, and then ... tried to do a wind calibration in my closed garage. When I was trying to do the wind calibration I was see a consistent 12 - 12.7mph wind reported. There was no wind, this is a closed garage.

Help ... please ... what's going on here?

Thanks,

Robert

[Velocomp]

There is a bug that is causing this problem. We're on it...

[rstrom]

Excellent ... now I won't go out and do another cal ride, etc.

Thanks for the reply ... this most likely saved me a lot of frustration.

Now ... the question is ... can the rides recorded while using the Newton be fixed?

Also, I'm assuming that this is a firmware bug. I know this was introduced in one of the OS2 updates, I'm assuming it was one of the last two. Is it possible to revert to older firmware versions?

Thanks,

Robert

[Velocomp]

Please install OS2.12, which was just released. This should correct the issue you encountered.

[rstrom]

A couple of posts up from here "Data Reset" you say

Make sure to update to 214, now available.

As blp mentions responding to your post

Isaac software says FW2.13 is the most recent.

I just checked via Issac and it is telling me that 2.13 is the most current.

Is there a 2.14 that is supposed to be posted but is not available for download for some reason?

Thanks,

Robert

[Velocomp]

2.14 is a typo. 2.13 is a beta and is not yet released. 2.12 is released and addresses the problem discussed in this thread.

[NorBike]

2.14 is a typo. 2.13 is a beta and is not yet released. 2.12 is released and addresses the problem discussed in this thread.

I think 2.13 was released last week......?

Uten navn.JPG (7.88 KiB) Viewed 8647 times

[Velocomp]

2.14 is a typo. 2.13 is a beta and is not yet released. 2.12 is released and addresses the problem discussed in this thread.

I think 2.13 was released last week......?

Uten navn.JPG

My bad. 2.13 is the current production release.

[rstrom]

OK ... now that we're all on the same page ...

[Russ]

Darn John,

Now my Pavlovian response has me panting for 2.14!
Ooooooohhhhhh

Russ

[Velocomp]

Darn John,

Now my Pavlovian response has me panting for 2.14!
Ooooooohhhhhh

Russ

So much cool stuff is on the way, you can't even imagine it. Or if you can, then I know why you're panting!

[Russ]

Ooohhh I can't wait!

Guess, when I am not riding, working, eating or sleeping or visiting LBS, I will just have to kill time watching bike videos on youtube

Short 1minute 8 second sample titled:
Sharing Copenhagen Bike Love with Breakfast at Summer Streets 2012
http://www.youtube.com/watch?v=Kwis_EoMPfg

smitten by bike love
Russ