I have an issue using the "Modbus Read" node of node-red-contrib-modbus. My modbus communication works on a Windows PC using CAS Modbus Scanner. Using the same hardware on a Raspberry Pi gives me some trouble. I am using a USB-RS485-Dongle and a SBC ALE3D5F energy meter. (sorry, as a new user I was only allowed to place two pictures and two links)
The USB-RS485-Dongle seems to be installed correctly:
~ $ dmesg
[ 5.926915] usb 1-1.3: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.54
[ 5.943737] usb 1-1.3: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 5.955483] usb 1-1.3: Product: USB2.0-Ser!
[ 10.172846] usb 1-1.3: ch341-uart converter now attached to ttyUSB0
Node-red-contrib-modbus recommends debugging via DEBUG=contribModbus* node-red -v. This gives the following result:
10 Feb 20:29:53 - [info] Starting flows
contribModbus:queue:core queue serial lock command node Serial_9600_8_E_1 +0ms
contribModbus:core:client Client -> new +0ms
contribModbus:core:client Client -> initialized +2ms
contribModbus:queue:core queue serial lock command node undefined +18ms
contribModbus:core:client Client -> new +12ms
contribModbus:core:client Client -> initialized +1ms
10 Feb 20:29:53 - [warn] [modbus-read:a16a70db.ede3f] Client -> open node a16a70db.ede3fundefined
contribModbus:core:client Client -> new +18ms
contribModbus:core:client Client -> init +2ms
10 Feb 20:29:53 - [warn] [modbus-client:5c2c3186.30196] Client -> fsm init state after new
10 Feb 20:29:53 - [warn] [modbus-client:5c2c3186.30196] Client -> first fsm init in 500 ms Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1
contribModbus:core:client Client -> init Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +14ms
contribModbus:core:client Client -> init Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +0ms
10 Feb 20:29:53 - [info] Started flows
10 Feb 20:29:53 - [error] Unable to listen on http://127.0.0.1:1880/
10 Feb 20:29:53 - [error] Error: port in use
Does anybody have a qualified recommendation, how to fix this issue?
And if that does not fix it - look at permissions on the TTY device - make sure the user that is starting and running node-red has permissions to that device/directory.
Do a search on the forum - about 2 months ago this same issue came up and was i believe resolved.
Do you have the modbus registers/map for the Energy meter ?
Can you confirm from the menu of your energy meter that the settings for the modbus device id, baud rate, Data bits etc are matching .. also check if the cabling is ok.
It seems that it does an auto read of two registers (big endian) if they are grouped together - which is a little strange - you would send out a request for one register and it sends back two.
Try one of the simple registers on there - based on you using the windows app and verifying all good i would suggest trying another modbus node - i remember when i was trying to get into Modbus to start with - same PC - Modbus-CAS would work to let me query the unit as would some commandline python tools - but i could not get the MOdbus nodes working on NR (under Windows)
Correct, the sbc energy meter is doing auto detection on the transmission baud rate and the parity is as well automatically detected. Nevertheless, on windows 9600 baud didn't work; 19200 worked without problems, reading single and multiple registers (in CAS you select the first register an define the amount). As you see in my Node-RED setup, I only want to read one simple voltage parameter. I tried to keep it simple and plan increase complexity after the simple stuff is working.
Yep - but as per the above - before you go any further - the error message you were giving is saying that NR is not running on the port - can you show your startup logs again after fixing that error ?
Thank you Colin! This (I believe) was a consequence of running DEBUG=contribModbus* node-red -v. (I hope)
I restarted the Raspi several times after this DEBUG-attempt and believe only one instance is running. How can I check if there are running multiple instances of Node-RED?
~ $ DEBUG=contribModbus* node-red -v
10 Feb 23:52:01 - [info]
Welcome to Node-RED
===================
10 Feb 23:52:01 - [info] Node-RED version: v1.2.9
10 Feb 23:52:01 - [info] Node.js version: v12.20.1
10 Feb 23:52:01 - [info] Linux 5.10.11-v7+ arm LE
10 Feb 23:52:03 - [info] Loading palette nodes
10 Feb 23:52:09 - [info] Dashboard version 2.27.0 started at /ui
10 Feb 23:52:09 - [info] Settings file : /home/pi/.node-red/settings.js
10 Feb 23:52:09 - [info] Context store : 'default' [module=memory]
10 Feb 23:52:09 - [info] User directory : /home/pi/.node-red
10 Feb 23:52:09 - [warn] Projects disabled : editorTheme.projects.enabled=false
10 Feb 23:52:09 - [info] Flows file : /home/pi/.node-red/flows_HeatingPi.json
10 Feb 23:52:10 - [warn]
---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------
10 Feb 23:52:10 - [info] Starting flows
contribModbus:queue:core queue serial lock command node Serial_9600_8_E_1 +0ms
contribModbus:core:client Client -> new +0ms
contribModbus:core:client Client -> initialized +2ms
contribModbus:queue:core queue serial lock command node undefined +21ms
contribModbus:core:client Client -> new +14ms
contribModbus:core:client Client -> initialized +2ms
10 Feb 23:52:10 - [warn] [modbus-read:a16a70db.ede3f] Client -> open node a16a70db.ede3fundefined
contribModbus:core:client Client -> new +20ms
contribModbus:core:client Client -> init +3ms
10 Feb 23:52:10 - [warn] [modbus-client:5c2c3186.30196] Client -> fsm init state after new
10 Feb 23:52:10 - [warn] [modbus-client:5c2c3186.30196] Client -> first fsm init in 500 ms Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1
contribModbus:core:client Client -> init Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +15ms
contribModbus:core:client Client -> init Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +1ms
10 Feb 23:52:10 - [info] Started flows
10 Feb 23:52:10 - [error] Unable to listen on http://127.0.0.1:1880/
10 Feb 23:52:10 - [error] Error: port in use
It is on autostart and I did not try to start it manually again. Can it be that the DEBUG is trying to start Node-RED again?
The DEBUG-log changed:
~ $ systemctl stop nodered
==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===
Authentication is required to stop 'nodered.service'.
Authenticating as: ,,, (pi)
Password:
==== AUTHENTICATION COMPLETE ===
~ $ DEBUG=contribModbus* node-red -v
10 Feb 23:58:39 - [info]
Welcome to Node-RED
===================
10 Feb 23:58:39 - [info] Node-RED version: v1.2.9
10 Feb 23:58:39 - [info] Node.js version: v12.20.1
10 Feb 23:58:39 - [info] Linux 5.10.11-v7+ arm LE
10 Feb 23:58:41 - [info] Loading palette nodes
10 Feb 23:58:47 - [info] Dashboard version 2.27.0 started at /ui
10 Feb 23:58:47 - [info] Settings file : /home/pi/.node-red/settings.js
10 Feb 23:58:47 - [info] Context store : 'default' [module=memory]
10 Feb 23:58:47 - [info] User directory : /home/pi/.node-red
10 Feb 23:58:47 - [warn] Projects disabled : editorTheme.projects.enabled=false
10 Feb 23:58:47 - [info] Flows file : /home/pi/.node-red/flows_HeatingPi.json
10 Feb 23:58:47 - [warn]
---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------
10 Feb 23:58:47 - [info] Starting flows
contribModbus:queue:core queue serial lock command node Serial_9600_8_E_1 +0ms
contribModbus:core:client Client -> new +0ms
contribModbus:core:client Client -> initialized +2ms
contribModbus:queue:core queue serial lock command node undefined +19ms
contribModbus:core:client Client -> new +12ms
contribModbus:core:client Client -> initialized +1ms
10 Feb 23:58:48 - [warn] [modbus-read:a16a70db.ede3f] Client -> open node a16a70db.ede3fundefined
contribModbus:core:client Client -> new +18ms
contribModbus:core:client Client -> init +2ms
10 Feb 23:58:48 - [warn] [modbus-client:5c2c3186.30196] Client -> fsm init state after new
10 Feb 23:58:48 - [warn] [modbus-client:5c2c3186.30196] Client -> first fsm init in 500 ms Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1
contribModbus:core:client Client -> init Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +14ms
contribModbus:core:client Client -> init Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +1ms
10 Feb 23:58:48 - [info] Started flows
10 Feb 23:58:48 - [info] Server now running at http://127.0.0.1:1880/
contribModbus:core:client Client -> RTU buffered port serial Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +494ms
contribModbus:core:client Client -> opened Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +24ms
contribModbus:queue:core queue serial unlock command node undefined +557ms
contribModbus:core:client Client -> time to open Unit 1 Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +1s
contribModbus:core:client Client -> connected Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +3ms
10 Feb 23:58:49 - [warn] [modbus-client:5c2c3186.30196] Client -> fsm connected after state opened Get More About It By Logging Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1
contribModbus:queue:core queue serial unlock command node undefined +1s
10 Feb 23:58:49 - [warn] [modbus-read:a16a70db.ede3f] Client -> startIntervalReading node a16a70db.ede3fundefined
contribModbus:core:client Client -> connected Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +10s
contribModbus:queue:core queue serial unlock command node undefined +13s
contribModbus:queue:core queue serial unlock command node undefined +3ms
contribModbus:core:client Client -> failed Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +3s
10 Feb 23:59:02 - [warn] [modbus-client:5c2c3186.30196] Client -> fsm failed state after connected Get More About It By Logging Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1
10 Feb 23:59:02 - [warn] [modbus-read:a16a70db.ede3f] Modbus Failure On State connected Get More About It By Logging
contribModbus:core:client Client -> broken Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +8ms
10 Feb 23:59:02 - [warn] [modbus-client:5c2c3186.30196] Client -> fsm broken state after failed Get More About It By Logging Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1
contribModbus:core:client Client -> activated Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +4ms
contribModbus:read Timed out +0ms
10 Feb 23:59:02 - [error] [modbus-read:a16a70db.ede3f] Timed out
contribModbus:core:client Client -> activated Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +21ms
contribModbus:core:client Client -> reading Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +7s
contribModbus:queue:core queue serial unlock command node undefined +10s
contribModbus:queue:core queue serial unlock command node undefined +1ms
contribModbus:core:client Client -> failed Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +3s
10 Feb 23:59:12 - [warn] [modbus-client:5c2c3186.30196] Client -> fsm failed state after reading Get More About It By Logging Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1
10 Feb 23:59:12 - [warn] [modbus-read:a16a70db.ede3f] Modbus Failure On State reading Get More About It By Logging
contribModbus:core:client Client -> broken Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +4ms
10 Feb 23:59:12 - [warn] [modbus-client:5c2c3186.30196] Client -> fsm broken state after failed Get More About It By Logging Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1
contribModbus:core:client Client -> activated Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +2ms
contribModbus:read Timed out +10s
10 Feb 23:59:12 - [error] [modbus-read:a16a70db.ede3f] Timed out
contribModbus:core:client Client -> activated Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +5ms
contribModbus:core:client Client -> reading Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +7s
contribModbus:queue:core queue serial unlock command node undefined +10s
contribModbus:queue:core queue serial unlock command node undefined +1ms
contribModbus:core:client Client -> failed Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +3s
10 Feb 23:59:22 - [warn] [modbus-client:5c2c3186.30196] Client -> fsm failed state after reading Get More About It By Logging Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1
10 Feb 23:59:22 - [warn] [modbus-read:a16a70db.ede3f] Modbus Failure On State reading Get More About It By Logging
contribModbus:core:client Client -> broken Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +6ms
10 Feb 23:59:22 - [warn] [modbus-client:5c2c3186.30196] Client -> fsm broken state after failed Get More About It By Logging Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1
contribModbus:core:client Client -> activated Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +3ms
contribModbus:read Timed out +10s
10 Feb 23:59:22 - [error] [modbus-read:a16a70db.ede3f] Timed out
contribModbus:core:client Client -> activated Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +5ms
contribModbus:core:client Client -> reading Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +7s
contribModbus:queue:core queue serial unlock command node undefined +10s
contribModbus:queue:core queue serial unlock command node undefined +1ms
contribModbus:core:client Client -> failed Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +3s
10 Feb 23:59:32 - [warn] [modbus-client:5c2c3186.30196] Client -> fsm failed state after reading Get More About It By Logging Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1
10 Feb 23:59:32 - [warn] [modbus-read:a16a70db.ede3f] Modbus Failure On State reading Get More About It By Logging
contribModbus:core:client Client -> broken Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +4ms
10 Feb 23:59:32 - [warn] [modbus-client:5c2c3186.30196] Client -> fsm broken state after failed Get More About It By Logging Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1
contribModbus:core:client Client -> activated Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +2ms
contribModbus:read Timed out +10s
10 Feb 23:59:32 - [error] [modbus-read:a16a70db.ede3f] Timed out
contribModbus:core:client Client -> activated Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +5ms
contribModbus:core:client Client -> reading Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +7s
contribModbus:queue:core queue serial unlock command node undefined +10s
contribModbus:queue:core queue serial unlock command node undefined +1ms
contribModbus:core:client Client -> failed Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +3s
10 Feb 23:59:42 - [warn] [modbus-client:5c2c3186.30196] Client -> fsm failed state after reading Get More About It By Logging Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1
10 Feb 23:59:42 - [warn] [modbus-read:a16a70db.ede3f] Modbus Failure On State reading Get More About It By Logging
contribModbus:core:client Client -> broken Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +5ms
10 Feb 23:59:42 - [warn] [modbus-client:5c2c3186.30196] Client -> fsm broken state after failed Get More About It By Logging Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1
contribModbus:core:client Client -> activated Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +3ms
contribModbus:read Timed out +10s
10 Feb 23:59:42 - [error] [modbus-read:a16a70db.ede3f] Timed out
contribModbus:core:client Client -> activated Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +6ms
contribModbus:core:client Client -> reading Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +7s
contribModbus:queue:core queue serial unlock command node undefined +10s
contribModbus:queue:core queue serial unlock command node undefined +1ms
contribModbus:core:client Client -> failed Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +3s
10 Feb 23:59:52 - [warn] [modbus-client:5c2c3186.30196] Client -> fsm failed state after reading Get More About It By Logging Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1
10 Feb 23:59:52 - [warn] [modbus-read:a16a70db.ede3f] Modbus Failure On State reading Get More About It By Logging
contribModbus:core:client Client -> broken Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +5ms
10 Feb 23:59:52 - [warn] [modbus-client:5c2c3186.30196] Client -> fsm broken state after failed Get More About It By Logging Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1
contribModbus:core:client Client -> activated Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +3ms
contribModbus:read Timed out +10s
10 Feb 23:59:52 - [error] [modbus-read:a16a70db.ede3f] Timed out
contribModbus:core:client Client -> activated Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +5ms
contribModbus:core:client Client -> reading Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +7s
contribModbus:queue:core queue serial unlock command node undefined +10s
contribModbus:queue:core queue serial unlock command node undefined +1ms
contribModbus:core:client Client -> failed Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +3s
11 Feb 00:00:02 - [warn] [modbus-client:5c2c3186.30196] Client -> fsm failed state after reading Get More About It By Logging Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1
11 Feb 00:00:02 - [warn] [modbus-read:a16a70db.ede3f] Modbus Failure On State reading Get More About It By Logging
contribModbus:core:client Client -> broken Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +6ms
11 Feb 00:00:02 - [warn] [modbus-client:5c2c3186.30196] Client -> fsm broken state after failed Get More About It By Logging Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1
contribModbus:core:client Client -> activated Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +3ms
contribModbus:read Timed out +10s
11 Feb 00:00:02 - [error] [modbus-read:a16a70db.ede3f] Timed out
contribModbus:core:client Client -> activated Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +5ms
contribModbus:core:client Client -> reading Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +7s
contribModbus:queue:core queue serial unlock command node undefined +10s
contribModbus:queue:core queue serial unlock command node undefined +1ms
contribModbus:core:client Client -> failed Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +3s
11 Feb 00:00:12 - [warn] [modbus-client:5c2c3186.30196] Client -> fsm failed state after reading Get More About It By Logging Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1
11 Feb 00:00:12 - [warn] [modbus-read:a16a70db.ede3f] Modbus Failure On State reading Get More About It By Logging
contribModbus:core:client Client -> broken Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +6ms
11 Feb 00:00:12 - [warn] [modbus-client:5c2c3186.30196] Client -> fsm broken state after failed Get More About It By Logging Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1
contribModbus:core:client Client -> activated Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +3ms
contribModbus:read Timed out +10s
11 Feb 00:00:12 - [error] [modbus-read:a16a70db.ede3f] Timed out
contribModbus:core:client Client -> activated Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +5ms
contribModbus:core:client Client -> reading Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +7s
contribModbus:queue:core queue serial unlock command node undefined +10s
contribModbus:queue:core queue serial unlock command node undefined +1ms
contribModbus:core:client Client -> failed Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +3s
11 Feb 00:00:22 - [warn] [modbus-client:5c2c3186.30196] Client -> fsm failed state after reading Get More About It By Logging Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1
11 Feb 00:00:22 - [warn] [modbus-read:a16a70db.ede3f] Modbus Failure On State reading Get More About It By Logging
contribModbus:core:client Client -> broken Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +5ms
11 Feb 00:00:22 - [warn] [modbus-client:5c2c3186.30196] Client -> fsm broken state after failed Get More About It By Logging Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1
contribModbus:core:client Client -> activated Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +3ms
contribModbus:read Timed out +10s
11 Feb 00:00:22 - [error] [modbus-read:a16a70db.ede3f] Timed out
contribModbus:core:client Client -> activated Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +6ms
contribModbus:core:client Client -> reading Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +7s
contribModbus:queue:core queue serial unlock command node undefined +10s
contribModbus:queue:core queue serial unlock command node undefined +1ms
contribModbus:core:client Client -> failed Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +3s
11 Feb 00:00:32 - [warn] [modbus-client:5c2c3186.30196] Client -> fsm failed state after reading Get More About It By Logging Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1
11 Feb 00:00:32 - [warn] [modbus-read:a16a70db.ede3f] Modbus Failure On State reading Get More About It By Logging
contribModbus:core:client Client -> broken Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +5ms
11 Feb 00:00:32 - [warn] [modbus-client:5c2c3186.30196] Client -> fsm broken state after failed Get More About It By Logging Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1
contribModbus:core:client Client -> activated Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +3ms
contribModbus:read Timed out +10s
11 Feb 00:00:32 - [error] [modbus-read:a16a70db.ede3f] Timed out
contribModbus:core:client Client -> activated Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +5ms
^C11 Feb 00:00:35 - [info] Stopping flows
contribModbus:core:client Client -> stop fsm on close Serial_9600_8_E_1 +3s
contribModbus:core:client Client -> stopped +2ms
11 Feb 00:00:35 - [warn] [modbus-client:Serial_9600_8_E_1] Client -> stopped state without reconnecting
contribModbus:core:client Client -> close node Serial_9600_8_E_1 +4ms
contribModbus:config:client close node Serial_9600_8_E_1 +0ms
contribModbus:core:client Client -> Connection closed simple Serial_9600_8_E_1 +2ms
contribModbus:core:client Client -> stop fsm on close 5c2c3186.30196 Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +4ms
contribModbus:core:client Client -> stopped Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +1ms
11 Feb 00:00:35 - [warn] [modbus-client:5c2c3186.30196] Client -> stopped state without reconnecting Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1
11 Feb 00:00:35 - [warn] [modbus-read:a16a70db.ede3f] Client -> resetIntervalToRead node a16a70db.ede3fundefined
contribModbus:core:client Client -> close node 5c2c3186.30196 Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +7ms
contribModbus:config:client close node 5c2c3186.30196 +14ms
11 Feb 00:00:35 - [warn] [modbus-read:a16a70db.ede3f] Client -> close node a16a70db.ede3fundefined
contribModbus:core:client Client -> Connection closed well 5c2c3186.30196 Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1 +24ms