-
-
Notifications
You must be signed in to change notification settings - Fork 109
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
Probing for Tags #43
Comments
Nope. Like every other part of the protocol, we'd need to sniff the activity using Wireshark, and then reverse-engineer the protocol elements used. Not documented, in any of the thousands of pages of documentation that I've read. |
It turns out that AB does document this. In their own "special" way. I got this from a user of my library and I thought I would pass along the joy for the season: Logix5000 Data Access Programming Manual Have fun. I love that the tag instance numbers come back in 32-bit quantities, but you can only use 16-bit instance IDs when requesting the next batch. |
Attribute 7 gives the size of one element and attribute 8 gives the array dimensions (all 3 at once each as a u32). |
Thanks for that! I'll have a look. Pull requests accepted!! |
Hi,
Is there any facility available like probing in which we can query for tags from the PLC directly to get to know which are the tags configured?
The text was updated successfully, but these errors were encountered: