Allen-Bradley 1756 ControlLogix User manual

Logix5000 Controllers
Import/Export
1756 ControlLogix Controllers
1769 CompactLogix Controllers
1789 SoftLogix Controllers
1794 FlexLogix Controllers
PowerFlex 700S DriveLogix Controllers
Reference Manual
Spare Allen-Bradley Parts

Important User Information
Because of the variety of uses for the products described in this
publication, those responsible for the application and use of this
control equipment must satisfy themselves that all necessary steps
have been taken to assure that each application and use meets all
performance and safety requirements, including any applicable laws,
regulations, codes and standards.
The illustrations, charts, sample programs and layout examples shown
in this guide are intended solely for purposes of example. Since there
are many variables and requirements associated with any particular
installation, Allen-Bradley does not assume responsibility or liability
(to include intellectual property liability) for actual use based upon
the examples shown in this publication.
Allen-Bradley publication SGI-1.1, Safety Guidelines for the
Application, Installation and Maintenance of Solid-State Control
(available from your local Allen-Bradley office), describes some
important differences between solid-state equipment and
electromechanical devices that should be taken into consideration
when applying products such as those described in this publication.
Reproduction of the contents of this copyrighted publication, in whole
or part, without written permission of Allen-Bradley Company, Inc.,
is prohibited.
Throughout this manual we use notes to make you aware of any
safety considerations:
Attention statements help you to:
•identify a hazard
•avoid a hazard
•recognize the consequences
Logix5550 is a trademark of Allen-Bradley, Inc., a Rockwell International Company.
Microsoft, Access, and Excel are trademarks of Microsoft.
ATTENTION
!
Identifies information about practices or
circumstances that can lead to personal injury or
death, property damage or economic loss
IMPORTANT Identifies information that is critical for successful
application and understanding of the product.

1Publication 1756-RM084F-EN-P - July 2002
Summary of Changes
Summary of Changes
This document describes how to use version 2.2 (major revision 2,
minor revision 2) of the import/export utility that is included with
RSLogix 5000 programming software, version 11.10.
Changes made for version 11.10 include:
•Support for the 1756-L63 controller (see page 2-5).
•New controller attributes to support sequential function charts
(see page 2-5).
•Corrected the DATATYPE attributes and added the FamilyType
attribute (see page 3-2).
•Additional information for the CompatibleModule and KeyMask
attributes of the MODULE component (see page 3-6).
•Addition of RSNetWorxFileName attribute to the MODULE
component (see page 3-7).
•Addition of SFC_ACTION, SFC_STEP, and SFC_STOP tag types
(see page 3-11).
•Addition of 38400 as a supported serial port baud rate (3-38).
•Addition of structured text instructions (see page 6-1).
•Addition of EOT, SFR, and SFP instructions to relay ladder (see
pages 4-5 and 4-8) and structured text (see pages 6-5 and 6-8).
•Addition of sequential function chart components
(see page 7-1).
•Addition of an appendix that lists the valid CommMethod and
ConfigMethod values for the supported I/O modules
(see page A-1)
Spare Allen-Bradley Parts

Publication 1756-RM084F-EN-P - July 2002
Summary of Changes 2
Notes:

