-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TCP ECCONRESET #129
Comments
Debug output:
|
Obs.: I want to read just one time and one address and close connection |
Hi carolina `var nodes7 = require('nodes7'); // This is the package name, if the repository is cloned you may need to require 'nodeS7' with uppercase S var variables = { conn.initiateConnection({ port: 102, host: '192.168.0.1', rack: 0, slot: 1, debug: false }, connected); function connected(err) { function valuesReady(anythingBad, values) { |
Hi minhbonghot, thanks for your reply! When I use the external module 'process.exit()' inside node-red, apparently the process it ends is the execution of node-red itself, so this solution doesn't work for me... If I could just disable reconnection maybe the problem would be solved, I don't know. |
Hi Ana, can you please change this to turn more debugging output on and then post the output again:
to
I don't have node red set up right now so I edited your code to look like this in index.js and I ran it standalone, and it disconnects from the PLC and reconnects properly:
|
Hi Ana, another thing I was going to mention: There are a couple of projects that implement nodes7 within node-red already: Would these help? |
Hey! So, I managed to make it work for a while, I tested it for 3 days in a row to do consecutive readings from a PLC, however after a while the reading stopped working and I started receiving ECCONRESET again, this time without reading... I believe that the problem is not the PLC because I monitored direct readings by MODBUS/TCP and they worked during these 3 days... New debug output:
The reading process only works again when I restart my Raspberry Pi. I started the readings at: 2022-10-07T15:15:06.9640000-03:00 And about the nodes for Node-RED, I tested them but they do not allow me to dynamically change the Host IP and Port as I do in this code. Is there any connection limit? Because it seems to me that it works for 2 days then it stops working as if it has reached a limit. Anyway, thanks for the help, I'll keep researching and trying to fix this. I'm still open to suggestions! |
Output after restarting Raspberry Pi:
Now it's working again, but I can't say for how long. |
@anacarolina-ms can you please check open TCP connections between the Pi and PLC using netstat on the Raspberry Pi or by looking at the active connection information in TIA Portal or the PLC web page, if enabled? I set up a similar flow (I pasted the flow posted by @liulysk in issue #130 and it has run for a few hours talking to an S7-1200 and so far seems to release all connections. |
Hi @plcpeople thanks for your help! Sending the outputs of netstat from my Raspberry Pi above. netstat:
netstat -st #TCP:
|
Hey! I'm working with your node on node-red for reading from a plc S7-1200, rack 0 and slot 1 with external functions. But every time I send a readAllItems I get the response I want but the connection resets every time and never closes, even with dropConnection and connectionCleanup... I've been trying to solve it for a few days now, if anyone has any ideas...
The text was updated successfully, but these errors were encountered: