openinverter forum

Seems you missed to update the OpenV2Gx. The cableCheck response does not show the intended
DC_EVSEStatus.EVSEStatusCode = dinDC_EVSEStatusCodeType_EVSE_IsolationMonitoringActive;
This was updated here: https://github.com/uhi22/OpenV2Gx/commi ... d86a159a47

Another small surprise: The ID.4 does not try secure communication (in contrast to the formerly tested Q4), the first SDP is just a non-secure request. Consequently the car offers just two quite old protocols, DIN from 2012 and ISO from 2013. Seems to be an older version of the ID.4, I understood that later offer secure communication for plug&charge.

Interesting. It's a 2022 model with Software 3.1
Will test the updated OpenV2G later

Yes yes

Now was in CurrentDemand for about a minute. Then it timed out because the inverter wasn't quick enough to start up. But the delays are changeable.
Why is TargetCurrent -0.2A?

Anyway, another milestone reached, thanks Uhi

Which target current? No idea where negative Target current should come from, hmm.
Congratulations for the ID.4 success, hopefully you can trick it to play, and it is not too nervous about negative charging currents.

A whole new experience today. Mr Q4 now has a BMW ix1 and of course we plugged it in. It went into CurrentDemand in no time

While we waited for the inverter to start up suddenly I lost my wifi connection. The GFCI had tripped

Not sure what's going wrong there, it would mean the IX has an exceptionally low isolation resistance?

Also the voltage is remarkably low, 310V @ 77% and it requests a max voltage of 337V.

Sounds like 80 cells (16*5).
The ground fault is strange. Does the inverter produce lot of high frequency AC swing on the DC lines? Then maybe the capacitance between battery and chassis leads to AC current. You could make some experiments with the Touran, adding some nano or microfarads between DC and PE and look when the GFCI trips.

Hi!
For first, thanks to everyone who contributed to the opensource ccs2 software, especially uhi22.
I was able to close contactors on Evolute I-Joy (aka Dongfeng Fengon E3 and Seres 3).
My configuration based on uhi22 documentation.
Ardunio nano for j1722.
Top board from TL-PA4010P rev. 4.1 for PCL communication.
I burned 3 pieces (two rev5.0 and one rev.4.1) of this boards due to improper input voltage, before it started working properly.
PyPLC successfully works on PC and on Radxa ROCK Pi S.
Also i tried run on orange pi zero, but it crashed. (I think it's because he's armhf, not aarch64)

Contactors remained closed for an hour without load. Battery discharged about 5% during this time by thermal control(battery heated to 25 from 5 celsius outside temp).

Now I'm waiting for the inverter to be delivered for try connect load.

If it is useful I maybe can provide more information, pcap dumps or some else.

Nice, my dad has a Seres 3