AB Remote I/O

D

Thread Starter

dmar

I'm considering adding I/O from existing SLCs to nearby motor control panels to add sequenced starting and other rather simple automation features. Will probably use SLC parts I have on hand, or maybe Flex I/O or Point I/O.

I encountered RIO on a large scale in a previous plant and was impressed with its reliability, which is an important factor here.

Is RIO still a viable choice for high reliability, low node count device level networking, or is it on its way out?

Would you go this route in my circumstance, or opt for Ethernet/IP, DeviceNet, or something else?
 
B

Bob Peterson

RIO is the easiest way to handle it with SLCs, but only works with the rack style SLCs (5/03 thru 5/05).

Devicenet can be made to work with one of the micrologix units (1500 I
think).

There are no AB Ethernet/IP options available for remote I/O for any of the SLCs. I have read somewhere that Opto22 has Ehernet/IP I/O that will work on 5/05s.

If you have a 5/05, I suggest considering the use of micrologix 1100s and 1400s as remote I/O drops. It is the most cost effective option, and gives you a certain amount of redundancy in control.
 
G

Gerald Beaudoin

Have you considered adding a second I/O rack to the existing one? Could be an option if the main rack is full. Hard to beat the reliability of "in rack" I/O.
 
J

James Ingraham

<i>Is RIO still a viable choice for high reliability, low node count device level networking, or is it on its way out?</i>

It all depends. RIO is certainly on it's way out. I wouldn't start a greenfield project with RIO. But you're not in a greenfield scenario. There's nothing wrong with using RIO in a situation like this. Flex has the advantage that you could later switch the comm module to EtherNet/IP as an upgrade path.

-James Ingraham
Sage Automation, Inc.
 
B

bob peterson

RIO is about as reliable an I/O bus as it gets. I would not be real worried about it.

I suspect the OP has discovered a sad fact of automation. That fact being that the cost of running all the conduit for hard wiring this kind of stuff often far exceeds the cost of the added I/O. It is a lot easier to get a blue hose run then a bunch of wires. Often the blue hose can just be tie wrapped to the building structure or existing conduits.

--
Bob
 
E

Eddie Willers

RIO is a very solid network, especially with the PLC-5 scanner channels and the 1747-SN. I imagine RA will continue to produce it for as long as PLC-5 controllers are around; probably another 10 years.

FLEX is probably the best option for you because of the robust AC and relay Output modules available, and because you can change to EtherNet/IP later. The three DIP switch banks can be tricky to configure but if there's a diagram in the cabinet anyone can follow it for reconfiguration.

The 1771 and 1747 style rack adapters will be around forever. There are no adapters for 1756 or 1734 (POINT) for the RIO protocol.

There is a set of 1791R CompactBlock modules for RIO, if you needed a smaller point count in 24V DC.
 
RE:

> The 1771 and 1747 style rack adapters will be around forever. There are no
> adapters for 1756 or 1734 (POINT) for the RIO protocol.

What about the 1756-DHRIO - have used this to connect a CLogix CPU to an existing 1771 I/O rack.
 
E

Eddie Willers

The 1756-DHRIO is a scanner module only, but the newer 1756-RIO module has Scanner, Adapter, and Listener modes.

The 1756-RIO requires a Logix CPU; the Adapter mode does not itself control a rack of I/O like the 1771-ASB or 1747-ASB modules do.

A little company in Florida called Quest Technical Solutions (www.QTSUSA.com) makes some good standalone RIO products for connectivity to other networks; their RIO standalone box is the basis for the A-B 1756-RIO.
 
Top