How does this work? about ads-async

[klauer]

I assume you're running just ads-async get plc_name_here Global_Variables.bBlink? I didn't see it in your output.

ADS itself can be a bit finicky. My guess is that the PLC is forcefully closing the connection prior to the request going through.

Here are a couple relevant limitations you might not be aware of:

• The main limitation is that there can't be two TCP connections to the same PLC from the same host. That is to say, if you have TwinCAT XAE talking to your PLC, ads-async won't be able to talk to it effectively. Similarly, you couldn't run two ads-async monitor processes in separate terminals on the same host; the PLC would only accept one.
• You need to have a route added to the PLC for the specific machine - otherwise the PLC won't accept your requests. Assuming you already added a route through the IDE, this shouldn't be the problem here. However, ads-async also offers the ability to add a route for you with a few additional command-line arguments (see ads-async get --help arguments --add-route, --our-net-id, and --our-host. From a Windows perspective, it may seem unnecessary to require those arguments, but remember that ads-async will run on Linux and macOS as well)

If neither of those applies, then you may have run into a "real" bug (at least something that ads-async could solve on its own). If you could provide even redacted debug log output, it could help resolve it. (ads-async --log DEBUG get plc_name ...)

[EricControls]

I am working locally on my engineering environment.
ads-async get localhost Global_Varibles.bBlink

I will attempt again as soon as I'm around hardware.

Thanks so much for your respond!