iPublication 1756-RM084F-EN-P - July 2002
Table of Contents
Chapter 1
Importing and Exporting Files
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Importing a Complete Text File into a Project. . . . . . . . . . . 1-2
Exporting a Complete Project to a Text File . . . . . . . . . . . . 1-3
Importing a Tags Text File into a Project . . . . . . . . . . . . . . 1-4
Exporting Tags to a Text File. . . . . . . . . . . . . . . . . . . . . . . 1-6
Selecting the scope of the tags to export. . . . . . . . . . . . 1-6
Chapter 2
Structuring a Complete (.L5K)
Import/Export File Format
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Internal file comments . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Placing Information in an Import/Export File . . . . . . . . . . . 2-2
Display style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Component descriptions. . . . . . . . . . . . . . . . . . . . . . . . 2-3
Defining a Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Specifying CONTROLLER attributes. . . . . . . . . . . . . . . . 2-5
CONTROLLER guidelines . . . . . . . . . . . . . . . . . . . . . . . 2-6
CONTROLLER example . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Chapter 3
Creating a Complete
Import/Export File
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Defining a Data Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Specifying DATATYPE attributes. . . . . . . . . . . . . . . . . . 3-2
Specifying a DATATYPE member . . . . . . . . . . . . . . . . . 3-2
Specifying DATATYPE member attributes . . . . . . . . . . . 3-4
DATATYPE guidelines . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
DATATYPE example . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Defining a Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Specifying MODULE attributes . . . . . . . . . . . . . . . . . . . 3-5
Specifying a MODULE connection list. . . . . . . . . . . . . . 3-7
Specifying MODULE connection list attributes . . . . . . . . 3-8
MODULE guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
MODULE example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Defining a Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Defining a TAG declaration for a non-alias tag . . . . . . . 3-11
Defining a TAG declaration for an alias tag. . . . . . . . . . 3-12
Defining an array specification . . . . . . . . . . . . . . . . . . . 3-12
Specifying TAG attributes . . . . . . . . . . . . . . . . . . . . . . . 3-13
Defining TAG initial values. . . . . . . . . . . . . . . . . . . . . . 3-28
Defining a comment for a TAG component. . . . . . . . . . 3-29
TAG guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30
TAG examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30
Spare Allen-Bradley Parts

Publication 1756-RM084F-EN-P - July 2002
ii
Defining a Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31
Specifying PROGRAM attributes . . . . . . . . . . . . . . . . . . 3-32
PROGRAM guidelines . . . . . . . . . . . . . . . . . . . . . . . . . 3-32
PROGRAM example. . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33
Defining a Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33
Specifying TASK attributes . . . . . . . . . . . . . . . . . . . . . . 3-34
TASK guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34
TASK example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35
Defining a Controller Object . . . . . . . . . . . . . . . . . . . . . . . 3-35
Specifying CONFIG attributes . . . . . . . . . . . . . . . . . . . . 3-36
CONFIG examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-40
Chapter 4
Entering Ladder Diagram Logic
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Entering a Ladder Logic Routine . . . . . . . . . . . . . . . . . . . . 4-1
Specifying ROUTINE attributes . . . . . . . . . . . . . . . . . . . 4-1
Entering Rung Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Rung guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Ladder ROUTINE example . . . . . . . . . . . . . . . . . . . . . . 4-3
Entering Branches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Example with a single branch. . . . . . . . . . . . . . . . . . . . 4-4
Example with two simultaneous branches. . . . . . . . . . . 4-4
Entering Rung Comments . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Entering Neutral Text for Ladder Instructions . . . . . . . . . . . 4-4
Chapter 5
Entering Function Block
Diagram Logic
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Entering a Function Block Diagram Routine . . . . . . . . . . . . 5-1
Specifying FBD_ROUTINE attributes. . . . . . . . . . . . . . . 5-2
Entering Function Block Diagram Logic . . . . . . . . . . . . . . . 5-2
SHEET guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
FBD_ROUTINE example . . . . . . . . . . . . . . . . . . . . . . . 5-4
Entering IREFs and OREFs. . . . . . . . . . . . . . . . . . . . . . . . . 5-6
IREF and OREF guidelines . . . . . . . . . . . . . . . . . . . . . . 5-7
IREF and OREF examples. . . . . . . . . . . . . . . . . . . . . . . 5-7
Entering ICONs and OCONs . . . . . . . . . . . . . . . . . . . . . . . 5-8
ICON and OCON guidelines. . . . . . . . . . . . . . . . . . . . . 5-8
ICON and OCON examples . . . . . . . . . . . . . . . . . . . . . 5-9
Entering Wires and Feedback Wires. . . . . . . . . . . . . . . . . . 5-9
WIRE guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
WIRE example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
Entering Blocks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
BLOCK guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
Entering Parameters for Function Block Instructions . . . . . . 5-12

