FeedVoices: Pollard
IEC 61131: Part III—The Benefits
There Are Some Good Reasons to Use an IEC 61131-Based Product
ControlDesign.com
By Jeremy Pollard, CET
As I wrap up my dissection of IEC 61131, you may want to catch up on the plot thus far by reading the previous columns that led us here. The saga is available online at ControlDesign.com/iec61131.
Now, make no mistake about 61131. We still are in the same environment we were in before its creation. Rockwell, Schneider, Siemens, GE and Wago all have their own programming environments. The business of automation won’t allow for real interoperability of these competing products.
The main difference from 20 years ago is that there is some form of commonality. There are some good reasons to use an IEC 61131-based product.
Tag names permit abstraction of the hardware I/O, so databases from product to product could be maintained externally. All will use tag names based variable allocation and typically the common elements, such as Boolean, will behave the same. That doesn’t mean, however, that all vendors support all the common elements.
Most products will have all five languages. A large benefit of an IEC 61131 integrated-development environment (IDE) is access to the function block part of the software. The power in function block programming is tremendous. This is the type of programming the older DCS products had 20 years ago. You can program a very complex part of the application and have it hidden behind a block. Some argue that this improves troubleshooting capabilities.
In return, it requires a better programming skill, as well as a good handle on the project scope and project management. This is foreign territory to many ladder programmers.
A selling feature of the standard is the ability to develop control strategies in the right language. While I agree with this, the plant floor maintenance staff usually doesn’t include a structured text guru. This is scary for the controls engineer who develops the application, so oftentimes he’ll just use ladder logic. One of the major benefits is left untapped as a result.
Proponents of IEC 61131 swear by its training and investment benefits. If you use Company A’s IEC 61131, and later you have to use Company B’s IEC 61131, you already know how to program the hardware. This is not necessarily so, but there is some truth to it.
Many companies use a development package from 3S. Some use a product from Softing, and others create their own. If an OEM used IEC software from four different hardware vendors and they all licensed their software from one company, the OEM stands a better chance of being able to migrate the learning curve to the new hardware and of being able to reuse the software.
Will the training cycle be shorter? Probably. But from vendor to vendor, there is some level of commonality that can be borrowed, but the impact may be limited.
Will IEC 61131 help the maintenance person trying to solve a problem at 3:00 A.M.? For most user companies that standardize on a single hardware platform, the answer is no. They’ll get used to whatever the software tool is. IEC 61131 isn’t important.
It might be important to you if you leave your company and have IEC 61131 on your resume. It surely can’t hurt.
If you are a machine builder or a manufacturer with multiple vendors that all use IEC 61131, maybe it helps. There are some inherent similarities that could help getting re-familiarized with a hardware platform or a software troubleshooting tool, but I think this is a personal function rather than a software tool function.
No doubt IEC 61131 is here to stay. Early misunderstandings of the benefits and the resulting misconceptions of what an IEC 61131-based product actually was turned off a lot of potential users.
Open is as open does. IEC 61131 is the same. It is simply a platform for a software product design tool for hardware. It provides some benefits for the OEM and the user, but mainly the vendors benefit, in my perception.
It is no panacea. It can help in our quest for a better automation platform, but we will leave that for IEC 61499, a true standard. As long as we don’t screw it up.
Jeremy Pollard has been writing about technology and software issues for many years. Publisher of The Software User Online, he has been involved in control system programming and training for more than 25 years.
More Voices
IEC 61131: Part III—The Benefits
05/09/2008
There Are Some Good Reasons to Use an IEC 61131-Based Product
What IEC 61131 Isn’t—Part II
04/18/2008
Ethernet Standards Are Global. Standards Regarding Power Plugs Are Local. In Which Corner Does IEC 61131 Belong?
IEC 61131-3: By the Numbers
04/06/2008
The Intent of Program Organizational Units (POUs) Is to Reduce Differences Between Suppliers, So A Timer Is A Timer, Regardless of Who Provides It
IEC 61131 Cage Match—Prologue
03/04/2008
Standards Are Great. There Are So Many to Choose From
Tools to Manage Trouble
02/08/2008
The Company Was Too Busy Killing Alligators to Remember That the Prime Objective Was to Drain the Swamp
LabView Style Book Is Worthy Read
10/31/2007
With instructor-led training running at about $2,000 a session, a self-learning book might be the ticket to get up to speed on this software.
Bit-Banger Does Process at AX
10/04/2007
Refineries can blow up, but with the square footage and sheer magnitude of the systems, the process control engineers have to get it right.
Software Rocks at CDAX
09/07/2007
Technology drives some customer needs, while others push service. Software handles everyone’s needs, which is why software vendors rock.
CDAX’s Real Relationships
08/01/2007
The Internet has become so pervasive by now that all troubleshooting and technical support should happen there, right? Do all machine builders need the same level of service? Perhaps not, but could this be considered a competitive advantage?
Firewall fireworks
06/04/2007
Columnist Jeremy Pollard, CET, notes customers are concerned about malicious damage intentions, yet the more we use Microsoft software and web services, the more we expose devices to hackers.
The search for secure data
05/07/2007
Embedded Intelligence columnist Jeremy Pollard, CET, is not declaring that encryption isn’t safe, but it’s only software, so how much can an insider make by selling the algorithms to the competition?
Service—Here today, gone tomorrow
04/04/2007
Embedded Intelligence columnist Jeremy Pollard, CET, says warranties are a necessary part of any business and that a good customer will most certainly get a better deal. What’s your policy?
Back to the books: PLC easy reader
02/01/2007
The coverage of IEC-61131 is complete and rivals standalone books on the subject. The author covers the languages, the application of the languages, and where the big benefits come from.
PLC home companion
01/03/2007
A tell-tale sign of good content is the handling of how a three-wire control circuit is built in a PLC. Embedded Intelligence columnist Jeremy Pollard, CET, reports that he finds the book's explanation confusing, although accurate.
Same ol’ song and no dance
12/15/2006
From a vendor’s perspective, legacy is innovation’s worst companion, and according to Industrial Networking columnist Jeremy Pollard, it’s very difficult to be innovative if it leaves the installed base behind.
30 years young
11/06/2006
Embedded Intelligence columnist Jeremy Pollard notes the divergence of people doing things and machines doing things has led to a large segment of workers who don’t have to think because machines do it for them.
Software as a service
10/10/2006
With the degree of change on some software platforms, paying huge dough for a product you will use sparingly really is pretty outrageous, making Internet access not just an option, but a necessity.
Slow going for IEC-61131
09/11/2006
Embedded Intelligence columnist Jeremy Pollard, CET, believes in PLCopen and its IEC-61131 language base and thinks you should too, but only after you get to know it well. Things sometimes are not as they appear.
Automation road trip
08/08/2006
At a tradeshow, we often don’t get the time, attention, and focus of vendors if we’re not an existing customer. At AutomationXchange, anyone with an automation initiative is important.
ECAD software eases electrification
06/05/2006
Embedded Intelligence columnist Jeremy Pollard takes a look at control drawing software options and finds you can move easily into using two new ECAD programs for control drawings and layouts.
Virtual computing in the industrial world
05/03/2006
Embedded Intelligence columnist Jeremy Pollard addresses the subject of accessing data from your server over the Internet, and asks how can we do better in both performance and cost?
Innovate, cultivate or evaporate
04/07/2006
Embedded Intelligence columnist, Jeremy Pollard, CET, wonders if we're forgetting to farm our own business infrastructures, processes and workers for help because we're too busy putting out fires.
Business is a contact sport
03/02/2006
Columnist Jeremy Pollard, CET, believes in a good team approach when preparing to work within global economies that demand it. But can working better as a team stem the flow of overseas jobs?
Survivor: Industrial OEM style
02/08/2006
CONTROL DESIGN Columnist Jeremy Pollard, CET, wonders what most of us would do if our businesses were interrupted -- seriously interrupted -- by something that stopped us from doing our daily work.
The saviors of PLC programmer sanity
09/15/2005
Embedded Intelligence writer Jeremy Pollard continues his series of columns on those influential few who made enormous impacts on the shape of industrial automation.
A PLC programmer’s pain -- 1980
07/17/2005
Embedded Intelligence writer Jeremy Pollard embarks on a trip down static-memory lane to recall the growing pains of the early days of brute force programming for some of you bit-bangers.
Genesis of the Programmable Logic Controller
06/15/2005
Embedded Intelligence writer Jeremy Pollard, CET, provides us with the history of the creation of the PLC, and how folklore has it that it was conceived on the back of a napkin more than three decades ago.
A simple solution to source code problems
06/01/1999
The flowcharting guys put in ladder logic for their customers. I guess they like ladder for control but agree that it needs to be dressed up.
Our HMI heroes
Embedded Intelligence writer Jeremy Pollard continues his series of columns on those influential few who made enormous impacts on the shape of industrial automation.