-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
Please add guidance on how to connect from TwinCAT XAE #2
Comments
Hi! Can you please explain me your use case? Do you want to connect the software to the twincat engineering? |
I have TwinCAT Engineering (XAE) installed on Windows 10, and am using it to write my PLC code. I would like to run that PLC code on the softBeckhoff PLC running in docker on the same machine. The "Broadcast Search" option in the Add Route Dialog in XAE does not find the softBeckhoff. I don't know what route to add manually to my TwinCAT Engineering environment, nor how to add the route from the softBeckhoff back. If I manually enter route information (e.g. IP Address=127.0.0.1, AmsNetId=192.168.1.20.1.1, Transport=TCP_IP), it asks for Remote credentials (Username/Password) which I don't know. |
Hi! Basically you just have to setup a route on your machine (unidirectional). Otherwise the SoftBeckhoff is will not be able to run your code or act like a PLC you can program 😢 . |
Thanks, but I'm having a few problems with this.
|
Hi!
In you case I would try to start the software from source, so you can use your local router server an all you local routes. |
Hi, Thank you for your advice, but I'm afraid I still can't get this to work on my setup. For now I'm going to use the Beckhoff XAR on a VMWare VM, but I may come back to this in the future. |
I have started the docker container, and can connect to the swagger API using a web browser, but I don't know how to add a route to the softBeckhoff PLC.
Please add some guidance on what value to put into the routing, and/or if routes need to be set up on the softBeckhoff via the API.
The text was updated successfully, but these errors were encountered: