It is normal to see the car thinking it is being charged, as charging protocol is used to do the trick. For Tesla, the real show stopper is when the BMS_a076_SW_Dch_While_Charging alert is show up, the session will be stop.

During the time I experiment this with Tesla car, it seems random ...

This is new to me, never happended before. Based on my limited experiment with Tesla car when the PLC disconnected while power is still be drawn the car just abort the session, due to protocol timeout (defined for each message). This should be normal behaviuor of the system at SECC-EVCC interface ...

It would be a "man in the middle" that would read incoming data from either direction and repeat it out the other side. The concern with just passive sniffing is you don't know which way the data is coming from.

Tesla's documentation on NACS isn't thorough enough, and I'm too cheap to pay the ...

It is a model Y, with CCS2 charge port. I use my own SECC in my test, so the detail in SLAC timing and CP signal could be different here.

From what you described it look like PEV does not go into sounding state, possible cause could be EVSE pwm signal is out of spec, check the timing and voltage ...

Will share the pcap file when I get back to the lab, in around two weeks. It is an incomplete session, time out after 12 sec at pre-charge. The session is to find out if Tesla close DC contactor during simulated charging, but it does not.

Regarding your plan to build an adaptor, is it passive ...

Ok I have already tried the scenario with 2 amps in the response but no difference. And if I actually follow the requested values from the car both timeout pretty quick after about 20 seconds.


Hmm...it does not check during pre-charge, but instead does this during charging.
Can you post the ...

Don't know how you obtained the data for each EVSE, but if I understand it correctly the under current column you have "target" which is set by the EV and "delivered" which is reported by the EVSE. From this, it is look like all chargers that you collect data from seem to behave as it should. As I ...

Luckily, the Ioniq does not timeout such fast. Latest results: Without drawing energy from the port, it keeps the contactors on for 10 minutes. Then it turns off, but a new session can be established after disconnecting and re-connecting the plug.
Did a session where I connected two bulbs with ...

EVSEProcessing finished means move on to cable check. EVSE_NotReafy shouldn’t matter. I would not send another charge parameter discovery request on this combo.


Confirmed this should be the correct protocol behaviour, the snipped below is from Tesla session.

INFO EXIficientCodec ...

For Q3: Regarding the power-relay in the charger, I have no experiences. Basically it needs the possibility to avoid voltage on the plug, not sure whether this needs a relay. What it definitely needs is some circuits to fulfill the cable check and the precharge. I do not have details regarding ...

From what I have captured during model Y charging session, Tesla does not support ISO 15118, so no suppory for plug and charge at the moment.

I have let it run for some minutes, there was no timeout. Will run longer tests hopefully soon.
The "simulated precharging" means: THe charger sends EVSEPresentVoltage with the same value which the car wants as target voltage. This makes the car thinking, that precharging is successfully finished ...

Understand, one day someone will take this work to that level. We all know that conformance test help ensure product is both functional and safe to use.

On a side note, I see you focus only on DIN stack I hope you alreay provision for additional stack when DIN is done. In my prevous project adding ...

This is great, thanks! I added the log files here:
https://github.com/uhi22/pyPLC/blob/master/results/2023-03-02_SuperCharger_CableCheck_error.decoded.txt and
https://github.com/uhi22/pyPLC/blob/master/results/2023-03-02_SuperCharger_CableCheck_error.pcapng
One problem is my wrong handling of the ...

Some small progress on the Tesla SuperCharger: SLAC and TCP connections work perfect, also with the headless Raspberry3 as controller. In contrast to the other chargers, the SuperCharger use only 8 characters session ID instead of 16. This case is not yet considered in the OpenV2Gx. At the moment ...

The other approach would be to pretend to be a CCS charger and initiate a charge session to get it to close the contactors - this would be a cleaner approach and may also be applicable to other cars.
The only possible hurdles is that it may time out if no charge is received, or it may complain if ...

Forgot to mention, I see in your pcap file, the last message is PreChargeRes which contain EVSEStatusCode = EVSE_EmergencyShutdown. Not sure why your setup trigger this emergency shutdown.

Today was the first time, when I was able to get some power from an Compleo 50kW triple charger. Used a 230V light bulb as load, the TPlink as modem, an arduino for switching the CP state, and the laptop as controller. The auto-ranging multimeter was not able to deal with the 400V DC, it shows ...

Hi all, I ordered the qca7005 and playing with it's EVSE version. And I have got one question about SLAC. Is SLAC implement in qca7005 firmware or I need to implement it by my self in a higher level software ? Like it was done in https://github.com/cblach/nikola-v2gstack.git


SLAC is implemented ...

I'm developing commercial SECC and EVCC, so not all details can be revealed (there is an NDA on my contract ).

This project is based on RISE-V2G-1.2.6, running on Raspberry pi with QCA-7000 PLC and CAN interface board ( I ordered from China via AliExpress). At this stage I have a prototype of a ...

This subject is resolved now, thanks CCSknowitall for his advice. Test sessions pcap file is attached.

You are truly expert on this, kudos.

I have found the bug, will fix it and let you know the result.

BTW: It appeared that ABB also require multiple messages during Charge Parameter Discovery state, but it probably more forgiven to this type of error and let the session continue.

I forgot to mention, the last response message from IES also indicate that the insulation testing is ongoing and few second later it show error screen, this may be due to my side terminate the session, see attached picture.

Sequence error means the other side requested a message type out of order.

Some stations only require one back and forth in Charge Parameter Discovery before moving on to cable check. Others require multiple messages, and will signify this in charge parameter discovery response messages with EVSE ...

yes, the stack work perfectly fine, just need some tweak.

However during the test I have some issue with IES charger, I have crate another post on this issue, may be you could have a look and share your comment.