Based on the changes in my prior message comparison, I was able to close contactors on the Kia EV6 and discharge at close to 800V. Since the charger emulated up to a 1000V the EV allowed direct access to the 800V battery without going thru the DC-DC/boost convertor.

Here's an image showing the ...

one update - I was able to collect traces from a real 350kW charger and have updated the OpenV2Gx code to reflect the params from there. The charger is giving much higher voltage and other params in the ChargeParameterDiscoveryRes - as below:
image.png

Hence I've updated the code to reflect these ...

Today I was able to test with 2 EVs in the US using CCS1 - Chevy Bolt and Kia Ev6 I was able to close contactors (EV expects voltage during pre-charge at the DC terminals - so I used a similar flyback that another member had used for the Polestar2 discharge.
The Bolt kept contactors closed for ...

Sure it works also without display. The display is just a listener of the serial line, so it does not matter whether it is present or not. If you connect a serial terminal, you nevertheless see the "display" messages. You could turn the message off by commenting the content of hardwareinterface ...

Hi @uhi22 - I am now trying to move further by taking your ccs32 codebase and bring it up on an ESP32 (WT32-ETH01) board similar to what you've detailed on github. I won't be using a display (is this possible to use without display and if so any specific config changes I would need in that case ...

I've used the QCA7005 as well as QCA47420 (TPlink hack) in EVSE mode with 2 cars Chevy Bolt and Kia EV6 and has worked with issues using pyPLC package from @uhi22

Not sure what the ARXXX is Atheros? if so, may be a pre-cursor to QCA as Atheros is now part of Qualcomm...

This is very interesting. I've a friend who has an old Nissan leaf and was worried in future as chargers move away from Chademo to NACS/CCS in US - this type of adapter come very handy. Would be interested to understand the conversion from CCS/greenPHY/IP to CAN/SWCAN based comm. I understand @Johu ...

So we are talking about EVSE mode, and the possibility to control the power supply. Well, this use case is at the moment not implemented at all. The existing hardwareInterface.py is handling only the PEV side.

My proposal would be:
1. Create a new module hardwareInterfaceEvse.py, to avoid ...

Hi @uhi22 had a quick question, on pyPLC side when using it in EVSE mode if I enable the serial port config in the pyPlc.ini


# Added by celeron55
# The serial port and baud rate used for communication. Used
# for serial devices like Dieter, OLED-Display and
# celeron55's measuring and switching ...

I was able to finally get a charge (fake) session going with the Chevy Bolt using the pyPLC EVSESim (did some changes to messages and attributes to match up real charger traces. Also the EV expects to see voltage and current at the terminals once the preCharge is complete. So I put a small DC ...

ListenMode in pyPLC. Does it work with TPlink modems - based on the release updates it seems it doesn't as the modem is dropping pkts not addressed to it? but works with Devolo modem? If so can you provide me with details on what h/w to use for this (I found this h/w on ebay - is this the one or ...

I updated the code in Openv2gx related to the encoding of CableCheckRes to match the real charger and the the Chevy Bolt was able to transition to the PreChargeReq/PreChargeRes state. I see the pyPLC calculating the EV Present Voltage based on the target sent in the Req and the logic seems to be ...

No, nothing to change on pyPLC side, the encode function creates the stream and nothing overwrites it. The code looks ok for me. Did you compile it before use? And did you compile it in the path where pyPLC searches it? (Sorry, stupid questions, but no better idea at the moment ;-) )


I found ...

Hi all - I tried the above suggestions - updated my params etc but no luck yet :-) So for now I am focusing on one car Chevy Bolt (where I am still stuck at the CableCheckResp and the PEV stops sending anything and then times out).
As I was going over the req/resp messages between I see in the ...

For the Tesla issue- make sure your modem is ready to start SLAC as soon as you switch to 5% duty cycle. Teslas (and a few others) will almost immediately try to start communicating after 5% starts. Stay in 100% duty for a few seconds beforehand if needed to verify the modem is ready before ...

I did a similar experiment on Tesla model Y, BYD-ATTO3, MG-EP they seem to measurement actual voltage at the charging port and send SessionStopReq, if the require pre-charge voltage of the chare port does not meet what have been requested for pre-charge. (In the experiment, I set the ...

I understood that the Kia/Hyundai 800V cars have to modes:

1. A "legacy mode", in which they are able to charge on 400V chargers, and use an internal step-up-converter to boost the 400 (or up to 500V) of a "old" charger to the internal battery charger. In this mode, I guess pulling energy out of ...

Hyundai/Kia HV vehicles run at 450V when dealing with “low voltage” chargers (typically 500v max). If charge parameter discovery response EVSE max voltage is below 450v, you’ll very likely fail out. Newer model S and X are ~450v as well, so your likely faulting out for the same reason for both ...

uhi22 wrote: ↑Fri Sep 22, 2023 4:10 pm BTW: Which plugin do you use in Wireshark to decode the EXI?

https://github.com/ChargePoint/wireshark-v2g

The values of the ChargeParameterResponse are not configurable at the moment. They are hardcoded here: https://github.com/uhi22/OpenV2Gx/blob/d0e22816ace99ff77b72bcb45273580ea65211a9/src/test/main_commandlineinterface.c#L1304
So you could try to change some of these values, re-compile the OpenV2Gx ...

Thank you for your detailed explanation and spending time to go over the messages. I think you're correct on the kia side, I noticed some of those fields in the req/resp and the resp had values which may need to be tweaked to something higher. Also I'll update my v2g code. How do I update the code ...

Hi @uhi22 - have some more updates from integrations with Chevy Bolt 2018, Kia EV6 2023, and Telsa Model S (with NACS/CCS adapter).
1. Chevy Bolt - transaction stuck at CableCheckReq/CableCheckResp and the EV doesn't send anything back and the transaction times out... and the EVSE goes back to ...

Interesting, could you record the Ethernet traffic using wireshark or tcpdump?


Sure, I'll do another run later today/tomorrow and get that data out. Have also asked some friends if I could use their Tesla Model S and Kia EV6 to try this same experiment. Will send out the logs/results in next ...

Hi I have finally got to a point where I was able to get the 5% PWM signal and rest of the wallbox related ckt to connect to the Bolt CCS1 charger - after that I manually started the pyPLC in EVSE mode and was able to see most of the messages between the Bolt <-> EVSE/pyPLC. The point where the ...

One more data point - I was able to use the pyPLC code with PEV/EVSE based on QCA7005 - from Aliexpress. next step is to make sure the CP has the correct voltage/duty cycle etc using open EVSE/instructible and then final showdown with an EV. So far the messages etc seem to be matching to the ISO ...