openinverter forum

LRBen wrote: ↑Thu Sep 14, 2023 8:08 pm but if anyone gets bored of waiting here is the cut down arduino script that runs the charger.

Hello,

I'm trying to run your program. What connections do you have to OBC apart from GND/+12V and PT CAN?

Electrocuter wrote: ↑Wed Jun 05, 2024 6:38 am Hello,

I'm trying to run your program. What connections do you have to OBC apart from GND/+12V and PT CAN?

I had it connected to a charge socket as well, most important things on the charge port is the temperature sensors. Or you can fake it with a resistor. If you code out the locking motor on the charger you don't need to connect that. It will also want CP and PP from the charge socket.

I have had it running on a Zombie now, it does work but the current ramping isn't very smooth near the end of the charge. It could probably also do with a better way to read when to go into charge mode. Code is on my github if you wanted to have a look.

Thanks, will give it a try. I will try to run it on the bench without a VW socket so I'll have to trick the OBC. I guess I'll have to find where the charge port temperature sensors are connected to the OBC.

Electrocuter wrote: ↑Thu Jun 06, 2024 4:58 pm I guess I'll have to find where the charge port temperature sensors are connected to the OBC.

The pin out is the same across all MEB/MLBevo chagers. Damien has a useful github with the pinouts on.
https://github.com/damienmaguire/VW-OnBoard-Charger

The MEB chargers thread also has some useful information on connector part numbers I think.

Mitchy wrote: ↑Mon May 08, 2023 11:42 pm Download link for the Project Files, A 7z file of the IDEX Project file folder, Gofile link as it was the easiest way to get this out:
https://gofile.io/d/8jLy7v
Will try to upload to a more suitable host in the future

Can you reupload please? The file is down.

I am starting now also to get my charger running. I put all the information in this posts into the Wiki: https://openinverter.org/wiki/VAG_MLBevo_MQB_Chargers

modellfan wrote: ↑Wed Nov 06, 2024 6:40 pm I am starting now also to get my charger running. I put all the information in this posts into the Wiki: https://openinverter.org/wiki/VAG_MLBevo_MQB_Chargers

Did you manage to get it working and which part number do you have?

Mitchy wrote: ↑Thu May 04, 2023 11:33 pm Quick test video.

Hi, what part number is the charger? Did you manage to make any more progress on this? Would it be possible to use it without the original charge port cover door etc? Would you share your complete latest code?

Should have more on this very soon.
I’ve ported the code over to one of the blue Can filter boards here: https://openinverter.org/forum/viewtop ... 922#p80922
Just using the OI ‘Tesla Charger’ can interface signals for now, so from Zombieverter, the charger appears as a tesla unit.
Keeping all the CAN signals for now, as I’m not sure what would be usable when trying to get CCS charging running.

Doing it this way (using an interface board) as I’m spoofing quite a few CAN signals and I’m not sure how well Zombie will keep up with this, along with the 1000 msg/sec that I’m spoofing for my Vehicle CAN.

I have a pretty rudimentary coding function written, this allows selecting between Type 1 and Type 2 charge schemes, and basically configures the charger between a UK or US coding.
I’m a bit worried as it doesn’t have many safeguards as of yet.

In a few days I should have things cleaned up enough and I’ll upload it to GitHub.

m.art.y wrote: ↑Sat May 10, 2025 8:47 pm Did you manage to get it working and which part number do you have?

Yes , got it working on bench . Don’t have the part number by hand. It’s 11kw Audi Etron . Did a detailed tutorial video but never uploaded it. Maybe I should

Mitchy wrote: ↑Mon May 19, 2025 2:34 pm Should have more on this very soon.
I’ve ported the code over to one of the blue Can filter boards here: https://openinverter.org/forum/viewtop ... 922#p80922
Just using the OI ‘Tesla Charger’ can interface signals for now, so from Zombieverter, the charger appears as a tesla unit.
Keeping all the CAN signals for now, as I’m not sure what would be usable when trying to get CCS charging running.

Doing it this way (using an interface board) as I’m spoofing quite a few CAN signals and I’m not sure how well Zombie will keep up with this, along with the 1000 msg/sec that I’m spoofing for my Vehicle CAN.

I have a pretty rudimentary coding function written, this allows selecting between Type 1 and Type 2 charge schemes, and basically configures the charger between a UK or US coding.
I’m a bit worried as it doesn’t have many safeguards as of yet.

In a few days I should have things cleaned up enough and I’ll upload it to GitHub.

Are you aware , that the teensy code was already ported by someone to Zombie ? It is on GitHub https://github.com/SomersetEV/Stm32-vcu -> cayenne branch

I was going to leverage that codebase as it's pretty well complete, but it was based on a early version of the teensy code.
I messed up the 'IF' statements, only using one = sign... No clue how it worked, or how I even managed to do it other than a "replace all", but shockingly the state machine still worked... Although it's very unstable and can keep the charger port locked unintentionally.
If you just set the IF statements correctly, the state machine doesn't work, so it was a early screw-up that lucked into working

