Topic: Is your CCM working? (Read 3703 times)

morpheus74 · « **Reply #15 on:** November 29, 2022, 10:18:37 PM »

hello,
news from Zero : they will change the CCM. The dealer already received it ...
I had a second pb, with the battery ... and they notice also to change the battery !! cause recent magic charging, and couldn't do more than 80km with full SOC ... the bike have 17 000km, and the problem is new since 2 weeks ... they had uploaded logs, and confirmed today the need to change the battery.
A support guy from Zero will come to my dealer to do the battery swap, stile waiting now to know when a battery will be available ... (sorry out of the thread for this last point)

zeronimbus · « **Reply #16 on:** December 10, 2022, 12:06:52 PM »

while waiting to receive the ttl cable for the ccm diag
a person from the French forum shared a link for me to connect the ccm.
here is my data
What do you think

<data>
<item>
<unitnumber>******</unitnumber>
<name>*****************</name>
<unittype>5</unittype>
<unitmodel>6</unitmodel>
<analog1>0.09</analog1>
<mileage>6377.98</mileage>
<software_version>200416</software_version>
<logic_state>2</logic_state>
<reason>2</reason>
<response>0</response>
<driver>0</driver>
<longitude>-0.6818</longitude>
<latitude>46.6525</latitude>
<altitude>101</altitude>
<gps_valid>1</gps_valid>
<gps_connected>1</gps_connected>
<satellites>4</satellites>
<velocity>0</velocity>
<heading>352</heading>
<emergency>0</emergency>
<shock/>
<ignition>0</ignition>
<door>0</door>
<hood>0</hood>
<volume>0</volume>
<water_temp/>
<oil_pressure>0</oil_pressure>
<main_voltage>12.4</main_voltage>
<analog3>0</analog3>
<siren>0</siren>
<lock>0</lock>
<int_lights>0</int_lights>
<datetime_utc>20221209144539</datetime_utc>
<datetime_actual>20221209144538</datetime_actual>
<address>La Gourbillière</address>
<perimeter/>
<color>2</color>
<soc>82</soc>
<tipover>0</tipover>
<charging>0</charging>
<chargecomplete>0</chargecomplete>
<pluggedin>1</pluggedin>
<chargingtimeleft>0</chargingtimeleft>
<storage>0</storage>
</item>
</data>

zeronimbus · « **Reply #17 on:** December 10, 2022, 05:59:16 PM »

here are the links for that info.
the first gives the number of the ccm unit
the second, the connection info.
put the email, the password, and the number of the ccm.
thank you to the person of the forum electrique.fr vehicles (schinze for not the quoted lol)

https://mongol.brono.com/mongol/api.php?commandname=get_units&format=xml&user=[TON_MAIL]&pass=[TON_PASS]

https://mongol.brono.com/mongol/api.php?commandname=get_last_transmit&format=xml&user=[TON_MAIL]&pass=[TON_PASS]&unitnumber=[TON_UNITNUMBER]

themonsterit · « **Reply #18 on:** December 12, 2022, 04:03:14 PM »

Quote from: zeronimbus on December 10, 2022, 12:06:52 PM

while waiting to receive the ttl cable for the ccm diag
a person from the French forum shared a link for me to connect the ccm.
here is my data
What do you think
<data>
<item>

<software_version>200416</software_version>

</data>

i see you are on the same fw 2020.4.16 as i am, and my ccm is not working too, maybe this EU firmware is bad and who have it... you know..

zeronimbus · « **Reply #19 on:** December 13, 2022, 08:41:29 PM »

I sent zero parts in the Netherlands an email, for a quote on the New CCM 2022, if it is compatible on my sr/s 2021?
no news for

karlh · « **Reply #20 on:** December 13, 2022, 09:04:32 PM »

