Communication between AB Control Logix and Koyo PLC

Forrest

Member
Join Date
Dec 2009
Location
Vancouver
Posts
45
Hi,

I didn't use AB Control Logix before and I would like to know can AB Control Logix communicate with other PLC (we are now using Koyo PLC) thro' Modbus TCP/IP? I heard that we need put a 3rd party Modbus TCP module to Control Logix, is it true? Thanks
 
Last edited:
The standard solution to add Modbus/TCP functionality to ControlLogix is the MVI56E-MNET module from Prosoft Technology.

There are a handful of standalone protocol gateways also available on the market; the HMS AnyBus devices are my favorite.
 
Thanks Ken,

That's meant we can connect Control Logix with MVI56E-MNET module and another PLC with MODBUS TCP module by a LAN cable directly.
Is it correct?

The standard solution to add Modbus/TCP functionality to ControlLogix is the MVI56E-MNET module from Prosoft Technology.

There are a handful of standalone protocol gateways also available on the market; the HMS AnyBus devices are my favorite.
 
Usually there is an Ethernet switch involved, but you can choose to connect module-to-module using a "crossover" Ethernet cable.
 
Hi there, question again...

In our design, there are 2 chassis with AB controller for redundant purpose and 1 I/O chassis. Should I need to buy 2 MODBUS TCP/IP modules and install in controller chassis or just to buy 1 modules and install it in I/O chassis?

Thanks again
 
oh... I am so surprised that this module costs me over US$2,000... I think I need to try other method...

Hi there, question again...

In our design, there are 2 chassis with AB controller for redundant purpose and 1 I/O chassis. Should I need to buy 2 MODBUS TCP/IP modules and install in controller chassis or just to buy 1 modules and install it in I/O chassis?

Thanks again
 
The Prosoft modules are the "safe bet" because they will handle 99% of the functions you throw at them and have the widest installed base and support.

If your application is cost-sensitive, check out some of the other suggestions.

I am posting this followup to mention that you cannot put any modules other than ControlLogix CPUs, ControlNet and EtherNet/IP modules, and the Redundancy modules into a Redundancy chassis.

Because Prosoft modules use backplane I/O connections, they cannot be placed in the Redundancy chassis with the controllers; you would have to place them in a remote chassis connected over ControlNet.

Also consider this issue: if the Redundant controllers switch over, the 1756-ENBT or -EN2T EtherNet/IP modules swap IP addresses. Until your Ethernet switches refresh their MAC ID tables, all connections to the Ethernet modules will be broken. What effect will that have on your Modbus connectivity or a standalone gateway device ? If you can wait for a TCP timeout or for whatever time it takes for the switches to rebuild their tables, you're OK. If not, you should consider a solution that does not rely on constant TCP connectivity to the ControlLogix.
 

Similar Topics

Sometimes I want faster updates on my SCADA system. I've researched documentation from AB and found a few pointers but I also have a few questions...
Replies
8
Views
2,247
Hi, I am currently working on a project in which the target is to communicate the GE PLC E05 with Allen Bradley Control Logix over Modbus Serial...
Replies
7
Views
4,410
Hi guys, we have a XBTGK magellis OIT. We're trying to communicate it with control logix AB PLC. I am having a problem communicating and " PLC...
Replies
0
Views
2,770
HOW TO COMMUNICATE BETWEEN 2 ''EN2T'' MODULES MOUNTED ON THE SAME ALLEN BRADLEY CONTROLLOGIX CHASSIS. BUT TWO EN2T HAS DIFFERENT NETWORK. ONE EN2T...
Replies
7
Views
4,264
Hello, I need communication between PLC Control Logix with TDC - 3000 of honeywell, I want to use DH+ protocol, and I need know the devices...
Replies
5
Views
6,806
Back
Top Bottom