Seite 1 von 1

WB meint Ladung startet aber nix passiert

Verfasst: Mi Aug 16, 2023 7:19 pm
von athlon
Hallo zusammen,

ich hab die SW2 seit Beta 3 im Einsatz und bis letzte Woche funktionierte auch alles. Dann hab ich im Kabal Master ein Update gemacht...

Der Ladepunkt Log meint folgendes:
2023-08-16 21:11:31,733 - {modules.internal_chargepoint_handler.internal_chargepoint_handler:131} - {DEBUG:Internal Chargepoint} - Init internal chargepoint as series
2023-08-16 21:11:31,735 - {modules.common.component_context:24} - {DEBUG:Internal Chargepoint} - Update Komponente ['Interner Ladepunkt 0']
2023-08-16 21:11:31,740 - {modules.internal_chargepoint_handler.clients:121} - {DEBUG:Internal Chargepoint} - tty_devices[PosixPath('/dev/serial/by-path/platform-3f980000.usb-usb-0:1.3:1.0-port0')]
2023-08-16 21:11:31,742 - {modules.internal_chargepoint_handler.clients:123} - {DEBUG:Internal Chargepoint} - resolved_devices['/dev/ttyUSB0']
2023-08-16 21:11:31,743 - {modules.internal_chargepoint_handler.clients:134} - {ERROR:Internal Chargepoint} - LP0 Device: /dev/ttyUSB0
2023-08-16 21:11:31,920 - {modules.common.evse:57} - {DEBUG:Internal Chargepoint} - FW-Version: 18
2023-08-16 21:11:31,926 - {modules.internal_chargepoint_handler.clients:48} - {DEBUG:Internal Chargepoint} - <modules.common.modbus.ModbusSerialClient_ object at 0x72543e68>
2023-08-16 21:11:31,928 - {modules.internal_chargepoint_handler.clients:49} - {ERROR:Internal Chargepoint} - Modbus-ID der EVSE an LP0: 1
2023-08-16 21:11:32,955 - {modules.internal_chargepoint_handler.clients:66} - {DEBUG:Internal Chargepoint} - <modules.common.modbus.ModbusSerialClient_ object at 0x72543e68>
2023-08-16 21:11:32,957 - {modules.internal_chargepoint_handler.clients:67} - {DEBUG:Internal Chargepoint} - Zähler <class 'modules.common.mpm3pm.Mpm3pm'> mit Modbus-ID:5 antwortet nicht.
2023-08-16 21:11:33,015 - {modules.internal_chargepoint_handler.clients:63} - {ERROR:Internal Chargepoint} - Verbauter Zähler: <class 'modules.common.sdm.Sdm630'> mit Modbus-ID: 105
2023-08-16 21:11:33,184 - {modules.common.evse:57} - {DEBUG:Internal Chargepoint} - FW-Version: 18
2023-08-16 21:11:33,392 - {modules.common.evse:57} - {DEBUG:Internal Chargepoint} - FW-Version: 18
2023-08-16 21:11:33,584 - {modules.common.evse:65} - {DEBUG:Internal Chargepoint} - Angabe der Ströme in 0,01A-Schritten ist aktiviert.
2023-08-16 21:11:33,743 - {modules.common.evse:65} - {DEBUG:Internal Chargepoint} - Angabe der Ströme in 0,01A-Schritten ist aktiviert.
2023-08-16 21:11:33,746 - {modules.common.component_context:24} - {DEBUG:Internal Chargepoint} - Update Komponente ['Ladepunkt 0']
2023-08-16 21:11:33,761 - {modules.common.fault_state:52} - {ERROR:Internal Chargepoint} - Interner Ladepunkt 0: FaultState FaultStateLevel.ERROR, FaultStr <class 'RuntimeError'> No access to /dev/mem. Try running as root!, Traceback:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/internal_chargepoint_handler.py", line 147, in __init__
self.init_gpio()
File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/internal_chargepoint_handler.py", line 152, in init_gpio
GPIO.setup(37, GPIO.OUT)
RuntimeError: No access to /dev/mem. Try running as root!

