Welcome to our new forum
All users of the legacy CODESYS Forums, please create a new account at account.codesys.com. But make sure to use the same E-Mail address as in the old Forum. Then your posts will be matched.
Close
With Codesys V3.5.15 and the latest V3.5.16.1 there is a problem with the Ethernet/IP implementation.
I have a device that is installed via EDS and has three Input assemblies 100, 101 and 102. There are 3 possible connections to each of these assemblies preconfigured in the EDS, "Listen only", "Input only" and "Exclusive Owner".
I am using an Allen Bradley scanner to realize the Exclusive Owner connections and configured three Listen Only connections (one for each assembly) in Codesys. This results in Codesys opening and closing connections with equal connection IDs, generally very weird behavior on the bus and in the end it will take the data of one connection and use it for all three.
I also tried this with Codesys V3.5.14 where it worked as expected!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is more of a bug report.
With Codesys V3.5.15 and the latest V3.5.16.1 there is a problem with the Ethernet/IP implementation.
I have a device that is installed via EDS and has three Input assemblies 100, 101 and 102. There are 3 possible connections to each of these assemblies preconfigured in the EDS, "Listen only", "Input only" and "Exclusive Owner".
I am using an Allen Bradley scanner to realize the Exclusive Owner connections and configured three Listen Only connections (one for each assembly) in Codesys. This results in Codesys opening and closing connections with equal connection IDs, generally very weird behavior on the bus and in the end it will take the data of one connection and use it for all three.
I also tried this with Codesys V3.5.14 where it worked as expected!