ZombieVerter VCU Support

[Jack Bauer]

You can indeed alter the min and max torque delivered. This is described in the video dealing with the parameters. From reports of others there does indeed seem to be a problem with the torque command in the 450h. This is part of the reason I'm currently installing a 450h system in my E39 as there is no point asking anyone else to work out a solution. Once I have the car rolling I'll debug and update the release firmware on Github.

[AdrianB]

UDCMAX missing!

UDCmax is not showing in my parameters list on the web interface. Has it been relabelled or is there some way I could have accidentally deleted it?

[Jack Bauer]

its now called udclim.

[Jack Bauer]

So new batch of VCU boards on the way from JLC. I have upreved the board to V1a to cover the following changes :

-Add footprint for Wemos D1 wifi module
-Move C71 and tracks to better clear mounting holes
-Remove I2C EEPROM and associated components as is unnecessary and just ads cost.

I'm also pleased to announce that as of this batch ALL parts will be included in the kits and the MCP25625 is now available from JLC for the first time since this chip shortage nonsense began.

[EvSteeve]

Hi guys following my wifi nightmare, i have (In short bursts) been able to reconnect and confirm i am on the latest firmware,
i have a couple of questions regarding this firmware..

After loading the firmware it shows i am still on version 1.00a but i have defiantly loaded 1.01 and also the can connection parameters have changed with the update.

With the can connections, why are there only 2 options when there are 3 can networks on the vcu?
With Everything on 'Can 1' I get udc readings from the shunt, but on can 2, (Which in the documentation the inverter shunt etc is wired to)

The leaf motor will also not spin on the firmware, which it would on 1.00a

I am getting readings from the Pot and also Potnom % is rising with throttle application..

regards

[AdrianB]

After loading the firmware it shows i am still on version 1.00a but i have defiantly loaded 1.01

I had the same concern with mine when I updated the firmware, however Damien confirmed a few posts back that he hadn’t updated the version number. Can’t help with the CAN questions as I’m only using CAN for the shunt. Good luck.

[Jack Bauer]

Yes the new firmware does need to have the rev number updated. Its on my to do list. As of this release can3 is reserved for chademo and other specialist functions such as swcan for running the volt/ampera heater etc.

[streber]

I have two wires coming out from each, one goes to the zombie connector and the other goes to the GS450H VCU connector. This is so I can plug in either the zombie or the GS450H VCU to run the one driveline...for testing purposes

I would hook everything up and check continuity from the header pins on the underside of the VCU board to a pin inserted into the inverter connector. Maybe a bad connector or solder joint in there somewhere. Then I'd start checking the CAN transceivers to see if one of them got fried. I've had both of these happen at various points in my project.

[catphish]

