Print

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

[TheRan]

So I had an accident Saturday night, went down on some grit and then a van behind me hit the bike and pushed it (after he went up a bank and flipped on his side, quite the event). There wasn't any major damage, a few scrapes, my handguards got bent out of place and my front wheel was a bit wonky. When I rode back home everything seemed fine other than the steering being off, had all sorts of flashing lights on my dash but that all went away after keying off and back on again. However riding yesterday I noticed the SoC behaving oddly, I think I turned the bike on at around 37% and by the time I'd got to work literally less than ten minutes later it had actually gained up to around 40%. Then while leaving work tonight it started off at 31% and went to 32% after a few minutes of me just standing at the bike, then the ride home that would usually drop me 1% if that instead got me down to 27% and the whole ride I had both the red triangle and the green circle flashing away at me and errors 20, 28, and 29 on the dash. These are respectively BMS low isolation, BMS isolation fault, and BMS isolation danger, and according to the unofficial manual that last one should make the contactor open. Other than the SoC I didn't notice any other peculiarities with how the bike rode, no cutting out. I've just put the bike on charge and it's doing it although it's only at 9/10 amps monitoring it on the app, cell balance is okay at 12mV. I'll see in the morning if it completes the charge.

I'm just not sure whether this is being caused by water ingress as it's been pretty wet lately and it's not like I haven't had isolation faults before (although not with the BMS) or whether the shock from the bike going down has buggered it. I've gone down a few times before and had no issues and I feel like impact damage would probably kill the thing outright and the bike wouldn't even ride never mind charge.

[T.S. Zarathustra]

I have not crashed my Zero. Yet  . 
If the BMS has gone bad due to the crash, some damage should be visible on the battery-case and surroundings. Maybe open the case and see if there is water (or visible damage) inside.
Ghost charging is not good news. I hope it's not serious. Best of luck.

[princec]

More likely the shock of the crash has crushed one or more cells in the pack.

Cas

[Specter]

if the bms it's self has not taken any damage, then there might be some loose connectors or damaged sensors causing the issues as well.  you also could have jarred something loose in places you can't see either, like in the battery compartment on some bus work, voltage sensors or something like that.  This doesn't mean that it's fine, you could have busted stuff on the bms board, just that it could be getting bad inputs from other places causing your problems.  Given it seemed fine then the problems creeped in, sounds like something is loose, and now giving you grief over it.  There could also be some pinched wires too as everything got slammed in the crash.  BMS' have a lot of small signal wires that arent always routed in the best way, and any hard shocks can pinch them, cut them, or fray them.  if it's looking at individual battery volts, now were talking only a few volts, so a slightly loose or even a bit off being full seated connector can absolutely cause you grief.

loose buswork can cause issues that will only appear after some use, as charge / discharge don't happen properly due to voltage swings across the loose connections now start causing short charge cycles, improper soc indictions etc due to them.

do you have some sort of factory reset option you could try, like a total reboot or default setting, see if that might help?  Set it to day 1 settings so you are starting with a clean slate, then anything creeping in, you know is current.

aaron

[ESokoloff]

I tried to send you some info via PM but no Joy.

[TheRan]

I got your PMs. I've not updated this thread as I've been so busy with work and just now got back from a week abroad. The days following my original post the errors 28 and 29 went away and the SoC went back to being accurate, the error 20 was intermittent and may have been coinciding with wet days. The last few days of riding to work I think the 20 stopped showing up completely, because that one wouldn't flash the red triangle like the 28 and 29 I didn't always remember to check if the code was still showing up because I had the dash set to show range by default. One thing I did notice though was that the range estimate seemed to be more reactive, updating more quickly than I remembered and adjusting to the riding conditions. I was also getting much higher estimates than previously at this time of year, like 70 miles from 100% which is more of a Summer range. After having not been ridden for a week the bike should be well and truly dry now so it will be interesting to see if any errors remain.