Neues Modul: 98_FREEZEMON Freezes monitoren und Verursacher identifizieren

FhemPiUser · 05 September 2022, 19:38:38

Hallo Stefan,

ok, danke.

Die bestehenden SH10rt_1 & SH10rt_2 devices würde ich ungern leeren und Interval 0 auf setzen, da dann meine Statistiken fehlen.

Ich würde zwei neue devices SH10rt_1_1 & SH10rt_2_1 zusätzlich anlegen mit Interval 0 und die bestehenden relay devices an diese weiterleiten lassen.

Ich beobachte dann die nächsten Stunden/Tage, ob die RAM-Nutzung steigt.

Modulversion ist Modbus 4.4.04 - 17.7.2021

Anbei schonmal das Log für SH10rt_1_1 und SH10rt_1 relay:

Code Auswählen


response: id 11, fc 4, i13009, len 2, values fff0ffff, tid 47
2022.09.05 19:44:30.934 5: SH10rt_1_relay_192.168.x.x: Send called from RelayResponse
2022.09.05 19:44:30.935 4: SH10rt_1_relay_192.168.x.x: Send 002f000000070b0404fff0ffff
2022.09.05 19:44:30.936 4: SH10rt_1_1: HandleResponse done, current frame / read buffer: 001700000007010404fff0ffff, id 1, fCode 4, tid 23,
request: id 1 fc 4 i13009, len 2, tid 23, master device SH10rt_1_1, for relay device SH10rt_1_relay_192.168.x.x (relayed), queued 0.11 secs ago, sent 0.11 secs ago,
response: id 11, fc 4, i13009, len 2, values fff0ffff, tid 47
2022.09.05 19:44:30.937 5: SH10rt_1_1: ResetExpect for HandleResponse from response to idle
2022.09.05 19:44:30.941 5: SH10rt_1_1: DropFrame called from ReadFn - drop 001700000007010404fff0ffff
2022.09.05 19:44:30.952 5: SH10rt_1_relay_192.168.x.x: readFn buffer: 0030000000060b0432de0001
2022.09.05 19:44:30.953 5: SH10rt_1_relay_192.168.x.x: ParseFrameStart called from ReadFn protocol TCP expecting id 11
2022.09.05 19:44:30.954 4: SH10rt_1_relay_192.168.x.x: ParseFrameStart (TCP, relay) extracted id 11, fCode 4, tid 48, dlen 6 and potential data 32de0001
2022.09.05 19:44:30.955 5: SH10rt_1_relay_192.168.x.x: HandleRequest called from ReadFn
2022.09.05 19:44:30.955 5: SH10rt_1_relay_192.168.x.x: ParseRequest called from HandleRequest
2022.09.05 19:44:30.956 4: SH10rt_1_relay_192.168.x.x: HandleRequest, current frame / read buffer: 0030000000060b0432de0001, id 11, fCode 4, tid 48,
request: id 11 fc 4 i13022, len 1, tid 48
2022.09.05 19:44:30.957 4: SH10rt_1_relay_192.168.x.x: RelayRequest called from HandleRequest
2022.09.05 19:44:30.957 5: SH10rt_1_relay: GetRelayIO found SH10rt_1_1 as Modbus relay forward io device for SH10rt_1_1 with id 1
2022.09.05 19:44:30.958 4: SH10rt_1_relay_192.168.x.x: RelayRequest via SH10rt_1_1, Proto TCP with id 1, current frame / read buffer: 0030000000060b0432de0001, id 11, fCode 4, tid 48,
request: id 11 fc 4 i13022, len 1, tid 48, for relay device SH10rt_1_relay_192.168.x.x
2022.09.05 19:44:30.959 5: SH10rt_1_1: QueueRequest called from RelayRequest with i13022, qlen 0 from master SH10rt_1_1 for relay SH10rt_1_relay_192.168.x.x through io device SH10rt_1_1
2022.09.05 19:44:30.960 5: SH10rt_1_1: ProcessRequestQueue called from QueueRequest as direct:SH10rt_1_1, qlen 1, force, request: request: id 1 fc 4 i13022, len 1, tid 199, master device SH10rt_1_1, for relay device SH10rt_1_relay_192.168.x.x (relayed), queued 0.00 secs ago
2022.09.05 19:44:30.961 5: SH10rt_1_1: checkDelays busDelayRead, last activity on bus was 0.040 secs ago, required delay is 0
2022.09.05 19:44:30.962 5: SH10rt_1_1: checkDelays sendDelay, last send to same device was 0.051 secs ago, required delay is 0.1
2022.09.05 19:44:30.962 5: SH10rt_1_1: checkDelays clientSwitchDelay is not relevant
2022.09.05 19:44:30.962 5: SH10rt_1_1: checkDelays commDelay, last communication with same device was 0.040 secs ago, required delay is 0.1
2022.09.05 19:44:30.963 4: SH10rt_1_1: checkDelays found commDelay not over, sleep for 0.060 forced
2022.09.05 19:44:31.023 4: SH10rt_1_1: checkDelays sleep done, go on with sending
2022.09.05 19:44:31.027 4: SH10rt_1_1: ProcessRequestQueue (V4.4.04 - 17.7.2021) qlen 1, sending 00c700000006010432de0001 via 192.168.3.160:502, read buffer empty,
request: id 1 fc 4 i13022, len 1, tid 199, master device SH10rt_1_1, for relay device SH10rt_1_relay_192.168.x.x (relayed), queued 0.07 secs ago
2022.09.05 19:44:31.027 5: SH10rt_1_1: Send called from ProcessRequestQueue
2022.09.05 19:44:31.028 5: DevIo_SimpleWrite SH10rt_1_1: 00c700000006010432de0001
2022.09.05 19:44:31.033 4: SH10rt_1_relay_192.168.x.x: HandleRequest Done, current frame / read buffer: 0030000000060b0432de0001, id 11, fCode 4, tid 48,
request: id 11 fc 4 i13022, len 1, tid 48, for relay device SH10rt_1_relay_192.168.x.x
2022.09.05 19:44:31.034 5: SH10rt_1_relay_192.168.x.x: DropFrame called from ReadFn - drop 0030000000060b0432de0001
2022.09.05 19:44:31.036 5: SH10rt_1_1: readFn buffer: 00c70000000501040203dc
2022.09.05 19:44:31.037 5: SH10rt_1_1: ParseFrameStart called from ReadFn protocol TCP expecting id 1
2022.09.05 19:44:31.038 4: SH10rt_1_1: ParseFrameStart (TCP, master) extracted id 1, fCode 4, tid 199, dlen 5 and potential data 0203dc
2022.09.05 19:44:31.038 5: SH10rt_1_1: HandleResponse called from ReadFn
2022.09.05 19:44:31.039 5: SH10rt_1_1: ParseResponse called from HandleResponse
2022.09.05 19:44:31.040 5: SH10rt_1_1: now parsing response data objects, master is SH10rt_1_1 relay is SH10rt_1_relay
2022.09.05 19:44:31.040 5: SH10rt_1_1: ParseDataString called from HandleResponse with data hex 03dc, type i, adr 13022
2022.09.05 19:44:31.041 5: SH10rt_1_1: SplitDataString called from ParseDataString with data hex 03dc, type i, adr 13022, valuesLen 1
2022.09.05 19:44:31.042 5: SH10rt_1_1: SplitDataString has no information about handling i13022
2022.09.05 19:44:31.042 5: SH10rt_1_1: CreateDataObjects called from ParseDataString with objList
2022.09.05 19:44:31.043 5: SH10rt_1_1: CreateDataObjects sortedList
2022.09.05 19:44:31.044 5: SH10rt_1_1: ParseDataString created 0 readings
2022.09.05 19:44:31.044 5: SH10rt_1_relay: ParseDataString called from HandleResponse with data hex 03dc, type i, adr 13022
2022.09.05 19:44:31.045 5: SH10rt_1_relay: SplitDataString called from ParseDataString with data hex 03dc, type i, adr 13022, valuesLen 1
2022.09.05 19:44:31.045 5: SH10rt_1_relay: SplitDataString has no information about handling i13022
2022.09.05 19:44:31.046 5: SH10rt_1_relay: CreateDataObjects called from ParseDataString with objList
2022.09.05 19:44:31.046 5: SH10rt_1_relay: CreateDataObjects sortedList
2022.09.05 19:44:31.047 5: SH10rt_1_relay: ParseDataString created 0 readings
2022.09.05 19:44:31.048 4: SH10rt_1_1: RelayResponse via SH10rt_1_relay_192.168.x.x, ioDev SH10rt_1_relay_192.168.x.x, current frame / read buffer: 00c70000000501040203dc, id 1, fCode 4, tid 199,
request: id 1 fc 4 i13022, len 1, tid 199, master device SH10rt_1_1, for relay device SH10rt_1_relay_192.168.x.x (relayed), queued 0.09 secs ago, sent 0.09 secs ago,
response: id 11, fc 4, i13022, len 1, values 03dc, tid 48
2022.09.05 19:44:31.049 5: SH10rt_1_relay_192.168.x.x: Send called from RelayResponse
2022.09.05 19:44:31.049 4: SH10rt_1_relay_192.168.x.x: Send 0030000000050b040203dc
2022.09.05 19:44:31.050 4: SH10rt_1_1: HandleResponse done, current frame / read buffer: 00c70000000501040203dc, id 1, fCode 4, tid 199,
request: id 1 fc 4 i13022, len 1, tid 199, master device SH10rt_1_1, for relay device SH10rt_1_relay_192.168.x.x (relayed), queued 0.09 secs ago, sent 0.09 secs ago,
response: id 11, fc 4, i13022, len 1, values 03dc, tid 48
2022.09.05 19:44:31.051 5: SH10rt_1_1: ResetExpect for HandleResponse from response to idle
2022.09.05 19:44:31.056 5: SH10rt_1_1: DropFrame called from ReadFn - drop 00c70000000501040203dc
2022.09.05 19:44:35.944 3: SH10rt_1_relay_192.168.x.x: read from TCP server connection got null -> closing
2022.09.05 19:44:35.944 3: SH10rt_1_relay_192.168.x.x: _UnDef is closing SH10rt_1_relay_192.168.x.x
2022.09.05 19:44:35.951 5: SH10rt_1_relay_192.168.x.x: Close called from UndefLDFn with noState and noDelete
2022.09.05 19:44:35.951 4: SH10rt_1_relay_192.168.x.x: Close TCP server listening connection and delete hash
2022.09.05 19:44:36.121 5: SH10rt_1_relay_192.168.x.x: Close is removing lastconn from parent device SH10rt_1_relay
2022.09.05 19:44:40.345 4: Connection accepted from SH10rt_1_relay_192.168.x.x
2022.09.05 19:44:40.345 4: SH10rt_1_relay: HandleServerConnection accepted new TCP connection as device SH10rt_1_relay_192.168.x.x
2022.09.05 19:44:40.444 5: SH10rt_1_relay_192.168.x.x: readFn buffer: 0031000000060b0413980002
2022.09.05 19:44:40.445 5: SH10rt_1_relay_192.168.x.x: ParseFrameStart called from ReadFn
2022.09.05 19:44:40.445 4: SH10rt_1_relay_192.168.x.x: ParseFrameStart (TCP, relay) extracted id 11, fCode 4, tid 49, dlen 6 and potential data 13980002
2022.09.05 19:44:40.445 5: SH10rt_1_relay_192.168.x.x: HandleRequest called from ReadFn
2022.09.05 19:44:40.446 5: SH10rt_1_relay_192.168.x.x: ParseRequest called from HandleRequest
2022.09.05 19:44:40.447 4: SH10rt_1_relay_192.168.x.x: HandleRequest, current frame / read buffer: 0031000000060b0413980002, id 11, fCode 4, tid 49,
request: id 11 fc 4 i5016, len 2, tid 49
2022.09.05 19:44:40.447 4: SH10rt_1_relay_192.168.x.x: RelayRequest called from HandleRequest
2022.09.05 19:44:40.448 5: SH10rt_1_relay: GetRelayIO found SH10rt_1_1 as Modbus relay forward io device for SH10rt_1_1 with id 1
2022.09.05 19:44:40.449 4: SH10rt_1_relay_192.168.x.x: RelayRequest via SH10rt_1_1, Proto TCP with id 1, current frame / read buffer: 0031000000060b0413980002, id 11, fCode 4, tid 49,
request: id 11 fc 4 i5016, len 2, tid 49, for relay device SH10rt_1_relay_192.168.x.x
2022.09.05 19:44:40.449 5: SH10rt_1_1: QueueRequest called from RelayRequest with i5016, qlen 0 from master SH10rt_1_1 for relay SH10rt_1_relay_192.168.x.x through io device SH10rt_1_1
2022.09.05 19:44:40.450 5: SH10rt_1_1: ProcessRequestQueue called from QueueRequest as direct:SH10rt_1_1, qlen 1, force, request: request: id 1 fc 4 i5016, len 2, tid 151, master device SH10rt_1_1, for relay device SH10rt_1_relay_192.168.x.x (relayed), queued 0.00 secs ago
2022.09.05 19:44:40.451 5: SH10rt_1_1: checkDelays commDelay, last communication with same device was 9.412 secs ago, required delay is 0.1
2022.09.05 19:44:40.452 5: SH10rt_1_1: checkDelays clientSwitchDelay is not relevant
2022.09.05 19:44:40.452 5: SH10rt_1_1: checkDelays sendDelay, last send to same device was 9.421 secs ago, required delay is 0.1
2022.09.05 19:44:40.452 5: SH10rt_1_1: checkDelays busDelayRead, last activity on bus was 9.412 secs ago, required delay is 0
2022.09.05 19:44:40.454 4: SH10rt_1_1: ProcessRequestQueue (V4.4.04 - 17.7.2021) qlen 1, sending 009700000006010413980002 via 192.168.3.160:502, read buffer empty,
request: id 1 fc 4 i5016, len 2, tid 151, master device SH10rt_1_1, for relay device SH10rt_1_relay_192.168.x.x (relayed), queued 0.00 secs ago
2022.09.05 19:44:40.455 5: SH10rt_1_1: Send called from ProcessRequestQueue
2022.09.05 19:44:40.456 5: DevIo_SimpleWrite SH10rt_1_1: 009700000006010413980002
2022.09.05 19:44:40.459 4: SH10rt_1_relay_192.168.x.x: HandleRequest Done, current frame / read buffer: 0031000000060b0413980002, id 11, fCode 4, tid 49,
request: id 11 fc 4 i5016, len 2, tid 49, for relay device SH10rt_1_relay_192.168.x.x
2022.09.05 19:44:40.459 5: SH10rt_1_relay_192.168.x.x: DropFrame called from ReadFn - drop 0031000000060b0413980002
2022.09.05 19:44:40.465 5: SH10rt_1_1: readFn buffer: 00970000000701040400000000
2022.09.05 19:44:40.465 5: SH10rt_1_1: ParseFrameStart called from ReadFn protocol TCP expecting id 1
2022.09.05 19:44:40.466 4: SH10rt_1_1: ParseFrameStart (TCP, master) extracted id 1, fCode 4, tid 151, dlen 7 and potential data 0400000000
2022.09.05 19:44:40.466 5: SH10rt_1_1: HandleResponse called from ReadFn
2022.09.05 19:44:40.466 5: SH10rt_1_1: ParseResponse called from HandleResponse
2022.09.05 19:44:40.467 5: SH10rt_1_1: now parsing response data objects, master is SH10rt_1_1 relay is SH10rt_1_relay
2022.09.05 19:44:40.467 5: SH10rt_1_1: ParseDataString called from HandleResponse with data hex 00000000, type i, adr 5016
2022.09.05 19:44:40.468 5: SH10rt_1_1: SplitDataString called from ParseDataString with data hex 00000000, type i, adr 5016, valuesLen 2
2022.09.05 19:44:40.468 5: SH10rt_1_1: SplitDataString has no information about handling i5016
2022.09.05 19:44:40.469 5: SH10rt_1_1: SplitDataString has no information about handling i5017
2022.09.05 19:44:40.469 5: SH10rt_1_1: CreateDataObjects called from ParseDataString with objList
2022.09.05 19:44:40.470 5: SH10rt_1_1: CreateDataObjects sortedList
2022.09.05 19:44:40.470 5: SH10rt_1_1: ParseDataString created 0 readings
2022.09.05 19:44:40.471 5: SH10rt_1_relay: ParseDataString called from HandleResponse with data hex 00000000, type i, adr 5016
2022.09.05 19:44:40.471 5: SH10rt_1_relay: SplitDataString called from ParseDataString with data hex 00000000, type i, adr 5016, valuesLen 2
2022.09.05 19:44:40.471 5: SH10rt_1_relay: SplitDataString has no information about handling i5016
2022.09.05 19:44:40.472 5: SH10rt_1_relay: SplitDataString has no information about handling i5017
2022.09.05 19:44:40.472 5: SH10rt_1_relay: CreateDataObjects called from ParseDataString with objList
2022.09.05 19:44:40.472 5: SH10rt_1_relay: CreateDataObjects sortedList
2022.09.05 19:44:40.473 5: SH10rt_1_relay: ParseDataString created 0 readings
2022.09.05 19:44:40.473 4: SH10rt_1_1: RelayResponse via SH10rt_1_relay_192.168.x.x, ioDev SH10rt_1_relay_192.168.x.x, current frame / read buffer: 00970000000701040400000000, id 1, fCode 4, tid 151,
request: id 1 fc 4 i5016, len 2, tid 151, master device SH10rt_1_1, for relay device SH10rt_1_relay_192.168.x.x (relayed), queued 0.02 secs ago, sent 0.02 secs ago,
response: id 11, fc 4, i5016, len 2, values 00000000, tid 49
2022.09.05 19:44:40.474 5: SH10rt_1_relay_192.168.x.x: Send called from RelayResponse
2022.09.05 19:44:40.474 4: SH10rt_1_relay_192.168.x.x: Send 0031000000070b040400000000
2022.09.05 19:44:40.475 4: SH10rt_1_1: HandleResponse done, current frame / read buffer: 00970000000701040400000000, id 1, fCode 4, tid 151,
request: id 1 fc 4 i5016, len 2, tid 151, master device SH10rt_1_1, for relay device SH10rt_1_relay_192.168.x.x (relayed), queued 0.03 secs ago, sent 0.02 secs ago,
response: id 11, fc 4, i5016, len 2, values 00000000, tid 49
2022.09.05 19:44:40.476 5: SH10rt_1_1: ResetExpect for HandleResponse from response to idle
2022.09.05 19:44:40.478 5: SH10rt_1_1: DropFrame called from ReadFn - drop 00970000000701040400000000
2022.09.05 19:44:40.571 5: SH10rt_1_relay_192.168.x.x: readFn buffer: 0032000000060b0432dd0001
2022.09.05 19:44:40.571 5: SH10rt_1_relay_192.168.x.x: ParseFrameStart called from ReadFn protocol TCP expecting id 11
2022.09.05 19:44:40.571 4: SH10rt_1_relay_192.168.x.x: ParseFrameStart (TCP, relay) extracted id 11, fCode 4, tid 50, dlen 6 and potential data 32dd0001
2022.09.05 19:44:40.572 5: SH10rt_1_relay_192.168.x.x: HandleRequest called from ReadFn
2022.09.05 19:44:40.572 5: SH10rt_1_relay_192.168.x.x: ParseRequest called from HandleRequest
2022.09.05 19:44:40.573 4: SH10rt_1_relay_192.168.x.x: HandleRequest, current frame / read buffer: 0032000000060b0432dd0001, id 11, fCode 4, tid 50,
request: id 11 fc 4 i13021, len 1, tid 50
2022.09.05 19:44:40.573 4: SH10rt_1_relay_192.168.x.x: RelayRequest called from HandleRequest
2022.09.05 19:44:40.573 5: SH10rt_1_relay: GetRelayIO found SH10rt_1_1 as Modbus relay forward io device for SH10rt_1_1 with id 1
2022.09.05 19:44:40.574 4: SH10rt_1_relay_192.168.x.x: RelayRequest via SH10rt_1_1, Proto TCP with id 1, current frame / read buffer: 0032000000060b0432dd0001, id 11, fCode 4, tid 50,
request: id 11 fc 4 i13021, len 1, tid 50, for relay device SH10rt_1_relay_192.168.x.x
2022.09.05 19:44:40.574 5: SH10rt_1_1: QueueRequest called from RelayRequest with i13021, qlen 0 from master SH10rt_1_1 for relay SH10rt_1_relay_192.168.x.x through io device SH10rt_1_1
2022.09.05 19:44:40.575 5: SH10rt_1_1: ProcessRequestQueue called from QueueRequest as direct:SH10rt_1_1, qlen 1, force, request: request: id 1 fc 4 i13021, len 1, tid 158, master device SH10rt_1_1, for relay device SH10rt_1_relay_192.168.x.x (relayed), queued 0.00 secs ago
2022.09.05 19:44:40.576 5: SH10rt_1_1: checkDelays busDelayRead, last activity on bus was 0.109 secs ago, required delay is 0
2022.09.05 19:44:40.576 5: SH10rt_1_1: checkDelays sendDelay, last send to same device was 0.118 secs ago, required delay is 0.1
2022.09.05 19:44:40.576 5: SH10rt_1_1: checkDelays clientSwitchDelay is not relevant
2022.09.05 19:44:40.576 5: SH10rt_1_1: checkDelays commDelay, last communication with same device was 0.109 secs ago, required delay is 0.1
2022.09.05 19:44:40.578 4: SH10rt_1_1: ProcessRequestQueue (V4.4.04 - 17.7.2021) qlen 1, sending 009e00000006010432dd0001 via 192.168.3.160:502, read buffer empty,
request: id 1 fc 4 i13021, len 1, tid 158, master device SH10rt_1_1, for relay device SH10rt_1_relay_192.168.x.x (relayed), queued 0.00 secs ago
2022.09.05 19:44:40.579 5: SH10rt_1_1: Send called from ProcessRequestQueue
2022.09.05 19:44:40.579 5: DevIo_SimpleWrite SH10rt_1_1: 009e00000006010432dd0001
2022.09.05 19:44:40.582 4: SH10rt_1_relay_192.168.x.x: HandleRequest Done, current frame / read buffer: 0032000000060b0432dd0001, id 11, fCode 4, tid 50,
request: id 11 fc 4 i13021, len 1, tid 50, for relay device SH10rt_1_relay_192.168.x.x
2022.09.05 19:44:40.583 5: SH10rt_1_relay_192.168.x.x: DropFrame called from ReadFn - drop 0032000000060b0432dd0001
2022.09.05 19:44:40.584 5: SH10rt_1_1: readFn buffer: 009e0000000501040201d8
2022.09.05 19:44:40.585 5: SH10rt_1_1: ParseFrameStart called from ReadFn protocol TCP expecting id 1
2022.09.05 19:44:40.585 4: SH10rt_1_1: ParseFrameStart (TCP, master) extracted id 1, fCode 4, tid 158, dlen 5 and potential data 0201d8
2022.09.05 19:44:40.586 5: SH10rt_1_1: HandleResponse called from ReadFn
2022.09.05 19:44:40.586 5: SH10rt_1_1: ParseResponse called from HandleResponse
2022.09.05 19:44:40.586 5: SH10rt_1_1: now parsing response data objects, master is SH10rt_1_1 relay is SH10rt_1_relay
2022.09.05 19:44:40.587 5: SH10rt_1_1: ParseDataString called from HandleResponse with data hex 01d8, type i, adr 13021
2022.09.05 19:44:40.587 5: SH10rt_1_1: SplitDataString called from ParseDataString with data hex 01d8, type i, adr 13021, valuesLen 1
2022.09.05 19:44:40.588 5: SH10rt_1_1: SplitDataString has no information about handling i13021
2022.09.05 19:44:40.588 5: SH10rt_1_1: CreateDataObjects called from ParseDataString with objList
2022.09.05 19:44:40.588 5: SH10rt_1_1: CreateDataObjects sortedList
2022.09.05 19:44:40.589 5: SH10rt_1_1: ParseDataString created 0 readings
2022.09.05 19:44:40.589 5: SH10rt_1_relay: ParseDataString called from HandleResponse with data hex 01d8, type i, adr 13021
2022.09.05 19:44:40.589 5: SH10rt_1_relay: SplitDataString called from ParseDataString with data hex 01d8, type i, adr 13021, valuesLen 1
2022.09.05 19:44:40.590 5: SH10rt_1_relay: SplitDataString has no information about handling i13021
2022.09.05 19:44:40.590 5: SH10rt_1_relay: CreateDataObjects called from ParseDataString with objList
2022.09.05 19:44:40.590 5: SH10rt_1_relay: CreateDataObjects sortedList
2022.09.05 19:44:40.591 5: SH10rt_1_relay: ParseDataString created 0 readings
2022.09.05 19:44:40.591 4: SH10rt_1_1: RelayResponse via SH10rt_1_relay_192.168.x.x, ioDev SH10rt_1_relay_192.168.x.x, current frame / read buffer: 009e0000000501040201d8, id 1, fCode 4, tid 158,
request: id 1 fc 4 i13021, len 1, tid 158, master device SH10rt_1_1, for relay device SH10rt_1_relay_192.168.x.x (relayed), queued 0.02 secs ago, sent 0.02 secs ago,
response: id 11, fc 4, i13021, len 1, values 01d8, tid 50
2022.09.05 19:44:40.592 5: SH10rt_1_relay_192.168.x.x: Send called from RelayResponse
2022.09.05 19:44:40.592 4: SH10rt_1_relay_192.168.x.x: Send 0032000000050b040201d8
2022.09.05 19:44:40.593 4: SH10rt_1_1: HandleResponse done, current frame / read buffer: 009e0000000501040201d8, id 1, fCode 4, tid 158,
request: id 1 fc 4 i13021, len 1, tid 158, master device SH10rt_1_1, for relay device SH10rt_1_relay_192.168.x.x (relayed), queued 0.02 secs ago, sent 0.02 secs ago,
response: id 11, fc 4, i13021, len 1, values 01d8, tid 50
2022.09.05 19:44:40.593 5: SH10rt_1_1: ResetExpect for HandleResponse from response to idle
2022.09.05 19:44:40.596 5: SH10rt_1_1: DropFrame called from ReadFn - drop 009e0000000501040201d8
2022.09.05 19:44:40.599 5: SH10rt_1_relay_192.168.x.x: readFn buffer: 0033000000060b0432c80001
2022.09.05 19:44:40.599 5: SH10rt_1_relay_192.168.x.x: ParseFrameStart called from ReadFn protocol TCP expecting id 11
2022.09.05 19:44:40.599 4: SH10rt_1_relay_192.168.x.x: ParseFrameStart (TCP, relay) extracted id 11, fCode 4, tid 51, dlen 6 and potential data 32c80001
2022.09.05 19:44:40.600 5: SH10rt_1_relay_192.168.x.x: HandleRequest called from ReadFn
2022.09.05 19:44:40.600 5: SH10rt_1_relay_192.168.x.x: ParseRequest called from HandleRequest
2022.09.05 19:44:40.601 4: SH10rt_1_relay_192.168.x.x: HandleRequest, current frame / read buffer: 0033000000060b0432c80001, id 11, fCode 4, tid 51,
request: id 11 fc 4 i13000, len 1, tid 51
2022.09.05 19:44:40.601 4: SH10rt_1_relay_192.168.x.x: RelayRequest called from HandleRequest
2022.09.05 19:44:40.602 5: SH10rt_1_relay: GetRelayIO found SH10rt_1_1 as Modbus relay forward io device for SH10rt_1_1 with id 1
2022.09.05 19:44:40.602 4: SH10rt_1_relay_192.168.x.x: RelayRequest via SH10rt_1_1, Proto TCP with id 1, current frame / read buffer: 0033000000060b0432c80001, id 11, fCode 4, tid 51,
request: id 11 fc 4 i13000, len 1, tid 51, for relay device SH10rt_1_relay_192.168.x.x
2022.09.05 19:44:40.603 5: SH10rt_1_1: QueueRequest called from RelayRequest with i13000, qlen 0 from master SH10rt_1_1 for relay SH10rt_1_relay_192.168.x.x through io device SH10rt_1_1
2022.09.05 19:44:40.603 5: SH10rt_1_1: ProcessRequestQueue called from QueueRequest as direct:SH10rt_1_1, qlen 1, force, request: request: id 1 fc 4 i13000, len 1, tid 44, master device SH10rt_1_1, for relay device SH10rt_1_relay_192.168.x.x (relayed), queued 0.00 secs ago
2022.09.05 19:44:40.604 5: SH10rt_1_1: checkDelays clientSwitchDelay is not relevant
2022.09.05 19:44:40.604 5: SH10rt_1_1: checkDelays sendDelay, last send to same device was 0.023 secs ago, required delay is 0.1
2022.09.05 19:44:40.604 5: SH10rt_1_1: checkDelays busDelayRead, last activity on bus was 0.018 secs ago, required delay is 0
2022.09.05 19:44:40.605 5: SH10rt_1_1: checkDelays commDelay, last communication with same device was 0.018 secs ago, required delay is 0.1
2022.09.05 19:44:40.605 4: SH10rt_1_1: checkDelays found commDelay not over, sleep for 0.082 forced
2022.09.05 19:44:40.687 4: SH10rt_1_1: checkDelays sleep done, go on with sending
2022.09.05 19:44:40.690 4: SH10rt_1_1: ProcessRequestQueue (V4.4.04 - 17.7.2021) qlen 1, sending 002c00000006010432c80001 via 192.168.3.160:502, read buffer empty,
request: id 1 fc 4 i13000, len 1, tid 44, master device SH10rt_1_1, for relay device SH10rt_1_relay_192.168.x.x (relayed), queued 0.09 secs ago
2022.09.05 19:44:40.690 5: SH10rt_1_1: Send called from ProcessRequestQueue
2022.09.05 19:44:40.691 5: DevIo_SimpleWrite SH10rt_1_1: 002c00000006010432c80001
2022.09.05 19:44:40.694 4: SH10rt_1_relay_192.168.x.x: HandleRequest Done, current frame / read buffer: 0033000000060b0432c80001, id 11, fCode 4, tid 51,
request: id 11 fc 4 i13000, len 1, tid 51, for relay device SH10rt_1_relay_192.168.x.x
2022.09.05 19:44:40.695 5: SH10rt_1_relay_192.168.x.x: DropFrame called from ReadFn - drop 0033000000060b0432c80001
2022.09.05 19:44:40.697 5: SH10rt_1_1: readFn buffer: 002c000000050104020000
2022.09.05 19:44:40.698 5: SH10rt_1_1: ParseFrameStart called from ReadFn protocol TCP expecting id 1
2022.09.05 19:44:40.698 4: SH10rt_1_1: ParseFrameStart (TCP, master) extracted id 1, fCode 4, tid 44, dlen 5 and potential data 020000
2022.09.05 19:44:40.699 5: SH10rt_1_1: HandleResponse called from ReadFn
2022.09.05 19:44:40.699 5: SH10rt_1_1: ParseResponse called from HandleResponse
2022.09.05 19:44:40.700 5: SH10rt_1_1: now parsing response data objects, master is SH10rt_1_1 relay is SH10rt_1_relay
2022.09.05 19:44:40.701 5: SH10rt_1_1: ParseDataString called from HandleResponse with data hex 0000, type i, adr 13000
2022.09.05 19:44:40.701 5: SH10rt_1_1: SplitDataString called from ParseDataString with data hex 0000, type i, adr 13000, valuesLen 1
2022.09.05 19:44:40.702 5: SH10rt_1_1: SplitDataString has no information about handling i13000
2022.09.05 19:44:40.702 5: SH10rt_1_1: CreateDataObjects called from ParseDataString with objList
2022.09.05 19:44:40.702 5: SH10rt_1_1: CreateDataObjects sortedList
2022.09.05 19:44:40.703 5: SH10rt_1_1: ParseDataString created 0 readings
2022.09.05 19:44:40.703 5: SH10rt_1_relay: ParseDataString called from HandleResponse with data hex 0000, type i, adr 13000
2022.09.05 19:44:40.704 5: SH10rt_1_relay: SplitDataString called from ParseDataString with data hex 0000, type i, adr 13000, valuesLen 1
2022.09.05 19:44:40.704 5: SH10rt_1_relay: SplitDataString has no information about handling i13000
2022.09.05 19:44:40.705 5: SH10rt_1_relay: CreateDataObjects called from ParseDataString with objList
2022.09.05 19:44:40.705 5: SH10rt_1_relay: CreateDataObjects sortedList
2022.09.05 19:44:40.706 5: SH10rt_1_relay: ParseDataString created 0 readings
2022.09.05 19:44:40.706 4: SH10rt_1_1: RelayResponse via SH10rt_1_relay_192.168.x.x, ioDev SH10rt_1_relay_192.168.x.x, current frame / read buffer: 002c000000050104020000, id 1, fCode 4, tid 44,
request: id 1 fc 4 i13000, len 1, tid 44, master device SH10rt_1_1, for relay device SH10rt_1_relay_192.168.x.x (relayed), queued 0.10 secs ago, sent 0.10 secs ago,
response: id 11, fc 4, i13000, len 1, values 0000, tid 51
2022.09.05 19:44:40.707 5: SH10rt_1_relay_192.168.x.x: Send called from RelayResponse
2022.09.05 19:44:40.707 4: SH10rt_1_relay_192.168.x.x: Send 0033000000050b04020000
2022.09.05 19:44:40.708 4: SH10rt_1_1: HandleResponse done, current frame / read buffer: 002c000000050104020000, id 1, fCode 4, tid 44,
request: id 1 fc 4 i13000, len 1, tid 44, master device SH10rt_1_1, for relay device SH10rt_1_relay_192.168.x.x (relayed), queued 0.11 secs ago, sent 0.11 secs ago,
response: id 11, fc 4, i13000, len 1, values 0000, tid 51
2022.09.05 19:44:40.709 5: SH10rt_1_1: ResetExpect for HandleResponse from response to idle
2022.09.05 19:44:40.712 5: SH10rt_1_1: DropFrame called from ReadFn - drop 002c000000050104020000
2022.09.05 19:44:40.748 5: SH10rt_1_relay_192.168.x.x: readFn buffer: 0034000000060b0432c80001
2022.09.05 19:44:40.749 5: SH10rt_1_relay_192.168.x.x: ParseFrameStart called from ReadFn protocol TCP expecting id 11
2022.09.05 19:44:40.749 4: SH10rt_1_relay_192.168.x.x: ParseFrameStart (TCP, relay) extracted id 11, fCode 4, tid 52, dlen 6 and potential data 32c80001
2022.09.05 19:44:40.749 5: SH10rt_1_relay_192.168.x.x: HandleRequest called from ReadFn
2022.09.05 19:44:40.750 5: SH10rt_1_relay_192.168.x.x: ParseRequest called from HandleRequest
2022.09.05 19:44:40.750 4: SH10rt_1_relay_192.168.x.x: HandleRequest, current frame / read buffer: 0034000000060b0432c80001, id 11, fCode 4, tid 52,
request: id 11 fc 4 i13000, len 1, tid 52
2022.09.05 19:44:40.751 4: SH10rt_1_relay_192.168.x.x: RelayRequest called from HandleRequest
2022.09.05 19:44:40.751 5: SH10rt_1_relay: GetRelayIO found SH10rt_1_1 as Modbus relay forward io device for SH10rt_1_1 with id 1
2022.09.05 19:44:40.751 4: SH10rt_1_relay_192.168.x.x: RelayRequest via SH10rt_1_1, Proto TCP with id 1, current frame / read buffer: 0034000000060b0432c80001, id 11, fCode 4, tid 52,
request: id 11 fc 4 i13000, len 1, tid 52, for relay device SH10rt_1_relay_192.168.x.x
2022.09.05 19:44:40.752 5: SH10rt_1_1: QueueRequest called from RelayRequest with i13000, qlen 0 from master SH10rt_1_1 for relay SH10rt_1_relay_192.168.x.x through io device SH10rt_1_1
2022.09.05 19:44:40.752 5: SH10rt_1_1: ProcessRequestQueue called from QueueRequest as direct:SH10rt_1_1, qlen 1, force, request: request: id 1 fc 4 i13000, len 1, tid 121, master device SH10rt_1_1, for relay device SH10rt_1_relay_192.168.x.x (relayed), queued 0.00 secs ago
2022.09.05 19:44:40.753 5: SH10rt_1_1: checkDelays commDelay, last communication with same device was 0.054 secs ago, required delay is 0.1
2022.09.05 19:44:40.753 5: SH10rt_1_1: checkDelays sendDelay, last send to same device was 0.060 secs ago, required delay is 0.1
2022.09.05 19:44:40.754 5: SH10rt_1_1: checkDelays busDelayRead, last activity on bus was 0.054 secs ago, required delay is 0
2022.09.05 19:44:40.754 5: SH10rt_1_1: checkDelays clientSwitchDelay is not relevant
2022.09.05 19:44:40.754 4: SH10rt_1_1: checkDelays found commDelay not over, sleep for 0.046 forced
2022.09.05 19:44:40.800 4: SH10rt_1_1: checkDelays sleep done, go on with sending
2022.09.05 19:44:40.802 4: SH10rt_1_1: ProcessRequestQueue (V4.4.04 - 17.7.2021) qlen 1, sending 007900000006010432c80001 via 192.168.3.160:502, read buffer empty,
request: id 1 fc 4 i13000, len 1, tid 121, master device SH10rt_1_1, for relay device SH10rt_1_relay_192.168.x.x (relayed), queued 0.05 secs ago
2022.09.05 19:44:40.803 5: SH10rt_1_1: Send called from ProcessRequestQueue
2022.09.05 19:44:40.803 5: DevIo_SimpleWrite SH10rt_1_1: 007900000006010432c80001
2022.09.05 19:44:40.806 4: SH10rt_1_relay_192.168.x.x: HandleRequest Done, current frame / read buffer: 0034000000060b0432c80001, id 11, fCode 4, tid 52,
request: id 11 fc 4 i13000, len 1, tid 52, for relay device SH10rt_1_relay_192.168.x.x
2022.09.05 19:44:40.807 5: SH10rt_1_relay_192.168.x.x: DropFrame called from ReadFn - drop 0034000000060b0432c80001
2022.09.05 19:44:40.810 5: SH10rt_1_1: readFn buffer: 0079000000050104020000
2022.09.05 19:44:40.810 5: SH10rt_1_1: ParseFrameStart called from ReadFn protocol TCP expecting id 1
2022.09.05 19:44:40.810 4: SH10rt_1_1: ParseFrameStart (TCP, master) extracted id 1, fCode 4, tid 121, dlen 5 and potential data 020000
2022.09.05 19:44:40.811 5: SH10rt_1_1: HandleResponse called from ReadFn
2022.09.05 19:44:40.811 5: SH10rt_1_1: ParseResponse called from HandleResponse
2022.09.05 19:44:40.812 5: SH10rt_1_1: now parsing response data objects, master is SH10rt_1_1 relay is SH10rt_1_relay
2022.09.05 19:44:40.812 5: SH10rt_1_1: ParseDataString called from HandleResponse with data hex 0000, type i, adr 13000
2022.09.05 19:44:40.812 5: SH10rt_1_1: SplitDataString called from ParseDataString with data hex 0000, type i, adr 13000, valuesLen 1
2022.09.05 19:44:40.813 5: SH10rt_1_1: SplitDataString has no information about handling i13000
2022.09.05 19:44:40.813 5: SH10rt_1_1: CreateDataObjects called from ParseDataString with objList
2022.09.05 19:44:40.813 5: SH10rt_1_1: CreateDataObjects sortedList
2022.09.05 19:44:40.814 5: SH10rt_1_1: ParseDataString created 0 readings
2022.09.05 19:44:40.814 5: SH10rt_1_relay: ParseDataString called from HandleResponse with data hex 0000, type i, adr 13000
2022.09.05 19:44:40.814 5: SH10rt_1_relay: SplitDataString called from ParseDataString with data hex 0000, type i, adr 13000, valuesLen 1
2022.09.05 19:44:40.815 5: SH10rt_1_relay: SplitDataString has no information about handling i13000
2022.09.05 19:44:40.815 5: SH10rt_1_relay: CreateDataObjects called from ParseDataString with objList
2022.09.05 19:44:40.815 5: SH10rt_1_relay: CreateDataObjects sortedList
2022.09.05 19:44:40.816 5: SH10rt_1_relay: ParseDataString created 0 readings
2022.09.05 19:44:40.816 4: SH10rt_1_1: RelayResponse via SH10rt_1_relay_192.168.x.x, ioDev SH10rt_1_relay_192.168.x.x, current frame / read buffer: 0079000000050104020000, id 1, fCode 4, tid 121,
request: id 1 fc 4 i13000, len 1, tid 121, master device SH10rt_1_1, for relay device SH10rt_1_relay_192.168.x.x (relayed), queued 0.06 secs ago, sent 0.06 secs ago,
response: id 11, fc 4, i13000, len 1, values 0000, tid 52
2022.09.05 19:44:40.817 5: SH10rt_1_relay_192.168.x.x: Send called from RelayResponse
2022.09.05 19:44:40.817 4: SH10rt_1_relay_192.168.x.x: Send 0034000000050b04020000
2022.09.05 19:44:40.818 4: SH10rt_1_1: HandleResponse done, current frame / read buffer: 0079000000050104020000, id 1, fCode 4, tid 121,
request: id 1 fc 4 i13000, len 1, tid 121, master device SH10rt_1_1, for relay device SH10rt_1_relay_192.168.x.x (relayed), queued 0.07 secs ago, sent 0.07 secs ago,
response: id 11, fc 4, i13000, len 1, values 0000, tid 52
2022.09.05 19:44:40.818 5: SH10rt_1_1: ResetExpect for HandleResponse from response to idle
2022.09.05 19:44:40.821 5: SH10rt_1_1: DropFrame called from ReadFn - drop 0079000000050104020000
2022.09.05 19:44:40.824 5: SH10rt_1_relay_192.168.x.x: readFn buffer: 0035000000060b0432d10002
2022.09.05 19:44:40.824 5: SH10rt_1_relay_192.168.x.x: ParseFrameStart called from ReadFn protocol TCP expecting id 11
2022.09.05 19:44:40.825 4: SH10rt_1_relay_192.168.x.x: ParseFrameStart (TCP, relay) extracted id 11, fCode 4, tid 53, dlen 6 and potential data 32d10002
2022.09.05 19:44:40.825 5: SH10rt_1_relay_192.168.x.x: HandleRequest called from ReadFn
2022.09.05 19:44:40.825 5: SH10rt_1_relay_192.168.x.x: ParseRequest called from HandleRequest
2022.09.05 19:44:40.826 4: SH10rt_1_relay_192.168.x.x: HandleRequest, current frame / read buffer: 0035000000060b0432d10002, id 11, fCode 4, tid 53,
request: id 11 fc 4 i13009, len 2, tid 53
2022.09.05 19:44:40.826 4: SH10rt_1_relay_192.168.x.x: RelayRequest called from HandleRequest
2022.09.05 19:44:40.827 5: SH10rt_1_relay: GetRelayIO found SH10rt_1_1 as Modbus relay forward io device for SH10rt_1_1 with id 1
2022.09.05 19:44:40.827 4: SH10rt_1_relay_192.168.x.x: RelayRequest via SH10rt_1_1, Proto TCP with id 1, current frame / read buffer: 0035000000060b0432d10002, id 11, fCode 4, tid 53,
request: id 11 fc 4 i13009, len 2, tid 53, for relay device SH10rt_1_relay_192.168.x.x
2022.09.05 19:44:40.827 5: SH10rt_1_1: QueueRequest called from RelayRequest with i13009, qlen 0 from master SH10rt_1_1 for relay SH10rt_1_relay_192.168.x.x through io device SH10rt_1_1
2022.09.05 19:44:40.828 5: SH10rt_1_1: ProcessRequestQueue called from QueueRequest as direct:SH10rt_1_1, qlen 1, force, request: request: id 1 fc 4 i13009, len 2, tid 23, master device SH10rt_1_1, for relay device SH10rt_1_relay_192.168.x.x (relayed), queued 0.00 secs ago
2022.09.05 19:44:40.829 5: SH10rt_1_1: checkDelays commDelay, last communication with same device was 0.017 secs ago, required delay is 0.1
2022.09.05 19:44:40.829 5: SH10rt_1_1: checkDelays sendDelay, last send to same device was 0.024 secs ago, required delay is 0.1
2022.09.05 19:44:40.829 5: SH10rt_1_1: checkDelays busDelayRead, last activity on bus was 0.017 secs ago, required delay is 0
2022.09.05 19:44:40.830 5: SH10rt_1_1: checkDelays clientSwitchDelay is not relevant
2022.09.05 19:44:40.830 4: SH10rt_1_1: checkDelays found commDelay not over, sleep for 0.083 forced
2022.09.05 19:44:40.913 4: SH10rt_1_1: checkDelays sleep done, go on with sending
2022.09.05 19:44:40.915 4: SH10rt_1_1: ProcessRequestQueue (V4.4.04 - 17.7.2021) qlen 1, sending 001700000006010432d10002 via 192.168.3.160:502, read buffer empty,
request: id 1 fc 4 i13009, len 2, tid 23, master device SH10rt_1_1, for relay device SH10rt_1_relay_192.168.x.x (relayed), queued 0.09 secs ago
2022.09.05 19:44:40.916 5: SH10rt_1_1: Send called from ProcessRequestQueue
2022.09.05 19:44:40.916 5: DevIo_SimpleWrite SH10rt_1_1: 001700000006010432d10002
2022.09.05 19:44:40.919 4: SH10rt_1_relay_192.168.x.x: HandleRequest Done, current frame / read buffer: 0035000000060b0432d10002, id 11, fCode 4, tid 53,
request: id 11 fc 4 i13009, len 2, tid 53, for relay device SH10rt_1_relay_192.168.x.x
2022.09.05 19:44:40.920 5: SH10rt_1_relay_192.168.x.x: DropFrame called from ReadFn - drop 0035000000060b0432d10002
2022.09.05 19:44:40.976 5: SH10rt_1_1: readFn buffer: 001700000007010404fff2ffff
2022.09.05 19:44:40.979 5: SH10rt_1_1: ParseFrameStart called from ReadFn protocol TCP expecting id 1
2022.09.05 19:44:40.984 4: SH10rt_1_1: ParseFrameStart (TCP, master) extracted id 1, fCode 4, tid 23, dlen 7 and potential data 04fff2ffff
2022.09.05 19:44:40.985 5: SH10rt_1_1: HandleResponse called from ReadFn
2022.09.05 19:44:40.986 5: SH10rt_1_1: ParseResponse called from HandleResponse
2022.09.05 19:44:40.987 5: SH10rt_1_1: now parsing response data objects, master is SH10rt_1_1 relay is SH10rt_1_relay
2022.09.05 19:44:40.989 5: SH10rt_1_1: ParseDataString called from HandleResponse with data hex fff2ffff, type i, adr 13009
2022.09.05 19:44:40.990 5: SH10rt_1_1: SplitDataString called from ParseDataString with data hex fff2ffff, type i, adr 13009, valuesLen 2
2022.09.05 19:44:40.991 5: SH10rt_1_1: SplitDataString has no information about handling i13009
2022.09.05 19:44:40.992 5: SH10rt_1_1: SplitDataString has no information about handling i13010
2022.09.05 19:44:40.993 5: SH10rt_1_1: CreateDataObjects called from ParseDataString with objList
2022.09.05 19:44:40.994 5: SH10rt_1_1: CreateDataObjects sortedList
2022.09.05 19:44:40.996 5: SH10rt_1_1: ParseDataString created 0 readings
2022.09.05 19:44:40.996 5: SH10rt_1_relay: ParseDataString called from HandleResponse with data hex fff2ffff, type i, adr 13009
2022.09.05 19:44:40.997 5: SH10rt_1_relay: SplitDataString called from ParseDataString with data hex fff2ffff, type i, adr 13009, valuesLen 2
2022.09.05 19:44:40.998 5: SH10rt_1_relay: SplitDataString has no information about handling i13009
2022.09.05 19:44:40.998 5: SH10rt_1_relay: SplitDataString has no information about handling i13010
2022.09.05 19:44:40.999 5: SH10rt_1_relay: CreateDataObjects called from ParseDataString with objList
2022.09.05 19:44:40.999 5: SH10rt_1_relay: CreateDataObjects sortedList
2022.09.05 19:44:41.000 5: SH10rt_1_relay: ParseDataString created 0 readings
2022.09.05 19:44:41.001 4: SH10rt_1_1: RelayResponse via SH10rt_1_relay_192.168.x.x, ioDev SH10rt_1_relay_192.168.x.x, current frame / read buffer: 001700000007010404fff2ffff, id 1, fCode 4, tid 23,
request: id 1 fc 4 i13009, len 2, tid 23, master device SH10rt_1_1, for relay device SH10rt_1_relay_192.168.x.x (relayed), queued 0.17 secs ago, sent 0.17 secs ago,
response: id 11, fc 4, i13009, len 2, values fff2ffff, tid 53
2022.09.05 19:44:41.002 5: SH10rt_1_relay_192.168.x.x: Send called from RelayResponse
2022.09.05 19:44:41.003 4: SH10rt_1_relay_192.168.x.x: Send 0035000000070b0404fff2ffff
2022.09.05 19:44:41.004 4: SH10rt_1_1: HandleResponse done, current frame / read buffer: 001700000007010404fff2ffff, id 1, fCode 4, tid 23,
request: id 1 fc 4 i13009, len 2, tid 23, master device SH10rt_1_1, for relay device SH10rt_1_relay_192.168.x.x (relayed), queued 0.18 secs ago, sent 0.18 secs ago,
response: id 11, fc 4, i13009, len 2, values fff2ffff, tid 53
2022.09.05 19:44:41.005 5: SH10rt_1_1: ResetExpect for HandleResponse from response to idle
2022.09.05 19:44:41.011 5: SH10rt_1_1: DropFrame called from ReadFn - drop 001700000007010404fff2ffff
2022.09.05 19:44:41.030 5: SH10rt_1_relay_192.168.x.x: readFn buffer: 0036000000060b0432de0001
2022.09.05 19:44:41.030 5: SH10rt_1_relay_192.168.x.x: ParseFrameStart called from ReadFn protocol TCP expecting id 11
2022.09.05 19:44:41.031 4: SH10rt_1_relay_192.168.x.x: ParseFrameStart (TCP, relay) extracted id 11, fCode 4, tid 54, dlen 6 and potential data 32de0001
2022.09.05 19:44:41.031 5: SH10rt_1_relay_192.168.x.x: HandleRequest called from ReadFn
2022.09.05 19:44:41.032 5: SH10rt_1_relay_192.168.x.x: ParseRequest called from HandleRequest
2022.09.05 19:44:41.033 4: SH10rt_1_relay_192.168.x.x: HandleRequest, current frame / read buffer: 0036000000060b0432de0001, id 11, fCode 4, tid 54,
request: id 11 fc 4 i13022, len 1, tid 54
2022.09.05 19:44:41.033 4: SH10rt_1_relay_192.168.x.x: RelayRequest called from HandleRequest
2022.09.05 19:44:41.034 5: SH10rt_1_relay: GetRelayIO found SH10rt_1_1 as Modbus relay forward io device for SH10rt_1_1 with id 1
2022.09.05 19:44:41.035 4: SH10rt_1_relay_192.168.x.x: RelayRequest via SH10rt_1_1, Proto TCP with id 1, current frame / read buffer: 0036000000060b0432de0001, id 11, fCode 4, tid 54,
request: id 11 fc 4 i13022, len 1, tid 54, for relay device SH10rt_1_relay_192.168.x.x
2022.09.05 19:44:41.035 5: SH10rt_1_1: QueueRequest called from RelayRequest with i13022, qlen 0 from master SH10rt_1_1 for relay SH10rt_1_relay_192.168.x.x through io device SH10rt_1_1
2022.09.05 19:44:41.036 5: SH10rt_1_1: ProcessRequestQueue called from QueueRequest as direct:SH10rt_1_1, qlen 1, force, request: request: id 1 fc 4 i13022, len 1, tid 100, master device SH10rt_1_1, for relay device SH10rt_1_relay_192.168.x.x (relayed), queued 0.00 secs ago
2022.09.05 19:44:41.037 5: SH10rt_1_1: checkDelays sendDelay, last send to same device was 0.119 secs ago, required delay is 0.1
2022.09.05 19:44:41.038 5: SH10rt_1_1: checkDelays clientSwitchDelay is not relevant
2022.09.05 19:44:41.038 5: SH10rt_1_1: checkDelays busDelayRead, last activity on bus was 0.051 secs ago, required delay is 0
2022.09.05 19:44:41.038 5: SH10rt_1_1: checkDelays commDelay, last communication with same device was 0.051 secs ago, required delay is 0.1
2022.09.05 19:44:41.039 4: SH10rt_1_1: checkDelays found commDelay not over, sleep for 0.049 forced
2022.09.05 19:44:41.088 4: SH10rt_1_1: checkDelays sleep done, go on with sending
2022.09.05 19:44:41.090 4: SH10rt_1_1: ProcessRequestQueue (V4.4.04 - 17.7.2021) qlen 1, sending 006400000006010432de0001 via 192.168.3.160:502, read buffer empty,
request: id 1 fc 4 i13022, len 1, tid 100, master device SH10rt_1_1, for relay device SH10rt_1_relay_192.168.x.x (relayed), queued 0.05 secs ago
2022.09.05 19:44:41.091 5: SH10rt_1_1: Send called from ProcessRequestQueue
2022.09.05 19:44:41.091 5: DevIo_SimpleWrite SH10rt_1_1: 006400000006010432de0001
2022.09.05 19:44:41.094 4: SH10rt_1_relay_192.168.x.x: HandleRequest Done, current frame / read buffer: 0036000000060b0432de0001, id 11, fCode 4, tid 54,
request: id 11 fc 4 i13022, len 1, tid 54, for relay device SH10rt_1_relay_192.168.x.x
2022.09.05 19:44:41.095 5: SH10rt_1_relay_192.168.x.x: DropFrame called from ReadFn - drop 0036000000060b0432de0001
2022.09.05 19:44:41.101 5: SH10rt_1_1: readFn buffer: 00640000000501040203dc
2022.09.05 19:44:41.101 5: SH10rt_1_1: ParseFrameStart called from ReadFn protocol TCP expecting id 1
2022.09.05 19:44:41.102 4: SH10rt_1_1: ParseFrameStart (TCP, master) extracted id 1, fCode 4, tid 100, dlen 5 and potential data 0203dc
2022.09.05 19:44:41.102 5: SH10rt_1_1: HandleResponse called from ReadFn
2022.09.05 19:44:41.102 5: SH10rt_1_1: ParseResponse called from HandleResponse
2022.09.05 19:44:41.103 5: SH10rt_1_1: now parsing response data objects, master is SH10rt_1_1 relay is SH10rt_1_relay
2022.09.05 19:44:41.103 5: SH10rt_1_1: ParseDataString called from HandleResponse with data hex 03dc, type i, adr 13022
2022.09.05 19:44:41.104 5: SH10rt_1_1: SplitDataString called from ParseDataString with data hex 03dc, type i, adr 13022, valuesLen 1
2022.09.05 19:44:41.104 5: SH10rt_1_1: SplitDataString has no information about handling i13022
2022.09.05 19:44:41.104 5: SH10rt_1_1: CreateDataObjects called from ParseDataString with objList
2022.09.05 19:44:41.105 5: SH10rt_1_1: CreateDataObjects sortedList
2022.09.05 19:44:41.105 5: SH10rt_1_1: ParseDataString created 0 readings
2022.09.05 19:44:41.105 5: SH10rt_1_relay: ParseDataString called from HandleResponse with data hex 03dc, type i, adr 13022
2022.09.05 19:44:41.106 5: SH10rt_1_relay: SplitDataString called from ParseDataString with data hex 03dc, type i, adr 13022, valuesLen 1
2022.09.05 19:44:41.106 5: SH10rt_1_relay: SplitDataString has no information about handling i13022
2022.09.05 19:44:41.106 5: SH10rt_1_relay: CreateDataObjects called from ParseDataString with objList
2022.09.05 19:44:41.107 5: SH10rt_1_relay: CreateDataObjects sortedList
2022.09.05 19:44:41.107 5: SH10rt_1_relay: ParseDataString created 0 readings
2022.09.05 19:44:41.108 4: SH10rt_1_1: RelayResponse via SH10rt_1_relay_192.168.x.x, ioDev SH10rt_1_relay_192.168.x.x, current frame / read buffer: 00640000000501040203dc, id 1, fCode 4, tid 100,
request: id 1 fc 4 i13022, len 1, tid 100, master device SH10rt_1_1, for relay device SH10rt_1_relay_192.168.x.x (relayed), queued 0.07 secs ago, sent 0.07 secs ago,
response: id 11, fc 4, i13022, len 1, values 03dc, tid 54
2022.09.05 19:44:41.108 5: SH10rt_1_relay_192.168.x.x: Send called from RelayResponse
2022.09.05 19:44:41.109 4: SH10rt_1_relay_192.168.x.x: Send 0036000000050b040203dc
2022.09.05 19:44:41.109 4: SH10rt_1_1: HandleResponse done, current frame / read buffer: 00640000000501040203dc, id 1, fCode 4, tid 100,
request: id 1 fc 4 i13022, len 1, tid 100, master device SH10rt_1_1, for relay device SH10rt_1_relay_192.168.x.x (relayed), queued 0.07 secs ago, sent 0.07 secs ago,
response: id 11, fc 4, i13022, len 1, values 03dc, tid 54
2022.09.05 19:44:41.110 5: SH10rt_1_1: ResetExpect for HandleResponse from response to idle
2022.09.05 19:44:41.112 5: SH10rt_1_1: DropFrame called from ReadFn - drop 00640000000501040203dc
2022.09.05 19:44:46.094 3: SH10rt_1_relay_192.168.x.x: read from TCP server connection got null -> closing
2022.09.05 19:44:46.101 3: SH10rt_1_relay_192.168.x.x: _UnDef is closing SH10rt_1_relay_192.168.x.x
2022.09.05 19:44:46.102 5: SH10rt_1_relay_192.168.x.x: Close called from UndefLDFn with noState and noDelete
2022.09.05 19:44:46.102 4: SH10rt_1_relay_192.168.x.x: Close TCP server listening connection and delete hash
2022.09.05 19:44:46.105 5: SH10rt_1_relay_192.168.x.x: Close is removing lastconn from parent device SH10rt_1_relay

