QUOTE(snowmaxx @ Nov 19 2008, 05:58 PM) [snapback]75959[/snapback]
Maybe I should have been more clear on this, I don't know. All of my IO is on slc500 racks. There is no local IO to the PLC-5/60.
Either way, it looks like I am out of luck.
Oh, OK. Yes, you are correct about not being able to expand it. At the time (80's), the SLC was intended to be a cut down version of a PLC 5. If you wanted PLC 5 power, you buy PLC 5.
However, that just means you have to go a DIFFERENT direction in terms of remote IO. Here are two suggestions that will be roughly the same cost as putting IO into your existing chassis. In fact, it may even be less expensive (and quite often is)! AB is purposely pricing 1746, 1747, 1785, and 1771 stuff such that you won't buy it anymore for cost reasons in new projects or even on old ones. I'm going to walk you down through the same thing that was presented to me by an AB salesman that used to be the "inside sales" guy for Chrysler. One of the maintenance/engineering managers at the company I work at is a former Chrysler guy so I also have enough insider information from the other side of the table to verify that what he was telling me was true.
First, consider 1791R (CompactBlock) IO, aka "butter sticks". This is effectively the replacement for the old 1791 standard block IO (which I highly suggest you don't use if you don't have to because it is now very expensive and hard to get). The reason that I suggest you don't go with it is if you go with a new processor any time in the near future, you will be stuck with your old Remote IO and the same problem you have now. Chrysler went with it a few years back and now they are wishing they didn't because they have to rip it all out and start over whenever they want to upgrade to newer communication and/or PLC's. The future of IO for a situation like yours is probably eventually going to be Ethernet. AB was slow to get on the Ethernet bandwagon but now they are full steam ahead. You could go Ethernet too except that you'd have to upgrade from your existing processor fleet to ControlLogix or CompactLogix. This is a very expensive move the first time around, but you gain massive flexibility. And the reality is that AB is just starting to come out with what will represent this IO series. If you want to see what they are cooking up, look at ArmorBlock. It uses the same connector system as most types of sensors (M12) and doesn't need a cabinet at all. It is not (and will never be) available in Remote IO.
Second, consider 1794 "Flex IO". This stuff is sort of like SLC IO. You put your choice of network adapter on the front (RIO (ASB), Ethernet, or DeviceNet). Then you simply attach terminal blocks (up to 8) with or without one or two extension cords (to make it fit in the enclosure) and plug in your IO. You can get nearly any kind of IO you want with this stuff and your choices are not nearly as limited as 1771/1746 stuff. For instance, the 1794-OB16D is a 16 bit output card with "diagnostics". The card doesn't need fuses. It has electronic fusing which means if you short out an output, it just shuts down the output until the impedance drops back down to normal. It also checks for a few milliamps of power on the output and signals this as an error, too (open wire). Effectively your most common failures (shorted wires and broken wires) are automatically troubleshooted by the on board diagnostics in the card. They also have true isolated analog IO at a reasonable price, something you don't get with 1746 IO. And you can do RIUP (removal and insertion under power) with no chance of damaging something.
Then in the future if you put in a different processor and/or different IO and you want to walk away from Remote IO, your upgrade consists of pulling the new IO cable and replacing the network interface card with a different one. This by the way is currently the IO of choice in my shop (18 PLC-5's, one SLC, and 1 CLX).
Your third option is one you probably didn't ever notice because they file it in a different catalog altogether. If you have Ethernet capability on your processors and speed is not a tremendous issue (or on the contrary, speed is very important), consider AB's entire line of super smart IO (as opposed to their semi-smart IO). I'm referring to Micrologix. A Micrologix 1100 will set you back about $500 US, about the same price as a 1746 chassis IO card (or less). It comes with 10 inputs, 6 outputs, 1 serial port, 1 Ethernet port, and two kind of wimpy (10 bit 0-10V DC only) analog inputs. It can expand with up to 4 IO cards and the IO cards are between about $150US and $300US each. It has a very small LCD display that is somewhat programmable as well. Oh, and it comes fully capable of running 95% of the SLC ladder logic language. It's basically a "brick" SLC with an IO card price. The IO configuration even for digital IO is kind of strange looking because you have to use MSG blocks even for digital IO, but it works flawlessly without any hassle. The only warning I have is to make absolutely sure that you download the latest firmware and flash the processor whenever you get one. They still have a lot of old crap drifting around but it's all upgradeable.
I have placed these in several places where I have literally used them as "smart IO". I have one of them that doesn't even have a program! It just sits there acting as an output card for a real PLC. I only have one of them in the entire plant that actually gets used as a "real" PLC. The others (about 4 or 5) are nothing but IO to me.
Granted, this approach lacks certain things. MSG blocks are ugly, no matter how you look at it. And it has an odd sort of speed problem. Also, it assumes that you've already run Ethernet all over your plant and you are familiar and comfortable with it. The IO CAN be very fast (as fast as remote IO). But it is still TCP and still subject to occasional problems with Ethernet, so it's OK for command/process oriented things. But I wouldn't trust it for direct machine control (if you are using it as remote IO). That being said, I do have two of them in my plant that are literally just an extension of the IO on a PLC-5 including handling operator push buttons and nobody really notices the slight of hand going on. Since you do have a local PLC though, you can still do machine control if you treat it as a "master/slave" situation, such as having the Micrologix run some sort of carriage mechanism with a few actuators and the master PLC simply sending high level commands (carriage start, carriage stop).
I have not bought a Micrologix 1400 yet but it looks very intriguing. I had a recent project which I was going to go in a different direction due to the amount of IO and the limits of a Micrologix 1100 but the 1400 has much more on board capacity.