Integration Victron PV

Anfragen zum Erstellen von Modulen, Fragen zu Modulen
mafe68
Beiträge: 48
Registriert: Mi Jan 05, 2022 11:45 am

Re: Integration Victron PV

Beitrag von mafe68 »

ama hat geschrieben: Do Jan 06, 2022 10:09 am ... reicht das:

Code: Alles auswählen

2022-01-06 11:07:06: **** FATAL ********************************* (LV0) at 61 cleanup /var/www/html/openWB/regel.sh
2022-01-06 11:07:06: **** FATAL Regulation loop needs 25 seconds (LV0) at 60 cleanup /var/www/html/openWB/regel.sh
2022-01-06 11:07:06: **** FATAL ********************************* (LV0) at 59 cleanup /var/www/html/openWB/regel.sh
2022-01-06 11:07:03: chargestatlp1 0	chargestatlp2 0	chargestatlp3 0 (LV1) at 1284 loadvars loadvars.sh
2022-01-06 11:07:03: plugstatlp1 0	plugstatlp2 0	plugstatlp3 0 (LV1) at 1283 loadvars loadvars.sh
2022-01-06 11:07:03: lp1enabled 1	lp2enabled 1	lp3enabled 1 (LV1) at 1282 loadvars loadvars.sh
2022-01-06 11:07:03: EVU 1:V/-0A 2: V/0A 3: V/0A (LV1) at 1281 loadvars loadvars.sh
2022-01-06 11:07:03: lla3 0	llv3 0	llas13  llas23  soclp1 89 soclp2 (LV1) at 1280 loadvars loadvars.sh
2022-01-06 11:07:03: lla2 0	llv2 0	llas12  llas22  sofortll 10 hausverbrauch 256 wattbezug -13 uberschuss 13 (LV1) at 1279 loadvars loadvars.sh
2022-01-06 11:07:03: lla1 0	llv1 230.1	llas11  llas21  mindestuberschuss 1320 abschaltuberschuss 300 lademodus 3 (LV1) at 1278 loadvars loadvars.sh
2022-01-06 11:07:03: pv1watt -348 pv2watt  pvwatt -348 ladeleistung 0 llalt 0 nachtladen 0 nachtladen 0 minimalA 6 maximalA 11 (LV1) at 1277 loadvars loadvars.sh
2022-01-06 11:07:03: speicherleistung 0 speichersoc 0 (LV1) at 1272 loadvars loadvars.sh
2022-01-06 11:07:02: EVU RET: 0 (LV2) at 21 main modules/bezug_victrongx/main.sh
2022-01-06 11:07:02: PID: 1909: root: EVU Einspeisung: 145.29267432921463
2022-01-06 11:07:02: PID: 1909: root: EVU Bezug: 8321.252222222221
2022-01-06 11:07:02: PID: 1909: root: EVU Watt: -13
2022-01-06 11:07:02: PID: 1909: root: Victron Leistung[W]: -13
2022-01-06 11:07:02: PID: 1909: root: simcount Zwischenergebnisse atkuelle Berechnung: Import: 29956508 Export: 523053.62758517265 Power: -13
2022-01-06 11:07:02: PID: 1909: root: simcount Ergebnis: Bezug[Wh]: 8321.252222222221, Einspeisung[Wh]: 145.29267432921463
2022-01-06 11:07:02: PID: 1909: root: simcount aufsummierte Energie: Bezug[Ws]: 29956508, Einspeisung[Ws]: 523053.62758517265
2022-01-06 11:07:02: PID: 1909: root: simcount Gesamtenergie im Zeitintervall: -129.6275851726532
2022-01-06 11:07:02: PID: 1909: root: simcount Berechnungsgrundlage: vergangene Zeit [s]8.363070011138916, vorherige Leistung[W]: -18, aktuelle Leistung[W]: -13
2022-01-06 11:07:02: PID: 1909: root: simcount Zwischenergebnisse letzte Berechnung: Import: 29956508 Export: 522924 Power: -18
2022-01-06 11:07:02: PID: 1909: pymodbus.payload: [13363]
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE'
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Getting transaction 7
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Adding transaction 7
2022-01-06 11:07:02: PID: 1909: pymodbus.factory: Factory Response[ReadHoldingRegistersResponse: 3]
2022-01-06 11:07:02: PID: 1909: pymodbus.framer.socket_framer: Processing: 0x0 0x7 0x0 0x0 0x0 0x5 0x1e 0x3 0x2 0x34 0x33
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: RECV: 0x0 0x7 0x0 0x0 0x0 0x5 0x1e 0x3 0x2 0x34 0x33
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY'
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Changing transaction state from 'SENDING' to 'WAITING FOR REPLY'
2022-01-06 11:07:02: PID: 1909: pymodbus.client.sync: New Transaction state 'SENDING'
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: SEND: 0x0 0x7 0x0 0x0 0x0 0x6 0x1e 0x3 0xa 0x32 0x0 0x1
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Running transaction 7
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Current transaction state - TRANSACTION_COMPLETE
2022-01-06 11:07:02: PID: 1909: pymodbus.payload: [2306]
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE'
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Getting transaction 6
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Adding transaction 6
2022-01-06 11:07:02: PID: 1909: pymodbus.factory: Factory Response[ReadHoldingRegistersResponse: 3]
2022-01-06 11:07:02: PID: 1909: pymodbus.framer.socket_framer: Processing: 0x0 0x6 0x0 0x0 0x0 0x5 0x1e 0x3 0x2 0x9 0x2
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: RECV: 0x0 0x6 0x0 0x0 0x0 0x5 0x1e 0x3 0x2 0x9 0x2
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY'
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Changing transaction state from 'SENDING' to 'WAITING FOR REPLY'
2022-01-06 11:07:02: PID: 1909: pymodbus.client.sync: New Transaction state 'SENDING'
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: SEND: 0x0 0x6 0x0 0x0 0x0 0x6 0x1e 0x3 0xa 0x3a 0x0 0x1
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Running transaction 6
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Current transaction state - TRANSACTION_COMPLETE
2022-01-06 11:07:02: PID: 1909: pymodbus.payload: [2327]
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE'
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Getting transaction 5
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Adding transaction 5
2022-01-06 11:07:02: PID: 1909: pymodbus.factory: Factory Response[ReadHoldingRegistersResponse: 3]
2022-01-06 11:07:02: PID: 1909: pymodbus.framer.socket_framer: Processing: 0x0 0x5 0x0 0x0 0x0 0x5 0x1e 0x3 0x2 0x9 0x17
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: RECV: 0x0 0x5 0x0 0x0 0x0 0x5 0x1e 0x3 0x2 0x9 0x17
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY'
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Changing transaction state from 'SENDING' to 'WAITING FOR REPLY'
2022-01-06 11:07:02: PID: 1909: pymodbus.client.sync: New Transaction state 'SENDING'
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: SEND: 0x0 0x5 0x0 0x0 0x0 0x6 0x1e 0x3 0xa 0x38 0x0 0x1
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Running transaction 5
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Current transaction state - TRANSACTION_COMPLETE
2022-01-06 11:07:02: PID: 1909: pymodbus.payload: [8]
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE'
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Getting transaction 4
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Adding transaction 4
2022-01-06 11:07:02: PID: 1909: pymodbus.factory: Factory Response[ReadHoldingRegistersResponse: 3]
2022-01-06 11:07:02: PID: 1909: pymodbus.framer.socket_framer: Processing: 0x0 0x4 0x0 0x0 0x0 0x5 0x1e 0x3 0x2 0x0 0x8
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: RECV: 0x0 0x4 0x0 0x0 0x0 0x5 0x1e 0x3 0x2 0x0 0x8
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY'
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Changing transaction state from 'SENDING' to 'WAITING FOR REPLY'
2022-01-06 11:07:02: PID: 1909: pymodbus.client.sync: New Transaction state 'SENDING'
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: SEND: 0x0 0x4 0x0 0x0 0x0 0x6 0x1e 0x3 0xa 0x3d 0x0 0x1
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Running transaction 4
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Current transaction state - TRANSACTION_COMPLETE
2022-01-06 11:07:02: PID: 1909: pymodbus.payload: [7]
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE'
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Getting transaction 3
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Adding transaction 3
2022-01-06 11:07:02: PID: 1909: pymodbus.factory: Factory Response[ReadHoldingRegistersResponse: 3]
2022-01-06 11:07:02: PID: 1909: pymodbus.framer.socket_framer: Processing: 0x0 0x3 0x0 0x0 0x0 0x5 0x1e 0x3 0x2 0x0 0x7
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: RECV: 0x0 0x3 0x0 0x0 0x0 0x5 0x1e 0x3 0x2 0x0 0x7
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY'
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Changing transaction state from 'SENDING' to 'WAITING FOR REPLY'
2022-01-06 11:07:02: PID: 1909: pymodbus.client.sync: New Transaction state 'SENDING'
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: SEND: 0x0 0x3 0x0 0x0 0x0 0x6 0x1e 0x3 0xa 0x3b 0x0 0x1
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Running transaction 3
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Current transaction state - TRANSACTION_COMPLETE
2022-01-06 11:07:02: PID: 1909: pymodbus.payload: [65531]
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE'
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Getting transaction 2
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Adding transaction 2
2022-01-06 11:07:02: PID: 1909: pymodbus.factory: Factory Response[ReadHoldingRegistersResponse: 3]
2022-01-06 11:07:02: PID: 1909: pymodbus.framer.socket_framer: Processing: 0x0 0x2 0x0 0x0 0x0 0x5 0x1e 0x3 0x2 0xff 0xfb
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: RECV: 0x0 0x2 0x0 0x0 0x0 0x5 0x1e 0x3 0x2 0xff 0xfb
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY'
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Changing transaction state from 'SENDING' to 'WAITING FOR REPLY'
2022-01-06 11:07:02: PID: 1909: pymodbus.client.sync: New Transaction state 'SENDING'
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: SEND: 0x0 0x2 0x0 0x0 0x0 0x6 0x1e 0x3 0xa 0x39 0x0 0x1
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Running transaction 2
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Current transaction state - TRANSACTION_COMPLETE
2022-01-06 11:07:02: PID: 1909: pymodbus.payload: [65450, 56, 17]
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE'
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Getting transaction 1
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Adding transaction 1
2022-01-06 11:07:02: PID: 1909: pymodbus.factory: Factory Response[ReadHoldingRegistersResponse: 3]
2022-01-06 11:07:02: PID: 1909: pymodbus.framer.socket_framer: Processing: 0x0 0x1 0x0 0x0 0x0 0x9 0x1e 0x3 0x6 0xff 0xaa 0x0 0x38 0x0 0x11
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: RECV: 0x0 0x1 0x0 0x0 0x0 0x9 0x1e 0x3 0x6 0xff 0xaa 0x0 0x38 0x0 0x11
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY'
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Changing transaction state from 'SENDING' to 'WAITING FOR REPLY'
2022-01-06 11:07:02: PID: 1909: pymodbus.client.sync: New Transaction state 'SENDING'
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: SEND: 0x0 0x1 0x0 0x0 0x0 0x6 0x1e 0x3 0xa 0x28 0x0 0x3
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Running transaction 1
2022-01-06 11:07:02: PID: 1909: pymodbus.transaction: Current transaction state - IDLE
2022-01-06 11:07:02: PID: 1909: root: Komponente Victron Zähler auslesen.
2022-01-06 11:07:02: PID: 1909: root: Start device reading {'componentNone': <modules.victron.counter.VictronCounter object at 0x75a70590>}
2022-01-06 11:07:02: PID: 1909: root: Victron MPPT: None
2022-01-06 11:07:02: PID: 1909: root: Victron Modbus-ID: 30
2022-01-06 11:07:02: PID: 1909: root: Victron IP-Adresse: 192.168.178.46
2022-01-06 11:07:02: **** Regulation loop start **** (LV1) at 70 main /var/www/html/openWB/regel.sh
2022-01-06 11:06:57: **** FATAL ********************************* (LV0) at 61 cleanup /var/www/html/openWB/regel.sh
2022-01-06 11:06:57: **** FATAL Regulation loop needs 26 seconds (LV0) at 60 cleanup /var/www/html/openWB/regel.sh
2022-01-06 11:06:57: **** FATAL ********************************* (LV0) at 59 cleanup /var/www/html/openWB/regel.sh
2022-01-06 11:06:54: chargestatlp1 0	chargestatlp2 0	chargestatlp3 0 (LV1) at 1284 loadvars loadvars.sh
2022-01-06 11:06:54: plugstatlp1 0	plugstatlp2 0	plugstatlp3 0 (LV1) at 1283 loadvars loadvars.sh
2022-01-06 11:06:54: lp1enabled 1	lp2enabled 1	lp3enabled 1 (LV1) at 1282 loadvars loadvars.sh
2022-01-06 11:06:54: EVU 1:V/-0A 2: V/0A 3: V/0A (LV1) at 1281 loadvars loadvars.sh
2022-01-06 11:06:54: lla3 0	llv3 0	llas13  llas23  soclp1 89 soclp2 (LV1) at 1280 loadvars loadvars.sh
2022-01-06 11:06:54: lla2 0	llv2 0	llas12  llas22  sofortll 10 hausverbrauch 237 wattbezug -18 uberschuss 18 (LV1) at 1279 loadvars loadvars.sh
2022-01-06 11:06:54: lla1 0	llv1 230.2	llas11  llas21  mindestuberschuss 1320 abschaltuberschuss 300 lademodus 3 (LV1) at 1278 loadvars loadvars.sh
2022-01-06 11:06:54: pv1watt -347 pv2watt  pvwatt -347 ladeleistung 0 llalt 0 nachtladen 0 nachtladen 0 minimalA 6 maximalA 11 (LV1) at 1277 loadvars loadvars.sh
2022-01-06 11:06:54: speicherleistung 0 speichersoc 0 (LV1) at 1272 loadvars loadvars.sh
2022-01-06 11:06:53: EVU RET: 0 (LV2) at 21 main modules/bezug_victrongx/main.sh
2022-01-06 11:06:52: PID: 393: root: EVU Einspeisung: 145.25674474914868
2022-01-06 11:06:52: PID: 393: root: EVU Bezug: 8321.252222222221
2022-01-06 11:06:52: PID: 393: root: EVU Watt: -18
2022-01-06 11:06:52: PID: 393: root: Victron Leistung[W]: -18
2022-01-06 11:06:52: PID: 393: root: simcount Zwischenergebnisse atkuelle Berechnung: Import: 29956508 Export: 522924.2810969353 Power: -18
2022-01-06 11:06:52: PID: 393: root: simcount Ergebnis: Bezug[Wh]: 8321.252222222221, Einspeisung[Wh]: 145.25674474914868
2022-01-06 11:06:52: PID: 393: root: simcount aufsummierte Energie: Bezug[Ws]: 29956508, Einspeisung[Ws]: 522924.2810969353
2022-01-06 11:06:52: PID: 393: root: simcount Gesamtenergie im Zeitintervall: -141.28109693527222
2022-01-06 11:06:52: PID: 393: root: simcount Berechnungsgrundlage: vergangene Zeit [s]9.418739795684814, vorherige Leistung[W]: -12, aktuelle Leistung[W]: -18
2022-01-06 11:06:52: PID: 393: root: simcount Zwischenergebnisse letzte Berechnung: Import: 29956508 Export: 522783 Power: -12
2022-01-06 11:06:52: PID: 393: pymodbus.payload: [13363]
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE'
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Getting transaction 7
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Adding transaction 7
2022-01-06 11:06:52: PID: 393: pymodbus.factory: Factory Response[ReadHoldingRegistersResponse: 3]
2022-01-06 11:06:52: PID: 393: pymodbus.framer.socket_framer: Processing: 0x0 0x7 0x0 0x0 0x0 0x5 0x1e 0x3 0x2 0x34 0x33
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: RECV: 0x0 0x7 0x0 0x0 0x0 0x5 0x1e 0x3 0x2 0x34 0x33
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY'
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Changing transaction state from 'SENDING' to 'WAITING FOR REPLY'
2022-01-06 11:06:52: PID: 393: pymodbus.client.sync: New Transaction state 'SENDING'
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: SEND: 0x0 0x7 0x0 0x0 0x0 0x6 0x1e 0x3 0xa 0x32 0x0 0x1
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Running transaction 7
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Current transaction state - TRANSACTION_COMPLETE
2022-01-06 11:06:52: PID: 393: pymodbus.payload: [2311]
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE'
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Getting transaction 6
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Adding transaction 6
2022-01-06 11:06:52: PID: 393: pymodbus.factory: Factory Response[ReadHoldingRegistersResponse: 3]
2022-01-06 11:06:52: PID: 393: pymodbus.framer.socket_framer: Processing: 0x0 0x6 0x0 0x0 0x0 0x5 0x1e 0x3 0x2 0x9 0x7
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: RECV: 0x0 0x6 0x0 0x0 0x0 0x5 0x1e 0x3 0x2 0x9 0x7
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY'
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Changing transaction state from 'SENDING' to 'WAITING FOR REPLY'
2022-01-06 11:06:52: PID: 393: pymodbus.client.sync: New Transaction state 'SENDING'
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: SEND: 0x0 0x6 0x0 0x0 0x0 0x6 0x1e 0x3 0xa 0x3a 0x0 0x1
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Running transaction 6
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Current transaction state - TRANSACTION_COMPLETE
2022-01-06 11:06:52: PID: 393: pymodbus.payload: [2325]
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE'
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Getting transaction 5
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Adding transaction 5
2022-01-06 11:06:52: PID: 393: pymodbus.factory: Factory Response[ReadHoldingRegistersResponse: 3]
2022-01-06 11:06:52: PID: 393: pymodbus.framer.socket_framer: Processing: 0x0 0x5 0x0 0x0 0x0 0x5 0x1e 0x3 0x2 0x9 0x15
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: RECV: 0x0 0x5 0x0 0x0 0x0 0x5 0x1e 0x3 0x2 0x9 0x15
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY'
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Changing transaction state from 'SENDING' to 'WAITING FOR REPLY'
2022-01-06 11:06:52: PID: 393: pymodbus.client.sync: New Transaction state 'SENDING'
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: SEND: 0x0 0x5 0x0 0x0 0x0 0x6 0x1e 0x3 0xa 0x38 0x0 0x1
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Running transaction 5
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Current transaction state - TRANSACTION_COMPLETE
2022-01-06 11:06:52: PID: 393: pymodbus.payload: [8]
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE'
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Getting transaction 4
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Adding transaction 4
2022-01-06 11:06:52: PID: 393: pymodbus.factory: Factory Response[ReadHoldingRegistersResponse: 3]
2022-01-06 11:06:52: PID: 393: pymodbus.framer.socket_framer: Processing: 0x0 0x4 0x0 0x0 0x0 0x5 0x1e 0x3 0x2 0x0 0x8
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: RECV: 0x0 0x4 0x0 0x0 0x0 0x5 0x1e 0x3 0x2 0x0 0x8
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY'
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Changing transaction state from 'SENDING' to 'WAITING FOR REPLY'
2022-01-06 11:06:52: PID: 393: pymodbus.client.sync: New Transaction state 'SENDING'
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: SEND: 0x0 0x4 0x0 0x0 0x0 0x6 0x1e 0x3 0xa 0x3d 0x0 0x1
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Running transaction 4
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Current transaction state - TRANSACTION_COMPLETE
2022-01-06 11:06:52: PID: 393: pymodbus.payload: [7]
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE'
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Getting transaction 3
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Adding transaction 3
2022-01-06 11:06:52: PID: 393: pymodbus.factory: Factory Response[ReadHoldingRegistersResponse: 3]
2022-01-06 11:06:52: PID: 393: pymodbus.framer.socket_framer: Processing: 0x0 0x3 0x0 0x0 0x0 0x5 0x1e 0x3 0x2 0x0 0x7
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: RECV: 0x0 0x3 0x0 0x0 0x0 0x5 0x1e 0x3 0x2 0x0 0x7
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY'
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Changing transaction state from 'SENDING' to 'WAITING FOR REPLY'
2022-01-06 11:06:52: PID: 393: pymodbus.client.sync: New Transaction state 'SENDING'
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: SEND: 0x0 0x3 0x0 0x0 0x0 0x6 0x1e 0x3 0xa 0x3b 0x0 0x1
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Running transaction 3
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Current transaction state - TRANSACTION_COMPLETE
2022-01-06 11:06:52: PID: 393: pymodbus.payload: [65530]
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Changing transaction state from 'PROCESSING REPLY' to 'TRANSACTION_COMPLETE'
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Getting transaction 2
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Adding transaction 2
2022-01-06 11:06:52: PID: 393: pymodbus.factory: Factory Response[ReadHoldingRegistersResponse: 3]
2022-01-06 11:06:52: PID: 393: pymodbus.framer.socket_framer: Processing: 0x0 0x2 0x0 0x0 0x0 0x5 0x1e 0x3 0x2 0xff 0xfa
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: RECV: 0x0 0x2 0x0 0x0 0x0 0x5 0x1e 0x3 0x2 0xff 0xfa
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Changing transaction state from 'WAITING FOR REPLY' to 'PROCESSING REPLY'
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: Changing transaction state from 'SENDING' to 'WAITING FOR REPLY'
2022-01-06 11:06:52: PID: 393: pymodbus.client.sync: New Transaction state 'SENDING'
2022-01-06 11:06:52: PID: 393: pymodbus.transaction: SEND: 0x0 0x2 0x0 0x0 0x0 0x6 0x1e 0x3 0xa 0x39 0x0 0x1
Bitte die Log als Code hier anlegen sonst werden die Threads ewig lang! Einfach bei erstellen des Thread in der Zeile oben das Code Zeichen </> auswählen und dann da den Log einfügen.
Zuletzt geändert von mafe68 am Do Jan 06, 2022 10:30 am, insgesamt 1-mal geändert.
suggarman
Beiträge: 407
Registriert: Di Feb 25, 2020 7:03 am

