Hi all, I guess we‘ll have to think a bit about the ADS protocol. So-far we have been connecting to the PLC using ADS, but I have just recently learnt that we can actually do a lot more.
For example, the thing with the AmsNetId, where we simply add “.1.1” to the IP. I can also reach the TwinCAT master that is attached to my PLC by connecting to the same IP, but using the AmsNetId “.3.1” at the end. Also did I notice that what we do with: reading out the symbol tables and the datatypes only seems to work with the PLC instance. If I connect to the Device Manager for reading out telemetry, this doesn’t work. Also don’t the multi-item-requests work. Now I’m experimenting with reading data from some IO cards, that are attached to my PLC via EtherCat adapter. I really should find out how to detect which features work and to add fallback layers (Like switching from Multi-Item-Requests to Single-Item-Requests if that’s not supported). But really interesting stuff you can theoretically do with our driver in it’s current state. Chris
