modebus-flex-getter

[wangganggit]

Which node-red-contrib-modbus version are you using?

5.40.0

What happened?

The 1-second rotation training was set, but it always reconnected after a period of time, resulting in a partial loss of data collection during that time period。

{"log":"9 Aug 08:18:28 - [warn] [modbus-flex-getter:192.168.102.100] Modbus Failure On State sending Get More About It By Logging\r\n","stream":"stdout","time":"2024-08-09T08:18:28.655016649Z"} {"log":"9 Aug 08:18:28 - [error] [modbus-flex-getter:192.168.102.100] Error: Timed out\r\n","stream":"stdout","time":"2024-08-09T08:18:28.655049399Z"} {"log":"9 Aug 08:18:28 - [info] [debug:debug 1] \r\n","stream":"stdout","time":"2024-08-09T08:18:28.655054149Z"} {"log":"9 Aug 08:18:33 - [info] [debug:debug 1] \r\n","stream":"stdout","time":"2024-08-09T08:18:33.65868257Z"}

Server

Modbus-Flex-Server Node (Please attach Script to the next section)

How can this be reproduced?

[ { "id": "75234d74bd9aadd5", "type": "modbus-flex-getter", "z": "f6f2187d.f17ca8", "name": "192.168.102.100", "showStatusActivities": true, "showErrors": true, "showWarnings": true, "logIOActivities": false, "server": "56be8af8440d8658", "useIOFile": false, "ioFile": "", "useIOForPayload": false, "emptyMsgOnFail": true, "keepMsgProperties": true, "delayOnStart": false, "startDelayTime": "", "x": 760, "y": 280, "wires": [ [ "255b41c93483b73b", "0156b42b397d46ce" ], [ "01d7950f0bfa4d28" ] ] }, { "id": "56be8af8440d8658", "type": "modbus-client", "name": "192.168.102.100", "clienttype": "tcp", "bufferCommands": true, "stateLogEnabled": false, "queueLogEnabled": false, "failureLogEnabled": true, "tcpHost": "192.168.102.100", "tcpPort": "502", "tcpType": "DEFAULT", "serialPort": "/dev/ttyUSB", "serialType": "RTU-BUFFERD", "serialBaudrate": "9600", "serialDatabits": "8", "serialStopbits": "1", "serialParity": "none", "serialConnectionDelay": "100", "serialAsciiResponseStartDelimiter": "0x3A", "unit_id": "1", "commandDelay": "1", "clientTimeout": "1000", "reconnectOnTimeout": true, "reconnectTimeout": "2000", "parallelUnitIdsAllowed": true, "showErrors": false, "showWarnings": true, "showLogs": true } ]

What did you expect to happen?

No response

Other Information

No response

[wangganggit]

以下是版本 nodered V4.0.2
node.js v20.15.1 node-red-contrib-modbus v5.41.0

[wangganggit]

以下是版本 nodered V4.0.2
node.js v20.15.1 node-red-contrib-modbus v5.41.0

[wangganggit]

{"log":" \u001b[34;1mmodbus-serial \u001b[0m unitid: \u001b[33m1\u001b[39m,\r\n","stream":"stdout","time":"2024-08-13T01:57:33.696943912Z"} {"log":" \u001b[34;1mmodbus-serial \u001b[0m functionCode: \u001b[33m3\u001b[39m,\r\n","stream":"stdout","time":"2024-08-13T01:57:33.69694678Z"} {"log":" \u001b[34;1mmodbus-serial \u001b[0m transactionsId: \u001b[33m34\u001b[39m\r\n","stream":"stdout","time":"2024-08-13T01:57:33.69694999Z"} {"log":" \u001b[34;1mmodbus-serial \u001b[0m} \u001b[34m+999ms\u001b[0m\r\n","stream":"stdout","time":"2024-08-13T01:57:33.696952957Z"} {"log":" \u001b[32;1mcontribModbus:queue:core \u001b[0mqueue serial unlock command node name: 192.168.102.100 id: ac5edb4e4e00ef90 \u001b[32m+1s\u001b[0m\r\n","stream":"stdout","time":"2024-08-13T01:57:34.697599196Z"} {"log":" \u001b[32;1mcontribModbus:queue:core \u001b[0mqueue serial unlock command node name: 192.168.102.100 id: ac5edb4e4e00ef90 \u001b[32m+0ms\u001b[0m\r\n","stream":"stdout","time":"2024-08-13T01:57:34.697638958Z"} {"log":" \u001b[34;1mmodbus-serial \u001b[0mmodbusErrorHandling:Timed out \u001b[34m+22m\u001b[0m\r\n","stream":"stdout","time":"2024-08-13T01:57:34.697643535Z"} {"log":" \u001b[32;1mcontribModbus:queue:core \u001b[0mqueue serial lock command node name: 192.168.102.100 id: ac5edb4e4e00ef90 \u001b[32m+0ms\u001b[0m\r\n","stream":"stdout","time":"2024-08-13T01:57:34.697646809Z"} {"log":" \u001b[32;1mcontribModbus:flex:getter \u001b[0mTimed out \u001b[32m+22m\u001b[0m\r\n","stream":"stdout","time":"2024-08-13T01:57:34.697649896Z"} {"log":" \u001b[34;1mmodbus-serial \u001b[0mTCP port: signal error: Error: read ECONNRESET \u001b[34m+1s\u001b[0m\r\n","stream":"stdout","time":"2024-08-13T01:57:35.11412102Z"} {"log":" \u001b[34;1mmodbus-serial \u001b[0mTCP port: signal close: true \u001b[34m+0ms\u001b[0m\r\n","stream":"stdout","time":"2024-08-13T01:57:35.11415247Z"} {"log":" \u001b[34;1mmodbus-serial \u001b[0mTCP port: signal connect \u001b[34m+4s\u001b[ 0m\r\n","stream":"stdout","time":"2024-08-13T01:57:38.701494855Z"} {"log":" \u001b[32;1mcontribModbus:queue:core \u001b[0mqueue serial unlock command node name: 192.168.102.100 id: ac5edb4e4e00ef90 \u001b[32m+4s\u001b[0m\r\n","stream":"stdout","time":"2024-08-13T01:57:38.701523468Z"} {"log":" \u001b[32;1mcontribModbus:queue:core \u001b[0msequential de-queue command \u001b[32m+998ms\u001b[0m\r\n","stream":"stdout","time":"2024-08-13T01:57:39.700803761Z"}