Learning IEC 61131-3 Programming Languages

As a long-time integrator, I've become a reliable source of help for most PLC-based ladder logic systems. But it's clear that I need to supplement this with object-based programming skills around the IEC 61131-3 standard languages. Is function block reusability, which is supposed to make my life easier, its biggest benefit? What's the learning curve like to become good at it?

Send us your comments, suggestions or solutions for this problem. We'll include it in the January '13 issue. You can comment here or email us at controldesign@putman.net. Please include your company, location and title in the response.

Show Comments
Hide Comments

Join the discussion

We welcome your thoughtful comments.
All comments will display your user name.

Want to participate in the discussion?

Register for free

Log in for complete access.


  • <p>Function block reusability is nice, but I don't think that should be the major selling point. How often do you need to do the exact same task in different projects? It happens, but I usually end up editing an existing function block and make a new one to suit the new purpose. I prefer the IEC style mostly because it offers so much flexibility. Some tasks are programmed more naturally in text, ladder, sequential function chart, etc. I don't know of anyone in the States that programs using instruction list. Very efficient from a processing standpoint, but not very intuitive. I tend to use sequential function chart programming for both overall machine control, and for function blocks. It is essentially a flow chart that has all your code in it.</p> <p>The learning curve isn't that long. I think that knowing ladder may not help you a whole lot because you may want to fall back on that instead of figuring out a better method. I know of several old-time PLC programmers that want nothing to do with anything other than ladder. Part of that is because the guys on the floor already know ladder well enough to troubleshoot, but the IEC style is a big change.</p>


RSS feed for comments on this page | RSS feed for all comments