i have set up a Project, that have around 350 ads nodes. (ADS Notification and ADS Outputs). -->i mean, thats under the Limit of the readme..
When i restart the PLC, everything is ok. But from the 1st or 2nd Deploy in Node-RED i have following Errors: (@every Deploy and peridically)
"Ads Register Notification timeout".
Sometimes followed by:
"Ads write timeout" and / or "This socket has been ended by the other party"
I have tried to set the timeout in the ads config node to 2000ms with the same result.
Node-RED: v1.0.3
Nodejs: 11.9.0
ADS: 1.1.22
My Node-RED is Running in a Docker Container on a Raspberry Pi and the PLC is Running on a CX5120 in the same Network.
It seems as the connection doesn't close correctly or something like that. Do you have an idea what can be wrong?
Hi there
I have following problem:
i have set up a Project, that have around 350 ads nodes. (ADS Notification and ADS Outputs). -->i mean, thats under the Limit of the readme..
When i restart the PLC, everything is ok. But from the 1st or 2nd Deploy in Node-RED i have following Errors: (@every Deploy and peridically)
"Ads Register Notification timeout". Sometimes followed by: "Ads write timeout" and / or "This socket has been ended by the other party" I have tried to set the timeout in the ads config node to 2000ms with the same result.
Node-RED: v1.0.3 Nodejs: 11.9.0 ADS: 1.1.22
My Node-RED is Running in a Docker Container on a Raspberry Pi and the PLC is Running on a CX5120 in the same Network.
It seems as the connection doesn't close correctly or something like that. Do you have an idea what can be wrong?
--> You can see here the start discussion: https://github.com/PLCHome/node-red-contrib-ads/issues/25#issue-578014758
maybe, you can fix that problem in the api..?