Ich hatte außerdem mal die Modbus ID des einen Relays auf 12 geändert, damit nicht beide die gleiche ID haben (11), aber das scheint keinen Unterschied zu machen.

StefanStrobel · 06 September 2022, 08:35:34

Hallo FhemPiUser,

wenn Du Deinen Wechselrichter mit mehreren Mastern anfragst, dann wird das Probleme geben. Soweit ich mich erinnere, verkraftet der nur einen Kommunikationspartner.

Ich gehe auch davon aus, dass das Speicherleck nicht von einem Bug im Modul kommt sondern vom einem Bug in Deinem Perl-Interpreter. Vermutlich wird der getriggert, wenn die Abfragen von evcc vom Relay über Dein Master-Device geleitet werden, in dem selbst eine zyklische Abfrage und viele Register definiert sind.
Eine andere Perl-Version oder ein Relay in einer VM auf einem anderen OS etc. könnten den Bug eventuell auch umgehen.
Zum Testen wäre es aber sehr hilfreich, wenn wir die Relay-Funktion von Deinen eigenen Abfragen und der Interpretation der Objekte trennen könnten.
Du könntest auch das Relay auf einem weiteren Pi aufsetzen und dann sowohl evcc als auch Deine eigenen Abfragen über dieses zusätzliche Relay schicken. Haupsache in der Fhem-Instanz mit dem Relay laufen keine weiteren Abfragen und keine Aufbereitung der Register ...

