The past 10 years have seen the demise of many third-party software developers that created programming software for the hardware vendors. They were there because hardware guys are hardware guys, and couldnt write software.
Most vendors still put the power of the automation solution in a box. This way they retain their captive audience. You have to use their software, cables, and methodology. No evolution there.
Evolution is defined technically as a gradual process in which something changes into a different and usually more complex or better form.
As it involves the PLC, call this gradualism, maybe? Has the PLC evolved? Is it better? And to what form has it moved? Surely its more complex.
Ive been involved with PLCs and automation for 30 years now. The PLC began as a very disruptive technology, a PDP -11 in drag, as Dick Morley likes to describe his invention. Morley is arguably referred to as the inventor of the PLC. The PDP-11 was a Digital Equipment Corp. mini-computer.
The PLC wasnt too fancy, took a beating, had no off switch, and looked less than cool. Oh, and it was really, really expensive at the time.
Whats happened over the past 10 years to the venerable PLC and its supporting cast?
In my years of doing PLC instruction, Ive always taught the notion that a PLC is a control systemit doesnt matter what it looks like. Its what it does thats important.
A PLC is an electronic apparatuswith programmable memory, inputs and outputs, and a power supplythat executes user-entered instructions. Yeah, it was a computer, but we didnt know it as such back then. We also needed a programming device to get those damned addresses into the thing.
We controlled discrete applications, then process applications, to the point where the lines blurred and the PLC morphed into a full-fledged automation controller. This is an important point.
Every vendor, be it Texas Instruments, Siemens, Struthers-Dunn, or Allen-Bradley, had its own way of doing things. Ten years has marked the demise of many third-party software developers that created programming software for the hardware vendors. They were there because hardware guys are hardware guys and couldnt write software. That has since changed.
Ten years ago is when IEC-61131 was a very-young implementation of an older idea.
The proprietary nature of the hardware suppliers created a market opportunity for many companies. It also created a nightmare for users. Does the phrase held captive ring a bell?
It was because of this environment that a group from GM Powertrain started OMAC (open, modular architecture control). This group promoted the use of open standards and open connectivity. I believe it started the evolutionary path to where we are today.
Who would have thought that DeviceNet devices from many vendors would play together on the same bus? That in itself is an evolution.
The price/performance ratios of current day PLCs are 30 times greater than 10 years ago. The power of the micro-PLC range is equivalent to the mid-to-large range PLC of yesteryear. The difference is in I/O count. Remember, 10 years ago, 256K of RAM was expensive.
Small and distributed is the way of today. The good ol days saw massive PLC processors with big footprints for central control. Now the available communication layers allow for more distributed automation.
And, lest we forget about software, Windows 95 brought in a whole new era of computer-based programming software that allows us to do in five minutes what it used to take an hour to do. Ease of use is up a gazillion percent.
Its not that we didnt have software before. Its just that its easier now. Windows allows for much more elaborate development platforms than DOS did. Learning curves are no longer steep. After all, its Windows.
Weve evolved from automation development using desktops on carts to laptops, thankfully!
Oh, how I long for the days of sealed keyboards and cassette recorders. Until I realize I have it better now.
Morley thinks PLCs are evolving into an appliance, and that this appliance had better be Internet-enabled (really means IP-enabled). So much so that he has developed his own home-based PLC, the PERTASCO (Personal Task Controller). Ease of use prevails, and you dont have to tell it who it is. He feels that most of what we do today is much too vendor-defined, and that the users are losing out.
The one common thread with the folks I talked to about this article was that the PLC now is the PAC (programmable automation controller), and it has its own vendor-defined definitions. Market differentiation is important, but functionally, they arent much different.
Mark the first point on the evolutionary curve here.
The PAC by definition is a PLC. It has everything that a PLC system has, but with differences.
PACs have the ability to handle discrete, motion, drive, safety, batch and process control applications all from a common control platform, says Lee Lane, Logix product manager for Rockwell Automation.
PLCs did this 10 years ago. Heck, even 20 years ago. The PLC-3 with Advisor graphics, or a Modicon 584 with Modvue graphics, were so cool! Do you remember the GA module?
Why would a new definition be required? Evolutionary, my dear reader, evolutionary.
Integration of components and of functionality is the single biggest contributor to the PAC movement. We could do the multiple-discipline stuff before, but it wasnt pretty. Not that everything was an afterthought, but nothing ever seemed to work just quite right at first, and it was painful to make changes.