Publication 1756-RM084F-EN-P - July 2002
iii
Chapter 6
Entering Structured Text Logic
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Entering a Structured Text Routine . . . . . . . . . . . . . . . . . . 6-1
Specifying STX_ROUTINE attributes . . . . . . . . . . . . . . . 6-1
Entering Structured Text Logic. . . . . . . . . . . . . . . . . . . . . . 6-2
Structured text STX_ROUTINE example . . . . . . . . . . . . 6-3
Entering Comments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Entering Structured Text . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Chapter 7
Entering Sequential Function
Chart Logic
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Entering a Sequential Function Chart Routine. . . . . . . . . . . 7-1
Specifying SFC_ROUTINE attributes . . . . . . . . . . . . . . . 7-3
SFC_ROUTINE example . . . . . . . . . . . . . . . . . . . . . . . . 7-4
Entering Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
Entering the PRESET block. . . . . . . . . . . . . . . . . . . . . . 7-11
Entering the LIMIT_HIGH block . . . . . . . . . . . . . . . . . . 7-11
Entering the LIMIT_LOW block . . . . . . . . . . . . . . . . . . 7-11
Entering the ACTION_LIST block . . . . . . . . . . . . . . . . . 7-12
STEP example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
Entering Transitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14
Entering the CONDITION block . . . . . . . . . . . . . . . . . . 7-15
TRANSITION example . . . . . . . . . . . . . . . . . . . . . . . . . 7-15
Entering Subroutine Calls . . . . . . . . . . . . . . . . . . . . . . . . . 7-15
SBR_RET example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16
Entering Stops. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16
STOP example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17
Entering Branches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17
Entering the LEG block . . . . . . . . . . . . . . . . . . . . . . . . 7-18
BRANCH example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19
Entering Directed Links . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19
DIRECTED_LINK guidelines . . . . . . . . . . . . . . . . . . . . . 7-20
DIRECTED_LINK example . . . . . . . . . . . . . . . . . . . . . . 7-20
Entering Text Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20
TEXT_BOX guidelines . . . . . . . . . . . . . . . . . . . . . . . . . 7-21
TEXT_BOX example . . . . . . . . . . . . . . . . . . . . . . . . . . 7-21
Entering Attachments . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-21
ATTACHMENT guidelines . . . . . . . . . . . . . . . . . . . . . . 7-21
ATTACHMENT example. . . . . . . . . . . . . . . . . . . . . . . . 7-21
Spare Allen-Bradley Parts

Publication 1756-RM084F-EN-P - July 2002
iv
Chapter 8
Structuring the Tag (.CSV)
Import/Export File Format
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Internal file comments . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Placing Information in a Tag (.CSV) Import/Export File . . . 8-2
Specifying a Tag Record . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Specifying dimensions . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
TAG examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Specifying an Alias Record . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Specifying a Comment Record . . . . . . . . . . . . . . . . . . . . . . 8-5
Sample Scenarios of Importing/Exporting Tags. . . . . . . . . . 8-6
Example Tag Import/Export File . . . . . . . . . . . . . . . . . . . . 8-7
Appendix A
Valid CommMethod and
ConfigMethod Values
1734 Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
1747 Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
1756 Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
1769 Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12
1771 Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12
1784 Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13
1788 Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13
1789 Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13
1794 Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14
1797 Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-16
PowerFlex Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-17
Drives and Motion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-17
Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-19
Appendix B
Considerations for Using
Microsoft Excel to Edit a .CSV File
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Recommendations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
RSLogix 5000 Data Transformations . . . . . . . . . . . . . . . . . . B-2
Microsoft Excel Data Transformation . . . . . . . . . . . . . . . . . B-2
Appendix C
Import/Export Revision History
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Backward Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Import/Export Version 2.1 RSLogix 5000 Version 10.0. . . . . C-2
Changes to support MESSAGE tag enhancements . . . . . C-3
Import/Export Version 2.0 RSLogix 5000 Version 9.0 . . . . . C-4
Motion Changes to Support the SERCOS Protocol. . . . . . . . C-5

