openinverter forum

Posted: **Sun Nov 28, 2021 7:39 pm**

EV_Builder wrote: ↑Sun Nov 28, 2021 3:18 pm Personally i like more compile time changes and building with make 2 versions of the hex/bin.
But i guess its a taste thing... the reason is that compile time variations means no IF statements in the code when we have a variation point.
(higher performance).
Also for the developer it makes it clearer (syntax highlighting) on which variation he is working.

Selecting targets via make configs seems like it doesn't necessarily have an advantage as far as being less complex. Anyone able to point to a good example of this methodology?

There is a good discussion on the PlatformIO community forum that goes into working with multiple targets in some detail.

It seems like if it was properly implemented, you would externalize all of the platform specifics and call those in via a single IF statement.

Posted: **Tue Nov 30, 2021 9:04 am**

Hello,

I am very glad that the motor turns !!!

forwards everything is OK
only in reverse the engine turns to a constant speed and stays there until I switch to forward again

what could be the problem ?

Posted: **Tue Nov 30, 2021 1:10 pm**

Hey nice job! Regarding your problem I would say we need to know: which version of the software and upload your config.

Posted: **Thu Dec 02, 2021 8:45 am**

PaulHeystee wrote: ↑Sat Nov 27, 2021 5:18 pm Yeah, I was looking for the BOM also, ideally the excel sheet needed for JLCPCB.

As previously mentioned and discussed in video, the design files are currently available on the 10 Euros/month or higher Patreon tiers only.

Posted: **Tue Dec 07, 2021 6:17 pm**

Jack; is the latest working LIM version online / committed to github?
Also i was wondering do we have PWM already working on the VCU?

Posted: **Tue Dec 07, 2021 10:13 pm**

Just wanted to share my finding on the VW Polo pedal.
I managed to take some measurements and found out which pin does what.

Posted: **Fri Dec 10, 2021 11:54 am**

Dunno if this is relevant, re wifi issues.

https://olimex.wordpress.com/2021/12/10 ... p-devices/

Posted: **Fri Dec 10, 2021 3:09 pm**

Brilliant thanks.

Posted: **Mon Dec 27, 2021 1:47 pm**

Now my board arrived just waiting for components.
If there is someone in Sweden or Nordic region i have pcb over.

Posted: **Mon Dec 27, 2021 2:35 pm**

blasaab wrote: ↑Mon Dec 27, 2021 1:47 pm Now my board arrived just waiting for components.
If there is someone in Sweden or Nordic region i have pcb over.

Did you correct the small errors?
I think Damien ships a V2?

Posted: **Mon Dec 27, 2021 3:07 pm**

EV_Builder wrote: ↑Mon Dec 27, 2021 2:35 pm
blasaab wrote: ↑Mon Dec 27, 2021 1:47 pm Now my board arrived just waiting for components.
If there is someone in Sweden or Nordic region i have pcb over.
Did you correct the small errors?
I think Damien ships a V2?

What i know there is only v2 for Lexus controller

Posted: **Mon Dec 27, 2021 3:36 pm**

In the support thread the information is spread out. Other FET partnumbers and some wires/jump leads are needed if I'm right.

Posted: **Tue Dec 28, 2021 9:18 am**

There has not as yet been a V2 for the Zombie VCU. The initial beta boards of which 10 were made and sold at cost to encourage uptake and participation in the project had two pcb layout errors. These were fixed and all release boards are as per schematics.

Posted: **Tue Dec 28, 2021 1:26 pm**

Ahh ok good to know then.

Posted: **Thu Feb 17, 2022 9:07 pm**

P.S.Mangelsdorf wrote: ↑Thu Dec 17, 2020 5:37 pm This looks exciting!

I've got a dumb/uniformed question:

Would it be possible/practical/make sense for some drive units to still create a new logic board for inside the unit, but all it does is connect to an external VCU either over CAN or otherwise?

Would that end up as the same as the current boards, but just controlled over CAN?

I'm thinking about the Tesla drive units, since we know Elon's board doesn't like to listen to CAN unless you ask nicely.

Like I said, very dumb and uninformed question.

Hello.
Is there a way to interface current ZombieVerter VCU with the openinverter Tesla SDU boards?

Posted: **Thu Feb 17, 2022 9:14 pm**

alexbeatle wrote: ↑Thu Feb 17, 2022 9:07 pm Hello.
Is there a way to interface current ZombieVerter VCU with the openinverter Tesla SDU boards?

Yes; by CANbus.

But if you could be more specific; for example if i'm right its not plug and play.

Posted: **Fri Feb 18, 2022 8:59 pm**

EV_Builder wrote: ↑Thu Feb 17, 2022 9:14 pm
alexbeatle wrote: ↑Thu Feb 17, 2022 9:07 pm Hello.
Is there a way to interface current ZombieVerter VCU with the openinverter Tesla SDU boards?
Yes; by CANbus.

But if you could be more specific; for example if i'm right its not plug and play.

