ElectricMotorcycleForum.com

Cas,

What battery are they using for replacement do you know?  Is it the newer bigger BCB battery?

Thx,
Paul.

You barely even need the logs to prove it - in my case all I had to do was ride 23 miles, observe the battery SOC at 65%, and then come back to the bike a few hours later to discover it had charged itself back up to 75%.

My dealer down in Torquay (Davant) managed to pull the logs successfully after I dropped it off and then presumably pulled them again a few hours later, and that was enough for Zero to acknowledge the issue and send me a new battery under warranty, which is apparently being fitted today (hurrah!)

Cas

Has anyone tried to diagnose/demonstrate the SOC symptoms from the 14.4 kWh battery packs?  Sometimes referred to as "magic charging" or "voltage sag" or "voltage rebound".
I live in Ireland and there are no dealers, the only one hasn't got the expertise (due to sick leave) to pull the logs and investigate.  So my options are very limited.
It appears that the logs downloaded via the Zero app are very small/recent - about 2,500 entries, and even when the bike is idle only covers a few days.
My next thought was to go a ride to recreate the issues and capture logs frequently... but then I don't know if the App Download can/would demonstrate the problem.

Any thoughts/experiences to share?

Thanks!
Paul.

Hi all,  I had similar issues with my 2020 SRF as those above.  My failure was triggered by the v19 firmware upgrade, replaced under warranty by the dealer, back and forth to trouble shoot and I ended up resolving on my own.   
There’s a thread on this :  https://www.electricmotorcycleforum.com/boards/index.php?topic=10973.msg102112#msg102112

My CCM had to be replaced a 2nd time as the first module wasn’t coded to my unit.  The new module worked at the dealers and then lasted 1 day, after which it only worked when keyed on or on charge.  That lasted 2 more days, after which - nada, “NOT CONNECTED”.  I waited and chased for months but my dealer and Zero country team weren’t interested.

In the end, I disconnected the CCM module completely and removed and replaced the SIM card.  That did the trick.  In future if I ever get a CCM issue again I’ll be doing this first.  It’s really easy to do.  Obviously DON’T if your bike is still under warranty!

This is a good FB article on how to get into the CCM and what it looks like:
http://zeromanual.com/index.php?title=Gen3/Cellular_Communications_Module&oldid=7116

Paul.

Just an update on my own CCM issues / situation.
I tried time and again to prompt the dealer, and Zero UK, I received silence.  I think these units are temperamental and so I suspect there are many root causes to what is the same symptom (no connectivity).
I decided to go in and investigate myself.  I had previously removed the 5v fuse to the CCM with no luck whatsoever.  The bike still reports “Cellular” status as “Not Connected”.  So I proceeded and removed the tank plastics (easily done) and removed the CCM module, which is just behind the ignition switch and secured with cable tied.  I just cut those and then removed the rubber boot that prevents water ingress.  The plastic housing is held closed by a single small screw.  Removing this I can see there is a sim.  I popped this out,  then put it all back together and connected to the bike.
Keying the bike on and the status showed as “Connected”.  I had forgotten to put a little internal plastic cover back on and when I did so it reported “Not Connected”. I took apart and reassembled (all whilst connected to the bike and keyed on) and it flipped to “Connected” again.  Loose wire connections?  Flaky cellular connection?  Unit upside down?  I’ve no idea.  After a few hours the bike is staying in a “Not Connected” state when keyed off and “Connected” when keyed on.  I remember a firmware fix was supposed to resolve loss of connectivity when the bike was off and not charging.   I’ll continue to monitor, fingers crossed I at least have connectivity when it’s charging - that’s the bit I miss; ie when should I go back to the bike if I’m not in Bluetooth range. 

Paul.

I just spent several months getting a new CCM fitted (under warranty).  It had to be coded to the bike which unfortunately the first that Zero sent out was not.  But after successful replacement it updates the Cloud status fine, but after the bike is keyed off for a couple of hours (next CCM update basically) then the SOC goes to 0%.  Key the bike on and leave for an update to occur and it is correct again.
It feels as though this is an issue with the new CCM sending back the wrong status when the bike is off.  But the dealer is stating this is a known issue with the App (Zero NextGen app that is). 
Anyone else with any further info on this issue?  I can't help but feel it's a simple config problem.   

Hi all,

I recently (2 months ago) updated the firmware on my SR/F to the latest v19.  The usual bike message appeared prompting the update after I finished a ride, so I chose to proceed with the over-the-air update.  That failed at 93%, the bike shut off and when I keyed off and on again I reattempted the update.  That also failed at the same point, this time I tried via the Zero mobile phone App, this worked fine.  As soon as it completed I noticed that the SOC and bike location remained at pre-update status.  Essentially the cloud status of my bike remained frozen.  I keyed off the bike and pulled Fuse 1 (5A) to the CCM unit, gave it 5 mins and replaced with a new 5A fuse.  Still no updated status, a number of weeks passed and the Zero App stated "last seen 3 weeks ago".

I took the bike to my dealer and they got in touch with Zero Europe (NL) and the conclusion was to replace the CCM unit.  Am I alone with regards issues like this after performing a firmware update? Or perhaps v19 in particular?  I am questioning whether to accept updates in future as I don't recall any new Firmware version from Zero landing without issue(s) - I also had the magic charging issue after I installed v18.

Interested to hear other opinions on this.

Cheers,
Paul.

Anyone get any luck with Zero support on the SOC freezing or sitting at 0 since the v18 update?