Re: Integration Victron PV

Beitrag von suggarman »

@suggarman,

für deinen Speicher verwendest Du das BYD Modul oder das Victron Modul?
Alles über Victron.
Tesla Model Y, VW E-Up, 2x openWB, Solaredge-PV 15,5 kWp ONO, BYD LVS 32 kWh und 3-phasige Victron Multiplus-II 5000 mit Victron DC-PV 7,2 kWp NNW, Daikin Wärmepumpe.
mafe68
Beiträge: 48
Registriert: Mi Jan 05, 2022 11:45 am

Re: Integration Victron PV

Beitrag von mafe68 »

Bei einem Victron ESS System laufen die alle über Victron auch bei mir die Pylontech LiFeSo4 Akkus.
ama
Beiträge: 70
Registriert: So Okt 14, 2018 7:38 pm

Re: Integration Victron PV

Beitrag von ama »

@mafe68,

Bekommst du nach dem letzten fix werte für speicherleistung und soc?

Bei mir beide 0...

Danke ama
mafe68
Beiträge: 48
Registriert: Mi Jan 05, 2022 11:45 am

Re: Integration Victron PV

Beitrag von mafe68 »

ama hat geschrieben: Do Jan 06, 2022 10:46 am @mafe68,

Bekommst du nach dem letzten fix werte für speicherleistung und soc?

