I've now tested the updates from master-dec-update, everything is running and switching as expected, but the LDU is still running backwards and communication with the web is not possible (Node3), and the temperature is still not correct with fan activation.

I think I now understand why I don't see CAN message 0x55 when the VCU is in ignition mode, in order to start the inverter. Since the engine speed of 750 rpm is already programmed in when the ignition is switched on, BMW doesn't allow a start because it thinks the engine is already running. It would ...

I've noticed another thing: the fan starts immediately, even when the temperature is at 8 degrees and 40 is the default setting. I have to set the temperature in the web interface to over 65 degrees for it to turn off; this must also be a bug.

Quick report: I replaced this in Can_OI.cpp
if(Param::GetBool(Param::din_forward) && opmode==MOD_RUN) tempIO+=8;//only send direction data if in run mode
if(Param::GetBool(Param::din_reverse) && opmode==MOD_RUN) tempIO+=16;//only send direction data if in run mode
with
int dir = Param::GetInt ...

Is this the file that's responsible for all of this? CAN_OI.cpp
Oh, I see, a lot of code is missing.

Back then you reprogrammed something and it worked, unfortunately I can't find that working firmware anymore.

https://openinverter.org/forum/viewtopi ... 664312091a

Yes, that worked a while ago, we even discussed it in another thread, but it hasn't worked since the new update 2.30. I sent the signal to the LDU via savvycan, and that works perfectly.

manny wrote: ↑Wed Jan 14, 2026 3:48 pm Does the gear inputs change on de vcu spot values?

Please post parameters json files.

Take a look at the screenshots above, and maybe read all the posts as well.

News about the faulty CAN communication to OI ?

I'll test it right away with version 5.35; yes, no signal is coming from the VCU via CAN for drive direction, only brake, start, and accelerator pedal are transmitted.


edit: i test it, The same applies to the downgrade; it can only be due to the VCU.

google übersetzer ist schon beschissen

LDU VCU with the car in forward gear and the brake pedal pressed down.

Pot1 and Pot2 are sent normally from the VCU to the LDU, as are the brake and start signals; only the drive direction remains at 0 and does not react at all.

Quick update: after testing with the Jaguar shift lever, there was no reaction on the LDU side, so it could be a software bug.

No problem, I'll do another test with the Jaguar gearshifter. Have nice holidays and a happy new year!

Has the CAN communication between the zombie and the LDU been tested? Because for me, the drive direction isn't working; everything is being passed through, brakes and inverter start works, but there's no drive directionl.

Just use the zombieverter and select the BMW E65 under vehicles, then you'll have peace and quiet. The CAN IDs are the same as for the Mini. Furthermore, the zombie can also perform many other tasks, such as controlling pumps and fans.

Hi, I have a problem with the Drive direction from the VCU to the LDU. The VCU clearly shows that the Drive direction is changing, but this isn't being passed to the LDU. Do I need to specify this in the canmapper? It should normally work without it. VCU version 2.30, LDU version 5.39

I think I've found something. I connected everything to the CAN network and monitored it on the SavvyCAN. Signals from the LDU and charger were missing. I then disconnected them individually, and lo and behold, when the ESPCANWeb isn't connected to the network, everything works perfectly. Perhaps ...

It's the current, unchanged 2.30a version, but it's displayed as 2.22a on the web. I only have the VCU connected to the CAN bus. As soon as I plug the Tesla DC-DC converter into the same CAN bus, the fan starts at the preset value of 40 degrees. To turn it off, I have to increase it to 65 degrees ...

It's strange, I even tried switching the pin to SL1, and the same thing happened. If I increase the activation temperature to 65°C, the fan switches off and then switches back on below 60°C. That shouldn't be happening. I'll try simulating the temperature via CAN bus and see how it behaves.

Quick update: it also works with espcanweb. I only realized a bit late that there seems to be a problem with my BMS somewhere; otherwise, your firmware works perfectly.

I'm experiencing a really strange issue here: when I connect the Tesla DC/DC converter to the CAN bus and then turn it on via the web interface, it immediately switches on the fan that I connected to GPout3. I can't turn it off again unless I disconnect the CAN bus and restart the VCU. I need to try ...

One small thing isn't working yet; I can't get a connection to the ESP32CANWeb. It was originally on Node 2. To rule out wiring errors, I flashed the old firmware, and now everything works again and I have a connection.

Perfect, it works! Tomorrow I'll wire everything up and report back on how it all works together.
Thank you so much, you made my day!