Print

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

[Hans2183]

Indeed I like how it's easier now to estimate range since you know how much you've ridden also.

I noticed it counted from 0 after my update issues and resets but figured that was due to the reset first. But now it also restarted this morning.

Just checked and the value resets as soon as you power the bike on start charging the bike.

Edit : it's charging that triggers te reset. Today I didn't charge on my location and kept counting till I got home again where I charged resetting the value.

[Hans2183]

Finally I understand how the release of the charger works now after that update And I have to say I don't like it.

If you charge to 100% capacity then all you need to do is use the key to turn the bike on and the charger is released. That is fine.

But if you have a charge goal set, so you don't go to 100%. Once that goal is reached charging stops and on turning the bike on you get the popup with the menu/override option. Doesn't matter which option you pick the cable is still locked. You have to turn the bike off and on again (so a second time that is) and only then it will release the cable.

I don't like that last part and I think that's sometime they overlooked implementing the new release logic.

[remmie]

I would say it is good that the cable doesn't unlock when you have a charge goal set and turn on the key. Just so you can choose "override" and it would hold on to the connector and charge all the way up to 100%.

BUT when you choose "menu"  it should release the charging cable, because you clearly want the stop the charging and go have a ride.
That should be a very easy fix in the next firmware update. 

[Hans2183]

The strange noise rectangle was back in the display this morning. Also the override doesn't work. Starts charging for like a minute and stops again. Before the update I could use that override to remove the scheduled charge delay or to charge to 100% which I do 1x a week for a single longer highway trip I have to make. It's in that state that the charge connection remains  locked.



So I asked my dealer to check with zero what they can do.

[jan]

The strange noise rectangle was back in the display this morning. Also the override doesn't work. Starts charging for like a minute and stops again. Before the update I could use that override to remove the scheduled charge delay or to charge to 100% which I do 1x a week for a single longer highway trip I have to make. It's in that state that the charge connection remains  locked.



So I asked my dealer to check with zero what they can do.

I also got the update and have similar troubles as you described with the latest firmware. My dealer let me know that Zero is working on a fix, scheduled for release this week. Fingers crossed...

[Hans2183]

indeed got a confirmation from my dealer Zero is aware and coming with a fix soon.

[Hans2183]

But no actual updates received so far.

And to make things worse I had it stored over the weekend at 85% and just wanted to fully charge it yesterday... It just shuts off after a minute or so. New warnings about "isolation fault" and "12V low voltage fault" and "battery module ineligible"... Looks like I'll be riding the GS to work 🤔

[jan]

Yikes, that sucks! Does it shut down only the charging, or the entire bike (i.e. unusable)? No update here either by the way...

[Hans2183]

it also shuts down when I don't have it plugged in. Also the red battery icon doesn't go out (like it normally does) and the orange engine icon remains on. It doesn't arm when I take it off the stand and toggle the killswitch. The stand icon goes away so no issue with that sensor.

I also got a "DC-DC low voltage" error once, but that one doesn't return on every startup.

Now if I wait for a few minutes with the bike off and then turn it on without charger plugged in it seems to work and even arm. But then when I want to charge again it works for a short moment, then goes back in this faulty state.

I'll try driving it to the nearest public charging option and try to charge there just to exclude the charge adapter I'm using. If that still fails it's up to the dealer to fix it.

[remmie]

Looks like the 12V battery. I've seen some reports that this small battery can cause all sorts of problems, including the warning about the DCDC converter. Seems a bit strange that such a problem would disable the entire bike. I hope that this 12V battery will not become like the calex charger on previous models.

You could try to measure and recharge the 12V battery with a normal battery tender. As you have a GS you probably have a battery tender as well

[Auriga]

Be careful about using a regular battery tender on their Li Ion 12V battery. They are not the same chemistry, and using a regular one will just damage the battery

[Hans2183]

I might be in luck. Looks like it's charging now. I set the 95% charge goal again and have the key on and then plugged it in. Like this it starts charging and seems to keep charging.

If I then can find a workaround for the 12V warnings not letting it arm I should be fine. I have a lifepo4 replacement in the GS and can use that charger for the zero. But I'll keep that as a last resort.

Edit: completed charge, released cable and it just arms like nothing was wrong before... So weird. I have a longer commute tomorrow with required charge at destination. I won't risk it. Later this week I can ride it on shorter commutes 🤞.

Being stranded twice in three months I can't call it a reliable machine though.

Edit2: Issues with that 12V battery indeed. I checked yesterday and it was at 13.38V which is perfect for a full lifepo4 battery. Checked again this morning and now it's only at 13.08V from just standing there. Something is draining that battery.

[Crissa]

I'd expect the radio that gives it network connectivity is using it.

-Crissa

[BrianTRice@gmail.com]

(following up on Crissa's suggestion) I don't know if this is relevant, but battery drain on a mobile phone is antenna-dominated. The cell data connection module might be thrashing trying to connect to its network if you're just out of range or possibly only barely within range.

AFAICT the only way to unstick it is rebooting the module. I think the OBD-II port allows the command to do it, but otherwise you may need to pull the relevant fuse and re-insert.

[Hans2183]

I'm currently having the update installed