![]() Is there any chance we’ll get a bug fix soon? A project I’m working on needs this library, and the whole program crashes due to this bug. Started Node-RED graphical event wiring tool.Įverything from the Raspbian installation to this palette has been freshly installed. Stopped Node-RED graphical event wiring tool. rvice: Scheduled restart job, restart counter is at 1. rvice: Main process exited, code=exited, status=1/FAILURE Raspberry Pi Zero W (Raspbian Lite 32-bit )Ģ7 Jul 22:32:35 - Server now running at Ģ7 Jul 22:32:35 - Encrypted credentials not foundĢ7 Jul 22:36:11 - Installing module: node-red-contrib-modbus, version: 5.21.2Ģ7 Jul 22:39:35 - Installed module: node-red-contrib-modbusĢ7 Jul 22:39:39 - Added node types:Ģ7 Jul 22:39:39 - node-red-contrib-modbus:modbus-clientĢ7 Jul 22:39:39 - node-red-contrib-modbus:modbus-responseĢ7 Jul 22:39:39 - node-red-contrib-modbus:modbus-readĢ7 Jul 22:39:39 - node-red-contrib-modbus:modbus-getterĢ7 Jul 22:39:39 - node-red-contrib-modbus:modbus-flex-getterĢ7 Jul 22:39:39 - node-red-contrib-modbus:modbus-writeĢ7 Jul 22:39:39 - node-red-contrib-modbus:modbus-flex-writeĢ7 Jul 22:39:39 - node-red-contrib-modbus:modbus-serverĢ7 Jul 22:39:39 - node-red-contrib-modbus:modbus-flex-serverĢ7 Jul 22:39:39 - node-red-contrib-modbus:modbus-queue-infoĢ7 Jul 22:39:39 - node-red-contrib-modbus:modbus-flex-connectorĢ7 Jul 22:39:39 - node-red-contrib-modbus:modbus-io-configĢ7 Jul 22:39:39 - node-red-contrib-modbus:modbus-response-filterĢ7 Jul 22:39:39 - node-red-contrib-modbus:modbus-flex-sequencerĢ7 Jul 22:44:25 - Installing module: node-red-contrib-modbus-tcp-ip, version: 1.1.5Ģ7 Jul 22:45:02 - Installed module: node-red-contrib-modbus-tcp-ipĢ7 Jul 22:45:02 - Added node types:Ģ7 Jul 22:45:02 - node-red-contrib-modbus-tcp-ip:modbus-tcp-ipĢ7 Jul 22:45:02 - Installing module: node-red-contrib-modbustcp, version: 1.2.3Ģ7 Jul 22:45:45 - Installed module: node-red-contrib-modbustcpĢ7 Jul 22:45:46 - Added node types:Ģ7 Jul 22:45:46 - node-red-contrib-modbustcp:modbustcp-serverĢ7 Jul 22:45:46 - node-red-contrib-modbustcp:modbustcp-writeĢ7 Jul 22:45:46 - node-red-contrib-modbustcp:modbustcp-readĢ7 Jul 22:47:45 - Uncaught Exception:Ģ7 Jul 22:47:45 - Error: listen EADDRNOTAVAIL: address not available 192.168.100.12:10502Īt tupListenHandle (net.js:1314:21)Īt processTicksAndRejections (internal/process/task_queues.js:83:21) It’s been 2 years and the same bug is present. Vendor : Calta Computer Systems Limited.The node-modbus package is just for the Modbus Server node.ĭescription of the connecting Modbus system: Yes, modbus-serial is the name but it does all, TCP and Serial. ( ) I have installed modbus-serial as a global package (using npm i -g).( ) I have installed modbus-serial package global from source (using git clone).(x) I am using just the Node-RED package and got modbus-serial package installed with it.Start / Stop the connection from remote device.Start a Modbus Request from another device.Minimal reproduction of the problem with instructions ( ) unexpected behavior => please visit the Wiki beforeĪfter a lost connection from Modbus master, the Modbus Server node shows an error that makes Node-Red to forced stop.Īfter a lost connection from Modbus master, the Modbus Server must show the connection error but Node-Red should remain active.(x) bug report => please search github for a similar issue or PR and test Modbus problems with the modbus-serial package before submitting.I’m submitting a … (check one with “x”) Problem
0 Comments
Leave a Reply. |