Bei mir beide 0...

Danke ama
Welche meist du von Hausspeicher oder vom EV Speicher? Hausspeicher werden mir die Daten angezeigt EV Speicher haben ich keinen da mein EV noch nicht geliefert wurdet. Aber für den EV Speicher werde ich mir was basteln das ich ihn simulieren kann.
Dateianhänge
Bildschirmfoto vom 2022-01-06 12-13-45.png
ama
Beiträge: 70
Registriert: So Okt 14, 2018 7:38 pm

Re: Integration Victron PV

Beitrag von ama »

Hallo Zusammen,

Ich habe meine Box jetzt restartet.

Seither bekomme ich Werte für den Speicher! Fehler im Status ist weg. Alles damit ok

Sorry und danke an alle füt die Unterstützung.

Ama
mafe68
Beiträge: 48
Registriert: Mi Jan 05, 2022 11:45 am

Re: Integration Victron PV

Beitrag von mafe68 »

Es ist immer gut wenn man nach dem update einen reboot macht den dann die Daten neu eingelesen werden oder man startet die einzelnen Module neu. Das wird man aber vermutlich auf der Konsole machen müssen.
aiole
Beiträge: 6861
Registriert: Mo Okt 08, 2018 4:51 pm

Re: Integration Victron PV

Beitrag von aiole »

OWB-Reboot geht auch für Normaluser über's GUI.
Einstellungen -> System -> Reboot
Oder meinst Du einen Victron-Regler?
ama
Beiträge: 70
Registriert: So Okt 14, 2018 7:38 pm

Re: Integration Victron PV

Beitrag von ama »

Hallo aiole,

hier ging es um den Restart der openWB. Den habe ich natürlich über den GUI gemacht.

Grüße, ama
aiole
Beiträge: 6861
Registriert: Mo Okt 08, 2018 4:51 pm

Re: Integration Victron PV

Beitrag von aiole »

ok - das war damals ein häufig nachgefragtes feature. Ab und zu sind doch mal shutdown oder reboot nötig.
Antworten