Micrologix Controllers To Micro800 Controllers Migration Guide
Micrologix Controllers To Micro800 Controllers Migration Guide
Micro800 Controllers
Migration Guide
Bulletins 1761, 1762, 1763, 1766, and 2080
Activities including installation, adjustments, putting into service, use, assembly, disassembly, and maintenance are required to be carried out by suitably trained
personnel in accordance with applicable code of practice.
If this equipment is used in a manner not specified by the manufacturer, the protection provided by the equipment may be impaired.
In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the use or application of this equipment.
The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and requirements associated with any
particular installation, Rockwell Automation, Inc. cannot assume responsibility or liability for actual use based on the examples and diagrams.
No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or software described in this manual.
Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation, Inc., is prohibited.
Throughout this manual, when necessary, we use notes to make you aware of safety considerations.
WARNING: Identifies information about practices or circumstances that can cause an explosion in a hazardous environment, which
may lead to personal injury or death, property damage, or economic loss.
ATTENTION: Identifies information about practices or circumstances that can lead to personal injury or death, property
damage, or economic loss. Attentions help you identify a hazard, avoid a hazard, and recognize the consequence.
IMPORTANT Identifies information that is critical for successful application and understanding of the product.
These labels may also be on or inside the equipment to provide specific precautions.
SHOCK HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that dangerous
voltage may be present.
BURN HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that surfaces may
reach dangerous temperatures.
ARC FLASH HAZARD: Labels may be on or inside the equipment, for example, a motor control center, to alert people to potential
Arc Flash. Arc Flash will cause severe injury or death. Wear proper Personal Protective Equipment (PPE). Follow ALL Regulatory
requirements for safe work practices and for Personal Protective Equipment (PPE).
Identifies information that is useful and can help to make a process easier to do or easier to understand.
Rockwell Automation recognizes that some of the terms that are currently used in our industry and in this publication are not in alignment with the
movement toward inclusive language in technology. We are proactively collaborating with industry peers to find alternatives to such terms and
making changes to our products and content. Please excuse the use of such terms in our content while we implement these changes.
Preface
About This Publication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Required Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
MicroLogix to Micro800 Converter tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Hardware Migration using Integrated Architecture Builder . . . . . . . . . . . . . . . . . . . . . . 8
Micro800 Simulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Download Firmware, AOP, EDS, and Other Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Summary of Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Chapter 1
Migrate Your MicroLogix Migrate MicroLogix 1000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Controller to a Compatible MicroLogix 1000 Controllers and Micro800 Controllers Comparison . . . . . . . . . . . . . . 10
Wiring Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Micro800 Controller
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Migrate MicroLogix 1100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
MicroLogix 1100 Controllers and Micro800 Controllers Comparison . . . . . . . . . . . . . . 13
Wiring Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Migrate MicroLogix 1200. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
MicroLogix 1200 Controllers and Micro800 Controllers Comparison . . . . . . . . . . . . . . 15
Wiring Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Migrate MicroLogix 1400. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
MicroLogix 1400 Controllers and Micro800 Controllers Comparison . . . . . . . . . . . . . . 18
Wiring Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Chapter 2
Plan Hardware Migration with Generate Hardware Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Integrated Architecture Builder Convert MicroLogix 1000, MicroLogix 1100, and MicroLogix 1200 Controllers to Micro800
Controllers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Convert MicroLogix 1400 Controllers to Micro850 and Micro870 Controllers. . . . . . . . 25
Chapter 3
Convert a MicroLogix Project to a Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Micro800 Project Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Overview of Program Execution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
High-Speed Counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
RSLogix Emulate 500 to Micro800 Simulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Logix Theme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Copy and Paste Code Between Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
What You Need. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Chapter 4
RLL Instruction Mapping Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Definitions, Acronyms, and Abbreviations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Bit Shift . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
BSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
BSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
MSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
EQU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
NEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
LES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
LEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
GRT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
GEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
LIM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
JMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
LBL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
RET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
SUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
TND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
I/O Related Interrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
IIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Appendix A
Additional Examples Configure Interrupts on a Micro800 Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Set Up High-Speed Counter (HSC) Instruction Variables . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Appendix B
Original and Converted Pick- Original RSLogix 500/RSLogix Micro Ladder Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
and-place Ladder Diagrams Connected Components Workbench Ladder Diagram (Converter Tool) . . . . . . . . . . . . . . 135
Tool Conversion Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Connected Components Workbench Ladder Diagram (Manual Conversion) . . . . . . . . . . . 139
Notes:
About This Publication This document serves as a guide for replacing your existing MicroLogix™ 1000, MicroLogix 1100,
MicroLogix 1200, or MicroLogix 1400 controller with a Micro800™ family of controllers.
The Micro800 family of controllers includes the Micro810®, Micro820®, Micro850®, and Micro870®
controllers.
Descriptions, wiring diagrams, dimensions, features, and specifications of the controllers are
provided to help you select the appropriate Micro800 controller to replace your MicroLogix
controller.
This document shows you how to use the software tools to select a suitable Micro800 controller,
and also how to convert your MicroLogix programs to work with the Micro800 controller.
Audience The intended audience of this document is owners of MicroLogix 1000, MicroLogix 1100, MicroLogix
1200, and MicroLogix 1400 controllers who are migrating to the Micro800 family of controllers, and
who are familiar with the RSLogix 500®/RSLogix™ Micro programming software. Knowledge of
programming in ladder language is expected to be able to program Micro800 systems effectively.
Required Software To complete the steps in this document, Connected Components Workbench™ software version 21
or later is required. As the main programming software for Micro800 systems. Connected
Components Workbench software provides a choice of IEC 61131-3 programming languages (ladder
diagram, function block diagram, structured text) with user-defined function block (UDFB) support
that optimizes machine control.
You need Connected Components Workbench software to write your ladder diagram, function block
diagram, or structured text programs, to execute the programs, and to see the results.
This document uses two features that are available in Connected Components Workbench software
version 12 or later.
The Converter tool can convert most RSLogix 500/RSLogix Micro instruction blocks. However, you
may need to modify the converted function blocks to confirm that they work properly. All
information that requires additional modifications are logged in a conversion report, and this
document shows you how to make the changes.
From IAB software version 9.8.2.2 onwards, MicroLogix 1400 controllers can migrate to Micro850
and Micro870 controllers.
Micro800 Simulator
The Micro800 Simulator can be used to perform testing and troubleshooting of a Connected
Components Workbench project, without a physical Micro800 controller.
Download Firmware, AOP, Download firmware, associated files (such as AOP, EDS, and DTM), and access product release
notes from the Product Compatibility and Download Center at rok.auto/pcdc.
EDS, and Other Files
Summary of Changes This publication contains the following new or updated information. This list includes substantive
updates only and is not intended to reflect all changes.
Topic Page
Updated template throughout
Removed Micro830 catalogs throughout
Removed Micro850 and Micro870 2080-LCx0 catalogs throughout
Added inclusive language statement 2
Added Hardware Migration using Integrated Architecture Builder section 8
Reorganized content in Chapter 1 - Migrate Your MicroLogix Controller to a Compatible Micro800 9…20
Controller
Added new Micro850 2080-L50E catalogs 9…19, 45
Added new Micro870 2080-L70E catalogs 9…20
Added instructions on converting MicroLogix 1400 controllers using IAB 25…35
Additional Resources These documents contain additional information concerning related products from Rockwell
Automation.
Resource Description
Micro800 Programmable Controllers General Instructions Reference Manual, Provides reference information about the instruction set available for developing programs for use
publication 2080-RM001 in Micro800 control systems.
Micro820 Programmable Controllers User Manual, publication 2080-UM005 A more detailed description of how to install and use your Micro820 programmable controllers.
Micro830, Micro850, and Micro870 Programmable Controllers User Manual, A more detailed description of how to install and use your Micro830, Micro850, and Micro870
publication 2080-UM002 programmable controllers.
Description of features, installation, wiring, and specifications for the Micro800 expansion I/O
Micro800 Expansion I/O Modules User Manual, publication 2080-UM003 modules.
Micro800 Plug-in Modules User Manual, publication 2080-UM004 Description of features, installation, wiring, and specifications for the Micro800 plug-in modules.
Micro800 Controllers: Getting Started with Motion Control Using a Simulated Provides instructions to implement a motion control project using Connected Components
Axis Quick Start, publication 2080-QS001 Workbench software.
Micro800 Controllers: Getting Started with CIP™ Client Messaging Quick Start, Provides instructions on how to use global variables with Micro800 controllers together with
publication 2080-QS002 PanelView™ Plus HMI terminals.
Micro800 Programmable Controllers: Getting Started with PanelView Plus Provides instructions on how to configure a Micro800 controller on FactoryTalk® Linx Gateway.
Quick Start, publication 2080-QS003
Configuring Micro800 Controllers on FactoryTalk Gateway Quick Start, Provides general guidelines for installing a Rockwell Automation industrial system.
publication 2080-QS005
Industrial Automation Wiring and Grounding Guidelines, publication 1770-4.1 Provides general guidelines for installing a Rockwell Automation industrial system.
Product Certifications website, rok.auto/certifications Provides declarations of conformity, certificates, and other certification details.
To migrate your existing MicroLogix controller system to a Micro800 controller system, you need to
understand your existing system requirements and then compare them to what is available in the
Micro800 family of products. To simplify the process, you can read through this chapter to
understand the migration options and process.
Figure 1 illustrates Micro800 controller capabilities based on performance, features, memory, and
I/O support.
Figure 1 - Consider Your MicroLogix Application
DNP3 support
DF1 support
Supports expansion modules
Supports plug-in modules and microSD™ cards
Motion control with pulse train output (PTO)
EtherNet/IP™ enabled
Class 1 implicit messaging support
Performance and features
Micro870 2080-L70E
Highest memory and I/O
Micro850 2080-L50E
3 axes of motion support
Micro820
Remote automation
Micro810
Smart relay
Memory and I/O
Table 1 lists specifications and applications for each Micro800 controller by application
requirement.
Table 1 - Select a Micro800 Controller
If You Need... Micro810 Micro820 Micro850 Micro870
Embedded digital I/O points 0 20 24 48 24
Maximum digital I/O 12 35 132 192 304
• USB programming port (with • USB programming port
• USB programming port
Communication options and • USB programming port 2080-REMLCD) • CIP Serial, DF1, Modbus RTU, ASCII
• CIP Serial, DF1, Modbus RTU, ASCII
protocols (with adapter) • CIP Serial, DF1, Modbus RTU, ASCII
• EtherNet/IP, Modbus TCP • EtherNet/IP, Modbus TCP • EtherNet/IP, Modbus TCP, DNP3(1)
Migrate MicroLogix 1000 This section helps you determine how to select and configure a suitable Micro820 controller for
your existing MicroLogix 1000 controller configuration.
Wiring Considerations
This section illustrates an example of wiring for your MicroLogix 1000 controller and how you can
migrate the wiring to a Micro800 controller. For a complete wiring guide for Micro800 controllers,
see Micro800 Programmable Controllers Installation Instructions, publication 2080-IN013.
Figure 2 - Compare Wiring for a 1761-L32BWA Controller and a 2080-L50E-48QWB Controller
1761-L32AAA 14…30 V DC
1761-L32AWA VDC + VDC VDC +
Com
1761-L32BWA VDC
Com
+ 24V – DC I/0 I/1 I/2 I/3 DC I/4 I/5 I/6 I/7 I/8 I/9 I/10 I/11 I/12 I/13 I/14 I/15 I/16 I/17 I/18 I/19
COM COM
DC OUT
85…264 VAC
VAC VAC VAC VAC VAC
L1 L2/N VDC O/0 VDC O/1 VDC O/2 O/3 VDC O/4 O/5 O/6 O/7 VDC O/8 O/9 O/10 O/11
CR CR CR CR CR CR CR CR CR CR
2080-L50E-48QWB
+DC a +DC b +DC c +DC d
-DC a -DC b -DC c -DC d
COM0 I-01 I-03 I-05 I-06 I-08 I-10 COM2 I-13 I-15 I-17 I-19 I-20 I-22 I-24 I-26
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
I-00 I-02 I-04 COM1 I-07 I-09 I-11 I-12 I-14 I-16 I-18 COM3 I-21 I-23 I-25 I-27
+DC24 CM0 CM1 CM2 CM3 CM4 CM5 CM6 CM7 O-08 O-10 CM8 O-13 O-15 O-16 O-18
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
-DC24 O-00 O-01 O-02 O-03 O-04 O-05 O-06 O-07 O-09 O-11 O-12 O-14 CM9 O-17 O-19
CR CR CR CR CR CR CR CR CR CR CR CR
+DC e
+DC j +DC k
-DC e L1 a L1 b L1 c +DC f +DC g +DC h
Additional Resources
Find publications with complete list of specifications, wiring diagrams, and other requirements.
Resource Description
MicroLogix 1000 Programmable Controllers Installation Instructions, Describes how to install and wire MicroLogix 1000 controllers.
publication 1761-IN001
MicroLogix 1000 Programmable Controllers User Manual, publication 1761-UM003 Describes how to configure and program MicroLogix 1000 controllers.
Micro800 Programmable Controllers Installation Instructions, publication 2080-IN013 Describes how to install and wire Micro810, Micro820, Micro850, and Micro870 controllers.
Micro800 Programmable Controller External AC Power Supply Installation Instructions, Describes how to install and wire an AC external power supply for Micro800 controllers.
publication 2080-IN011
MicroLogix 1000 Programmable Controllers Document Update, publication 1761-DU001. Explains the differences for input circuits capable of 24V AC or 24V DC operation.
Migrate MicroLogix 1100 This section helps you determine how to select and configure a suitable Micro820 or Micro850
controller for your existing MicroLogix 1100 controller configuration.
Wiring Considerations
This section illustrates an example of wiring for your MicroLogix 1100 controller and how you can
migrate the wiring to a Micro800 controller. For a complete wiring guide for Micro800 controllers,
see Micro800 Programmable Controllers Installation Instructions, publication 2080-IN013.
Figure 3 - Compare Wiring for a 1763-L16BBB Controller and a 2080-L50E-24QBB Controller
1763-L16BBB
+DCa +DCb L1c
-DC
+DC CR CR CR
Outputs
+ 24V - NOT VAC O/0 VAC O/1 NOT NOT DC O/2 O/3 O/4 O/5 DC NOT
DC IN USED VDC VDC USED USED 24V+ 24V- USED
2080-L50E-24QBB
Sourcing:+DC a Sourcing:-DC a Sourcing:+DC b Sourcing:-DC b
Sinking: -DC a Sinking: +DC a Sinking: -DC b Sinking: +DC b
L1 L2
2080-PS120-240VAC
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
N
I-00 I-02 I-04 I-06 COM1 I-09 I-11 I-13
CR CR
+DC d +DC e
-DC d -DC e
Additional Resources
Find publications with complete list of specifications, wiring diagrams, and other requirements.
Resource Description
MicroLogix 1100 Programmable Controllers Installation Instructions, Describes how to install and wire MicroLogix 1100 controllers.
publication 1763-IN001
MicroLogix 1100 Programmable Controllers User Manual, publication 1763-UM001 Describes how to configure and program MicroLogix 1100 controllers.
Micro800 Programmable Controllers Installation Instructions, publication 2080-IN013 Describes how to install and wire Micro810, Micro820, Micro850, and Micro870 controllers.
Micro800 Programmable Controller External AC Power Supply Installation Instructions, Describes how to install and wire an AC external power supply for Micro800 controllers.
publication 2080-IN011
Provides detailed specifications for Micro800 controllers, expansion I/O modules, plug-in
Micro800 Programmable Controllers Technical Data, publication 2080-TD001 modules, and accessories.
Migrate MicroLogix 1200 This section helps you determine how to select and configure a suitable Micro850 or Micro870
controller for your existing MicroLogix 1200 controller configuration.
Micro850(1) Micro870(2)
MicroLogix 1200 Controller
Controller Required Plug-in Module / Accessories Controller Required Plug-in Module / Accessories
1762-L24AWA • 2080-PS120-240VAC x 1
2080-L50E-24AWB
1762-L24AWAR • 2080-MEMBAK-RTC2 x 1
• 2085-ECR
2080-L70E-24AWB • 2080-PS120-240VAC x 1
1762-L40AWA • 2080-MEMBAK-RTC2 x 1
2080-L50E-48AWB
1762-L40AWAR
• 2085-IA8 x 1(4)
• 2080-PS120-240VAC x 1(3) • 2085-OW8 x 1
1762-L24BWA • 2080-MEMBAK-RTC2 x 1 • 2080-PS120-240VAC x 1
2080-L50E-24QWB
1762-L24BWAR • 2080-MEMBAK-RTC2 x 1
2080-L70E-24QWB • 2085-ECR
2080-L70E-24QWBK • 2080-PS120-240VAC x 1
1762-L40BWA 2080-L50E-48QWB • 2080-MEMBAK-RTC2 x 1
1762-L40BWAR
• 2085-IQ16 x 1
• 2085-OW8 x 1
• 2080-PS120-240VAC x 1
1762-L24BXB • 2080-MEMBAK-RTC2 x 1
2080-L50E-24QBB
1762-L24BXBR
• 2080-OW4I x 1 or 2085-OW8 x 1(5)
• 2080-MEMBAK-RTC2 x 1
• 2085-ECR 2080-L70E-24QBB • 2085-ECR
2080-L70E-24QBBK • 2080-PS120-240VAC x 1
1762-L40BXB • 2080-OW4I x 1 or 2085-OW8 x 1(5)
2080-L50E-48QBB • 2080-MEMBAK-RTC2 x 1
1762-L40BXBR
• 2080-OW4I x 1 or 2085-OW8 x 1(5)
• 2085-IQ16 x 1
(1) Use the Micro850 controller for up to four expansion modules.
(2) Use the Micro870 controller for more than four expansion modules.
(3) The 2080-PS120-240VAC power supply is required to convert AC power DC power. It is optional if you use an external power supply.
(4) To migrate from a 1762-L40AWA or 1762-L40AWAR, add 2085-IA8 and 2085-OW8 expansion I/O modules to fill the I/O gap.
(5) The 2080-L50E-24QBB, 2080-L50E-48QBB, 2080-L70E-24QBB, and 2080-L70E-24QBBK require additional relay modules if the embedded output of the MicroLogix 1200 uses relay output. Use either
the 2080-OW4I plug-in module or the 2085-OW8 expansion I/O module.
1762-L24BWA
COM
Wiring Considerations
This section illustrates an example of wiring for your MicroLogix 1200 controller and how you can
migrate the wiring to a Micro800 controller. For a complete wiring guide for Micro800 controllers,
see Micro800 Programmable Controllers Installation Instructions, publication 2080-IN013.
Figure 4 - Compare Wiring for a 1762-L40BWA Controller and a 2080-L50E-48QWB Controller
1762-L40BWA, 1762-L40BWAR
Sinking Inputs Sourcing Inputs
-DCb +DCb +DCb -DCb
-DCa -DCc
+DC +DCa
+DCc
+DC
+DCc -DC
-DC -DCa -DCa -DCb
-DCc -DCc
+DCa +DCb +DCa +DCc
L1d L1f
L2d L2e L2f
L2a L2b L2c
L2
Outputs L1
CR CR CR CR
VAC VAC OUT OUT OUT VAC OUT OUT OUT OUT VAC OUT OUT
L1 NEUT 0 1 2 DC 3 5 7 8 10 DC 5 13 15
VAC VAC VAC OUT OUT OUT VAC OUT OUT OUT OUT
DC 0 DC 1 DC 2 3 4 6 DC 4 9 11 12 14
CR CR CR CR
L2c
L2d L2e L2f
2080-L50E-48QWB
L1a L1b L1c L1e
COM0 I-01 I-03 I-05 I-06 I-08 I-10 COM2 I-13 I-15 I-17 I-19 I-20 I-22 I-24 I-26
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
I-00 I-02 I-04 COM1 I-07 I-09 I-11 I-12 I-14 I-16 I-18 COM3 I-21 I-23 I-25 I-27
+DC24 CM0 CM1 CM2 CM3 CM4 CM5 CM6 CM7 O-08 O-10 CM8 O-13 O-15 O-16 O-18
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
-DC24 O-00 O-01 O-02 O-03 O-04 O-05 O-06 O-07 O-09 O-11 O-12 O-14 CM9 O-17 O-19
CR CR CR CR CR CR CR CR CR CR CR CR
+DC e
+DC j +DC k
-DC e L1 a L1 b L1 c +DC f +DC g +DC h
Additional Resources
Find publications with complete lists of specifications, wiring diagrams, and other requirements.
Resource Description
MicroLogix 1200 Programmable Controllers Installation Instructions, publication 1762-IN006 Describes how to install and wire MicroLogix 1200 controllers.
MicroLogix 1200 Programmable Controllers User Manual, publication 1762-UM001 Describes how to configure and program MicroLogix 1200 controllers.
Describes how to install and wire Micro810, Micro820, Micro850, and Micro870
Micro800 Programmable Controllers Installation Instructions, publication 2080-IN013 controllers.
Micro800 Programmable Controller External AC Power Supply Installation Instructions, Describes how to install and wire an AC external power supply for Micro800
publication 2080-IN011 controllers.
Micro800 Digital Input, Output, and Combination Plug-in Modules Wiring Diagrams, publication Describes how to install and wire Micro800 digital plug-in modules.
2080-WD011
Micro800 Plug-in Modules User Manual, publication 2080-UM004 Describes how to configure and program Micro800 plug-in modules.
Migrate MicroLogix 1400 This section helps you determine how to select and configure a suitable Micro850 or Micro870
controller for your existing MicroLogix 1400 controller configuration.
Micro850(1) Micro870(2)
MicroLogix 1400 Controller
Controller Required Plug-in Module / Accessories Controller Required Plug-in Module / Accessories
• 2080-PS120-240VAC x 1(3) 2080-L70E-24AWB • 2080-PS120-240VAC x 1
1766-L32AWA 2080-L50E-24AWB 2080-L70E-24QWBN
• 2080-MEMBAK-RTC2 x 1 • 2080-MEMBAK-RTC2 x 1
• 2085-ECR 2080-L70E-24QWB • 2085-ECR
1766-L32BWA 2080-L50E-24QWB
• Additional plug-in or expansion I/O to 2080-L70E-24QWBN • Additional plug-in or expansion I/O to
match total 1766 embedded I/O density 2080-L70E-24QBB match total 1766 embedded I/O density
1766-L32BXB 2080-L50E-24QBB • 2080-OW4I x 1(4)
• 2080-OW4I x 1(4) 2080-L70E-24QBBN
• 2080-PS120-240VAC x 1 2080-L70E-24AWB • 2080-PS120-240VAC x 1
1766-L32AWAA 2080-L50E-24AWB 2080-L70E-24QWBN
• 2080-MEMBAK-RTC2 x 1 • 2080-MEMBAK-RTC2 x 1
• 2085-ECR 2080-L70E-24QWB • 2085-ECR
1766-L32BWAA 2080-L50E-24QWB • Additional plug-in or expansion I/O to • Additional plug-in or expansion I/O to
2080-L70E-24QWBN
match total 1766 embedded I/O density match total 1766 embedded I/O density
• 2080-IF4 x 1 or 2080-OF2 x 1(5) 2080-L70E-24QBB • 2080-IF4 x 1 or 2080-OF2 x 1(5)
1766-L32BXBA 2080-L50E-24QBB 2080-L70E-24QBBN
• 2080-OW4I x 1 or 2085-OW8 x 1(6) • 2080-OW4I x 1 or 2085-OW8 x 1(6)
(1) Use the Micro850 controller for up to four expansion modules.
(2) Use the Micro870 controller for more than four expansion modules.
(3) The 2080-PS120-240VAC power supply is required to convert AC power DC power. It is optional if you use an external power supply.
(4) The Micro850 and Micro870 controllers require additional relay modules if the embedded output of the 1766-L32BXB controller uses relay output.
(5) An analog plug-in is required to support the embedded analog capability of 1766-L32AWAA and 1766-L32BWAA controllers.
(6) The 2080-L50E-24QBB, 2080-L70E-24QBB, and 2080-L70E-24QBBN require additional relay modules if the embedded output of the MicroLogix 1400 uses relay output. Use either the 2080-OW4I
plug-in module or the 2085-OW8 expansion I/O module.
MicroLogix 1400 Table 9 - MicroLogix 1400, Micro850, and Micro870 Controller Dimensions
MicroLogix 1400 Controller A B C
1766-L32BWA
1766-L32AWA
C 1766-L32BXB
180 mm (7.087 in.) 87 mm (3.43 in.) 90 mm (3.54 in.)
1766-L32BWAA
1766-L32AWAA
B A
1766-L32BXBA
Micro850 - 24-point
Micro850 Controller A B C
2080-L50E-24AWB
2080-L50E-24QWB
158 mm (6.22 in.)
2080-L50E-24QVB
2080-L50E-24QBB
2080-L50E-48AWB 80 mm (3.15 in.) 90 mm (3.54 in.)
2080-L50E-48QWB
Micro850 - 48-point
2080-L50E-48QWBK 283 mm (9.37 in.)
2080-L50E-48QVB
2080-L50E-48QBB
Micro870 Controller A B C
2080-L70E-24AWB
2080-L70E-24QWB
Micro870 2080-L70E-24QWBN
A B 2080-L70E-24QWBK 157 mm (6.22 in.) 80 mm (3.15 in.) 90 mm (3.54 in.)
2080-L70E-24QBB
C 2080-L70E-24QBBN
2080-L70E-24QBBK
Wiring Considerations
This section illustrates an example of wiring for your MicroLogix 1400 controller and how you can
migrate the wiring to a Micro800 controller. For a complete wiring guide for Micro800 controllers,
see Micro800 Programmable Controllers Installation Instructions, publication 2080-IN013.
Figure 5 - Compare Wiring for a 1766-L32BXB Controller and a 2080-L70E-24QBB Controller
1766-L32BXB,
1766-L32BXBA Input terminal block
IN0 IN2 COM 1 IN5 IN7 IN8 IN10 COM 3 IN13 IN15 IN17 IN19 IV0(+) IV2(+)
COM 0 IN1 IN3 IN4 IN6 COM 2 IN9 IN11 IN12 IN14 IN16 IN18 COM IV1(+) IV3(+)
ANA
DC0 DC1 VDC2 OUT3 OUT5 OUT7 DC3 DC4 DC5 OUT11 OV0
VAC VAC VAC VAC VAC
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
I-00 I-02 I-04 I-06 COM1 I-09 I-11 I-13
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
-DC24 O-00 -CM0 O-02 O-04 O-06 O-08 -CM1
Note: If the MicroLogix 1400 controller uses analog on the input terminal, add a Micro800 analog plug-in to the Micro800 controller.
Additional Resources
Find publications with complete lists of specifications, wiring diagrams, and other requirements.
Resource Description
MicroLogix 1400 Programmable Controllers Installation Instructions, Describes how to install and wire MicroLogix 1400 controllers.
publication 1766-IN001
MicroLogix 1400 Programmable Controllers User Manual, publication 1766-UM001 Describes how to configure and program MicroLogix 1400 controllers.
Micro800 Programmable Controllers Installation Instructions, publication 2080-IN013 Describes how to install and wire Micro810, Micro820, Micro850, and Micro870 controllers.
Micro800 Programmable Controller External AC Power Supply Installation Instructions, Describes how to install and wire an AC external power supply for Micro800 controllers.
publication 2080-IN011
Micro800 Digital Input, Output, and Combination Plug-in Modules Wiring Diagrams, Describes how to install and wire Micro800 digital plug-in modules.
publication 2080-WD011
Micro800 Plug-in Modules User Manual, publication 2080-UM004 Describes how to configure and program Micro800 plug-in modules.
This chapter describes how to use the MicroLogix Migration Wizard within IAB software to assist
with converting your MicroLogix controller to a compatible controller. At the base level,
MicroLogix 1000, MicroLogix 1100, MicroLogix 1200, and MicroLogix 1400 controllers migrate to
Micro800 controllers. MicroLogix 1500 controllers migrate to MicroLogix 1400 controllers or
CompactLogix™ 5370 (L1/L2) controllers.
Generate Hardware Convert MicroLogix 1000, MicroLogix 1100, and MicroLogix 1200
Configuration Controllers to Micro800 Controllers
To convert your MicroLogix 1000, MicroLogix 1100, and MicroLogix 1200 system to a compatible
controller system, do the following:
1. Launch Integrated Architecture Builder software from Start —> Programs —> Rockwell
Automation —> Integrated Architecture Builder —> Integrated Architecture Builder.
Alternatively, you can double-click the IAB icon on your computer.
4. Enter a name into the Workspace Name field, such as ‘MicroLogix Migration Wizard’, and
click OK.
12. Once the hardware is generated, you can view your configuration in the Hardware tab.
The MicroLogix 1400 is added to the IAB project and the view is switched to the Hardware
View to display the choice. The Device List tab opens to the MicroLogix tab so that you can
drag-and-drop I/O modules to the MicroLogix 1400.
26 Rockwell Automation Publication 2080-RM002C-EN-E - March 2023
Chapter 2 Plan Hardware Migration with Integrated Architecture Builder
IAB software version 9.8.2.2 has a new Migrate to Micro800 button on the hardware
view toolbar. Do not select it at this point.
3. Use the Configure Chassis button to add expansion I/O or to change the MicroLogix 1400
catalog number.
To build an existing MicroLogix 1400 system and then migrate it to a Micro800 controller do the
following:
1. From the Hardware view, select Configure Chassis.
2. Set the Number of Modules to 7 using the up and down arrows as shown.
3. Select OK.
There are seven empty expansion module slots.
4. In the Device List window, expand the I/O Modules categories for the MicroLogix 1400 for
analog and digital I/O modules.
5. Drag-and-drop the first seven modules listed to the corresponding empty expansion I/O
slots in the Hardware View window.
1 2 3 4 5 6 7
In the Hardware View window, the MicroLogix 1400 controller is connected to an EtherNet/IP
network and RS-232 ASCII network.
1. Right-click on the controller and create a new EtherNet/IP network.
2. Connect the controller to the EtherNet/IP network by making the selections shown.
IAB switches to the Network View to show the MicroLogix 1400 connected to the newly
created EtherNet/IP network.
3. From the Device List view, expand Computers and Operator Interface —> Graphic Terminals
—> 2711R PanelView™ 800.
4. Drag-and-drop a 2711R-T10T Graphic Terminal (HMI device) to the Network View. The graphic
terminal is added to the systems and is connected to the network.
The MicroLogix 1400 system is also connected to a Serial ASCII network. To create and
connect the controller to a Serial ASCII network:
5. In the Hardware View window, right-click on the controller and select the items that are
shown to create and connect the controller to a Serial ASCII network.
7. In the Device List window, expand Generic devices, and drag-and-drop the device that is
shown to the network.
Not all third-party devices are included in IAB. To represent a SERIAL ASCII
device not in IAB, you can use a generic device.
The existing system setup is complete. To migrate the existing controller system that you must
select the following options:
1. From the Options menu, select Auto-recommend Software in BOM and unselect Exclude
Existing Components in BOM.
• The Auto-recommend Software in BOM option adds the appropriate software based
on the products in your IAB project for those software products that exist in the
Software Portal.
• The Exclude Existing Components in BOM option determines if the MicroLogix 1400
that is being migrated shows up in the bill of materials along with the new Micro800
hardware.
Click Migrate
to Micro800
The network requirements show that both EtherNet/IP and RS-232/RS-485 networks are
needed. Hover over the information icon to see more details. The network requirements are
used for selecting an appropriate Micro800 controller.
2. Under Digital I/O Requirements, exceptions display as notes. Be sure to read the notes.
The I/O channel count for each I/O type shows next to the I/O type. Hover over the
information icon to see how many I/O channels are embedded in the controller and how
many I/O channels are used by an expansion I/O module.
3. In the Workspace window, expand the MicroLogix 1400 to see how the migration dialog box
is populating the various I/O channel counts. Review the list carefully.
4. On the migration dialog box, select Continue.
IAB launches the Hardware Selection dialog of the Micro800 Wizard and pre-populates it
with the migration requirements. The migration wizard displays the default solution.
5. Use the drop-down menus to change the default migration solution. Consider the following
options:
• Both the Micro850 and Micro 870 controllers are viable solutions and both have a
built-in EtherNet/IP communication port.
• There are multiple Micro850 and Micro870 solutions.
• There are multiple analog I/O module solutions.
• The 2080-SERIALISOL module is added for RS-232 ASCII network support.
• Specialty modules can be added.
6. When done, select Finish on the Hardware Selection dialog box.
Migration Results
When the migration is complete, IAB switches to Hardware view. You can review the migrated
options by doing the following:
1. In the Workspace window, expand the folders.
2. Select the Micro850 controller from the list on the left to see its graphical representation to
the right.
Old MicroLogix
system
New Mico800
system
Both the existing MicroLogix 1400 and the migrated Micro850 are in the project. You can see
how the I/O requirements were migrated to the Micro850 controller by reviewing the list in
the tree view of the Workspace window.
To generate a project BOM for the converted controller system, do the following:
1. From the IAB menu, select Project BOM and select OK to display the generated Project bill of
materials dialog box.
2. If prompted, save the Project BOM.
Since you chose to unselect Exclude Existing Components in BOM in Set System Options on
page 30, both the migrated to and the migrated from controllers are included in the Project
BOM.
3. Select Close to exit the dialog.
To generate a project BOM without the existing MicroLogix 1400 controller system, do the following:
1. From the Options menu, select Exclude Existing Components in BOM.
2. From the IAB menu, select Project BOM and select OK to display the generated Project bill of
materials dialog box.
Rockwell Automation Publication 2080-RM002C-EN-E - March 2023 33
Chapter 2 Plan Hardware Migration with Integrated Architecture Builder
IMPORTANT All other existing devices remain in the Project BOM. If you want the
IAB project to retain knowledge of the existing system, you must
unselect the Exclude Existing Components in BOM option. If you
select the option, the IAB project file (.iab) loses all knowledge of the
existing MicroLogix 1400 system.
5. Select Close to exit the dialog.
In the Architecture View window, you can see both the Migrated From system (MicroLogix 1400) and
the Migrate To (Micro800) system. We recommend that you save and keep this version of the file.
You can create a favorite for the Micro800 chassis and then create a new IAB file with the newly
created favorite chassis. With this new IAB file, you can create and connect the controller to
whichever network and network devices that you need.
In the Network View and Architecture View windows, make text box notes for which network
devices you don’t need to purchase since they already exist.
Manually modify any BOM or Report to remove any existing devices. In this way, you have a
complete picture of the old system and the new system in two different IAB project files (.iab).
You can customize the report that is generated from the migration. For instance, you can include a
supplemental Material list as an appendix in the IAB report. To include the list, do the following:
1. From the Options menu, select Options —> Report Options —> Include Supplemental
Materials.
Notes:
Overview This chapter describes two ways that you can convert your existing MicroLogix project to a
Micro800 project – convert the project manually, or use the MicroLogix to Micro800 Converter tool.
Before You Begin There is a new feature in Connected Components Workbench software version 12 or later that
changes the instructions to be more similar to RSLogix 500/RSLogix Micro. This feature is called the
Logix theme and the purpose is to switch Connected Components Workbench software instructions
into RSLogix 500/RSLogix Micro instructions.
Program names must begin with a letter or underscore, followed by up to 127 letters, digits, or
single underscores. Use programming languages such as ladder logic, function block diagrams,
and structured text.
Up to 256 programs can be included in a project, depending on available controller memory. By
default, the programs are cyclic (executed once per cycle or scan). As each new program is added
to a project, it is assigned the next consecutive order number. When you start the Project Organizer
in Connected Components Workbench software, it displays the program icons based on this order.
You can view and modify an order number for a program from the program properties. However,
the Project Organizer does not show the new order until the next time the project is opened.
The Micro800 controller supports jumps within a program. Call a subroutine of code within a
program by encapsulating that code as a user-defined function (UDF) or user-defined function
block (UDFB). A UDF is similar to a traditional subroutine and uses less memory than a UDFB, while
a UDFB can have multiple instances. Although a UDFB can be executed within another UDFB, a
maximum nesting depth of five is supported. A compilation error occurs if this limit is exceeded.
This limit also applies to UDFs.
Alternatively, you can assign a program to an available interrupt and have it executed only when
the interrupt is triggered. A program assigned to the User Fault Routine runs once before the
controller goes into Fault mode.
Besides the User Fault Routine, Micro800 controllers also support two Selectable Timed Interrupts
(STI). STIs execute assigned programs once every setpoint interval (1…65535 ms).
The Global System Variables that are associated with cycles/scans are:
• __SYSVA_CYCLECNT – Cycle counter
• __SYSVA_TCYCURRENT – Current cycle time
• __SYSVA_TCYMAXIMUM – Maximum cycle time since last start.
Execution Rules
This section illustrates the execution of a program. The execution follows four main steps within a
loop. The loop duration is a cycle time for a program.
1. Read inputs 1
2. Execute POUs(a)/programs
2
3. Write outputs
4. Housekeeping (datalog, recipe, communications) 3
1
2
(a) Program Organizational Unit 3
When a cycle time is specified, a resource waits until this time has elapsed before starting the
execution of a new cycle. The Program Organization Unit (POU) execution time varies depending on
the number of active instructions. When a cycle exceeds the specified time, the loop continues to
execute the cycle but sets an overrun flag. In such a case, the application no longer runs in real
time.
When a cycle time is not specified, a resource performs all steps in the loop then restarts a new
cycle without waiting.
For more information, see Program Execution in Micro800 Controllers in the Micro830, Micro850,
and Micro870 Programmable Controllers User Manual, publication 2080-UM002.
High-Speed Counter
High-Speed Counter (HSC) is available in Micro800 controllers, however configuration and operation
is done through Connected Components Workbench software instructions. The more common HSC
configuration can be done from the software interface, however doing it through instructions gives
you access to all configuration options. See the HSC example under the Logix examples section
later in this chapter.
Logix Theme
The Logix theme can be selected from the navigation bar. When you change to the Logix theme, all
your ladder diagram instructions names are updated to how they were named in the RSLogix 500/
RSLogix Micro software.
The following example shows the difference in instruction names between the two themes.
Instruction in Default Theme
Interrupts
There are a few types of interrupts that are common to both the MicroLogix controller and the
Micro800 controller –The User Fault Routine, Event Input Interrupt (EII), Selectable Timed Interrupt
(STI), and High-Speed Counter (HSC) (applicable to embedded HSC only). In the Micro800 controller,
these interrupts are configurable under the controller branch. For more information on interrupts,
see the Connected Components Workbench software Help.
It is important to understand how to configure your own interrupt because the MicroLogix to
Micro800 Converter tool does not handle it. You have to identify and configure interrupts manually.
For an example of how to configure an interrupt, see Configure Interrupts on a Micro800 Controller
on page 129.
After you paste the code into your Connected Components Workbench project, there are cases
where you are required to make some changes manually. These cases are categorized as
supported instruction, semi-supported instruction, and unknown instructions. The following
sections briefly explain what to expect when you copy and paste a program.
Supported Instruction
This group of instructions have identical functions to their respective instruction in RSLogix 500/
RSLogix Micro software. Generally, you do not have to make any changes when you copy and paste
such code. Most of the operator type instructions work like this, such as ADD, SUB, EQU.
Semi-supported Instructions
This category applies to slightly more advanced instructions. Timer and counter are two such
instructions because when you copy and paste them into the Connected Components Workbench
software, some feature or parameter does not match. You must verify the logic and make any
necessary changes. For example, when you paste a PID instruction from RSLogix 500/RSLogix
Micro software to Connected Components Workbench software, the instruction is not identical. You
have to convert the parameters and its associated output in the program manually.
PID instruction in RSLogix 500/
RSLogix Micro software PID instruction in Connected Components Workbench software
Unsupported Instruction
When you see ‘UNK:xxx’ in the Ladder Text Input box, it means that the ‘xxx’ instruction is not
supported in Connected Components Workbench software. For example, program control
instructions such as JSR, SBR, and MCR are treated as unknown instructions (UNK) as they are not
required in Connected Components Workbench software.
Sometimes an unknown instruction can result from converting a semi-supported instruction. When
an RSLogix 500/RSLogix Micro instruction is converted to a Connected Components Workbench
instruction that has fewer parameters, the excess parameters are dropped and considered as
UNK. To determine how to configure the instruction, see the Connected Components Workbench
software Help.
TOF instruction in RSLogix 500/
RSLogix Micro software
What You Need You need the following software to perform the conversion.
• Connected Components Workbench software version 12 or later.
• RSLogix 500/RSLogix Micro software.
Convert Your Project with The general steps to convert your project with the MicroLogix to Micro800 Converter tool can be
summarized as follows:
the Converter Tool
1. Save the RSLogix 500/RSLogix Micro Project as an SLC File
2. Run the MicroLogix to Micro800 Converter Tool
3. Convert the SLC File to a Connected Components Workbench Project
4. Understand the Conversion Process
5. Resolve Compilation Errors
3. Click Save.
The Export SLC Format dialog box displays.
4. Click OK.
The Export Results dialog box displays.
IMPORTANT The converter tool only supports MicroLogix controllers. The tool does not
work with other controllers even if you convert their project files to .SLC
files.
For general information about the converter tool, see the MicroLogix to Micro800 Converter tool
Help.
5. Click Downloads.
The Downloads page displays.
6. Click the show downloads icon.
Argument Description
SourceSlcFilePath Provides the path to the .slc file to be converted.
TargetCatalogID Specifies the Catalog ID for the target controller.
Has a value of either True or False. Determines whether the instruction description
optionConcatenateComment is shortened to just the comment.
In the following example, the SLC file that is named ‘pick-and-place’ is converted for use with a
Micro850 controller (catalog number 2080-L50E-24QWB) and not to concatenate the instruction
descriptions.
When you convert a project, all embedded I/O are renamed automatically. For example, I:0/0 is
renamed to _IO_EM_DI_00. If all embedded points are converted properly, you do not need to
reassign any I/O.
MicroLogix embedded I/O terminals
When the target controller does not have enough embedded I/O, the converted variable name is marked with a warning sign.
There are some situations where you must reassign I/O. For example, when you migrate from a
40-point MicroLogix controller with five or six expansion I/O modules, to a 24-point Micro870
controller. Since only Micro870 controllers support only 24 embedded I/O points, you must assign
the remaining MicroLogix embedded I/O points to the Micro870 expansion I/O modules.
The converter tool version 5.0 does not reassign terminals on the expansion I/O modules
automatically. This behavior can cause confusion as the converter tool renames the terminals on
the modules to the Micro800 embedded I/O terminals, and results in duplicate outputs.
To resolve this error, you have to rename all expansion I/O addresses. A recommended method is
to create a Long data file (For example, L9) and rename all expansion I/O addresses to the bit
address of the data file. For example, rename the address I:6/31 to L9:6/31, retaining the slot and
channel number for reference.
With this method, when you migrate into Connected Components Workbench software, L9:6/31 is
renamed to L9[6].31. Since the slot and channel number information is converted into the new
array data format, it is easy to reassign them manually to the respective I/O terminal on the
Micro800 expansion module.
This address, L9[6].31 can be denoted as
channel 31 of the sixth expansion module on the
MicroLogix controller.
This method makes it easy to map the I/O onto a
Micro800 expansion module.
If the project is converted successfully, there is only one ladder diagram in your program file and
the rest of the ladder programs are located under the user-defined functions (UDFs) branch. The
converter tool converts subroutines into UDFs and your program calls these functions in the main
routine. However, if an interrupt initiates any of the subroutines, you must convert the interrupt
routine manually. See the Connected Components Workbench software Help on how to create an
interrupt program. You can also see Configure Interrupts on a Micro800 Controller on page 129 for
more information.
MicroLogix Instructions
Most of the compilation errors are generated due to instructions. Not all MicroLogix instructions
have their equivalent in Micro800 instructions. Some instructions are similar but have differences
that require minor changes to make the Micro800 instructions behave the same as the MicroLogix
instruction.
The help file for the converter tool contains a list of the supported and unsupported MicroLogix
instructions. Unsupported instructions are probably not needed anymore due to the difference in
design between MicroLogix controllers and Micro800 controllers. For supported instructions, there
are a few categories as described here.
• Direct Replacement
MicroLogix instructions that fall under this category are basic instructions such as coil,
contact, and basic math instructions such as ADD, SUB, MUL.
• Similar Replacement
MicroLogix instructions that fall under this category means that the same instruction is
available in Micro800 controllers, but the instruction has less or more parameters. The
Micro800 instructions function slightly differently, but they can easily be configured to
achieve the same result as the MicroLogix instructions. Examples of similar instructions are
ONS, OSF, OSR, counter, and timer.
• UDFB Placeholder
MicroLogix instructions that fall under this category require more effort to resolve. For
example, the MicroLogix PWM instruction. A UDFB placeholder is a function block without
code, or empty function block. Since a Micro800 controller has its own timer, you are
expected to use this timer to develop your own PWM function within the block.
Alternatively, an example of the Micro800 PWM UDFB code is available on the Rockwell
Automation Sample Code Library at https://www.rockwellautomation.com/en-us/support/
product/product-downloads/application-code-library/sample-code.html.
This code is not identical to the MicroLogix PWM instruction, but you can use it as a guide to
configure the UDFB to suit your application.
• UDFB Replacement
MicroLogix instructions that fall under this category are replaced automatically by the
converter tool. UDFBs that replace supported MicroLogix instructions are developed to
behave as close as possible to the original instruction. Examples of UDFBs are
RA_TON_MICROLOGIX, RA_CTD_MICROLOGIX, and RA_CTU_MICROLOGIX.
The MicroLogix processors store all data in global data tables. You can access this data by
specifying the address of the data you want. A Micro800 controller supports data that is local to a
program, and data that is global to all tasks within the controller. A Micro800 controller can also
share data with other controllers, and instead of addresses, you use tags to access the data you
want.
Each MicroLogix data table file can store several words of related data. A Micro800 controller uses
arrays to store related data. The converter tool converts the MicroLogix data table files to Micro800
arrays.
With a Micro800 controller, you use a tag (alphanumeric name) to address data (variables). The
controller uses the tag name internally and does not need to cross-reference a physical address.
The following are some examples of how a MicroLogix data table is mapped to Micro800 variables.
Table 10 - Examples of MicroLogix Data Table to Micro800 Variables Mapping
MicroLogix Address Map to Micro800 Address
N7:500 N7[500]
N17:25 N17[25]
R6:100 R6[100]
C5:0 C5[0]
T4:6 T4[6]
I:0/5 _IO_EM_DI_05
O:0/4 _IO_EM_DO_04
For an extended list of examples, see the MicroLogix to Micro800 Converter tool Help.
User Documentation
If the Logix database is exported with your RSLogix project as a .SLC file, the symbols, address
comments, instruction comments, and rung comments in the program are preserved. There are
some limitations on the number of characters and descriptions for the comments. For example,
certain strings become concatenated. To understand more about this limitation, see the help file
for the converter tool for details.
Most of the time this error message appears due to the UDFB placeholders. Since most instructions
are converted into UDFBs, there may be many empty blocks that require your attention. Developing
the application code for these UDFBs helps to resolve a significant number of errors because a
particular UDFB function may be used multiple times within a project.
Instruction parameter data type is difference between MicroLogix controllers and Micro800
controllers. Many of the INT arrays that the converter tool creates are used in Micro800 instructions
that require a REAL data type. Resolving data type errors typically reduces the number of errors
significantly.
This variable arises from a converted project and is an indication that the MicroLogix address
format is not supported. The converter tool automatically renames the address to something that
is supported. You must resolve this error programmatically.
• By default, the Interrupt3_USER_FAULT POU program is created. From the RSLogix 500/
RSLogix Micro project, the MAIN_PROG (Lad 2) program is converted to “MAIN_PROG” in
Connected Components Workbench, while USER_FAULT (Lad 3), HSC_INT (Lad 4), STI_INT
(Lad 5), and Lad 6 to Lad 16 from the RSLogix 500/RSLogix Micro project are converted to a
UDFB.
• The converter tool adds other Interrupts (for example, Interrupt4_HSC_INT) if any HSC-
related instructions are present in the project.
You can configure it to an interrupt from the controller configuration section or delete the
interrupt program if the interrupt is not needed in the program.
• For this project, the Interrupt3_USER_FAULT can be deleted when not in use.
• For Jump to Subroutine (JSR), the converter tool creates a call to the UDFB (subroutine that
is called in JSR) in the program.
• The following data types are converted into an array (under Global Variables).
• The partially supported MicroLogix 1000 instructions are converted into a user-defined
function block (UDFB) that contains logic to perform the function of the MicroLogix
instruction.
See the converter tool Help for more information about the fully supported, partially
supported, and unsupported MicroLogix 1000 instructions.
• Results are displayed in the Output and Error List windows at the end of the conversion
process, and stored in the conversion log file.
The Error List window provides information about the items that did not fully convert from
your source project to your new project.
The Output window displays the location of the Conversion Report in CSV format, where you
can find all information from the Error list.
Once no errors are encountered and all warnings have been addressed, save the project and test
to see if it has the desired behavior.
See Appendix B, Original RSLogix 500/RSLogix Micro Ladder Diagram to view the pick-and-place
project in RSLogix 500/RSLogix Micro and in Connected Components Workbench after you have
used the converter tool.
Convert Your Project To migrate all your existing RSLogix 500/RSLogix Micro project code, you have to create a
Connected Component Workbench project with a similar structure. This section describes how to
Manually create your original program structure in the Connected Components Workbench software
environment and how to handle I/O addressing differences.
The general steps for manual conversion can be summarized as follows:
• Generate an Existing RSLogix 500/RSLogix Micro Project Report
• Create Equivalent Program Files
• Create Representative Data Files
• Create Equivalent Logic in Program File
Generate an Existing The RSLogix 500/RSLogix Micro report for your application contains information such as a program
file list, a data file list, and ladder diagrams. This information is used as reference when creating a
RSLogix 500/RSLogix Micro program in Connected Components Workbench software.
Project Report 1. Open the existing RSLogix 500/RSLogix Micro project.
2. Go to File Report Options.
Create Equivalent Program The program execution between MicroLogix controllers and Micro800 controllers is different. To
understand more about Micro800 controller execution order, review Overview of Program
Files Execution on page 37.
To create the equivalent program files for your RSLogix 500/RSLogix Micro project in Connected
Components Workbench software, do the following.
1. Launch the Connected Components Workbench software.
2. Click New.
3. Enter a project name and click Create.
Verify that the Add Device on Create checkbox is selected, otherwise the Add Device menu
does not appear.
4. From the Add Device catalog, expand Controllers and select your target controller.
See Generate Hardware Configuration on page 21 for how to generate a list of suitable target
controllers.
5. Select the latest firmware revision and click Add to Project.
6. In the Project Organizer, right-click Programs to add a ladder diagram as your main routine.
Note that subsequent programs are not subroutine. All programs under project organizer are
executed in sequential order, unless they are configured for STI or interrupt. You can incorporate
all the subroutine logic into one ladder diagram or create a UDF or UDFB to replace the subroutine.
Create Representative Use the report that is generated for your project as a reference to create representative data files
in Connected Components Workbench software by configuring the variables for the project. If your
Data Files configuration requires expansion I/O modules, do it here. This section provides some guidance for
configuring embedded I/O, binary file, and integer file. If your project requires you to configure
more data files for expansion I/O or other data types, use this section as a guide to continue
configuring the other data files.
The following data files are used in the examples in this section:
• Output (O0)
• Input (I1)
• Binary (B3)
• Integer (N7)
The section shows the steps for configuring the variables that are needed for programming Index
Addressing in Connected Components Workbench software. Programming steps are shown in
Program Index Addressing on page 56.
1. On the Project Organizer panel, under MAIN_PROG, double-click Local Variables.
Create Equivalent Logic in This section describes how to transfer the logic from an RSLogix 500/RSLogix Micro program. In
Connected Components Workbench software version 12 or later, copy and paste between the
Program File RSLogix 500/RSLogix Micro and Connected Components Workbench software environment is
supported. You can select all logic in an RSLogix 500/RSLogix Micro program, copy, and paste it
into a Connected Components Workbench program.
However not all instructions are supported. Therefore, some rungs do not appear as expected. You
must fix the unsupported instructions and syntax-related errors manually.
1. To paste code from an RSLogix 500/RSLogix Micro program, you must change Connected
Components Workbench software to the Logix theme. This theme allows the ladder editor to
understand the code that is being pasted.
2. Copy your main program (LAD 2) from the RSLogix project and paste it in your main ladder
diagram of your Connected Components Workbench project.
3. Since Connected Components Workbench software does not support the JSR instruction,
you must replace all JSRx instructions with their respective UDFB or UDF that were created
previously.
a. Double-click the JSRx instruction to bring up the Instruction Block Selector.
b. Search for the respective UDF or UDFB.
c. Select it and click OK to insert.
d. Repeat step 3 until all JSRx instructions have been replaced with their respective UDF or
UDFB.
4. Copy the logic from the subroutine and paste them into their respective UDFB or UDF that
were created for them.
Logix Examples Here are some program examples to show how things are done in the Connected Components
Workbench software environment. For more information, see the Connected Components
Workbench software Help.
The ladder program shown in Figure 6 enables indexed addressing in Connected Components
Workbench software.
Figure 6 - Enable Indexed Addressing
1. Add a rung.
On the Toolbox panel, double-click Rung. A new rung displays.
On the Toolbox panel, drag Branch and place it above the + (Addition) instruction block.
3. On the Branch, place a MOV instruction block with the following parameters:
• i1 = N7[Offset_Value]
• o1 = N7[2]
This instruction block allows the program to move the data selected based on the
Offset_Address to N7[2].
2. Add a rung. This rung is used to add the Timer Done bit.
3. On the blank rung, add the following elements and their respective variables:
• Reset Coil = _IO_EM_DO_02
• Set Coil = _IO_EM_DO_01
• Direct Contact = TON_1.Q
The following graphic shows the converted rung that uses the TON instruction in Connected
Components Workbench software:
In RSLogix 500/RSLogix Micro software, the HSL instruction is required to configure the low and
high presets, the output patterns, and mask bit patterns.
In Connected Components Workbench software, only the HSC instruction is required. It can be used
to start/stop HSC counter, to refresh HSC status, to reload HSC setting, and to reset HSC
accumulator.
For more information, See the chapter “Use the High-Speed Counter and Programmable Limit
Switch” in the Micro830, Micro850, and Micro870 Programmable Controllers User Manual,
publication 2080-UM002.
1. Add a rung. This rung is used to add the HSC instruction block.
2. On the blank rung, add the HSC instruction block with the following parameters:
Table 14 - HSC Instruction Block Parameters
Parameter Value (Example) Description
HscCmd hs_0 HSC Commands
HscApp... hsapp_0 HSC Configuration data
HscStsln... hsstats_0 HSC Status information
PlsData hsp_0 Programmable Limit Switch Data
Sts (blank) HSC function block execution status
The following rung shows the HSC instruction that is created in Connected Components
Workbench software:
3. Add a rung. This rung is used to add the ANY_TO_UDINT and MOV instruction blocks.
4. On the blank rung, add the HSC and MOV instruction blocks with the following parameters:
Table 15 - HSC and MOV Instruction Block Parameters
Instruction Parameter Values Details
i1 N7[0]
ANY_TO_UDINT Output Mask
o1 hsapp_0.OutputMask
i1 N7[1]
ANY_TO_UDINT High Preset Output
o1 hsapp_0.HPOutput
i1 N7[2]
ANY_TO_DINT High Preset Setting
o1 hsapp_0.HPSetting
Verify that proper values for the variables OFSetting, HPSetting, and UFSetting are set before
triggering Start/Run for the HSC. Otherwise, the controller is faulted. It is optional to set a
value for LPSetting for certain counting modes.
The following rung shows the data assignment to the required HSC parameters.
Before you enable the HSC function block, verify that HscCmd has been set to a valid value from
1…4. Otherwise, the controller is faulted.
Rockwell Automation Publication 2080-RM002C-EN-E - March 2023 61
Chapter 3 Convert a MicroLogix Project to a Micro800 Project
Build and Test Your Project After you have created the equivalent RSLogix 500/RSLogix Micro program in Connected
Components Workbench software, you must build and verify your project. Use an actual controller,
or the Micro800 Simulator feature that is available in Connected Components Workbench software
version 12 or later to perform the test. Depending on the method that you select, see the
corresponding section for instructions on how to perform the test.
• Test Project With the Micro800 Simulator
• Test Project With a Physical Controller
b. Click the ‘Synchronize’ icon from the toolbar to sync your I/O configuration with the
Simulator.
4. When the Micro800 Simulator is powered on, it appears in the FactoryTalk® Linx and
RSLinx® software. You can download a project to the Simulator as though it is a physical
Micro800 controller.
a. Right-click the controller and select Download.
b. Select the Micro800 Simulator in the RSLinx Connection Browser and click OK.
You cannot manipulate digital and analog outputs in the simulation environment because
the program controls them.
6. Click Device —> Exit to close the Simulator.
The Output window displays. The build result should show zero errors.
2. Download the project to the controller by selecting Device —>Download from the menu bar.
5. Click Yes to put the controller into RUN mode to test the program.
6. On the Project Organizer panel, double-click Main_PROG to show the ladder program.
Active rungs are displayed in red and inactive rungs in blue. You can monitor the live values
in the program.
The program goes into Debug mode for Connected Components Workbench software
version 8 or later.
Notes:
Overview The purpose of this chapter is to identify the functional difference between the Relay Ladder Logic
(RLL) instructions of the RSLogix 500 and RSLogix Micro and Connected Components Workbench
software. The RSLogix 500 and RSLogix Micro softwares are ladder logic programming packages
for the MicroLogix processors. Connected Components Workbench software is used to develop
programs for Micro800 controllers.
The comparison only identifies the logic and behavioral differences and does not explain each
instruction in detail. See the reference manual for more details.
Definitions, Acronyms, and See the following table for definitions of terms used in this chapter.
Abbreviations Term Definition
RLL Relay Ladder Logic
CCW Connected Components Workbench software
MSB Most Significant Bit
Description
Behavioral Differences
1. The Connected Components Workbench SHL instruction shifts one 32-bit data field. But the
RSLogix BSL instruction can shift any size of bits; (for example, 34-bit or 48-bit field sizes)
by 1.
Example: With the following ladder example, the program shifts a 34-bit data field from the
B3 data file:
2. Bits continue to shift until the MSB reaches the 15th bit position in the Binary Data File.
3. The shift operation clears the index register S:24 to zero.
Parameter
CS - Comms
Long Word
Immediate
IOS - I/O
Element
Indirect
MG, PD
RI/RIX
T, C, R
Direct
Word
RTC
HSC
LCD
MMI
PLS
BHI
STI
Bit
EII
ST
N
O
B
S
L
I
File • • • • • • • • • •
Control (2) • •
Length • •
Source • • • • • • • • •
(1) See Important note about indirect addressing.
(2) Control file only. Not valid for Timers and Counters.
IMPORTANT You cannot use indirect addressing with: S, MG, PD, RTC, HSC, PTOX, PWMX,
STI, EII, BHI, MMI, CS, IOS, and DLS files.
DWORD
STRING
LWORD
LREAL
UDINT
USINT
ULINT
WORD
BOOL
REAL
BYTE
DATE
UINT
DINT
TIME
SINT
LINT
INT
EN •
IN •
NbS •
ENO
SHL • •
BSR
Description
Behavioral Differences
1. The Connected Components Workbench SHR instruction shifts one 32-bit data field. But the
RSLogix BSR instruction can shift any size of bits (for example, 34-bit or 48-bit field sizes) by
1.
Example: With the following ladder example, the program shifts a 34-bit data field from the
B3 data file:
2. The number of bits in the bit array, up to 1680 bits. A length value of 0 causes the input bit to
be transferred to the UL bit.
3. The shift operation clears the index register S:24 to zero.
Parameter
CS - Comms
Long Word
Immediate
IOS - I/O
Element
Indirect
MG, PD
RI/RIX
T, C, R
Direct
Word
HSC
RTC
LCD
MMI
PLS
BHI
STI
Bit
EII
ST
N
O
B
S
F
L
I
File • • • • • • • • • •
Control (2) • •
Length • •
Source • • • • • • • • •
(1) See Important note about indirect addressing.
(2) Control file only. Not valid for Timers and Counters.
IMPORTANT You cannot use indirect addressing with: S, MG, PD, RTC, HSC, PTOX, PWMX,
STI, EII, BHI, MMI, CS, IOS, and DLS files.
STRING
LWORD
LREAL
UDINT
ULINT
USINT
WORD
BOOL
REAL
BYTE
DATE
UINT
DINT
TIME
SINT
LINT
INT
EN •
IN •
NbS •
ENO
SHL • •
Communication MSG
The MSG instruction is an output instruction that allows the controller to initiate an exchange of
data with other devices. The relationship with the other devices can be either peer-to-peer
communication or master-to-slave communication. The type of communication that a particular
application requires determine the programming configuration requirements of the MSG
instruction.
Communication Considerations
See the following chart for serial port and EtherNet/IP communications from MicroLogix 1000
controllers to Micro820/Micro850 controllers:
Table 22 - EtherNet/IP Communications from MicroLogix 1000 Controllers to Micro820/Micro850 Controllers
RS-232 Communication (MicroLogix 1000) Description Micro820 Micro850
CIP Serial (embedded serial port/ CIP Serial (embedded serial port/
DF1 full-duplex (all 1761) Point-to-point 2080-SERIALISOL plug-in) 2080-SERIALISOL plug-in)
Single master, multiple slaves up to 255
DF1 half-duplex (1761 series D and later, 1761
devices Modbus RTU (embedded serial port/ Modbus RTU (embedded serial port/
analog controllers) Baud (300...38.4 kbps) 2080-SERIALISOL plug-in) 2080-SERIALISOL plug-in)
slave to slave messaging
DH-485 half-duplex (series C and later, 1761 RS-485, up to 32 devices Modbus RTU (embedded serial port/ Modbus RTU (embedded serial port/
analog controllers), requires 1761-NET-AIC Baud (9600/19200) 2080-SERIALISOL plug-in) 2080-SERIALISOL plug-in)
Ethernet Communication (MicroLogix 1000) Description Micro820 Micro850
Requires 1761-NET-ENI — Embedded Ethernet Embedded Ethernet
For MicroLogix 1000 controllers, the MSG instruction is an output instruction that transfers data
from one node to another on the DH-485 communication network. The instruction can be
programmed as a write or read message. The target device can be another SLC™ 500 processor on
the network, or a non-SLC 500 device, using the common interface file (485CIF file 9 in SLC 500
processors). The 485CIF protocol is also used for PLC-2® type messages.
For Micro800 controllers, see the following table for supported communication instructions.
Table 23 - Supported Communication Instructions
Function Block Description
MSG_CIPGENERIC Send a CIP generic explicit message.
MSG_CIPSYMBOLIC Send a CIP symbolic explicit message.
MSG_MODBUS Send a Modbus message.
MSG_MODBUS2 Send a MODBUS/TCP message over an Ethernet Channel.
The following table lists the communication protocols that the Modbus and CIP message function
blocks support.
Table 24 - Supported Modbus and CIP Message Communication Protocols
Messaging Protocol Communication Media Use this Function Block
Through a Serial port that is configured
Modbus/RTU client and server MSG_MODBUS
as Modbus RTU
Over the Ethernet instead of through a
Modbus/TCP client and server MSG_MODBUS2
serial port
Through an embedded Ethernet MSG_CIPSYMBOLIC
EtherNet/IP client and server channel MSG_CIPGENERIC
CIP Serial client and server Ethernet cable or Serial cable MSG_CIPSYMBOLIC
Through an RS-232 port configured
ASCII See ASCII serial port instructions
with an ASCII driver
Comparison The MicroLogix supported data types for EQU, NEQ, GRT, LES, GEQ, and LEQ are as follows:
Table 25 - EQU, NEQ, GRT, LES, GEQ, and LEQ Instructions – Valid Addressing Modes and File Types
Address
Data Files Function Files(1) Address Level
Mode(2)
CS - Comms
Long Word
Immediate
IOS - I/O
Element
Indirect
MG, PD
RI/RIX
HSC(3)
T, C, R
Direct
Word
RTC
LCD
MMI
PLS
BHI
STI
Bit
EII
ST
N
O
B
S
L
I
Source A • • • • • • • • • • • • • • • • • • • • • • • • •
Source B • • • • • • • • • • • • • • • • • • • • • • • • •
(1) PTOX and PWMX files are only for use with MicroLogix 1400 BXB or BXBA unit.
(2) See Important note about indirect addressing.
(3) Only use the High-Speed Counter Accumulator (HSC.ACC) for Source A in GRT, LES, GEQ, and LEQ instructions.
IMPORTANT You cannot use indirect addressing with: S, MG, PD, RTC, HSC, PTOX, PWMX,
STI, EII, BHI, MMI, CS, IOS, and DLS files.
EQU
Description
Behavioral Differences
None
DWORD
STRING
LWORD
LREAL
UDINT
USINT
ULINT
WORD
BOOL
REAL
BYTE
DATE
UINT
DINT
TIME
SINT
LINT
INT
EN •
i1 • • • • • • • • • • • • • • •(1) • •
i2 • • • • • • • • • • • • • • •(1) • •
ENO •
o1 •
(1) The Time input applies to the ST, LD, and FBD languages.
NEQ
Description
Behavioral Differences
None
DWORD
STRING
LWORD
LREAL
UDINT
USINT
ULINT
WORD
BOOL
REAL
BYTE
DATE
UINT
DINT
TIME
SINT
LINT
INT
EN •
i1 • • • • • • • • • • • • • • • • •
i2 • • • • • • • • • • • • • • • • •
ENO •
o1 •
LES
Description
This instruction checks whether one value is less than another value.
Figure 11 - LES Functional Block Diagram
Behavioral Differences
None
DWORD
STRING
LWORD
LREAL
UDINT
USINT
ULINT
WORD
BOOL
REAL
BYTE
DATE
UINT
DINT
TIME
SINT
LINT
INT
EN •
i1 • • • • • • • • • • • • • • • •
i2 • • • • • • • • • • • • • • • •
ENO •
o1 •
LEQ
Description
This instruction checks whether one value is less than or equal to another value.
Figure 12 - LEQ Functional Block Diagram
RSLogix 500/RSLogix Micro Connected Components Workbench
Behavioral Differences
None
Immediate
Parameter
DWORD
STRING
LWORD
LREAL
UDINT
Direct
USINT
WORD
ULINT
BOOL
REAL
BYTE
DATE
UINT
TIME
DINT
SINT
LINT
INT
EN •
i1 • • • • • • • • • • • • • • •(1) • •
i2 • • • • • • • • • • • • • • •(1) • •
ENO •
o1 •
(1) The Time input applies to the ST, LD, and FBD languages.
GRT
Description
This instruction checks whether one value is greater than another value.
Figure 13 - GRT Functional Block Diagram
RSLogix 500/RSLogix Micro Connected Components Workbench
Behavioral Differences
None
DWORD
STRING
LWORD
LREAL
UDINT
USINT
ULINT
WORD
BOOL
REAL
BYTE
DATE
UINT
DINT
TIME
SINT
LINT
INT
EN •
i1 • • • • • • • • • • • • • • • • •
i2 • • • • • • • • • • • • • • • • •
ENO •
o1 •
GEQ
Description
This instruction checks whether one value is greater than or equal to another value.
Figure 14 - GEQ Functional Block Diagram
RSLogix 500/RSLogix Micro Connected Components Workbench
Behavioral Differences
None
DWORD
STRING
LWORD
LREAL
UDINT
USINT
ULINT
WORD
BOOL
REAL
BYTE
DATE
UINT
DINT
TIME
SINT
LINT
INT
EN •
i1 • • • • • • • • • • • • • • • • •
i2 • • • • • • • • • • • • • • • • •
ENO •
o1 •
LIM
Description
This instruction is used to compare a value with defined lower and upper limits.
Figure 15 - LIM Functional Block Diagram
RSLogix 500/RSLogix Micro Connected Components Workbench
Behavioral Differences
The behavioral differences between MicroLogix controllers and Micro800 controllers are as follows:
The output is TRUE when the Test value is within or equal to the Lower and Upper limit, The behavior of the output Q is shown according to the following graph:
that is
The output is FALSE when the Test value is within the Upper and Lower limit, that is The behavior of the output Q is shown according to the following graph:
CS - Comms
Long Word
Immediate
IOS - I/O
Element
Indirect
MG, PD
RI/RIX
T, C, R
Direct
Word
HSC
RTC
LCD
MMI
PLS
BHI
STI
Bit
EII
ST
N
O
B
S
L
I
Low Limit • • • • • • • • • • • • • • • • • • • • • • • • •
Test • • • • • • • • • • • • • • • • • • • • • • • • •
High Limit • • • • • • • • • • • • • • • • • • • • • • • • •
(1) PTOX and PWMX files are only for use with MicroLogix 1400 BXB or BXBA unit.
(2) See Important note about indirect addressing.
IMPORTANT You cannot use indirect addressing with: S, MG, PD, RTC, HSC, PTOX, PWMX,
STI, EII, BHI, MMI, CS, IOS, and DLS files.
DWORD
STRING
LWORD
LREAL
UDINT
USINT
ULINT
WORD
BOOL
REAL
BYTE
DATE
UINT
DINT
TIME
SINT
LINT
INT
EN •
H •
X •
L •
EPS •
QH • •
Q •
QL •
Control JMP
Description
Jump to label.
Figure 16 - JMP Functional Block Diagram
RSLogix 500/RSLogix Micro Connected Components Workbench
None
Behavioral Differences
None
Not applicable
LBL
Description
Labels are used as a target for jump instructions or to control the execution of the diagram.
Figure 17 - LBL Functional Block Diagram
RSLogix 500/RSLogix Micro Connected Components Workbench
None
Behavioral Differences
None
Not applicable
RET
Description
This output instruction marks the end of subroutine execution or the end of the subroutine file.
Figure 18 - RET Functional Block Diagram
RSLogix 500/RSLogix Micro Connected Components Workbench
None
Behavioral Differences
None
Not applicable
SUS
Description
Behavioral Differences
Not applicable
Table 45 - Supported Data Types in Micro800 Controllers
Data Type
Parameter
DWORD
STRING
LWORD
LREAL
UDINT
USINT
WORD
ULINT
BOOL
REAL
BYTE
DATE
UINT
DINT
TIME
SINT
LINT
INT
EN/ENABLE •
SusID •
ENO •
TND
Description
This instruction is used to debug a program progressively, or conditionally omit the balance of your
current program file or subroutines.
Figure 20 - TND Functional Block Diagram
RSLogix 500/RSLogix Micro Connected Components Workbench
None
Behavioral Differences
When using a MicroLogix controller, do not execute this instruction from the user error fault routine
(file 3), high-speed counter routine (file 4), or selectable timed routine (file 5), otherwise a fault
(major fault 0035) occurs.
Not applicable
Table 47 - Supported Data Types in Micro800 Controllers
Data Type
Parameter
DWORD
STRING
LWORD
LREAL
UDINT
USINT
ULINT
WORD
BOOL
REAL
BYTE
DATE
UINT
DINT
TIME
SINT
LINT
INT
EN •
TND •
ENO •
Description
This instruction is used to update the input data without waiting for the next input scan to begin.
Behavioral Differences
CS - Comms
Parameter
Long Word
Immediate
IOS - I/O
Element
Indirect
MG, PD
RI/RIX
T, C, R
Direct
Word
HSC
RTC
LCD
MMI
PLS
BHI
STI
Bit
EII
ST
N
O
B
S
L
I
Slot • • • •
Mask • • • • • • • • •
Length •
DWORD
STRING
LWORD
LREAL
UDINT
USINT
WORD
ULINT
BOOL
REAL
BYTE
DATE
UINT
TIME
DINT
SINT
LINT
INT
EN/ENABLE •
InputType •
InputSlot •
Sts •
ENO •
IOM
Description
This instruction is used to update the outputs without waiting for the next output scan.
Figure 22 - IOM Functional Block Diagram
RSLogix 500/RSLogix Micro Connected Components Workbench
Behavioral Differences
CS - Comms
Parameter
Long Word
Immediate
IOS - I/O
Element
Indirect
MG, PD
RI/RIX
T, C, R
Direct
Word
HSC
RTC
LCD
MMI
PLS
BHI
STI
Bit
EII
ST
N
O
B
S
L
I
Slot • • • •
Mask • • • • • • • • •
Length •
STRING
LWORD
LREAL
UDINT
USINT
WORD
ULINT
BOOL
REAL
BYTE
DATE
UINT
DINT
TIME
SINT
LINT
INT
EN/ENABLE •
OutputType •
OutputSlot •
Sts •
ENO •
Disable timer.
None
Behavioral Differences
None
Not applicable
Table 55 - Supported Data Types in Micro800 Controllers
Data Type
Parameter
DWORD
STRING
LWORD
LREAL
UDINT
USINT
WORD
ULINT
BOOL
REAL
BYTE
DATE
UINT
TIME
DINT
SINT
LINT
INT
EN •
IRQType •
UID •
STE
Description
Enable timer.
None
Behavioral Differences
None
Not applicable
Table 57 - Supported Data Types in Micro800 Controllers
Data Type
Parameter
DWORD
STRING
LWORD
LREAL
UDINT
USINT
WORD
ULINT
BOOL
REAL
BYTE
DATE
UINT
DINT
TIME
SINT
LINT
INT
EN •
IRQType •
UID •
STS
Description
Configure timer.
None
Behavioral Differences
Not applicable
Table 59 - Supported Data Types in Micro800 Controllers
Data Type
Parameter
DWORD
STRING
LWORD
LREAL
UDINT
USINT
ULINT
WORD
BOOL
REAL
BYTE
DATE
UINT
DINT
TIME
SINT
LINT
INT
EN/ENABLE •
IRQType •
SetPoint •
STIS •
Description
If the source or destination is a String data type, the other party must also be a String data type, or
a USINT (UCHAR and BYTE) data type. If it is not, a data type mismatch is reported.
Behavioral Differences
The maximum length that can be copied depending on data type is as follows:
CS - Comms
Long Word
Immediate
IOS - I/O
Element
Indirect
MG, PD
RI/RIX
T, C, R
Direct
Word
RTC
HSC
LCD
MMI
PLS
BHI
STI
Bit
EII
ST
N
A
O
B
S
L
I
Source • • • • • • • • • • • • •
Destination • • • • • • • • • • • • •
Length •
(1) See Important note about indirect addressing.
IMPORTANT You cannot use indirect addressing with: S, MG, PD, RTC, HSC, PTOX, PWMX,
STI, EII, BHI, MMI, CS, IOS, and DLS files.
STRING
LWORD
LREAL
UDINT
USINT
ULINT
WORD
BOOL
REAL
BYTE
DATE
UINT
TIME
DINT
LINT
SINT
INT
EN/ENABLE •
Src • • • • • • • • • • • • • • • • • •
SrcOffst •
Dest • • • • • • • • • • • • • • • • •
DestOffset •
Length •
Swap •
STS •
ENO •
Math The MicroLogix supported data types for ADD, SUB, MUL, DIV, NEG, and CLR are as follows:
Table 64 - Math Instructions (ADD, SUB, MUL, DIV, NEG, CLR) Valid Addressing Modes and File Types
Address
Data Files Function Files(1) Address Level
Mode(3)
DLS - Data Log(2)
PTOX, PWMX
Parameter
CS - Comms
Long Word
Immediate
IOS - I/O
Element
Indirect
MG, PD
RI/RIX
T, C, R
Direct
Word
HSC
RTC
LCD
MMI
PLS
BHI
STI
Bit
EII
ST
N
O
B
S
L
I
Source A • • • • • • • • • • • • • • • • • • • • • • • • • •
Source B • • • • • • • • • • • • • • • • • • • • • • • • • •
Destination • • • • • • • • • • • • • • • • • • • •
(1) PTOX and PWMX files are only for use with MicroLogix 1400 BXB or BXBA unit.
(2) The Data Log Status file can only be used for the following math instructions: ADD, SUB, MUL, DIV, NEG, and SCP.
(3) See Important note about indirect addressing.
IMPORTANT You cannot use indirect addressing with: S, MG, PD, RTC, HSC, PTOX, PWMX,
STI, EII, BHI, MMI, CS, IOS, and DLS files.
ADD
Description
Only supports the same data types for both input and output.
Behavioral Differences
DWORD
STRING
LWORD
LREAL
UDINT
USINT
ULINT
WORD
BOOL
REAL
BYTE
DATE
UINT
DINT
TIME
SINT
LINT
INT
EN •
i1 • • • • • • • • • • • • • • • •
i2 • • • • • • • • • • • • • • • •
o1 • • • • • • • • • • • • • • • •
ENO •
SUB
Description
Only supports the same data types for both input and output.
Behavioral Differences
For this instruction, the source has to be a word (16 bits), so all relevant data types with word sizes
are supported.
Table 70 - Supported Data Types in Micro800 Controllers
Data Type
Parameter
DWORD
STRING
LWORD
LREAL
UDINT
USINT
ULINT
WORD
BOOL
REAL
BYTE
DATE
UINT
TIME
DINT
SINT
LINT
INT
EN •
i1 • • • • • • • • • • • • • • •
i2 • • • • • • • • • • • • • • •
o1 • • • • • • • • • • • • • • •
ENO •
MUL
Description
Only supports the same data types for both input and output.
Behavioral Differences
DWORD
STRING
LWORD
LREAL
UDINT
USINT
ULINT
WORD
BOOL
REAL
BYTE
DATE
UINT
DINT
TIME
SINT
LINT
INT
EN •
i1 • • • • • • • • • • • • • •
i2 • • • • • • • • • • • • • •
o1 • • • • • • • • • • • • • •
ENO •
DIV
Description
Behavioral Differences
2. If the remainder is 0.5 or greater, the destination is rounded up. The unrounded quotient is
placed in the most significant word of the math register; the remainder is placed in the least
significant word.
3. This instruction impacts the status flags in the following way:
Table 75 - Status Flag Impact
With this Bit: The Controller:
S:0/0 Carry (C) Always resets.
Sets if division by zero or overflow is detected; otherwise resets. On overflow, the
minor error flag is also set. The value 32,767 is placed in the destination. If S:2/14
S:0/1 Overflow (V) (math overflow selection bit) is set, then the unsigned, truncated overflow
remains in the destination.
S:0/2 Zero (Z) Sets if result is zero, otherwise resets; undefined if overflow is set.
S:0/3 Sign (S) Sets if result is negative, otherwise resets; undefined if overflow is set.
DWORD
STRING
LWORD
LREAL
UDINT
USINT
ULINT
WORD
BOOL
REAL
BYTE
DATE
UINT
DINT
TIME
SINT
LINT
INT
EN •
i1 • • • • • • • • • • • • • •
i2 • • • • • • • • • • • • • •
o1 • • • • • • • • • • • • • •
ENO •
DDV
Description
Behavioral Differences
STRING
LWORD
LREAL
UDINT
ULINT
USINT
WORD
BOOL
REAL
BYTE
DATE
UINT
DINT
TIME
SINT
LINT
INT
EN •
i1 • • • • • • • • • • • • • •
i2 • • • • • • • • • • • • • •
o1 • • • • • • • • • • • • • •
ENO •
NEG
Description
Both the input and the output must be of the same data type.
Behavioral Differences
STRING
LWORD
LREAL
UDINT
USINT
WORD
ULINT
BOOL
REAL
BYTE
DATE
UINT
DINT
TIME
SINT
LINT
INT
EN •
i1 • • • • • •
o1 • • • • • •
ENO •
SQR
Description
Behavioral Differences
CS - Comms
Long Word
Immediate
IOS - I/O
Element
Indirect
MG, PD
RI/RIX
T, C, R
Direct
Word
HSC
RTC
LCD
MMI
PLS
BHI
STI
Bit
EII
ST
N
O
B
S
F
L
I
Source • • • • • • • • • • • • •
Destination • • • • • • • • • • • •
(1) See Important note about indirect addressing.
IMPORTANT You cannot use indirect addressing with: S, MG, PD, RTC, HSC, PTOX, PWMX,
STI, EII, BHI, MMI, CS, IOS, and DLS files.
DWORD
STRING
LWORD
LREAL
UDINT
USINT
ULINT
WORD
BOOL
REAL
BYTE
DATE
UINT
DINT
TIME
SINT
LINT
INT
EN •
IN •
SQRT •
ENO •
Move and Logical The MicroLogix supported data types for AND, OR, XOR and NOT are as follows:
Table 87 - Logical Instructions Valid Addressing Modes and File Types
Address
Data Files Function Files(1) Address Level
Mode(2)
Parameter
CS - Comms
Long Word
Immediate
IOS - I/O
Element
Indirect
MG, PD
RI/RIX
T, C, R
Direct
Word
RTC
HSC
LCD
MMI
PLS
BHI
STI
Bit
EII
ST
N
O
B
S
L
I
Source A • • • • • • • • • • • • • • • • • • • • • • • • •
(3) • • • • • • • • • • • • • • • • • • • • • • • • •
Source B
Destination • • • • • • • • • • • • • • • • • •
(1) PTOX and PWMX files are valid for MicroLogix 1400 BXB or BXBA unit.
(2) See Important note about indirect addressing.
(3) Source B does not apply to the NOT instruction. The NOT instruction only has one source value.
IMPORTANT You cannot use indirect addressing with: S, MG, PD, RTC, HSC, PTOX, PWMX,
STI, EII, BHI, MMI, CS, IOS, and DLS files.
STRING
LWORD
LREAL
UDINT
ULINT
USINT
WORD
BOOL
REAL
BYTE
DATE
UINT
DINT
TIME
SINT
LINT
INT
EN •
i1 • • • • • • • • • • • • • • • • • •
o1 • • • • • • • • • • • • • • • • • •
ENO •
MOV
Description
Only supports same data types for both input and output.
Behavioral Differences
Parameter
CS - Comms
Long Word
Immediate
IOS - I/O
Element
Indirect
MG, PD
RI/RIX
T, C, R
Direct
Word
HSC
RTC
LCD
MMI
PLS
BHI
STI
Bit
EII
ST
N
O
B
S
L
I
Source • • • • • • • • • • • • • • • • • • • • • • • • • • •
Destination • • • • • • • • • • • (3) (3) (3) (3) • • • •
(1) PTOX and PWMX files are valid for MicroLogix 1400 BXB or BXBA unit.
(2) See Important note about indirect addressing.
(3) Some elements can be written to. Consult the function file for details.
IMPORTANT You cannot use indirect addressing with: S, MG, PD, RTC, HSC, PTOX, PWMX,
STI, EII, BHI, MMI, CS, IOS, and DLS files.
DWORD
STRING
LWORD
LREAL
UDINT
USINT
ULINT
WORD
BOOL
REAL
BYTE
DATE
UINT
DINT
TIME
SINT
LINT
INT
EN •
i1 • • • • • • • • • • • • • • • • • •
o1 • • • • • • • • • • • • • • • • • •
ENO •
AND
Description
The Connected Components Workbench AND operator only supports BOOL values.
Behavioral Differences
DWORD
STRING
LWORD
LREAL
UDINT
USINT
ULINT
WORD
BOOL
REAL
BYTE
DATE
UINT
DINT
TIME
SINT
LINT
INT
EN •
i1 •
o1 •
ENO •
XOR
Description
The Connected Components Workbench XOR operator only supports BOOL values.
Behavioral Differences
DWORD
STRING
LWORD
LREAL
UDINT
USINT
ULINT
WORD
BOOL
REAL
BYTE
DATE
UINT
DINT
TIME
SINT
LINT
INT
EN •
i1 •
i2 •
o1 •
ENO •
OR
Description
Behavioral Differences
STRING
LWORD
LREAL
UDINT
USINT
ULINT
WORD
BOOL
REAL
BYTE
DATE
UINT
TIME
DINT
LINT
SINT
INT
EN •
i1 •
i2 •
o1 •
ENO •
NOT
Description
The Connected Components Workbench NOT operator only supports BOOL values.
Behavioral Differences
STRING
LWORD
LREAL
UDINT
USINT
ULINT
WORD
BOOL
REAL
BYTE
DATE
UINT
TIME
DINT
LINT
SINT
INT
EN •
i1 •
o1 •
ENO •
Descriptions
None
Behavioral Differences
None
Parameter
CS - Comms
Long Word
Immediate
IOS - I/O
Element
Indirect
MG, PD
RI/RIX
T, C, R
Direct
Word
HSC
RTC
LCD
MMI
PLS
BHI
STI
Bit
EII
ST
N
O
B
S
L
I
Operand Bit • • • • • • • • • • • • • • • • • • • • • •
(1) PTOX and PWMX files are only for use with MicroLogix 1400 BXB or BXBA unit.
(2) See Important note about indirect addressing.
IMPORTANT You cannot use indirect addressing with: S, MG, PD, RTC, HSC, PTOX, PWMX,
STI, EII, BHI, MMI, CS, IOS, and DLS files.
XIO
Description
Examine whether the bit field is OFF based on the rung state.
None
Behavioral Differences
None
Parameter CS - Comms
Long Word
Immediate
IOS - I/O
Element
Indirect
MG, PD
RI/RIX
T, C, R
Direct
Word
HSC
RTC
LCD
MMI
PLS
BHI
STI
Bit
EII
ST
N
O
B
S
L
I
Operand Bit • • • • • • • • • • • • • • • • • • • • • •
(1) PTOX and PWMX files are only for use with MicroLogix 1400 BXB or BXBA unit.
(2) See Important note about indirect addressing.
IMPORTANT You cannot use indirect addressing with: S, MG, PD, RTC, HSC, PTOX, PWMX,
STI, EII, BHI, MMI, CS, IOS, and DLS files.
OTE
Description
None
Behavioral Differences
The OTE is reset when programmed within an inactive or false Master Control Reset (MCR) zone.
Parameter
CS - Comms
Long Word
Immediate
IOS - I/O
Element
Indirect
MG, PD
RI/RIX
T, C, R
Direct
Word
HSC
RTC
LCD
MMI
PLS
BHI
STI
Bit
EII
ST
N
O
B
S
L
I
Destination Bit • • • • • • • • • • • • • • • • •
(1) PTOX and PWMX files are only for use with MicroLogix 1400 BXB or BXBA unit.
(2) See Important note about indirect addressing.
IMPORTANT You cannot use indirect addressing with: S, MG, PD, RTC, HSC, PTOX, PWMX,
STI, EII, BHI, MMI, CS, IOS, and DLS files.
OTL
Description
None
Behavioral Differences
Table 112 - OTL and OTU Instructions Valid Addressing Modes and File Types
Address
Data Files Function Files(1) Address Level
Mode(2)
CS - Comms
Long Word
Immediate
IOS - I/O
Element
Indirect
MG, PD
RI/RIX
T, C, R
Direct
Word
HSC
RTC
LCD
MMI
PLS
BHI
STI
Bit
EII
ST
N
O
B
S
L
I
Operand Bit • • • • • • • • • • • • • • • • •
(1) PTOX and PWMX files are only for use with MicroLogix 1400 BXB or BXBA unit.
(2) See Important note about indirect addressing.
IMPORTANT You cannot use indirect addressing with: S, MG, PD, RTC, HSC, PTOX, PWMX,
STI, EII, BHI, MMI, CS, IOS, and DLS files.
OTU
Description
None
Behavioral Differences
CS - Comms
Long Word
Immediate
IOS - I/O
Element
Indirect
MG, PD
RI/RIX
T, C, R
Direct
Word
HSC
RTC
LCD
MMI
PLS
BHI
STI
Bit
EII
ST
N
O
B
S
L
I
Operand Bit • • • • • • • • • • • • • • • • •
(1) PTOX and PWMX files are only for use with MicroLogix 1400 BXB or BXBA unit.
(2) See Important note about indirect addressing.
IMPORTANT You cannot use indirect addressing with: S, MG, PD, RTC, HSC, PTOX, PWMX,
STI, EII, BHI, MMI, CS, IOS, and DLS files.
OSR
Description
None
Behavioral Differences
None
CS - Comms
Parameter
Long Word
Immediate
IOS - I/O
Element
Indirect
MG, PD
RI/RIX
T, C, R
Direct
Word
HSC
RTC
LCD
MMI
PLS
BHI
STI
Bit
EII
ST
N
O
B
S
L
I
Storage Bit • • • •
Output Bit • • • • • • • •
STRING
LWORD
LREAL
UDINT
USINT
ULINT
WORD
BOOL
REAL
BYTE
DATE
UINT
TIME
DINT
SINT
LINT
INT
EN •
CLK •
Q •
ENO •
Timer and Counter The MicroLogix supported data types for TON, TOF, and RTO are as follows:
Table 118 - Timer Instructions Valid Addressing Modes and File Types
Address
Data Files(1) Function Files Mode Address Level
CS - Comms
Parameter
Long Word
Immediate
IOS - I/O
Element
Indirect
MG, PD
RI/RIX
T, C, R
Direct
Word
HSC
RTC
LCD
MMI
PLS
BHI
STI
Bit
EII
ST
N
O
B
S
L
I
Timer • • •
Time Base • •
Preset • •
Accumulator • •
(1) Valid for Timer Files only.
The MicroLogix supported data types for CTD and CTU are as follows:
Table 119 - CTD and CTU Instructions Valid Addressing Modes and File Types
Address
Data Files(1) Function Files Mode Address Level
CS - Comms
Parameter
Long Word
Immediate
IOS - I/O
Element
Indirect
MG, PD
RI/RIX
T, C, R
Direct
Word
HSC
RTC
LCD
MMI
PLS
BHI
STI
Bit
EII
ST
N
O
B
S
L
I
Counter • • •
Preset • •
Accumulator • •
(1) Valid for Counter Files only.
CTD
Description
Behavioral Differences
1. On the low to high transition of the rung, the counter counts down by 1. The done bit (DN) is
set as along as the Accum value is greater than or equal to the Preset value. It is cleared
when its value is less than the Preset value.
2. The counter in MicroLogix continues to count down even after reaching zero. This behavior
is NOT the same with Connected Components Workbench instruction. The underflow in
MicroLogix is SET only when the Accum value crosses over from -32,768 to 32,767 whereas
in Connected Components Workbench, the underflow bit is SET when the CV value reaches
zero.
STRING
LWORD
LREAL
UDINT
USINT
ULINT
WORD
BOOL
REAL
BYTE
DATE
UINT
DINT
TIME
SINT
LINT
INT
EN •
LOAD •
PV •
Q •
CV •
ENO •
CTU
Description
None
Behavioral Differences
In Connected Components Workbench, the counter counts upwards until it reaches the limit of CV
whereas in RSLogix, the counter continues to count upwards.
DWORD
STRING
LWORD
LREAL
UDINT
USINT
ULINT
WORD
BOOL
REAL
BYTE
DATE
UINT
DINT
TIME
SINT
LINT
INT
EN •
CU •
RESET •
PV •
Q •
CV •
ENO •
TON
Description
This instruction is used to turn an output on or off after the timer has been on for a preset time
interval.
Figure 47 - TON Functional Block Diagram
RSLogix 500/RSLogix Micro Connected Components Workbench
None
Behavioral Differences
On returning to the REM Run or REM Test mode, the following can happen:
Condition Result
EN bit remains set
If the rung is true: TT bit remains set
ACC value is reset
EN bit is reset
If the rung is false: TT bit is reset
ACC value is reset
DWORD
STRING
LWORD
LREAL
UDINT
USINT
ULINT
WORD
BOOL
REAL
BYTE
DATE
UINT
DINT
TIME
SINT
LINT
INT
EN •
IN •
PT •
Q •
ET •
ENO •
TOF
Description
This instruction is used to turn an output on or off after its rung has been off for a preset time
interval.
Figure 48 - TOF Functional Block Diagram
RSLogix 500/RSLogix Micro Connected Components Workbench
None
Behavioral Differences
On returning to the REM Run or REM Test mode, the following can happen:
Condition Result
TT bit is reset
DN bit remains set
If the rung is true: EN bit is set
ACC value is reset
TT bit is reset
DN bit is reset
If the rung is false: EN bit is reset
ACC value is set equal to the preset value
STRING
LWORD
LREAL
UDINT
ULINT
USINT
WORD
BOOL
REAL
BYTE
DATE
UINT
DINT
TIME
SINT
LINT
INT
EN •
IN •
PT •
Q •
ET •
ENO •
RTO
Description
This retentive instruction lets the timer stop and start without resetting the accumulated value.
Figure 49 - RTO Functional Block Diagram
RSLogix 500/RSLogix Micro Connected Components Workbench
If using a Micro810 or Micro820 controller, the RTO internal timer does not persist through a power
cycle by default. To persist the internal timer, set the Retained configuration parameter to true.
If using a Micro850 or Micro870 controller, the RTO internal timer persists through a power cycle.
Behavioral Differences
When the processor changes from the REM Run or REM Test mode to the REM Program or REM Fault
mode, or user power is lost while the timer is timing but not yet at the preset value, the following
occurs:
• Timer Enable (EN) bit remains set.
• Timer Timing (TT) bit remains set.
• Accumulated value (ACC) remains the same.
On returning to the REM Run or REM Test mode, the following can happen:
Condition Result
TT bit remains set
If the rung is true: EN bit remains set
ACC value remains the same and resumes incrementing
TT bit is reset
DN bit remains in its last state
If the rung is false: EN bit is reset
ACC value remains in its last state
DWORD
STRING
LWORD
LREAL
UDINT
USINT
ULINT
WORD
BOOL
REAL
BYTE
DATE
UINT
DINT
TIME
SINT
LINT
INT
EN •
IN •
RST •
PT •
Q •
ET •
ENO •
High-Speed Counter
Description
The HSC instruction counts high-speed pulses from a high-speed input with a specified maximum
pulse rate. An alternative set of high-speed counter instructions have been added in Connected
Components Workbench software version 11 or later. This set of instructions makes them more
intuitive than the standard HSC instruction. They also provide additional status information, such as
pulse rate and touch probe position. To learn more about these instructions, see the Connected
Components Workbench software Help for the following.
• HSCE
• HSCE_CFG
• HSCE_READ_STS
• HSCE_SET_STS
None
Behavioral Differences
When the high-speed counter is enabled, data table counter C5:0 is used by the ladder program for
monitoring the high-speed counter accumulator and status.
Table 132 - Counter Data File Elements (C5:0)
15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00
Word 0 CU CD DN OV UN UA HP LP IV IN IH IL PE LS IE <- Status Word
Word 1 Preset Value
Word 2 Accumulator Value
The high-speed counter accumulator and status are found under the HscSTSInfo parameters.
Table 133 - HscSTSInfo Parameters
User
Parameter Data Type HSC Mode Program Description
Access
CountEnable BOOL 0…9 Read only Counting enabled
ErrorDetected BOOL 0…9 Read/write Nonzero means error detected.
CountUpFlag BOOL 0…9 Read only Count up flag
CountDwnFlag BOOL 2…9 Read only Count down flag
HSC is Mode 1A or Mode 1B; accumulator counts up
Mode1Done BOOL 0 or 1 Read/write to the HP value.
OVF BOOL 0…9 Read/write Overflow is detected.
UNF BOOL 0…9 Read/write Underflow is detected.
CountDir BOOL 0…9 Read only 1: count up; 0: count down
HPReached BOOL 2…9 Read/write High preset reached.
LPReached BOOL 2…9 Read only Low preset reached.
OFCauseInter BOOL 0…9 Read/write Overflow caused an HSC Interrupt.
UFCauseInter BOOL 2…9 Read/write Underflow caused an HSC Interrupt.
HPCauseInter BOOL 0…9 Read/write High preset reached, causing an HSC Interrupt.
LPCauseInter BOOL 2…9 Read/write Low preset reached, causing an HSC Interrupt.
PlsPosition UINT 0…9 Read only Position of the Programmable Limit Switch (PLS)
Displays the error codes that are detected by the
ErrorCode UINT 0…9 Read/write HSC subsystem.
Accumulator DINT Read/write Actual accumulator reading
HP DINT Read only Last high preset setting
LP DINT Read only Last low preset setting
HPOutput UDINT Read/write Last high preset output setting
Additional Examples
Configure Interrupts on a For this example, use a Selectable Timed Interrupt (STI).
Micro800 Controller 1. Create a program to execute when the interrupt occurs.
a. On the Project Organizer panel, right-click Programs and select
Add New LD: Ladder Diagram.
b. Rename the program as STI_INT.
2. On the Project Organizer panel, double-click Micro850.
The Micro850 controller tab displays.
3. On the lower left of the tab, expand Controller, then click Interrupts.
The configured Interrupts can be configured or deleted from the Controller - Interrupts
workspace.
Set Up High-Speed Counter The controller uses Indexed Addressing to locate the correct encoder count from the data table
N7[10] to N7[17] and load the information into the high preset of the high-speed counter.
(HSC) Instruction Variables
The HSC instruction is required to allow the HSC parameters (N7[0] to N7[4]) to be loaded for the
same instruction:
Table 136 - HSC Instructions for Parameters N7[0] to N7[4]
Name Data Value Details
N7[0] 0001h Output Mask – Control gripper
N7[1] 0000h Output pattern for High Preset – Turn off gripper
N7[2] 100d High Preset – Loaded from table N7[10] to N7[17]
N7[3] 0001h Output pattern for Low Preset – Turn on gripper
N7[4] 0d Low Preset – Home position when encoder triggers Z-reset
The number of pulses the head must travel to reach each bin location is stored in a data table that
starts at address N7 [10] and ends at N7 [17]. This value is entered under the Initial Value field so
that it is used as the value of a variable when a controller starts execution for the first time, such as
after a program download.
Table 137 - HSC Instructions for Parameters N7[10] to N7[17]
Name Data Value Details
N7[10] 100d Number of pulses to reach Bin Location A
N7[11] 200d Number of pulses to reach Bin Location B
N7[12] 300d Number of pulses to reach Bin Location C
N7[13] 400d Number of pulses to reach Bin Location D
N7[14] 500d Number of pulses to reach Bin Location E
N7[15] 600d Number of pulses to reach Bin Location F
N7[16] 700d Number of pulses to reach Bin Location G
N7[17] 800d Number of pulses to reach Bin Location H
1. On the Project Organizer panel, double-click Global Variables.
2. Click the + symbol for the variable N7 to expand the row.
3. Double-click the Initial Value field for N7 [0], then enter “01”.
4. Repeat step 3 for N7 [1] to N7[4] and N7[10] to N7[17] for the rest of the data values as
shown in Table 136 and Table 137.
Figure 51 shows the completed entries:
Figure 51 - Complete HSC Instructions
Notes:
In this appendix, you can view and compare the three different ladder diagrams of the pick-and-
place application.
• Original RSLogix 500/RSLogix Micro Ladder Diagram
• Connected Components Workbench Ladder Diagram (Converter Tool)
• Connected Components Workbench Ladder Diagram (Manual Conversion)
Original RSLogix 500/ The following shows the original pick-and-place application ladder diagram in the RSLogix 500/
RSLogix Micro report.
RSLogix Micro Ladder
Diagram
Connected Components The following shows the pick-and-place application ladder diagram that was converted with the
MicroLogix to Micro800 Converter tool in Connected Components Workbench software.
Workbench Ladder Diagram
(Converter Tool)
Source:
Destination:
(grab part)
Connected Components The following shows the pick-and-place application ladder diagram that was converted manually
in Connected Components Workbench software.
Workbench Ladder Diagram
(Manual Conversion)
Notes:
Documentation Feedback
Your comments help us serve your documentation needs better. If you have any suggestions on how to improve our content, complete the
form at rok.auto/docfeedback.
At the end of life, this equipment should be collected separately from any unsorted municipal waste.
Rockwell Automation maintains current product environmental compliance information on its website at rok.auto/pec.
Allen-Bradley, CompactLogix, Connected Components Workbench, expanding human possibility, FactoryTalk, FactoryTalk Linx, FactoryTalk Linx Gateway, Integrated Architecture Builder, MicroLogix,
Micro800, Micro810, Micro820, Micro830, Micro850, Micro870, PanelView, PanelView Plus, PLC-2, Product Selection Toolbox, Rockwell Automation, RSLinx, RSLogix 500, RSLogix Emulate, RSLogix Micro,
SLC 500, and TechConnect are trademarks of Rockwell Automation, Inc.
CIP and EtherNet/IP are trademarks of ODVA, Inc.
microSD is a trademark of SD-3C.
Trademarks not belonging to Rockwell Automation are property of their respective companies.
Rockwell Otomasyon Ticaret A.Ş. Kar Plaza İş Merkezi E Blok Kat:6 34752, İçerenköy, İstanbul, Tel: +90 (216) 5698400 EEE Yönetmeliğine Uygundur
ASIA PACIFIC: Rockwell Automation SEA Pte Ltd., 2 Corporation Road, #04-05, Main Lobby, Corporation Place, Singapore 618494, Tel: (65) 6510-6608, Fax: (65) 6510-6699