Gruß
Stefan

FhemPiUser · 08 September 2022, 07:47:10

Merkwürdigerweise gibt es keine Probleme mit dem Wechselrichter, obwohl ich mit mehreren Mastern anfrage (wie beschrieben zwei neue devices SH10rt_1_1 & SH10rt_2_1 zusätzlich zu SH10rt_1 und SH10rt_2). Evtl. weil die Anfragen von der gleichen IP-Adresse kommen. Jedenfalls trat das Speicherleck wieder auf, auch mit den leeren devices SH10rt_1_1 & SH10rt_2_1, an die der relay weiterleitet.

Wenn das nicht weiterhilft, müsste ich mal den Vorschlag mit dem weiteren Pi aufgreifen. Ich würde dann eine frische fhem Installation auf dem zweiten Pi machen und dort nur den relay und die leeren master devices SH10rt_1_1 & SH10rt_2_1 einrichten und evcc auf den relay auf dem zweiten pi konfigurieren - in der Hoffnugn der Wechselrichter kriegt das dann hin, da dann ja die Anfragen von einer anderen IP Adresse kommen. Würde der Test helfen?

Update: Habe das jetzt so umgestellt wie von Dir empfohlen, d.h. eigene fhem Instanz auf eigenem Pi, auf dem nur die Relays (die evcc abfragen) und die dazugehörigen leeren Master-Device SH10rt_1_1 & SH10rt_2_1 (die wiederum den WR abfragen) laufen. Das funktioniert. Was soll ich nun testen?

