Chapter 1 Import and export files
38 Rockwell Automation Publication 1756-RM084S-EN-P - March 2015
The import/export feature L5X format is structured by using the Extensible
Markup Language (XML). The XML specification is an open standard and is
widely documented elsewhere. The only special convention used to describe the
L5X format in this document is that items shown in square brackets ([ ]) are
optional.
White space characters include spaces, tabs, carriage returns, new line, and form
feeds. These characters can occur anywhere in an import/export file, except in
keywords or names. If white space characters occur outside of descriptions, they
are ignored.
Internal file comments
Enter internal file comments to document your .L5X import files by using the
XML commenting format. The import process ignores these comments. Place
comments anywhere in an import/export .L5X file except within XML tag
elements. You cannot next a comment within another comment.
An XML comment begins with the character sequence <!-- and ends with the
character sequence -->. The comment appears between the begin and end
character sequence. The character sequence -- may not appear within a comment.
The text of the comment is ignored by the XML parser. This is an example.
<!-- This is a comment that includes an XML start tag element,
<mytag>. The start tag is ignored by the parser. -->
Component Descriptions
Descriptions of components are optional. Unlike internal file comments,
descriptions of components are imported. To add a description to a component,
add a <Description> start tag element as the first sub-element of the component
and then the description as a CDATA element in the body of the <Description>
element.
Component descriptions are brought into the project without being processed by
the XML parser for markup language. The description text is contained in a
CDATA element, a standard in the XML specification. A CDATA element
begins with the character sequence <![CDATA[ and ends with the character
sequence ]]>. None of the text within the CDATA element is interpreted by the
XML parser. The CDATA element preserves formatting so there is no need to use
control characters to enter formatted descriptions.
<Task Name="Task1" Type="PERIODIC" Rate="1000" Priority="10"
Watchdog="500" DisableUpdateOutputs="false" InhibitTask="false">
<Description>
<
