Bin gerade dabei, den eUp zu laden.
Die openWB standart 2+ mit Software 1.9 steuert den go-eCharger am Ladepunkt 2.
Habe 16A eingestellt. Die Spannung wird merkwürdigerweise ab- und eingeschaltet.
Den Enyaq hatte ich gestern ebenfalls geladen - da sah es normal aus.
Woran könnte es liegen?
Merkwürdiges Verhalten eUp laden: OpenWB steuert den go-eCharger
Re: Merkwürdiges Verhalten eUp laden: OpenWB steuert den go-eCharger
HIer der Ladelog dazu:
2023-12-01 21:48:12: PID: 6897: llog=2 (LV2) at 206 processChargepoint ./ladelog.sh
2023-12-01 21:48:12: PID: 6897: car is not charging (LV1) at 200 processChargepoint ./ladelog.sh
2023-12-01 21:48:12: PID: 6897: charged since plugged: 2025.700 - 2031.300 = 5.60 (LV1) at 125 processChargepoint ./ladelog.sh
2023-12-01 21:48:12: PID: 6897: car connected: plugstat=1 (LV1) at 102 processChargepoint ./ladelog.sh
2023-12-01 21:48:12: PID: 6897: rfid=0; power=10; meter=2031.300 (LV1) at 97 processChargepoint ./ladelog.sh
2023-12-01 21:48:12: PID: 6897: soc not configured or zero (LV2) at 87 processChargepoint ./ladelog.sh
2023-12-01 21:48:12: PID: 6897: # processing charge point 2 (LP2 go-eCharger) (LV1) at 81 processChargepoint ./ladelog.sh
2023-12-01 21:48:12: PID: 6897: car is not charging (LV1) at 200 processChargepoint ./ladelog.sh
2023-12-01 21:48:12: PID: 6897: unplug detected (LV2) at 141 processChargepoint ./ladelog.sh
2023-12-01 21:48:12: PID: 6897: car not connected: plugstat=0 (LV1) at 130 processChargepoint ./ladelog.sh
2023-12-01 21:48:12: PID: 6897: rfid=0; power=0; meter=4330.579 (LV1) at 97 processChargepoint ./ladelog.sh
2023-12-01 21:48:12: PID: 6897: soc not configured or zero (LV2) at 87 processChargepoint ./ladelog.sh
2023-12-01 21:48:12: PID: 6897: # processing charge point 1 (LP1: OpenWB Garage) (LV1) at 81 processChargepoint ./ladelog.sh
2023-12-01 21:48:12: PID: 6897: "loglademodus"=0 (LV2) at 27 main ./ladelog.sh
2023-12-01 21:48:12: PID: 6897: ### start (->/var/www/html/openWB/web/logging/data/ladelog/202312.csv) (LV1) at 10 main ./ladelog.sh
2023-12-01 21:48:07: PID: 5465: LP2, Lademodus Sofort. Ladung geändert auf 14 Ampere (LV0) at 360 sofortlademodus sofortlademodus.sh
2023-12-01 21:48:12: PID: 6897: llog=2 (LV2) at 206 processChargepoint ./ladelog.sh
2023-12-01 21:48:12: PID: 6897: car is not charging (LV1) at 200 processChargepoint ./ladelog.sh
2023-12-01 21:48:12: PID: 6897: charged since plugged: 2025.700 - 2031.300 = 5.60 (LV1) at 125 processChargepoint ./ladelog.sh
2023-12-01 21:48:12: PID: 6897: car connected: plugstat=1 (LV1) at 102 processChargepoint ./ladelog.sh
2023-12-01 21:48:12: PID: 6897: rfid=0; power=10; meter=2031.300 (LV1) at 97 processChargepoint ./ladelog.sh
2023-12-01 21:48:12: PID: 6897: soc not configured or zero (LV2) at 87 processChargepoint ./ladelog.sh
2023-12-01 21:48:12: PID: 6897: # processing charge point 2 (LP2 go-eCharger) (LV1) at 81 processChargepoint ./ladelog.sh
2023-12-01 21:48:12: PID: 6897: car is not charging (LV1) at 200 processChargepoint ./ladelog.sh
2023-12-01 21:48:12: PID: 6897: unplug detected (LV2) at 141 processChargepoint ./ladelog.sh
2023-12-01 21:48:12: PID: 6897: car not connected: plugstat=0 (LV1) at 130 processChargepoint ./ladelog.sh
2023-12-01 21:48:12: PID: 6897: rfid=0; power=0; meter=4330.579 (LV1) at 97 processChargepoint ./ladelog.sh
2023-12-01 21:48:12: PID: 6897: soc not configured or zero (LV2) at 87 processChargepoint ./ladelog.sh
2023-12-01 21:48:12: PID: 6897: # processing charge point 1 (LP1: OpenWB Garage) (LV1) at 81 processChargepoint ./ladelog.sh
2023-12-01 21:48:12: PID: 6897: "loglademodus"=0 (LV2) at 27 main ./ladelog.sh
2023-12-01 21:48:12: PID: 6897: ### start (->/var/www/html/openWB/web/logging/data/ladelog/202312.csv) (LV1) at 10 main ./ladelog.sh
2023-12-01 21:48:07: PID: 5465: LP2, Lademodus Sofort. Ladung geändert auf 14 Ampere (LV0) at 360 sofortlademodus sofortlademodus.sh
Re: Merkwürdiges Verhalten eUp laden: OpenWB steuert den go-eCharger
Welche Software Version hast du auf dem go-e, und welche Hardware Version? Für Hardware V2 ab Software v42 hat das Laden über die API nicht mehr gut funktioniert, da hilft dann ein downgrade auf v41 über den go-e Support.
Re: Merkwürdiges Verhalten eUp laden: OpenWB steuert den go-eCharger
Hardware: V3
Firmware: 055.7 bzw 055.8
Firmware: 055.7 bzw 055.8