Idea: merging Openinverter and Zombieverter codebase

[peakPWR]

I just came up with an idea while I was trying to read through ZV firmware source:
ZV is based on OI so both share some code but as discussed in another thread, ZV got extended over a long period of time and that's why the code is not as clean as it used to be (no offence, just taking notes).
On the other hand the OI code seems pretty clean in my opinion.

Crazy thought: Would it be possible to "start all over" with a fresh template of OI and add ZV features to that code base?
Final goal would be to merge the software entirely so OI supports the Zombieverter hardware.

This way we could create a healthy environment as we "start all over" although we don't really have to start from zero.
Additionally we support two diffferent concepts: OI with it's direct connection to inverter hardware and ZV with it's more CAN message oriented approach.

So my question: is this possible? Is this a good idea or am I missing something?
I value the open source nature of both projects and all the effort that went into it, so don't get me wrong, I'm not complaining, it just seems like a good thing to do.

[tom91]

Feel free to do it yourself.

You understand right there are two distinct functions conducted by various bits of code.

ZV is currently being reworked by myself.

Please not OI is an "eco system" there are various/lots of code bases for certain aplications

STM32_Sine/FOC = OI replacement control logic
STM32_Charge = Tesla Charger
STM32_VCU = ZombieVerter VCU

All built on the OI code base.

I do not understand what you are trying to achieve?

[peakPWR]

Please not OI is an "eco system" there are various/lots of code bases for certain aplications

STM32_Sine/FOC = OI replacement control logic
STM32_Charge = Tesla Charger
STM32_VCU = ZombieVerter VCU

Thank you for your clarification.

My misconception is that zombieverter is a fork of OI but it's more like a the VCU part of that ecosystem.

Ok that's my fault then ... now I understand!