Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[nicktulloh]

I don't have the glitch on my '12 DS yet). As usual, the internet amplifies the negative and who knows how prevalent the glitch is.

What does occur to me is that Zero is really tempting fate by not recalling. Clearly the glitch could result in an accident. Hopefully that doesn't happen but if it does, and if it's serious, it could take the company down.

[DedoBurns]

I am not giving up on Zero. Despite my dealership that is playing catch-up, they and especially the eastern zero tech have been responsive. I am still riding and just dealing with it until I hear back about the next course of action. Trying to be patient and trusting.

Some other notes of interest:

My zero was a demo so may have been a somewhat earlier build (Edit: #123, I assume it is consecutive out of the factory?)

the update, done sometime in early September, did negate the need to restart with the key while moving. It does seem that it will cut off at higher speeds now.

[Justin Andrews]

Interesting, so it looks like there WAS an update that came out after my bike was updated...

I could really use that throttle reset capability, I'll have to contact Zero and see if I can get the update.


(My bike is #232 so I wonder if the earlier 2012 models are more prone to the glitch, or if thats just coincedence. )

[NoiseBoy]

Mine must be one of the last bikes off the line and I haven't had a glitch so far after 5500 miles.  Although I tend to do alot of short distance trips, less than 10 miles but 4+ times a day.  Maybe the lack of extended running helps?

[Justin Andrews]

I do around 40 miles a day, so I don't think its that. Strangely my longest glitch free ride was a 80 mile long ride.
However being an ex-demo bike, it only has 3500 miles on the clock (of which I've put 2000 of those miles on)

Maybe the earlier 2012 bikes are more prone to the glitch?

[protomech]

If the problem is faulty potting around the motor encoder, it's possible that either batches of the motors are unaffected or that Motenergy improved their potting procedure over time.

So yes, the later bikes might be spared. Who has the highest VIN that's been affected by the glitch?

[Justin Andrews]

My VIN ends in 232

[WindRider]

My VIN is 248 and I have not had the glitch in 6,400 miles.

Got a call from the dealer a few days ago and they updated Firmware on the MBB, SevCon, and recalibrated the motor.

[protomech]

They probably had to recalibrate after upgrading the Sevcon controller firmware. But periodic manual motor recalibrations can also forestall the encoder drift.

[Richard230]

I have VIN 51 and after almost 7K miles, no glitch here.  But then I don't ride in the rain and my motor has never become very hot.  All of my riding is in temperatures of between 35 and 80 degrees F and I never spend much time at freeway speeds.  I have never seen the high temperature warning light (or any warning lights, for that matter) and I doubt my motor has gotten above 100 degrees, based upon feeling the case with my hand after stopping.  So maybe all of those factors have kept the encoder happy.   

[Justin Andrews]

or any warning lights, for that matter

What not even the "kickstand down" warning light...?

[kcoplan]

My bike is in the 300s -- 316, or so, I think -- and, yes, I had Glitch 2.0, so I dont think later builds were immune.  But I did ride all last winter in NY, on wet, salted roads sometimes -- corrosion city.

--Karl

[Richard230]

or any warning lights, for that matter

What not even the "kickstand down" warning light...?

I thought that was a "kickstarter" light.   

[Doctorbass]

My 2012 S ZF9 VIN is ending with   93

and I HAVE THAT GLITCH... sometime very rare sometime make the ride very dangerous!

Doc

[rotoiti]

My DS ZF9 is #135. I did 5,000 miles last year but only a meager 1,000 this year since I got the glitch. I need to finally ride my bike to the service but I am not sure how to demonstrate the glitch to them.