outlandnish wrote: ↑Tue Nov 18, 2025 12:01 am Here's the OEM to OpenInverter pin mapping if anyone needs it:

I've spotted a small error in the diagram. Pin 1 is Proximity Input on the OEM but is the Start Input on the OI board. Would be nice to get an update.

That looks spicy. Might it be an idea to put that on a small mod board to test out before going for broke on one of your giant PCBs?

Ah. Thanks for the background. It makes sense they would keep things the same.

I have the bits so I was going to try to get at the leadframe and resurrect one. It should be possible to compare both sensors for science.

I have a bit of confusion about the current sensors. I bought MLX91209LVA-CAA-000 parts which are set to 50mV/mT sensitivity as that was what was listed on the schematic. I note that the install video (and now wiki ) lists MLX91209LVA-CAA-002 as the part which is the 7.3mV/mT sensitivity variant ...

Congratulations on getting your motor running!

The oil pump behaviour is concerning. At the moment the code is utterly minimal and just sets the pump to run at a fixed speed irrespective of operating mode, temps, motor rpm, etc. If LIN bus comms are working as you describe but the pump speed can't ...

I was doing that yesterday too. Desoldering the PCB was pretty painless as you point out.

One gotcha that has bitten me since is to do with the current sensor housing. I hadn't appreciated the order from Damien's video and had forgotten to heat the current sensors prior to levering away at the ...

You never know until you try stuff. I've updated OpenInverter CAN Tool to allow fractional second steps between log entries. With a step of 0.1 and you log ALL parameters you only get about 3 a second, VALUES does better at about 6 entries. Nothing melts down and the inverter runs fine.

For proper ...

I've just released v0.5.1 of the tool:

What's New

• Allow fractional logging steps down to 0.1 second
• Add python 3.14 support

Just a minor maintenance release.

Yes but only in 1 second steps. If you add "-s 5" or "--step 5" it'll go in 5 second steps. I'm guessing you're looking for less than 1 second though?

Edit: If you are after smaller time steps than 1 second you're better setting up a CAN map for the params you are interested in. You can use "oic ...

My question is if there was a way to isolate the problem driver or other component with the WiFi web interface or some other troubleshooting method. Thanks in advance for any ideas or support!


I'd definitely recommend getting set up with a CAN configuration tool, either esp32-web-interface or ...

I've published my Saleae Logic 2 extension for the gate drivers here: https://github.com/davefiddes/STGAP1BS-SPI-Analyzer Hopefully it'll appear on their "store" shortly. You can install it manually by downloading it and loading it in Logic 2. Instructions for how to do this are in the repo README ...

Thanks for finding the problem there outlandnish. It's a pretty facepalmingly stupid bug on my part. No idea how I managed to get that in there. Your fix is on the right track but is actually the reverse of what's required. The way the gate drivers work is that the first data to be clocked out when ...

It's entirely possible the gate driver status is wrong. :-/ I'll investigate but it'll be tomorrow before I get to that.

Voltages for Phase B look wild. The zener in the PSU should stop the negative rail getting below -5.1V.

Did you check the board was working before soldering it to the inverter chassis & mosfets? I would recommend bench testing with just 12V and CAN. The inverter should come up and report that the gate drivers are all OK. It doesn't need the big mosfets to function. You shouldn't need to dismount to ...

I could add an OilTemp option to snsm that would copy the tmpoil value into tmpm. This would be passed on to others va the default CAN map on ID 0x190.

Internally the only thing we use tmpm for is derating the throttle (in association with tmpmmax). We probably also need to add a tmpoilmax param ...

I've just pushed support for the motor temp sensor. Managed to temperature cycle it between 0 degrees and 100 degrees and got a nice fit to get the Steinhart-Hart coefficients.

To use it just set snsm to "TeslaM3" (ditto snshs):

oic write snsm TeslaM3
oic write snshs TeslaM3


Note: The option ...

Stumbled across a source for the Sumitomo connector for the main inverter: https://www.aliexpress.com/item/1005005920568514.html
It's from the same supplier, Jorch, as the ZombieVerter VCU housing.

A parts order arrived. I've fitted my STGAP1BS gate drivers (not the STGAP1AS Tesla fit). They seem to be working fine so far and report no faults. I've not put HV on them yet though.

I've also got a set of hall-effect current sensors but haven't fitted them just yet either.

Congratulations on getting things running.

"oic cmd save" or bonk the "Save to Flash" button on the "Device Control" page of oic-gui.

I added support for the correct thermistors to the firmware today. Just pick "TeslaM3" for the "snshs" parameter.

Still working on the motor temp sensor. There was some data from the early days of the project but it doesn't look great. I'll see if I can get a cleaner set of readings.

If you are able to create a new tab on the spreadsheet https://github.com/davefiddes/stm32-sine/blob/M3_DU/misc/temp_sensors.ods with the expected ADC readings at different temperatures. The reference voltage is 3.3V and the "load" resistor is 10k.

I can easily add in a new temp curve temporarily ...

I'm sure that Damien meant to provide the thermistors. They were included with my board. Unfortunately I can't find any helpful identification beyond "47K" on the part. I too am waiting for info on the part number to make sure the firmware has the correct calibration curve.

The most recent ...

Today's discovery, the two throttle inputs are swapped around compared to other OI boards. I'm able to swap them back in the firmware so have opted to do that. The MG DU is also affected but I haven't swapped them as they don't need a custom analog input config for other things.

Damien, can you ...

Plugging the numbers from the MIBA website into the handy Digikey calculator you get a discharge time of 4.8 seconds with a 680uF bus cap going from 350V to 60V. So that's the regulation that Tesla were designing to it seems.

Looks like a charger inhibit input would play nice with the Foccci ...

I've been thinking (dangerous I know) and I think I've found a potential gotcha with the HV discharge behaviour on the current boards.

As long as the inverter MCU has power the HV discharge is disabled. The MCU switches off (or is switched off externally) and the HV discharge kicks on. This is all ...