harryting
Lifetime Supporting Member
Ok, you guys/girls, you are my last hope as I already tried their tech support who are probably correct on this matter but someone here might be more versed in Ethernet/IP.
Background:
I'm trying to passing data between two segregated Ethernet/IP networks with Contrologix and I settled on using a Anybus Ethernet/IP Slave to Ethernet/IP Slave gateway. I worked with Prosoft stuff before but they don't make such a gateway so I opted for the Anybus device instead. Like other such devices I encountered before, the documentation is... well, written by engineers.
After piecing together the documentation, it appears there's no way to have more than one PLC writing to the Gateway without overwriting the other PLC unlike the Prosoft product where one can do CIP Data Table Write to only certain block of register. Sure, I can MSG to concentrate data all in one PLC than write to the gateway but I prefer to keep data hops to a minimal if all possible.
more detail, the instruction show the MSG setup as "CIP Generic", Service type-Set Attribute Single, Service code-10, Instance-150, Class-4, Attribute-3. No mention of PLC5 Table Write or CIP Table Write are supported.
Any ideas? Like I said, I can go around this problem but I rather not make it more complicated than necessary.
Background:
I'm trying to passing data between two segregated Ethernet/IP networks with Contrologix and I settled on using a Anybus Ethernet/IP Slave to Ethernet/IP Slave gateway. I worked with Prosoft stuff before but they don't make such a gateway so I opted for the Anybus device instead. Like other such devices I encountered before, the documentation is... well, written by engineers.
After piecing together the documentation, it appears there's no way to have more than one PLC writing to the Gateway without overwriting the other PLC unlike the Prosoft product where one can do CIP Data Table Write to only certain block of register. Sure, I can MSG to concentrate data all in one PLC than write to the gateway but I prefer to keep data hops to a minimal if all possible.
more detail, the instruction show the MSG setup as "CIP Generic", Service type-Set Attribute Single, Service code-10, Instance-150, Class-4, Attribute-3. No mention of PLC5 Table Write or CIP Table Write are supported.
Any ideas? Like I said, I can go around this problem but I rather not make it more complicated than necessary.