I'm doing a conversion with a Tesla SDU with the V6 replacement board -- works great on the test bench. Adding SimpBMS and the Elcon charger + DC/DC.
To tie them all together and do the CCS (maybe CHAdeMO) charging too, I'm considering the super awesome ZombieVerter.

I don't see it currently "natively" supporting my hardware. I watched the wiki videos and see how the web interface covers a lot of ground.
So makes me wonder, would I need to fork the firmware for my case and dive into c++ or there's a way to setup custom CAN messaging via web interface to talk to my hardware.

Posted: **Sat Feb 19, 2022 10:54 am**

The latter, you will need mainly in the VCU work, to tie your combination together. The inverter firmware can be configured pretty much over the webGUI.

I advice to start with pulling the VCU software from GitHub and check if all your hardware is there.

Posted: **Fri Apr 15, 2022 10:15 am**

I am currently pushing larger changes onto the master branch.
Basically I had done tons of refactoring on separate branches and then found development continued at the master branch making my changes unmergeable. So now doing it again based on the recent code.

I will be making functional changes in the near future and I want to work off a clean base. Also I'm thinking it helps the future of ZombieVerter if clean code principles are applied.

Please someone review it and most of all, test it. I'm sure I'll break stuff but since I have no ZombieVerter deployed I can't test myself. I'm doing my best to only do structural changes, no functional ones yet.

Posted: **Fri Apr 15, 2022 1:01 pm**

Alright, forward-ported the structural changes, so we are almost back at this stage: viewtopic.php?p=32602#p32602

Posted: **Mon May 09, 2022 7:35 pm**

I am posting this update/question here as I realize that the support thread is probably not intended for custom code related questions.

So I am still working on the "Float refactor" branch and I am finally at the point to implement my BMS related changes.
Communication with the Think City battery modules requires a considerable amount of CAN messages.
Previously I got the SW responding to the newly introduced CAN messages by modification of the stm32_can.h, but now it does not work.
This is what previously worked, but now I am stuck at 20pcs user message no matter what I put here:

Code: Select all

#ifndef MAX_ITEMS_PER_MESSAGE
#define MAX_ITEMS_PER_MESSAGE    8
#endif
#ifndef MAX_MESSAGES
#define MAX_MESSAGES            10
#endif
#ifndef SENDBUFFER_LEN
#define SENDBUFFER_LEN          20
#endif
#ifndef MAX_USER_MESSAGES
#define MAX_USER_MESSAGES       30	 //Used to be: 10
#endif

Any idea what has changed?
As mentined, I managed to get more CAN messages by changing the "MAX_USER_MESSAGES" with a SW version prior to the Float refactor.

Posted: **Tue May 10, 2022 11:59 am**

Not 100% sure but could it be you're running out of hardware resources for filters?

Posted: **Tue May 10, 2022 7:32 pm**

johu wrote: ↑Tue May 10, 2022 11:59 am Not 100% sure but could it be you're running out of hardware resources for filters?

Luckily the reason turned out to be just my stupidity.

I recall you mentioning at some point, that the amount of user CAN messages will be configured in the makefile in the future.
I did check the makefile, but for some reason I missed this:

Code: Select all

-fno-common -fno-builtin -pedantic -DSTM32F1 -DT_DEBUG=$(TERMINAL_DEBUG) -DMAX_USER_MESSAGES=30 \

As you can see, I have it set at 30 at the moment and now it works!

Posted: **Sun May 15, 2022 7:47 pm**

In case of the powertrain CAN, things are triggered to happen event based with this piece of code:

Code: Select all

static void CanCallback(uint32_t id, uint32_t data[2]) //This is where we go when a defined CAN message is received.
{
   switch (id)
   {
      case 0x521:
      ISA::handle521(data);//ISA CAN MESSAGE
      break;

How do I trigger things based on events (specific messages) on the vehicle CAN?

Posted: **Sun May 15, 2022 8:31 pm**

It's the same function because in main():

Code: Select all

   c.SetReceiveCallback(CanCallback);
   c2.SetReceiveCallback(CanCallback);

openinverter forum

The ZombieVerter VCU Project

Re: The ZombieVerter VCU Project

Re: The ZombieVerter VCU Project

Re: The ZombieVerter VCU Project

Re: The ZombieVerter VCU Project

Re: The ZombieVerter VCU Project

Re: The ZombieVerter VCU Project

Re: The ZombieVerter VCU Project

Re: The ZombieVerter VCU Project

Re: The ZombieVerter VCU Project

Re: The ZombieVerter VCU Project

Re: The ZombieVerter VCU Project

Re: The ZombieVerter VCU Project

Re: The ZombieVerter VCU Project

Re: The ZombieVerter VCU Project

Re: The ZombieVerter VCU Project

Re: The ZombieVerter VCU Project

Re: The ZombieVerter VCU Project

Re: The ZombieVerter VCU Project

Re: The ZombieVerter VCU Project

Re: The ZombieVerter VCU Project

Re: The ZombieVerter VCU Project

Re: The ZombieVerter VCU Project

Re: The ZombieVerter VCU Project

Re: The ZombieVerter VCU Project

Re: The ZombieVerter VCU Project