P.S.: Interessanterweise lehnt der WR die Verbindungen ab, wenn evcc direkt mit dem WR spricht. Es funktioniert aber mit dem fhem modbusattr relay dazwischen (der auf dem gleichem Pi läuft wie evcc).

StefanStrobel · 08 September 2022, 22:51:07

Ok, wenn das Problem auf dem separaten Pi auch auftritt obwohl nur noch die Relay-Funktion aktiv ist und keine eigenen Abfragen mehr gemacht werden, dann müssten wir es identifizieren und beheben können.
Dazu bräuchte ich die vollständige Konfiguration und ausführliche Logs wobei alle Modbus-Devices auf verbose 5 stehen. Am besten über den ganzen Zeitraum, in dem man einen signifikanten Speicheranstieg sehe kann.

Gruß Stefan

KölnSolar · 09 September 2022, 11:01:22

Nach 2 Seiten individueller Thematik, die nichts mit freezemon zu tun hat: Ist es nicht sinniger das Thema in einem eigenen Thread abzuhandeln ?

FhemPiUser · 09 September 2022, 17:30:07

Habe ein neues Thema dafür erstellt unter folgendem Link: https://forum.fhem.de/index.php/topic,129098.0.html

KölnSolar · 17 März 2023, 23:25:58

Hi Oli,
bist ja wieder etwas mehr aktiv(freu).

