openinverter forum

Hey ho everyone.
We discussed today about the lack of organization of firmware development, at least when it comes to inverter firmware. Probably other projects, too.

Now, the situation is, that I wake up every morning knowing there are a number of outstanding issues and improvements. But when I sit down in front of my computer, I can't actually remember what they were and where to find them. So I watch youtube instead. Not good.

We discussed somehow to extend the forum to organize tracking but it's probably easier to use a bug tracking system that is actually meant for the task: github issues. E.g. for inverter that is this: https://github.com/jsphuebner/stm32-sine/issues

Now, I think the forum is still a great place to assess whether a given issue is a user or system error. But if it turns out to be the latter, we need to keep track of it. Otherwise chances are it won't be fixed.

So that would be the "process": discuss on forum -> open an issue if appropriate

That's where the solution begins. Hopefully. Thanks

I think this is an excellent step forward. Thank you!

Fully agree. Started the process with this: https://github.com/jsphuebner/esp32-web ... e/issues/1
I think it would help if everybody thinks about the topics which were discussed in the past, and if something seems to be open, just discuss and create an issue for each.

I've created an issue for another frequently requested feature - dead-zone free regen throttle mapping: https://github.com/jsphuebner/stm32-sine/issues/38

Please could we create some tags to properly label "feature requests" and "bugs"?

Cool, I see this is catching on. Thanks very much
Also the "new firmware" threads tend to have issue-ish stuff in them.

johu wrote: ↑Fri Oct 20, 2023 6:36 pmNow, the situation is, that I wake up every morning knowing there are a number of outstanding issues and improvements. But when I sit down in front of my computer, I can't actually remember what they were and where to find them. So I watch youtube instead.

Most of us have also discovered this technique to avoiding progress. It has an almost perfect success rate.

catphish wrote: ↑Fri Oct 20, 2023 8:32 pm Please could we create some tags to properly label "feature requests" and "bugs"?

"enhancement" and "bug" already existed as label and I have added "safety" for safety critical enhancements.

johu, could you enable the "Thanks" feature Announcements? It's present in other General|General threads (non-Announcement) threads, but not this one.

Moved the wifi discussion: viewtopic.php?t=4512
Please don't discuss concrete issues here

asavage wrote: ↑Thu Dec 07, 2023 7:18 pm johu, could you enable the "Thanks" feature Announcements? It's present in other General|General threads (non-Announcement) threads, but not this one.

Seems to be a limitation of the plugin, couldn't find any option to enable it here

Hi! Sorry if this is the wrong place to post this. I'm an EE by trade who's been working in the microelectronics industry for the past 12 years and is just now trying to cut my teeth in contributing back to open source projects. I've got extensive experience in C programming for embedded devices, and familiarity with power electronics systems. I own two EVs, but the most hands-on experience I have with electric vehicles specifically is building the battery pack for my eBike conversion. I dream of one day converting a yellow Jeep Wrangler for my wife.

I have free-time, a reasonable amount of cash for buying components, and I'd love to help out. Where can I be the most useful?

greetings, when trying to compile the stm32 charging firmware, it gives an error, there is no file in the nvic library.

I had the same issue. The answer can be found by searching for "nvic" over the complete forum, and we get here: viewtopic.php?p=64542#p64542

I think we have a bug in the VCU version 2.30.TE, the accelerator pedal position is overwritten by some values, the LDU is also no longer accessible via WiFi, after a downgrade to 2.30.TD, everything works normally again, maybe someone can take a look at it

medo wrote: ↑Mon Feb 24, 2025 7:28 pm2.30.TE

Why are you on that version. Where are the values being overwritten? provide more info as this is zero to go on.

oh, my mistake, everything is working, well I installed the version for testing, to give feedback if desired, and in the hope that the drive direction finally be transmitted to the LDU

Was there an update with any notes of that being worked on.

https://github.com/damienmaguire/Stm32-vcu/issues/129

Again it is on my list to look at.

Some people have it working apparently as touched on in the topics you opened about this before.

I'm sorry, I must have overlooked that

johu wrote: ↑Fri Oct 20, 2023 6:36 pm discuss on forum -> open an issue if appropriate

My apologies for sending a DM to ask how to ask about a feature or enhancement. And after getting my ears boxed and some more research I read Johannes' post about features and issues above. So hear goes.

Subject: Zombieverter - Enhancement for utilizing the BMS (master and slaves) and Contactor unit from the Ioniq5 Battery pack. I do note that there is work going on (or was going on) to discover the CAN mapping of the BMS (Thanks for the links, Bratitude!)
viewtopic.php?t=1179
viewtopic.php?t=2243

If there is documentation to add the Ioniq5 CAN Communication to the Zombieverter, I would be game to try as I have the full 32 module Ioniq5 battery pack and am planning to buy the Zombieverter VCU.

I noted from the page https://openinverter.org/wiki/ZombieVerter_VCU that the intent was for "An open-source EV conversion VCU (vehicle control unit) for controlling salvaged EV components!
I also note that it currently supports these salvaged and off the shelf parts. Nissan leaf BMS/battery pack, kangoo bms, orion bms, imp bms, ISA shunt, BMW SBOX, VW EBOX.
So it seems to me that adding the Ioniq5 Battery BMS and contactor box would be a good addition.
My concern is I have no knowledge of the VCU project as I was having 4 back fusion surgeries and recoveries over the last 4 years and was mostly out of touch from openinverter.org. I have a lot of catching up to do and would appreciate thoughts, direction and any hints.