Closed karyuv closed 8 years ago
Interesting. If two computers try to read, and only one computer at a time can, then perhaps there are limits on the number of "Unconnected" EtherNet/IP CIP connections that the PLC can support? If it supports only one, then that might explain the issue.
It looks like you are only temporarily setting up the EtherNet/IP CIP connection, performing the read, and then tearing it down. If the "unconnected" connections are rate-limited by the PLC, then that might explain the issue.
If you could increase the logging level and collect the error response from the failing connection, then we could diagnose exactly the error code being returned by the PLC.
In general, I would recommend establishing the EtherNet/IP CIP connection, and retaining it for a longer duration, even if you only issue requests intermittently. There is significant overhead in establishing the connection. You'll need to re-arrange your code to drop the connection and re-establish it whenever you time out a request, though.
Hello Sir, Your advise helped. I modified to connect only once but read iteratively. I was able to read the same tag from two different computers and no problems in that. Thank you!.
Hello, I am trying to read a tag on a Allen Bradley PLC. I was able to read the tags from Linux PC and there was no issue with that.
An other computer, tried to read the same tag and which made the other computer not being able to read it and vice versa.
This the snippet of the code, I am using on both of these computers.
please share your thoughts on this.