2023-08-16 21:11:33,769 - {modules.common.component_context:24} - {DEBUG:Internal Chargepoint} - Update Komponente ['Ladepunkt 0']
2023-08-16 21:11:35,798 - {modules.internal_chargepoint_handler.internal_chargepoint_handler:131} - {DEBUG:Internal Chargepoint} - Init internal chargepoint as series
2023-08-16 21:11:35,799 - {modules.common.component_context:24} - {DEBUG:Internal Chargepoint} - Update Komponente ['Interner Ladepunkt 0']
2023-08-16 21:11:35,801 - {modules.internal_chargepoint_handler.clients:121} - {DEBUG:Internal Chargepoint} - tty_devices[PosixPath('/dev/serial/by-path/platform-3f980000.usb-usb-0:1.3:1.0-port0')]
2023-08-16 21:11:35,802 - {modules.internal_chargepoint_handler.clients:123} - {DEBUG:Internal Chargepoint} - resolved_devices['/dev/ttyUSB0']
2023-08-16 21:11:35,803 - {modules.internal_chargepoint_handler.clients:134} - {ERROR:Internal Chargepoint} - LP0 Device: /dev/ttyUSB0
2023-08-16 21:11:35,982 - {modules.common.evse:57} - {DEBUG:Internal Chargepoint} - FW-Version: 18
2023-08-16 21:11:35,985 - {modules.internal_chargepoint_handler.clients:48} - {DEBUG:Internal Chargepoint} - <modules.common.modbus.ModbusSerialClient_ object at 0x726b9610>
2023-08-16 21:11:35,987 - {modules.internal_chargepoint_handler.clients:49} - {ERROR:Internal Chargepoint} - Modbus-ID der EVSE an LP0: 1
2023-08-16 21:11:37,004 - {modules.internal_chargepoint_handler.clients:66} - {DEBUG:Internal Chargepoint} - <modules.common.modbus.ModbusSerialClient_ object at 0x726b9610>
2023-08-16 21:11:37,005 - {modules.internal_chargepoint_handler.clients:67} - {DEBUG:Internal Chargepoint} - Zähler <class 'modules.common.mpm3pm.Mpm3pm'> mit Modbus-ID:5 antwortet nicht.
2023-08-16 21:11:37,051 - {modules.internal_chargepoint_handler.clients:63} - {ERROR:Internal Chargepoint} - Verbauter Zähler: <class 'modules.common.sdm.Sdm630'> mit Modbus-ID: 105
2023-08-16 21:11:37,211 - {modules.common.evse:57} - {DEBUG:Internal Chargepoint} - FW-Version: 18
2023-08-16 21:11:37,419 - {modules.common.evse:57} - {DEBUG:Internal Chargepoint} - FW-Version: 18
2023-08-16 21:11:37,579 - {modules.common.evse:65} - {DEBUG:Internal Chargepoint} - Angabe der Ströme in 0,01A-Schritten ist aktiviert.
2023-08-16 21:11:37,739 - {modules.common.evse:65} - {DEBUG:Internal Chargepoint} - Angabe der Ströme in 0,01A-Schritten ist aktiviert.
2023-08-16 21:11:37,742 - {modules.common.component_context:24} - {DEBUG:Internal Chargepoint} - Update Komponente ['Ladepunkt 0']
2023-08-16 21:11:37,749 - {modules.common.fault_state:52} - {ERROR:Internal Chargepoint} - Interner Ladepunkt 0: FaultState FaultStateLevel.ERROR, FaultStr <class 'RuntimeError'> No access to /dev/mem. Try running as root!, Traceback:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/internal_chargepoint_handler.py", line 147, in __init__
self.init_gpio()
File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/internal_chargepoint_handler.py", line 152, in init_gpio
GPIO.setup(37, GPIO.OUT)
RuntimeError: No access to /dev/mem. Try running as root!

2023-08-16 21:11:37,804 - {modules.common.component_context:24} - {DEBUG:Internal Chargepoint} - Update Komponente ['Ladepunkt 0']
2023-08-16 21:11:37,806 - {modules.internal_chargepoint_handler.internal_chargepoint_handler:169} - {DEBUG:Internal Chargepoint} - ***Start***
2023-08-16 21:11:37,809 - {modules.internal_chargepoint_handler.internal_chargepoint_handler:171} - {DEBUG:Internal Chargepoint} - {'cp0': InternalChargepointHandlerData(cp_interruption_duration=0, parent_cp='5', phases_to_use=0, set_current=0, trigger_phase_switch=False), 'cp1': InternalChargepointHandlerData(cp_interruption_duration=0, parent_cp=None, phases_to_use=0, set_current=0, trigger_phase_switch=False), 'global_data': GlobalHandlerData(heartbeat=1692212911, parent_ip='localhost', configured=True), 'rfid_data': RfidData(last_tag='')}
2023-08-16 21:11:37,818 - {modules.common.fault_state:52} - {ERROR:Internal Chargepoint} - Ladepunkt 0: FaultState FaultStateLevel.ERROR, FaultStr <class 'KeyError'> 'debug_level', Traceback:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/internal_chargepoint_handler.py", line 181, in loop
_loop()
File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/internal_chargepoint_handler.py", line 172, in _loop
log.setLevel(SubData.system_data["system"].data["debug_level"])
KeyError: 'debug_level'
Die Box erkennt das Auto, erkennt genügend Überschuss und sagt Ladung gestartet aber der Schütz zieht nicht an. Hardwareseitig ist da kein Problem denn manuell löst er aus.
Wie bekomm ich ohne komplettes neuaufsetzen den Fehler beseitigt?

Re: WB meint Ladung startet aber nix passiert

Verfasst: Mi Aug 16, 2023 7:34 pm
von etnie83
viewtopic.php?p=91146#p91146

Wird das selbe Problem sein wie hier mittlerweile mehrere melden, mich inbegriffen
Meine Abhilfe war auf Entwicklungszweig 2.0.0 zurück und LP löschen und neu hinzufügen

Re: WB meint Ladung startet aber nix passiert

Verfasst: Do Aug 17, 2023 6:56 am
von athlon
Hab ich gestern Abend versucht und nun zusätzlich noch Heartbeat Fehler dazu bekommen. :x

EDIT: Ich hab jetzt Werkseinstellungen und Release 2023-08-03 drauf gemacht seitdem läufts wieder.