Page 1 of 1
16383rpm issue on startup
Posted: Thu May 11, 2023 10:09 pm
by Domt177
Hi everyone,
Having an issue with my leaf gen 1 (EM61 motor and inverter) used with a zombieverter.
When I turn the inverter on after precharge (when I give it 12v supply to both permanent and ign) the web interface reads the speed as 16383rpm, this obviously means it won’t send any torque request and so won’t spin.
I know comms between the inverter and zombie are good as it’s reporting invUDC and temperatures correct
Any help appreciated
Thanks
Re: 16383rpm issue on startup
Posted: Fri May 12, 2023 11:22 am
by Domt177
I’ve plugged in my Canbus reader and can see 0x1DA and 0x55A but can’t see 0x120 which I believe is supposed to be sent by the inverter, which is odd as it’s sending temps and voltage
Re: 16383rpm issue on startup
Posted: Sun May 14, 2023 12:16 pm
by Domt177
I’ve now narrowed this down to I think the inverter sending an error state as b6 & 0xb0 aren’t 0, any ideas about how I can go about reading this error to find out what it might be?
Re: 16383rpm issue on startup
Posted: Sun May 14, 2023 12:46 pm
by royhen99
Are you using DBC file to interpret messages?
EV-can_ZE0.dbc has B6 of 0x1DA as a message counter that cycles between 0 and 3.
Re: 16383rpm issue on startup
Posted: Sun May 14, 2023 4:19 pm
by Domt177
royhen99 wrote: ↑Sun May 14, 2023 12:46 pm
Are you using DBC file to interpret messages?
EV-can_ZE0.dbc has B6 of 0x1DA as a message counter that cycles between 0 and 3.
Loaded the DBC,
MG_Clock is counting normally (0,1,2,3)
CRC_1DA which I’m assuming could be the error state part of the message is cycling between 85,95,208 and 218
Re: 16383rpm issue on startup
Posted: Sat Oct 21, 2023 7:08 am
by EV_Builder
Check if the variable in code has an assignment for a value even when the canbus isn't connected at all. So simple test: disconnect CAN and reboot inverter SW and check web GUI
Re: 16383rpm issue on startup
Posted: Sat Jan 20, 2024 3:04 pm
by Rojerrojer
Did you ever find a solution to this? I think I have the same issue but with a Thinderstruck VCU. I would really appreciate any feedback or solution you may have found. I am hoping the inverter or motor resolver are not toast.