®

PLCopen
for efficiency in automation

PLCopen XML now available as IEC 61131-10

Opening up the development environments by specifying XML formats for IEC 61131-3

Background information complete new market, in which the focus is on

Since the release of the IEC 61131-3 programming reusability of software developments up to whole
standard, users want to be able to exchange their projects.
programs, libraries and projects between software tools This XML exchange format supports life cycle
like development environments. Although this was not management of automation systems, e.g. in case of
the intent of the standard itself, it was a task that the redesign, maintenance or device replacement. If an
independent organization PLCopen committed itself to. IEC 61131-3 project is stored in this XML format, it
could be reused independent of a special development
IEC 61131-3 defines programming languages. As such it environment. And thus, it could be modified and
is a part of a total solution. Other parts are tools for maintained by any other development environment
simulation, debugging, version control, documentation, supporting this standard’s XML exchange format.
networking, and more. PLCopen has decided years ago
to realize interfaces towards these supporting tools. This Originally the work was done by the PLCopen
resulted in a workgroup named TC6 for XML Technical Committee 6 fits well into the PLCopen
(eXtensible Mark-up Language). This committee mission:
defined an open interface which can be used by different We want to be the leading association resolving topics
kinds of software tools to transfer the information that is related to control programming to support the use of
on the screen to other platforms. This screen information international standards in this field.
does not only contain textual information, but also
graphical information, like where the function blocks are With the release of the 3rd edition of IEC 61131-3 in
and how they are connected to each other. 2013, a major overhaul was needed to include the
changes and extensions like object oriented features.
User Perspective This work was done within the IEC committee based on
PLCopen wanted to accomplish that, without much the work of PLCopen TC6 – XML and resulted in IEC
additional effort, a project can be transferred from one 61131-10 PLC open XML exchange format. This new
development environment to another without losing version is not compatible to previous versions of
information, even when it is incomplete, syntactically PLCopen XML.
incorrect, or contains compile errors, e.g. such a project
could be an in-between version or a project containing Programming in its environment
several unconnected FBD blocks. This of course is also As mentioned before, the programming tools are just a
valid for the POUs, and especially for User Derived part of the whole suite of software tools that can be used
Function Block libraries. This means that the program to make an application work. The result of the PLCopen
itself has to remain the same, e.g. not be altered during XML activity opens the development environment by
this transfer. The big variety of possibilities has to be providing interfaces to other software tools. In the figure
brought under one umbrella. And XML provides the below, one can identify the interfaces around the blue
right technology for this. circle.

Results of this PLCopen Workgroup Production Modelling & Development

Producer (export)

planning Simulation environment

The result of the PLCopen XML work opens the
development environment by providing interfaces to
other software tools. Electrical
engineering
As such it will be more than an export / import tool from XML exchange format

one development environment to another: it is just a

Consumer (import)

small step to feed for instance a documentation tool with

the information. Actually, it is not important where this Code Development
Documentation
XML-code is coming from as long as it is recognizable analysis environment
and usable. It could be generated by other tools like
simulation and modelling tools, and consumed by
verification, documentation, and version control tools. TC6 – XML: Definition of use cases
In principle all relevant information will be exported. The participants identified 4 areas where the
The importing tool has to be intelligent in filtering specification fits ideal:
which parts of this information is useful and needs to be 1. Exchange format between all five languages;
imported and used. With this PLCopen creates a
2. Interface to producers of graphical and logical Schemas
information, like modelling tools; The exchange format is specified as a corresponding
3. Interface to consumer of graphical and logical XML schema, being an independent file with the .xsd
information, like documentation generator and extension and as such part of the specification. Supplier
management; and version control; specific extensions can be added – see schema’s below.
4. Distribution format for function block libraries.
PLCopen TC6 – XML official release
What is included The PLCopen technical document XML formats for IEC
With the scope of whole projects, a lot of information 61131-3 was first released in 2005. Version 2.0 followed
needs to be stored in the XML format. And since we do in 2008, improving the interface to the virtual factory
not know upfront which tool will be the consumer of the and the real controllers. An update with some minor
information, we have to export all potential relevant changes, version 2.01, was published in 2009.
information. This include items like:
 Textual Programming Languages: IL and ST Nowadays the PLCopen XML specification is an
 Graphical Programming Languages: LD and FBD integral part of the IEC 61131 suite of specifications
 Structural Language: SFC with the release of the international standard
 Graphical Information, like place and position, and IEC 61131-10 PLC open XML exchange format in
routing of connections 2019.
 Comments
 Program Organization Units – (User Derived) PLCopen members using this technology can be easily
Functions and Function Blocks, Programs identified by the following logo:
 (User Derived) Datatypes
 Project information (layered structure)
 Mapping information
 Supplier specific information

This means that the exported file contains ‘everything’,

including supplier specific information. The consumer
side, with the parsing function during input, must
contain the intelligence to select the relevant
information, and to check on the consistency of this
data. For this the tool can use a different scheme. The specification is available at www.IEC.org
Combining both schemes provide the possibility to For more information, check www.PLCopen.org.
check the incompatibilities, and get the relevant If this information is helpful for you or your company,
information more easily. This clearly shows the benefits think about joining this association, and help to increase
of using XML schemes. the efficiency in industrial automation.

Schema with only IEC 61131-3

features (top line) the project XML
document should simply specify
the formal XML exchange format.
In case the “AddData” mechanism
is used in the project, the project
XML document should refer to the
extended schemata.

In the case supplier specific

language extensions are used, the
supplier should define their own
schema with the extensions besides
the standard formal XML
exchange format schema
(Abstract complex type)