Redundant CLX Processors to TDC 3000

EY12

Member
Join Date
Mar 2008
Location
california
Posts
2
I would like to set up a redudnat CLX processor configuration using the redundancy module. I would like to integrate this system into an existing DH+ network using just one DHRIO card in one of the chassis. Can this be done? I have heard that the Honeywell can't communicate to a redundant processor configuratin via DH+.
 
EY12 said:
I would like to set up a redudnat CLX processor configuration using the redundancy module. I would like to integrate this system into an existing DH+ network using just one DHRIO card in one of the chassis. Can this be done? I have heard that the Honeywell can't communicate to a redundant processor configuratin via DH+.

If you put the DHRIO module in a non-redundant chassis, then I don't see why this wouldn't work. The biggest trouble you will most likely enounter is setting up the DHRIO routing table. This is necessary because the TDC3000 will not be able to configure multihopping to route to the processor.
 
What do you mean by routing table? Can the DHRIO card exist in one of the chassis which houses one of the processors?
 
There are several reasons why the method you describe will not work.

You cannot put a 1756-DHRIO module into a chassis along with a redundant ControlLogix controller. Only CPUs, Ethernet modules, ControlNet Modules, and System Redundancy Modules (SRMs) can reside in the controller chassis.

I cannot speak for Honeywell and the capability of your TDC3000 system (there is more than one "serial gateway" type device for TDC3000) but in my experience the SIO module can only perform "Local DF1" messaging. If a 1756-DHRIO is located outside the processor chassis, it cannot use a local message because the target of a Local Message must be a local slot.

In addition, if your DH+ network is principally used to interface with Honeywell TDC-3000, then it probably includes some 1770-KF2 or 1785-KE modules. In my experience, the 1756-DHRIO module can have some DH+ problems when only -KF2 or -KE modules are on the network with it. When PLC-5 or SLC-5/04 controllers are present, those problems do not occur.

My very strong recommendation for communicating with a redundant ControlLogix system from a TDC-3000 control system is to use a Prosoft MVI56 module in a remote chassis. The Modbus version (MVI56-MCMR especially) or the DF1 version (MVI56-DFCMR) can be used depending on which protocols are in place on the Honeywell side.
 

Similar Topics

Hi everybody, I have a CLX system with 2 redundant 1756-L71. Our customer requires two values: "CPU1_OK" and "CPU2_OK" to be sent via modbus...
Replies
0
Views
1,192
Hi Guys, Maybe you have some experience with this set-up and can give me some pointers. Project is to use an Emerson DCS to communicate (via...
Replies
3
Views
2,038
AB Gurus, I have a problem with RSLinx auto configuring nodes on the wrong driver. I have dual ethernet (2 ethernet networks completely separate...
Replies
2
Views
5,671
Hi guys, I'm sizing up a redundant CLX setup using 1757-SRM modules. 2 CPU, 2 SRM modules, 2 racks, 2 p/s. But I'm not sure if I should buy...
Replies
3
Views
2,529
Hi, Does anyone know if we can put a Prosoft Modbus module in the ControlLogix redundant CPU Chassis each? Will it cause any negative effect to...
Replies
2
Views
3,361
Back
Top Bottom