1Publication 1756-RM084F-EN-P - July 2002
Chapter 1
Importing and Exporting Files
Introduction
This document describes how to use version 2.2 (major revision 2,
minor revision 2) of the import/export utility that is included with
RSLogix 5000 programming software, version 11.10.
With a Logix controller, you can import/export an entire project or
you can import/export tags within a project.
When you import or export a project, you use the entire project. The
text file is a complete import/export file, that includes tag definitions,
data, program logic, I/O configuration information, and controller
configuration information. If you import or export tags, the text file is
a partial import/export file, that includes only tag definitions and
tag comments.
The structure of the import/export file depends on whether you
perform a complete or partial import/export operation. There are also
different considerations for complete and partial import/export
operations. This chapter shows how to perform the import/export
operations and describes any considerations.
When working with: You can: See Page:
projects import a text file to create a project 1-2
export a project into a text (.L5K) file 1-3
tags import tags into a project 1-4
export tags into a text (.CVS) file 1-6
Spare Allen-Bradley Parts

Publication 1756-RM084F-EN-P - July 2002
1-2 Importing and Exporting Files
Importing a Complete Text
File into a Project
You can import controller information from a saved text file (that has
a .L5K extension). This lets you use any text editor to create a project.
1. Select File →Open.
2. Select the text file.
Select the file to import.
By default, the software points to the
\RSLogix5000\Project folder. You can change
the default via Tools → Options.
Specify the name for the file to import.
Click Open.
The text file must have a .L5K extension.
3. Specify the name and location of the project
Specify the project name.
Specify the project location.
Click Import.

Publication 1756-RM084F-EN-P - July 2002
Importing and Exporting Files 1-3
If you import a project that has forces, the project defaults to Forces
Disabled, even if the project was exported with Forces Enabled.
For more information about the structure of the complete
import/export file, see:
Exporting a Complete
Project to a Text File
You can export the project to a text file. You can then use any text
editor to modify the project.
For information on: See chapter:
structuring a complete import/export file 2
creating a complete import/export file 3
entering logic 4
1. Select File →Save As.
2. Define the project.
Click Save.
Make sure the project you want to export is already open.
Specify the name of the text file.
Select the .L5K file format.
IMPORTANT Any unsaved edits are automatically saved when you
OK the export operation.
Spare Allen-Bradley Parts

Publication 1756-RM084F-EN-P - July 2002
1-4 Importing and Exporting Files
Importing a Tags Text File
into a Project
When you are offline and have a project open, you can import tags
from a saved text file (that has a .CSV extension). This lets you use a
database program (like MicrosoftExcel) to create and edit tags.
1. Select Tools →Import Tags.
2. Select the text file.
Select the file to import.
Specify the name for the file to import.
The text file must have a .CSV extension.
Click Import.
Select the .CSV file format.
Select how to handle collisions.

Publication 1756-RM084F-EN-P - July 2002
Importing and Exporting Files 1-5
When you import tags, the possibility exists for tags in the import file
to have the same name as tags already in the open project. This
condition is a collision. You specify how to handle a collision when
you select the tag file to import:
It is also possible to have tags in the import file that do not exist in the
open project. You can select whether to create these tags in the
project.
If you delete tags from an import/export file and then import the file,
tags are not deleted from the controller project. You have to use the
programming software to delete tags from the tag list.
For more information about the structure of the partial import/export
file, see:
If you want to: Select:
replace the tag in the project with the tag
from the import file
Overwrite
(this is the default selection)
keep the tag that is in the project and
discard the tag in the import file
Discard
For information on: See chapter:
structuring a partial import/export file 6
Spare Allen-Bradley Parts

Publication 1756-RM084F-EN-P - July 2002
1-6 Importing and Exporting Files
Exporting Tags to a
Text File
When you have a project open, you can export tags to a text file. You
can then use a database program (like Microsoft Excel) to edit tags.
Selecting the scope of the tags to export
When you export tags, you have these choices as to which tags in the
project you want to export.
1. Select Tools →Export Tags.
2. Define the project.
Click Export.
Make sure the project you want to export tags from is already open.
Specify the name of the tags file.
Select the .CSV file format.
Select the scope of the tags to export.
Scope: This option exports:
All tags in project all the tags (controller-scope and program-scope) in the
project to a text file.
Controller tags the controller-scoped tags of the project to a text file.
Program tags the program-scoped tags of the program you specify. Use
the drop-down arrow to display the available programs in
the current project.

