Sounds more like software to me. Storage mode snafu?I think you're correct. Is there a way for me to deal with it?
Cas :)
Sounds more like software to me. Storage mode snafu?SW update are now done. Here is what I now have:
Cas :)
Did you hear the contactor click?Yes, the contactor clicks even when I try my unsuccessful charge. And clicks again when it gives up. So that is NOT the issue.
Cas :)
Why not contact Zero's customer service and ask them about the problem?That is not my style until I give up and get desperate.
Could it be the 10A charging fuse holder in the wiring harness? A similar thing happened on my bike and several others as described in this thread:Are you referring to a 2023 Zero DSR/X ? Is there a fuse in a harness somewhere that I have not yet found? A photo of the area of the bike would be helpful.
https://www.electricmotorcycleforum.com/boards/index.php?topic=11400.msg117610#msg117610 (https://www.electricmotorcycleforum.com/boards/index.php?topic=11400.msg117610#msg117610)
You can first clean the fuse holder contacts and see if that fixes it. If it does, then replace the whole fuse holder, as it's not the fuse but the fuse holder itself, and the problem will otherwise return. If it does not, then this is probably not the problem.
Unlikely the BMU itself has managed to fail all on its own. Much more likely to be a little bit of corrosion and / or moisture on a critical connector, which happens when things get left alone for months. Make sure your 12V battery is fully charged too, which apparently can also cause init problems.My 12V battery is at 13.0VDC after the bike not being on for a day. It is at 13.22 VDC when the DC2DCC is active (when bike is keyed on, 13.30 when trying to charge).
Cas :)
Error 31 means battery module ineligible, whatever that means, but I would take that to mean the fault lies within the battery and not the charging. I would also assume this wouldn't allow the bike to ride, did you try this?The bike rides fine, but so far, I only rode it a very short distance, from my driveway back into the garage just to test that it runs.
You can download the log fiels with the app.Thanks, I will look into it. I have never used the parser before. I knew it existed, but this is the first time I really want to know what was going on by looking at log files. Perhaps that is the first thing I should have done. But now I am glad I worked on the bike so I know how to get to things. The 12 volt fuses are in a real stupid location in the DSR/X.
They are binary and you can analyze them with https://ernstgl.github.io/ZeroGen3LogParser (https://ernstgl.github.io/ZeroGen3LogParser)
You can see the voltages of highest and lowest cells.
| 70 | 76 | 1/2/1970 7:32:04 AM | 558000 | 47 | 84835 | 0 | 0 | 0 | 0 | 3652 | 3652 | 3655 | 43 | 138 | 25 | 51 | 0 | 255 | 1 | 0 | 0 | 7 | 102303 | 0 | 18 | 25 | 26 | 47 | 138 | 3 | 162 | 0 | 143811 | 0 | 3 | 0 | |
| 53 | 253 | 1/2/1970 7:32:04 AM | 327000 | 24 | 86197 | Saving stats, hibernating for 86400 sec | |||||||||||||||||||||||||||||||
| 31 | 253 | 9/29/2025 6:10:12 AM | 180000 | 0 | 86228 | Exiting Hibernate | |||||||||||||||||||||||||||||||
| 83 | 253 | 9/29/2025 6:10:12 AM | 180000 | 1 | 86311 | Board was reset. Source: Hib Wak n, Power-On, Supply WD, Power Val | |||||||||||||||||||||||||||||||
| 42 | 253 | 9/29/2025 6:10:12 AM | 181000 | 2 | 86353 | Entering ZERO_BMS_STATE_IDLE | |||||||||||||||||||||||||||||||
| 31 | 253 | 9/29/2025 6:10:12 AM | 181000 | 3 | 86384 | Discharge enabled | |||||||||||||||||||||||||||||||
| 63 | 253 | 9/29/2025 6:10:12 AM | 182000 | 4 | 86447 | ERRO eroBmsManagePackIo returned ZERO_RET_FAIL | |||||||||||||||||||||||||||||||
| 45 | 253 | 9/29/2025 6:10:12 AM | 341000 | 5 | 86492 | Entering ZERO_BMS_STATE_STANDBY | |||||||||||||||||||||||||||||||
| 52 | 75 | 9/29/2025 6:10:13 AM | 21000 | 6 | 86544 | 0 | 0 | 0 | 32 | 3785 | 0 | 3793 | 0 | 0 | 21 | 51 | 0 | 120 | 0 | 0 | 0 | 3 | 106104 | 13 | 2 | ||||||||||||
| 64 | 253 | 9/29/2025 6:10:13 AM | 64000 | 7 | 86608 | 1000000 baud: Could not read eeprom from cellbox 0 | |||||||||||||||||||||||||||||||
| 64 | 253 | 9/29/2025 6:10:13 AM | 79000 | 8 | 86672 | 1000000 baud: Could not read eeprom cellbox 1 | |||||||||||||||||||||||||||||||
| 96 | 253 | 9/29/2025 6:10:13 AM | 102000 | 9 | 86768 | 400000 baud: cellbox_id 0 CRC invalid. value: 0x02, crc_read: 0x20, crc_calc: 0x0E | |||||||||||||||||||||||||||||||
| 96 | 253 | 9/29/2025 6:10:13 AM | 122000 | 10 | 86864 | 4000 aud: cellbox_id 1 CRC invalid. value: 0x02, crc_read: 0x20, crc_calc: 0x0E | |||||||||||||||||||||||||||||||
| 39 | 253 | 9/29/2025 6:10:13 AM | 152000 | 11 | 86903 | cellbox_id 0: 0x16 (22MY) | |||||||||||||||||||||||||||||||
| 39 | 253 | 9/29/2025 6:10:13 AM | 222000 | 12 | 86942 | ellbox_id 1: 0x16 (22MY) | |||||||||||||||||||||||||||||||
| 38 | 253 | 9/29/2025 6:10:13 AM | 222000 | 13 | 86980 | Cell type detected: 22MY | |||||||||||||||||||||||||||||||
| 56 | 253 | 9/29/2025 6:10:13 AM | 222000 | 14 | 87036 | Latching 12V Output ON, lowest cell:3785mv | |||||||||||||||||||||||||||||||
| 45 | 253 | 9/29/2025 6:10:13 AM | 222000 | 15 | 87081 | Fault set: INVALID/NO CELL TYPE | |||||||||||||||||||||||||||||||
| 49 | 253 | 9/29/2025 6:10:13 AM | 225000 | 16 | 87130 | Fault cleared: INVALID/NO CELL TYPE |
| 63 | 253 | 1/2/1970 2:43:40 AM | 192000 | 4 | 75929 | ERROR: ZeroBmsManagePackIo urned ZERO_RET_FAIL | ||||||||||||||||||||
| 45 | 253 | 1/2/1970 2:43:40 AM | 332000 | 5 | 75974 | Entering ZERO_BMS_STATE_STANDBY | ||||||||||||||||||||
| 52 | 75 | 1/2/1970 2:43:40 AM | 733000 | 6 | 76026 | 0 | 0 | 0 | 32 | 3654 | 0 | 3657 | 0 | 0 | 28 | 51 | 0 | 120 | 0 | 0 | 0 | 3 | 102366 | 6 | 14 | |
| 65 | 253 | 1/2/1970 2:43:40 AM | 733000 | 0 | 76091 | 1000000 baud: Could not read eeprom from cellbox 0 | ||||||||||||||||||||
| 64 | 253 | 1/2/1970 2:43:40 AM | 802000 | 8 | 76155 | 1000000 baud: Could not read eeprom from cellbox 1 | ||||||||||||||||||||
| 96 | 253 | 1/2/1970 2:43:40 AM | 802000 | 9 | 76251 | 400000 baud: cellbox_id 0 CRC invalid. value: 0x02, crc_read: 0x20, crc_calc: 0x0E | ||||||||||||||||||||
| 96 | 253 | 1/2/1970 2:43:41 AM | 39000 | 10 | 76347 | 400000 baud: cellbox_id 1 invalid. value: 0x02, crc_read: 0x20, crc_calc: 0x0E | ||||||||||||||||||||
| 39 | 253 | 1/2/1970 2:43:41 AM | 108000 | 11 | 76386 | cellbox_id 0: 0x16 (22MY) | ||||||||||||||||||||
| 39 | 253 | 1/2/1970 2:43:41 AM | 148000 | 12 | 76425 | cellbox_id 1: 0x16 MY) | ||||||||||||||||||||
| 38 | 253 | 1/2/1970 2:43:41 AM | 148000 | 13 | 76463 | Cell type detected: 22MY | ||||||||||||||||||||
| 56 | 253 | 1/2/1970 2:43:41 AM | 148000 | 14 | 76519 | Latching 12V Output ON, lowest cell:3654mv | ||||||||||||||||||||
| 45 | 253 | 1/2/1970 2:43:41 AM | 150000 | 15 | 76564 | Fault set: IN D/NO CELL TYPE |
January 1st 1970 is when Unix time started, which is basically the zero point from where all computers count from to know what the time is. It's why in many calendar apps you can't scroll back before then, because to the computer that time doesn't exist. Being the first entry in the logs it can be assumed it writes that before it does the count to figure out the actual date and time.Thanks for the info. I assume that means it is expected and normal to start with a date of 1970. So then for me to see the real date, I need to look at the date where it first changes.
The EEPROM read fails are probably an issue.Perhaps because of the "BMU ineligible" error. But neither error tells me why it happened.
Cas :)
| 3 | 253 | 6/4/2026 9:31:10 PM | 764000 | 48 | 1114 | Fault set: CONTROLLER_WARNING | |||||||||||||||||||
| 35 | 253 | 6/4/2026 9:31:10 PM | 766000 | 49 | 1149 | controller warning 50 | |||||||||||||||||||
| 27 | 253 | 6/4/2026 9:31:11 PM | 314000 | 50 | 1176 | MBB RTC Valid | |||||||||||||||||||
| 38 | 253 | 6/4/2026 9:31:11 PM | 316000 | 51 | 1214 | Fault cleared: DC_DC_LOW | |||||||||||||||||||
| 47 | 253 | 6/4/2026 9:31:13 PM | 736000 | 52 | 1261 | Fault cleared: CONTROLLER_WARNING | |||||||||||||||||||
| 69 | 253 | 6/4/2026 9:31:22 PM | 982000 | 53 | 1330 | CHARGER LSS: Freeing CHARGER node id 0x10 for charger 0 | |||||||||||||||||||
| 26 | 253 | 6/4/2026 9:32:22 PM | 610000 | 54 | 1356 | Key Sw = OFF | |||||||||||||||||||
| 64 | 253 | 6/4/2026 9:32:22 PM | 704000 | 55 | 1420 | Control flags changed. Old: 0x204076 New: 0x204078 | |||||||||||||||||||
| 43 | 253 | 6/4/2026 9:32:22 PM | 705000 | 56 | 1463 | State change from STOP to HIB | |||||||||||||||||||
| 50 | 253 | 6/4/2026 9:32:22 PM | 725000 | 57 | 1513 | MTC pending change by 3 from 0 to 0 | |||||||||||||||||||
| 75 | 81 | 6/4/2026 9:32:22 PM | 726000 | 58 | 1588 | 0 | 0 | 0 | 96 | 114300 | 0 | 0 | 100 | 0 | 0 | HIB | 48 | 2960 | 37 | 34 | 0 | 0 | 13296640 | ||
| 70 | 253 | 6/4/2026 9:32:22 PM | 727000 | 59 | 1658 | Disch limits: curr 897 cap 897 act 2147483647 pow 102527 | |||||||||||||||||||
| 63 | 253 | 6/4/2026 9:32:22 PM | 728000 | 60 | 1721 | Ch limits: curr 83 cap 83 act 2147483647 pow 9486 | |||||||||||||||||||
| 29 | 84 | 6/4/2026 9:32:22 PM | 728000 | 61 | 1751 | 0 | -65028 | 0 | -1 | ||||||||||||||||
| 64 | 253 | 6/4/2026 9:32:22 PM | 731000 | 62 | 1815 | Control flags changed. Old: 0x204078 New: 0x200070 | |||||||||||||||||||
| 60 | 253 | 6/4/2026 9:32:22 PM | 733000 | 63 | 1875 | Disable flags changed. Old: 0x0000 New: 0x0004 | |||||||||||||||||||
| 106 | 253 | 6/4/2026 9:32:22 PM | 739000 | 64 | 1981 | Stopping 12v charge. DC-DC 13378688uV, Battery 13296640uV, Combined 13135518uV, Ambient 30C |
Maybe it's a little too late but here is a trouble shooting suggestion. The unofficial Zero manual has a description for building an adapter to read information through the OBD port. It's for Gen 2 bikes but works on Gen 3 also. I think I had to switch the TX and RX wires and use a different Baud rate but after some messing around I got it to work on a laptop. When you key on the bike you can see all the start commands as it is happening. You can see all the commands just like you see in the logs, the same when you plug into charge. Pretty useful for trouble shooting. If you type in "help", you bring up a menu of all the info you can get. It's fun even if you don't need it. There are posts about it from a long time ago. Here is an example. This is "BMS interface" screen. You can see things like charge targets, lowest cell voltage, how many amps the headlights are drawing, pack capacity.Thanks, that could be handy.
Good to hear it's working. Intermittent problems are the worst! Make sure your towing insurance is paid up, ha ha!I think it all had to do something with the bike sitting a bit too long, such as the battery getting out of balance causing the BMU to stop the charge. Perhaps right on the edge. After around 20 charge attempts, it started to charge fine. IOW, I don't think the fix was anything else that I did.