A puzzler...
Scenario -
1 "Master" ControlLogix L73, and 7 "Slave" ControlLogix L61 - all Version 19.
All chassis interconnected via a "Ring" network using 1756-EN2TR modules, rev. 4
Also there is an "IP" network to all chassis, using 1756-EN2T modules, rev. 4, connected via SixNet managed switches - "out-of-the-box" configuration.
Produced/Consumed tags, going both directions, (i.e. master to slave, and slave to master), have been configured.
The producer tags are configured each for 2 consumers, and these are consumed into separate tags in the consuming PLC via the "Ring" network, and the IP network.
The idea is that the IP tags are a redundant backup for the Ring network tags, the Ring only having single point failure protection.
We cannot get the IP tags to work, even though the setup has been checked, double-checked, and checked again. The "Ring" connected tags work correctly.
Specifically we get error 16#0203 "Connection Timed Out" on the processors in the IP branches of the I/O configurations in all projects.
This error indicates the connection is established, but the data transfer did not complete (it depends where you read about the error code).
However, I have added the member "Connection_Status" to the tag UDTs, and we are seeing that the connection is not established.
We do not have a problem with the number of connections, well within capabilities.
All tags are set to "Multicast", since this is a redundancy system, with 2 "Master" PLCs, Unicast is not allowed in redundancy systems, as it disqualifies the redundant chassis.
The Sixnet switches all have IGMP enabled (default).
This must be a simple thing to fix, but we have not got anywhere.
Can anyone shed any light on where the problem might be, as RA tell me this configuration should work.
Scenario -
1 "Master" ControlLogix L73, and 7 "Slave" ControlLogix L61 - all Version 19.
All chassis interconnected via a "Ring" network using 1756-EN2TR modules, rev. 4
Also there is an "IP" network to all chassis, using 1756-EN2T modules, rev. 4, connected via SixNet managed switches - "out-of-the-box" configuration.
Produced/Consumed tags, going both directions, (i.e. master to slave, and slave to master), have been configured.
The producer tags are configured each for 2 consumers, and these are consumed into separate tags in the consuming PLC via the "Ring" network, and the IP network.
The idea is that the IP tags are a redundant backup for the Ring network tags, the Ring only having single point failure protection.
We cannot get the IP tags to work, even though the setup has been checked, double-checked, and checked again. The "Ring" connected tags work correctly.
Specifically we get error 16#0203 "Connection Timed Out" on the processors in the IP branches of the I/O configurations in all projects.
This error indicates the connection is established, but the data transfer did not complete (it depends where you read about the error code).
However, I have added the member "Connection_Status" to the tag UDTs, and we are seeing that the connection is not established.
We do not have a problem with the number of connections, well within capabilities.
All tags are set to "Multicast", since this is a redundancy system, with 2 "Master" PLCs, Unicast is not allowed in redundancy systems, as it disqualifies the redundant chassis.
The Sixnet switches all have IGMP enabled (default).
This must be a simple thing to fix, but we have not got anywhere.
Can anyone shed any light on where the problem might be, as RA tell me this configuration should work.