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.
my ccm is faulty from the beginning ( february ) and i have open a ticket to my dealer, and i call it every week for status... but at today nothing.
my current ccm have 2 problems, it never report soc % and charge status to the server,
but the worst problem is that after a server position update ( with bike in motion) it hang, simply ccm go to low power mode and never wakeup, to fix this you need to disconnect 12v battery.
if bike is stationary it update server position without issues every time you turn on key.
running a canbus trace on the communication lines, the bike send soc % and fw ver to the ccm every sec, and ccm send back the info you see in the diagnostic.
as soon it hang it disconnect from bus and all the data transmitted from mbb is not captured.
i have also found canbus messages (id253) with soc 0% sent to the ccm at key on, this is likely the cause of the bad soc% reported to the server (if ccm update the server with this value)...and i think it will be addressed by a new MBB firmware soon or later... (i'm running MBB v24)
p.s you can check the real data sent from ccm to the server with the following info
https://www.electricmotorcycleforum.com/boards/index.php?topic=9520.0cause app can be bugged too