Ich hab da einen freeze, den mein Modul verursacht.

Wenn ich fhem stoppe, läuft FHEM komischerweise wieder und fährt runter.

Es wird dann auch der freezemon-Eintrag gelogged.

Code Auswählen

2023.03.17 22:44:46 1: [Freezemon] freezedetect: possible freeze starting at 23:45:37, delay is 82749.8 possibly caused by: no bad guy found :-(

Nur weder am 16.3., noch am 17.3. steht irgendetwas in meinen täglichen freezemon-Logs. War die Dauer zu lang ?
Ein anderer Rpi hatte 16.3. 23:45 dasselbe Problem. Der fährt FHEM aber automatisch und schneller runter. Da fand ich Einträge im freezemon-Log.

Code Auswählen

2023.03.17 00:15:56.475 5: [Freezemon] freezedetect: ----------- Starting Freeze handling at 2023.03.17 00:15:56.475 ---------------------
[Freezemon] freezedetect: possible freeze starting at 23:45:37, delay is 1819.474 possibly caused by: no bad guy found :-(-

Idee ?
Grüße Markus

ch.eick · 02 Juni 2023, 10:42:57

EDIT: Wenn es gewünscht wird könnte ich hierfür auch einen eigenen Thread aufmachen.

Hallo zusammen,
seit gestern habe nun auch freezemon aktiviert, da es immer wieder zu kleinen warte Zeiten kommt.
Ich habe keine spezielle Konfiguration gemacht, da ich das Modul noch nicht kenne und so auch schon Meldungen im Log erscheinen

Diese Meldung kann ich bisher gar nicht zuordnen, was könnte das denn sein?

Code Auswählen

2023.06.02 10:18:04.859 1: [Freezemon] myFreezemon: possible freeze starting at 10:18:03, delay is 1.858 possibly caused by: tmr-CODE(0x5566547368)(ProcessRequestQueue) tmr-CODE(0x5566547368)(ProcessRequestQueue)

Könnte ich zur besseren Diagnose noch irgendwelche Einstellungen im freezemon vornehmen?

Was bisher geschah

Code Auswählen

Ich habe stündlich eine KI Prognose für die PV-Anlage, bei der das SQL SELECT als Prozedur im MySQL Docker Container ca. 70 Sekunden läuft.
Danach wird asynchron ein Python Skript mit ebenfalls ca. 60 Sekunden gestartet. Das ganze wird NonBlocking mit DbRep ausgeführt und 
erscheint somit auch nicht beim freezemon. Zur Ausführungszeit geht die RPI4 CPU Zeit von MySQL und anschließend vom Python Skript 
auf 100%, was jedoch anscheinend keinen direkten Einfluss auf FHEM zuhaben scheint.

Dann taucht manchmal tmr-DbLog_execMemCacheAsync(LogDB_2) auf, was wohl durch das PV-Anlagen Logging mit dem Wegschreiben in die DB zusammen hängt.

Ein tmr-HttpUtils_TimeoutErr(N/A), manchmal alle 6 Minuten habe ich wohl schon gefunden, da dort das selbe HTTPMOD Device direkt 
hintereinander mit unterschiedlichem Kommando aufgerufen wurde. 
Das habe ich jetzt mit einer timer Verzögerung im DOIF etwas verschoben. Jetzt scheint es besser zu passen.

Ich habe bereits einige Funktionalitäten zu Docker Containern ausgelagert, was bereits seit 2019 zu einem flüssigeren und stabielerem Ablauf geführt hat.

Code Auswählen

fhem_2022_fhem_1 fhem/fhem:latest
fhem_2022_grafana_old_1 grafana/grafana:7.5.11
fhem_2022_mysql_1 mysql/mysql-server
fhem_2022_node-red_ nodered/node-red:latest
fhem_2022_portainer_1 portainer/portainer:latest
fhem_2022_sonos_1 ghcr.io/svrooij/sonos2mqtt
fhem_2022_vallox_1 mruettgers/vallox-mqtt-bridge:latest
fhem_2022_zigbee2mqtt_1 koenkk/zigbee2mqtt:latest

VG Christian

RalfRog · 28 Juni 2023, 16:58:40

Hallo in die Runde

Habe vergangenen Sonntag ein komplettes FHEM-Update gemacht (ansonsten in diesem Jahr immer bisher nur Module einzeln).
Lt. Log war 98_freezemon.pm im Update nicht dabei - letzte Version Oktober 2021. Ich hatte in der Vergangenheit mal zum Test ein Freezemon definiert - ich meine es wäre zwischnzeitlich inaktiv gesetzt worden.

Lt. aktueller fhem.cfg ist das Device weg

Im RestoreVerzeichnis von Sonntag steht noch:

Code Auswählen

define FreezeMon freezemon
setuuid FreezeMon 63a5bf25-f33f-a8ec-00cc-416f512fef277bc1
attr FreezeMon fm_statistics 1

und auch im Log vom hochfahren steht:

Code Auswählen

2023.06.25 00:35:41.017 3: freezemon defined FreezeMon freezemon
...
2023.06.25 00:38:45.917 0: [Freezemon] FreezeMon: Unwrapping CallFn
2023.06.25 00:38:45.919 0: [Freezemon] FreezeMon: Unwrapping AnalyzeCommand
2023.06.25 00:38:45.920 0: [Freezemon] FreezeMon: Unwrapping HttpUtils_NonblockingGet
2023.06.25 00:38:45.921 0: [Freezemon] FreezeMon: Unwrapping Log3

Danach scheint es "irgendwie/automatisch" aus der fhem.cfg gelöscht worde zu sein, da es nicht mehr enthalten ist.

Wer weiss/hat eine Idee wie es dazu kommen kann?

Gruß Ralf

Edit:
die fhem.cfg trägt den Zeitstempel des Logeintrags "-rw-r--r-- 1 fhem dialout 104700 Jun 25 00:38 fhem.cfg"

vbs · 23 Juli 2023, 11:48:08

Also ich hab bisher immer apptime verwendet, um Freezes auf die Schliche zu kommen, aber wollte nun auch mal freezemon einsetzen. Aber irgendwie kann ich mit freezemon den Verursacher nicht identifizieren - mit apptime aber schon.

Aktuelles Fallbeispiel:
Ich hab ein Gerät (also physisch) "CO2Mini". Das hängt an einem Raspi. Wenn der nicht erreichbar ist, führt das minütlich zu 3 sekündingen Freezes in FHEM.

apptime sagt dazu Folgendes:

Code Auswählen

name                                    function                              max    count      total  average  maxDly  avgDly TS Max call    param Max call
 sz_co2mini                              co2mini_Ready                        3004        2    6009.04  3004.52    0.00    0.00 23.07. 11:24:01 HASH(sz_co2mini)
 sys_cul868                              CUL_Read                                29      14      91.91    6.56    0.00    0.00 23.07. 11:23:32 HASH(sys_cul868)
 sys_cul433                              CUL_Read                                28      14      81.95    5.85    0.00    0.00 23.07. 11:23:32 HASH(sys_cul433)

Also sofort sehr klar zu sehen, woran es liegt.

freezemon meldet minütlich sowas:

Code Auswählen

s:11:32:23 e:11:32:25 f:2.281 d:tmr-FW_closeInactiveClients(N/A) tmr-CODE(0x560294518be0)(YAMAHA_AVR_GetStatus) tmr-DbLog_execMemCacheAsync(benDbLog) tmr-MQTT2_CLIENT_keepalive(sys_mqtt) tmr-EspLedController_Check(wz_lightLedCouch) tmr-EspLedController_Check(ku_lightLedCeil) tmr-EspLedController_Check(sz_lightLedWall) tmr-EspLedController_Check(ku_lightLedFloor) tmr-HMUARTLGW_CheckCredits(sys_culHm) tmr-EspLedController_Check(wz_lightLedTv) tmr-PRESENCE_StartLocalScan(sz_s8_pres)

Da ist mir nicht ganz klar, wie das zu lesen ist. Das sind vermutlich einfach alles mögliche Kandidaten? Also das sind ne ganze Menge, aber ausgerechnet der tatsächliche Verursacher taucht nicht auf. $:-\$

sunrise · 13 November 2023, 15:36:57

Hallo zusammen! Nutzt Ihr das Modul noch?

Ich habe es heute zum 1. Mal verwendet (inkl. Plots) und bin hierüber verwundert:

ZitatFreezes today: 36.845 - Longest Freeze 0.00

Sollen das 36.845 Freezes sein? Aber dann 0.00?

EDIT: Ah, die Anzahl wird in Bruchzahlen im Plot-Titel angegeben. Zumindest sieht es so aus, wenn ich mir die Logs anschaue. Wieso hier aber überhaupt erst eine Bruchzahl entsteht, weiß ich nicht.

Code Auswählen

define MyFreezemon freezemon
setuuid MyFreezemon xxxxx
attr MyFreezemon room Server

define FileLog_MyFreezemon FileLog /opt/fhem/log/MyFreezemon-%Y-%m.log MyFreezemon
setuuid FileLog_MyFreezemon xxxxx
attr FileLog_MyFreezemon archivedir /opt/fhem/log/archive/
attr FileLog_MyFreezemon createGluedFile 1
attr FileLog_MyFreezemon nrarchive 2

define SVG_FileLog_MyFreezemon SVG FileLog_MyFreezemon:freezemon_gplot:CURRENT
setuuid SVG_FileLog_MyFreezemon xxxxx
attr SVG_FileLog_MyFreezemon plotReplace TL={"Freezes today: ".$data{max1}." - Longest Freeze ".sprintf("%.2f ",$data{max2}) }
attr SVG_FileLog_MyFreezemon room Server

define SVG_FileLog_MyFreezemon_day SVG FileLog_MyFreezemon:freezemon_day:CURRENT
setuuid SVG_FileLog_MyFreezemon_day xxxxx
attr SVG_FileLog_MyFreezemon_day fixedrange month
attr SVG_FileLog_MyFreezemon_day plotReplace TL={"Max Freezes: ".$data{max1}." - Max Freezetime ".sprintf("%.2f ",$data{max2}) }
attr SVG_FileLog_MyFreezemon_day room Server

Ich weiß, dass das THZ-Modul (für eine SE/Tecalor Wärmepumpe) hin und wieder Hänger hat, aber die o.g. Zahl macht für mich keinen Sinn.

Blick ins komplette Freezemon Log:

Code Auswählen

2023-11-13_14:16:01 MyFreezemon s:14:16:00 e:14:16:01 f:1.414 d:tmr-THZ_GetRefresh(N/A) 
2023-11-13_14:16:01 MyFreezemon freezeTime: 1.414
2023-11-13_14:16:01 MyFreezemon fcDay: 3
2023-11-13_14:16:01 MyFreezemon ftDay: 7.143
2023-11-13_14:16:01 MyFreezemon freezeDevice: tmr-THZ_GetRefresh(N/A) 
2023-11-13_14:18:24 MyFreezemon s:14:18:22 e:14:18:24 f:2.476 d:tmr-THZ_GetRefresh(N/A) 
2023-11-13_14:18:24 MyFreezemon freezeTime: 2.476
2023-11-13_14:18:24 MyFreezemon fcDay: 4
2023-11-13_14:18:24 MyFreezemon ftDay: 9.619
2023-11-13_14:18:24 MyFreezemon freezeDevice: tmr-THZ_GetRefresh(N/A) 
2023-11-13_14:18:47 MyFreezemon s:14:18:46 e:14:18:47 f:1.306 d:no bad guy found :-(
2023-11-13_14:18:47 MyFreezemon freezeTime: 1.306
2023-11-13_14:18:47 MyFreezemon fcDay: 5
2023-11-13_14:18:47 MyFreezemon ftDay: 10.925
2023-11-13_14:18:47 MyFreezemon freezeDevice: no bad guy found :-(
2023-11-13_14:22:43 MyFreezemon s:14:22:41 e:14:22:43 f:2.464 d:tmr-THZ_GetRefresh(N/A) 
2023-11-13_14:22:43 MyFreezemon freezeTime: 2.464
2023-11-13_14:22:43 MyFreezemon fcDay: 6
2023-11-13_14:22:43 MyFreezemon ftDay: 13.389
2023-11-13_14:22:43 MyFreezemon freezeDevice: tmr-THZ_GetRefresh(N/A) 
2023-11-13_14:26:59 MyFreezemon s:14:26:57 e:14:26:59 f:2.458 d:tmr-THZ_GetRefresh(N/A) 
2023-11-13_14:26:59 MyFreezemon freezeTime: 2.458
2023-11-13_14:26:59 MyFreezemon fcDay: 7
2023-11-13_14:26:59 MyFreezemon ftDay: 15.847
2023-11-13_14:26:59 MyFreezemon freezeDevice: tmr-THZ_GetRefresh(N/A) 
2023-11-13_14:29:43 MyFreezemon s:14:29:41 e:14:29:43 f:2.474 d:tmr-THZ_GetRefresh(N/A) 
2023-11-13_14:29:43 MyFreezemon freezeTime: 2.474
2023-11-13_14:29:43 MyFreezemon fcDay: 8
2023-11-13_14:29:43 MyFreezemon ftDay: 18.321
2023-11-13_14:29:43 MyFreezemon freezeDevice: tmr-THZ_GetRefresh(N/A) 
2023-11-13_14:32:59 MyFreezemon s:14:32:57 e:14:32:59 f:2.465 d:tmr-THZ_GetRefresh(N/A) 
2023-11-13_14:32:59 MyFreezemon freezeTime: 2.465
2023-11-13_14:32:59 MyFreezemon fcDay: 9
2023-11-13_14:32:59 MyFreezemon ftDay: 20.786
2023-11-13_14:32:59 MyFreezemon freezeDevice: tmr-THZ_GetRefresh(N/A) 
2023-11-13_14:35:12 MyFreezemon s:14:35:10 e:14:35:12 f:2.449 d:tmr-THZ_GetRefresh(N/A) 
2023-11-13_14:35:12 MyFreezemon freezeTime: 2.449
2023-11-13_14:35:12 MyFreezemon fcDay: 10
2023-11-13_14:35:12 MyFreezemon ftDay: 23.235
2023-11-13_14:35:12 MyFreezemon freezeDevice: tmr-THZ_GetRefresh(N/A) 
2023-11-13_14:37:22 MyFreezemon s:14:37:20 e:14:37:22 f:2.438 d:tmr-THZ_GetRefresh(N/A) 
2023-11-13_14:37:22 MyFreezemon freezeTime: 2.438
2023-11-13_14:37:22 MyFreezemon fcDay: 11
2023-11-13_14:37:22 MyFreezemon ftDay: 25.673
2023-11-13_14:37:22 MyFreezemon freezeDevice: tmr-THZ_GetRefresh(N/A) 
2023-11-13_14:40:29 MyFreezemon s:14:40:27 e:14:40:29 f:2.439 d:tmr-THZ_GetRefresh(N/A) 
2023-11-13_14:40:29 MyFreezemon freezeTime: 2.439
2023-11-13_14:40:29 MyFreezemon fcDay: 12
2023-11-13_14:40:29 MyFreezemon ftDay: 28.112
2023-11-13_14:40:29 MyFreezemon freezeDevice: tmr-THZ_GetRefresh(N/A) 
2023-11-13_15:08:56 MyFreezemon s:15:08:54 e:15:08:56 f:2.169 d:tmr-THZ_GetRefresh(N/A) 
2023-11-13_15:08:56 MyFreezemon freezeTime: 2.169
2023-11-13_15:08:56 MyFreezemon fcDay: 13
2023-11-13_15:08:56 MyFreezemon ftDay: 30.281
2023-11-13_15:08:56 MyFreezemon freezeDevice: tmr-THZ_GetRefresh(N/A) 
2023-11-13_15:21:56 MyFreezemon s:15:21:54 e:15:21:56 f:2.178 d:tmr-THZ_GetRefresh(N/A) 
2023-11-13_15:21:56 MyFreezemon freezeTime: 2.178
2023-11-13_15:21:56 MyFreezemon fcDay: 14
2023-11-13_15:21:56 MyFreezemon ftDay: 32.459
2023-11-13_15:21:56 MyFreezemon freezeDevice: tmr-THZ_GetRefresh(N/A) 
2023-11-13_15:24:16 MyFreezemon s:15:24:14 e:15:24:16 f:2.187 d:tmr-THZ_GetRefresh(N/A) 
2023-11-13_15:24:16 MyFreezemon freezeTime: 2.187
2023-11-13_15:24:16 MyFreezemon fcDay: 15
2023-11-13_15:24:16 MyFreezemon ftDay: 34.646
2023-11-13_15:24:16 MyFreezemon freezeDevice: tmr-THZ_GetRefresh(N/A) 
2023-11-13_15:29:11 MyFreezemon s:15:29:09 e:15:29:11 f:2.199 d:tmr-THZ_GetRefresh(N/A) 
2023-11-13_15:29:11 MyFreezemon freezeTime: 2.199
2023-11-13_15:29:11 MyFreezemon fcDay: 16
2023-11-13_15:29:11 MyFreezemon ftDay: 36.845
2023-11-13_15:29:11 MyFreezemon freezeDevice: tmr-THZ_GetRefresh(N/A)

Was ist das denn? Verursacher des Freezes nicht identifiziert?

Zitatno bad guy found

Gisbert · 14 November 2023, 09:54:56

Hallo sunrise,

ich nutze das Modul immer noch. Seit ein paar Monaten bin ich von einem HP T610 auf einen Fujitsu Futro S740 (mit Proxmox) umgestiegen. Letzter ist ca. 5-6mal schneller als der HP, weshalb ich nur noch wenige kurze Freezes habe

Viele Grüße Gisbert