-
Notifications
You must be signed in to change notification settings - Fork 18
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
ads-client in a Docker #82
Comments
In my tests and experience, the 48898 TCP port is the only one that is required. It's important to understand that the 48898 is the port that the PLC/TwinCAT router is listening to. However the ads-client itself uses next available/random TCP port to connect from, unless set excplicitly to port with So if you set Hope this message makes any sense. |
Hi, Thanks for your Answer. This make sense, but it didn't work. Maybe it is different what the Interestingly, the node-red-contrib-ads node works without port forwarding (Nor 48898). The connection is established as soon as the route is entered on the PLC. |
Interesting. What happens if you set localAdsPort and localAddress empty? Of course these are totally different libraries. Could you share all the settings from both? |
Sorry.. I mean localTcpPort, not ads port. The ADS port is required as you are using Raspberry Pi without AMS router. |
So both localAddress and localTcpPort are now empty?` EADDRNOTAVAIL means that it can't start a connection from local interface 10.1.47.50. |
if both are empty, it seems to work! Maybe, docker has a problem when localAddress is set, because of every container has it own ip.. ? Maybe you can add this in your description..? |
Glad to hear! :) The localAddress can be empty almost always. Only reason I can image is that you have many interfaces (like ethernet, wifi, etc) and you need to provide manually which one to use. So the problem indeed was that it tried to connect using 10.1.47.50 however the was no such interface in your docker container. I'll see if I could add this info somewhere in FAQ! |
Hi
I have a problem when running Node-RED in a docker.
Communication then only works if I run the container with --network host . In other words, the entire host network into the container route.
https://docs.docker.com/network/network-tutorial-host/
Since this isn't the goal of Docker, I'm wondering what ports I need to route for the configuration to work.
Raspberry Pi 4 with docker container
CX9020 TwinCAT 2.11 Runtime
I have already tried the following ports:
The text was updated successfully, but these errors were encountered: