Fragen nach Update auf Software2 (Ladeleistung, Powerwall"Struktur")
Fragen nach Update auf Software2 (Ladeleistung, Powerwall"Struktur")
Hallo zusammen,
ich habe seit April 2023 meine OpenWB series2 Standard+ mit PV-Anlage und Tesla Powerwall erfolgreich (Sofort-Laden, PV-Laden etc.) am Laufen gehabt und nun auf "Software2" geupdated.
Ich bin jetzt auf der aktuellsten Version "Release" 2024-01-03 12:21:20
Der Update-Vorgang (SD-Karte von openWB bestellt), die initiale Konfiguration der Software2 und Datenübernahme haben gut funktioniert denke ich - heute beim Sofort-Laden habe ich allerdings festgestellt, dass die Ladeleistung immer runter geht bzw. ganz stoppt, wenn größere Verbraucher im Haus Strom ziehen. (Wasserkocher, Ofen)
Ich sehe auch Meldungen, dass die Ladeleistung heruntergeregelt werden muss weil der Maximalwert am "Tesla Zähler" erreicht wurde.
Mir ist nun nicht klar, ob meine "Struktur" überhaupt korrekt ist - ob ich z.B. noch einen "virtuellen" Zähler brauche? - oder ob z.B. die Maximalwerte des "Tesla Zähler" nicht die Werte des Hausanschlusses (DHH mit Wärmepume) sein sollten?
Ich poste einmal ein paar Screenshots in der Hoffnung dass da jemanden gleich ein grober Bock meiner Einstellungen oder "Struktur" / Lastmanagement auffällt. Ansonsten kann ich auch noch Daten aus dem "Main-Log" oder "Log des internen Ladepunktes" beisteuern (da sind einige Errors / Fault state zum "Internal Chargepoint" drin)
(gibt es eigentlich in der Standard2 noch das .../openWB/ramdisk/openWB.log?)
Ich danke euch - wenn wichtige Details meiner Anfrage fehlen zu "Geräten und Komponenten" liefere ich gerne nach.
Viele Grüße
Tobias
ich habe seit April 2023 meine OpenWB series2 Standard+ mit PV-Anlage und Tesla Powerwall erfolgreich (Sofort-Laden, PV-Laden etc.) am Laufen gehabt und nun auf "Software2" geupdated.
Ich bin jetzt auf der aktuellsten Version "Release" 2024-01-03 12:21:20
Der Update-Vorgang (SD-Karte von openWB bestellt), die initiale Konfiguration der Software2 und Datenübernahme haben gut funktioniert denke ich - heute beim Sofort-Laden habe ich allerdings festgestellt, dass die Ladeleistung immer runter geht bzw. ganz stoppt, wenn größere Verbraucher im Haus Strom ziehen. (Wasserkocher, Ofen)
Ich sehe auch Meldungen, dass die Ladeleistung heruntergeregelt werden muss weil der Maximalwert am "Tesla Zähler" erreicht wurde.
Mir ist nun nicht klar, ob meine "Struktur" überhaupt korrekt ist - ob ich z.B. noch einen "virtuellen" Zähler brauche? - oder ob z.B. die Maximalwerte des "Tesla Zähler" nicht die Werte des Hausanschlusses (DHH mit Wärmepume) sein sollten?
Ich poste einmal ein paar Screenshots in der Hoffnung dass da jemanden gleich ein grober Bock meiner Einstellungen oder "Struktur" / Lastmanagement auffällt. Ansonsten kann ich auch noch Daten aus dem "Main-Log" oder "Log des internen Ladepunktes" beisteuern (da sind einige Errors / Fault state zum "Internal Chargepoint" drin)
(gibt es eigentlich in der Standard2 noch das .../openWB/ramdisk/openWB.log?)
Ich danke euch - wenn wichtige Details meiner Anfrage fehlen zu "Geräten und Komponenten" liefere ich gerne nach.
Viele Grüße
Tobias
----------------------
openWB series2 standard+ (LAN)
Tesla Powerwall 2 & Gateway (LAN)
BMW i3S 2022
----------------------
openWB series2 standard+ (LAN)
Tesla Powerwall 2 & Gateway (LAN)
BMW i3S 2022
----------------------
-
- Beiträge: 3418
- Registriert: Sa Feb 20, 2021 9:55 am
- Has thanked: 4 times
- Been thanked: 59 times
Re: Fragen nach Update auf Software2 (Ladeleistung, Powerwall"Struktur")
Klick mal im Lastmanagement den Tesla-Zähler auf und kuck, was da eingetragen ist. Das ist die Stelle, in der der maximale Hausbezug eingetragenniat.
openWB-series2, openWB-Buchse, E3/DC S10pro+19.5kWh, 30kWp Ost-Süd, Model 3 und Ion
Re: Fragen nach Update auf Software2 (Ladeleistung, Powerwall"Struktur")
Danke Gero für die schnelle Rückmeldung.
Das sieht in der Tat nicht gut aus bei mir - ich habe da eher was konfiguriert wo ich dachte das muss ungefähr das sein, was die Wallbox maximal bekommt.
Aber was muss da normalerweise an Werten rein - es heisst ja nur "Tesla Zähler" ? (Ich weiß nicht mehr, was das initial drin stand )
Und die in Lastmangement angelegte "Struktur" sollte so stimmen?
Das sieht in der Tat nicht gut aus bei mir - ich habe da eher was konfiguriert wo ich dachte das muss ungefähr das sein, was die Wallbox maximal bekommt.
Aber was muss da normalerweise an Werten rein - es heisst ja nur "Tesla Zähler" ? (Ich weiß nicht mehr, was das initial drin stand )
Und die in Lastmangement angelegte "Struktur" sollte so stimmen?
----------------------
openWB series2 standard+ (LAN)
Tesla Powerwall 2 & Gateway (LAN)
BMW i3S 2022
----------------------
openWB series2 standard+ (LAN)
Tesla Powerwall 2 & Gateway (LAN)
BMW i3S 2022
----------------------
-
- Beiträge: 7747
- Registriert: Mo Okt 08, 2018 4:51 pm
- Has thanked: 18 times
- Been thanked: 31 times
Re: Fragen nach Update auf Software2 (Ladeleistung, Powerwall"Struktur")
Die Struktur sollte passen.
Schau mal in den Zählerschrank. EFH sind meist mit mind. 3x35A u.24kW abgesichert.
Die 16A sind sicher zu gering und könnten aus der Voreinstellung kommen. Da sowohl Leistung als auch Phasenströme überwacht werden, wird das Lastmanagement bei den Strömen drosseln.
In neueren Versionen (beta und master) wurde die Voreinstellung von 3x16A/11kW auf 3x35A/24kW umgestellt.
Es geht dort um den HAUSANSCHLUSS (= EVU-Punkt, rot) und nicht um den Ladepunkt (blau).
Schau mal in den Zählerschrank. EFH sind meist mit mind. 3x35A u.24kW abgesichert.
Die 16A sind sicher zu gering und könnten aus der Voreinstellung kommen. Da sowohl Leistung als auch Phasenströme überwacht werden, wird das Lastmanagement bei den Strömen drosseln.
In neueren Versionen (beta und master) wurde die Voreinstellung von 3x16A/11kW auf 3x35A/24kW umgestellt.
Es geht dort um den HAUSANSCHLUSS (= EVU-Punkt, rot) und nicht um den Ladepunkt (blau).
Re: Fragen nach Update auf Software2 (Ladeleistung, Powerwall"Struktur")
Danke aiole - habe 3x 35A Sicherungen gesehen und jetzt mal auf 24kW und 3x35A im "Tesla Zähler" gestellt.
Ich hänge das Auto dran und probiere es mal mit Sofortladen aus wenn ich aus der Arbeit zurück bin .
Ich hänge das Auto dran und probiere es mal mit Sofortladen aus wenn ich aus der Arbeit zurück bin .
----------------------
openWB series2 standard+ (LAN)
Tesla Powerwall 2 & Gateway (LAN)
BMW i3S 2022
----------------------
openWB series2 standard+ (LAN)
Tesla Powerwall 2 & Gateway (LAN)
BMW i3S 2022
----------------------
Re: Fragen nach Update auf Software2 (Ladeleistung, Powerwall"Struktur")
Danke für eure Hilfe -
hatte vorher das Auto angesteckt und es wurde sofort mit der eingestellten Leistung Sofort-geladen ohne zu Schwanken wenn im Haus Verbraucher dazu kamen.
Nur hinten raus ist die Ladung dann bei 99% immer abgebrochen und wieder gestartet und wieder abgebrochen und wieder gestartet bis ich dann nach 2-3 mal dieses Verhaltens auf "Stop" gegangen bin.
Das hatte ich bei der Version 1.9 nicht... da ging die Ladeleistung gegen Ende immer geschmeidig runter auf eine Phase und die minimale Ladeleistung bis die 100% erreicht waren.
Ich hänge mal ein Bild, Ladelog und SoC Log an (dass die BMW API beim SoC hin- und wieder einen 403 wirft kenne ich / hatte ich mit der Version 1.9 auch schon.)
SoC Log:
Ladelog:
Vielleicht weiß da noch jemand Rat - ist da noch ein Wurm drin?
Im Tagesdiagramm habe ich die Geräte auch irgendwie "doppelt" drin und die Bezeichnungen wie "ev.ev0.soc" kommen mir auch komisch vor?
Ich danke euch herzlich und wünsche einen guten Start ins Wochenende.
hatte vorher das Auto angesteckt und es wurde sofort mit der eingestellten Leistung Sofort-geladen ohne zu Schwanken wenn im Haus Verbraucher dazu kamen.
Nur hinten raus ist die Ladung dann bei 99% immer abgebrochen und wieder gestartet und wieder abgebrochen und wieder gestartet bis ich dann nach 2-3 mal dieses Verhaltens auf "Stop" gegangen bin.
Das hatte ich bei der Version 1.9 nicht... da ging die Ladeleistung gegen Ende immer geschmeidig runter auf eine Phase und die minimale Ladeleistung bis die 100% erreicht waren.
Ich hänge mal ein Bild, Ladelog und SoC Log an (dass die BMW API beim SoC hin- und wieder einen 403 wirft kenne ich / hatte ich mit der Version 1.9 auch schon.)
SoC Log:
Code: Alles auswählen
2024-02-02 16:44:16,004 - {modules.vehicles.bmw.api:73} - {ERROR:fetch soc_ev0} - bmw.getHTTP: Request failed, StatusCode: 403
2024-02-02 16:44:16,007 - {modules.vehicles.bmw.api:258} - {ERROR:fetch soc_ev0} - bmw.requestData: Data Request Error err=RuntimeError(), type(err)=<class 'RuntimeError'>
2024-02-02 16:44:16,008 - {modules.vehicles.bmw.api:278} - {ERROR:fetch soc_ev0} - bmw.fetch_soc: requestData Error, vehicle: 0 err=RuntimeError(), type(err)=<class 'RuntimeError'>
2024-02-02 16:44:16,009 - {modules.common.fault_state:55} - {ERROR:fetch soc_ev0} - BMW: FaultState FaultStateLevel.ERROR, FaultStr <class 'RuntimeError'> , Traceback:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/common/configurable_vehicle.py", line 66, in update
car_state = self._get_carstate_by_source(vehicle_update_data, source)
File "/var/www/html/openWB/packages/modules/common/configurable_vehicle.py", line 109, in _get_carstate_by_source
return self.__component_updater(vehicle_update_data)
File "/var/www/html/openWB/packages/modules/vehicles/bmw/soc.py", line 20, in updater
return api.fetch_soc(
File "/var/www/html/openWB/packages/modules/vehicles/bmw/api.py", line 273, in fetch_soc
data = requestData(token, vin)
File "/var/www/html/openWB/packages/modules/vehicles/bmw/api.py", line 255, in requestData
body = getHTTP(url, headers)
File "/var/www/html/openWB/packages/modules/vehicles/bmw/api.py", line 74, in getHTTP
raise RuntimeError
RuntimeError
2024-02-02 16:45:22,604 - {modules.vehicles.bmw.api:73} - {ERROR:fetch soc_ev0} - bmw.getHTTP: Request failed, StatusCode: 403
2024-02-02 16:45:22,607 - {modules.vehicles.bmw.api:258} - {ERROR:fetch soc_ev0} - bmw.requestData: Data Request Error err=RuntimeError(), type(err)=<class 'RuntimeError'>
2024-02-02 16:45:22,608 - {modules.vehicles.bmw.api:278} - {ERROR:fetch soc_ev0} - bmw.fetch_soc: requestData Error, vehicle: 0 err=RuntimeError(), type(err)=<class 'RuntimeError'>
2024-02-02 16:45:22,611 - {modules.common.fault_state:55} - {ERROR:fetch soc_ev0} - BMW: FaultState FaultStateLevel.ERROR, FaultStr <class 'RuntimeError'> , Traceback:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/common/configurable_vehicle.py", line 66, in update
car_state = self._get_carstate_by_source(vehicle_update_data, source)
File "/var/www/html/openWB/packages/modules/common/configurable_vehicle.py", line 109, in _get_carstate_by_source
return self.__component_updater(vehicle_update_data)
File "/var/www/html/openWB/packages/modules/vehicles/bmw/soc.py", line 20, in updater
return api.fetch_soc(
File "/var/www/html/openWB/packages/modules/vehicles/bmw/api.py", line 273, in fetch_soc
data = requestData(token, vin)
File "/var/www/html/openWB/packages/modules/vehicles/bmw/api.py", line 255, in requestData
body = getHTTP(url, headers)
File "/var/www/html/openWB/packages/modules/vehicles/bmw/api.py", line 74, in getHTTP
raise RuntimeError
RuntimeError
2024-02-02 16:50:21,651 - {modules.vehicles.bmw.api:73} - {ERROR:fetch soc_ev0} - bmw.getHTTP: Request failed, StatusCode: 403
2024-02-02 16:50:21,654 - {modules.vehicles.bmw.api:258} - {ERROR:fetch soc_ev0} - bmw.requestData: Data Request Error err=RuntimeError(), type(err)=<class 'RuntimeError'>
2024-02-02 16:50:21,655 - {modules.vehicles.bmw.api:278} - {ERROR:fetch soc_ev0} - bmw.fetch_soc: requestData Error, vehicle: 0 err=RuntimeError(), type(err)=<class 'RuntimeError'>
2024-02-02 16:50:21,694 - {modules.common.fault_state:55} - {ERROR:fetch soc_ev0} - BMW: FaultState FaultStateLevel.ERROR, FaultStr <class 'RuntimeError'> , Traceback:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/common/configurable_vehicle.py", line 66, in update
car_state = self._get_carstate_by_source(vehicle_update_data, source)
File "/var/www/html/openWB/packages/modules/common/configurable_vehicle.py", line 109, in _get_carstate_by_source
return self.__component_updater(vehicle_update_data)
File "/var/www/html/openWB/packages/modules/vehicles/bmw/soc.py", line 20, in updater
return api.fetch_soc(
File "/var/www/html/openWB/packages/modules/vehicles/bmw/api.py", line 273, in fetch_soc
data = requestData(token, vin)
File "/var/www/html/openWB/packages/modules/vehicles/bmw/api.py", line 255, in requestData
body = getHTTP(url, headers)
File "/var/www/html/openWB/packages/modules/vehicles/bmw/api.py", line 74, in getHTTP
raise RuntimeError
RuntimeError
2024-02-02 17:36:40,952 - {modules.vehicles.bmw.api:73} - {ERROR:fetch soc_ev0} - bmw.getHTTP: Request failed, StatusCode: 403
2024-02-02 17:36:40,954 - {modules.vehicles.bmw.api:258} - {ERROR:fetch soc_ev0} - bmw.requestData: Data Request Error err=RuntimeError(), type(err)=<class 'RuntimeError'>
2024-02-02 17:36:40,956 - {modules.vehicles.bmw.api:278} - {ERROR:fetch soc_ev0} - bmw.fetch_soc: requestData Error, vehicle: 0 err=RuntimeError(), type(err)=<class 'RuntimeError'>
2024-02-02 17:36:40,958 - {modules.common.fault_state:55} - {ERROR:fetch soc_ev0} - BMW: FaultState FaultStateLevel.ERROR, FaultStr <class 'RuntimeError'> , Traceback:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/common/configurable_vehicle.py", line 66, in update
car_state = self._get_carstate_by_source(vehicle_update_data, source)
File "/var/www/html/openWB/packages/modules/common/configurable_vehicle.py", line 109, in _get_carstate_by_source
return self.__component_updater(vehicle_update_data)
File "/var/www/html/openWB/packages/modules/vehicles/bmw/soc.py", line 20, in updater
return api.fetch_soc(
File "/var/www/html/openWB/packages/modules/vehicles/bmw/api.py", line 273, in fetch_soc
data = requestData(token, vin)
File "/var/www/html/openWB/packages/modules/vehicles/bmw/api.py", line 255, in requestData
body = getHTTP(url, headers)
File "/var/www/html/openWB/packages/modules/vehicles/bmw/api.py", line 74, in getHTTP
raise RuntimeError
RuntimeError
2024-02-02 17:41:39,853 - {modules.vehicles.bmw.api:73} - {ERROR:fetch soc_ev0} - bmw.getHTTP: Request failed, StatusCode: 403
2024-02-02 17:41:39,855 - {modules.vehicles.bmw.api:258} - {ERROR:fetch soc_ev0} - bmw.requestData: Data Request Error err=RuntimeError(), type(err)=<class 'RuntimeError'>
2024-02-02 17:41:39,857 - {modules.vehicles.bmw.api:278} - {ERROR:fetch soc_ev0} - bmw.fetch_soc: requestData Error, vehicle: 0 err=RuntimeError(), type(err)=<class 'RuntimeError'>
2024-02-02 17:41:39,858 - {modules.common.fault_state:55} - {ERROR:fetch soc_ev0} - BMW: FaultState FaultStateLevel.ERROR, FaultStr <class 'RuntimeError'> , Traceback:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/common/configurable_vehicle.py", line 66, in update
car_state = self._get_carstate_by_source(vehicle_update_data, source)
File "/var/www/html/openWB/packages/modules/common/configurable_vehicle.py", line 109, in _get_carstate_by_source
return self.__component_updater(vehicle_update_data)
File "/var/www/html/openWB/packages/modules/vehicles/bmw/soc.py", line 20, in updater
return api.fetch_soc(
File "/var/www/html/openWB/packages/modules/vehicles/bmw/api.py", line 273, in fetch_soc
data = requestData(token, vin)
File "/var/www/html/openWB/packages/modules/vehicles/bmw/api.py", line 255, in requestData
body = getHTTP(url, headers)
File "/var/www/html/openWB/packages/modules/vehicles/bmw/api.py", line 74, in getHTTP
raise RuntimeError
RuntimeError
2024-02-02 18:56:08,134 - {modules.vehicles.bmw.api:73} - {ERROR:fetch soc_ev0} - bmw.getHTTP: Request failed, StatusCode: 403
2024-02-02 18:56:08,137 - {modules.vehicles.bmw.api:258} - {ERROR:fetch soc_ev0} - bmw.requestData: Data Request Error err=RuntimeError(), type(err)=<class 'RuntimeError'>
2024-02-02 18:56:08,138 - {modules.vehicles.bmw.api:278} - {ERROR:fetch soc_ev0} - bmw.fetch_soc: requestData Error, vehicle: 0 err=RuntimeError(), type(err)=<class 'RuntimeError'>
2024-02-02 18:56:08,140 - {modules.common.fault_state:55} - {ERROR:fetch soc_ev0} - BMW: FaultState FaultStateLevel.ERROR, FaultStr <class 'RuntimeError'> , Traceback:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/common/configurable_vehicle.py", line 66, in update
car_state = self._get_carstate_by_source(vehicle_update_data, source)
File "/var/www/html/openWB/packages/modules/common/configurable_vehicle.py", line 109, in _get_carstate_by_source
return self.__component_updater(vehicle_update_data)
File "/var/www/html/openWB/packages/modules/vehicles/bmw/soc.py", line 20, in updater
return api.fetch_soc(
File "/var/www/html/openWB/packages/modules/vehicles/bmw/api.py", line 273, in fetch_soc
data = requestData(token, vin)
File "/var/www/html/openWB/packages/modules/vehicles/bmw/api.py", line 255, in requestData
body = getHTTP(url, headers)
File "/var/www/html/openWB/packages/modules/vehicles/bmw/api.py", line 74, in getHTTP
raise RuntimeError
RuntimeError
Code: Alles auswählen
2024-02-02 16:39:51,412 - {modules.common.evse:57} - {DEBUG:Internal Chargepoint} - FW-Version: 18
2024-02-02 16:39:51,462 - {modules.common.fault_state:55} - {ERROR:Internal Chargepoint} - Ladepunkt 0: FaultState FaultStateLevel.ERROR, FaultStr modules.internal_chargepoint_handler.chargepoint_module <class 'modules.common.fault_state.FaultState'> ("modules.common.modbus <class 'modules.common.fault_state.FaultState'> ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>), Traceback:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/common/modbus.py", line 90, in __read_registers
raise FaultState.error(__name__+" "+str(response))
modules.common.fault_state.FaultState: ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/chargepoint_module.py", line 80, in get_values
plug_state, charge_state, self.set_current_evse = self.__client.evse_client.get_plug_charge_state()
File "/var/www/html/openWB/packages/modules/common/evse.py", line 39, in get_plug_charge_state
set_current, _, state_number = self.client.read_holding_registers(
File "/var/www/html/openWB/packages/modules/common/modbus.py", line 123, in read_holding_registers
return self.__read_registers(
File "/var/www/html/openWB/packages/modules/common/modbus.py", line 105, in __read_registers
raise FaultState.error(__name__+" "+str(type(e))+" " +
modules.common.fault_state.FaultState: ("modules.common.modbus <class 'modules.common.fault_state.FaultState'> ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/internal_chargepoint_handler.py", line 242, in update
state = self.module.get_values(phase_switch_cp_active, rfid_data.last_tag)[0]
File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/chargepoint_module.py", line 125, in get_values
raise FaultState.error(__name__ + " " + str(type(e)) + " " + str(e)) from e
modules.common.fault_state.FaultState: ('modules.internal_chargepoint_handler.chargepoint_module <class \'modules.common.fault_state.FaultState\'> ("modules.common.modbus <class \'modules.common.fault_state.FaultState\'> (\'modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)\', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>)', <FaultStateLevel.ERROR: 2>)
2024-02-02 16:58:56,111 - {modules.common.evse:57} - {DEBUG:Internal Chargepoint} - FW-Version: 18
2024-02-02 16:58:56,160 - {modules.common.fault_state:55} - {ERROR:Internal Chargepoint} - Ladepunkt 0: FaultState FaultStateLevel.ERROR, FaultStr modules.internal_chargepoint_handler.chargepoint_module <class 'modules.common.fault_state.FaultState'> ("modules.common.modbus <class 'modules.common.fault_state.FaultState'> ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>), Traceback:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/common/modbus.py", line 90, in __read_registers
raise FaultState.error(__name__+" "+str(response))
modules.common.fault_state.FaultState: ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/chargepoint_module.py", line 80, in get_values
plug_state, charge_state, self.set_current_evse = self.__client.evse_client.get_plug_charge_state()
File "/var/www/html/openWB/packages/modules/common/evse.py", line 39, in get_plug_charge_state
set_current, _, state_number = self.client.read_holding_registers(
File "/var/www/html/openWB/packages/modules/common/modbus.py", line 123, in read_holding_registers
return self.__read_registers(
File "/var/www/html/openWB/packages/modules/common/modbus.py", line 105, in __read_registers
raise FaultState.error(__name__+" "+str(type(e))+" " +
modules.common.fault_state.FaultState: ("modules.common.modbus <class 'modules.common.fault_state.FaultState'> ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/internal_chargepoint_handler.py", line 242, in update
state = self.module.get_values(phase_switch_cp_active, rfid_data.last_tag)[0]
File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/chargepoint_module.py", line 125, in get_values
raise FaultState.error(__name__ + " " + str(type(e)) + " " + str(e)) from e
modules.common.fault_state.FaultState: ('modules.internal_chargepoint_handler.chargepoint_module <class \'modules.common.fault_state.FaultState\'> ("modules.common.modbus <class \'modules.common.fault_state.FaultState\'> (\'modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)\', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>)', <FaultStateLevel.ERROR: 2>)
2024-02-02 17:16:42,995 - {modules.common.evse:57} - {DEBUG:Internal Chargepoint} - FW-Version: 18
2024-02-02 17:16:43,044 - {modules.common.fault_state:55} - {ERROR:Internal Chargepoint} - Ladepunkt 0: FaultState FaultStateLevel.ERROR, FaultStr modules.internal_chargepoint_handler.chargepoint_module <class 'modules.common.fault_state.FaultState'> ("modules.common.modbus <class 'modules.common.fault_state.FaultState'> ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>), Traceback:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/common/modbus.py", line 90, in __read_registers
raise FaultState.error(__name__+" "+str(response))
modules.common.fault_state.FaultState: ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/chargepoint_module.py", line 80, in get_values
plug_state, charge_state, self.set_current_evse = self.__client.evse_client.get_plug_charge_state()
File "/var/www/html/openWB/packages/modules/common/evse.py", line 39, in get_plug_charge_state
set_current, _, state_number = self.client.read_holding_registers(
File "/var/www/html/openWB/packages/modules/common/modbus.py", line 123, in read_holding_registers
return self.__read_registers(
File "/var/www/html/openWB/packages/modules/common/modbus.py", line 105, in __read_registers
raise FaultState.error(__name__+" "+str(type(e))+" " +
modules.common.fault_state.FaultState: ("modules.common.modbus <class 'modules.common.fault_state.FaultState'> ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/internal_chargepoint_handler.py", line 242, in update
state = self.module.get_values(phase_switch_cp_active, rfid_data.last_tag)[0]
File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/chargepoint_module.py", line 125, in get_values
raise FaultState.error(__name__ + " " + str(type(e)) + " " + str(e)) from e
modules.common.fault_state.FaultState: ('modules.internal_chargepoint_handler.chargepoint_module <class \'modules.common.fault_state.FaultState\'> ("modules.common.modbus <class \'modules.common.fault_state.FaultState\'> (\'modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)\', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>)', <FaultStateLevel.ERROR: 2>)
2024-02-02 17:45:58,266 - {modules.common.evse:57} - {DEBUG:Internal Chargepoint} - FW-Version: 18
2024-02-02 17:45:58,315 - {modules.common.fault_state:55} - {ERROR:Internal Chargepoint} - Ladepunkt 0: FaultState FaultStateLevel.ERROR, FaultStr modules.internal_chargepoint_handler.chargepoint_module <class 'modules.common.fault_state.FaultState'> ("modules.common.modbus <class 'modules.common.fault_state.FaultState'> ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>), Traceback:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/common/modbus.py", line 90, in __read_registers
raise FaultState.error(__name__+" "+str(response))
modules.common.fault_state.FaultState: ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/chargepoint_module.py", line 80, in get_values
plug_state, charge_state, self.set_current_evse = self.__client.evse_client.get_plug_charge_state()
File "/var/www/html/openWB/packages/modules/common/evse.py", line 39, in get_plug_charge_state
set_current, _, state_number = self.client.read_holding_registers(
File "/var/www/html/openWB/packages/modules/common/modbus.py", line 123, in read_holding_registers
return self.__read_registers(
File "/var/www/html/openWB/packages/modules/common/modbus.py", line 105, in __read_registers
raise FaultState.error(__name__+" "+str(type(e))+" " +
modules.common.fault_state.FaultState: ("modules.common.modbus <class 'modules.common.fault_state.FaultState'> ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/internal_chargepoint_handler.py", line 242, in update
state = self.module.get_values(phase_switch_cp_active, rfid_data.last_tag)[0]
File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/chargepoint_module.py", line 125, in get_values
raise FaultState.error(__name__ + " " + str(type(e)) + " " + str(e)) from e
modules.common.fault_state.FaultState: ('modules.internal_chargepoint_handler.chargepoint_module <class \'modules.common.fault_state.FaultState\'> ("modules.common.modbus <class \'modules.common.fault_state.FaultState\'> (\'modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)\', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>)', <FaultStateLevel.ERROR: 2>)
2024-02-02 17:50:40,398 - {modules.common.evse:57} - {DEBUG:Internal Chargepoint} - FW-Version: 18
2024-02-02 17:50:40,447 - {modules.common.fault_state:55} - {ERROR:Internal Chargepoint} - Ladepunkt 0: FaultState FaultStateLevel.ERROR, FaultStr modules.internal_chargepoint_handler.chargepoint_module <class 'modules.common.fault_state.FaultState'> ("modules.common.modbus <class 'modules.common.fault_state.FaultState'> ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>), Traceback:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/common/modbus.py", line 90, in __read_registers
raise FaultState.error(__name__+" "+str(response))
modules.common.fault_state.FaultState: ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/chargepoint_module.py", line 80, in get_values
plug_state, charge_state, self.set_current_evse = self.__client.evse_client.get_plug_charge_state()
File "/var/www/html/openWB/packages/modules/common/evse.py", line 39, in get_plug_charge_state
set_current, _, state_number = self.client.read_holding_registers(
File "/var/www/html/openWB/packages/modules/common/modbus.py", line 123, in read_holding_registers
return self.__read_registers(
File "/var/www/html/openWB/packages/modules/common/modbus.py", line 105, in __read_registers
raise FaultState.error(__name__+" "+str(type(e))+" " +
modules.common.fault_state.FaultState: ("modules.common.modbus <class 'modules.common.fault_state.FaultState'> ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/internal_chargepoint_handler.py", line 242, in update
state = self.module.get_values(phase_switch_cp_active, rfid_data.last_tag)[0]
File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/chargepoint_module.py", line 125, in get_values
raise FaultState.error(__name__ + " " + str(type(e)) + " " + str(e)) from e
modules.common.fault_state.FaultState: ('modules.internal_chargepoint_handler.chargepoint_module <class \'modules.common.fault_state.FaultState\'> ("modules.common.modbus <class \'modules.common.fault_state.FaultState\'> (\'modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)\', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>)', <FaultStateLevel.ERROR: 2>)
2024-02-02 18:00:20,007 - {modules.common.evse:57} - {DEBUG:Internal Chargepoint} - FW-Version: 18
2024-02-02 18:00:20,055 - {modules.common.fault_state:55} - {ERROR:Internal Chargepoint} - Ladepunkt 0: FaultState FaultStateLevel.ERROR, FaultStr modules.internal_chargepoint_handler.chargepoint_module <class 'modules.common.fault_state.FaultState'> ("modules.common.modbus <class 'modules.common.fault_state.FaultState'> ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>), Traceback:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/common/modbus.py", line 90, in __read_registers
raise FaultState.error(__name__+" "+str(response))
modules.common.fault_state.FaultState: ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/chargepoint_module.py", line 80, in get_values
plug_state, charge_state, self.set_current_evse = self.__client.evse_client.get_plug_charge_state()
File "/var/www/html/openWB/packages/modules/common/evse.py", line 39, in get_plug_charge_state
set_current, _, state_number = self.client.read_holding_registers(
File "/var/www/html/openWB/packages/modules/common/modbus.py", line 123, in read_holding_registers
return self.__read_registers(
File "/var/www/html/openWB/packages/modules/common/modbus.py", line 105, in __read_registers
raise FaultState.error(__name__+" "+str(type(e))+" " +
modules.common.fault_state.FaultState: ("modules.common.modbus <class 'modules.common.fault_state.FaultState'> ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/internal_chargepoint_handler.py", line 242, in update
state = self.module.get_values(phase_switch_cp_active, rfid_data.last_tag)[0]
File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/chargepoint_module.py", line 125, in get_values
raise FaultState.error(__name__ + " " + str(type(e)) + " " + str(e)) from e
modules.common.fault_state.FaultState: ('modules.internal_chargepoint_handler.chargepoint_module <class \'modules.common.fault_state.FaultState\'> ("modules.common.modbus <class \'modules.common.fault_state.FaultState\'> (\'modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)\', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>)', <FaultStateLevel.ERROR: 2>)
2024-02-02 18:14:06,492 - {modules.common.evse:57} - {DEBUG:Internal Chargepoint} - FW-Version: 18
2024-02-02 18:14:06,541 - {modules.common.fault_state:55} - {ERROR:Internal Chargepoint} - Ladepunkt 0: FaultState FaultStateLevel.ERROR, FaultStr modules.internal_chargepoint_handler.chargepoint_module <class 'modules.common.fault_state.FaultState'> ("modules.common.modbus <class 'modules.common.fault_state.FaultState'> ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>), Traceback:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/common/modbus.py", line 90, in __read_registers
raise FaultState.error(__name__+" "+str(response))
modules.common.fault_state.FaultState: ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/chargepoint_module.py", line 80, in get_values
plug_state, charge_state, self.set_current_evse = self.__client.evse_client.get_plug_charge_state()
File "/var/www/html/openWB/packages/modules/common/evse.py", line 39, in get_plug_charge_state
set_current, _, state_number = self.client.read_holding_registers(
File "/var/www/html/openWB/packages/modules/common/modbus.py", line 123, in read_holding_registers
return self.__read_registers(
File "/var/www/html/openWB/packages/modules/common/modbus.py", line 105, in __read_registers
raise FaultState.error(__name__+" "+str(type(e))+" " +
modules.common.fault_state.FaultState: ("modules.common.modbus <class 'modules.common.fault_state.FaultState'> ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/internal_chargepoint_handler.py", line 242, in update
state = self.module.get_values(phase_switch_cp_active, rfid_data.last_tag)[0]
File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/chargepoint_module.py", line 125, in get_values
raise FaultState.error(__name__ + " " + str(type(e)) + " " + str(e)) from e
modules.common.fault_state.FaultState: ('modules.internal_chargepoint_handler.chargepoint_module <class \'modules.common.fault_state.FaultState\'> ("modules.common.modbus <class \'modules.common.fault_state.FaultState\'> (\'modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)\', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>)', <FaultStateLevel.ERROR: 2>)
2024-02-02 18:23:37,438 - {modules.common.evse:57} - {DEBUG:Internal Chargepoint} - FW-Version: 18
2024-02-02 18:23:37,487 - {modules.common.fault_state:55} - {ERROR:Internal Chargepoint} - Ladepunkt 0: FaultState FaultStateLevel.ERROR, FaultStr modules.internal_chargepoint_handler.chargepoint_module <class 'modules.common.fault_state.FaultState'> ("modules.common.modbus <class 'modules.common.fault_state.FaultState'> ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>), Traceback:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/common/modbus.py", line 90, in __read_registers
raise FaultState.error(__name__+" "+str(response))
modules.common.fault_state.FaultState: ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/chargepoint_module.py", line 80, in get_values
plug_state, charge_state, self.set_current_evse = self.__client.evse_client.get_plug_charge_state()
File "/var/www/html/openWB/packages/modules/common/evse.py", line 39, in get_plug_charge_state
set_current, _, state_number = self.client.read_holding_registers(
File "/var/www/html/openWB/packages/modules/common/modbus.py", line 123, in read_holding_registers
return self.__read_registers(
File "/var/www/html/openWB/packages/modules/common/modbus.py", line 105, in __read_registers
raise FaultState.error(__name__+" "+str(type(e))+" " +
modules.common.fault_state.FaultState: ("modules.common.modbus <class 'modules.common.fault_state.FaultState'> ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/internal_chargepoint_handler.py", line 242, in update
state = self.module.get_values(phase_switch_cp_active, rfid_data.last_tag)[0]
File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/chargepoint_module.py", line 125, in get_values
raise FaultState.error(__name__ + " " + str(type(e)) + " " + str(e)) from e
modules.common.fault_state.FaultState: ('modules.internal_chargepoint_handler.chargepoint_module <class \'modules.common.fault_state.FaultState\'> ("modules.common.modbus <class \'modules.common.fault_state.FaultState\'> (\'modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)\', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>)', <FaultStateLevel.ERROR: 2>)
2024-02-02 18:33:41,063 - {modules.common.evse:57} - {DEBUG:Internal Chargepoint} - FW-Version: 18
2024-02-02 18:33:41,138 - {modules.common.fault_state:55} - {ERROR:Internal Chargepoint} - Ladepunkt 0: FaultState FaultStateLevel.ERROR, FaultStr modules.internal_chargepoint_handler.chargepoint_module <class 'modules.common.fault_state.FaultState'> ("modules.common.modbus <class 'modules.common.fault_state.FaultState'> ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>), Traceback:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/common/modbus.py", line 90, in __read_registers
raise FaultState.error(__name__+" "+str(response))
modules.common.fault_state.FaultState: ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/chargepoint_module.py", line 80, in get_values
plug_state, charge_state, self.set_current_evse = self.__client.evse_client.get_plug_charge_state()
File "/var/www/html/openWB/packages/modules/common/evse.py", line 39, in get_plug_charge_state
set_current, _, state_number = self.client.read_holding_registers(
File "/var/www/html/openWB/packages/modules/common/modbus.py", line 123, in read_holding_registers
return self.__read_registers(
File "/var/www/html/openWB/packages/modules/common/modbus.py", line 105, in __read_registers
raise FaultState.error(__name__+" "+str(type(e))+" " +
modules.common.fault_state.FaultState: ("modules.common.modbus <class 'modules.common.fault_state.FaultState'> ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/internal_chargepoint_handler.py", line 242, in update
state = self.module.get_values(phase_switch_cp_active, rfid_data.last_tag)[0]
File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/chargepoint_module.py", line 125, in get_values
raise FaultState.error(__name__ + " " + str(type(e)) + " " + str(e)) from e
modules.common.fault_state.FaultState: ('modules.internal_chargepoint_handler.chargepoint_module <class \'modules.common.fault_state.FaultState\'> ("modules.common.modbus <class \'modules.common.fault_state.FaultState\'> (\'modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)\', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>)', <FaultStateLevel.ERROR: 2>)
2024-02-02 18:37:31,990 - {modules.common.evse:57} - {DEBUG:Internal Chargepoint} - FW-Version: 18
2024-02-02 18:37:32,038 - {modules.common.fault_state:55} - {ERROR:Internal Chargepoint} - Ladepunkt 0: FaultState FaultStateLevel.ERROR, FaultStr modules.internal_chargepoint_handler.chargepoint_module <class 'modules.common.fault_state.FaultState'> ("modules.common.modbus <class 'modules.common.fault_state.FaultState'> ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>), Traceback:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/common/modbus.py", line 90, in __read_registers
raise FaultState.error(__name__+" "+str(response))
modules.common.fault_state.FaultState: ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/chargepoint_module.py", line 80, in get_values
plug_state, charge_state, self.set_current_evse = self.__client.evse_client.get_plug_charge_state()
File "/var/www/html/openWB/packages/modules/common/evse.py", line 39, in get_plug_charge_state
set_current, _, state_number = self.client.read_holding_registers(
File "/var/www/html/openWB/packages/modules/common/modbus.py", line 123, in read_holding_registers
return self.__read_registers(
File "/var/www/html/openWB/packages/modules/common/modbus.py", line 105, in __read_registers
raise FaultState.error(__name__+" "+str(type(e))+" " +
modules.common.fault_state.FaultState: ("modules.common.modbus <class 'modules.common.fault_state.FaultState'> ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/internal_chargepoint_handler.py", line 242, in update
state = self.module.get_values(phase_switch_cp_active, rfid_data.last_tag)[0]
File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/chargepoint_module.py", line 125, in get_values
raise FaultState.error(__name__ + " " + str(type(e)) + " " + str(e)) from e
modules.common.fault_state.FaultState: ('modules.internal_chargepoint_handler.chargepoint_module <class \'modules.common.fault_state.FaultState\'> ("modules.common.modbus <class \'modules.common.fault_state.FaultState\'> (\'modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)\', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>)', <FaultStateLevel.ERROR: 2>)
Im Tagesdiagramm habe ich die Geräte auch irgendwie "doppelt" drin und die Bezeichnungen wie "ev.ev0.soc" kommen mir auch komisch vor?
Ich danke euch herzlich und wünsche einen guten Start ins Wochenende.
----------------------
openWB series2 standard+ (LAN)
Tesla Powerwall 2 & Gateway (LAN)
BMW i3S 2022
----------------------
openWB series2 standard+ (LAN)
Tesla Powerwall 2 & Gateway (LAN)
BMW i3S 2022
----------------------
-
- Beiträge: 3418
- Registriert: Sa Feb 20, 2021 9:55 am
- Has thanked: 4 times
- Been thanked: 59 times
Re: Fragen nach Update auf Software2 (Ladeleistung, Powerwall"Struktur")
IIm Fahzeugprofil gibt es einen Punkt „erlaubte Abweichung der Ladeleistung“ stell den mal hoch. Das ist das Einzige, was mir zu dem Abschalten einfällt. Gehen Ende sinkt die Ladeleistung ja immer mehr ab. Mein Tesla wird nicht abgeschaltet bei 99%
openWB-series2, openWB-Buchse, E3/DC S10pro+19.5kWh, 30kWp Ost-Süd, Model 3 und Ion
Re: Fragen nach Update auf Software2 (Ladeleistung, Powerwall"Struktur")
Das Auto lädt nicht mit der gewünschten Phasenzahl, daher versucht die openWB umzuschalten. In der aktuellen Beta sind die Umschaltversuche auf 3 begrenzt und man kann in den übergreifenden Ladeeeinstellungen die wiederholte Phasenumschaltung komplett abschalten.
Re: Fragen nach Update auf Software2 (Ladeleistung, Powerwall"Struktur")
Danke LenaK und Gero -
ich habe Parameter zur "Abweichung der Ladeleistung" angepasst und werde das Sofortladen probieren und berichten.
Das Auto oder am Auto hat sich zwischen Sofware 1.9 und Software2 der OpenWB nichts geändert - deswegen würde ich erwarten, dass die Ladeleistung gegen Ende genau wie mit Version 1.9 einfach geschmeidig runter geht bis auf 1 Phase mit 6A und die 100% erreicht sind.
Was die ganzen Errors in den SoC- und Ladelogs bedeuten kann hier niemand beantworten?
Oder das Thema mit den Bezeichnungen wie "ev.ev0.soc" im Diagramm?
ich habe Parameter zur "Abweichung der Ladeleistung" angepasst und werde das Sofortladen probieren und berichten.
Das Auto oder am Auto hat sich zwischen Sofware 1.9 und Software2 der OpenWB nichts geändert - deswegen würde ich erwarten, dass die Ladeleistung gegen Ende genau wie mit Version 1.9 einfach geschmeidig runter geht bis auf 1 Phase mit 6A und die 100% erreicht sind.
Was die ganzen Errors in den SoC- und Ladelogs bedeuten kann hier niemand beantworten?
Oder das Thema mit den Bezeichnungen wie "ev.ev0.soc" im Diagramm?
----------------------
openWB series2 standard+ (LAN)
Tesla Powerwall 2 & Gateway (LAN)
BMW i3S 2022
----------------------
openWB series2 standard+ (LAN)
Tesla Powerwall 2 & Gateway (LAN)
BMW i3S 2022
----------------------
-
- Beiträge: 722
- Registriert: Fr Feb 04, 2022 6:19 pm
- Has thanked: 8 times
- Been thanked: 16 times
Re: Fragen nach Update auf Software2 (Ladeleistung, Powerwall"Struktur")
Wäre es vielleicht ein anderer Ansatz zu fragen, warum überhaupt die Wallbox etwas ändern muss, wenn das Auto hier entscheidet, nicht mit der vollen Phasenzahl zu laden? Ich vermute, dass DaHuhn sich im Modus Sofort-Laden befand. Also Wallbox gibt gemäß den Einstellungen bspw. die volle Phasenzahl und Stromstärke frei und alles andere bleibt dann dem Auto überlassen - ohne, dass hier was geändert werden muss seitens der oWB, wenn das Auto was anderes macht…LenaK hat geschrieben: ↑Mo Feb 05, 2024 8:17 am Das Auto lädt nicht mit der gewünschten Phasenzahl, daher versucht die openWB umzuschalten. In der aktuellen Beta sind die Umschaltversuche auf 3 begrenzt und man kann in den übergreifenden Ladeeeinstellungen die wiederholte Phasenumschaltung komplett abschalten.
War das in der 1.9 vielleicht so? Dann würde sowas sicherlich vermieden werden können… oder ist das zu kurz gedacht?