1Publication 1756-RM084F-EN-P - July 2002
Chapter 2
Structuring a Complete (.L5K)
Import/Export File Format
Introduction
This chapter explains the overall structure of a complete
import/export file. The file extension for a complete import/export file
is .L5K.
For information about the specifics of each component in an
import/export file, see the chapter “Creating an Import/Export File”.
For information on entering logic, see the chapter “Entering Logic.”
Conventions
The import/export utility is based on the formats specified by the
IEC 1131-3 specification. The examples follow these conventions:
White space characters include spaces, tabs, carriage return, newline,
and form feed. 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
You can enter comments to document your import files. The import
process ignores these comments. You can place comments anywhere
in an import/export file, except in keywords, names, component
descriptions, and the value portion of attributes (before the delimiting
comma or the end parenthesis).
Convention: Meaning:
< > items shown in angle brackets are required
[ ] items shown in square brackets are optional
user_value
items in italics indicate user-supplied information
LITERAL items in all uppercase indicate a required keyword
or symbol that must be entered as shown
“[“ items in double quotes are required characters
Spare Allen-Bradley Parts

Publication 1756-RM084F-EN-P - July 2002
2-2 Structuring a Complete (.L5K) Import/Export File Format
You can enter comments using either of these methods:
•Start the comment with two percent (%%) characters and stop at
the end of the line.
•Start the comment with a “(*” and end with a corresponding “*)”.
Comments can extend multiple lines.
Placing Information in an
Import/Export File
The import/export file contains different components of information.
These components are:
All components in an import export file follow this structure:
Component_Type < component_name > [ Attributes ]
[
body ]
END_
Component_Type
Where:
Component: Identifies:
CONTROLLER name of the controller
DATATYPE user-defined and I/O data structures
MODULE modules in the controller organizer
TAG controller-scope tags
PROGRAM program files
ROUTINE ladder logic routines
FBD_ROUTINE function block diagram routines
SFC_ROUTINE sequential function chart routine
STX_ROUTINE structured text routine
TASK controller tasks
CONFIG configuration information
Item: Identifies:
Component_Type the component (as defined in above table)
component_name a specific instance of the component
Attributes any attributes of the component
can also contain a description of the component
separate each attribute with a comma (,)
body any sub-components (children) of this component
END_Component_Type end of the component information

Publication 1756-RM084F-EN-P - July 2002
Structuring a Complete (.L5K) Import/Export File Format 2-3
Display style
Tags and data types support a radix attribute that lets you specify how
to display the associated numerical information. The options are:
Component descriptions
Descriptions of components are optional. Unlike internal comments,
descriptions are imported. Place the description within double quotes.
For example:
TASK Task1 (Description := “Hello World”, Rate := 10000,
Priority := 10 )
END_TASK
To enter control characters in the description, precede the character
with a dollar sign ($). The following table shows how to enter the
supported control characters in a description:
Display Option: Example (based on 15 decimal):
Binary (uses a 2# prefix) 2#0000_0000_0000_1111
Octal (uses a 8# prefix) 8#000_017
Decimal 15
Hex (uses a 16# prefix) 16#000F
Ascii ‘$00$0F’
Exponential 1.5000000e+01
Float 15.0
For this character: Enter:
$$$
‘$’
“$Q
10 (line feed) $L or $l
13,10 (carriage return, line feed) $N or $n
12 (form feed) $P or $p
13 (carriage return) $R or $r
9 (tab) $T or $t
xxxx (4-digit character code that
represents a hexadecimal value)
$xxxx
Spare Allen-Bradley Parts

Publication 1756-RM084F-EN-P - July 2002
2-4 Structuring a Complete (.L5K) Import/Export File Format
Defining a Controller
The CONTROLLER component is the overall structure of a project to
be executed on one controller. It contains the configuration
information and logic that you download to one controller. Preceding
the CONTROLLER component, you have the header remarks
(optional) and the version statement:
Import-Export
Version := RSLogix 5000 - 11.00.00.00
Owner := User Name, Allen-Bradley Co., Inc.
Exported := Fri June 14 10:25:38 2002
IE_VER := 2.2;
Following the header and version statement, the CONTROLLER
component follows this structure:
CONTROLLER < controller_name > [ Attributes ]
[<DATATYPE declaration>]
[<MODULE declaration>]
[<TAG declaration>]
[<PROGRAM declaration>]
[<TASK declaration>]
[<CONFIG controller objects declaration>]
END_CONTROLLER
Where:
Item: Identifies:
controller_name the controller name for the project
Attributes attributes of the controller
can also contain a description of the controller
separate each attribute with a comma (,)
DATATYPE I/O and user-defined data structures
See page 3-1.
MODULE devices in the controller organizer
See page 3-5.
TAG controller-scope tags
See page 3-10.
PROGRAM organization of routines
See page 3-31.
TASK organization of programs
See page 3-33.
CONFIG characteristics of controller objects (status information)
See page 3-35.

Publication 1756-RM084F-EN-P - July 2002
Structuring a Complete (.L5K) Import/Export File Format 2-5
Specifying CONTROLLER attributes
You can specify these attributes for a CONTROLLER:
Attribute: Description:
Description Provide information about the controller.
Specify: Description := ”
text ”
ProcessorType Specify the type of controller (1756-L1, 1756-L53, 1756-L55, 1756-L63, 1769-L20,
1769-L30, 1789-L60, 1794-L33, 1794-L34, PowerFlex700S)
Specify: ProcessorType :=
name
Major Specify the major revision number (1-127) of the controller.
Specify: Major :=
number
TimeSlice Percentage of available CPU time (10-90) that is assigned to communications.
Specify: TimeSlice :=
value
PowerLossProgram Name of the program to be executed on reboot after a power loss.
Specify: PowerLossProgram :=
name
MajorFaultProgram Name of the program to be executed when a major fault occurs.
Specify: MajorFaultProgram :=
name
CommPath List of the devices in the communication path. The communication path ends with the
controller (\Backplane\1).
Specify: CommPath :=
device\device\device... \Backplane\1
SecurityCode Specify whether the RSI Security Server is enabled for the controller. Enter 0 if the
controller is unsecured; enter -1 the controller is secured.
Specify: SecurityCode :=
text
RedundancyEnabled Specify whether redundancy is used or not. Enter a 0 to disable redundancy; enter a 1 to
enable redundancy.
Specify: RedundancyEnabled :=
number
KeepTestEditsOnSwitchOver Specify whether to keep test edits on when a switchover occurs (only in a redundant
system). Enter a 0 not to keep test edits on; enter a 1 to keep test edits on.
Specify: KeepTestEditsOnSwitchOver :=
number
DataTablePadPercentage Specify the amount of data table to reserve. If redundancy is not enabled, enter 0. If
redundancy is enabled, enter 50.
Specify: DataTablePadPercentage :=
name
SFCExecutionControl Specify whether the SFC executes the current active steps before returning control
(CurrentActive) or whether the SFC executes all threads until reaching a false transition
(UntilFalse).
Specify: SFCExecutionControl :=
name
SFCRestartPosition Specify whether the SFC restarts at the most recently executed step (MostRecent) or at
the initial step (InitialStep).
Specify: SFCRestartPosition :=
name
SFCLastScan Specify how the SFC manages its state on last scan. Select AutomaticReset,
ProgrammaticReset, or DontScan.
Specify: SFCLastScan :=
name
Spare Allen-Bradley Parts

Publication 1756-RM084F-EN-P - July 2002
2-6 Structuring a Complete (.L5K) Import/Export File Format
CONTROLLER guidelines
Keep these guidelines in mind when defining a data type:
•All declarations must be explicitly ordered as shown in the
syntax above.
•The maximum number of tasks depends on the controller type:
•There can only be one continuous task.
•Programs can only be scheduled under one task
•Scheduled programs must be defined - i.e. must exist
CONTROLLER example
CONTROLLER TestImportExport (Description := “Example",
TimeSlice := 11, MajorFaultProgram := Prg2)
END_CONTROLLER
Controller: Maximum Number of Tasks:
ControlLogix 32
SoftLogix5800 32
FlexLogix 8
CompactLogix (L20, L30) 4
DriveLogix 4