tom91 wrote: ↑Sat Mar 21, 2020 1:49 pm
Luckily some clever guy took good notes.
Kudos to you Tom!
Currently the Isolated feedbacks and temperatures are unknown and the current ratios, but all pins for the current sensors identified.
So i will let the hot water in and measure the resistance then... the same way i did for Ampera inverter before John Kelly sent me IGBT datasheet.
I couldnt find the NTC beta in the datasheet for MH6560C.
I have an air conditioning compressor from a Passat GTE. That should be the same as in E_Golf and Golf GTE. It is available from € 100 and is controlled by a LIN bus. So far I haven't been able to figure out what to send. The boudrate is 19600. Does someone have a car where to read the signal?
tom91 wrote: ↑Sat Mar 21, 2020 1:49 pm
Currently the Isolated feedbacks and temperatures are unknown and the current ratios, but all pins for the current sensors identified.
Hi again!
I manage to get one VW inverter here. Its so small!
I managed to open it up and i see the brain board gets its signals from the big connector on the side. So your idea was to replace its brain with your own master board. I would ask three questions, though i dont mean to imply the fairytale...
First question Tom91; why does it need isolated power supply?
Next question; Is there only one isolated supply or more required?
Third question; did you figure also the pinout on how to start the DCDC 12V converter? Any info on its connector pins? I see it is also ERNI 1.27mm 8P connector no. 284699.
So my plan is to build my interface board and try to use gen2 controler to drive a motor first with 60Vdc. Then i will try to make DCDC obey.
arber333 wrote: ↑Wed Apr 15, 2020 5:57 pm
I manage to get one VW inverter here. Its so small!
First question Tom91; why does it need isolated power supply?
Next question; Is there only one isolated supply or more required?
Third question; did you figure also the pinout on how to start the DCDC 12V converter? Any info on its connector pins? I see it is also ERNI 1.27mm 8P connector no. 284699.
That inverter looks different then the one i had.
No it does not, it is the supply to the optos and isolators. Check the schematics.
No isolated supply, just 5V as far as i know and then a supply in of 20V (atleast that worked for me.
It is painful to get working right i remember that much. It takes 12-20V then creates the isolated supply from that.
No idea on the DCDC.
I would say there is quite some figuring out left to do, I should have disassembled the whole inverter and powered it on to try and intercept the signals to the power stages to check my findings.
tom91 wrote: ↑Wed Apr 15, 2020 7:11 pm
I would say there is quite some figuring out left to do, I should have disassembled the whole inverter and powered it on to try and intercept the signals to the power stages to check my findings.
I think i will do the same and trace the outputs vs your results. Hopefully they used the same layout.
I have here 50Vdc battery and also one 10A power supply that can supply enough current to turn my small ACIM motor.
It seems that it would be better to abandon the side connector and make a new cover from the front in which to mount a new board. Space is tight...
Do you have some photos of that inverter board? Maybe i can catch some similarities.
So to get the isolation side to work you need to generate a 12-20V supply and then a pwm signal to start generating some voltage. there is a feedback output to indicate the isolated side has power.
Pictures of the brick i have and done the testing on, now its just down to getting it working really. Designed the PCB so I can use the Johannes brain to drive the IGBTS while the other signals and unkowns are on the screw terminals.
Dug out my setup, need to do more testing and documentation as now I do not know how to get the correct voltage on the isolated side and igbts switching.
Hope to get some done in the coming days.
Anyone has any info on VW inverter and charger wiring from Golf GTE? HV and LV connector pinout would be appreciated.
I have them sitting here not doing their thing and that frustrates me .
I think (on a Google image search based hunch) that it could be the same as the PIM in a fiat 500e.
I'm interested in a few things to do with that car in particular:
1) I'd love to add some sort of DC fast charge to it, so one option might be to tap into the connections for the battery at the inverter.
2) if the inverter in the fiat dies, or reports an issue, the fiat equivalent part number is $5k, whereas these inverters can be found much more cheaply than that. It'd be great to know if the only change required would be software
3) general interest, and a pipe dream of adding rear wheel drive to my 500e to make a 4wd beast.
Loving the resources posted so far. Thanks all who've submitted info.
I can't put a charge in to the pack as it's on the garage floor and I don't have a spare charger, but I do have a load of spare slave boards. My plan was to get an internal capture with the charging replaying to the external buses, and then replay the internal capture to a spare board with nearly full but out of balance 18650s.
VW Beetle 2003
Outlander front generator
Prius Gen 3 inverter (EVBMW logic board)
Outlander charger
3x Golf GTE batteries
Chademo Charging
Outlander water heater
I have a hunch based on how the messages are built and the fact there are 12 cells per slave.
Having reviewed the logs to figure out which IDs are most likely from the pack master.
These are the first two ids that contain the same values for another 7 sets of ids.
Since there are 8 module with 12 cells each this sort of makes sense.
Then you see the behaviour, 16x 0xFE followed bij 12x 0x00 and 4xFE. So could this be an initialisation state and then 12 values (relating to 12 cells?) get set to zero, and remaining 4 are still in the init state due to not being used.
I would say try and spoof this behaviour onto the bus and then set the values to something else then 0x00 after the initialisation.
Not following I can get a capture of just the master on the internal bus it get ID's it sends. So far I think 0x0BA 3rd byte is contactor related, when it's 0x29 the contactors are closed. The normal IDs use a strange CRC so modifying might be difficult, 2nd byte 2nd nibble seems to be a counter on these. The extended IDs don't seem to have a counter. https://github.com/commaai/opendbc/blob ... /common.cc is all I can find on that.
VW Beetle 2003
Outlander front generator
Prius Gen 3 inverter (EVBMW logic board)
Outlander charger
3x Golf GTE batteries
Chademo Charging
Outlander water heater
My hunch is that the message ids: 0x1A55540A to 0x1A55541F
contain a balancing command, as the table below. As a vw gte pack with a SimpBMS does not use these messages getting them onto the bus should be straight forward and can be altered for testing.
I could also just code this experimentally into the SimpBMS code, I will have a look around localy and see if I can obtain one GTE module for testing.
I see what you mean now I've looked in savvycan. I've got a few BMS slave boards if you want a couple posting. I believe rstevens81 is near to you and have 8 modules also.
Any guesses as to what value will kick it off? I can send some to a board with 18650s attached this week.
0xbb is likely from the contactor/shunt/isolation board, bytes 1&2 are thought to contain the current "It measures + or - and upto about + - 200 Amps . Value seems to be Amps × 160"
VW Beetle 2003
Outlander front generator
Prius Gen 3 inverter (EVBMW logic board)
Outlander charger
3x Golf GTE batteries
Chademo Charging
Outlander water heater
I have obtained a module and can probably also obtain a contactor box when I get to it. Any more captures of a full pack being used however is very useful.
So my hunch looks correct. Turns out that the message that contains the temperatures also contains feedback.
I am still working on trying to verify it actually works, my module however is at 3.69 cell volts so causing a voltage delta utilizing balancing bleeders is hard.
The findings are updated in my github, also put a crude function to force balancing on module 7 and 8 in code and this is only meant for testing. If anyone has a test setup and wants to try something please let me know and I can tweak the code to match.
I have had to run my testing for a prolonged period of time, 6+ hours due to the module under test being around 3.68V (thus the "fat" region in the SOC curve).
I can conclude no that the cells which are commanded to discharge have actually all droppen away from the rest of the cells. This is done with one module in a repeating pattern and another forcing a single cell to discharge.
This means I can commit to writing a section of software that determines which cells need balancing based on voltage, just like the Tesla Model S firmware.