From the initial code, I've been revising the state machine a bit and was trying to get my head around how best to implement a standalone & zombie based version. I left all the messy comments and such, so it's an organized mess that I understand
Also have the lock/unlock commands figured out.
Been trying to sort out the max SOC cutoff signal, right now the charger will Soft Stop when SOC reaches 100%.

I've actually spent the last few nights porting it over to Zombie's CAN 3. Hoping to test to see if the SPI CAN is suitable. Plus the SPI channel is underutilized, so it's best.

The hope is that the charger will eventually work with CCS charging, So there's a bit of an unknown until I can mimic a CCS session, hence why I want to keep all the extra CAN spoofing, in case there's a need for a BMS signal or added safeguard.

modellfan wrote: ↑Tue May 20, 2025 9:14 pm Did a detailed tutorial video but never uploaded it. Maybe I should

Yes please!

Mitchy wrote: ↑Wed May 21, 2025 11:33 am I've actually spent the last few nights porting it over to Zombie's CAN 3. Hoping to test to see if the SPI CAN is suitable. Plus the SPI channel is underutilized, so it's best.

If I understand you correctly and you are now implementing a more advanced version on zombie using CAN3 I am highly interested. Please share the git repo, I would like to collaborate with you. Same target for me. Make the charger stable on Zombie VCU and integrate it with FOCCCI. Either on template repo of johuebner or on current ZombieRepo as fork.

Mitchy wrote: ↑Wed May 21, 2025 11:33 am I've actually spent the last few nights porting it over to Zombie's CAN 3

Why CAN3?

In my deployment I have the OI can on CAN1, Vehicle CAN on CAN2, so I figure CAN3 is a safe bet.
It's a shame it's so under utilized. (I understand why)
I'm also assuming no one really uses Chademo now with Focci and CCS options coming up.
It's easy enough to port back to the STM CAN channels, I just needed to keep things separate to get to the next step without worrying too much about bus clashes.

The Charger scope hasn't been the highest priority, as I only installed my batteries in the car last week. haha
But now that I'm getting to the point where I'll need to top them up, this is the next main thing on my list.

Leaning on your FOCCI code addition, as I'm using all the same parameters for the CCS stuff; in hopes that the VW charger will also support CCS charge natively.

So you didn’t start yet ? Should I set up a repo ? Would you be interested to collaborate implementing the code as Zombie software module ?

Just an update.
CAN3 was a fail...
At least with my CAN messaging strategy of just dumping whatever message needed into it's respective timer, which resulted in a cue of 4-8 messages to have to send.
May have been more successful if I spaced them out by 5-10ms each, as the duration between messages is key, but not the fact that they all come at once.
Something to note is that the CAN3 requires a delay (implemented as a NOP) so after so long of a delay, the OI CAN interface will time out if there's a consecutive NOP delay of much more than 30000 cycles.

Anyway,
Rolled everything back to use CAN1/CAN2.
Code should be portable between Zombie, and Zombie+CanBridge... What I've done is use the same base code and Chargerhw class.
Moved onto creating a custom CAN interface map between Zombie and the CanBridge,
Realistically most will just use the base Zombie code.

Todo:

• Strip out my hacky simulation code for bench testing

• Add a toggle into Zombie for the UDS Coding.

• Create CAN timeout failure modes

• Need a way to silence the bus, as any network traffic seems to wake the charger.

• If bus is asleep, need to do some testing on bus recovery on charger wakeup

Any chance this code will work on the older MQB chargers, like the 3.6kW I am trying to run? I think I know the answer, but having a quick comparison with Damiens initial code, it seems FlexCAN is running here, and not in the initial one, hence my question......
I hope to throw each ID using SavvyCan at the charger & see what values I get back. Anything giving nothing, I would remove & see if I get life out of it, but the FlexRay has me wondering if I need to convert the code beforehand.

Finally found matching NW12 water connectors, from BMW dealer.
17108417218 / 8417218 is straight for 17mm hose, this was only 2€ from BWM!
81318423188 / 8423188 is 90deg sadly only for about 9mm hose, 10€ from BMW

modellfan wrote: ↑Tue May 20, 2025 9:14 pm Yes , got it working on bench . Don’t have the part number by hand. It’s 11kw Audi Etron . Did a detailed tutorial video but never uploaded it. Maybe I should

Hi, did you manage to upload it? Would you share a link to your channel?

Mitchy wrote: ↑Mon Jun 02, 2025 11:18 am Just an update.
CAN3 was a fail...
At least with my CAN messaging strategy of just dumping whatever message needed into it's respective timer, which resulted in a cue of 4-8 messages to have to send.
May have been more successful if I…

Do you have a git link ? I want to collaborate on the open points .

@myart I will cut the tutorial soon . Give me some more days

Car is charging with the teensy code. @mitchy I would really appreciate if you can share your zombie Vcu code so we can join forces . Whould be sad to redo , what you already did.