CCM part numbers for 2021 and 2022 models are different (at least here in the USA), but that may only be because the 2022 part is listed as 4G. Parts catalogs are available on the AF1 Racing website (https://www.af1racing.com/).

Mooseman · « **Reply #21 on:** December 15, 2022, 07:31:18 AM »

Update: in short, nothing is happening. My bike has been sitting at the dealership since November 3rd. After posting here someone from Zero contacted me to offer help. Interesting since I tried to get Zero involved so they can hopefully fix the issue but they pretty much brushed me off.

Anyway, so I was told they'd get in touch with the dealer to get the issue resolved. That was two weeks ago. Nobody contacted me during this time, no status update, no nothing. The only thing that has changed is that the app now says that the last connection was 6 months ago instead of 5...

I wish I could say I'm disappointed but this is actually exactly what I expected after all the bad experience I've had with Zero so far. This company is dead to me. I've never seen so much incompetence in both technical skills and customer service. It is beyond me how it can take so long to replace a part and set it up so that it works.

Sorry for the rant.

zeronimbus · « **Reply #22 on:** December 15, 2022, 11:58:10 AM »

really sorry for you.
I am in the same position as you.
CCM still not working.
this morning, insulation fault 43, the bike no longer charges.
I will try to reset the motherboard.
I love this bike but I no longer trust zero.
only words, but no action.
they should be harassed on facebook

zeronimbus · « **Reply #23 on:** December 18, 2022, 06:07:02 PM »

I connected the usb ttl cable to the odb2 socket
plugged into the bike, and it gives me this.
cannot type a command name.
ideas ?

DEBUG: 12/18/2022 12:30:24.023 ../src/Application/zero_mbb_manage_bike.c : line 552 - Disable flags changed. Old: 0x000d New: 0x0001
12/18/2022 12:30:24.231 - Connecting mod 3. V_(mod: 115935, bus: 115860, bus_oc: 0)mV,
12/18/2022 12:30:24.233 - I_(out: 1333, lim_dischg: 552000, lim_chg: -28000, lim_CC: 100000)mA
12/18/2022 12:30:24.540 - Module 3 Contactor is now Closed
12/18/2022 12:30:26.203 - CHARGER LSS: Found at least one unassigned node.
DEBUG: 12/18/2022 12:30:27.032 ../src/Application/zero_mbb_manage_bike.c : line 2373 - Fault cleared: CONTROLLER_WARNING
12/18/2022 12:30:29.775 - CHARGER LSS: Found unassigned node with identity: 0x00000466 0x00000009 0x006400C9 0x001DC5B0.
12/18/2022 12:30:29.814 - CHARGER LSS: Successfully assigned node ID 0x10
12/18/2022 12:30:29.845 - CHARGER LSS: Found at least one unassigned node.
12/18/2022 12:30:30.835 - CHARGER LSS: Scan Failed.
12/18/2022 12:30:31.355 - CHARGER LSS: Found at least one unassigned node.
12/18/2022 12:30:35.094 - CHARGER LSS: Found unassigned node with identity: 0x00000466 0x00000009 0x006400C9 0x001DC556.
12/18/2022 12:30:35.133 - CHARGER LSS: Successfully assigned node ID 0x11
DEBUG: 12/18/2022 12:31:34.705 ../src/Application/zero_mbb_manage_bike.c : line 627 - Key Sw = OFF
DEBUG: 12/18/2022 12:31:34.799 ../src/Application/zero_mbb_manage_bike.c : line 545 - Control flags changed. Old: 0x4076 New: 0x4078
12/18/2022 12:31:34.801 - State change from STOP to HIB
DEBUG: 12/18/2022 12:31:34.837 ../src/Application/zero_mbb_msc.c : line 1185 - MTC pending change by 3 from 1 to 1

Charge State 1 from 3
DEBUG: 12/18/2022 12:31:34.841 ../src/Application/zero_mbb_manage_bike.c : line 545 - Control flags changed. Old: 0x4078 New: 0x0070
DEBUG: 12/18/2022 12:31:34.843 ../src/Application/zero_mbb_manage_bike.c : line 552 - Disable flags changed. Old: 0x0001 New: 0x0005
DEBUG: 12/18/2022 12:31:41.303 ../src/Application/zero_mbb_manage_bike.c : line 620 - Key Sw = ON
DEBUG: 12/18/2022 12:31:41.305 ../src/Application/zero_mbb_manage_bike.c : line 545 - Control flags changed. Old: 0x0070 New: 0x007e
12/18/2022 12:31:41.306 - State change from HIB to WAIT
Charge State 1 from 3
DEBUG: 12/18/2022 12:31:41.321 ../src/Application/zero_mbb_manage_bike.c : line 545 - Control flags changed. Old: 0x007e New: 0x4076
DEBUG: 12/18/2022 12:31:41.346 ../src/Application/zero_mbb_manage_bike.c : line 666 - Kickstand Sw = UP
DEBUG: 12/18/2022 12:31:41.348 ../src/Application/zero_mbb_manage_bike.c : line 545 - Control flags changed. Old: 0x4076 New: 0x4066
DEBUG: 12/18/2022 12:31:41.417 ../src/Application/zero_mbb_manage_bike.c : line 658 - Kickstand Sw = DOWN
DEBUG: 12/18/2022 12:31:41.418 ../src/Application/zero_mbb_manage_bike.c : line 545 - Control flags changed. Old: 0x4066 New: 0x4076
12/18/2022 12:31:41.770 - LSS: Found at least one unassigned node.
12/18/2022 12:31:42.392 - LSS: Found unassigned node with identity: 0x00000466 0x00000002 0x00000001 0x000100BC.
12/18/2022 12:31:42.427 - LSS: Successfully assigned node ID 0x0A
12/18/2022 12:31:42.448 - LSS: Found at least one unassigned node.
12/18/2022 12:31:43.063 - Registering Mod 2 (115941mV, 1 brick )
12/18/2022 12:31:43.141 - LSS: Found unassigned node with identity: 0x00000466 0x00000002 0x00000001 0x00011864.
12/18/2022 12:31:43.169 - LSS: Successfully assigned node ID 0x0B
DEBUG: 12/18/2022 12:31:43.276 ../src/Application/zero_mbb_manage_bike.c : line 552 - Disable flags changed. Old: 0x0005 New: 0x000d
12/18/2022 12:31:43.874 - Registering Mod 3 (115938mV, 4 brick )
12/18/2022 12:31:44.177 - State change from WAIT to STOP
DEBUG: 12/18/2022 12:31:44.185 ../src/Application/zero_mbb_manage_bike.c : line 3650 - Entered STOP- opening latch
12/18/2022 12:31:44.190 - All Contactors open
DEBUG: 12/18/2022 12:31:44.279 ../src/Application/zero_mbb_manage_bike.c : line 2218 - Fault set: CONTROLLER_WARNING
DEBUG: 12/18/2022 12:31:44.280 ../src/Application/zero_mbb_manage_bike.c : line 2253 - controller warning 200
12/18/2022 12:31:44.567 - Precharging from module 2, Vpackoc: 115944mV
12/18/2022 12:31:44.568 - Connecting mod 2. V_(mod: 115944, bus: 0, bus_oc: 0)mV,
12/18/2022 12:31:44.570 - I_(out: 0, lim_dischg: 151000, lim_chg: -7000, lim_CC: 100000)mA
12/18/2022 12:31:45.888 - Module 2 Contactor is now Closed
12/18/2022 12:31:45.890 - At least one contactor is now closed
DEBUG: 12/18/2022 12:31:45.892 ../src/Application/zero_mbb_manage_bike.c : line 552 - Disable flags changed. Old: 0x000d New: 0x0001
12/18/2022 12:31:46.099 - Connecting mod 3. V_(mod: 115935, bus: 115845, bus_oc: 0)mV,
12/18/2022 12:31:46.100 - I_(out: 1600, lim_dischg: 552000, lim_chg: -28000, lim_CC: 100000)mA
12/18/2022 12:31:46.398 - Module 3 Contactor is now Closed
12/18/2022 12:31:48.010 - CHARGER LSS: Found at least one unassigned node.
DEBUG: 12/18/2022 12:31:48.869 ../src/Application/zero_mbb_manage_bike.c : line 2373 - Fault cleared: CONTROLLER_WARNING
12/18/2022 12:31:51.762 - CHARGER LSS: Found unassigned node with identity: 0x00000466 0x00000009 0x006400C9 0x001DC556.
12/18/2022 12:31:51.803 - CHARGER LSS: Successfully assigned node ID 0x10
12/18/2022 12:31:51.843 - CHARGER LSS: Found at least one unassigned node.
12/18/2022 12:31:56.483 - CHARGER LSS: Found unassigned node with identity: 0x00000466 0x00000009 0x006400C9 0x001DC5B0.
12/18/2022 12:31:56.530 - CHARGER LSS: Successfully assigned node ID 0x11

themonsterit · « **Reply #24 on:** December 19, 2022, 04:08:45 PM »

yes, zero console is not standard,
you can use this small program i made to interface it
https://drive.google.com/file/d/1xFppbBsfCtPkoJzsk0wwxbPf_gVOVHPW/view?usp=sharing

"open" the FTDI com port connected to the bike and type the comand or select the tab with pre-coded commands to show data.

ms_smart · « **Reply #25 on:** December 19, 2022, 04:59:03 PM »

@zeronimbus, I also get from time to time DEBUG messages - but have never seen that many. Normally you can just ignore them. If you can't type in a command, your serial line settings might be incorrect.

PaulZero · « **Reply #26 on:** December 20, 2022, 02:51:45 PM »

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.

karlh · « **Reply #27 on:** December 20, 2022, 07:19:43 PM »

Quote from: themonsterit on December 19, 2022, 04:08:45 PM

yes, zero console is not standard,
you can use this small program i made to interface it
https://drive.google.com/file/d/1xFppbBsfCtPkoJzsk0wwxbPf_gVOVHPW/view?usp=sharing

"open" the FTDI com port connected to the bike and type the comand or select the tab with pre-coded commands to show data.

Can you post the source code? I would like to rewrite it to run on Linux.

Mooseman · « **Reply #28 on:** March 02, 2023, 10:45:26 PM »

So I just received an email telling me that my CCM is now working. The bike has been sitting at the dealership for 4 months. I still can't connect to the bike via the app though. I even installed the Zero NextGen app on a different phone where it has never been installed before and there is still no connection to the bike.

Zero claims that they can see the bike from their end and tells me that the problem will be fixed with an app update that is "scheduled to be released in April".

I have a hard time believing that this is true. I can't even connect to the bike using the ZenGo app. Also, am I to understand that all previous app versions since February 2022 had the same issue? Wouldn't that mean that as of right now, nobody can access their bike via the NextGen app version 2.7.1?

Something doesn't seem right. Plus, either way: my problem hasn't been resolved. I brought my bike in with the problem description that I can't connect to the bike via the cell connection. As it stands right now, I still can't. I just want this POS repaired so I can sell it and never deal with Zero Motorcycles again. "The Tesla of Motorcycles" my ass. I never had anything even close to this mess happen with my Model 3.

2020_SRS_Commuter · « **Reply #29 on:** March 07, 2023, 06:17:32 AM »

The part I dont get is, why did it need to sit in a shop for them to come to this determination?
At least it could be ridden while they were sorting that out.

ElectricMotorcycleForum.com

News:

Author Topic: Is your CCM working? (Read 3703 times)

morpheus74

Re: Is your CCM working?

zeronimbus

Re: Is your CCM working?

zeronimbus

Re: Is your CCM working?

themonsterit

Re: Is your CCM working?

zeronimbus

Re: Is your CCM working?

karlh

Re: Is your CCM working?

Mooseman

Re: Is your CCM working?

zeronimbus

Re: Is your CCM working?

zeronimbus

Re: Is your CCM working?

themonsterit

Re: Is your CCM working?

ms_smart

Re: Is your CCM working?

PaulZero

Re: Is your CCM working?

karlh

Re: Is your CCM working?

Mooseman

Re: Is your CCM working?

2020_SRS_Commuter

Re: Is your CCM working?