Addressing AB SLC500

[keklon]

Hello all,
How can I address an Allen Bradley IO (SLC500) with Direct logic or Do More PLC? I am planning to replace an obsolete AB SLC 5/05 with a DL or DM PLC but wish to use the 3 local IO racks as time allows. Is this doable? It will also keep downtime to a minimum.

[franji1]

Do-more is much newer than DirectLogic.

Do-more (BRX) supports these A/B supported protocols: EtherNet/IP, Modbus/TCP, Modbus/RTU.

However, I do not know which of these are supported by your specific PLC, the SLC500.

[keklon]

The PLC is the 5/05 Cat. 1747-L551 which I will remove. I would like to address the AB racks filled with the existing digital IO. I will plan on replacing the Analog card to the suited Do More replacement. Can I address the AB Digital IO Modules with a Do More PLC if I install a RS232 com port?

[franji1]

The PLC is the 5/05 Cat. 1747-L551 which I will remove. I would like to address the AB racks filled with the existing digital IO. I will plan on replacing the Analog card to the suited Do More replacement. Can I address the AB Digital IO Modules with a Do More PLC if I install a RS232 com port?

Does it support Modbus/RTU?

[keklon]

The reason I wish to install the alternative PLC is due to the obsolete state of the 5/05 controller. I don't have RS Logix to support the system and the only reasonable option I see is to replace the controller with a cost-effective alternative. I wish to mitigate the down time by using some of the existing hardware.
Years ago, I came across an application where a Koyo PLC was connected to old TI sequencer IO modules thru a serial connection. Bypassing the TI sequencer. This is what gave me the idea. Is there anything available to adapt the AB Rack & IO modules to a BRX controller?

[franji1]

Is there anything available to adapt the AB Rack & IO modules to a BRX controller?

What communication protocols do your AB I/O racks support?  This is an A/B product question.

[keklon]

According to the AB Documentation "The SLC 500 family features communications
modules and devices which provide support for different networks, including
EtherNet/IP,
ControlNet, DeviceNet, DH+, DH-485, Universal Remote I/O and serial networks"
Is there a more specific specification I should be looking for?

[franji1]

According to the AB Documentation "The SLC 500 family features communications
modules and devices which provide support for different networks, including
EtherNet/IP,
ControlNet, DeviceNet, DH+, DH-485, Universal Remote I/O and serial networks"
Is there a more specific specification I should be looking for?

You need to go on A/B's forum and ask questions to get the best answers.  What can go in the CPU slot that can address the I/O that is just a comm slave?  I can tell you that answer easily with the 205 and BRX Automation Direct PLC I/O lines, but since this is AB, I have no clue.  AB experts sometimes look at this forum, but I bet a ton more monitor AB's forums.

[jwbaker3]

I don't think it will work but you can get a 1747 AENTR to replace the SLC 5/05 and use it as remote I/O on a 5069 Compactlogix or a 1756 Controllogix I have used the Do More as remote I/O for the Compactlogix and the controllogix but have never been able to go the other way. I have not tried now that the DoMore will do Implicit messaging but I would not think it will work AB doesn't play well with others and forget getting information on anything other than AB products. You know the I/O for the 1747 is being made obsolete very fast by AB? Save yourself some problems 6 months from now when you cant get any spare parts (other than Ebay) and change all the hardware to DoMore or something current.

[Controls Guy]

Hello all,
How can I address an Allen Bradley IO (SLC500) with Direct logic or Do More PLC? I am planning to replace an obsolete AB SLC 5/05 with a DL or DM PLC but wish to use the 3 local IO racks as time allows. Is this doable? It will also keep downtime to a minimum.

So your remote racks are probably on AB RIO (remote I/O) which is a proprietary serial protocol run over the same media (blue hose / smurf tube) as Data Highway+.    I wouldn't even attempt talking to that; AB's implementation of remote I/O, especially as it applies to the 1747/SLC platform, is very quirky and I'm not even sure it's publicly documented like DF1, the serial protocol of that era (and I've written AB drivers, just don't).   NOT going to be a fun time if it's even possible.

The 1747 platform is fully obsolete as of March 1 of last year, you're not getting any replacement parts except from Ebay or equivalent.

One option is leaving the 5/05 and talking to one of it's comm ports from the BRX and just using it as an I/O head.   I know they support E/IP to at least some degree as that's one of the protocol choices in Linx to talk to them (the driver for legacy AB Ethernet, called PCCC Ethernet,  is named ABETH in Linx).   Do-More may be able to talk to that.  Some of the later SLC OSs and firmwares support Modbus RTU, not sure if TCP is available, thinking no.   You could certainly get a standalone or rack mounted gateway that will translate between AB-speak and BRX-speak.

Another option is to replace the remote I/O adapters in the remote racks (presumably 1747-ASB if RIO) with Ethernet/IP ones, if you can find them, and if Do-More's Ethernet/IP implementation will talk to those.  But again, do you want to drop money into something that's already past obsolescence?

EDIT: Just noticed that although this thread was near the top, it was almost all from the beginning of January.   Sorry for the too little, too late help!