rstrouse
commented
2 years ago I have had this problem with socat in the past. Unfortunately, it is related to the adapter not opening up with the proper settings from socat. Here is my pm2 startup. Notice I hav added all the baud rate settings but it doesn't always restart appropriately. The funny part is that I created a small bit of code that opens the port locally at 9600 8N1 then closes it and it works every time.
The solution below is still being tested and I have a completely different adapter. In your python program are you connecting via the python serial interface. If you are then perhaps sharing your connection code may shed some light on how to get the remote adapter to open with the correct settings.
module.exports = {
apps : [{
name: 'socat',
cwd: '/usr/bin',
script: 'socat',
args: 'TCP-LISTEN:9801,fork,reuseaddr FILE:/dev/ttyUSB0,b9600,ispeed=9600,ospeed=9600,raw',
autorestart: false,
restart_delay: 10000,
watch: true,
ignore_watch: ['data', 'config.json', 'node_modules', 'logs', 'dist', 'cache'],
listen_timeout: 60000
}],
deploy : {
production : {
user : 'SSH_USERNAME',
host : 'SSH_HOSTMACHINE',
ref : 'origin/master',
repo : 'GIT_REPOSITORY',
path : 'DESTINATION_PATH',
'pre-deploy-local': '',
'post-deploy' : 'npm install && pm2 reload ecosystem.config.js --env production',
'pre-setup': ''
}
}
};
jwtaylor310
mguinness
tagyoureit
Describe the bug After a temporary (1 minute or more) loss of RS485 connectivity, commands sent from dashPanel fail. Restarting the poolController program fixes the problem.
To Reproduce Steps to reproduce the behavior: Disable RS485 connectivity for approximately 1 minute. For testing, I am able to force the error by power cycling the network switch that connects the Pi running the programs and the Elfin RS485 adapter.
Expected behavior Clicking on a Feature "button" should cause the feature to turn on/off. After the RS485 disruption, doing this causes the indicator 'light' to turn yellow for a few seconds and then revert to its previous state. The poolController console log shows the command was sent but no action results.
Screenshots If applicable, add screenshots to help explain your problem.
Packet Capture replay.zip
Pool Equipment
Desktop (please complete the following information):
Additional context I have been experiencing intermittent command failures after the system has been running for several days. The only solution I have found has been restarting the poolController. I recently found that I can force the error by power cycling the network switch that the RS485 adapter uses to communicate with the Pi that is running the pool programs. Once the switch is power cycled, Feature on/off commands no longer work. I have an earlier Python program that communicates through the same network switch and it is able to successfully send commands after the power cycle. The poolController console display shows an apparently successful ECONNRESET which does not fix the problem. While the system is in the fail mode it still displays the pool status correctly, showing updates resulting from commands entered on the EasyTouch wireless or on the OCP.
Here is an annotated copy of the poolController console display showing the problem. Manual annotations are in Italics:
Init state for Pool Controller [10/17/2021, 8:19:42 AM] info: The current git branch output is master [10/17/2021, 8:19:42 AM] info: The current git commit output is ab95b2243e75d84cf730af38419e75cae7668209 [10/17/2021, 8:19:42 AM] info: Starting up SSDP server [10/17/2021, 8:19:42 AM] info: Checking njsPC versions... [10/17/2021, 8:19:42 AM] info: Starting Pool System easytouch [10/17/2021, 8:19:42 AM] info: Server is now listening on 0.0.0.0:4200 [10/17/2021, 8:19:42 AM] info: Net connect (socat) connected to: 172.16.31.242:8899 [10/17/2021, 8:19:42 AM] info: Net connect (socat) Connection connected [10/17/2021, 8:19:42 AM] info: Net connect (socat) ready and communicating: 172.16.31.242:8899 [10/17/2021, 8:19:43 AM] info: Auto-backup initialized Last Backup: 2021-10-16T23:23:21.532-0400 Next Backup: 2021-10-17T11:23:21.532-0400 [10/17/2021, 8:19:43 AM] info: New socket client connected lhRWFQBiD5jEGWbUAAAB -- 192.168.80.55 [10/17/2021, 8:19:43 AM] info: [8:19:43 AM] 192.168.80.55 GET /state/all?null {} [10/17/2021, 8:19:43 AM] info: New socket client connected wqfub2-xKf-sfIXVAAAD -- 192.168.80.55 [10/17/2021, 8:19:43 AM] info: [8:19:43 AM] 192.168.80.55 GET /state/all?null {} Pentair EasyTouch System Detected! [10/17/2021, 8:19:44 AM] info: Found Controller Board EasyTouch2 8 [10/17/2021, 8:19:44 AM] info: Requesting easytouch configuration [10/17/2021, 8:19:45 AM] info: New socket client connected kOpFvp-zS5Qo2qJMAAAF -- 172.16.31.151 [10/17/2021, 8:19:45 AM] info: [8:19:45 AM] 172.16.31.151 GET /state/all?null {} sendRS485PortStats set to false [10/17/2021, 8:19:54 AM] info: New socket client connected 0ec3sapjgsHuuQKxAAAH -- 192.168.80.55 [10/17/2021, 8:19:54 AM] info: [8:19:54 AM] 192.168.80.55 GET /state/all?null {} RS485 Stats:{ "bytesReceived": 1465 "success": 48, "failed": 1, "bytesSent": 468, "collisions": 0, "failureRate": 2.04% } RS485 Stats:{ "bytesReceived": 1692 "success": 56, "failed": 2, "bytesSent": 540, "collisions": 0, "failureRate": 3.45% } [10/17/2021, 8:20:02 AM] info: EasyTouch system config complete. [10/17/2021, 8:20:02 AM] info: Initializing Nixie Controller [10/17/2021, 8:20:02 AM] info: Nixie Controller Initialized [10/17/2021, 8:20:02 AM] info: [8:20:02 AM] 192.168.80.55 GET /state/all?null {} [10/17/2021, 8:20:02 AM] info: New socket client connected utMk3yfS5f4U9V1AAAJ -- 192.168.80.55 [10/17/2021, 8:20:02 AM] info: [8:20:02 AM] 192.168.80.55 GET /state/all?null {} [10/17/2021, 8:20:03 AM] info: Last auto-backup 2021-10-16T23:23:21.532-0400 Next auto - backup 2021-10-17T11:23:21.532-0400 08:21:00 Network Switch Disabled 08:23:00 Network Switch Enabled 08:24:52 “HP ENABLED” circuit commanded on [10/17/2021, 8:24:52 AM] info: [8:24:52 AM] 192.168.80.55 PUT /state/circuit/setState {"id":9,"state":true} FAILED [10/17/2021, 8:24:52 AM] error: Net connect (socat) Connection: Error: read ECONNRESET. Retry in 10 seconds [10/17/2021, 8:24:52 AM] info: Net connect (socat) closed due to error: 172.16.31.242:8899 [10/17/2021, 8:25:02 AM] info: Net connect (socat) connected to: 172.16.31.242:8899 [10/17/2021, 8:25:02 AM] info: Net connect (socat) Connection connected [10/17/2021, 8:25:02 AM] info: Net connect (socat) ready and communicating: 172.16.31.242:8899 08:27:00 “HP ENABLED” circuit commanded on [10/17/2021, 8:27:00 AM] info: [8:27:00 AM] 192.168.80.55 PUT /state/circuit/setState {"id":9,"state":true} FAILED 08:29:00 “HP ENABLED” circuit commanded on [10/17/2021, 8:29:00 AM] info: [8:29:00 AM] 192.168.80.55 PUT /state/circuit/setState {"id":9,"state":true} FAILED _