I have a strange behavior with the Charging Station NS. It is brand new.
After initial setup, everything is fine, no car connected, also the Station reported, car not connected.
First time connecting the car:
connected car was not detected
than CP calibration done
car connection detected successfully
than charging started via web surface
no relay clicking was hearable, status jumps directly to charged
After that, the station is somehow stuck in the same states. Hitting “Stop” charging and the station goes back to status “Waiting for start”, Unplugging the car doesn’t change this. Rebooting the station doesn’t change this. Directly after reboot again “Waiting for start”. Everything without plugged car. (Car and cable are working fine on other charging stations.)
After factory reset, I can reproduce the same behavior.
I tried with other/higher current settings as well, no difference (since the contactor doesn’t click, it never comes to the point, where current is drawn)
I also tried with automatic start and manuell start
I hesitated openig the CS so far, because it is brand new and I don’t want to risk any warrenty. If the policy is, that it doesn’t affect warrenty, I can open and double check everything.
I did a bench test. Connected to a completely different AC wiring. Emulated the car connection with the required resistor/diode configuration directly connected to the CP line.
Found out, that everything worked fine with this configuration. No CP calibration required, car detected, charging can be started, contactor clicks.
After that, I connected the real car again, still measuring the CP line and found out, that nothing changes at CP line at all. Further investigtion showed, that the CP line in the socket did not had the required contact to the CP line in the plug.
Root cause was: plug was not plugged in sufficiently. But: the final millimeters required extensive force. I didn’t expect that. ( I already plugged in a lot of EVs.)
From my perspective, that the CP line doesn’t have a connection at all, could be easily detected during CP calibration. In this case a warning could be shown, instead of silently succeed.
Could this be considered as a feature request for the next FW version?