I visited EvSteeve yesterday to assist with his STM32-VCU setup. He has an Isascale shunt and Leaf inverter running on the same CAN bus (he says this is CAN EXT2, but I didn't confirm this).

I observed the following:
* The reported version number of 1.01 is 1.00A (already confirmed and discussed)
* With firmware 1.00A the precharge process works correctly and the motor spins
* With firmware 1.01, there is a new choice of CAN1 and CAN2 for each function. When I set all options to CAN1, the precharge works (ie data is read from the shunt), but the leaf inverter does not spin the motor.

I didn't have time to debug properly (quite literally, the wifi module overheats and crashes after about 60 seconds), but it would seem that there is still some confusion around the selection of buses.

I've suggested he order some D1 minis and adapter boards to replace the bad wifi modules, but it would be helpful if anyone with an understanding of the code could suggest why setting all interfaces to CAN1 causes the shunt (on CAN EXT 2) to work, but not the leaf inverter on the same bus.

[AdrianB]

I've suggested he order some D1 minis and adapter boards to replace the bad wifi modules

I have some adapter boards arriving any day now. The minimum order was for five so I’m happy to share the spares. Shippings says they arrived in the UK yesterday, so PM me your address and I’ll post them on once they get here.

[Jack Bauer]

Brilliant. Another bug for me to find.

[marcexec]

I have a spare D1 mini in Dublin if anyone is stuck.

[Kelju]

After quite a while of working on my battery assembly for the RX8 it became time to implement the associated modification to the Zombie this evening.
I flashed in my bin file and noticed that the activity led is not blinking anymore.
In previous occasions this has been due to some coding bug and the revival to operational state has been possibly by flashing in the known working FW.

Now I am facing the situation that the dam activity led just won't start blinking no matter which FW I flash in (the flash process seems to go through normally according to the web interface).

Any idea what's the problem with the Zombie and how it can be revived?

[dadiowe]

Hi,
This .bin file is a blank file. I recall Damien giving me the link for it.
If you flash this file then power down and repower the Zombieverter then use the latest recommended .bin file on the github page it might cure your problem. I have tried thid method myself and it has worked for me.

[Kelju]

Thank you. I will give it a try.

[Jack Bauer]

This problem is also covered in the videos in the wiki.

[sigdigits]

Any suggestions for an unlucky individual that is trying to program a board with the GD chip? I'm sure in the end the answer will be... replace with an stm32, but due to the chip shortage here I am.
I am using an stlink programmer in win 10, passed power test with 12v but have solid "3v3 on' LED, no blinky "ACCTY" LED
I tried uploading the .hex that Damien shared in this thread for the GD chip (GD32F107VCT6), stlink utility shows program uploaded and device memory matching the .hex file

After much hair pulling, I was able to program a bare esp12f with the esp8266 web interface, so maybe I can try that after I get it connected to the zombie

[EV_Builder]

Any suggestions for an unlucky individual that is trying to program a board with the GD chip? I'm sure in the end the answer will be... replace with an stm32, but due to the chip shortage here I am.
I am using an stlink programmer in win 10, passed power test with 12v but have solid "3v3 on' LED, no blinky "ACCTY" LED
I tried uploading the .hex that Damien shared in this thread for the GD chip (GD32F107VCT6), stlink utility shows program uploaded and device memory matching the .hex file

After much hair pulling, I was able to program a bare esp12f with the esp8266 web interface, so maybe I can try that after I get it connected to the zombie

I can send you an STM if you like. In the end we are here to help .
DM me and let me know the exact spec. you want not sure if i have the same memory size as sold by "Jack"

[Jack Bauer]

https://lcsc.com/product-detail/Microco ... C8315.html

[sigdigits]

https://lcsc.com/product-detail/Microco ... C8315.html

That's awesome they finally got stock, I'll grab some THANKS!!

I still want to try and program the GD chip if it's at all worth it... it IS already soldered onto the board
I was going to try and clone the repo and make the edits listed in the wiki, but I got a permissions/password error when I tried cloning it from git.
STlink utility "fails successfully" showing the code uploaded, but the board only shows the 3v3 LED solid, and ACCTY LED unlit

I still have to try the OTA update, but I need to curl the file system files to the esp chip before I can attempt that

[EV_Builder]

You need to flash the bootloader too...

[sigdigits]

You need to flash the bootloader too...

Thanks... I just saw that re-reading through the wiki/forums! I was thrown off as I was able to just upload the .hex to my tesla charger board. STlink utility seemed to give the same success messages as well, adding to the confusion.

Side note, I get this error trying to clone from git:
"Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists."

The libopeninv source folder with the files that need modificaiton is empty, can I copy them from the stm32-vcu git page?

[EV_Builder]

You don't need to load a key etc. for just clone ing the repo. and enable recursive so you get those deps. like libopeninv and libopencm3.
There is a thread about toolchain. Read that one (i recommend).

[electromatic]

Hi, just wanted to say that NCV8461DR2G is available at RS again if you are missing this one. https://uk.rs-online.com/web/p/peripher ... ps/1869867.

[sigdigits]

You don't need to load a key etc. for just clone ing the repo. and enable recursive so you get those deps. like libopeninv and libopencm3.
There is a thread about toolchain. Read that one (i recommend).

I guess I didn’t clarify well enough... I get that error when I use the command line to clone the git repository.
If I download the source code, those folders are empty

I’m got the bootloader loaded with stlink, and accty blinking now. I’m going to try uploading the firmware over wifi