I have a bug using Enterprise IIoT Gateway, I have some Predictive Maintenance Sensors, the communication of these sensors fails very often, sometimes the sensors do not communicate or stay in FLY state, I have tried to Restart Node-Red but it does not work.
Using Node-Red with @ncd-io/node-red-enterprise-sensors, the pre-installed library, sometimes I get an error from the Wireless Gateway node, this is the error:
{"code":1, "description": "Wireless module is not responding"}
Also, I read from Node-Red the /dev folder to find the ttymxc files, which is the dev to use the default wireless gateway on the IIoT Gateway and sometimes it just reads:
Additionally I would check the Configuration nodes menu to ensure you don’t have duplicate communication interfaces configured. Commonly caused by Importing flows.
Check the menu in the top right (three horizontal lines) > Configuration Nodes > ncd-gateway-config. You should only have one serial port going to /dev/ttymxc2
Everything looks correct to me. I would try deleting the Wireless Gateway and sensor nodes, then also the ncd-gateway-config node and try creating them again. You can reference your screen shot here to setup the new Wireless Gateway node.
For what it’s worth these Enterprise Gateways have been very reliable and I have not seen the Wireless Gateway nodes ever fail to connect.
Also the node red will say “FLY” till sensor sends its next packet and the next packet will come after every 5, 10 or 15 min based on the set interval values.
I see this node state behavior. In the first tests, I saw that the sensor went to “FLY” state, 5 minutes later, it went to “Running” state, but now they only stay in “FLY” state, this tells me that the sensors can communicate with the Gateway, but only for one time and the Gateway does not receive more data.
This can happen to me with one sensor but there are other sensors that do have the normal behavior and the Gateway receives data correctly.
I run the command “pm2 restart all” from Node-red but I keep seeing the error “Wireless module did not respond” from the Wireless Gateway node over and over again
Yes, I have the OTF configured
The sensors send data every 5 minutes, which is how I have configured it.
The IDs start at 1, and the delay is 300 on each sensor.
I have finally tried it, but the behavior is still the same.
This past week we tried connecting an ethernet modem to the Enterprise Gateway and disabling in Node-RED the built-in modem and all sensors communicate perfectly without losing data.
Testing with the Enterprise’s built-in modem some sensors do not communicate at all while others do communicate correctly.
I’m going to share with you all the sensor configuration, maybe that will help.
Hello, @Bhaskar
I have time this thursday or friday for a meeting. We really want to know what the problem is with this Gateway, so let me know if you have time for a meeting
Hi, @jacob@Bhaskar, bad news
I let you know that 5 minutes after the end of the meeting, the serial modem has failed.
I share some screenshots from the debug window