Micro830-850-870 Manual

Micro830, Micro850, and Micro870
Programmable Controllers
Micro810 Controller Catalog Numbers 2080-LC10-12AWA, 2080-LC10-12QWB, 2080-LC10-12DWD, 2080-LC10-12QBB
Micro820 Controller Catalog Numbers 2080-LC20-20AWB, 2080-LC20-20AWBR, 2080-LC20-20QWB, 2080-LC20-20QWBR,
2080-LC20-20QBB, 2080-LC20-20QBBR
Micro830 Controller Catalog Numbers 2080-LC30-10QWB, 2080-LC30-10QVB, 2080-LC30-16AWB, 2080-LC30-16QWB,
2080-LC30-16QVB, 2080-LC30-24QWB, 2080-LC30-24QVB, 2080-LC30-24QBB, 2080-LC30-48AWB, 2080-LC30-48QWB,
2080-LC30-48QVB, 2080-LC30-48QBB
Micro850 Controller Catalog Numbers 2080-LC50-24AWB, 2080-L50E-24AWB, 2080-LC50-24QWB, 2080-L50E-24QWB,
2080-LC50-24QVB, 2080-L50E-24QVB, 2080-LC50-24QBB, 2080-L50E-24QBB, 2080-LC50-48AWB, 2080-L50E-48AWB,
2080-LC50-48QWB, 2080-L50E-48QWB, 2080-LC50-48QWBK, 2080-L50E-48QWBK, 2080-LC50-48QVB, 2080-L50E-48QVB,
2080-LC50-48QBB, 2080-L50E-48QBB
Micro870 Controller Catalog Numbers 2080-LC70-24AWB, 2080-L70E-24AWB, 2080-LC70-24QWB, 2080-L70E-24QWB,
2080-LC70-24QWBK, 2080-L70E-24QWBK, 2080-L70E-24QWBN, 2080-LC70-24QBB, 2080-L70E-24QBB, 2080-LC70-24QBBK,
2080-L70E-24QBBK, 2080-L70E-24QBBN
User Manual Original Instructions

Micro830, Micro850, and Micro870 Programmable Controllers User Manual
Important User Information

Read this document and the documents listed in the additional resources section about installation, configuration, and
operation of this equipment before you install, configure, operate, or maintain this product. Users are required to familiarize
themselves with installation and wiring instructions in addition to requirements of all applicable codes, laws, and standards.
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.
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).
2 Rockwell Automation Publication 2080-UM002M-EN-E - April 2022

Table of Contents
Preface
About This Publication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Conformal Coated Catalogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Download Firmware, AOP, EDS, and Other Files . . . . . . . . . . . . . . . . . . . 11
Summary of Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Chapter 1
Hardware Overview Hardware Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Micro830 Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Programming Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Embedded Serial Port Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Embedded Ethernet Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Chapter 2
About Your Controller Programming Software for Micro800 Controllers . . . . . . . . . . . . . . . . . . 23
Obtain Connected Components Workbench Software . . . . . . . . . . 23
Use Connected Components Workbench Software . . . . . . . . . . . . . 23
Controller Changes in Run Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Using Run Mode Change (RMC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Uncommitted Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
RMC Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Limitations of RMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Using Run Mode Configuration Change (RMCC). . . . . . . . . . . . . . . . . . . 28
Using Modbus RTU Communication . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Using EtherNet/IP Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Safety Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Disconnect Main Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Safety Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Power Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Periodic Tests of Master Control Relay Circuit. . . . . . . . . . . . . . . . . . 33
Power Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Isolation Transformers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Power Supply Inrush. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Loss of Power Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Input States on Power Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Other Types of Line Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Preventing Excessive Heat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Master Control Relay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Using Emergency-Stop Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Rockwell Automation Publication 2080-UM002M-EN-E - April 2022 3

Table of Contents
Chapter 3
Install Your Controller Controller Mounting Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Mounting Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
DIN Rail Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Panel Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Panel Mounting Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
System Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Chapter 4
Wire Your Controller Wiring Requirements and Recommendation . . . . . . . . . . . . . . . . . . . . . . 47
Use Surge Suppressors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Recommended Surge Suppressors . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Grounding the Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Wiring Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Controller I/O Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Minimize Electrical Noise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Analog Channel Wiring Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Minimize Electrical Noise on Analog Channels . . . . . . . . . . . . . . . . . 56
Grounding Your Analog Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Wiring Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Embedded Serial Port Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Chapter 5
Communication Connections Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Supported Communication Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Modbus RTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
CIP Serial Client/Server – DF1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
ASCII. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Modbus TCP Client/Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
CIP Symbolic Client/Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
CIP Client Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Sockets Client/Server TCP/UDP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
CIP Communications Pass-thru . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Examples of Supported Architectures . . . . . . . . . . . . . . . . . . . . . . . . . 64
Use Modems with Micro800 Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Making a DF1 Point-to-Point Connection . . . . . . . . . . . . . . . . . . . . . . 65
Construct Your Own Modem Cable. . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Configure Serial Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Configure CIP Serial Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Configure Modbus RTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Configure ASCII. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Configure Ethernet Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Validate IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Ethernet Host Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Configure CIP Serial Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
OPC Support Using FactoryTalk Linx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Table of Contents
Chapter 6
Micro870 Controller Distributed Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Network Protocol Channel Configuration for DNP3 Slave. . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Serial Port Link Layer Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Ethernet Layer Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
DNP3 Slave Application Layer Configuration . . . . . . . . . . . . . . . . . . . 78
Serial Link Layer Configuration Parameters. . . . . . . . . . . . . . . . . . . . 78
Ethernet Layer Configuration Parameters . . . . . . . . . . . . . . . . . . . . . 81
DNP3 Slave Application Layer Configuration Parameters. . . . . . . . 86
DNP3 Slave Application Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Function Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Internal Indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
DNP3 Objects and Controller Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . 105
DNP3 Object Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
DNP3 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
DNP3 Data Set Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Object Quality Flags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
DNP3 Device Attribute Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Event Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Generate Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
DNP3 10K Event Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Control Generating Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Report Event By Polled Response. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Report Event By Unsolicited Response. . . . . . . . . . . . . . . . . . . . . . . . 121
Collision Avoidance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Time Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Diagnostics for Ethernet Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Diagnostics for Secure Authentication. . . . . . . . . . . . . . . . . . . . . . . . 126
Function Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Implementation Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Chapter 7
Program Execution in Micro800 Overview of Program Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Execution Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Optional Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Controller Load and Performance Considerations. . . . . . . . . . . . . . . . . 135
Periodic Execution of Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Power Up and First Scan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Variable Retention. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Memory Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Guidelines and Limitations for Advanced Users . . . . . . . . . . . . . . . . . . . 137
Chapter 8
Motion Control PTO Motion Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Use the Micro800 Motion Control Feature . . . . . . . . . . . . . . . . . . . . 140
Input and Output Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Motion Control Function Blocks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
General Rules for the Motion Control Function Blocks . . . . . . . . . 145
Motion Axis and Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Table of Contents
Axis States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Motion Stop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Motion Direction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Axis Elements and Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Axis Error Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
MC_Engine_Diag Data Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Function Block and Axis Status Error Codes . . . . . . . . . . . . . . . . . . . . . . 160
Major Fault Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Motion Axis Configuration in Connected Components Workbench . 163
Add New Axis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Edit Axis Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Axis Start/Stop Velocity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Real Data Resolution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
PTO Pulse Accuracy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Motion Axis Parameter Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Delete an Axis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Monitor an Axis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Homing Function Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Conditions for Successful Homing . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
MC_HOME_ABS_SWITCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
MC_HOME_LIMIT_SWITCH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
MC_HOME_REF_WITH_ABS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
MC_HOME_REF_PULSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
MC_HOME_DIRECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Use PTO for PWM Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
POU PWM_Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
HSC Feedback Axis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Chapter 9
Use the High-Speed Counter and High-Speed Counter Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Programmable Limit Switch Programmable Limit Switch Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
What is High-Speed Counter? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Features and Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
HSC Inputs and Wiring Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
High Speed Counter (HSC) Data Structures . . . . . . . . . . . . . . . . . . . . . . 187
HSC APP Data Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
HSC STS (HSC Status) Data Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
High-Speed Counter (HSC) Function Block. . . . . . . . . . . . . . . . . . . . . . . 202
HSC Commands (HScCmd) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
HSC_SET_STS Function Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Programmable Limit Switch (PLS) Function . . . . . . . . . . . . . . . . . . . . . . 205
PLS Data Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
PLS Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
PLS Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
HSC Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
HSC Interrupt Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
HSC Interrupt POU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
HSC Interrupt Status Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

Table of Contents
Chapter 10
Controller Security Protected Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Exclusive Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Password Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Compatibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Work with a Locked Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Upload from a Password-Protected Controller. . . . . . . . . . . . . . . . . 215
Debug a Password-Protected Controller . . . . . . . . . . . . . . . . . . . . . . 215
Download to a Password-Protected Controller. . . . . . . . . . . . . . . . . 216
Transfer Controller Program and Password-Protect Receiving
Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Back Up and Restore a Password-Protected Controller . . . . . . . . . 217
Configure Controller Password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Recover from a Lost Password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Using the Memory Module Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Chapter 11
Using microSD Cards Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Project Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Backup and Restore Directory Structure . . . . . . . . . . . . . . . . . . . . . . 223
Power-up Settings in ConfigMeFirst.txt . . . . . . . . . . . . . . . . . . . . . . 224
General Configuration Rules in ConfigMeFirst.txt . . . . . . . . . . . . . 226
ConfigMeFirst.txt Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Deliver Project Updates to Customers Through Email . . . . . . . . . . 227
Data Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Data Log Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Data Log Function (DLG) Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Recipe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Recipe Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Quickstart Projects for Data Log and Recipe Function Blocks. . . . . . . 238
Use the Data Log Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Use the Recipe Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Appendix A
Modbus Mapping for Micro800 Modbus Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Endian Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Mapping Address Space and Supported Data Types . . . . . . . . . . . . 251
Example 1, PanelView 800 HMI (Master) to Micro800 (Slave) . . . 252
Example 2, Micro800 (Master) to PowerFlex 4M Drive (Slave) . . . 253
Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Appendix B
Quickstarts Flash Upgrade Your Micro800 Firmware . . . . . . . . . . . . . . . . . . . . . . . . . 257
Flash Upgrade From MicroSD Card . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Establish Communications Between RSLinx and a Micro830/Micro850/
Micro870 Controller through USB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Configure Controller Password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Set Controller Password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Change Password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Clear Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Table of Contents
Use the High-Speed Counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270

Create the HSC Project and Variables. . . . . . . . . . . . . . . . . . . . . . . . . 271
Assign Values to the HSC Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Assign Variables to the Function Block. . . . . . . . . . . . . . . . . . . . . . . . 276
Run the High-Speed Counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Use the Programmable Limit Switch (PLS) Function . . . . . . . . . . . 279
Forcing I/Os . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Checking if Forces (locks) are Enabled . . . . . . . . . . . . . . . . . . . . . . . . 281
I/O Forces After a Power Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Use Run Mode Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Create the Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
Edit the Project Using Run Mode Change . . . . . . . . . . . . . . . . . . . . . 285
Appendix C
User Interrupts Information About Using Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
What is an Interrupt? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
When Can the Controller Operation be Interrupted? . . . . . . . . . . . 290
Priority of User Interrupts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
User Interrupt Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
User Fault Routine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
User Interrupt Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
STIS - Selectable Timed Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
UID - User Interrupt Disable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
UIE - User Interrupt Enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
UIF - User Interrupt Flush . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
UIC – User Interrupt Clear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Using the Selectable Timed Interrupt (STI) Function . . . . . . . . . . . . . . 297
Selectable Time Interrupt (STI) Function Configuration and Status. 298
STI Function Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
STI Function Status Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Using the Event Input Interrupt (EII) Function . . . . . . . . . . . . . . . . . . . 299
Event Input Interrupt (EII) Function Configuration and Status . . . . 300
EII Function Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
EII Function Status Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
Appendix D
Troubleshooting Status Indicators on the Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Normal Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Fault Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Corrective Action for Recoverable and Non-recoverable Faults . . 310
Retrieve a Fault Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
Controller Error Recovery Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
Calling Rockwell Automation for Assistance . . . . . . . . . . . . . . . . . . . . . . 311

Table of Contents
Appendix E
PID Function Blocks PID Function Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
IPIDCONTROLLER Function Block. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
How to Autotune. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
How Autotune Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
Troubleshooting an Autotune Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
PID Application Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
PID Code Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
Appendix F
System Loading Calculate Total Power for Your Micro830/Micro850/Micro870
Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
Appendix G
Connect to Networks using DF1 DF1 Full-Duplex Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
DF1 Half-Duplex Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
DF1 Half-Duplex Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Considerations When Communicating as a DF1 Slave on a Multi-
drop Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Using Modems with Micro800 Programmable Controllers. . . . . . 327
Modem Control Line Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
DF1 Full-Duplex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
DF1 Half-Duplex Slave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
DF1 Half Duplex Master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
DF1 Radio Modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
Configure DF1 Half-Duplex Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 330
RTS Send Delay and RTS Off Delay . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Configure a Standard-Mode DF1 Half-Duplex Master Station . . . . . . 330
Minimum DF1 Half-Duplex Master ACK Timeout. . . . . . . . . . . . . . 332
Determining Minimum Master ACK Timeout . . . . . . . . . . . . . . . . . 333
DF1 Half-Duplex Master Communication Diagnostics . . . . . . . . . 333
Configure a Message-based Mode DF1 Half-Duplex
Master Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
Configure a Slave Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
Configure Poll Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
DF1 Half-Duplex Slave Communication Diagnostics . . . . . . . . . . . 338
Configure a Radio Modem Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
DF1 Radio Modem Communication Diagnostics . . . . . . . . . . . . . . . 339
Configure the Store and Forward Table . . . . . . . . . . . . . . . . . . . . . . . 340
Index
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343

Table of Contents
Notes:

Preface
About This Publication Use this manual if you are responsible for designing, installing, programming,
or troubleshooting control systems that use Micro800™ controllers.
You should have a basic understanding of electrical circuitry and familiarity

with relay logic. If you do not, obtain the proper training before using this
product.
This manual is a reference guide for Micro800 controllers, plug-in modules,

and accessories. It describes the procedures you use to install, wire, and
troubleshoot your controller. This manual:
• explains how to install and wire your controllers
• gives you an overview of the Micro800 controller system
See the Online Help provided with Connected Components Workbench™

software for more information on programming your Micro800 controller.
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.
Conformal Coated Catalogs Catalog numbers with the suffix ‘K’ are conformal coated and their
specifications are the same as non-conformal coated catalogs.
Download Firmware, AOP, Download firmware, associated files (such as AOP, EDS, and DTM), and access
EDS, and Other Files product release notes from the Product Compatibility and Download Center at
rok.auto/pcdc.
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
Added new Micro850 (2080-L50E) and Micro870 (2080-L70E) catalogs Throughout
Updated table Additional Resources 12
Updated table Micro850 Controllers – Number and Types of Inputs/Outputs 20
Updated table Micro870 Controllers – Number and Types of Inputs/Outputs 21
Updated section Use Connected Components Workbench Software 23
Updated topic Using Run Mode Change (RMC) 24
Updated section RMC memory 25
Updated section Limitations of RMC 27
Updated topic Using Run Mode Configuration Change (RMCC) 28
Updated section CIP Serial Client/Server - DF1 61
Updated section CIP Symbolic Client/Server 62
Updated table CIP Serial Driver Parameters 67

Preface
Topic Page
New chapter Micro870 Controller Distributed Network Protocol 75
Updated topic Password Protection 214
Updated section Back Up and Restore a Password-Protected Controller 217
Updated topic Using the Memory Module Plug-In 218
Updated topic Using microSD Cards Overview 221
Updated topic Project Backup and Restore 222
Removed appendix Specifications. Specifications for Micro800 controllers can be found in –
the Micro800 Programmable Controllers Technical Data, publication 2080-TD001
Added appendix Connect to Networks Using DF1 325
Additional Resources These documents contain additional information concerning related products
from Rockwell Automation.
Resource Description
Micro800 Programmable Controller Family Selection Guide, Provides information to help you select the Micro800 controller, plug-ins, expansion I/O, and
publication 2080-SG001 accessories, based on your requirements.
Micro800 Programmable Controllers Technical Data, publication 2080-TD001 Provides detailed specifications for Micro800 controllers, expansion I/O modules, plug-in
modules, and accessories.
Information on features, configuration, wiring, installation, and specifications for the Micro800
Micro800 Expansion I/O Modules User Manual, publication 2080-UM003 expansion I/O modules and power supply.
Information on features, configuration, installation, wiring, and specifications for the Micro800
Micro800 Plug-in Modules User Manual, publication 2080-UM004 plug-in modules.
Micro800 Programmable Controllers General Instructions Reference Manual, Information on instruction sets for developing programs for use in Micro800 control systems.
publication 2080-RM001
Micro800 Programmable Controllers: Getting Started with Motion Control Provides quick start instructions for implementing a motion control project in Connected
Using a Simulated Axis Quick Start, publication 2080-QS001 Components Workbench software.
Micro800 Programmable Controllers: Getting Started with CIP Client Provides quick start instructions for using CIP GENERIC and CIP Symbolic Messaging.
Messaging Quick Start, publication 2080-QS002
Micro800 Programmable Controllers: Getting Started with PanelView Plus Provides quick start instructions for using global variables for Micro800 controllers together with
Quick Start, publication 2080-QS003 PanelView™ Plus HMI terminals.
Configuring Micro800 Controllers on FactoryTalk Linx Gateway Quick Start, Provides quick start instructions for configuring a Micro800 controller on FactoryTalk Linx
publication 2080-QS005 Gateway.
Kinetix 3 Motion Control Indexing Application Connected Components Accel Provides quick start instructions for implementing a Kinetix 3 drive indexing application
Toolkit Quick Start, publication CC-QS025 using Connected Components Workbench software and a Micro800 controller.
Motion Control PTO Application Building Block Quick Start, Provides quick start instructions for implementing PTO motion control of a Kinetix 3 drive using
publication CC-QS033 Connected Components Workbench software and a Micro800 controller.
Micro800 Programmable Controller External AC Power Supply Installation Information on mounting and wiring the optional external power supply.
Instructions 2080-IN001
Micro800 Programmable Controllers Installation Instructions, Information on mounting and wiring Micro800 Controllers
publication 2080-IN013
Micro800 16-point and 32-point 12/24V Sink/Source Input Modules Information on mounting and wiring the expansion I/O modules (2085-IQ16, 2085-IQ32T)
Installation Instructions, publication 2085-IN001
Micro800 Bus Terminator Module Installation Instruction, Information on mounting and wiring the expansion I/O bus terminator (2085-ECR)
publication 2085-IN002
Micro800 16-Point Sink and 16-Point Source 12/24V DC Output Modules Information on mounting and wiring the expansion I/O modules (2085-OV16, 2085-OB16)
Installation Instructions, publication 2085-IN003
Micro800 8-Point and 16-Point AC/DC Relay Output Modules Installation Information on mounting and wiring the expansion I/O modules (2085-OW8, 2085-OW16)
Instructions, publication 2085-IN004
Micro800 8-Point Input and 8-Point Output AC Modules Installation Information on mounting and wiring the expansion I/O modules (2085-IA8, 2085-IM8, 2085-OA8)
Micro800 4-channel and 8-channel Analog Voltage/current Input and Output Information on mounting and wiring the expansion I/O modules (2085-IF4, 2085-IF8, 2085-OF4)
Modules Installation Instructions, publication 2085-IN006
Micro800 4-channel Thermocouple/RTD Input Module Installation Information on mounting and wiring the expansion I/O module (2085-IRT4)
Micro870 Programmable Controllers 24V DC Expansion Power Supply Information on mounting and wiring the optional external power supply for expansion I/O
Installation Instructions, publication 2085-IN008 modules.
Micro800 RS-232/RS-485 Isolated Serial Port Plug-in Module Wiring Information on mounting and wiring the Micro800 RS-232/RS-485 Isolated Serial Port Plug-in
Diagrams, publication 2080-WD002 Module.

Preface
Resource Description
Micro800 Non-isolated Unipolar Analog Input Plug-in Module Wiring Information on mounting and wiring the Micro800 Non-isolated Unipolar Analog Input Plug-in
Micro800 Non-isolated Unipolar Analog Output Plug-in Module Wiring Information on mounting and wiring the Micro800 Non-isolated Unipolar Analog Output Plug-in
Micro800 Non-isolated RTD Plug-in Module Wiring Diagrams, Information on mounting and wiring the Micro800 Non-isolated RTD Plug-in Module.
publication 2080-WD005
Micro800 Non-isolated Thermocouple Plug-in Module Wiring Diagrams, Information on mounting and wiring the Micro800 Non-isolated Thermocouple Plug-in Module.
Micro800 Memory Backup and High Accuracy RTC Plug-In Module Wiring Information on mounting and wiring the Micro800 Memory Backup and High Accuracy RTC Plug-
Diagrams, publication 2080-WD007 In Module.
Micro800 6-Channel Trimpot Analog Input Plug-In Module Wiring Diagrams, Information on mounting and wiring the Micro800 6-Channel Trimpot Analog Input Plug-In
publication 2080-WD008 Module.
Micro800 Digital Relay Output Plug-in Module Wiring Diagrams, Information on mounting and wiring the Micro800 Digital Relay Output Plug-in Module.
Micro800 Digital Input, Output, and Combination Plug-in Modules Wiring Information on mounting and wiring the Micro800 Digital Input, Output, and Combination Plug-in
Diagrams, publication 2080-WD011 Modules.
Micro800 High-Speed Counter Plug-in Module Wiring Diagram, Information on mounting and wiring the High-Speed Counter Plug-in module.
Micro800 DeviceNet Plug-in Module Wiring Diagram, publication 2080-WD013 Information on mounting and wiring the Micro800 DeviceNet® plug-in module.
EtherNet/IP Network Devices User Manual, publication ENET-UM006 Describes how to configure and use EtherNet/IP devices to communicate on the EtherNet/IP
network.
Ethernet Reference Manual, publication ENET-RM002 Describes basic Ethernet concepts, infrastructure components, and infrastructure features.
Provides guidance on how to conduct security assessments, implement Rockwell Automation
System Security Design Guidelines Reference Manual, products in a secure system, harden the control system, manage user access, and dispose of
publication SECURE-RM001 equipment.
Industrial Components Preventive Maintenance, Enclosures, and Contact Provides a quick reference tool for Allen-Bradley® industrial automation controls and
Ratings Specifications, publication IC-TD002 assemblies.
Designed to harmonize with NEMA Standards Publication No. ICS 1.1-1987 and provides general
Safety Guidelines for the Application, Installation, and Maintenance of guidelines for the application, installation, and maintenance of solid-state control in the form of
Solid-state Control, publication SGI-1.1 individual devices or packaged assemblies incorporating solid-state components.
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.
You can view or download publications at rok.auto/literature.
You can download the latest version of Connected Components Workbench

software for your Micro800 controller at rok.auto/ccw.

Preface
Notes:

Chapter 1
Hardware Overview
This chapter provides an overview of the Micro830®, Micro850®, and

Micro870® controller hardware features. It has the following topics:
Topic Page
Hardware Features 16
Micro830 Controllers 16
Programming Cables 21
Embedded Serial Port Cables 21
Embedded Ethernet Support 22

Chapter 1 Hardware Overview
Hardware Features Micro830, Micro850, and Micro870 controllers are economical brick style
controllers with embedded inputs and outputs. Depending on the controller
type, it can accommodate from two to five plug-in modules. The Micro850 and
Micro870 controllers have expandable features. The Micro850 controller can
support up to four expansion I/O modules and the Micro870 controller can
support up to eight expansion I/O modules.
IMPORTANT For information on supported plug-in modules and expansion I/O, see the
following publications:
• Micro800 Expansion I/O Modules User Manual, publication 2080-UM003
• Micro800 Plug-in Modules User Manual, publication 2080-UM004
The controllers also accommodate any class 2 rated 24V DC output power
supply that meets minimum specifications such as the optional Micro800
power supply.
See Troubleshooting on page 303 for descriptions of status indicator operation

for troubleshooting purposes.
Micro830 Controllers
Micro830 10/16-point controllers and status indicators
1 2 3 4 5 6 7 8 Status indicator
Controller
14
15
16
17
18
19
20
13 12 11 10 6 9 7
Micro830 24-point controllers and status indicators

Controller
1 2 3 4 5 6 7 8
Status indicator
14
15
16
17
18
19
20
13 12 11 10 9 6 9 8


Controller
1 2 3 4 5 8 6 7 8
Status indicator
14
15
16
17
18
19
20
13 12 11 10 6 9 8
Controller Description
Description Description
1 Status indicators 8 Mounting screw hole / mounting foot
2 Optional power supply slot 9 DIN rail mounting latch
3 Plug-in latch 10 Mode switch
4 Plug-in screw hole 11 Type B connector USB port
5 40-pin high-speed plug-in connector 12 RS-232/RS-485 non-isolated combo serial port
6 Removable I/O terminal block 13 Optional AC power supply
7 Right-side cover
Status Indicator Description(1)

14 Input status 18 Force status
15 Power status 19 Serial communications status
16 Run status 20 Output status
17 Fault status
(1) For detailed description of the different status LED indicators, see Troubleshooting on page 303.
1 2 3 4 5 6 7 8
Status indicators
16
17
18
19
20
21
22
23
24
15 14 13 12 11 10 6 10 8 9

1 Status indicators 9 Expansion I/O slot cover
RJ-45 Ethernet connector (with embedded green and
6 Removable I/O terminal block 14 yellow LED indicators)
7 Right-side cover 15 Optional power supply
8 Mounting screw hole / mounting foot

16 Input status 21 Fault status
17 Module Status 22 Force status
18 Network Status 23 Serial communications status
19 Power status 24 Output status
20 Run status
(1) For detailed descriptions of the different status LED indicators, see Troubleshooting on page 303.
1 2 3 4 5 8 6 7 8
Status indicators
16
17
18
19
20
21
22
23
24
15 14 13 12 11 6 10 8 9
RJ-45 EtherNet/IP connector
6 Removable I/O terminal block 14 (with embedded yellow and green LED indicators)
7 Right-side cover 15 Optional AC power supply


17 Module status 22 Force status
18 Network status 23 Serial communications status
20 Run status
(1) For detailed descriptions of these LED status indicators, see Troubleshooting on page 303.
Note: You can order the following replacement terminal blocks separately:
• 2080-RPL24RTB for 24-point base controllers
• 2080-RPL48RTB for 48-point base controllers
1 2 3 4 5 6 7 8
Status indicators
16
17
18
19
20
21
22
23
24
15 14 13 12 11 10 6 10 8 9
RJ-45 Ethernet connector (with embedded green and
6 Removable I/O terminal block 14 yellow LED indicators)
7 Right-side cover 15 Optional power supply

17 Module Status 22 Force status

Status Indicator Description(1) (Continued)

18 Network Status 23 Serial communications status
20 Run status
(1) For detailed descriptions of the different status LED indicators, see Troubleshooting on page 303.
You can order replacement terminal blocks, catalog number 2080-RPL24RTB,

separately.
Table 1 - Micro830 Controllers – Number and Types of Inputs/Outputs

Inputs Outputs
Catalog Number PTO Support HSC Support
110V AC 24V DC/V AC Relay 24V Sink 24V Source
2080-LC30-10QWB – 6 4 – – – 2
2080-LC30-10QVB – 6 – 4 – 1 2
2080-LC30-16AWB 10 – 6 – – – –
2080-LC30-16QWB – 10 6 – – – 2
2080-LC30-16QVB – 10 – 6 – 1 2
2080-LC30-24QWB – 14 10 – – – 4
2080-LC30-24QVB – 14 – 10 – 2 4
2080-LC30-24QBB – 14 – – 10 2 4
2080-LC30-48AWB 28 – 20 – – – –
2080-LC30-48QWB – 28 20 – – – 6
2080-LC30-48QVB – 28 – 20 – 3 6
2080-LC30-48QBB – 28 – – 20 3 6

Inputs Outputs
2080-LC50-24AWB 14 – 10 – – – –
2080-L50E-24AWB 14 – 10 – – – –
2080-LC50-24QWB – 14 10 – – – 4
2080-L50E-24QWB – 14 10 – – – 4
2080-LC50-24QVB – 14 – 10 – 2 4
2080-L50E-24QVB – 14 – 10 – 2 4
2080-LC50-24QBB – 14 – – 10 2 4
2080-L50E-24QBB – 14 – – 10 2 4
2080-LC50-48AWB 28 – 20 – – – –
2080-L50E-48AWB 28 – 20 – – – –
2080-LC50-48QWB – 28 20 – – – 6
2080-L50E-48QWB – 28 20 – – – 6
2080-LC50-48QWBK – 28 20 – – – 6
2080-L50E-48QWBK – 28 20 – – – 6

Table 2 - Micro850 Controllers – Number and Types of Inputs/Outputs (Continued)

Inputs Outputs
2080-LC50-48QVB – 28 – 20 – 3 6
2080-L50E-48QVB – 28 – 20 – 3 6
2080-LC50-48QBB – 28 – – 20 3 6
2080-L50E-48QBB – 28 – – 20 3 6

Inputs Outputs
2080-LC70-24AWB 14 – 10 – – – –
2080-L70E-24AWB 14 – 10 – – – –
2080-LC70-24QWB – 14 10 – – – 4
2080-L70E-24QWB – 14 10 – – – 4
2080-LC70-24QWBK – 14 10 – – – 4
2080-L70E-24QWBK – 14 10 – – – 4
2080-L70E-24QWBN – 14 10 – – – 4
2080-LC70-24QBB – 14 – – 10 2 4
2080-L70E-24QBB – 14 – – 10 2 4
2080-LC70-24QBBK – 14 – – 10 2 4
2080-L70E-24QBBK – 14 – – 10 2 4
2080-L70E-24QBBN – 14 – – 10 2 4
Programming Cables
Micro800 controllers have a USB interface, making standard USB cables

usable as programming cables.
Use a standard USB A Male to B Male cable for programming the controller.
Embedded Serial Port Cables
Embedded serial port cables for communication are listed here. All embedded
serial port cables must be 3 meters in length, or shorter.

Table 4 - Embedded Serial Port Cable Selection Chart

Connectors Length Cat. No. Connectors Length Cat. No.
8-pin Mini DIN to 8-pin Mini DIN 0.5 m (1.5 ft) (1) 8-pin Mini DIN to 9-pin D Shell 0.5 m (1.5 ft) 1761-CBL-AP00(1)
1761-CBL-AM00
8-pin Mini DIN to 8-pin Mini DIN 2 m (6.5 ft) 1761-CBL-HM02(1) 8-pin Mini DIN to 9-pin D Shell 2 m (6.5 ft) 1761-CBL-PM02(1)
8-pin Mini DIN to 8-pin Mini DIN (with lock 2 m (6.5 ft) 8-pin Mini DIN with lock mechanism to 2 m (6.5 ft)
1761-CBL-AH02 1761-CBL-PH02
mechanism on both connectors) 9-pin D Shell
8-pin Mini DIN to 6-pin RS-485 terminal 30 cm (11.8in.)
— 1763-NC01 series A
block
(1) Series C or later for Class 1 Div 2 applications.
Embedded Ethernet Support
For Micro850 and Micro870 controllers, a 10/100 Base-T Port (with embedded
green and yellow LED indicators) is available for connection to an Ethernet
network through any standard RJ-45 Ethernet cable. The LED indicators serve
as indicators for transmit and receive status.
RJ-45 Ethernet Port Pin Mapping yellow LED

RJ-45 connector
Contact
Number Signal Direction Primary Function
green LED
1 TX+ OUT Transmit data +
2 TX- OUT Transmit data -
Differential Ethernet Receive The yellow status LED indicates
3 RX+ IN
Data + Link (solid yellow) or No Link (off).
4 Terminated
The green status LED indicates
5 Terminated activity (blinking green) or no
activity (off).
Differential Ethernet Receive
6 RX- IN Data -
7 Terminated
8 Terminated
Shield Chassis Ground
Micro850 and Micro870 controllers support Ethernet crossover cables

(2711P-CBL-EX04).
Ethernet Status Indication
Micro850 and Micro870 controllers also support two LEDs for EtherNet/IP™ to
indicate the following:
• Module status
• Network status
See Troubleshooting on page 303 for descriptions of Module and Network

status indicators.

Chapter 2
About Your Controller
Programming Software for Connected Components Workbench software is a set of collaborative tools
Micro800 Controllers supporting Micro800 controllers. It is based on Rockwell Automation and
Microsoft® Visual Studio® technology and offers controller programming,
device configuration and integration with HMI editor. Use this software to
program your controllers, configure your devices and design your operator
interface applications.
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 support that optimizes machine control.
Obtain Connected Components Workbench Software
A free download is available at rok.auto/ccw.
Use Connected Components Workbench Software
To help you program your controller through the Connected Components

Workbench software, you can refer to the Connected Components Workbench
Online Help (it comes with the software).
IMPORTANT The new Micro850 (2080-L50E) and Micro870 (2080-L70E) controllers

are only supported from Connected Components Workbench software
version 20.01.00 onwards.
Controller Changes in Run Micro820®/Micro830/Micro850/Micro870 controllers allow you to make

Mode certain changes while in run mode by using the following features:
• Run Mode Change (RMC)
This feature allows logic modifications to a running project without
going to remote program mode.
For more information, see Using Run Mode Change (RMC) on page 24.
• Run Mode Configuration Change (RMCC)|
This feature allows changing the address configuration of the controller
to be made within a program during run mode.
For more information, see Using Run Mode Configuration Change
(RMCC) on page 28.

Chapter 2 About Your Controller
Using Run Mode Change Run Mode Change (RMC) is a productivity enhancement feature supported in
(RMC) Connected Components Workbench software for Micro820/Micro830/
Micro850/Micro870 controllers. It saves the user time by allowing logic
modifications to a running project without going to remote program mode
and without disconnecting from the controller.
IMPORTANT Micro820/Micro830/Micro850 controller firmware revision 8.xxx or

higher is also required to use Run Mode Change.
RMC is useful when the user is developing a project by incrementally adding

small changes to the logic and immediately wants to see the effects of the
changes on the machine. With RMC, since the controller stays in remote run
mode, the controller logic and machine actuators will not have to constantly
reinitialize, which can occur if the controller is switched to remote program
mode (for example, first scan bit is checked in program logic to clear outputs).
When user is editing, building, and downloading a project without using RMC,
a full build of the entire controller project is performed and also a full
download of the project is performed. During RMC an incremental build is
performed and only incremental changes are downloaded to the controller.
IMPORTANT Do not disconnect from the controller after performing Run Mode
Change, do a full build, and try to reconnect. Connected Components
Workbench software treats the project in the controller as different from
the project in Connected Components Workbench software, and ask to
either upload or download even though the logic is identical.
RMC is performed incrementally at the end of every program scan in order to

prevent a large delay in the program scan. This adds up to an additional 12 ms
to the scan time. For example, if the program scan is normally 10 ms, it may
increase to 22 ms during RMC until the update is finished. Similarly user
interrupts may be delayed.
Example of the Benefits of Using RMC – 20% Reduction in Download Time

Number of Time to Perform Conventional Time to Test Logic and
Changes Download (seconds) Accept Changes (seconds)
1 36 29
5 180 130
10 360 255
Memory size of project used for comparison:
Data = 14784 bytes; Program = 2352 bytes
Note: The duration starts when the RMC button is clicked while connected to the controller and ends when the accept is
finished. For example:
1. When connected to the controller, click RMC
2. Modify program
3. Click Test Logic
4. Click Accept to finish, or click Test Logic to make another change
ATTENTION: Use extreme caution when you use Run Mode Change. Mistakes
can injure personnel and damage equipment. Before using Run Mode Change:
• assess how machinery will respond to the changes.
• notify all personnel about the changes.
A new global variable __SYSVA_PROJ_INCOMPLETE has been added to

indicate when Run Mode Changes are being made. This can be used to notify
personnel on the HMI that there are uncommitted changes in the controller.

Bit Definitions of Global Variable – __SYSVA_PROJ_INCOMPLETE
Bit Definition
Set when the Run Mode Change process starts.
Cleared once the Run Mode Change is written permanently to the controller (completion of Accept or
0 Undo).
This bit can be used to warn operators that a run mode change is in progress and that there are
uncommitted changes in the controller.
Set if an error occurred while saving the changes to flash or an integrity check failed during Run
1 Mode Change.
Cleared on the next successful Run Mode change.
When you perform a Test Logic Change, the value of the variable is changed
from zero to one. After you choose to accept or undo the changes, the value of
the variable is reset to zero.
IMPORTANT When a Test Logic is performed, or undoing changes after the Test Logic
is completed, any active communication instructions will be aborted
while the changes are downloaded to the controller.
Uncommitted Changes
Uncommitted changes are changes made in RMC that have not been accepted
or undone after a Test Logic Change has been performed.
If the controller power loses power while there are uncommitted changes, you
will not be able to re-enter RMC upon reconnection. You can choose to re-
download the project to keep the changes, or upload if the uncommitted
changes are not wanted.
If you choose to upload a project with uncommitted changes from the

controller, you cannot enter RMC until you have done a full download.
RMC Memory
Run Mode Change (RMC) memory is used to store both the logic and user
variable changes made during RMC. The default amount of memory allocated
is 2 KB and can be increased up to 16 KB. However there is still a limit of 2 KB
for logic and user variables changes per Test Logic. To adjust the amount of
RMC memory, the controller must be offline. After you have adjusted the
amount, you must build the project and download it to the controller.
IMPORTANT In a Connected Components Workbench software version 8 project, the

available user data space was reduced by 6 KB to support optimal
project settings for the new RMC feature.
If you have a project that was developed before version 8, you may need
to reduce the default “Allocated” 8 KB Temporary Variables section from
the Memory page in order to compile the project successfully.

Controller Memory Diagnostics Page in Connected Components Workbench software
During RMC an incremental build is performed and only incremental changes

are downloaded to the controller until the RMC memory has been filled.
RMC Memory Usage Example

Controller Memory RMC Memory
(for User Program + Data) (Default size = 2KB)
1st change and Test 2nd change and 3rd change and
Logic Test Logic Test Logic
(Add logic) (Remove logic) (Add logic)
Free memory
Free RMC memory Used RMC memory
Used memory
If not enough RMC memory is available to make more changes (for example, a
“not enough memory” error message appears during RMC build or Test Logic),
then a full download must be performed to transfer the incremental changes
from the RMC memory to standard user program and data memory.
Transferring Contents in RMC Memory to Controller Memory
The changes that you have made during RMC are stored in RMC memory and
will remain there until you perform a full build and download (while the
controller is disconnected).
RMC Memory Usage When Performing Full Build and Download Example
Free memory Free RMC memory
Used RMC memory is copied to

New used memory controller memory
However if the controller memory does not have enough space remaining to
copy the contents of the RMC memory as shown below, the operation will fail
and a “not enough memory” error message will appear. Do not use RMC if you
are near the limits of your controller memory.

Insufficient Controller Memory Example

Free RMC memory
Error will occur due to insufficient

Used memory controller memory remaining
Limitations of RMC
Take note of the following limitations when using the Run Mode Change
(RMC) feature:
• Configuration changes cannot be made (for example, change filter
times).
• Up to 2 KB of logic (approximately 150 boolean instructions(1)) and user
variables and can be added for each Test Logic.
• Total memory allocated for RMC (cumulative of all Test Logic Changes)
can be increased from 2 KB to 16 KB, but the 2 KB limit for logic and user
variables per Test Logic remains.
• Up to 20 POU (Program Organizational Units) can be added for each
change (for example, if you currently have 5 POU, you can add 20 more
for a total of 25 POU).
• If a User Defined Function Block is modified that changes the local
variables, the local variables will be reinitialized or reset to zero and a
warning message will be shown during the build. If you want to reapply
the initial value, right-click on the UDFB and select Refactor → Reset
Initial Values of Instances.
• RMC is not possible after doing a Discover Project operation if a new
module is detected because the configuration has changed.
• Exchange files cannot be imported when in RMC because it is considered
a configuration change.
• Making changes to the display configuration (for example, hiding
comments) are treated as logic changes and require you to build the
project.
• Global variables cannot be deleted or modified in RMC, but can be added.
To delete or modify a global variable, Connected Components
Workbench software must be disconnected from the controller.
• When using CIP™ messaging in RMC, setting the CIPTARGETCFG data
type parameter ConnClose to TRUE has no effect. The Ethernet session
does not close immediately upon successful messaging and you have to
wait for the connection to timeout after 60 seconds. This applies to
Connected Components Workbench software version 9 or earlier
projects. For version 10 or later projects, the CIP connection timeout is
configurable.
WARNING: If you delete the output rung when in Run Mode Change and accept
the changes, the output on the controller will remain ON.
See Use Run Mode Change on page 282 for an example on how to use this
feature.
(1) Approximately 85 boolean instructions for Micro850 (2080-L50E) and Micro870 (2080-L70E)
controllers.
Using Run Mode Run Mode Configuration Change (RMCC) is a productivity enhancement
Configuration Change feature supported in Connected Components Workbench software for
Micro820/Micro830/Micro850/Micro870 controllers. It allows users to reuse
(RMCC) an identical program with multiple controllers simply by changing the address
configuration of a controller within the program during run mode. Micro820/
Micro830/Micro850 controller firmware revision 9.xxx or higher is required to
use this feature.
RMCC can be used to change the address configuration of the controller

during run mode when the communication protocol is set to Modbus RTU for
serial ports or EtherNet/IP for the Ethernet port. RMCC uses a CIP Generic
message which can only be sent from within a controller program and not
from an external device to the controller.
IMPORTANT During RMCC the scan time may increase to close to 100 ms. Do not
perform RMCC if the controller is performing time critical operations.
CIP Generic Message Instruction for Run Mode Configuration Change
Run Mode Configuration Change (RMCC) can only be performed by the

controller that is sending the message. To do that, you need to configure the
CIP Generic message as a loop-back message by setting the path to “0,0”.
Configure CIP Generic Message as a Loop-back Message
For Micro830/Micro850/Micro870 controllers, the address configuration

change is permanent and will retained when the controller is power cycled.
From firmware revision 10 onwards, Micro820 controllers also retain the
address configuration when the controller is power cycled.

Using Modbus RTU Communication
To use RMCC with the Modbus RTU communication protocol, the serial port
must be set to the Modbus slave role. A CIP Generic message is sent from
within a program with the following parameters.
CIP Generic Message Parameters for RMCC using Modbus RTU

Parameter Value
Service 16
Class 70
2 – Embedded serial port
Instance 5, 6, 7, 8, or 9 – Plug-in modules
Attribute 100
ReqData New node address, 1
ReqLen 2
RMCC Modbus Example – Set the Parameters
RMCC Modbus Example – Set the New Node Address
The first byte indicates the new node address for the controller. For this
example, the new node address is “3”. The second byte must always be “1”, this
indicates that the Modbus role is configured as Slave.
RMCC Modbus Example – Set the Message Length
When the new node address is configured and applied, the port is not
restarted.
IMPORTANT You must ensure that the new node address being configured is unique
as it will not be checked against existing node addresses of other
devices.
You can verify that the node address has changed after performing RMCC by
looking at the Communication Diagnostics tab for the controller.

RMCC Modbus Example – Verify Address Change
Using EtherNet/IP Communication

To use RMCC with the EtherNet/IP communication protocol, the controller
must be configured to use a static IP address. If the controller is configured to
use BOOTP or DHCP, the change will be rejected. A CIP Generic message is
sent from within a program with the following parameters.
Use RMCC when configuring the controller during commissioning.

Immediately after changing the IP address, the cycle time may increase up to
100 ms for one program scan.
CIP Generic Message Parameters for RMCC using EtherNet/IP

Parameter Value
Service 16
Class 245
Instance 1
Attribute 5
ReqData IP address, Subnet mask, Gateway address
ReqLen 22 bytes
RMCC EtherNet/IP Example – Set the Parameters

RMCC EtherNet/IP Example – Set the New IP Address
For this example, the new IP Address is set to the following:

• IP address = 192.168.1.10
• Subnet mask = 255.255.255.0
• Gateway address = 192.168.1.1
RMCC EtherNet/IP Example – Set the Message Length
After the new IP address is configured and applied, the controller will
disconnect from the Connected Components Workbench software if
communication is through Ethernet.
IMPORTANT Micro830 controllers do not support Run Mode Configuration Change

using EtherNet/IP.
IMPORTANT You should not perform IP address changes continuously. Allow an

interval of at least six seconds before performing the next IP address
change in order for duplicate address detection to work properly.
You can verify that the IP address has changed after performing RMCC by
looking at the Ethernet settings for the controller.

RMCC EtherNet/IP Example – Verify Address Change
Safety Considerations Safety considerations are an important element of proper system installation.
Actively thinking about the safety of yourself and others, as well as the
condition of your equipment, is of primary importance. We recommend
reviewing the following safety considerations.
Disconnect Main Power
The main power disconnect switch should be located where operators and
maintenance personnel have quick and easy access to it. In addition to
disconnecting electrical power, all other sources of power (pneumatic and
hydraulic) should be de-energized before working on a machine or process
controlled by a controller.
WARNING: Explosion Hazard

Do not replace components, connect equipment, or disconnect equipment
unless power has been switched off.
Safety Circuits
Circuits installed on the machine for safety reasons, like overtravel limit
switches, stop push buttons, and interlocks, should always be hard-wired
directly to the master control relay. These devices must be wired in series so
that when any one device opens, the master control relay is de-energized,
thereby removing power to the machine. Never alter these circuits to defeat
their function. Serious injury or machine damage could result.
WARNING: Explosion Hazard

Do not connect or disconnect connectors while circuit is live.

Power Distribution
There are some points about power distribution that you should know:
• The master control relay must be able to inhibit all machine motion by
removing power to the machine I/O devices when the relay is de-
energized. It is recommended that the controller remain powered even
when the master control relay is de-energized.
• If you are using a DC power supply, interrupt the load side rather than
the AC line power. This avoids the additional delay of power supply turn-
off. The DC power supply should be powered directly from the fused
secondary of the transformer. Power to the DC input and output circuits
should be connected through a set of master control relay contacts.
Periodic Tests of Master Control Relay Circuit
Any part can fail, including the switches in a master control relay circuit. The
failure of one of these switches would most likely cause an open circuit, which
would be a safe power-off failure. However, if one of these switches shorts out,
it no longer provides any safety protection. These switches should be tested
periodically to assure they will stop machine motion when needed.
Power Considerations The following explains power considerations for the micro controllers.
Isolation Transformers
You may want to use an isolation transformer in the AC line to the controller.
This type of transformer provides isolation from your power distribution
system to reduce the electrical noise that enters the controller and is often used
as a step-down transformer to reduce line voltage. Any transformer used with
the controller must have a sufficient power rating for its load. The power
rating is expressed in volt-amperes (VA).
Power Supply Inrush
During power-up, the Micro800 power supply allows a brief inrush current to
charge internal capacitors. Many power lines and control transformers can
supply inrush current for a brief time. If the power source cannot supply this
inrush current, the source voltage may sag momentarily.
The only effect of limited inrush current and voltage sag on the Micro800 is
that the power supply capacitors charge more slowly. However, the effect of a
voltage sag on other equipment should be considered. For example, a deep
voltage sag may reset a computer connected to the same power source. The
following considerations determine whether the power source must be
required to supply high inrush current:
• The power-up sequence of devices in a system.
• The amount of the power source voltage sag if the inrush current cannot
be supplied.

• The effect of voltage sag on other equipment in the system.
If the entire system is powered-up at the same time, a brief sag in the power
source voltage typically will not affect any equipment.
Loss of Power Source
The optional Micro800 AC power supply is designed to withstand brief power

losses without affecting the operation of the system. The time the system is
operational during power loss is called program scan hold-up time after loss of
power. The duration of the power supply hold-up time depends on power
consumption of controller system, but is typically between 10 milliseconds and
3 seconds.
Input States on Power Down
The power supply hold-up time as described above is generally longer than the
turn-on and turn-off times of the inputs. Because of this, the input state
change from “On” to “Off” that occurs when power is removed may be recorded
by the controller before the power supply shuts down the system.
Understanding this concept is important. The user program should be written
to take this effect into account.
Other Types of Line Conditions
Occasionally the power source to the system can be temporarily interrupted. It

is also possible that the voltage level may drop substantially below the normal
line voltage range for a period of time. Both of these conditions are considered
to be a loss of power for the system.
Preventing Excessive Heat For most applications, normal convective cooling keeps the controller within
the specified operating range. Ensure that the specified temperature range is
maintained. Proper spacing of components within an enclosure is usually
sufficient for heat dissipation.
In some applications, a substantial amount of heat is produced by other

equipment inside or outside the enclosure. In this case, place blower fans
inside the enclosure to assist in air circulation and to reduce “hot spots” near
the controller.
Additional cooling provisions might be necessary when high ambient

temperatures are encountered.
Do not bring in unfiltered outside air. Place the controller in an enclosure

to protect it from a corrosive atmosphere. Harmful contaminants or dirt
could cause improper operation or damage to components. In extreme
cases, you may need to use air conditioning to protect against heat
build-up within the enclosure.

Master Control Relay A hard-wired master control relay (MCR) provides a reliable means for
emergency machine shutdown. Since the master control relay allows the
placement of several emergency-stop switches in different locations, its
installation is important from a safety standpoint. Overtravel limit switches or
mushroom-head push buttons are wired in series so that when any of them
opens, the master control relay is de-energized. This removes power to input
and output device circuits. See Figure 1 on page 36 and Figure 2 on page 37.
WARNING: Never alter these circuits to defeat their function since

serious injury and/or machine damage could result.
If you are using an external DC power supply, interrupt the DC output side
rather than the AC line side of the supply to avoid the additional delay of
power supply turn-off.
The AC line of the DC output power supply should be fused.
Connect a set of master control relays in series with the DC power supplying
the input and output circuits.
Place the main power disconnect switch where operators and maintenance
personnel have quick and easy access to it. If you mount a disconnect switch
inside the controller enclosure, place the switch operating handle on the
outside of the enclosure, so that you can disconnect power without opening
the enclosure.
Whenever any of the emergency-stop switches are opened, power to input and
output devices should be removed.
When you use the master control relay to remove power from the external I/O
circuits, power continues to be provided to the controller’s power supply so
that diagnostic indicators on the controller can still be observed.
The master control relay is not a substitute for a disconnect to the controller. It
is intended for any situation where the operator must quickly de-energize I/O
devices only. When inspecting or installing terminal connections, replacing
output fuses, or working on equipment within the enclosure, use the
disconnect to shut off power to the rest of the system.
Do not control the master control relay with the controller. Provide the
operator with the safety of a direct connection between an emergency-stop
switch and the master control relay.
Using Emergency-Stop Switches
When using emergency-stop switches, adhere to the following points:

• Do not program emergency-stop switches in the controller program. Any
emergency-stop switch should turn off all machine power by turning off
the master control relay.
• Observe all applicable local codes concerning the placement and labeling
of emergency-stop switches.
• Install emergency-stop switches and the master control relay in your
system. Make certain that relay contacts have a sufficient rating for your
application. Emergency-stop switches must be easy to reach.

• In the following illustration, input and output circuits are shown with
MCR protection. However, in most applications, only output circuits
require MCR protection.
The following illustrations show the Master Control Relay wired in a grounded
system.
In most applications input circuits do not require MCR protection; however, if

you need to remove power from all field devices, you must include MCR
contacts in series with input power wiring.
Figure 1 - Schematic – Using IEC Symbols
L1 L2
230V AC
Disconnect
Fuse MCR
230V AC
I/O circuits
Isolation Operation of either of these contacts will remove

transformer power from the external I/O circuits, stopping Master Control Relay (MCR)
115V AC machine motion. Cat. No. 700-PK400A1
X1 X2
or 230V AC
Emergency-stop Stop Start Suppressor
Fuse push button Cat. No. 700-N24
Overtravel limit
switch
MCR
Suppr.
MCR
MCR
115V AC or 230V AC
I/O circuits
DC power supply.
Use IEC 950/EN 60950
_ MCR
+
24V DC
(Lo) (Hi)
I/O circuits
Line terminals: Connect to terminals of power supply.
Line terminals: Connect to 24V DC terminals of power supply.

Figure 2 - Schematic – Using ANSI/CSA Symbols
L1 L2
230V AC
Disconnect
Fuse MCR
230V AC
output
circuits
Isolation Operation of either of these contacts will remove

transformer power from the external I/O circuits, stopping
Master Control Relay (MCR)
115V AC or machine motion.
X1 X2 Cat. No. 700-PK400A1
230V AC Emergency-stop Suppressor
push button Start Cat. No. 700-N24
Fuse Overtravel limit Stop
switch
MCR
Suppr.
MCR
MCR
115V AC or 230V AC
I/O circuits
DC power supply. Use NEC

Class 2 for UL Listing.
MCR
_ +
(Lo) (Hi)
24 V DC
Line terminals: Connect to terminals of power supply I/Ocircuits
Line terminals: Connect to 24V DC terminals of power supply.

Notes:

Chapter 3
Install Your Controller
This chapter serves to guide the user on installing the controller. It includes the
following topics.
Topic Page
Controller Mounting Dimensions 39
Mounting Dimensions 39
DIN Rail Mounting 41
Panel Mounting 41
Controller Mounting Mounting Dimensions

Dimensions
Mounting dimensions do not include mounting feet or DIN rail latches.
Micro830 10-point and 16-point Controllers

2080-LC30-10QWB, 2080-LC30-10QVB, 2080-LC30-16AWB, 2080-LC30-16QWB, 2080-LC30-16QVB
100 (3.94) 80 (3.15)
90 (3.54)
Measurements in mm (in.)
Micro830 24-point Controllers

2080-LC30-24QW8B, 2080-LC30-24QVB, 2080-LC30-24QBB
150 (5.91) 80 (3.15)
90 (3.54)

Chapter 3 Install Your Controller

2080-LC30-48AWB, 2080-LC30-48QWB, 2080-LC30-48QVB, 2080-LC30-48QBB
230 (9.06) 80 (3.15)
90 (3.54)

2080-LC50-24AWB, 2080-LC50-24QBB, 2080-LC50-24QVB, 2080-LC50-24QWB,
2080-L50E-24AWB, 2080-L50E-24QBB, 2080-L50E-24QVB, 2080-L50E-24QWB
2080-LC70-24AWB, 2080-LC70-24QWB, 2080-LC70-24QWBK, 2080-LC70-24QBB, 2080-LC70-24QBBK,
2080-L70E-24AWB, 2080-L70E-24QWB, 2080-L70E-24QWBK, 2080-L70E-24QWBN, 2080-L70E-24QBB,
2080-L70E-24QBBK, 2080-L70E-24QBBN
158 (6.22) 80 (3.15)
90 (3.54)

2080-LC50-48AWB, 2080-LC50-48QWB, 2080-LC50-48QWBK, 2080-LC50-48QBB, 2080-LC50-48QVB,
2080-L50E-48AWB, 2080-L50E-48QWB, 2080-L50E-48QWBK, 2080-L50E-48QBB, 2080-L50E-48QVB,
238 (9.37) 80 (3.15)
90 (3.54)
Maintain spacing from objects such as enclosure walls, wireways, and adjacent
equipment. Allow 50.8 mm (2 in.) of space on all sides for adequate ventilation.
If optional accessories/modules are attached to the controller, such as the
power supply 2080-PS120-240VAC or expansion I/O modules, make sure that
there is 50.8 mm (2 in.) of space on all sides after attaching the optional parts.
DIN Rail Mounting
The module can be mounted using the following DIN rails: 35 x 7.5 x 1 mm
(EN 50 022 - 35 x 7.5).
For environments with greater vibration and shock concerns, use the panel
mounting method, instead of DIN rail mounting.
Before mounting the module on a DIN rail, use a flat-blade screwdriver in the
DIN rail latch and pry it downwards until it is in the unlatched position.
1. Hook the top of the DIN rail mounting area of the controller onto the
DIN rail, and then press the bottom until the controller snaps onto the
DIN rail.
2. Push the DIN rail latch back into the latched position.
Use DIN rail end anchors (Allen-Bradley part number 1492-EAJ35 or 1492-
EAHJ35) for vibration or shock environments.
To remove your controller from the DIN rail, pry the DIN rail latch downwards
until it is in the unlatched position.
Panel Mounting
The preferred mounting method is to use four M4 (#8) screws per module.
Hole spacing tolerance: ±0.4 mm (0.016 in.).
Follow these steps to install your controller using mounting screws.

1. Place the controller against the panel where you are mounting it. Make
sure the controller is spaced properly.
2. Mark drilling holes through the mounting screw holes and mounting feet
then remove the controller.
3. Drill the holes at the markings, then replace the controller and mount it.
Leave the protective debris strip in place until you are finished wiring the
controller and any other devices.
IMPORTANT For instructions on how to install your Micro800 system with expansion I/O,
see Micro800 Expansion I/O Modules User Manual, publication 2080-UM003.

Panel Mounting Dimensions

Micro830 10-Point and 16-Point Controllers
2080-LC30-10QWB, 2080-LC30-10QVB, 2080-LC30-16AWB, 2080-LC30-16QWB, 2080-LC30-16QVB
86 mm (3.39 in.)
100 mm (3.94 in.)
Micro830 24-Point Controllers

2080-LC30-24QWB, 2080-LC30-24QVB, 2080-LC30-24QBB
2080-LC50-24AWB, 2080-LC50-24QBB, 2080-LC50-24QVB, 2080-LC50-24QWB,
2080-L50E-24AWB, 2080-L50E-24QBB, 2080-L50E-24QVB, 2080-L50E-24QWB
2080-LC70-24AWB, 2080-LC70-24QWB, 2080-LC70-24QWBK, 2080-LC70-24QBB, 2080-LC70-24QBBK,
2080-L70E-24AWB, 2080-L70E-24QWB, 2080-L70E-24QWBK, 2080-L70E-24QWBN, 2080-L70E-24QBB,
2080-L70E-24QBBK, 2080-L70E-24QBBN
131 mm (5.16 in.)
100 mm (3.94 in.)

Micro830 48-Point Controllers

2080-LC30-48AWB, 2080-LC30-48QWB, 2080-LC30-48QVB, 2080-LC30-48QBB
2080-LC50-48AWB, 2080-LC50-48QWB, 2080-LC50-48QWBK, 2080-LC50-48QBB, 2080-LC50-48QVB,
2080-L50E-48AWB, 2080-L50E-48QWB, 2080-L50E-48QWBK, 2080-L50E-48QBB, 2080-L50E-48QVB
108 mm (4.25 in.) 108 mm (4.25 in.)
100 mm (3.94 in.)
System Assembly
Micro830, Micro850, and Micro870 24-point Controllers (Front)
27.8 (1.09)
45 (1.77) 145.2 (5.72) 44.4 (1.75) 14.4 (0.567)
7.2 (0.28) 7.8 (0.31) 7.8 (0.31)

33.8 (1.33)
131 (5.16)
90
110.8 (3.54)
(4.36) 100
(3.94)
7.2 (0.28)
131 (5.16) 36.6 (1.44)
7.2 (0.28) 22.8 (0.90)
Micro830/Micro850/Micro870 24-pt controller with Micro800 power supply Expansion I/O slots
(Applicable to Micro850 and Micro870 only)
Single-width (1st slot)
Double-width (2nd slot)
2085-ECR (terminator)

Micro830, Micro850, and Micro870 24-point Controllers (Side)
87 (3.42)
80 (3.15)
Micro830/Micro850/Micro870 24-pt controller with Micro800 power supply Expansion I/O Slots
(Applicable to Micro850 and Micro870 only)
Measurements in mm (in.) 2085-ECR (terminator)
Micro830 and Micro850 48-point Controllers (Front)
44.4 (1.75)
27.8 (1.09) 14.4 (0.57)
45 (1.77) 230 (9.05)
7.8
33.8 108 (4.25) 108 (4.25) (0.31)
(1.33) 7 (0.27) 7.8 (0.31)
100.1 90
(3.94) (3.54)
110.8
(4.36)
7.2 (0.28) 7 (0.27)

216 (8.50)
36.6 (1.44)
22.8 (0.90)
Micro830/Micro850 48 pt Controller with Micro800 Power Supply Expansion I/O Slots

(Applicable to Micro850 only)
Measurements in mm (in.) Double-width (2nd slot)

Micro830 and Micro850 48-point Controllers (Side)
87
(3.42)
80 (3.15)
Micro830/Micro850 48-pt controller with Micro800 power supply Expansion I/O Slots
(Applicable to Micro850 only)
Measurements in mm (in.) Single-width (1st slot)

Notes:

Chapter 4
Wire Your Controller
This chapter provides information on the Micro830, Micro850, and Micro870

controller wiring requirements. It includes the following sections:
Topic Page
Wiring Requirements and Recommendation 47
Use Surge Suppressors 48
Recommended Surge Suppressors 49
Grounding the Controller 50
Wiring Diagrams 51
Controller I/O Wiring 55
Minimize Electrical Noise 55
Analog Channel Wiring Guidelines 55
Minimize Electrical Noise on Analog Channels 56
Grounding Your Analog Cable 56
Wiring Examples 56
Embedded Serial Port Wiring 57
Wiring Requirements and

Recommendation WARNING: Before you install and wire any device, disconnect power to the
controller system.
WARNING: Calculate the maximum possible current in each power and

common wire. Observe all electrical codes dictating the maximum current
allowable for each wire size. Current above the maximum ratings may cause
wiring to overheat, which can cause damage.
United States Only: If the controller is installed within a potentially hazardous
environment, all wiring must comply with the requirements stated in the
National Electrical Code 501-10 (b).
• Allow for at least 50 mm (2 in.) between I/O wiring ducts or terminal

strips and the controller.
• Route incoming power to the controller by a path separate from the
device wiring. Where paths must cross, their intersection should be
perpendicular.
Do not run signal or communications wiring and power wiring in the
same conduit. Wires with different signal characteristics should be
routed by separate paths.
• Separate wiring by signal type. Bundle wiring with similar electrical
characteristics together.
• Separate input wiring from output wiring.

Chapter 4 Wire Your Controller
• Label wiring to all devices in the system. Use tape, shrink-tubing, or

other dependable means for labeling purposes. In addition to labeling,
use colored insulation to identify wiring based on signal characteristics.
For example, you may use blue for DC wiring and red for AC wiring.
Wire Requirements
Wire Size
Type Min Max
Micro830/ Solid 0.2 mm2 (24 AWG) 2.5 mm2 (12 AWG)
Micro850/ rated @ 90 °C (194 °F)
Micro870 insulation max
Controllers Stranded 0.2 mm2 (24 AWG) 2
2.5 mm (12 AWG)
Use Surge Suppressors Because of the potentially high current surges that occur when switching
inductive load devices, such as motor starters and solenoids, the use of some
type of surge suppression to protect and extend the operating life of the
controllers output contacts is required. Switching inductive loads without
surge suppression can significantly reduce the life expectancy of relay
contacts. By adding a suppression device directly across the coil of an inductive
device, you prolong the life of the output or relay contacts. You also reduce the
effects of voltage transients and electrical noise from radiating into adjacent
systems.
Figure 3 shows an output with a suppression device. We recommend that you

locate the suppression device as close as possible to the load device.
Figure 3 - Output with Suppression Device

+DC or L1
Suppression
device
VAC/DC
Out 0
Out 1
Out 2
AC or DC
Out 3
outputs Load
Out 4
Out 5
Out 6
Out 7
COM DC COM or L2
If the outputs are DC, we recommend that you use an 1N4004 diode for surge
suppression, as shown in Figure 4 on page 49. For inductive DC load devices, a
diode is suitable. A 1N4004 diode is acceptable for most applications. A surge
suppressor can also be used. See Recommended Surge Suppressors on page 49.
These surge suppression circuits connect directly across the load device.

Figure 4 - DC Outputs with Surge Suppression

+24V DC
VAC/DC
Out 0
Out 1
Out 2
Relay or solid-state Out 3
DC outputs Out 4
Out 5 IN4004 diode
Out 6
Out 7 A surge suppressor can
24V DC common
also be used.
COM
Suitable surge suppression methods for inductive AC load devices include a

varistor, an RC network, or an Allen-Bradley surge suppressor, shown in
Figure 5. These components must be appropriately rated to suppress the
switching transient characteristic of the particular inductive device. See
Recommended Surge Suppressors on page 49 for recommended suppressors.
Figure 5 - Surge Suppression for Inductive AC Load Devices
Output device Output device Output device
Surge
suppressor
Varistor RC network
Recommended Surge Suppressors
Use the Allen-Bradley surge suppressors shown in the following table for use
with relays, contactors, and starters.
Recommended Surge Suppressors

Device Coil Voltage Suppressor Catalog Number Type(4)
24…48V AC 100-KFSC50
110…280V AC 100-KFSC280 RC
380…480V AC 100-KFSC480
Bulletin 100/104K 700K 12…55 V AC, 12…77V DC 100-KFSV55
56…136 VAC, 78…180V DC 100-KFSV136 MOV
137…277V AC, 181…250 V DC 100-KFSV277
12…250V DC 100-KFSD250 Diode

Recommended Surge Suppressors (Continued)

Device Coil Voltage Suppressor Catalog Number Type(4)
24…48V AC 100-FSC48(1)
110…280V AC 100-FSC280(1) RC
380…480V AC 100-FSC480(1)
12…55V AC, 12…77V DC 100-FSV55(1)
Bulletin 100C, (C09…C97)
56…136V AC, 78…180V DC 100-FSV136(1)
MOV
137…277V AC, 181…250V DC 100-FSV277(1)
278…575V AC 100-FSV575(1)
12…250V DC 100-FSD250(1) Diode
12…120V AC 599-K04
Bulletin 509 Motor Starter Size 0...5 MOV
240…264V AC 599-KA04
12…120V AC 199-FSMA1(2) RC
Bulletin 509 Motor Starter Size 6
12…120V AC 199-GSMA1(3) MOV
AC coil Not Required
24…48V DC 199-FSMA9
Bulletin 700 R/RM Relay
50…120V DC 199-FSMA10 MOV
130…250V DC 199-FSMA11
6…150V AC/DC 700-N24 RC
24…48V AC/DC 199-FSMA9
Bulletin 700 Type N, P, PK, or PH Relay 50…120V AC/DC 199-FSMA10 MOV
130…250V AC/DC 199-FSMA11
6…300V DC 199-FSMZ-1 Diode
Miscellaneous electromagnetic devices limited to 35 6…150V AC/DC 700-N24 RC
sealed VA
(1) Catalog numbers for screwless terminals include the string ’CR’ after ’100-’. For example: Cat. No. 100-FSC48 becomes Cat. No. 100-CRFSC48; Cat. No. 100-FSV55 becomes 100-CRFSV55; and
so on.
(2) For use on the interposing relay.
(3) For use on the contactor or starter.
(4) RC Type not to be used with Triac outputs. Varistor is not recommended for use on the relay outputs.
Grounding the Controller This product is intended to be mounted to a well grounded mounting surface
such as a metal panel. See the Industrial Automation Wiring and Grounding
Guidelines, publication 1770-4.1, for additional information.
WARNING: All devices connected to the RS-232/RS-485 communication port

must be referenced to controller ground, or be floating (not referenced to a
potential other than ground). Failure to follow this procedure may result in
property damage or personal injury.

Wiring Diagrams The following illustrations show the wiring diagrams for the Micro800
controllers. Controllers with DC inputs can be wired as either sinking or
sourcing inputs. Sinking and sourcing does not apply to AC inputs.
High-speed inputs and outputs are indicated by .
2080-LC30-10QWB
Input terminal block
COM0 I-01 I-03 I-04 NC NC
1 2 3 4 5 6 7 8 9 10 11 12
I-00 I-02 COM1 I-05 NC NC
Output terminal block
+DC24 CM0 CM1 CM2 CM3 NC
1 2 3 4 5 6 7 8 9 10 11 12
-DC24 O-00 O-01 O-02 O-03 NC
2080-LC30-10QVB
COM0 I-01 I-03 I-04 NC NC
1 2 3 4 5 6 7 8 9 10 11 12
I-00 I-02 COM1 I-05 NC NC
+DC24 +CM0 O-01 +CM1 O-03 NC
1 2 3 4 5 6 7 8 9 10 11 12
-DC24 O-00 -CM0 O-02 -CM1 NC
2080-LC30-16AWB, 2080-LC30-16QWB
COM0 I-01 I-03 I-04 I-06 I-08
1 2 3 4 5 6 7 8 9 10 11 12
I-00 I-02 COM1 I-05 I-07 I-09
+DC24 CM0 CM1 CM2 CM3 O-04
1 2 3 4 5 6 7 8 9 10 11 12
-DC24 O-00 O-01 O-02 O-03 O-05
2080-LC30-16AWB has no high-speed inputs.
2080-LC30-16QVB
COM0 I-01 I-03 I-04 I-06 I-08
1 2 3 4 5 6 7 8 9 10 11 12
I-00 I-02 COM1 I-05 I-07 I-09
+DC24 +CM0 O-01 +CM1 O-03 O-04
1 2 3 4 5 6 7 8 9 10 11 12
-DC24 O-00 -CM0 O-02 -CM1 O-05

2080-LC30-24QWB, 2080-LC50-24AWB, 2080-LC50-24QWB, 2080-L50E-24AWB, 2080-L50E-24QWB,

2080-LC70-24AWB, 2080-LC70-24QWB, 2080-LC70-24QWBK, 2080-L70E-24AWB, 2080-L70E-24QWB,
2080-L70E-24QWBK, 2080-L70E-24QWBN
COM0 I-01 I-03 I-05 I-07 I-08 I-10 I-12
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
+DC24 CM0 CM1 CM2 O-03 O-05 O-06 O-08
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
-DC24 O-00 O-01 O-02 O-04 CM3 O-07 O-09
2080-LC30-24QWB, 2080-LC50-24QWB, 2080-L50E-24QWB, 2080-LC70-24QWB,

2080-LC70-24QWBK, 2080-L70E-24QWB, 2080-L70E-24QWBK, 2080-L70E-24QWBN,
DC Input Configuration
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
L
COM0 I-01 I-03 I-05 I-07 I-08 I-10 I-12
N 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
+DC24 CM0 CM1 CM2 O-03 O-05 O-06 O-08

+24 VDC
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
-DC24 O-00 O-01 O-02 O-04 CM3 O-07 O-09
-24 VDC
CR CR CR CR CR
+DC c L1 b L1 c
+DC c
-DC c L2 b L2 c
-DC c
IMPORTANT • Do not connect –DC24 (Output terminal 2) to Earth/Chassis Ground.

• In Micro870 systems that use more than four Micro800 Expansion I/O
modules, we recommend using a 1606-XLP60EQ power supply instead of
a 2080-PS120-240VAC power supply. Make sure to wire both the Micro870
controller and 2085-EP24VDC expansion power supply to the same
1606-XLP60EQ power supply.

2080-LC50-24AWB, 2080-L50E-24AWB, 2080-LC70-24AWB, 2080-L70E-24AWB,

L2 a L1 a L2 b L1 b
L1 L2
2080-PS120-240VAC
L
COM0 I-01 I-03 I-05 I-07 I-08 I-10 I-12
N 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
+DC24 CM0 CM1 CM2 O-03 O-05 O-06 O-08

+24 VDC
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
-DC24 O-00 O-01 O-02 O-04 CM3 O-07 O-09
-24 VDC
CR CR CR CR CR
+DC c L1 b L1 c
+DC c
-DC c L2 b L2 c
-DC c
IMPORTANT Do not connect –DC24 (Output terminal 2) to Earth/Chassis Ground.

2080-LC30-24QVB, 2080-LC30-24QBB, 2080-LC50-24QVB, 2080-LC50-24QBB, 2080-L50E-24QVB,
2080-L50E-24QBB, 2080-LC70-24QBB, 2080-LC70-24QBBK, 2080-L70E-24QBB, 2080-L70E-24QBBK,
2080-L70E-24QBBN
COM0 I-01 I-03 I-05 I-07 I-08 I-10 I-12
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
+DC24 +CM0 O-01 +CM1 O-03 O-05 O-07 O-09
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
2080-LC30-24QBB, 2080-LC50-24QBB, 2080-L50E-24QBB, 2080-LC70-24QBB, 2080-LC70-24QBBK,

2080-L70E-24QBB, 2080-L70E-24QBBK, 2080-L70E-24QBBN,

L1 L2
2080-PS120-240VAC
L
COM0 I-01 I-03 I-05 I-07 I-08 I-10 I-12
N
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
+DC24 +CM0 O-01 +CM1 O-03 O-05 O-07 O-09

+24 VDC
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
-24 VDC
CR CR
+DC d +DC e
-DC d -DC e

IMPORTANT • Do not connect –DC24 (Output terminal 2) to Earth/Chassis Ground.

• In Micro870 systems that use more than four Micro800 Expansion I/O
modules, we recommend using a 1606-XLP60EQ power supply instead of
a 2080-PS120-240VAC power supply. Make sure to wire both the Micro870
controller and 2085-EP24VDC expansion power supply to the same
1606-XLP60EQ power supply.
2080-LC30-24QVB, 2080-LC50-24QVB, 2080-L50E-24QVB, DC Input Configuration

L1 L2
2080-PS120-240VAC
L
COM0 I-01 I-03 I-05 I-07 I-08 I-10 I-12
N
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
+DC24 +CM0 O-01 +CM1 O-03 O-05 O-07 O-09

+24 VDC
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
-24 VDC
CR CR
+DC d -DC d +DC e -DC e
IMPORTANT Do not connect –DC24 (Output terminal 2) to Earth/Chassis Ground.

2080-LC30-48AWB, 2080-LC30-48QWB, 2080-LC50-48AWB, 2080-LC50-48QWB,
2080-LC50-48QWBK, 2080-L50E-48AWB, 2080-L50E-48QWB, 2080-L50E-48QWBK
Input terminal blocks
COM0 I-01 I-03 I-05 I-06 I-08 I-10 COM2
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
TERMINAL BLOCK 1
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
I-14 I-16 I-18 COM3 I-21 I-23 I-25 I-27
TERMINAL BLOCK 3
Output terminal blocks
+DC24 CM0 CM1 CM2 CM3 CM4 CM5 CM6
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
TERMINAL BLOCK 2
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
O-07 O-09 O-11 O-12 O-14 CM9 O-17 O-19
TERMINAL BLOCK 4
2080-LC30-48AWB has no high-speed inputs.

2080-LC30-48QVB, 2080-LC30-48QBB, 2080-LC50-48QVB, 2080-LC50-48QBB, 2080-L50E-48QVB,

2080-L50E-48QBB
Input terminal blocks
COM0 I-01 I-03 I-05 I-06 I-08 I-10 COM2
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
TERMINAL BLOCK 1
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
I-14 I-16 I-18 COM3 I-21 I-23 I-25 I-27
TERMINAL BLOCK 3
Output terminal blocks
+DC24 +CM0 O-01 O-03 +CM1 O-05 O-07 O-09
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
-DC24 O-00 O-02 -CM0 O-04 O-06 O-08 -CM1
TERMINAL BLOCK 2
+CM2 O-11 O-13 O-15 +CM3 O-17 O-19 NC
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
O-10 O-12 O-14 -CM2 O-16 O-18 -CM3 NC
TERMINAL BLOCK 4
Controller I/O Wiring This section contains some relevant information about minimizing electrical
noise and also includes some wiring examples.
Minimize Electrical Noise
Because of the variety of applications and environments where controllers are

installed and operating, it is impossible to ensure that all environmental noise
will be removed by input filters. To help reduce the effects of environmental
noise, install the Micro800 system in a properly rated (for example, NEMA)
enclosure. Make sure that the Micro800 system is properly grounded.
A system may malfunction due to a change in the operating environment after

a period of time. We recommend periodically checking system operation,
particularly when new machinery or other noise sources are installed near the
Micro800 system.
Analog Channel Wiring Guidelines
Consider the following when wiring your analog channels:

• The analog common (COM) is not electrically isolated from the system,
and is connected to the power supply common.
• Analog channels are not isolated from each other.
• Use Belden cable #8761, or equivalent, shielded wire.
• Under normal conditions, the drain wire (shield) should be connected to
the metal mounting panel (earth ground). Keep the shield connection to
earth ground as short as possible.
• To ensure optimum accuracy for voltage type inputs, limit overall cable
impedance by keeping all analog cables as short as possible. Locate the
I/O system as close to your voltage type sensors or actuators as possible.

Minimize Electrical Noise on Analog Channels
Inputs on analog channels employ digital high-frequency filters that

significantly reduce the effects of electrical noise on input signals. However,
because of the variety of applications and environments where analog
controllers are installed and operated, it is impossible to ensure that all
environmental noise will be removed by the input filters.
Several specific steps can be taken to help reduce the effects of environmental
noise on analog signals:
• install the Micro800 system in a properly rated enclosure, for example,
NEMA. Make sure that the shield is properly grounded.
• use Belden cable #8761 for wiring the analog channels, making sure that
the drain wire and foil shield are properly earth grounded.
• route the Belden cable separately from any AC wiring. Additional noise
immunity can be obtained by routing the cables in grounded conduit.
Grounding Your Analog Cable
Use shielded communication cable (Belden #8761). The Belden cable has two
signal wires (black and clear), one drain wire, and a foil shield. The drain wire
and foil shield must be grounded at one end of the cable.
Foil shield
Black wire
Insulation
Drain wire
Clear wire
IMPORTANT Do not ground the drain wire and foil shield at both ends of the cable.
Wiring Examples
Examples of sink/source, input/output wiring are shown below.
Sink output wiring example User side
+V DC Fuse
Logic side
D Load +
OUT
G –
24V supply
DC COM
Micro800 Sink output

Sink input wiring example
Com 24V
DC
~ +
I/P
Fuse
Source output wiring example

+V DC Fuse
Logic side User side

S OUT
+
G
–
Load
24V supply
DC COM
Micro800 source output
Source input wiring example
Com
Fuse
~
+
I/P
24V
DC
Embedded Serial Port The embedded serial port is a non-isolated RS-232/RS-485 serial port, which is
Wiring targeted to be used for short distances (<3 m) to devices such as HMIs.
See Embedded Serial Port Cables on page 21 for a list of cables that can be used
with the embedded serial port 8-pin Mini DIN connector.
For example, the 1761-CBL-PM02 cable is typically used to connect the

embedded serial port to PanelView™ 800 HMI using RS-232.

Embedded Serial Port

2 1
5 3
8 7 6
Pinout Explanations
Pin Definition RS-485 Example RS-232 Example
1 RS-485+ B(+) (not used)
2 GND GND GND
3 RS-232 RTS (not used) RTS
4 RS-232 RxD (not used) RxD
5 RS-232 DCD (not used) DCD
6 RS-232 CTS (not used) CTS
7 RS-232 TxD (not used) TxD
8 RS-485- A(-) (not used)
IMPORTANT • Do not connect the GND pin of the serial port to Earth/Chassis Ground. The
GND pin of the serial port is the DC common for the Serial Port
Communication signals and is not intended for Shield Ground.
• If the length of the serial cable is more than 3 meters, use an isolated serial
port, catalog number 2080-SERIALISOL.

Chapter 5
Communication Connections
Overview This chapter describes how to communicate with your control system and
configure communication settings. The method you use and cabling required
to connect your controller depends on what type of system you are employing.
This chapter also describes how the controller establishes communication with
the appropriate network. Topics include:
Topic Page
Supported Communication Protocols 59
CIP Communications Pass-thru 64
Use Modems with Micro800 Controllers 65
Configure Serial Port 66
Configure Ethernet Settings 71
Configure CIP Serial Driver 73
OPC Support Using FactoryTalk Linx 73
The Micro830, Micro850, and Micro870 controllers have the following

embedded communication channels:
• a non-isolated RS-232/RS-485 combo port
• a non-isolated USB programming port
In addition, the Micro850 and Micro870 controllers have an RJ-45 Ethernet

port.
Supported Communication Micro830, Micro850, and Micro870 controllers support communication

Protocols through the embedded RS-232/RS-485 serial port as well as any installed serial
port plug-in modules. In addition, Micro850 and Micro870 controllers also
support communication through the embedded Ethernet port, and can be
connected to a local area network for various devices providing 10 Mbps/
100 Mbps transfer rate.
These are the communication protocols supported by Micro830/Micro850/

Micro870 controllers:
• Modbus RTU Master and Slave
• CIP Serial Client/Server (DF1)
• CIP Symbolic Client/Server
• ASCII
• DNP3 (1)
(1) DNP3 is only supported on 2080-L70E-24QxBN controllers.

Chapter 5 Communication Connections
These are the communication protocols supported by Micro850 and Micro870

controllers only:
• EtherNet/IP Client/Server
• Modbus TCP Client/Server
• DHCP Client
• Sockets Client/Server TCP/UDP
Connection Limits for Micro830/Micro850/Micro870 Controllers
Micro850/
Description Micro830 Micro870
CIP Connections
Total number of client plus server connections for all ports 16 24
Maximum number of client connections for all ports 15 16
Maximum number of server connections for all ports 16 24
Client 16
Maximum number of EtherNet/IP connections –
Server 23
Client – –
Maximum number of USB connections
Server 15 23
Client 15 16
Maximum number of Serial connections
Server 15 23
TCP Connections
Total number of client plus server connections 64
Client 16
Maximum number for EtherNet/IP
Server 16
–
Client 16
Maximum number for Modbus TCP
Server 16
Maximum number for User Programmable Sockets 8
User Programmable Sockets
Total number of User Programmable Sockets – 8
(any combination of UDP plus TCP Client/Server)
IMPORTANT If all client/server connections are fully loaded, performance may be

affected, such as data loss and intermittent delays during communication.
Here are some configuration examples based on the limits described in the
table above:
1. The maximum number of drives that can be controlled over EtherNet/IP
is 16. This is due to the maximum limit of TCP Client connections is 16,
and the maximum limit of EtherNet/IP Client connections is also 16.
2. If you have 10 devices controlled over EtherNet/IP, the maximum
number of devices that can be controlled over serial is six. This is due to
the maximum limit of Client connections is 16.
3. The total number of UDP sockets plus TCP Client/Server sockets has a
maximum limit of eight.

Modbus RTU
Modbus is a half-duplex, master-slave communications protocol. The Modbus

network master reads and writes bits and registers. Modbus protocol allows a
single master to communicate with a maximum of 247 slave devices. Micro800
controllers support Modbus RTU Master and Modbus RTU Slave protocol. For
more information on configuring your Micro800 controller for Modbus
protocol, see the Connected Components Workbench Online Help. For more
information about the Modbus protocol, see Modbus Protocol Specifications
available from https://www.modbus.org.
For information on Modbus mapping, see Modbus Mapping for Micro800 on

page 251.
To configure the serial port as Modbus RTU, see Configure Modbus RTU on
page 68.
Use MSG_MODBUS instruction to send Modbus messages over serial port.
CIP Serial Client/Server – DF1
CIP Serial Client/Server allows CIP protocol to be used over a serial port. It is
typically used with modems. The advantage over non-CIP serial protocols is
that since the protocol is CIP, program downloads are supported including
CIP pass-through from the serial port to Ethernet.
ASCII
ASCII provides connection to other ASCII devices, such as bar code readers,
weigh scales, serial printers, and other intelligent devices. You can use ASCII
by configuring the embedded or any plug-in serial RS-232/RS-485 port for the
ASCII driver. See the Connected Components Workbench Online Help for
more information.
To configure the serial port for ASCII, see Configure ASCII on page 70.
Modbus TCP Client/Server
The Modbus TCP Client/Server communication protocol uses the same

Modbus mapping features as Modbus RTU, but instead of the serial port, it is
supported over Ethernet. Modbus TCP Server takes on Modbus Slave features
on Ethernet.
No protocol configuration is required other than configuring the Modbus

mapping table. For information on Modbus mapping, see Modbus Mapping
for Micro800 on page 251.
Use MSG_MODBUS2 instruction to send Modbus TCP messages over

Ethernet port.

With Connected Components Workbench software version 12 or later, the

Modbus TCP Server is disabled by default. If you want to use Modbus TCP, you
can enable it from the Ethernet settings.
CIP Symbolic Client/Server

CIP Symbolic is supported by any CIP-compliant interface including Ethernet
(EtherNet/IP) and serial port (CIP Serial). This protocol allows HMIs to easily
connect to the Micro830/Micro850/Micro870 controller.
Micro850 and Micro870 controllers support up to 16 simultaneous EtherNet/IP

client connections and 23 simultaneous EtherNet/IP Server connections.
CIP Serial, supported on Micro830, Micro850, and Micro870 controllers,

makes use of DF1 Full-Duplex protocol, which provides point-to-point
connection between two devices.
DF1 Half-duplex Master, DF1 Half-Duplex Slave, and DF1 Radio Modem are
supported in Micro850 (2080-L50E) and Micro870 (2080-L70E) controllers.
These protocols provide connection to multiple devices over RS-485 or radio
modems.
The Micro800 controllers support the protocol through RS-232 connection to

external devices, such as computers running RSLinx® Classic software,
PanelView Component terminals (firmware revisions 1.70 and above),
PanelView 800 terminals, or other controllers that support CIP Serial over DF1
Full-Duplex, such as ControlLogix® and CompactLogix™ controllers that have
embedded serial ports. Bulletins 2080-L50E and 2080-L70E also support DF1
Half Duplex and Radio Modem protocol.
EtherNet/IP, supported on the Micro850 and Micro870 controller, makes use

of the standard Ethernet TCP/IP protocol.
The Micro850 and Micro870 controller supports up to 23 simultaneous

EtherNet/IP Server connections.
To configure CIP Serial, see Configure CIP Serial Driver on page 66.
To configure for EtherNet/IP, see Configure Ethernet Settings on page 71.
For more information on DF1 protocol, see Connect to Networks using DF1 on
page 325.

CIP Symbolic Addressing
Users may access any global variables through CIP Symbolic addressing except
for system and reserved variables.
One- or two-dimension arrays for simple data types are supported (for
example, ARRAY OF INT[1…10, 1…10]) are supported but arrays of arrays (for
example, ARRAY OF ARRAY) are not supported. Array of strings are also
supported.
Supported Data Types in CIP Symbolic

Data Type(1) Description
Logical Boolean with values TRUE(1) and FALSE(0)
BOOL (Uses up 8 bits of memory)
SINT Signed 8-bit integer value
INT Signed 16-bit integer value
DINT Signed 32-bit integer value
LINT(2) Signed 64-bit integer value
USINT Unsigned 8-bit integer value
UINT Unsigned 16-bit integer value
UDINT Unsigned 32-bit integer value
ULINT(2) Unsigned 64-bit integer value
REAL 32-bit floating point value
LREAL(2) 64-bit floating point value
STRING character string (1 byte per character)
(3) Unsigned 32-bit integer value
DATE
TIME(3) Unsigned 32-bit integer value
(1) Logix MSG instruction can read/write SINT, INT, DINT, LINT, and REAL data types using “CIP Data Table Read” and “CIP Data
Table Write” message types.
BOOL, USINT, UINT, UDINT, ULINT, LREAL, STRING, SHORT_STRING, DATE, and TIME data types are not accessible with the Logix
MSG instruction.
(2) Not supported in PanelView Component or PanelView 800.
(3) Can be used by sending data to UDINT, mainly for use with PanelView Plus and PanelView 800 HMI terminals.
CIP Client Messaging
CIP Generic and CIP Symbolic messages are supported on Micro800

controllers through the Ethernet and serial ports. These client messaging
features are enabled by the MSG_CIPSYMBOLIC and MSG_CIPGENERIC
function blocks.
For more information and sample quickstart project to help you use the CIP
Client Messaging feature, see Micro800 Programmable Controllers: Getting
Started with CIP Client Messaging, publication 2080-QS002.
Sockets Client/Server TCP/UDP
Sockets protocol is used for Ethernet communications to devices that do not

support Modbus TCP and EtherNet/IP. Sockets support client and server, and
TCP and UDP. Typical applications include communicating to printers,
barcode readers, and PCs.

CIP Communications Pass- The Micro830, Micro850, and Micro870 controllers support pass-thru on any
thru communications port that supports Common Industrial Protocol (CIP) for
applications such as program download. It does not support applications that
require dedicated connections such as HMI. Micro830, Micro850, and
Micro870 controllers support a maximum of one hop. A hop is defined to be an
intermediate connection or communications link between two devices – in
Micro800, this is through EtherNet/IP or CIP Serial or CIP USB.
Examples of Supported Architectures

USB to EtherNet/IP
USB EtherNet/IP
Micro850 Micro850
controller1 controller2
For program download
The user can download a program from the PC to controller1 over USB. Also, the program
can be downloaded to controller2 and controller3 over USB to EtherNet/IP.
Micro850
controller3
EtherNet/IP to CIP Serial
EtherNet/IP CIP Serial
Micro850 Micro830
controller1 controller2
For program download
USB to DeviceNet
USB DeviceNet Esc Sel

PowerFlex® 525 drive
with
25-COMM-D adapter
(Address 1)
Micro850 controller
with
For program download 2080-DNET20 plug-in scanner
(Address 0)
CompactBlock™ LDX I/O

(Address 2)

EtherNet/IP to DeviceNet
EtherNet/IP DeviceNet Esc Sel

PowerFlex 525 drive
with
25-COMM-D adapter
(Address 1)
Micro850 controller
with
For program download 2080-DNET20 plug-in scanner
(Address 0)
The user can use Connected Components Workbench software to

configure the PowerFlex drives.
CompactBlock LDX I/O
(Address 2)
IMPORTANT Micro800 controllers do not support more than one hop (for example, from
EtherNet/IP -> CIP Serial -> EtherNet/IP).
Use Modems with Micro800 Serial modems can be used with the Micro830, Micro850, and Micro870
Controllers controllers.
Making a DF1 Point-to-Point Connection

You can connect the Micro830, Micro850, and Micro870 programmable
controller to your serial modem using an Allen-Bradley null modem serial
cable (1761-CBL-PM02) to the controller’s embedded serial port together with a
9-pin null modem adapter – a null modem with a null modem adapter is
equivalent to a modem cable. The recommended protocol for this
configuration is CIP Serial.
Construct Your Own Modem Cable
If you construct your own modem cable, the maximum cable length is 15.24 m
(50 ft) with a 25-pin or 9-pin connector. See the following typical pinout for
constructing a straight-through cable:
DTE Device
(Micro830/850/870 DCE Device
Channel 0) (Modem, etc)
8-Pin 25-Pin 9-Pin
7 TXD TXD 2 3
4 RXD RXD 3 2
2 GND GND 7 5
1 B(+) DCD 8 1
8 A(-) DTR 20 4
5 DCD DSR 6 6
6 CTS CTS 5 8
3 RTS RTS 4 7

Configure Serial Port You can configure the serial port driver as CIP Serial, Modbus RTU, ASCII, or
Shutdown through the Device Configuration tree in the Connected
Components Workbench software.
Configure CIP Serial Driver

1. Open your Connected Components Workbench project. On the device
configuration tree, go to the Controller properties. Click Serial Port.
2. Select CIP Serial from the Driver field.
3. Specify a baud rate. Select a communication rate that all devices in your
system support. Configure all devices in the system for the same
communication rate. Default baud rate is set at 38,400 bps.
4. In most cases, parity and station address should be left at default
settings.

5. Click Advanced Settings and set Advanced parameters.

See Table 5 for a description of the CIP Serial parameters.
Table 5 - CIP Serial Driver Parameters
Parameter Options Default
Toggles between the communication rate of 1200, 2400, 4800,
Baud Rate 38400
9600, 19200, and 38400.
Specifies the parity setting for the serial port. Parity provides
Parity additional message-packet error detection. Select Even, Odd, or None
None.
Station (Node) Address Enter a1 for
Enter value from 0…254. 1
DF1 Full-Duplex.
Defines the DF1 mode – Full-Duplex, Half-Duplex master, Configured as full-
DF1 Mode(1) Half-Duplex slave, Radio Modem(2). duplex by default.
• Full-Duplex: No Handshake, Full-Duplex (RTS always ON).
• Half-Duplex slave: No Handshake, Half-Duplex without
continuous carrier (RTS/CTS).
Configured as no
Control Line • Half-Duplex master: No Handshake, Half-Duplex without handshake by default.
continuous carrier (RTS/CTS), Full Duplex (RTS always ON).
• Radio Modem: No Handshake, Half-Duplex without continuous
carrier (RTS/CTS), Half-Duplex with DCD Handshake.
Detects and eliminates duplicate responses to a message.
Duplicate Packet Duplicate packets may be sent under noisy communication Enabled
Detection conditions when the sender’s retries are not set to 0. Toggles
between Enabled and Disabled.
Error Detection Toggles between CRC and BCC. CRC
To use embedded responses, choose Enabled Unconditionally. If
you want the controller to use embedded responses only when it
detects embedded responses from another device, choose After
Embedded Responses One Received. After One Received
If you are communicating with another Allen-Bradley device,
choose Enabled Unconditionally. Embedded responses increase
network traffic efficiency.
The number of times the controller will resend a message packet
NAK Retries because the controller received a NAK response to the previous 3
message packet transmission.
The number of enquiries (ENQs) that you want the controller to send
ENQ Retries 3
after an ACK timeout occurs.
Specifies the number of times a message is retried after the first
Transmit Retries attempt before being declared undeliverable. Enter a value from 3
0…127.
Specifies the amount of time after a packet is transmitted that an
ACK Timeout (x20 ms) 50
ACK is expected.
Enabled, Disabled
When EOT Suppression is enabled, the slave does not respond
EOT Suppression when polled if no message is queued. This saves modem Disabled
transmission power and time when there is no message to
transmit.
0...65,535 (can be set in 20 ms increments)
Poll Timeout only applies when a slave device initiates a MSG
instruction. It is the amount of time that the slave device waits
for a poll from the master device. If the slave device does not
Poll Timeout (x20 ms) receive a poll within the Poll Timeout, a MSG instruction error is 3000
generated, and the ladder program needs to re-queue the MSG
instruction. If you are using a MSG instruction, it is
recommended that a Poll Timeout value of zero not be used. Poll
Timeout is disabled when set to zero.
RTS Off Delay (x20 ms) Specifies the delay time between when the last serial character 0
is sent to the modem and when RTS is deactivated. Gives the
modem extra time to transmit the last character of a packet.
RTS Send Delay (x20 ms) Specifies the time delay between setting RTS until checking for 0
the CTS response. For use with modems that are not ready to
respond with CTS immediately upon receipt of RTS.

Table 5 - CIP Serial Driver Parameters (Continued)

0...255
Specifies the number of times a slave device attempts to resend
Message Retries a message packet when it does not receive an ACK from the 3
master device. For use in noisy environments where message
packets may become corrupted in transmission.
Priority Polling Range – Select the last slave station address to priority poll. 0
High
Priority Polling Range – Select the first slave station address to priority poll. Entering 255 255
Low disables priority polling.
Normal Polling Range – Select the last slave station address to normal poll. 0
High
Normal Polling Range – Select the first slave station address to normal poll. Entering 255 255
Low disables normal polling.
Enter the quantity of active stations located in the normal poll
range that you want polled during a scan through the normal poll
Normal Poll Group Size range before returning to the priority poll range. If no stations 0
are configured in the Priority Polling Range, leave this parameter
at 0.
Defines the amount of time, in 20 ms increments, that the
master station will wait after receiving an ACK (to a master-
Reply Message Wait initiated message) before polling the slave station for a reply. 5
Timeout Choose a time that is, at minimum, equal to the longest time that
a slave station needs to format a reply packet. This would
typically be the maximum scan time of the slave station.
If you want to:
• Receive only one message from a slave station per its turn,
choose STANDARD (SINGLE MESSAGE TRANSFER PER NODE
SCAN). Choose this method only if it is critical to keep the poll
list scan time to a minimum.
• Receive as many messages from a slave station as it has,
choose STANDARD (MULTIPLE MESSAGE TRANSFER PER NODE
SCAN).
• Accept unsolicited messages from slave stations, choose
MESSAGE BASED (ALLOW SLAVES TO INITIATE MESSAGES)
• Slave station-initiated messages are acknowledged and
processed after all master station-initiated (solicited)
messages. MESSAGE BASED
Polling Mode Slave stations can only send messages when they are polled. (ALLOW SLABES TO
If the message-based master station never sends a slave INITIATE MESSAGES)
station a message, the master station will never send the
slave station a poll. Therefore, to regularly obtain a slave
station-initiated message from a slave station, you should
choose to use standard communication mode instead.
• Ignore unsolicited messages from slave stations, choose
MESSAGE BASED (DO NOT ALLOW SLAVES TO INITIATE
MESSAGES)
Slave station-initiated messages are acknowledged and
discarded. The master station acknowledges the slave
station-initiated message so that the slave station removes
the message from its transmit queue, which allows the next
packet slated for transmission into the transmit queue.
(1) For more information on DF1 protocol, see Connect to Networks using DF1 on page 325
(2) Half-Duplex and Radio Modem DF1 modes are only supported on Micro850 (2080-L50E) and Micro870 (2080-L70E) controllers.
Configure Modbus RTU


2. Select Modbus RTU on the Driver field.
3. Specify the following parameters:

• Baud rate
• Parity
• Unit address
• Modbus Role (Master, Slave, Auto)
Modbus RTU Parameters
Baud Rate 1200, 2400, 4800, 9600, 19200, 38400 19200
Parity None, Odd, Even None
Modbus Role Master, Slave, Auto Master

4. Click Advanced Settings to set advanced parameters.

See the table for available options and default configuration for advanced
parameters.
Modbus RTU Advanced Parameters
Media RS-232, RS-232 RTS/CTS, RS-485 RS-232
Data Bits Always 8 8
Stop Bits 1, 2 1
Response Timer 0…999,999,999 milliseconds 200
Broadcast Pause 0…999,999,999 milliseconds 200
Inter-char Timeout 0…999,999,999 microseconds 0
RTS Pre-delay 0…999,999,999 microseconds 0
RTS Post-delay 0…999,999,999 microseconds 0
Configure ASCII
configuration tree, go to Controller properties. Click Serial Port.
2. Select ASCII on the Driver field.
3. Specify baud rate and parity.
ASCII Parameters
Baud Rate 1200, 2400, 4800, 9600, 19200, 38400 19200
Parity None, Odd, Even None
4. Click Advanced Settings to configure advanced parameters.

ASCII Advanced Parameters

Parameters Options Default
Full Duplex
Half-duplex with continuous carrier
Control Line No Handshake
Half-duplex without continuous carrier
No Handshake
CRT
Deletion Mode Ignore Ignore
Printer
Data Bits 7, 8 8
Stop Bits 1, 2 1
XON/XOFF Enabled or Disabled Disabled
Echo Mode Enabled or Disabled Disabled
Append Chars 0x0D,0x0A or user-specified value 0x0D,0x0A
Term Chars 0x0D,0x0A or user-specified value 0x0D,0x0A
Configure Ethernet Settings 1. Open your Connected Components Workbench project (for example,
Micro850). On the device configuration tree, go to Controller properties.
Click Ethernet.
2. Under Ethernet, click Internet Protocol.

Configure Internet Protocol (IP) settings. Specify whether to obtain the
IP address automatically using DHCP or manually configure IP address,
subnet mask, and gateway address.

The Ethernet port defaults to the following out-of-the box settings:

• DHCP (dynamic IP address)
• Address Duplicate Detection: On
IMPORTANT When a DHCP server fails, the Micro800 controller allocates IP

addresses in the private range 169.254.0.1 to 169.254.255.254. The
Micro800 controller verifies its address is unique on the network
using ARP. When the DHCP server is again able to service
requests, the Micro800 controller updates its address
automatically.
3. Click the checkbox Detect duplicate IP address to enable detection of
duplicate address.
4. Under Ethernet, click Port Settings.
5. Set Port State as Enabled or Disabled.

6. To manually set connection speed and duplexity, uncheck the option box
Auto-Negotiate speed and duplexity. Then, set Speed (10 Mbps or 100
Mbps) and Duplexity (Half or Full) values.
7. Click Save Settings to Controller if you would like to save the settings to
your controller.
8. On the device configuration tree, under Ethernet, click Port Diagnostics
to monitor Interface and Media counters. The counters are available and
updated when the controller is in Debug mode.
Validate IP Address
Modules must validate the incoming IP address configuration, whether it is
obtained through explicit configuration or through DHCP.
The following rules must be obeyed when configuring the IP address:

• The IP address for the module cannot be set to zero, a multicast address,
a broadcast address, or an address on the Class A loopback network
(127.x.x.x).
• The IP address should not start with zero, and the IP address network ID
should be not zero.
• The Network mask cannot be set to 255.255.255.255.
• The Gateway address must be on the same subnet as the IP address that
is being configured.
• The Name Server address cannot be set to zero, a multicast address, a
broadcast address, or an address on the Class A loopback network
(127.x.x.x).

The valid range of static IPv4 IP address exclude:

• Broadcast or zero IP (255.255.255.255 or 0.0.0.0)
• IP address starting with 0 or 127 (0.xxx.xxx.xxx or 127.xxx.xxx.xxx)
• IP address ending with 0 or 255 (xxx.xxx.xxx.0 or xxx.xxx.xxx.255)
• IP addresses in range 169.254.xxx.xxx (169.254.0.0 to 169.254.255.255)
• IP addresses in range 224.0.0.0 to 255.255.255.255
Ethernet Host Name

Micro800 controllers implement unique host names for each controller, to be
used to identify the controller on the network. The default host name is
comprised of two parts: product type and MAC address, separated by a
hyphen. For example: 2080LC50-xxxxxxxxxxxx, where xxxxxxxxxxxx is the
MAC address.
The user can change the host name using the CIP Service Set Attribute Single
when the controller is in Program/Remote Program mode.
Configure CIP Serial Driver 1. Open your Connected Components Workbench project. On the device
2. Select CIP Serial from the Driver field.
3. Specify a baud rate. Select a communication rate that all devices in your
system support. Configure all devices in the system for the same
communication rate. Default baud rate is set @ 38,400 bps.
4. In most cases, parity and station address should be left at default
settings.
5. Click Advanced Settings and set Advanced parameters.
OPC Support Using Support for Open Platform Communications (OPC) using CIP symbolic has
FactoryTalk Linx been added from firmware release 7.011 onwards. This can be used in place of
Modbus addressing.
FactoryTalk® Linx software version 5.70 (CPR9 SR7) or later and FactoryTalk®
Linx Gateway software version 3.70 (CPR9 SR7) or later are required.

Notes:

Chapter 6
Micro870 Controller Distributed Network

Protocol
Overview This chapter describes how to configure the DNP3 communication settings.
Topics include:
Topic Page
Channel Configuration for DNP3 Slave 75
DNP3 Slave Application Layer 100
DNP3 Objects and Controller Variables 105
DNP3 Device Attribute Object 116
Event Reporting 117
Collision Avoidance 122
Time Synchronization 123
Diagnostics 124
Function Codes 126
Implementation Table 127
Channel Configuration for The default communication protocol for the serial ports is DF1 Full-Duplex. To
DNP3 Slave communicate with Distributed Network Protocol (DNP3), the channel must be
configured for DNP3 Slave.
The default communication protocol for the Ethernet channel in the controller
is EtherNet/IP. To communicate with DNP3 over IP protocol, select DNP3 over
IP Enable in the Ethernet configuration page.
IMPORTANT The DNP3 protocol is only supported in the following Micro870

controllers.
• 2080-L70E-24QBBN
• 2080-L70E-24QWBN
To program the controller, use Connected Components Workbench software

version 20.01.00 or later.

Chapter 6 Micro870 Controller Distributed Network Protocol
In Connected Components Workbench software, open the Micro870 controller

project tree.
There are three configurations related to DNP3 protocol in Connected

Components Workbench software:
• Serial and/or Ethernet port configuration
• DNP3 Slave Application Layer configuration.
Serial Port Link Layer Configuration
Link Layer related configuration can be done in the Serial Port configuration
page.

Ethernet Layer Configuration
To enable DNP3 over IP protocol, select DNP3 over IP Enable in the Ethernet
configuration page.
Link Layer related configuration can also be done in the Ethernet

configuration page.

DNP3 Slave Application Layer Configuration
Application Layer related configuration can be done in the DNP3 Slave

configuration page.
DNP3 Slave configuration is shared by the serial and Ethernet ports if multiple
ports are configured for DNP3 protocol. Any changes in the DNP3 Slave
configuration page affects all ports.
Serial Link Layer Configuration Parameters
Driver
This selection should be set to DNP3 Slave to communicate with DNP3

protocol.
Node Address
This value is a node address of this DNP3 Slave.

The valid range is 0…65519.
Default value is 1.
Baud
The selections can be 38400, 19200, 9600, 4800, 2400, and 1200.
Default selection is 38400.
Parity
The selections can be NONE, EVEN, and ODD. Default selection is NONE.

Stop Bits
The selections can be 1 and 2.

Default selection is 1.
Enable Master Address Validation
Valid selections are Enabled (Checked) and Disabled (Unchecked). Default

value is Disabled (Unchecked).
When the selection is Disabled (Unchecked), the controller accepts the

requests from any DNP3 Master.
When the selection is Enabled (Checked), the controller accepts the requests
only from the DNP3 Master which is configured in the Master Node0…Master
Node4. The maximum number of Master Node Addresses for the Master
Address Validation is 5.
Enable Self-Address

When this bit is Disabled (Unchecked), any packets which contain the
destination address 65532(FFFCh) are ignored.
When this bit is Enabled (Checked), any packets which contain the destination
address 65532(FFFCh) are accepted and processed.
Any responses back to the DNP3 Master includes the actual configured DNP3
address of the Micro870 controller.
Master Node0
This value is used to:

• validate the Master node address when the Enable Master Address
Validation is Enabled (Checked)
• send Unsolicited Response when Unsolicited Response functionality is
enabled. An Unsolicited Response is sent out to the DNP3 Master having
this address.
The valid range is 0…65519. Default value is 0.
Master Node1, Master Node2, Master Node3, Master Node4
This value is used to check validation for Master node address when Enable
Master Address Validation is Enabled (Checked).

Control Line
The selections can be No Handshake and Half-Duplex without continuous

carrier (CTS/RTS).
Default selection is No Handshake.
When the controller is connected to DNP3 Master using RS-232 line directly,
you must select No Handshake. If you want to use the Modem line in a half
duplex network, you must select Half-Duplex without continuous carrier
(CTS/RTS). If the controller is connected to an RS-485 network, you must select
No Handshake.
Request LL Confirmation

When the selection is Disabled (Unchecked), Primary Frames from the

controller are sent out with the function code
FC_UNCONFIRMED_USER_DATA (4).
When the selection is Enabled (Checked), Primary Frames from the controller
are sent out with the function code FC_CONFIRMED_USER_DATA (3). In this
case, the controller waits for the confirmation and may retry the Frame if it did
not receive the confirmation from DNP3 Master within the time Confirmation
Timeout (x1 ms).
Send LL Confirmation

When the selection is Disabled (Unchecked), the optional Secondary Frame is

not sent out with the function code FC_NACK (1) or FC_NOT_SUPPORTED (15).
When the selection is Enabled (Checked), the optional Secondary Frame is sent
out with the function code FC_NACK (1) or FC_NOT_SUPPORTED (15).
IMPORTANT Micro870 (2080-L70E-24QxBN) controllers support this function only

when the DNP3 Master sends confirmed user data. This function is not
supported when the DNP3 Master sends unconfirmed user data.
Confirmation Timeout (x1 ms)
When Request LL Confirmation is enabled, the controller waits to receive a

confirmation frame until this timeout has expired.

Message Retries
When Confirmation Timeout (x1 ms) has expired and this parameter was non-
zero value, the controller tries to send retry packets.
Pre-transmit Delay (x1 ms)
The controller waits for the specified time before sending the packet.
RTS Off Delay (x1 ms)
When the Control is set at Half Duplex Modem (CTS/RTS handshaking), this
feature is enabled. This specifies a time delay between the end of a
transmission and dropping of the RTS signal.
RTS Send Delay (x1 ms)
When the Control is set at Half Duplex Modem (CTS/RTS handshaking), this
entry is enabled. This specifies a time delay between the raising of the RTS and
the initiation of a transmission.
Max Random Delay (x1 ms)
This parameter is used with Pre-transmit Delay (x1 ms) for Collision Avoidance
on RS-485 network. For more details, see Collision Avoidance on page 122.
Ethernet Layer Configuration Parameters

The DNP3 over IP subsystem in the controller supports Listening End Point,
TCP Dual End Point and Datagram End Point type.
Listening End Point type supports a single TCP connection as a Server and
UDP datagram.
TCP Dual End Point type supports a single TCP connection as a Server, a single
TCP connection as a Client and UDP datagram.
Datagram End Point type supports UDP datagram from DNP3 Masters. The
default TCP and UDP port numbers are 20000 and the port numbers are
configurable.

The End Point type can be determined by the parameter End Point Type.
According to the parameter, the controller works as different End Point types.
See Table 6 for each configuration.
Table 6 - End Point Types

End Point Type Connection Description
Any of the requests are accepted and the responses
are transmitted via this connection.
A single TCP server connection The unsolicited responses are transmitted via this
Listening End Point connection when this connection is available.
Accepts only broadcast packets when DNP3
UDP datagram destination node is one of 0xFFFD, 0xFFFE and
0xFFFF in the request.
The unsolicited responses are transmitted via this
A single TCP server connection connection when this connection is available.
This connection has higher priority than the Client
connection.
Dual End Point The unsolicited responses are transmitted via this
A single TCP client connection connection when this connection is available.
The controller does not request TCP client connection
to DNP3 Master until an unsolicited response is
generated.
Accepts only broadcast packets when DNP3
UDP datagram destination node is one of 0xFFFD, 0xFFFE and
0xFFFF in the request.
All responses can be transmitted to the different
DNP3 Master port according to the configuration of
the parameters Remote UDP Port Number and Master
Datagram End Point UDP datagram only IP Address0. If this parameter is not set to 0, the
solicited responses are sent to the DNP3 Master port
that is configured. If this parameter is set to 0, the
solicited responses are sent to the DNP3 Master port
that sent the request.
TCP connection is not available in this configuration.
The parameter DNP3 over IP Enable is configured in the Ethernet

configuration page and other parameters are configured in the DNP3 Slave
configuration page.
DNP3 over IP Enable
The valid selections are Enabled (Checked) and Disabled (Unchecked). Default
When the selection is Disabled (Unchecked), DNP3 service over Ethernet is

disabled after the configuration is downloaded to the controller.
When the selection is Enabled (Checked), DNP3 service over Ethernet is

enabled after the configuration is downloaded to the controller.
Enable Master Address Validation


only from the DNP3 Master Node Address which is configured in the
parameters Master Node0 on page 79, and Master Node1, Master Node2,
Master Node3, Master Node4 on page 79. The maximum number of Master
Node Address for the Master Address Validation is 5.
Enable Self-Address
When this bit is Disabled (Unchecked), any packets which contain the
destination address 65532 (FFFCh) are ignored.
When this bit is Enabled (Checked), any packets which contain the destination
address 65532 (FFFCh) are accepted and processed.
Any responses back to the DNP3 Master includes the actual configured DNP3
address of the Micro870 controller.
Enable Access Control

only from the DNP3 Master IP Address which is configured in the parameters
Master IP Address0 to Master IP Address4. The maximum number of Master
IP Address for the Access Control is 5.
End Point Type
The valid selections are Listening, Dual and Datagram Only.
Default is Listening End Point Type.
Master Node0

• validate Master node address when the Enable Master Address
Validation is Enabled (Checked)
this address.

Master Node1, Master Node2, Master Node3, Master Node4
This value is used for validation of the Master node address when the Enable
Master Address Validation is Enabled (Checked). This value is only shown and
valid when the Enable Master Address Validation is Enabled (Checked).
Master IP Address0

• validate Master IP address when the Enable Access Control is Enabled
(Checked)
this address.
The valid value is an IP address. Default value is 0.0.0.0.
Master IP Address1, Master IP Address2, Master IP Address3, Master IP Address4
This value is used for validation of the Master IP address when the Enable
Access Control is Enabled (Checked). This value is only shown and valid when
the Enable Access Control is Enabled (Checked).
The valid value is an IP address. Default value is 0.0.0.0.
Master TCP Port Number (Unsol)
This value is used to configure Master TCP Port Number for Unsolicited
Response.
Master UDP Port Number for Initial Unsolicited
This value is used to configure Master UDP Port Number for Initial Unsolicited
Response if the parameter End Point Type is selected as Datagram Only.

Master UDP Port Number
This value is used to configure Master UDP Port Number if the parameter End
Point Type is selected as Datagram Only.
Keep Alive Interval (x 1s)
This parameter specifies a time interval for TCP Keep Alive mechanism.
If the timer times out, the controller transmits a keep-alive message. The keep-
alive message is a DNP Data Link Layer status request
(FC_REQUEST_LINK_STATUS). If a response is not received to the keep-alive
message, the controller deems the TCP connection broken and closes the TCP
connection.
Slave Node Address
This value is a node address of this DNP3 Slave.
Local Port Number (UDP)
This value is used to configure Local UDP Port Number which is used for UDP
socket listening.
Local Port Number (TCP)
This value is used to configure Local TCP Port Number which is used for TCP
socket listening.

DNP3 Slave Application Layer Configuration Parameters
Channel for Unsolicited Response
Only channels already configured for DNP3 protocol appear in the Channel for
Unsolicited Response dropdown menu. Any and all Unsolicited Responses are
transmitted via this selected channel.
Restore Events After Power Cycle
When the selection is Disabled (Unchecked), DNP3 events which are generated
before a power cycle are flushed after a power cycle. When the option is
Enabled (Checked), all DNP3 events are restored after a power cycle.
Valid selections are Enabled (Checked) and Disabled (Unchecked), with

disabled as default value.
Unsolicited Responses On Start Up

When the selection is Disabled (Unchecked), the controller does not send any
enabled Unsolicited Responses after a restart until it has received a
FC_ENABLE_UNSOLICITED (20) command from the DNP3 Master.
When the selection is Enabled (Checked), the controller sends any enabled
Unsolicited Responses after a restart to the DNP3 Master unconditionally.
Unsolicited Responses For Class1

When the selection is Disabled (Unchecked), Unsolicited Response is disabled

for Class 1 events. To prevent overflowing of the event buffer, DNP3 Master
should poll for Class 1 events.
When the selection is Enabled (Checked), Unsolicited Response is enabled for

Class 1 events.

Unsolicited Responses For Class2



Class 2 events.
Enable Unsolicited For Class3



Class 3 events.
Send Initial Unsolicited Null Response On Start Up

When the selection is Disabled (Unchecked), the controller does not send
Unsolicited NULL Response with RESTART IIN bit on startup.
When the selection is Enabled (Checked), the controller sends Unsolicited

NULL Response with RESTART IIN bit on startup.
This selection is also used for sending the Restart IIN bit during Driver and
Channel configuration changes. See Internal Indications on page 104 for more
information.
Enable Confirmation

When the selection is Disabled (Unchecked), the controller sends Response

packets with CON bit set in its header under the following conditions only:
• When the response has Event data.
• When the response is multi-fragment response.
• When the Unsolicited Response is sent.

When the selection is Enabled (Checked), the controller always sends

Response packets with the CON bit set in its header, which causes the DNP3
Master to send replies confirming that it received each Response packet
without error.
Enable Time Synchronization

This parameter used with Time Synchronization Interval (x1 mins).
When the selection is Disabled (Unchecked), the controller does not perform
any time synchronization.
When the selection is Enabled (Checked), the controller sets the NEED_TIME
Internal Indication bit (IIN1.4) on power up and every interval configured in
Time Synchronization Interval (x1 mins).
Time Synchronization Interval (x1 mins)
This parameter is used with Enable Time Synchronization. Only valid when
Enable Time Synchronization is Enabled (Checked).
The valid range is 0…32767. Default value is 0. If the value is 0, the NEED_TIME
Internal Indication (IIN1.4) bit are set at startup and then after every Time
Synchronization Interval minutes if the value is greater than 0.
When the parameter Enable Time Synchronization is Disabled (Unchecked),

the IIN1.4 bit is never turned on.
Max Response Size
The controller sends Application Layer frame to fit in Max Response Size. If
the Response packet size is larger than this value, the controller fragments the
Response packet.
The valid range is 27…2048 in bytes. Default value is 2048.
Confirmation Timeout (x1 ms)
When Enable Confirmation is enabled, the controller waits for Application

Layer Confirmation until the Confirmation Timeout (x1 ms) has expired.
The valid range is 100…65535 in 1 ms increments. Default value is 10000.
Number of Retries
This parameter is only for Unsolicited Response. If this value has the
maximum which is 65535, it means infinite retries of the Unsolicited Response.

Number of Class1 Events
If the controller is configured not to initiate Class 1 Unsolicited Responses, this

parameter is used to limit the maximum number of events, which is generated
and logged into the event buffer for Class 1 events. In this case, value 0 disables
Class 1 event generation.
If the controller is configured to generate Unsolicited Responses, and the

number of queued Class 1 events reaches this value, an Unsolicited Response is
initiated.

See DNP3 10K Event Logging on page 119 for more information.
Hold Time after Class1 Events (x 1s)
This parameter is only for a Class 1 Unsolicited Response. The controller holds
the events during Hold Time after Class1 Events (x 1s) before initiating an
Unsolicited Response.
The value of 0 indicates that responses are not delayed due to this parameter.
The parameters Number of Class1 Events and Hold Time after Class1 Events
(x 1s) are used together so that if either one of the criteria are met, an
Unsolicited Response is transmitted.
By default, the Hold time is re-triggered for each new event detected.
If the controller is configured not to initiate Class 2 Unsolicited Responses,

this parameter is used to limit the maximum number of events, which is
generated and logged into the event buffer for Class 2 events. In this case,
value 0 disables Class 2 event generation.

initiated.

See DNP3 10K Event Logging on page 119 for more information

The Parameters Number of Class2 Events and Hold Time after Class2 Events
If the controller is configured not to initiate Class 3 Unsolicited Responses, this

parameter is used to limit the maximum number of events, which is generated
and logged into the event buffer for Class 3 events. In this case, value 0 disables
Class 3 event generation.

initiated.

See DNP3 10K Event Logging on page 119 for more information.
The parameters Number of Class3 Events and Hold Time after Class3 Events
Select Timeout (x 1s)
This parameter is used for controlling CROB (Control Relay Output Block) and
AOB (Analog Output Block). After receiving the request with the function code
FC_SELECT(3), DNP3 Master should send the request with the function code
FC_OPERATE(4) within this configured time.

DNP3 Object Data and Config
The DNP3 Mapping selection under DNP3 Slave in the controller properties
allow you to define the mapping of the listed DNP3 object and object properties
(class number, online/offline status, object quality flags, deadbands, and/or
thresholds) to controller variables.
See DNP3 Objects and Controller Variables on page 105 for more information.
DNP3 Secure Authentication
The controller implements the DNP3 Secure Authentication based on the

DNP3 Specification, Supplement to Volume 2, Secure Authentication,
Version 2.00 and 5.00.
DNP3 Secure Authentication has been implemented in the DNP3 Application

Layer of the controller system. If you configure any parameters regarding
DNP3 Secure Authentication in the DNP3 Slave Application Layer
configuration, it affects all ports which are configured for DNP3 protocol in
the controller.
Enable Secure Authentication
When the selection is Disabled (Unchecked), the controller disables DNP3

Secure Authentication subsystem.
When the selection is Enabled (Checked), the controller enables DNP3 Secure
Authentication subsystem.

Secure Authentication Version
This parameter specifies the authentication version that this DNP3 slave
controller uses.
Select 2 for Secure Authentication version 2 and select 5 for Secure

Authentication version 5. Default value is 2.
Enable Aggressive Mode in Secure Authentication
When the selection is Disabled (Unchecked), the controller disables DNP3

Aggressive Mode in Secure Authentication subsystem.
When the selection is Enabled (Checked), the controller enables DNP3

Aggressive Mode in Secure Authentication subsystem.
Critical Function Code in Secure Authentication
This critical function code in the DNP3 Slave configuration page is used to
define the list of the critical function codes in Secure Authentication. A critical
function code should be defined by clicking the number icon to change it
between Critical and Non-critical.
The following table shows the default state of the function codes that are
defined in Connected Components Workbench software.
Function Codes
Function Code Critical FCs Function Code Critical FCs
0 (0x00) non-critical 20 (0x14) critical
1 (0x01) non-critical 21 (0x15) critical
2 (0x02) critical 22 (0x16) non-critical
4 (0x04) critical 24 (0x18) critical
6 (0x06) critical 26 (0x1A) non-critical
7 (0x07) non-critical 27 (0x1B) non-critical
8 (0x08) non-critical 28 (0x1C) non-critical
9 (0x09) non-critical 29 (0x1D) critical

Function Codes (Continued)

Function Code Critical FCs Function Code Critical FCs
10 (0x0A) non-critical 30 (0x1E) non-critical
11 (0x0B) non-critical 31 (0x1F) critical
12 (0x0C) non-critical 129 (0x81) non-critical
13 (0x0D) critical 130 (0x82) non-critical
14 (0x0E) critical
Expected Session Key Change Interval (x1 min) in Secure Authentication
This parameter is used for configuring the expected session key change
interval in minutes.
The valid range is 0…120 (min). Default value is 15 mins.
When DNP3 Master does not change the Session Key within this time
configured, the controller invalidate the Session Key and its state for each user.
Expected Session Key Change Count in Secure Authentication
This parameter is used for configuring the expected session key change count.
Reply Timeout (x100 ms) in Secure Authentication
This parameter is used for configuring the reply timeout in 100 ms.
The valid range is 0…1200 (120 s). Default value is 20 (2 s).
Maximum Error Count in Secure Authentication
This parameter is used for configuring the maximum error count.
HMAC Algorithm in Secure Authentication
This parameter is used for configuring the HMAC Algorithm.

• SHA-1
- Truncated to 4 octets (serial)
- Truncated to 10 octets (networked)
• SHA-256
- Truncated to 8 octets (serial)
- Truncated to 16 octets (networked)
Default value is SHA-256.

Update Key in Secure Authentication
This parameter is used to define user information Secure Authentication.
In Connected Components Workbench software, you can create the user keys
in the DNP3 Slave configuration page.
User Number
Valid range is 1…65535.
User Role
A dropdown selection of various roles that you can define for each user
number (Viewer, Operator, Engineer, Installer, SECADM, SECAUD,
RBACMNT, and single user).
User Name
Define the unique name for each user, up to 32 characters (numbers,
alphabets, and symbols).
Update Key
The key to be used by each user, up to 32 hexadecimal digits.
To create a new user, follow these steps.

1. Click Configure to open Update Key.
2. Click Add.
3. Enter the User Number, select the User Role, enter the User Name, and
enter the Update Key.
4. Click Encrypt or OK to create the new user.
5. Download the project to the controller to update the user information in
the controller.
To remove an existing user, follow these steps.

1. Click Configure to open Update Key.
2. Select the user to be removed and click Delete.
3. Click OK to close the window.
4. Download the project to the controller to update the user information in
the controller.

Update Key Change Method and Certificate Authority Key
IMPORTANT This feature is only available in Secure Authentication Version 5.
A Certificate Authority Key is a Symmetric (encrypted) or Public (not

encrypted) key that is stored in the controller for authentication with the DNP3
master when a Key change request is processed.
Symmetric Key
Public Key
The type of key used in the certificate is based on the Update Key Change
Method setting that you have selected in the configuration. To define the key,
select one of the following settings.
• To use Symmetric Key in authorization:
- AES-128/SHA-1-HMAC
- AES-256/SHA-256-HMAC
• To use Public Key in authorization:
- RSA-2048/RSA SHA-256/SHA-256/HMAC
- RSA-3072/RSA SHA-256/SHA-256-HMAC
To configure the Certificate Authorization Key, click Configure.
To define a Symmetric Key, enter 32 or 64 characters into the field, depending

on the Update Key Change Method that you have selected. Click OK to accept
and encrypt the key.

To define a Public Key, you must generate an RSA-2048 or RSA-3072 Public

Key, depending on the Update Key Change Method that you have selected, and
enter it into the field. Click OK to accept the changes. Public Keys are not
encrypted.
Example of a Public Key
Default Variation Config
This configuration is used to define default variations in a response to a

Class 0 poll request.
In Connected Components Workbench software version 20.01.00 or later, you

can select Default Variation Table in the DNP3 Slave configuration page to
change the configuration.

Table 7 shows the structure of the DNP3 Default Variation Configuration File.
Table 7 - DNP3 Default Variation Configuration File
Group Default Variation for the following Objects Standard Default Variation Alternate Default Variations
0 - All variation
1 Binary Input Static Object 1 - Packed format 2 - With flag
0 - All variation
2 Binary Input Change Object 3 - With relative time 1 - Without time
2 - With absolute time
0 - All variation
3 Double Bit Binary Input Static Object 1 - Packed format 2 - With flag
0 - All variation
4 Double Bit Binary Input Change Object 3 - With relative time 1 - Without time
2 - With absolute time
0 - All variation
10 Binary Output Static Object 2 - Output status with flag 1 - Packed format
0 - All variation
11 Binary Output Change Object 2 - Status with time 1 - Status without time
0 - All variation
13 Binary Output Command 2 - Command status with time 1 - Command status without time
0 - All variation
1 - 32-bit with flag
16-bit Counter Static Object 6 - 16-bit without flag 2 - 16-bit with flag
5 - 32-bit without flag
20
0 - All variation
32-bit Counter Static Object 5 - 32-bit without flag 2 - 16-bit with flag
0 - All variation
Frozen 16-bit Counter Static Object 10 - 16-bit without flag 5 - 32-bit with flag and time
6 - 16-bit with flag and time
21
0 - All variation
Frozen 32-bit Counter Static Object 9 - 32-bit without flag 5 - 32-bit with flag and time

Table 7 - DNP3 Default Variation Configuration File (Continued)

0 - All variation
16-bit Counter Change Object 2 - 16-bit with flag 5 - 32-bit with flag and time
22
0 - All variation
32-bit Counter Change Object 1 - 32-bit with flag 5 - 32-bit with flag and time
0 - All variation
Frozen 16-bit Counter Change Object 2 - 16-bit with flag 5 - 32-bit with flag and time
23
0 - All variation
Frozen 32-bit Counter Change Object 1 - 32-bit with flag 5 - 32-bit with flag and time
0 - All variation
16-bit Analog Input Static Object 4 - 16-bit without flag 3 - 32-bit without flag
5 - Single-precision, floating-point with flag
6 - Double-precision, floating-point with flag
0 - All variation
30 32-bit Analog Input Static Object 3 - 32-bit without flag 4 - 16-bit without flag
5 - Single-precision, floating-point with flag
0 - All variation
Short Float Analog Input 5 - Single-precision, floating-point with flag 3 - 32-bit without flag
0 - All variation
1 - 32-bit without time
3 - 32-bit with time
16-bit Analog Input Change Object 2 - 16-bit without time 5 - Single-precision, floating-point without time
6 - Double-precision, floating-point without time
7 - Single-precision, floating-point with time
8 - Double-precision, floating-point with time
0 - All variation
32 32-bit Analog Input Change Object 1 - 32-bit without time 5 - Single-precision, floating-point without time
0 - All variation
Short Float Analog Input Change Object 5 - Single-precision, floating-point without time 4 - 16-bit with time


0 - All variation
Frozen 16-bit Analog Input Change Object 2 - 16-bit without time 5 - Single-precision, floating-point without time
0 - All variation
33 Frozen 32-bit Analog Input Change Object 1 - 32-bit without time 5 - Single-precision, floating-point without time
0 - All variation
Frozen Short Float Analog Input Change Object 5 - Single-precision, floating-point without time 4 - 16-bit with time
0 - All variation
16-bit Analog Input Reporting Dead Band 1 - 16-bit 2 - 32-bit
3 - Single-precision, floating-point
0 - All variation
34 32-bit Analog Input Reporting Dead Band 2 - 32-bit 1 - 16-bit
3 - Single-precision, floating-point
0 - All variation
Short Float Analog Input Reporting Dead Band 3 - Single-precision, floating-point 1 - 16-bit
2 - 32-bit
0 - All variation
16-bit Analog Output Static Object 2 - 16-bit with flag 3 - Single-precision, floating-point with flag
0 - All variation
40 32-bit Analog Output Static Object 1 - 32-bit with flag 3 - Single-precision, floating-point with flag
0 - All variation
Short Float Analog Output Status 3 - Single-precision, floating-point with flag 2 - 16-bit with flag
0 - All variation
16-bit Analog Output Change Object 2 - 16-bit without time 5 - Single-precision, floating-point without time
0 - All variation
42 32-bit Analog Output Change Object 1 - 32-bit without time 5 - Single-precision, floating-point without time
0 - All variation
Short Float Analog Output Change Object 5 - Single-precision, floating-point without time 4 - 16-bit with time


0 - All variation
16-bit Analog Output Command Change Object 2 - 16-bit without time 5 - Single-precision, floating-point without time
0 - All variation
43 32-bit Analog Output Command Change Object 1 - 32-bit without time 5 - Single-precision, floating-point without time
0 - All variation
Short Float Analog Output Command Change Object 5 - Single-precision, floating-point without time 4 - 16-bit with time
DNP3 Slave Application This section covers DNP3 Slave Application Layer Function Codes and Internal
Layer Indications. All of the Function Codes that are supported in the controller are
summarized in Function Codes for DNP3 in Micro870 Controllers on page 126.
For details of Packet Formats for the request and response, see the DNP3
Protocol specifications.
Function Codes
CONFIRM (FC Byte = 0x00)
00 – Confirm
A DNP3 master sends a message with this function code to confirm receipt of a
response fragment. In a general environment, the controller receives a
response with this function code. But the controller may generate a response
with this function code when a DNP3 Master sends a request with the CON bit
set in the application control header.
READ (FC Byte = 0x01)
01 – Read
The READ function code is used by a DNP3 master to request data from the
controller.

WRITE (FC Byte = 0x02)
02 – Write
The WRITE function code is used to write the contents of DNP3 objects from
the DNP3 master to the controller. This function code is used for clearing bit
IIN1.7 [DEVICE_RESTART], setting time in the controller and downloading
user programs to the controller.
SELECT (FC Byte = 0x03)
03 – Select
The SELECT function code is used in conjunction with the OPERATE function
code as part of select-before-operate method for issuing control requests. This
procedure is used for controlling binary output (CROB) or analog output
(AOB) objects.
OPERATE (FC Byte = 0x04)
04 – Operate
See SELECT (FC Byte = 0x03) on page 101.
DIRECT_OPERATE (FC Byte = 0x05)
05 – Direct Operate
This direct operate function is similar to the FC_OPERATE function code
except that no preceding select command is required.
DIRECT_OPERATE_NR (FC Byte = 0x06)
06 – Direct Operate No Resp

See DIRECT_OPERATE (FC Byte = 0x05). No response message is returned
when this request is issued from a DNP3 master.
IMMED_FREEZE (FC Byte = 0x07)
07 – Immediate Freeze
Upon receiving a request with this function, the controller copies the current
value of a counter point to a separate memory location associated with the
same point. The copied value remains constant until the next freeze operation
to the same point.
IMMED_FREEZE_NR (FC Byte = 0x08)
08 – Immediate Freeze No Resp

See IMMED_FREEZE (FC Byte = 0x07). No response message is returned when
this request is issued from a DNP3 master.
FREEZE_CLEAR (FC Byte = 0x09)
09 – Freeze and Clear
Upon receiving a request with this function, the controller copies the current
value to the frozen value, then clears the current value to 0 immediately.
FREEZE_CLEAR_NR (FC Byte = 0x0A)
10 – Freeze and Clear No Resp

See FREEZE_CLEAR (FC Byte = 0x09). No response message is returned when
this request is issued from a DNP3 master.
COLD_RESTART (FC Byte = 0x0D)
13 – Cold Restart
This function code forces the controller to perform a complete restart upon
powering up.
WARM_RESTART (FC Byte = 0x0E)
14 – Warm Restart
This function code forces the controller to perform a partial reset.
INITIALIZE_APPL (FC Byte = 0x10)
16 – Initialize Application
This function code is used to initialize the user program which was
downloaded by Connected Components Workbench software.
START_APPL (FC Byte = 0x11)
17 – Start Application
This function code is used to start the user program which was downloaded by
Connected Components Workbench software.
STOP_APPL (FC Byte = 0x12)
18 Stop Application
This function code is used to stop the user program which was downloaded by
ENABLE_UNSOLICITED (FC Byte = 0x14)
20 – Enable Unsolicited Message

This function is used to dynamically enable unsolicited messages generated in
the controller.
DISABLE_UNSOLICITED (FC Byte = 0x15)
21 – Disable Unsolicited Message

This function is used to dynamically disable unsolicited messages generated in
the controller.
DELAY_MEASURE (FC Byte = 0x17)
23 – Delay Measurement, used for Non-LAN Procedure

This function code is used to measure the communication channel delay time.

RECORD_CURRENT_TIME (FC Byte = 0x18)
24 – Record Current Time, used for LAN Procedure

This function code is used in the procedure for time synchronizing controllers
that communicate over a LAN.
OPEN_FILE (FC Byte = 0x19)
25 – Open File
This function code is used to make a file available for reading or writing.
CLOSE_FILE (FC Byte = 0x1A)
26 – Close File
After the file reading or writing operation, this function code used to unlock
the file.
DELETE_FILE (FC Byte = 0x1B)
27 – Delete File
A DNP3 master uses this function code to delete a file.
GET_FILE_INFO (FC Byte = 0x1C)
28 – Get File Information

This function code is for the master to retrieve information about a file in the
controller.
AUTHENTICATE_FILE (FC Byte = 0x1D)
29 – Authenticate File
This function code is used to obtain an authentication key that is needed to
open or delete a file.
ABORT_FILE (FC Byte = 0x1E)
30 – Abort File
This function code is used to immediately request termination of the current
read/write operation and close the file, without saving.
ACTIVATE_CONFIG (FC Byte = 0x1F)
31 – Activate Config
This function code is used to begin using the configuration or executable code
specified by the objects included in the request.
AUTHENTICATE_REQ (FC Byte = 0x20)
32 – Authentication Request
The master uses this function code when sending authentication messages to
the controller that require a response

AUTHENTICATE_ERR (FC Byte = 0x21)
33 – Authentication Request No Resp

This function code is used by the master to send authentication messages
when no return response is required.
RESPONSE (FC Byte = 0x22)
129 – Response
All responses except for Unsolicited Response messages use this function code.
UNSOLICITED_RESPONSE (FC Byte = 0x23)
130 – Unsolicited Response

Unsolicited Responses always use this function code regardless of which DNP3
objects are included.
AUTHENTICATE_RESPONSE (FC Byte = 0x24)
131 – Authentication Response

This function code is used to issue authentication messages to the master.
Internal Indications
Internal Indication bits are set under the following conditions of the
controllers:
• IIN1.0: ALL_STATIONS. This bit is set when an all-stations message is
received.
• IIN1.1: CLASS_1_EVENTS. This bit is set when Class 1 event data is
available.
available.
available.
• IIN1.4: NEED_TIME. This bit is set when Time synchronization is
required.
• IIN1.5: LOCAL_CONTROL. This bit is set when the controller is in Non-
executing mode.
• IIN1.6: DEVICE_TROUBLE. This bit is set when the controller is in Fault
mode.
• IIN1.7: DEVICE_RESTART. This bit is set when the DNP3 driver is just
configured, in channel configuration or when the controller has been
restarted.
To set this bit during the driver configuration and channel
configuration, you need to select the Send Init. Unsol. Null Resp. on
Restart setting and set Status Bit S:36/13 to 1 before downloading to the
controller.
• IIN2.0: NO_FUNC_CODE_SUPPORT. This bit is set when a request
which has an unknown function code is received.
• IIN2.1: OBJECT_UNKNOWN. This bit is set when a request which has an
unknown object is received.

• IIN2.2: PARAMETER_ERROR. This bit is set when a request with a

qualifier/range field that cannot be processed is received.
• IIN2.3: EVENT_BUFFER_OVERFLOW. This bit is set when an event
buffer overflow condition exists in the controller and at least one
unconfirmed event is lost.
• IIN2.4: ALREADY_EXECUTING. Not supported.
• IIN2.5: CONFIG_CORRUPT. This bit is set when a bad file type and bad
file number are detected.
• IIN2.6: Reserved.
• IIN2.7: Reserved.
DNP3 Objects and Controller All of the DNP3 Objects that are supported in the controller are summarized in
Variables Implementation Table for Micro870 controllers on page 128.
Variables used in DNP3 Objects are not the same as that used in the controller,
but are similar. Mapping is required between variables in DNP3 Objects and
controller variables.
Overview
DNP3 Data objects that are implemented in the controller are listed below:
• DNP3 Binary Input Object
• DNP3 Double Bit Binary Input Object
• DNP3 Binary Output Object
• DNP3 Counter Object
• DNP3 Frozen Counter Object
• DNP3 Analog Input Object
• DNP3 Analog Output Object
• DNP3 BCD Object
• DNP3 Data-Set Object
Some of objects are divided into several Object files to map data in the
controller.
• Counter Object — 16-bit and 32-bit Counter Object
• Analog Input Object — 16-bit and 32-bit Analog Input Object, and Short
Floating Point Analog Input Object.
• Analog Output Object — 16-bit and 32-bit Analog Output Object, and
Short Floating Point Analog Output Object.

DNP3 Mapping for Micro870 controllers
You can create the different data objects by mapping them to the variables
created in the controller. You can configure the Data object for each DNP3
Object in the DNP3 Slave configuration page. Variables can be BOOL, INT,
DINT, or REAL data types.
DNP3 Object Data

Table 8 - Relationship between DNP3 Object Database and Micro800 Variables
DNP Objects Micro800 Variables
Object Name Related Groups Maximum Configurable Index Data Name Maximum Configurable Elements
Binary Input Object 1, 2 4096 Binary Input Object 256
Double Bit Binary Input Object 3, 4 2048 Double Bit Binary Input Object 256
Binary Output Object 10, 12 4096 Binary Input Object 256
16-bit Counter Object
Counter Object 20, 22 256 256
32 bit Counter Object
Reflection of Counter Object which Reflection of 16-bit Counter Object
Frozen Counter Object 21, 23 -
was configured Reflection of 32-bit Counter Object
16-bit Analog Input Object
Analog Input Object 30, 32 256 32-bit Analog Input Object 256
Short Floating Point Analog Input Object
16-bit Analog Output Object
Analog Output Object 40, 41 256 32-bit Analog Output Object 256
Short Floating Point Analog Output Object
BCD Object 101 256 Small BCD Object 256
85, 87, 88 Data-Set Prototypes Object
Data-Set Object 10 10
86, 87, 88 Data-Set Descriptors Object

DNP3 Configuration
You can configure parameters such as Class level and Object Flag bit
information for each element. This information is defined during object
creation in the data mapping window in DNP3 mapping.
DNP3 Data Set Object
To create a Data Set Object from the DNP3 Subsystem in the controller,
configure Data Set Prototypes/Descriptors Object in the DNP3 Data-set
Descriptor/Prototype under DNP3 Slave.
Each Data Set Prototypes Object can have up to 10 elements of Data Set
Prototypes, and each Data Set Descriptors Object can have up to 10 elements of
Data-set Descriptors.
As an example, with Data Set Prototypes entry, you can create any number of
Data Set Prototype Object in the DNP3 Data Set Prototype configuration
screen, up to a maximum of 10 entries.

As an example, with Data Set Descriptors entry, you can create any number of
Data Set Descriptor Object in the DNP3 Data Set Descriptor configuration
screen, up to a maximum of 10 entries
Once the Data Set Prototypes and Descriptors are configured in the DNP3
Slave setting page of Connected Components Workbench software version
20.01.00 or later, you can see the DNP3 Descriptor DSX and Prototype PTYPX
under the respective DNP3 Data Set branch, where X is the element numbers
of each Prototype or Descriptor.

For DNP3 PTYPX, you can configure the controller to construct the Data Set
Prototype objects.
For DNP3 DSX, you can configure the controller to construct the Data Set
Descriptor objects.

Data Set Prototypes Configuration Parameters
These parameters are used to construct Data Set Prototypes object.
You can add or delete the index in each PTYPx entry.
Descriptor Code: UUID for index 2. NSPC/NAME/DAEL for index 3 or higher.
Data Type Code: NONE for index 2. VSTR/UINT/INT/FLT/OSTR/BSTR/TIME

for index 3 or higher.
Max Data Length (bytes): 0 for element 1. 0…255 for index 3 or higher.
Ancillary Value: Binary Array in hexadecimal for element 1. ASCII strings for
index 3 or higher. Maximum 32 bytes.

Data-Set Descriptors Configuration Parameters
These parameters are used to construct Data-Set Descriptors objects.
The Read and Enable Event allows assignment of characteristics to the

Descriptor.
• Read – set if Data-Set is readable.
• Enable Event – set if outstation generates a Data-Set event.
Event Class – With the Enable Event checked, the event class is displayed to
allow assignment of Event Class to this Descriptor.
• 1 – Class 1
• 2 – Class 2
• 3 – Class 3
Trigger Event: Define and set this parameter to generate an event by the ladder
logic to generate timed events. Once this parameter is set by the ladder logic or
communications, the controller clears it automatically after generating an
event at the end of scan.
Disable Change Event: Define and set this parameter to suppress the events
generated by any Event Occurrence Condition.
Event Occurrence Condition: The conditions of Data-Set Event for each Data-
Set Descriptor can be configured by Data-Set Event Occurrence Condition 1/2/
3/4 in the DNP3 Data-Set Descriptors Object. When one of the values that are
pointing to the Event Occurrence Condition 1/2/3/4 are changed or the criteria
are met, the controller generates a Data-Set Event, retrievable using the object
Group 88, Variation 1.
The following table shows the supported conditions for Point Addressing
under Event Occurrence Conditions.

Point Address Type Point Type Point Index Event Occurrence Condition
Empty NONE: No point type is associated. 0 No Event is generated.
BI: Binary input 0…4095
B2I: Double-bit input 0…2047 When the Point Type and Point
Index are pointing a specific point,
Standard DNP3 Point CI: Counter 0…511 if the value of the point is
AI: Analog input 0…767 changed, an event is generated.
BCD: BCD point 0…255
Event is generated based on the
Variable Select the tag from the controller. 0 condition of the variable tag
selected.
Note that a Data-set event can consume any number of event buffers,
depending on the Data-set configuration. This is only applicable for Data-set
events. The event for other objects consumes a single event buffer. When using
Data-set events, increase the number of events in the DNP3 Slave
configuration.
Descriptor Element Configuration: Each Descriptors element is configured by

clicking on the individual DSX under the DNP3 Data-set Descriptor. Add new
index by clicking Add in each DSX.
Descriptor Code: NAME, DAEL, PTYP
Data Type Code: VSTR, UINT, INT, FLT, OSTR, BSTR, TIME
Max Data Length (bytes): 0…255
Ancillary Value: Any string. This can be a binary array or ASCII string, up to
32 bytes.
Point Addressing under Descriptor Element Configuration: Data-Set value for

each Data-Set element is configured by:
• Point Address Type
• Point Index

When these values are configured properly according to the supported data
files, the controller responds with a Group 87, Variation 1 object filled with the
value in the data file. Table 9 on page 113 shows the supported data files for the
Point Addressing.
Table 9 - Point Address Type — Standard DNP3 Point
Point Address Data Type Maximum

Data Length Point Type Point Index Low Byte Point Index High Byte
Type Code (bytes)
NONE = 0:
NONE = 0 0 No point type is 0
associated.
0…4095 max
BI = 1: When the Data Types other than OSTR and BSTR
Binary input are used, the Point Index must be set to a point
offset that is divisible by 16.
NONE = 0 0 0…2047 max
Standard B2I = 3: When the Data Types other than OSTR and BSTR
DNP3 Point UINT = 2 0, 1, 2, or 4
INT = 3 0, 1, 2, or 4 Double-bit input are used, the Point Index must be set to a point
OSTR = 5 0…255 offset that is divisible by 8.
BSTR = 6 0…255 CI = 20: 0…511 max
TIME = 7 0…6 Counter
AI = 30: 0…767 max
Analog input
BCD = 101: 0…255 max
BCD point
When the Descriptor Code is selected as PTYP, the Point Addressing

parameters for the Descriptor element are replaced by 10 Point Addressing
parameters. These should be configured in the same order of the DAEL
elements in the relevant Prototypes.
For instance, if Prototype 0 includes a Namespace at Index 3 and Name at

Index 4, then the first DAEL in the Prototype 0 is at Index 5.

Object Quality Flags
The object flag is composed of an 8 bit string for some DNP3 objects. The tables
below show Flag Descriptions for each object. The ONLINE, RESTART,
COMM_LOST, REMOTE_FORCED and LOCAL_FORCED flags are common to
all object group types that contain flags.
There are some rules for the Object flag set or clear for each bit by the
controller. The rules below are also applied to Event data.
• When the controller is in Non-executing mode, the object flag is always
all 0.
• When the controller is in Executing mode and there is no configuration
file, only the Online flag in the object flag is set.
• When the controller is in Executing mode and there is a configuration
file, the flags in the object flag are set according to the upper byte of the
configuration files.
Object Flags for Binary Input
Bit Offset Name Description
0 when the controller is or was in Non-executing mode.
1 when the controller is or was in Executing mode and the configuration file
0 ONLINE does not exist.
May be 1 when the controller is or was in Executing mode and the
configuration file exists.
1 RESTART Always 0. Not used.
2 COMM_LOST Always 0. Not used.
3 REMOTE_FORCED Always 0. Not used.
4 LOCAL_FORCED Always 0. Not used.
5 CHATTER_FILTER Always 0. Not used.
6 Reserved Always 0. Not used.
7 STATE Reflects point state of Binary Input point.
Object Flags for Double Binary Input

May be 1 when the controller is or was in Executing mode and the
configuration file exists.

Object Flags for Double Binary Input (Continued)

5 CHATTER_FILTER Always 0. Not used.
6 STATE Reflects point state of Double-bit Binary Input point. Double-bit LSB.
7 STATE Reflects point state of Double-bit Binary Input point. Double-bit MSB
Object Flags for Binary Output

May be 1 when the controller is in Executing mode and the configuration file
exists.
7 STATE Reflects point state of Binary Output point.
Object Flags for Counter

exists.
1 RESTART
2 COMM_LOST
3 REMOTE_FORCED 0 when the controller is or was in Executing mode and the configuration file
4 LOCAL_FORCED does not exist.
5 ROLLOVER May be 1 when the controller is in Executing mode and the configuration file
exists.
6 DISCONTINUITY
7 Reserved
Object Flags for Analog Input

exists.
1 RESTART
2 COMM_LOST
5 OVER_RANGE May be 1 when the controller is in Executing mode and the configuration file
exists.
6 REFERENCE_ERR
7 Reserved

Object Flags for Analog Output

exists.
1 RESTART
2 COMM_LOST
5 Reserved May be 1 when the controller is in Executing mode and the configuration file
exists.
6 Reserved
7 Reserved
DNP3 Device Attribute The Device Attribute object can be used to identify DNP3 Slave devices.
Object With the controller, some of the variations are written so that you can read or
write your own strings in your application.
The R/W property shows if the object is Read Only, Read, or Write. If the R/W
property is writable, the value which was written by DNP3 master device is
stored to non-volatile memory.
The object group of the Device Attribute is 0. The supported range of the
variation is 209…255.
Object Group 0, Variations for Attribute Set 0
Variation Read/Write Attribute Max Length in Bytes Description Value

Data Type
Secure authentication version supported in out
209 Read Only UINT 1 5
station
210 Read Only UINT 1 Number of secure statistic available in out station 18
212 Read Only UINT 1 Number of master-defined Data-Set prototypes 1
213 Read Only UINT 1 Number of outstation-defined Data-Set prototypes 1
214 Read Only UINT 1 Number of master-defined Data-Sets 1
215 Read Only UINT 1 Number of outstation-defined Data-Sets 1
216 Read Only UINT 1 Max number of binary outputs per request 1
217 Read Only UINT 4 Local timing accuracy 100 in microseconds
218 Read Only UINT 4 Duration of timing accuracy 100 in seconds
219 Read Only INT 1 Support for analog output events 1
220 Read Only UINT 4 Max analog output index 0
221 Read Only UINT 4 Number of analog outputs 0
222 Read Only INT 1 Support for binary output events 1
223 Read Only UINT 4 Max binary output index 0
224 Read Only UINT 4 Number of binary outputs 0
225 Read Only INT 1 Support for frozen counter events 1
226 Read Only INT 1 Support for frozen counters 1
227 Read Only INT 1 Support for counter events 1
228 Read Only UINT 4 Max counter index 0
229 Read Only UINT 4 Number of counter points 0
230 Read Only INT 1 Support for frozen analog inputs 1
231 Read Only INT 1 Support for analog input events 1
232 Read Only UINT 4 Maximum analog input index 0

Object Group 0, Variations for Attribute Set 0 (Continued)
Variation Read/Write Attribute Max Length in Bytes Description Value

Data Type
233 Read Only UINT 4 Number of analog input points 0
234 Read Only INT 1 Support for double-bit binary input events 1
235 Read Only UINT 4 Maximum double-bit binary input index 0
236 Read Only UINT 4 Number of double-bit binary input points 0
237 Read Only INT 1 Support for binary input events 1
238 Read Only UINT 4 Max binary input index 0
239 Read Only UINT 4 Number of binary input points 0
240 Read Only UINT 4 Max transmit fragment size Response size
241 Read Only UINT 4 Max receive fragment size Response size
This variation returns firmware FRN. FRN 1.00.
Supported ranges: FRN x.yy, FRN x.yyy, FRN xx.yy, or
242 Read Only VSTR 5 Device manufacturer's software version FRN xx.yyy where x, xx is 0 ~ 99 and yy, yyy 00 ~ 999.
For example, FRN 1.00, FRN 1.05, FRN 12.05, FRN 102.27
or FRN 103.117.
Supported ranges: HW SER x/REV yy where x is A ~ F
and yy is 00 ~ 31.
243 Read Only VSTR 6 Device manufacturer's hardware version For example, HW SER A/REV 01, HW SER B/REV 03, or
HW SER C/REV 31.
244 — — — Reserved for future assignment —
length of the string
245 Read /Write VSTR User-assigned location name Default
value, max 255 bytes
length of the string
246 Read /Write VSTR User-assigned ID code/number Default
value, max 255 bytes
This variation returns Subset level and Test procedure
249 Read Only VSTR 6 DNP subset and conformance version. 3:2004.
Supported ranges:
length of the string 2080-L70E-24xxxN SER A where xxx is QWB or QBB.
250 Read Only VSTR Device manufacturer's product name and model
value For example, 2080-L70E-QWBN SER A or 2080-L70E-
24QBBN SER A.
This variation returns the Company name, Rockwell
252 Read Only VSTR 19 Device manufacturer's name Automation.
253 Read Only — — Reserved for future assignment —
This variable returns all of the variations in this group
254 Read Only — — Non-specific all attributes request except this variation.
This variation returns the R/W property for each
variation.
255 Read Only — — List of attribute variations 0 for Read Only
1 for Read or Write
Event Reporting This section covers how to generate DNP3 events from DNP3 Data Objects and
how to report the generated events by polled response or unsolicited response.
Generate Events
The controller has a separate buffer area that you can use to log DNP3 events
internally.
The maximum number of the Events that can be logged is 10000 (see DNP3
10K Event Logging on page 119), regardless of the Event data type. In

2080-L70E-24QxBN controllers, a Data-Set event can consume multiple

numbers of the event buffers.
If the number of the generated events reaches this value, the controller sets
IIN2.3 [EVENT_BUFFER_OVERFLOW]. Further events are not logged until
the logged events are reported to DNP3 Master and the buffer is available.
The logged events are not removed until they are reported to DNP3 Master
successfully. Logged event can also be cleared when one of the following events
occur:
• New OS firmware upgrade
• New user program download.
Figure 6 shows how to generate events for a Binary Input Object and a 16-bit
Analog Input Object. In the DNP3 Slave configuration, Binary Input Object
Data and 16-bit Analog Input Object Data is configured in the DNP3 mapping
table.
Figure 6 - Generate Events for Binary Input Object
Click Add to select, or create a binary variable from the variable selector screen
for the Binary Input Object.
There are two methods to create Binary Input Object. You can create the object
as a BOOL data type or as an UINT data type. The UINT data type represents
similar to a BOOL array of 16 bits and this representation is similar to the
BOOL array used in MicroLogix™ 1400 controllers.

The setting in the image above shows that the different class events can be
triggered when the BOOL variable is triggered. When using the UINT variable,
any of the bits in the UINT will trigger the respective class event.
In the same manner, create this 16-bit Analog Input Object in the Analog Input
tab and define Index 0 as Class 1, Index 1 as Class 2, and Index 2 as Class 3.
DNP3 10K Event Logging
Up to 10,000 events can be logged. To configure the number of events, change

the Unsolicited Responses for the Class 1/2/3 to Enabled and define 10,000 into
the Number of Events field. Download the project into the controller for the
setting to take effect.

When there is a change in the configuration for the number of events, you
must download the project into the controller for the setting to take effect.
Control Generating Event
The controller checks all elements in the Object Data for changes at the end of a
scan and generates events where needed.
The key method to turn on and off event generating by ladder logic is to assign
the variable to be used for controlling into the Trigger Event and Disable
Change Events field.
The following example shows how to control the event generation condition by
using the Deadband for Analog Input Objects.
In this example, for 16-bit Analog Input point 0, if the absolute value of the
difference between the present value of variable AnalogValue1 and the value
that was most recently queued as an event for that point exceeds the deadband
value in variable AnalogV1Deadband, then an event is generated for that point.

Report Event By Polled Response
When a DNP3 Master sends a poll to read Class events, any events logged to the
event buffer are reported in the polled response.
Define the Number of Events for the respective Class event in the DNP3 Slave
configuration page as shown in the following example.
Report Event By Unsolicited Response
To initiate and send Unsolicited Responses to a DNP3 Master, the parameters

below should be configured correctly. For more details, see DNP3 Slave
Application Layer Configuration Parameters on page 86.
• Master Node 0
• Channel for Unsolicited Response
• Enable Unsolicited On Start Up
• Enable Unsolicited For Class1
• Send Initial Unsolicited On Start Up
• Number of Class1 Events
• Hold Time after Class1 Events (x1s)
• DNP3 Object Data
• DNP3 Object Config
• Content of the Config File

In some cases, the controller may not send an Unsolicited Response even
though the parameters are configured properly.
• Normally, when the parameter Enable Unsolicited On Start Up is
checked, the controller initiates an Unsolicited Response with the
function code ENABLE_UNSOLICITED(20), if there are any events
logged into the event buffer. However, when a request with the function
code DISABLE_UNSOLICITED(21) is received, an Unsolicited Response
will not be sent.
• When the parameter Enable Unsolicited On Start Up is unchecked, the
controller does not trigger the Unsolicited Response until a request with
the function code ENABLE_UNSOLICITED(20) from the DNP3 Master is
received.
Figure 7 shows how to initiate and send the Unsolicited Response. Master
Node 0 in the DNP3 Slave configuration page indicates that the Unsolicited
Response is reported to the Master with the node address 3.
Figure 7 - Initiate and Send Unsolicited Response
The parameter for Unsolicited Response in the DNP3 Slave configuration

indicates that the Unsolicited Response is reported for all the communication
ports (Serial and Ethernet) that are defined. In this example, Initial
Unsolicited Response is sent on startup and all events of class 1, 2 and 3 are
reported. Since Hold Times are configured to 5 seconds, generated events are
reported after 5 seconds.
Collision Avoidance The controller currently supports the first of the two methods listed below for
collision avoidance.
• Detecting transmitted data (TX/RX line on RS-485 communication).
• Detecting out-of-band carrier (DCD on RS-232C communication).
When the controller is connected to RS-485 network, it monitors all data on the
link. If the controller is preparing to transmit a packet and finds the link busy,
it waits for an interval defined by the Backoff_Time until it is no longer busy.
Backoff_Time = Pre Transmit Delay (x1 ms) + Max Random Delay (x1 ms)

The Pre Transmit Delay (x1 ms) in the Link Layer Channel Configuration file is
a fixed delay and the Max Random Delay (x1 ms) in the Channel Configuration
file is a maximum random delay for Channel 0 and Channel 2. You must
specify those parameters to get the collision avoidance mechanism.
After the Backoff_Time, the controller tries again, either indefinitely, or up to a

configurable maximum number of retries. If a maximum is used, the protocol
considers this as a link failure.
Time Synchronization The time value in the real time clock (RTC) of the controller (firmware real time
clock) or plug-in module (2080-MEMBAK-RTC2 or 2080-SDMEMRTC-SC) is
updated every 1 second.
The DNP3 subsystem and the RTC (firmware or plug-in module) are
synchronized by the following conditions:
• power up
• a request for time synchronization from DNP3 Master.
At power up, the DNP3 subsystem gets the time from the controller. For the
controller to acquire the correct time, a plug-in module RTC should be used
and enabled before a power cycle to acquire the correct time from the
controller. The firmware RTC always reverts to a default time and date after a
power cycle, so it is not able to provide an accurate time to the DNP3
subsystem.
If a plug-in module RTC is not used, then the firmware RTC must be enabled.
To enable firmware RTC, select Enable firmware real time clock.
When there is a write request for time synchronization from a DNP3 Master,
the time in the RTC (firmware or plug-in module) is synchronized with the
time from the DNP3 Master.
This table shows the 2080-MEMBAK-RTC2 plug-in module Accuracy.

Configure the Time Synchronization Interval in the Micro870 DNP3 Slave
configuration according to this table, so that a DNP3 Master can send the time
synchronization request periodically for more accurate times in the controller.
2080-MEMBAK-RTC2 Accuracy
RTC Accuracy(1) Ambient Temperature
±5 sec/month 25 °C (77 °F)
±9 sec/month -20…+65 °C (-4…+149 °F)
(1) These numbers are maximum worst case values over a 31-day month.

Diagnostics Errors in a DNP3 Slave subsystem are logged in the Communication

Diagnostics page in Connected Components Workbench software.
Figure 8 - Communication Diagnostics for Embedded Serial Port
Figure 9 - Communication Diagnostics for 2080-SERIALISOL Plug-in Module

Diagnostics for Ethernet Channel
Diagnostic Counters and Errors in DNP3 Slave subsystem for the Ethernet
channel are shown in Connected Components Workbench software. Click
Diagnose to display the Diagnostic page.
Figure 10 - Communication Diagnostics for Ethernet Port
Table 10 - Error Codes

Value (DEC) Mnemonic Description
0 ERROR_PHYS_TRANSMIT Error returned from target transmit routine
1 ERROR_PHYS_CHAR_TIMEOUT Intercharacter timeout occurred
2 ERROR_PHYS_REMOTE_CLOSE Remote side of channel closed connection
3 ERROR_LINK_FRAME_LENGTH Incoming frame too short or exceeded buffer size
4 ERROR_LINK_ADDRESS_UNKNOWN Received frame was for an unknown link address
5 ERROR_LINK_ILLEGAL_FUNCTION Illegal link function code in received frame
6 ERROR_LINK_INVALID_CHECKSUM Invalid checksum or CRC
7 ERROR_LINK_NOT_RESET Link has not been reset, frame rejected
8 ERROR_LINK_FCB Received invalid frame count bit
9 ERROR_LINK_INVALID_START_CHAR Did not receive correct starting sync char
10 ERROR_LINK_FRAME_TIMEOUT Entire frame was not received in specified time
11 ERROR_LINK_CNFM_TIMEOUT Link Confirm was not received in specified tim
12 ERROR_LINK_STATUS_TIMEOUT Link status response not received in specified time
The following link errors are used by 101/103
13 ERROR_LINK_WRONG_SESN Response was not from expected session
14 ERROR_LINK_WRONG_REPLY Received unexpected reply, frame rejected
15 ERROR_LINK_INVALID_2ND_CHAR Did not receive correct second sync char
16 ERROR_LINK_INVALID_END_CHAR Did not receive correct ending sync character
17 ERROR_LINK_MISMATCHING_LENGTH Variable length bytes in FT1.2 frame did not match
18 ERROR_LINK_INV_DIR Received invalid dir bit in control octet
The following link errors are used by 104
19 ERROR_LINK_NO_CNFM_RECEIVED Confirm of 104 U-format APDU not received
20 ERROR_LINK_NO_ACK_RECEIVED Acknowledge of 104 I-format APDU not received

Table 10 - Error Codes (Continued)

Value (DEC) Mnemonic Description
21 ERROR_LINK_SEQUENCE_UNKNOWN Unknown confirming sequence number in received APDU
22 ERROR_LINK_OUT_OF_SEQUENCE Received APDU not in sequence with previous APDU
Transport layer errors
23 ERROR_TPRT_SEQUENCE_ERROR Sequence number error
Diagnostics for Secure Authentication

Diagnostic information for Secure Authentication is shown in Connected
Components Workbench software. Click Diagnose to display the Diagnostic
page.
Function Codes These tables show the Application Layer Function codes implemented in the
controller.
Table 11 - Function Codes for DNP3 in Micro870 Controllers
Message Type Function Code Name Micro870 Support Description
Confirmation 0 (0x00) CONFIRM Yes Controller parses/sends
Request 1 (0x01) READ Yes Controller parses
Request 2 (0x02) WRITE Yes Controller parses
Request 3 (0x03) SELECT Yes Controller parses
Request 4 (0x04) OPERATE Yes Controller parses
Request 5 (0x05) DIRECT_OPERATE Yes Controller parses
Request 6 (0x06) DIRECT_OPERATE_NR Yes Controller parses
Request 7 (0x07) IMMED_FREEZE Yes Controller parses
Request 8 (0x08) IMMED_FREEZE_NR Yes Controller parses
Request 9 (0x09) FREEZE_CLEAR Yes Controller parses
Request 10 (0x0A) FREEZE_CLEAR_NR Yes Controller parses
Request 11 (0x0B) FREEZE_AT_TIME No

Table 11 - Function Codes for DNP3 in Micro870 Controllers (Continued)

Message Type Function Code Name Micro870 Support Description
Request 12 (0x0C) FREEZE_AT_TIME_NR No
Controller parses. Controller should not be in the executing mode
Request 13 (0x0D) COLD_RESTART Yes and any program and files should not be in open state.
Request 14 (0x0E) WARM_RESTART No Controller parses
Request 15 (0x0F) INITIALIZE_DATA No Obsolete
Controller parses. Clears fault and changes the controller mode to
Request 16 (0x10) INITIALIZE_APPL Yes
Remote Program.
Controller parses. Clears fault and changes the controller mode to
Request 17 (0x11) START_APPL Yes Remote Run.
Controller parses. Changes the controller mode to Remote
Request 18 (0x12) STOP_APPL Yes Program.
Request 19 (0x13) SAVE_CONFIG No Deprecated
Request 20 (0x14) ENABLE_UNSOLICITED Yes Controller parses
Request 21 (0x15) DISABLE_UNSOLICITED Yes Controller parses
Request 22 (0x16) ASSIGN_CLASS No
Request 23 (0x17) DELAY_MEASURE Yes Controller parses. Used for non-LAN
Request 24 (0x18) RECORD_CURRENT_TIME No Controller parses. Used for LAN
Request 25 (0x19) OPEN_FILE Yes Controller parses
Request 26 (0x1A) CLOSE_FILE Yes Controller parses
Request 27 (0x1B) DELETE_FILE Yes Controller parses
Request 28 (0x1C) GET_FILE_INFO No Controller parses
Request 29 (0x1D) AUTHENTICATE_FILE Yes Controller parses
Request 30 (0x1E) ABORT_FILE No Controller parses
Request 31 (0x1F) ACTIVATE_CONFIG No Controller parses
Request 32 (0x20) AUTHENTICATE_REQ No Controller parses
Request 33 (0x21) AUTHENTICATE_ERR No Controller parses
Response 34 (0x22) RESPONSE Yes Controller sends
Response 35 (0x23) UNSOLICITED_RESPONSE Yes Controller sends
Response 36 (0x24) AUTHENTICATE_RESPONSE No Controller sends
37 (0x25)…47 (0x2F) No Reserved
Implementation Table Micro870 (2080-L70E-24QxBN) controllers supports DNP3 Certification

Subset Level 2.
Table 12 identifies which object groups and variations, function codes and
qualifiers the device supports in both requests and responses. The Request and
Response columns identify all requests and responses that may be sent/parsed
by a DNP3 Master, or must be parsed/sent by the controller.
The implementation table lists all functionality required by either DNP3

Master or controller as defined within the DNP3 IED Conformance Test
Procedures. Any functionality beyond the highest subset level supported is
indicated by grayed table cells.

Table 12 - Implementation Table for Micro870 controllers

Request Response
DNP Object Group & Variation DNP3 Master may issue DNP3 Master must parse
Controller must parse Controller may issue
Group Num Var Num Description Function Codes (dec) Qualifier Codes (hex) Function Codes (dec) Qualifier Codes (hex)
211…239
241…243 Device Attribute 00, 01 (start-stop)
0 1 (read) 129 (response) 00 (start-stop)
248…250 06 (no range, or all)
252
00, 01 (start-stop)
240 1 (read) 129 (response) 00 (start-stop)
0 Device Attribute 06 (no range, or all)
245…247
2 (write) 00, 01 (start-stop)
Device Attribute – Non-specific all 00, 01 (start-stop)
0 254 1 (read)
attributes request 06 (no range, or all)
Device Attributes – List of attribute 00, 01 (start-stop)
0 255 1 (read) 129 (response) 00 (start-stop)
variations 06 (no range, or all)
00, 01 (start-stop)
1 0 Binary Input – Any Variation 1 (read)
06 (no range, or all)
00, 01 (start-stop)
1 1 Binary Input – Packed format 1 (read) 06 (no range, or all) 129 (response) 00, 01 (start-stop)
1 2 Binary Input – With flags 00, 01 (start-stop)

1 (read) 129 (response) 00, 01 (start-stop)
2 0 Binary Input Event – Any Variation 1 (read) 07, 08 (limited qty)
06 (no range, or all) 129 (response)
2 1 Binary Input Event – Without time 1 (read) 17, 28 (index)
07, 08 (limited qty) 130 (unsol. resp)
Binary Input Event – With absolute 06 (no range, or all) 129 (response)
2 2 1 (read) 17, 28 (index)
time 07, 08 (limited qty) 130 (unsol. resp)
2 3 Binary Input Event – With relative time 1 (read) 17, 28 (index)
00, 01 (start-stop)
3 0 Double-bit Binary Input – Any Variation 1 (read) 06 (no range, or all)
Double-bit Binary Input – Packed 00, 01 (start-stop)
3 1 1 (read) 129 (response) 00, 01 (start-stop)
format 06 (no range, or all)
00, 01 (start-stop)
3 2 Double-bit Binary Input – With flags 1 (read) 06 (no range, or all) 129 (response) 00, 01 (start-stop)
Double-bit Binary Input Event – Any 06 (no range, or all)
4 0 1 (read)
Variation 07, 08 (limited qty)
Double-bit Binary Input Event – 06 (no range, or all) 129 (response)
4 1 1 (read) 17, 28 (index)
Without time 07, 08 (limited qty) 130 (unsol. resp)
Double-bit Binary Input Event – With 06 (no range, or all) 129 (response)
4 2 1 (read) 17, 28 (index)
absolute time 07, 08 (limited qty) 130 (unsol. resp)
Double-bit Binary Input Event – With 06 (no range, or all) 129 (response)
4 3 1 (read) 17, 28 (index)
relative time 07, 08 (limited qty) 130 (unsol. resp)
00, 01 (start-stop)
10 0 Binary Output – Any Variation 1 (read)
Binary Output – Output status with 00, 01 (start-stop)
flags 06 (no range, or all)
3 (select)
Binary Command – Control relay 4 (operate)
12 1 17, 28 (index) 129 (response) echo of request
output block (CROB) 5 (direct op)
6 (dir. op, no ack)
00, 01 (start-stop)
20 0 Counter – Any Variation 1 (read)
00, 01 (start-stop)
20 1 Counter – 32-bit with flag 1 (read) 06 (no range, or all) 129 (response) 00, 01 (start-stop)
7 (freeze)
8 (freeze noack)
20 1 Counter – 32-bit with flag 06 (no range, or all)
9 (freeze clear)
10 (frz. cl. noack)
00, 01 (start-stop)
20 2 Counter – 16-bit with flag 1 (read) 06 (no range, or all) 129 (response) 00, 01 (start-stop)

Table 12 - Implementation Table for Micro870 controllers (Continued)

Request Response
7 (freeze)
8 (freeze noack)
20 2 Counter – 16-bit with flag 06 (no range, or all)
9 (freeze clear)
10 (frz. cl. noack)
00, 01 (start-stop)
20 5 Counter – 32-bit without flag 1 (read) 06 (no range, or all) 129 (response) 00, 01 (start-stop)
7 (freeze)
8 (freeze noack)
20 5 Counter – 32-bit without flag 9 (freeze clear) 06 (no range, or all)
10 (frz. cl. noack)
00, 01 (start-stop)
20 6 Counter – 16-bit without flag 1 (read) 06 (no range, or all) 129 (response) 00, 01 (start-stop)
7 (freeze)
8 (freeze noack)
20 6 Counter – 16-bit without flag 06 (no range, or all)
9 (freeze clear)
10 (frz. cl. noack)
00, 01 (start-stop)
21 0 Frozen Counter – Any Variation 1 (read)
21 1 Frozen Counter – 32-bit with flag 1 (read) 06 (no range, or all) 129 (response) 00, 01 (start-stop)
00, 01 (start-stop)
21 2 Frozen Counter – 16-bit with flag 1 (read) 06 (no range, or all) 129 (response) 00, 01 (start-stop)
Frozen Counter – 32-bit with flag and 00, 01 (start-stop)
time 06 (no range, or all)
Frozen Counter – 16-bit with flag and 00, 01 (start-stop)
time 06 (no range, or all)
00, 01 (start-stop)
21 9 Frozen Counter – 32-bit without flag 1 (read) 06 (no range, or all) 129 (response) 00, 01 (start-stop)
00, 01 (start-stop)
21 10 Frozen Counter – 16-bit without flag 1 (read) 06 (no range, or all) 129 (response) 00, 01 (start-stop)
22 0 Counter Event – Any Variation 1 (read) 07, 08 (limited qty)
22 1 Counter Event – 32-bit with flag 1 (read) 07, 08 (limited qty) 130 (unsol. resp) 17, 28 (index)
22 2 Counter Event – 16-bit with flag 1 (read) 07, 08 (limited qty) 130 (unsol. resp) 17, 28 (index)
Counter Event – 32-bit with flag and 06 (no range, or all) 129 (response)
22 5 1 (read) 17, 28 (index)
Counter Event – 16-bit with flag and 06 (no range, or all) 129 (response)
22 6 1 (read) 17, 28 (index)
23 0 Frozen Counter Event – Any Variation 1 (read) 07, 08 (limited qty)
23 1 Frozen Counter Event – 32-bit with flag 1 (read) 17, 28 (index)
23 2 Frozen Counter Event – 16-bit with flag 1 (read) 07, 08 (limited qty) 130 (unsol. resp) 17, 28 (index)
Frozen Counter Event – 32-bit with flag 06 (no range, or all) 129 (response)
23 5 1 (read) 17, 28 (index)
and time 07, 08 (limited qty) 130 (unsol. resp)
Frozen Counter Event – 16-bit with flag 06 (no range, or all) 129 (response)
23 6 1 (read) 17, 28 (index)
and time 07, 08 (limited qty) 130 (unsol. resp)
00, 01 (start-stop)
30 0 Analog Input – Any Variation 1 (read)
00, 01 (start-stop)
30 1 Analog Input – 32-bit with flag 1 (read) 06 (no range, or all) 129 (response) 00, 01 (start-stop)
00, 01 (start-stop)
30 2 Analog Input – 16-bit with flag 1 (read) 129 (response) 00, 01 (start-stop)
00, 01 (start-stop)
30 3 Analog Input – 32-bit without flag 1 (read) 06 (no range, or all) 129 (response) 00, 01 (start-stop)


Request Response
00, 01 (start-stop)
30 4 Analog Input – 16-bit without flag 1 (read) 129 (response) 00, 01 (start-stop)
Analog Input – Single-prec flt-pt with 00, 01 (start-stop)
flag 06 (no range, or all)
32 0 Analog Input Event – Any Variation 1 (read) 07, 08 (limited qty)
Analog Input Event – 32-bit without 06 (no range, or all) 129 (response)
32 1 1 (read) 17, 28 (index)
Analog Input Event – 16-bit without 06 (no range, or all) 129 (response)
32 2 1 (read) 17, 28 (index)
32 3 Analog Input Event – 32-bit with time 1 (read) 07, 08 (limited qty) 130 (unsol. resp) 17, 28 (index)
32 4 Analog Input Event – 16-bit with time 1 (read) 07, 08 (limited qty) 130 (unsol. resp) 17, 28 (index)
Analog Input Event – Single-prec flt-pt 06 (no range, or all) 129 (response)
32 5 1 (read) 17, 28 (index)
without time 07, 08 (limited qty) 130 (unsol. resp)
Analog Input Event – Single-prec flt-pt 06 (no range, or all) 129 (response)
32 7 1 (read) 17, 28 (index)
with time 07, 08 (limited qty) 130 (unsol. resp)
00, 01 (start-stop)
40 0 Analog Output Status – Any Variation 1 (read)
00, 01 (start-stop)
40 1 Analog Output Status – 32-bit with flag 1 (read) 06 (no range, or all) 129 (response) 00, 01 (start-stop)
00, 01 (start-stop)
40 2 Analog Output Status – 16-bit with flag 1 (read) 06 (no range, or all) 129 (response) 00, 01 (start-stop)
Analog Output Status – Single-prec flt- 00, 01 (start-stop)
pt with flag 06 (no range, or all)
3 (select)
4 (operate)
41 1 Analog Output – 32-bit 5 (direct op) 17, 27, 28 (index) 129 (response) echo of request
6 (dir. op, no ack)
3 (select)
4 (operate)
41 2 Analog Output – 16-bit 17, 27, 28 (index) 129 (response) echo of request
5 (direct op)
6 (dir. op, no ack)
3 (select)
4 (operate)
41 3 Analog Output – Single-prec flt-pt 5 (direct op)
17, 27, 28 (index) 129 (response) echo of request
6 (dir. op, no ack)
07 (limited qty)
1 (read) 07 (limited qty = 1) 129 (response)
50 1 Time and Date – Absolute time (qty = 1)
2 (write) 07 (limited qty = 1)
Time and Date – Absolute time at last 2 (write)
50 3 07 (limited qty = 1)
recorded time
Time and Date CTO – Absolute time, 129 (response) 07 (limited qty)
51 1 synchronized 130 (unsol. resp) (qty = 1)
Time and Date CTO – Absolute time, 129 (response) 07 (limited qty)
51 2 unsynchronized 130 (unsol. resp) (qty = 1)
07 (limited qty)
52 2 Time Delay – Fine 129 (response) (qty = 1)
60 1 Class Objects – Class 0 data 1 (read) 06 (no range, or all)
1 (read) 07, 08 (limited qty)
60 2 Class Objects – Class 1 data
20 (enbl. unsol.) 06 (no range, or all)
21 (dab. unsol.)
60 3 Class Objects – Class 2 data 1 (read) 07, 08 (limited qty)


Request Response
1 (read) 07, 08 (limited qty)
60 4 Class Objects – Class 3 data
20 (enbl. unsol.) 06 (no range, or all)
21 (dab. unsol.)
1 (read) 00, 01 (start-stop) 129 (response) 00, 01 (start-stop)
80 1 Internal Indications – Packed format 00 (start-stop)
2 (write) index=7
85 0 Data-Set Prototype 1 (read) 06 (no range, or all)
00, 01 (start-stop)
85 1 Data-Set Prototype 1 (read) 06 (no range, or all) 129 (response) 5B (free format)
17, 28 (index)
00, 01 (start-stop)
86 1 Data-Set Descriptor – Contents 1 (read) 06 (no range, or all) 129 (response) 5B (free format)
17, 28 (index)
00, 01 (start-stop)
86 2 Data-Set Descriptor – Characteristics 1 (read) 06 (no range, or all) 129 (response) 5B (free format)
17, 28 (index)
00, 01 (start-stop)
87 0 Data-Set – Present Value 1 (read) 06 (no range, or all)
17, 28 (index)
00, 01 (start-stop)
87 1 Data-Set – Present Value 1 (read) 06 (no range, or all) 129 (response) 5B (free format)
17, 28 (index)
88 0 Data-Set Event 1 (read) 07, 08 (limited qty)
88 1 Data-Set Event – Snapshot 1 (read) 07, 08 (limited qty) 130 (unsol. resp) 5B (free format)
16 (init. appl.) 06 (no range, or all)
90 1 Application – Identifier 17 (start appl.) 5B (free format)
18 (stop appl.)
07 (limited qty)
91 1 Status of Requested Operation 129 (response) (qty = 1)
120 1 Authentication – Challenge 32 (Auth Request) 5B (free format) 131 (Auth. resp) 5B (free format)
120 2 Authentication – Reply 32 (Auth Request) 5B (free format) 131 (Auth. resp) 5B (free format)
Authentication – Aggressive Mode
120 3 Any requests 07 (limited qty) 129 (response) 07 (limited qty)
Request
Authentication – Aggressive Mode
120 3 130 (unsol. resp) 07 (limited qty)
Request
Authentication – Session Key Status
120 4 32 (Auth Request) 07 (limited qty)
Request
120 5 Authentication – Session Key Status 131 (Auth. resp) 5B (free format)
120 6 Authentication – Session Key Change 32 (Auth Request) 5B (free format)
120 7 Authentication – Error 33 (Auth Request, no ack) 5B (free format) 131 (Auth. resp) 5B (free format)
120 7 Authentication – Error 1 (read) 06 (no range, or all) 129 (response) 5B (free format)
120 9 Authentication – HMAC Any requests 5B (free format) 129 (response) 5B (free format)
120 9 Authentication – HMAC 130 (unsol. resp) 5B (free format)
No Object (function code only) 13 (cold restart)
No Object (function code only) 14 (warm restart)
No Object (function code only) 23 (delay meas.)
No Object (function code only) 24 (record current time)

Notes:

Chapter 7
Program Execution in Micro800
This section provides a brief overview of running or executing programs with a

Micro800 controller.
IMPORTANT This section generally describes program execution in Micro800 controllers.

Certain elements may not be applicable or true for certain models (for
example, Micro820 does not support PTO motion control).
For detailed information regarding ladder diagrams, instructions, function

blocks, and so on, see Micro800 Programmable Controllers Instruction
Manual, publication 2080-RM001.
Overview of Program A Micro800 cycle or scan consists of reading inputs, executing programs in
Execution sequential order, updating outputs, and performing housekeeping (data log,
recipe, communications).
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 may 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 up the Project Organizer in
Connected Components Workbench, it displays the program icons based on
this order. You can view and modify an order number for a program from the
program’s 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 is exceeded. This 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 just prior to the controller going into Fault mode.

Chapter 7 Program Execution in Micro800
In addition to the User Fault Routine, Micro800 controllers also support two
Selectable Timed Interrupts (STI). STIs execute assigned programs once every
set point interval (1…65535 ms).
The Global System Variables 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(1)/programs
2
3. Write outputs
4. Housekeeping (data log, recipe, communications) 3
(1) Program Organizational Unit.
When a cycle time is specified, a resource waits until this time has elapsed
before starting the execution of a new cycle. The POUs 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.
Optional Module Normally before the read inputs step, the controller will verify the presence of
any configured plug-in and expansion I/O modules. If a plug-in or expansion
I/O module is missing, the controller will fault. In Connected Components
Workbench software release 10 or later, an Optional Module configuration
option is added to prevent a missing plug-in I/O or expansion I/O module
from faulting the controller if enabled. This option can be enabled separately
for each plug-in I/O or expansion I/O module.
ATTENTION: If the optional module feature is enabled, use the MODULE_INFO

instruction to verify that the module is present because the controller will not
fault if the module is missing.

Controller Load and Within one program scan cycle, the execution of the main steps (as indicated
Performance in the Execution Rules diagram) could be interrupted by other controller
activities that have higher priority than the main steps. Such activities include,
Considerations
1. User Interrupt events, including STI, EII, and HSC interrupts (when
applicable);
2. Communication data packet receiving and transmitting;
3. PTO Motion engine periodical execution (if supported by the controller).
When one or several of these activities occupy a significant percentage of the

Micro800 controller execution time, the program scan cycle time will be
prolonged. The Watchdog timeout fault (0xD011) could be reported if the
impact of these activities is underestimated, and the Watchdog timeout is set
marginally. The Watchdog setting defaults to 2 s and generally never needs to
be changed.
Periodic Execution of Programs
For applications where periodic execution of programs with precise timing is

required, such as for PID, it is recommended that STI (Selectable Timed
Interrupt) be used to execute the program. STI provides precise time intervals.
It is not recommended that the system variable __SYSVA_TCYCYCTIME be

used to periodically execute all programs as this also causes all communication
to execute at this rate.
WARNING: Communication timeouts may occur if programmed cycle time is set

too slow (for example, 200 ms) to maintain communications.
System Variable for Programmed Cycle Time

Variable Type Description
Programmed cycle time.
Note: Programmed cycle time only accepts values in multiples
__SYSVA_TCYCYCTIME TIME of 10 ms. If the entered value is not a multiple of 10, it will be
rounded up to the next multiple of 10.
Power Up and First Scan In Program mode, all analog and digital input variables hold their last state,
and the LEDs are always updated. Also all analog and digital output variables
hold their last state, but only the analog outputs hold their last state while the
digital outputs are off.
When transitioning from Program mode to Run mode, all analog output
variables hold their last state but all digital output variables are cleared.
Two system variables are also available from revision 2 and later.

System Variables for Scan and Power-up on Firmware Revision 2 and later
Variable Type Description
First scan bit.
Can be used to initialize or reset variables immediately after
_SYSVA_FIRST_SCAN BOOL every transition from Program to Run mode.
Note: True only on first scan. After that, it is false.
Power-up bit.
Can be used to initialize or reset variables immediately after
download from Connected Components Workbench or
_SYSVA_POWER_UP_BIT BOOL immediately after being loaded from memory backup module
(for example, microSD™ card).
Note: True only on the first scan after a power-up, or running a
new ladder for the first time.
Variable Retention
After a power cycle, all variables inside instances of instructions are cleared.
Micro830 and Micro850 controllers retain all user-created variables. Micro810®
and Micro820 controllers can only retain a maximum of 400 bytes of user-
created variable values. Micro870 controllers can only retain a maximum of 128
kilobytes of user-created variable values.
For example: A user-created variable called My_Timer of Time data type will be
retained after a power cycle but the elapsed time (ET) within a user-created
timer TON instruction will be cleared. This means that after a power cycle,
global variables are cleared or set to initial value, and depending on the
controller, some or all user-created variable values are retained. You can
choose which variables to retain by selecting them on the global variable page.
Memory Allocation Depending on base size, available memory on Micro800 controllers are shown
in the table below.
Memory Allocation for Micro800 Controllers

10/16-point 20-point 24- and 48-points 24-point
Attribute (Micro830) (Micro820) (Mico830, Micro850) (Micro870)
Program steps(1) 4K 10 K 10 K 20 K
Data bytes 8 KB 20 KB 20 KB 40 KB
(1) Estimated Program and Data size are “typical” – program steps and variables are created dynamically.
1 Program Step = 12 data bytes.
These specifications for instruction and data size are typical numbers. When a
project is created for Micro800, memory is dynamically allocated as either
program or data memory at build time. This means that program size can
exceed the published specifications if data size is sacrificed and vice versa. This
flexibility allows maximum usage of execution memory. In addition to the

user-defined variables, data memory also includes any constants and

temporary variables generated by the compiler at build time.
If your project is larger, it affects the power up time. Typical power up time is
10...15 seconds for all controllers. However, if your project has a lot of initial
and project values, it may cause the power up time to exceed 30 seconds. After
boot up, EtherNet/IP connections may take up to 60 seconds to establish.
The Micro800 controllers also have project memory, which stores a copy of the
entire downloaded project (including comments), as well as configuration
memory for storing plug-in setup information, and so on.
Guidelines and Limitations Here are some guidelines and limitations to consider when programming a
for Advanced Users Micro800 controller using Connected Components Workbench software:
• Each program/POU can use up to 64 Kb of internal address space. For all
controllers except Micro870, it is recommended that you split large
programs into smaller programs to improve code readability, simplify
debugging and maintenance tasks.
• A User Defined Function (UDF) uses significantly less memory than a
User Defined Function Block (UDFB). For example, 30% less for a typical
sized program compared to a UDFB with one instance. The savings
increases as the number of UDFB instances increases.
• A User Defined Function Block (UDFB) can be executed within another
UDFB, with a limit of five nested UDFBs. Avoid creating UDFBs with
references to other UDFBs, as executing these UDFBs too many times
may result in a compile error. This also applies to UDFs.
Example of Five Nested UDFBs
UDFB1
UDFB2
UDFB3
UDFB4
UDFB5
• Structured Text (ST) is much more efficient and easier to use than
Ladder Logic, when used for equations. If you are used to using the
RSLogix 500® CPT Compute instruction, a great alternative is to use ST
combined with either UDF or UDFB.
As an example, for an Astronomical Clock Calculation, Structured Text
uses 40% less Instructions.
Display_Output LD:
Memory Usage (Code) : 3148 steps
Memory Usage (Data) : 3456 bytes
Display_Output ST:
Memory Usage (Code) : 1824 steps
Memory Usage (Data) : 3456 bytes
• You may encounter an Insufficient Reserved Memory error while
downloading and compiling a program over a certain size. One
workaround is to use arrays, especially if there are many variables.
Notes:

Chapter 8
Motion Control
Generally two types of motion control are used in Micro800 controller motion
applications that have Kinetix® 3 servo drives.
• Indexed Motion – Micro800 controller issues position indexes to the
servo drive using Modbus RTU communications or discrete I/O. Used for
simple positioning. See publication CC-QS025 for building block
example.
• PTO Motion – Micro800 controller uses pulse and direction outputs to
the servo drive for precise control of position and velocity with Modbus
RTU communications or discrete I/O for feedback. Micro800 motion
configuration and instructions make programming easy. See publication
CC-QS033 for building block example.
PTO Motion Control Certain Micro830, Micro850, and Micro870 controllers, shown in Table 13,
support motion control through high-speed pulse-train outputs (PTO). PTO
functionality refers to the ability of a controller to accurately generate a
specific number of pulses at a specified frequency. These pulses are sent to a
motion device, such as a servo drive, which in turn controls the number of
rotations (position) of a servo motor. Each PTO is exactly mapped to one axis,
to allow for control of simple positioning in stepper motors and servo drives
with pulse/direction input.
As the duty cycle of the PTO can be changed dynamically, the PTO can also be
used as a pulse width modulation (PWM) output.
PTO/PWM and motion axes support on the Micro830, Micro850, and Micro870
controllers are summarized below.
Table 13 - PTO/PWM and Motion Axis Support on Micro830, Micro850,

and Micro870
Controller PTO (built-in) Number of Axes Supported
(1)
10/16 Points
2080-LC30-10QVB 1 1
2080-LC30-16QVB
24 Points
2080-LC30-24QVB (1)
2080-LC30-24QBB (1)
2080-LC50-24QVB
2080-L50E-24QVB
2080-LC50-24QBB 2 2
2080-L50E-24QBB
2080-LC70-24QBB
2080-L70E-24QBB
2080-LC70-24QBBK
2080-L70E-24QBBK
2080-L70E-24QBBN

Chapter 8 Motion Control
Table 13 - PTO/PWM and Motion Axis Support on Micro830, Micro850,

and Micro870 (Continued)
Controller PTO (built-in) Number of Axes Supported
48 Points
2080-LC30-48QVB (1)
2080-LC30-48QBB (1)
2080-LC50-48QVB 3 3
2080-L50E-48QVB
2080-LC50-48QBB
2080-L50E-48QBB
(1) For Micro830 catalogs, Pulse Train Output functionality is only supported from firmware revision 2 and later.
ATTENTION: To use the Micro800 Motion feature effectively, users need to

have a basic understanding of the following:
• PTO components and parameters
See Use the Micro800 Motion Control Feature on page 140 for a general
overview of Motion components and their relationships.
• Programming and working with elements in the Connected Components
Workbench software
The user needs to have a working knowledge of ladder diagram, structured
text, or function block diagram programming to be able to work with motion
function blocks, variables, and axis configuration parameters.
ATTENTION: To learn more about Connected Components Workbench

software and detailed descriptions of the variables for the Motion Function
Blocks, you can refer to Connected Components Workbench software Online
Help that comes with your Connected Components Workbench software
installation.
IMPORTANT The PTO function can only be used with the controller’s embedded I/O. It
cannot be used with expansion I/O modules.
Use the Micro800 Motion Control Feature
The Micro800 motion control feature has the following elements. New users
need to have a basic understanding of the function of each element to
effectively use the feature.
Components of Motion Control

Element Description Page
Consists of one pulse output and one
Pulse Train Outputs direction output. A standard interface to • Input and Output Signals on page 141
control a servo or stepper drive.
From a system point of view, an axis is a
mechanical apparatus that is driven by a
motor and drive combination. The drive • Motion Axis and Parameters on
receives position commands through the page 152
Micro800 pulse train outputs interface based
Axis • Motion Axis Configuration in
on the PLC execution of motion function
blocks. Connected Components Workbench
On the Micro800 controller, it is a pulse train on page 163
output and a set of inputs, outputs, and
configuration.
• Connected Components Workbench
Online Help
• Motion Control Function Blocks on
A set of instructions that configure or act page 144
Motion Function Blocks upon an axis of motion. • Axis_Ref Data Type on page 158
• Function Block and Axis Status Error
Codes on page 160
• Homing Function Block on page 173

Components of Motion Control (Continued)

Rate of change of acceleration. The Jerk
component is mainly of interest at the start • See Acceleration, Deceleration, and
Jerk and end of motion. Too high of a Jerk may Jerk Inputs on page 145.
induce vibrations.
To use the Micro800 motion feature, you need to:

1. Configure the Axis Properties
See Motion Axis Configuration in Connected Components Workbench
on page 163 for instructions.
2. Write your motion program through the Connected Components
Workbench software
For instructions on how to use the Micro800 motion control feature, see
the quickstart instructions, Use the Motion Control Feature on Micro800
Controllers, publication 2080-QS001.
3. Wire the Controller
For fixed and configurable inputs/outputs, see Input and Output Signals
on page 141. See Sample Motion Wiring Configuration on 2080-LC30-
xxQVB / 2080-LC50-xxQVB / 2080-LC70-xxQVB on page 143 for
reference.
The next sections provide a more detailed description of the motion

components. You can also see the Connected Components Workbench Online
Help for more information about each motion function block and their
variable inputs and outputs.
Input and Output Signals Multiple input/output control signals are required for each motion axis, as
described in the next tables. PTO Pulse and PTO Direction are required for an
axis. The rest of the input/outputs can be disabled and reused as regular I/O.
Fixed PTO Input/Output

Motion Signals PTO0 (EM_00) PTO1 (EM_01) PTO2 (EM_02)
Name on
Logical Name in Name on Logical Name in Logical Name in Name on Terminal
Terminal
Software Terminal Block Software Software Block
Block
PTO pulse _IO_EM_DO_00 O-00 _IO_EM_DO_01 O-01 IO_EM_DO_02 O-02
PTO direction _IO_EM_DO_03 O-03 _IO_EM_DO_04 O-04 IO_EM_DO_05 O-05
Lower (Negative) Limit switch _IO_EM_DI_00 I-00 _IO_EM_DI_04 I-04 IO_EM_DI_08 I-08
Upper (Positive) Limit switch _IO_EM_DI_01 I-01 _IO_EM_DI_05 I-05 IO_EM_DI_09 I-09
Absolute Home switch _IO_EM_DI_02 I-02 _IO_EM_DI_06 I-06 IO_EM_DI_10 I-10
Touch Probe Input switch _IO_EM_DI_03 I-03 _IO_EM_DI_07 I-07 IO_EM_DI_11 I-11
Configurable Input/Output
Motion Signals Input/Output Notes
Servo/Drive On OUTPUT Can be configured as any embedded output.
Servo/Drive Ready INPUT Can be configured as any embedded input.
In-Position signal (from INPUT Can be configured as any embedded input.
servo/motor)
Home Marker INPUT Can be configured as any embedded input, from input 0...15.

These I/O can be configured through the axis configuration feature in

Connected Components Workbench. Any outputs assigned for motion should
not be controlled in the user program.
See Motion Axis Configuration in Connected Components Workbench on

page 163.
IMPORTANT If an output is configured for motion, then that output can no longer be
controlled or monitored by the user program and cannot be forced. For
example, when a PTO Pulse output is generating pulses, the
corresponding logical variable IO_EM_DO_xx will not toggle its value and
will not display the pulses in the Variable Monitor but the physical LED
will give an indication.
If an input is configured for motion, then forcing the input only affects
the user program logic and not motion. For example, if the input Drive
Ready is false, then the user cannot force Drive Ready to true by forcing
the corresponding logical variable IO_EM_DI_xx to be true.
Motion Wiring Input/Output Description

Motion Signals Input/Output Description Uniqueness
PTO pulse from the embedded fast output, to be
PTO pulse OUTPUT Not Shared
connected to Drive PTO input.
PTO pulse direction indication, to be connected to
PTO direction OUTPUT Not Shared
Drive Direction input.
The control signal used to activate/deactivate Can be shared
Servo/Drive.
Servo/Drive On OUTPUT with more than
This signal becomes Active when MC_Power (on) is one drive
commanded.
The input for hardware negative limit switch, to be
Lower (Negative) INPUT connected to mechanical/electrical negative limit Not Shared
Limit switch sensor.
The input for hardware positive limit switch, to be
Upper (Positive) INPUT connected to mechanical/electrical positive limit Not Shared
Limit switch sensor.
Absolute Home The input for hardware home switch (sensor), to be
INPUT Not Shared
switch connected to mechanical/electrical home sensor.
The input for hardware touch probe signal, to be
Touch Probe Input used with Motion MC_TouchProbe and
INPUT Not Shared
switch MC_AbortTrigger function blocks to capture axis
commanded position during the motion path.
The input signal that indicates Servo/Drive is ready
to receive PTO pulse and direction signal from
controller. Can be shared
Servo/Drive Ready INPUT No moving function blocks can be issued to an axis with more than
before the axis has this signal ready if this signal is one drive
Enabled in the motion axis configuration or axis
properties page.
The input signal that indicates the moving part is
in the commanded position. This signal has to be
Active after the moving part reaches the
commanded position for MoveAbsolute and
In-Position signal MoveRelative function blocks.
INPUT Not Shared
(from servo/motor) For MoveAbsolute and MoveRelative function
blocks, when In_Position is enabled, the controller
will report an error (EP_MC_MECHAN_ERR) if the
signal is not active within 5 seconds when the last
PTO pulse sent out.
This signal is the zero pulse signal from the motor
Home Marker INPUT encoder. This signal can be used for fine homing Not Shared
sequence to improve the homing accuracy.

Sample Motion Wiring Configuration on 2080-LC30-xxQVB / 2080-LC50-xxQVB / 2080-LC70-xxQVB
24V 24V
Power Power
supply supply
1 2
+ + _
–
+DC 24 +CM0 Pin 1, 2
-DC 24 +CM1 Encoder signal cable
Pin 49 (CLK+)
O-00 Pin 12 (CLK-)
Pin25 (DIR+)
Encoder
Motor
O-03 Pin 14 (DIR-)
O-06 Pin 3 (Enable)
2080-LC50-xxQVB
2080-LC30-xxQVB
O-07 Pin 7 (RST)
Kinetix3
3
Motor power cable
Kinetix
-CM0
-CM1
Notes:
1. Drive Enable (Pin 3) and Reset Drive (Pin 7) will be operating as sourcing inputs when (Pin 1, 2) connected to – of the Power Supply 2.
2. To help you configure Kinetix 3 drive parameters, so the drive can communicate and be controlled by a Micro830/Micro850/Micro870
controller, see publication CC-QS033. The parameter Command Type must be set to “Step/Direction.Positive Logic”, and the parameter
Controller Output Type must be set to “Open Collector Input”.
Sample Motion Wiring Configuration on 2080-LC30-xxQBB / 2080-LC50-xxQBB / 2080-LC70-xxQBB
24V 24V
Power Power
supply supply
1 2
+ + _
–
+DC 24 +CM0 Pin 1, 2
-DC 24 +CM1 Encoder signal cable
Pin 12(CLK-)
O-00 Pin 49(CLK+)
Pin 14(DIR-)
Encoder
Motor
O-03 Pin 25(DIR+)

O-06 Pin 3(Enable)
2080-LC50-xxQBB
2080-LC30-xxQBB
O-07 Pin 7(RST)

Kinetix33
Kinetix
-CM0 Motor power cable

-CM1
Notes:
1. Drive Enable (Pin 3) and Reset Drive (Pin 7) will be operating as sinking inputs when (Pin 1, 2) connected to + of the Power Supply 2.
2. To help you configure Kinetix 3 drive parameters, so the drive can communicate and be controlled by a Micro830/Micro850/Micro870
controller, see publication CC-QS033. The parameter Command Type must be set to “Step/Direction.Positive Logic”, and the parameter
Controller Output Type must be set to “Open Collector Input”.

Motion Control Function Motion control function blocks instruct an axis to a specified position,
Blocks distance, velocity, and state.
Function Blocks are categorized as Movement (driving motion) and

Administrative.
Administrative Function Blocks

Function Block Name Function Block Name
MC_Power MC_ReadAxisError
MC_Reset MC_ReadParameter
MC_TouchProbe MC_ReadBoolParameter
MC_AbortTrigger MC_WriteParameter
MC_ReadStatus MC_WriteBoolParameter
MC_SetPosition
WARNING: During Run Mode Change (RMC), the MC_Power function block should
be disabled, which will power down the axis. Otherwise the axis will remain
powered even if the function block is deleted.
Take note of the following:
• If a new instance of MC_Power accesses the axis, the axis will enter the error
stop state.
• If MC_Power is inside a UDFB and any edit is made to the UDFB that changes
the UDFB template (for example, adding a local variable), the axis will enter
the error stop state.
Movement Function Blocks

Correct Axis State for issuing
Function Block Name Description Function Block
This function block commands an axis to a Standstill, Discrete Motion,
MC_MoveAbsolute specified absolute position. Continuous Motion
This function block commands an axis of a Standstill, Discrete Motion,
MC_MoveRelative specified distance relative to the actual Continuous Motion
position at the time of execution.
This function block commands a never-ending Standstill, Discrete Motion,
MC_MoveVelocity axis move at a specified velocity. Continuous Motion
This function block commands the axis to
perform the “search home” sequence. The
“Position” input is used to set the absolute
MC_Home position when reference signal is detected, and Standstill
configured Home offset is reached. This
function block completes at “StandStill” if the
homing sequence is successful.
This function block commands an axis stop
and transfers the axis to the state “Stopping”. It
aborts any ongoing function block execution.
While the axis is in state Stopping, no other
function block can perform any motion on the
same axis. After the axis has reached velocity Standstill, Discrete Motion,
MC_Stop zero, the Done output is set to TRUE Continuous Motion, Homing
immediately. The axis remains in the state
“Stopping” as long as Execute is still TRUE or
velocity zero is not yet reached. As soon as
“Done” is SET and “Execute” is FALSE the axis
goes to state “StandStill”.

Movement Function Blocks (Continued)

Correct Axis State for issuing
Function Block Name Description Function Block
This function block commands an axis to a
controlled motion stop. The axis is moved to Standstill, Discrete Motion,
MC_Halt the state “Discrete Motion”, until the velocity is Continuous Motion
zero. With the Done output set, the state is
transferred to “StandStill”.
ATTENTION: During Run Mode Change, the Movement Function Blocks can
only be deleted when that Function Block has been done or aborted.
Otherwise unintended axis and Function Block behavior may occur.
ATTENTION: Each motion function block has a set of variable inputs and
outputs that allows you to control a specific motion instruction. See the
Connected Components Workbench Online Help for a description of these
variable inputs and outputs.
General Rules for the Motion Control Function Blocks
To work with motion control function blocks, users need to be familiar with
the following general rules.
General Rules for the Motion Function Block

Parameter General Rules
When Execute is True: The parameters are used with the rising edge of the Execute input. To modify any parameter, it is necessary to
Input parameters change the input parameter(s) and to trigger motion again.
When Enable is True: The parameters are used with the rising edge of the Enable input and can be modified continuously.
If a function block is configured with parameters that result in a violation of application limits, the instance of the function block
Inputs exceeding application generates an error. The Error output will be flagged On, and error information will be indicated by the output ErrorID.
limits The controller, in most cases, will remain in Run mode, and no motion error will be reported as a major controller fault.
For MC_MoveAbsolute function block, the position input is the absolute location commanded to the axis. For MC_MoveRelative, the
Position/Distance Input distance input is the relative location (considering current axis position is 0) from current position.
Velocity can be a signed value. Users are advised to use positive velocity.
Direction input for the MC_MoveVelocity function block can be used to define the direction of the move (that is, negative velocity x
Velocity Input negative direction = positive velocity).
For MC_MoveRelative and MC_MoveAbsolute function blocks the absolute value of the velocity is used.
Velocity input does not need to be reached if Jerk input is equal to 0.
For MC_MoveAbsolute, direction input is ignored. (This is reserved for future use.)
For MC_MoveVelocity, direction input value can be 1 (positive direction), 0 (current direction) or -1 (negative direction). For any other
Direction Input value, only the sign is taken into consideration. For example, -3 denotes negative direction, +2 denotes positive direction, and so on.
For MC_MoveVelocity, the resulting sign of the product value derived from velocity x direction decides the motion direction, if the
value is not 0. For example, if velocity x direction = +300, then direction is positive.
• Deceleration or Acceleration inputs should have a positive value. If Deceleration or Acceleration is set to be a non-positive value, an
error will be reported (Error ID: MC_FB_ERR_RANGE).
• The Jerk input should have a non-negative value. If Jerk is set to be a negative value, error will be reported.
(Error ID: MC_FB_ERR_RANGE).
Acceleration, Deceleration, and • If maximum Jerk is configured as zero in Connected Components Workbench motion configuration, all jerk parameters for the
Jerk Inputs motion function block has to be configured as zero. Otherwise, the function block reports an error (Error ID: MC_FB_ERR_RANGE).
• If Jerk is set as a non-zero value, S-Curve profile is generated. If Jerk is set as zero, trapezoidal profile is generated.
• If the motion engine fails to generate the motion profile prescribed by the dynamic input parameters, the function block reports an
error (Error ID: MC_FB_ERR_PROFILE).
See Function Block and Axis Status Error Codes on page 160 for more information about error codes.

General Rules for the Motion Function Block (Continued)

With Execute: The outputs Busy, Done, Error, and CommandAborted indicate the state of the function block and are mutually
exclusive – only one of them can be true on one function block. If execute is true, one of these outputs has to be true.
The outputs Done, Busy, Error, ErrorID, and CommandAborted are reset with the falling edge of Execute. However, the falling edge of
Execute does not stop or even influence the execution of the actual function block. Even if Execute is reset before the function block
completes, the corresponding outputs are set for at least one cycle.
If an instance of a function block receives a new Execute command before it completes (as a series of commands on the same
instance), the new Execute command is ignored, and the previously issued instruction continues with execution.
Output Exclusivity
With Enable: The outputs Valid and Error indicate whether a read function block executes successfully. They are mutually exclusive:
only one of them can be true on one function block for MC_ReadBool, MC_ReadParameter, MC_ReadStatus.
The Valid, Enabled, Busy, Error, and ErrorID outputs are reset with the falling edge of Enable as soon as possible.
Output Exclusivity
When used in Function Block Diagram, you can connect the axis output parameter to the Axis input parameter of another motion
function block for convenience (for example, MC_POWER to MC_HOME).
Axis Output When used in a Ladder Diagram, you cannot assign a variable to the Axis output parameter of another motion function block because
it is read-only.


The output Done is set when the commanded action has completed successfully.
With multiple function blocks working on the same axis in a sequence, the following rule applies:
When one movement on an axis is aborted with another movement on the same axis without having reached the final goal, output
Done will not be set on the first function block.
Behavior of Done Output
Every function block has a Busy output, indicating that the function block is not yet finished (for function blocks with an Execute
input), and new output values are pending (for function blocks with Enable input).
Busy is set at the rising edge of Execute and reset when one of the outputs Done, Aborted, or Error is set, or it is set at the rising edge
of Enable and reset when one of the outputs Valid or Error is set.
It is recommended that the function block continue executing in the program scan for as long as Busy is true, because the outputs
will only be updated when the instruction is executing. For example, in ladder diagram, if the rung becomes false before the
instruction finishes executing, the Busy output will stay true forever even though the function block has finished executing.
Behavior of Busy Output
Output Active In current implementation, buffered moves are not supported. Consequently, Busy and Active outputs have the same behavior.


CommandAborted is set when a commanded motion is aborted by another motion command.
When CommandAborted occurs, other output signals such as InVelocity are reset.
Behavior of CommandAborted
Output
The Enable input for read function blocks is level-sensitive. On every program scan with the Enable input as true, the function block
will perform a read and update its outputs. The Valid output parameter shows that a valid set of outputs is available.
The Valid output is true as long as valid output values are available and the Enable input is true. The relevant output values will be
Enable and Valid Status refreshed as long as the input Enable is true.
If there is a function block error, and the relevant output values are not valid, then the valid output is set to false. When the error
condition no longer exists, the values will be updated and the Valid output will be set again.
Relative move does not require the axis to be homed. It simply refers to a move in a specified direction and distance.
Relative Move versus Absolute Absolute move requires that the axis be homed. It is a move to a known position within the coordinate system, regardless of distance
Move and direction. Position can be negative or positive value.
Buffered Mode For all motion control function blocks, BufferMode input parameter is ignored. Only aborted moves are supported for this release.
All blocks have two outputs which deal with errors that can occur during execution. These outputs are defined as follows:
• Error – Rising edge of “Error” informs that an error occurred during the execution of the function block, where the function block
cannot successfully complete.
• ErrorID – Error number.
Error Handling • Types of errors:
• Function block logic (such as parameters out of range, state machine violation attempted)
• Hard limits or soft limits reached
• Drive failure (Drive Ready is false)
For more information about function block error, see Motion Function Block and Axis Status Error ID on page 161.
Simultaneous Execution of Two Movement Function Blocks (Busy Output = True)
The general rule is that when a movement function block is busy, then a
function block with the same instance (for example, MC_MoveRelative2)
cannot be executed again until the function block status is not busy.
MC_MoveRelative, MC_MoveAbsolute will be busy until final position is

reached. MC_MoveVelocity, MC_Halt, and MC_Stop will be busy until final
velocity is reached.

Velocity
Time
Execute1
Busy1
When a movement function block is busy, a function block with a different

instance (for example, MC_MoveRelative1 and MC_MoveAbsolute1 on the
same axis) can abort the currently executing function block. This is mostly
useful for on-the-fly adjustments to position, velocity, or to halt after a specific
distance.
Example: Move to Position Ignored Due to Busy

For simple moves, the movement
Simple move position using one instance function block finishes. Busy output
Velocity
of MC_MoveRelative, MC_MoveAbsolute indicates that the function block is

This command is ignored
executing and must be allowed to
finish before Execute input is toggled
again.
If Execute is toggled again before

Busy is false, the new command is
ignored. No error is generated.
Time
Execute1
Busy1

Example: Successful Aborted Move
Velocity
Aborted move is possible if using two
instances of MC_MoveRelative,
MC_MoveAbsolute. The second instance
can immediately abort the first instance
(and vice versa) for applications where on-
the-fly corrections are needed.
Time
Execute1
Busy1
CommandAborted1
Execute2
Busy2
Example: Changing Velocity With No Abort
When changing velocity, generally, an aborted move is not necessary since the
function block is only Busy during acceleration (or deceleration). Only a single
instance of the function block is required.
To bring the axis to a standstill, use MC_Halt.

Velocity
Time
Execute1
Busy
Halt Execute
Busy

It is possible for the movement function blocks and MC_Halt to abort another
motion function block during acceleration/deceleration. This is not
recommended as the resulting motion profile may not be consistent.
ATTENTION: If MC_Halt aborts another motion function block during

acceleration and the MC_Halt Jerk input parameter is less than the Jerk of
the currently executing function block, the Jerk of the currently executing
function block is used to prevent an excessively long deceleration.
Example: Aborted Movement Function Block During Acceleration/Deceleration
Velocity
Time
Execute1
Busy
CommandAborted
Halt Execute
Busy
IMPORTANT If MC_Halt aborts another movement function block during acceleration

and the MC_Halt Jerk input parameter is less than the Jerk of the
currently executing FB, the Jerk of the currently executing function
block is used to prevent excessively long deceleration.

Example: Error Stop using MC_Stop cannot be Aborted
Velocity
This command is ignored.
Time
MC_Stop Execute
Busy
Motion function block Execute
MC_Halt and MC_Stop are both used to bring an axis to a StandStill but
MC_Stop is used when an abnormal situation occurs.
MC_Stop can abort other motion function blocks but can never be
aborted itself.
MC_Stop goes to the Stopping state and normal operation cannot

resume.
Motion Axis and Parameters The following state diagram illustrates the behavior of the axis at a high level
when multiple motion control function blocks are activated. The basic rule is
that motion commands are always taken sequentially, even if the controller
has the capability of real parallel processing. These commands act on the axis’
state diagram.
The axis is always in one of the defined states see Figure 11 on page 153. Any
motion command is a transition that changes the state of the axis and, as a
consequence, modifies the way the current motion is computed.

Figure 11 - Motion Axis State Diagram
MC_MoveAbsolute
MC_MoveRelative MC_MoveVelocity
MC_MoveAbsolute; MC_MoveRelative; MC_Halt
MC_Halt
Discrete MC_MoveVelocity Continuous

Motion Motion
MC_Stop
MC_Stop
Error
Error Stopping
Note 6 Error
Done
Note 1
MC_MoveAbsolute MC_Stop
MC_MoveRelative
MC_MoveVelocity
ErrorStop
MC_Stop
Note 4 Note 2
Error Error
MC_Reset MC_Reset and
MC_Power.Status=FALSE
Done
Homing StandStill Note 3
Disabled Note 5
MC_Home
NOTES:
1. In the ErrorStop and Stopping states, all function blocks (except MC_Reset), can be called although they will not be executed.
MC_Reset generates a transition to the StandStill state. If an error occurs while the state machine is in the Stopping state, a transition to the ErrorStop
state is generated.
Axis position still updates even if the Axis state is ErrorStop. Also, the MC_TouchProbe function block is still active if it was executed before the ErrorStop
state.
2. Power.Enable = TRUE and there is an error in the Axis.
3. Power.Enable = TRUE and there is no error in the Axis.
4. MC_Stop.Done AND NOT MC_Stop.Execute.
5. When MC_Power is called with Enable = False, the axis goes to the Disabled state for every state including ErrorStop.
6. If an error occurs while the state machine is in Stopping state, a transition to the ErrorStop state is generated.
Axis States
The axis state can be determined from one of the following predefined states.
Axis state can be monitored through the Axis Monitor feature of the
Connected Components Workbench software when in debug mode.
Motion States
State Value State Name
0x00 Disabled
0x01 Standstill
0x02 Discrete Motion
0x03 Continuous Motion
0x04 Homing
0x06 Stopping
0x07 Stop Error

Axis State Update
On motion execution, although the motion profile is controlled by Motion

Engine as a background task, which is independent from POU scan, axis state
update is still dependent on when the relevant motion function block is called
by the POU scan.
For example, on a moving axis on a Ladder POU (state of a rung=true), an

MC_MoveRelative function block in the rung is scanned and the axis starts to
move. Before MC_MoveRelative completes, the state of the rung becomes
False, and MC_MoveRelative is no longer scanned. In this case, the state of this
axis cannot switch from Discrete Motion to StandStill, even after the axis fully
stops, and the velocity comes to 0.
Limits
The Limits parameter sets a boundary point for the axis, and works in
conjunction with the Stop parameter to define a boundary condition for the
axis on the type of stop to apply when certain configured limits are reached.
There are three types of motion position limits.

• Hard Limits
• Soft Limits
• PTO Pulse Limits
See Motion Axis Configuration in Connected Components Workbench on
page 163 for information on how to configure limits and stop profiles and
the acceptable value range for each.

If any one of these limits is reached on a moving axis (except on homing), an

over travel limit error will be reported and the axis will be stopped based on
configured behavior.
Sample Limits configuration in Connected Components Workbench
Hard Limits
Hard limits refer to the input signals received from physical hardware devices
such as limit switches and proximity sensors. These input signals detect the
presence of the load at the maximum upper and minimum lower extents of
allowable motion of the load or movable structure that carries the load, such as
a load tray on a transfer shuttle.
Hardware limits are mapped to discrete inputs that are associated with data
tags/variables.
When a hard limit switch is enabled, the axis comes to a stop when the limit
switch is detected during motion. If hard stop on hard limit switch is
configured as ON and the limit is detected, motion is stopped immediately
(that is, PTO pulse is stopped immediately by the hardware). Alternatively, if
hard stop on hard limit switch is configured as OFF, motion will be stopped
using Emergency Stop parameters.
When any hard limit switch is enabled, the input variable connecting to this
physical input can still be used in User Application.
When a hard limit switch is enabled, it will be used automatically for

MC_Home function block, if the switch is in the Homing direction configured
in the Connected Components Workbench software (Mode:
MC_HOME_ABS_SWITCH or MC_HOME_REF_WITH_ABS). See Homing
Function Block on page 173.
Soft Limits
Soft limits refer to data values that are managed by the motion controller.
Unlike hardware limits that detect the presence of the physical load at specific
points in the allowable motion of the load, soft limits are based on the stepper
commands and the motor and load parameters.
Soft limits are displayed in user-defined units. The user can enable individual
soft limits. For non-enabled soft limits (whether upper or lower), an infinite
value is assumed.

Soft Limits are activated only when the corresponding axis is homed. Users
can enable or disable soft limits, and configure an upper and lower limit
setting through the Connected Components Workbench software.
Soft Limits Checking on the Function Blocks

Function Block Limits Checking
MC_MoveAbsolute
The target position will be checked against the soft limits before motion starts.
MC_MoveRelative
MC_MoveVelocity The soft limits will be checked dynamically during motion.
When a soft limit is enabled, the axis comes to a stop when the limit is detected
during motion. The motion is stopped using emergency stop parameters.
If both hard and soft limits are configured as enabled, for two limits in the
same direction (upper or lower), the limits should be configured such that the
soft limit is triggered before the hard limit.
PTO Pulse Limits
This limit parameter is not configurable by the user and is the physical
limitation of the embedded PTO. The limits are set at 0x7FFF0000 and -
0x7FFF0000 pulses, for upper and lower limits, respectively.
PTO pulse limits are checked by the controller unconditionally — that is, the
checking is always ON.
On a non-continuous motion, to prevent a moving axis going to ErrorStop

status with Motion PTO Pulse limits detected, user needs to prevent current
position value going beyond PTO Pulse limit.
On a continuous motion (driven by MC_MoveVelocity function block), when

the current position value goes beyond PTO pulse limit, PTO pulse current
position will automatically roll over to 0 (or the opposite soft limit, if it is
activated), and the continuous motion continues.
For a continuous motion, if the axis is homed, and the soft limit in the motion
direction is enabled, soft limit will be detected before PTO pulse limit being
detected.
Motion Stop
There are three types of stops that can be configured for an axis.
Immediate Hardware Stop
This type of Immediate Stop is controlled by the hardware. If a Hard Stop on a

Hard Limit switch is enabled, and the Hard Limit has been reached, the PTO
pulse for the axis will be cut off immediately by the controller. The stop
response has no delay (less than 1 μs).

Immediate Soft Stop
The maximum possible response delay for this type of stop could be as much as
the Motion Engine Execution time interval. This type of stop is applicable in
the following scenarios:
• During motion, when axis PTO Pulse Limit is reached;
• One Hard Limit is enabled for an axis, but Hard Stop on Hard Limit
switch is configured as Off. If the Emergency Stop is configured as
Immediate Software Stop, during motion, when the Hard Limit switch is
detected;
• One Soft Limit is enabled for an axis and the axis has been homed. If the
emergency stop is configured as Immediate Soft Stop, during motion,
when the Soft Limit reach is detected;
• The Emergency Stop is configured as Immediate Soft Stop. During
motion, MC_Stop function block is issued with Deceleration parameter
equal to 0.
Decelerating Soft Stop
Decelerating soft stop could be delayed as much as Motion Engine Execution

Time interval. This type of stop is applied in the following scenarios:
• One Hard Limit is enabled for an axis, but Hard Stop on Hard Limit
switch is configured as Off. If the emergency stop is configured as
decelerating stop, during motion, when the Hard Limit switch is
detected;
• One Soft Limit is enabled for an axis and the axis has been homed. If the
emergency stop is configured as decelerating stop, during motion, when
the soft limit reach is detected by firmware;
• The Emergency Stop is configured as Decelerating Stop. During motion,
the MC_Stop function block is issued with deceleration parameter set
to 0.
• During motion, MC_Stop function block is issued with Deceleration
parameter not set to 0.
Motion Direction
For distance (position) motion, with the target position defined (absolute or
relative), the direction input is ignored.
For velocity motion, direction input value can be positive (1), current (0) or
negative (-1). For any other value, only the sign (whether positive or negative) is
considered and defines whether the direction is positive or negative. This
means that if the product of velocity and direction is -3, then direction type is
negative.

MC_MoveVelocity Supported Direction Types

Direction Type Value Used(1) Direction Description
Specific for motion/rotation direction.
Positive direction 1 Also called clockwise direction for rotation motion.
Current direction instructs the axis to continue its motion with
new input parameters, without direction change.
Current direction 0 The direction type is valid only when the axis is moving and the
MC_MoveVelocity is called.
Specific for motion/rotation direction.
Negative direction -1 Also referred to as counter-clockwise direction for rotation
motion.
(1) Data type: short integer.
Axis Elements and Data Types
Axis_Ref Data Type
Axis_Ref is a data structure that contains information on a motion axis. It is

used as an input and output variable in all motion function blocks. One
axis_ref instance is created automatically in the Connected Components
Workbench software when the user adds one motion axis to the configuration.
The user can monitor this variable in controller debug mode through the
software when the motion engine is active, or in the user application as part of
user logic. It can also be monitored remotely through various communication
channels.
Data Elements for Axis_Ref

Element Name Data Type Description
The logic axis ID automatically assigned by the Connected Components
Axis_ID UINT8 Workbench software. This parameter cannot be edited or viewed by user.
ErrorFlag UINT8 Indicates whether an error is present in the axis.
Indicates whether homing operation is successfully executed for the axis
or not.
AxisHomed UINT8 When the user tries to redo homing for an axis with AxisHomed already set
(homing performed successfully), and the result is not successful, the
AxisHomed status will be cleared.
Indicates whether the axis is in constant velocity movement or not.
ConsVelFlag UINT8 Stationary axis is not considered to be in constant velocity.
AccFlag UINT8 Indicates whether the axis is in an accelerating movement or not.
DecFlag UINT8 Indicates whether the axis is in a decelerating movement or not.
Indicates the current state of the axis. For more information, see Axis
AxisState UINT8
States on page 153.
Indicates the cause for axis error when error is indicated by ErrorFlag. This
ErrorID UINT16 error usually results from motion function block execution failure.
See Motion Function Block and Axis Status Error ID on page 161.
ExtraData UINT16 Reserved.
Indicates the final target position of the axis for MoveAbsolute and
REAL MoveRelative function blocks.
TargetPos
(float)(1) For MoveVelocity, Stop, and Halt function blocks, TargetPos is 0 except
when the TargetPos set by previous position function blocks is not cleared.

Data Elements for Axis_Ref (Continued)

Element Name Data Type Description
REAL On a moving axis, this is the current position the controller commands the axis
CommandPos
(float)(1) to go to.
The maximum target velocity issued to the axis by a move function block.
REAL The value of TargetVel is same as the velocity setting in current function
TargetVel block, or smaller, depending on other parameters in the same function
(float)(1) block. This element is a signed value indicating direction information.
See PTO Pulse Accuracy on page 172 for more information.
REAL During motion, this element refers to the velocity the controller commands
CommandVel the axis to use. This element is a signed value indicating direction
(float)(1) information.
(1) See Real Data Resolution on page 170 for more information on REAL data conversion and rounding.
IMPORTANT • Once an axis is flagged with error, and the error ID is not zero, the user needs
to reset the axis (using MC_Reset) before issuing any other movement
function block.
• The update for axis status is performed at the end of one program scan
cycle, and the update is aligned with the update of Motion Axis status.
Axis Error Scenarios
In most cases, when a movement function block instruction issued to an axis

results in a function block error, the axis is also usually flagged as being in
Error state. The corresponding ErrorID element is set on the axis_ref data for
the axis. However, there are exception scenarios where an axis error is not
flagged. The exception can be, but not limited to, the following scenarios:
• A movement function block instructs an axis, but the axis is in a state
where the function block could not be executed properly. For example,
the axis has no power, or is in Homing sequence, or in Error Stop state.
• A movement function block instructs an axis, but the axis is still
controlled by another movement function block. The axis cannot allow
the motion to be controlled by the new function block without going to a
full stop. For example, the new function block commands the axis to
change motion direction.
• When one movement function block tries to control an axis, but the axis
is still controlled by another movement function block, and the newly
defined motion profile cannot be realized by the controller. For example,
User Application issues an S-Curve MC_MoveAbsolute function block to
an axis with too short a distance given when the axis is moving.
• When one movement function block is issued to an axis, and the axis is
in the Stopping or Error Stopping sequence.
For the above exceptions, it is still possible for the user application to issue a
successful movement function block to the axis after the axis state changes.

MC_Engine_Diag Data Type
The MC_Engine_Diag data type contains diagnostic information on the

embedded motion engine. It can be monitored in debug mode through the
Connected Components Workbench software when the motion engine is
active, or through the user application as part of user logic. It can also be
monitored remotely through various communication channels.
One MC_Engine_Diag instance is created automatically in the Connected

Components Workbench software when the user adds the first motion axis in
the motion configuration. This instance is shared by all user-configured
motion axes.
Data Elements for MC_Engine_Diag

Element Name Data Type
MCEngState UINT16
CurrScantime(1) UINT16
MaxScantime(1) UINT16
CurrEngineInterval(1) UINT16
MaxEngineInterval(1) UINT16
ExtraData UINT16
(1) The time unit for this element is microsecond. This diagnostic information can be used to optimize motion configuration and
user application logic adjustment.
MCEngstate States
State Name State Description
MC engine exists (at least one axis defined), but the engine is idle as there
MCEng_Idle 0x01 is no axis is moving. The Engine diagnostic data is not being updated.
MC engine exists (at least one axis defined) and the engine is running. The
MCEng_Running 0x02 diagnostic data is being updated.
MCEng_Faulted 0x03 MC engine exists, but the engine is faulted.
Function Block and Axis All motion control function blocks share the same ErrorID definition.
Status Error Codes
Axis error and function block error share the same Error ID, but error
descriptions are different, as described in Table 14 on page 161.
Error code 128 is warning information to indicate the motion profile has
been changed and velocity has been adjusted to a lower value but the
function block can execute successfully.

Table 14 - Motion Function Block and Axis Status Error ID

Error ID Error ID MACRO Error Description for Function Block Error Description for Axis Status(1)
00 MC_FB_ERR_NO Function block execution is successful. The axis is in operational state.
The axis is not operational due to incorrect axis state
The function block cannot execute because the axis is not
01 MC_FB_ERR_WRONG_STATE detected during a function block execution. Reset the state
in the correct state. Check the axis state. of the axis using the MC_Reset function block.
The axis is not operational due to invalid axis dynamic
The function block cannot execute because there is invalid parameter(s) (velocity, acceleration, deceleration, or jerk)
axis dynamic parameter(s) (velocity, acceleration, set in a function block.
02 MC_FB_ERR_RANGE deceleration, or jerk) set in the function block. Reset the state of the axis using the MC_Reset function
Correct the setting for the dynamic parameters in the block.
function block against Axis Dynamics configuration page. Correct the setting for the dynamic parameters in the
function block against Axis Dynamics configuration page.
The axis is not operational due to invalid parameter(s)
The function block cannot execute because there is invalid other than velocity, acceleration, deceleration, or jerk, set
parameter other than velocity, acceleration, deceleration, in a function block.
03 MC_FB_ERR_PARAM or jerk, set in the function block. Reset the state of the axis using the MC_Reset function
Correct the setting for the parameters (for example, mode block.
or position) for the function block. Correct the setting for the parameters (for example, mode
or position) for the function block.
The function block cannot execute because the axis does Motion internal Fault, Error ID = 0x04.
04 MC_FB_ERR_AXISNUM not exist, the axis configuration data is corrupted, or the Call Tech support.
axis is not correctly configured.
The axis is not operational due to drive or mechanical
The function block cannot execute because the axis is issues.
faulty due to drive or mechanical issues. Check the connection between the drive and the controller
05 MC_FB_ERR_MECHAN Check the connection between the drive and the controller (Drive Ready and In-Position signals), and ensure the drive
(Drive Ready and In-Position signals), and ensure the drive is operating normally.
is operating normally. Reset the state of the axis using the MC_Reset function
block.
The axis is not powered on.
The function block cannot execute because the axis is not Power on the axis using MC_Power function block.
06 MC_FB_ERR_NOPOWER powered on. Reset the state of the axis using the MC_Reset function
Power on the axis using MC_Power function block. block.
The function block cannot execute because the resource
required by the function block is controlled by some other
function block or not available.
Ensure the resource required by the function block The axis is not operational due to the resource required by
available for use. a function block is under the control of other function
Some examples: block, or not available.
07 MC_FB_ERR_RESOURCE • MC_power function block attempts to control the same Ensure the resource required by the function block
axis. available for use.
Reset the state of the axis using the MC_Reset function
• MC_Stop function block is executed against the same block.
axis at the same time.
• Two or more MC_TouchProbe function blocks are
executed against the same axis at the same time.
The axis is not operational due to motion profile defined in
The function block cannot execute because the motion a function block cannot be achieved.
08 MC_FB_ERR_PROFILE profile defined in the function block cannot be achieved. Reset the state of the axis using the MC_Reset function
Correct the profile in the function block. block. Correct the profile in the function block.
The function block cannot execute because the motion The axis is not operational. The motion profile requested in
profile requested in the function block cannot be achieved the function block cannot be achieved because of current
due to current axis velocity. axis velocity.
Some examples: Some examples:
• The function block requests the axis to reverse the • The function block requests the axis to reverse the
direction while the axis is moving.
09 MC_FB_ERR_VELOCITY direction while the axis is moving.
• The required motion profile cannot be achieved due to • The required motion profile cannot be achieved due to
current velocity too low or too high. current velocity too low or too high.
Reset the state of the axis using the MC_Reset function
Check the motion profile setting in the function block, and block.
correct the profile, or re-execute the function block when Correct the motion profile in the function block, or re-
the axis velocity is compatible with the requested motion execute the function block when the axis velocity is
profile. compatible with the requested motion profile.

Table 14 - Motion Function Block and Axis Status Error ID (Continued)

Error ID Error ID MACRO Error Description for Function Block Error Description for Axis Status(1)
The axis is not operational due to soft limit error detected,
This function block cannot execute as it will end up moving or due to expected soft limit error in a function block.
beyond the soft limit, or the function block is aborted as Reset the state of the axis using the MC_Reset function
10 MC_FB_ERR_SOFT_LIMIT the soft limit has been reached. block.
Check the velocity or target position settings in the Check the velocity or target position settings for the
function block, or adjust soft limit setting. function block, or adjust Soft Limit setting.
This function block is aborted as the Hard Limit switch
active state has been detected during axis movement, or The axis is not operational due to hard limit error detected.
aborted as the Hard Limit switch active state has been Reset the state of the axis using the MC_Reset function
11 MC_FB_ERR_HARD_LIMIT detected before axis movement starts. block, and then move the axis away from the hard limit
Move the axis away from the hard limit switch in the switch in the opposite direction.
opposite direction.
The axis is not operational due to PTO Accumulator logic
This function block cannot execute as it will end up moving limit error detected, or due to expected PTO accumulator
beyond the PTO Accumulator logic limit, or the function logic limit error in a function block.
block is aborted as the PTO Accumulator logic limit has Reset the state of the axis using the MC_Reset function
12 MC_FB_ERR_LOG_LIMIT been reached. block.
Check the velocity or target position settings for the Check the velocity or target position settings for the
function block. Or, use MC_SetPosition function block to function block. Or, use MC_SetPosition function block to
adjust the axis coordinate system. adjust the axis coordinate system.
The axis is not operational due to a motion engine
execution error.
A motion engine execution error is detected during the Cycle power to the entire motion setup, including
execution of this function block. controller, drives and actuators, and then download the
Cycle power to the entire motion setup, including
13 MC_FB_ERR_ENGINE User Application again.
controller, drives and actuators, and then download the If the fault is persistent, contact your local Rockwell
User Application again. Automation technical support representative. For contact
If the fault is persistent, call Tech support. information, see:
rok.auto/support
The Function Block cannot execute because the axis needs The axis is not operational because the axis is not homed.
to be homed first.
16 MC_FB_ERR_NOT_HOMED Reset the state of the axis using the MC_Reset Function
Execute homing against the axis using MC_Home Function Block.
Block.
Motion internal Fault, Error ID = 0x80.
Warning: The requested motion parameter for the axis has Contact your local Rockwell Automation technical support
128 MC_FB_PARAM_MODIFIED been adjusted. representative. For contact information, see: rok.auto/
The function block executes successfully. support
(1) You can view axis status through the Axis Monitor feature of the Connected Components Workbench software.
When a motion control function block ends with an error, and the axis is in
ErrorStop state, in most cases, MC_Reset function block (or, MC_Power Off/
On and MC_Reset) can be used to have the axis to be recovered. With this, the
axis can get back to normal motion operation without stopping the controller
operation.
Major Fault Handling In case the controller encounters issues where recovery is not possible through
the Stop, Reset, or Power function blocks, controller operation will be stopped
and a major fault will be reported.
Table 15 on page 163 defines the motion-related major fault codes for Micro830,
Micro850, and Micro870 controllers.

Table 15 - Major Fault Error Codes and Description

Major Fault Fault ID MACRO Major Fault Description
Value
There is general configuration error detected in the motion
configuration downloaded from Connected Components
Workbench software, such as Num of Axis, or Motion
0xF100 EP_MC_CONFIG_GEN_ERR execution interval being configured out of range.
When this major fault is reported, there could be no axis in
ErrorStop state.
Motion configuration has mismatch issues with motion
resource downloaded to the controller. There are some
0xF110 EP_MC_RESOURCE_MISSING motion resources missing.
When this major fault is reported, there could be no axis in
ErrorStop state.
Motion configuration for axis cannot be supported by this
catalog, or the configuration has some resource conflict
with some other motion axis, which has been configured
0xF12x EP_MC_CONFIG_AXS_ERR earlier. The possible reason could be maximum velocity,
max acceleration is configured out of supported range.
x = the logic Axis ID (0…3).
There is a motion engine logic error (firmware logic issue or
memory crash) for one axis detected during motion engine
cyclic operation. One possible reason can be motion engine
0xF15x EP_MC_ENGINE_ERR data/memory crash.
(This is motion engine operation error, and should not
happen in normal condition.)
x = the logic Axis ID (0…3).
Motion Axis Configuration in A maximum of three motion axes can be configured through the Connected
Connected Components Components Workbench software. To add, configure, update, delete, and
monitor an axis in the Connected Components Workbench software, see the
Workbench sections that follow.
Configuration changes must be compiled and downloaded to the

controller to take effect.
Values for the different motion axis parameters are validated based on a
set of relationships and pre-determined absolute range. See Motion Axis
Parameter Validation on page 172 for a description of the relationships
between parameters.
Add New Axis
IMPORTANT Motion Engine Execution Time
When an axis is added to the configuration, the Motion Engine Execution Time can be configured from 1…10 ms (default: 1 ms). This global parameter applies to all motion axis configurations.
1. On the Device Configuration tree, right-click <New Axis>. Click Add.

2. Provide an axis name. Click Enter.

Name must begin with a letter or underscore character, followed by a letter
or single underscore characters.
You can also press F2 to edit axis name.
3. Expand the newly created Axis to see the following configuration

categories:
• General
• Motor and Load
• Limits
• Dynamics
• Homing
To help you edit these motion properties, see Edit Axis Configuration on
page 164. You can also learn more about axis configuration parameters.
Edit Axis Configuration
General Parameters
1. On the axis configuration tree, click General.
The <Axis Name> - General properties tab appears.
2. Edit General parameters. See Table 16 on page 165 for a description of the
general configuration parameters for a motion axis.
IMPORTANT To edit these general parameters, see Input and Output Signals on
page 141 for more information about fixed and configurable outputs.

Table 16 - General Parameters

Parameter Description and Values
Axis Name User defined. Provides a name for the motion axis.
PTO Channel Shows the list of available PTO channels.
Presents the logical variable name of the Direction Output channel based on the PTO
Pulse Output channel value that has been assigned.
Presents the logical variable name of the Direction Output channel based on the PTO
Direction Output channel value that has been assigned.
Drive Enable Output Servo On Output Enable flag. Check the option box to enable.
- Output The list of available digital output variables that can be assigned as servo/drive output.
- Active Level Set as High (default) or Low.
In-position Input Check the option box to enable in-position input monitoring.
List of digital input variables for in-position input monitoring.
- Input Select an input.
Servo Ready Input Enable flag.
Drive Ready Input Check the option box to enable the input.
- Input The list of digital input variables. Select an input.
Configure whether an input for touch probe is used.
Touch Probe Input Check the option box to enable touch probe input.
- Input List of digital input variables. Select an input.
- Active Level Set the active level for touch probe input as High (default) or Low.
PTO Channel Naming
Names of embedded PTO channels have the prefix EM (embedded) and each
available PTO channel is enumerated starting from 0. For example, a controller
that supports three axes will have the following PTO channels available:
• EM_0
• EM_1
• EM_2
Motor and Load
Edit the Motor Load properties as defined in Table 17 on page 166.
IMPORTANT Certain parameters for Motor and Load are Real values. For more
information, see Real Data Resolution on page 170

Table 17 - Motor and Load Parameters

Parameter Description and Values
Defines user unit scaling that matches your mechanical system values. These units
User-defined Unit shall be carried forward into all command and monitor axis in user unit values
throughout programming, configuration, and monitoring functions.
Select from any of the following options:
– mm
– cm
Position – inches
– revs
– custom unit (ASCII format of up to 7 characters long)
Time Read only. Predefined in seconds.
Motor Revolution Defines pulse per revolution and travel per revolution values.
Defines the number of pulses needed to obtain one revolution of the drive motor.
Pulse per Revolution(1) Range: 0.0001…8388607
Default: 200.0
Travel per revolution defines the distance, either linear or rotational, that the load
moves per revolution of the motor.
Travel per Revolution(1) Range: 0.0001…8388607.
Default:1.0 user unit.
Direction Defines polarity, mode, and change of delay time values.
Direction polarity determines whether the direction signal received by the
controller as a discrete input should be interpreted on the input as received by the
Polarity motion controller, (that is, the non-inverted case), or whether the signal should be
inverted prior to interpretation by the motion control logic.
Set as Inverted or Non-inverted (default).
Set as Bi-directional (default), Positive (clockwise), or Negative (counter-clockwise)
Mode direction.
Configure from 0…100 ms.
Change Delay Time Default value is 10 ms.
(1) The parameter is set as REAL (float) value in Connected Components Workbench. To learn more about conversions and
rounding of REAL values, see Real Data Resolution on page 170.
A red border on an input field indicates that an invalid value has been
entered. Scroll over the field to see tooltip message that will let you know
the valid value range for the parameter. Supply the valid value.
ATTENTION: Modifying Motor Revolution parameters may cause axis

runaway.
Limits
Edit the Limits parameters based on the table below.
ATTENTION: To learn more about the different types of Limits, see Limits on
page 154.

Table 18 - Limits Parameters
Parameter(1) Value
Hard Limits Defines upper and lower hard limits for the axis.
Configure whether to perform a forced PTO hardware stop
(immediately turn off pulse output) or whether to decelerate (leave
pulse output on and use deceleration values as defined on the
When hard limits is reached, apply Emergency Stop profile).
Set as any of the following:
• Forced PTO Hardware Stop
• Emergency Stop Profile
Lower Hard Limit Click checkbox to enable a lower hard limit.
Active Level (for Lower Hard Limit) High or Low.
Upper Hard Limit Click checkbox to enable.
Active Level (for Upper Hard Limit) High or Low.
Soft Limits Defines upper and lower soft limits values.
Lower Soft Limit(2) Lower soft limit should be less than upper soft limit.
1. Click checkbox to enable an lower/upper soft limit.
Upper Soft Limit(2) 2. Specify a value (in mm).
(1) To convert from user units to pulse:
Travel per revolution
Value in user unit = Value in pulse x Pulse per revolution
entered. Scroll over the field to see tooltip message that will let you know
the valid value range for the parameter. Supply the valid value.
3. Click Dynamics. The <Axis Name> - Dynamics tab appears. Edit the
Dynamics parameters based on the values in Table 19 on page 168.

Table 19 - Dynamics Parameters

Parameter Values
Start/Stop Velocity The range is based on Motor and Load parameters (See Motor and Load
(1) (2)
Parameters on page 166) using:
Range 1…100,000 pulse/sec
Default: 300 rpm
For example, you can configure the value from 0.005…500 mm/s for 200 pulses
Start/Stop Velocity in rpm(1) (2) per revolution and units of 1 mm per revolution.(3)
Rpm value is automatically populated when a value in user units is specified, but
the user can also initially enter an rpm value.
Start/stop velocity should not be greater than maximum velocity.
The range is based on Motor and Load parameters (See Motor and Load
(1) (2) Parameters on page 166) using:
Max Velocity Range: 1…10,000,000 pulse/sec.
Default: 100,000.0 pulse/sec
(1)
Max Acceleration Range: 1…10,000,000 pulse/sec2
Default: 10,000,000 pulse/sec2
Max Deceleration(1) Range: 1…100,000 pulse/sec2
Max Jerk(1) Range: 0…10,000,000 pulse/sec3
Emergency Stop Profile Defines stop type, velocity, deceleration, and jerk values.
Stop Type Set as Deceleration Stop (default) or Immediate Stop.
Stop Velocity(1) Range: 1…100,000 pulse/sec
Default: 300 rpm
Stop Deceleration(1) Range: 1…10,000,000 pulse/sec
Default: 300.0 rpm2
Stop Jerk(1) Range: 0...10,000,000 pulse/sec3
Default: 0.0 rpm3 (Disabled)
(2) The formula for deriving rpm to user unit, and vice versa:
v (in user unit/sec) x 60 s
v (in rpm) =
travel per revolution (in user unit)
(3) To convert from parameter value from pulse to user units:
Travel per revolution
Value in user unit = Value in pulse x Pulse per revolution
entered. Scroll over the field to see tooltip message that will let you
know the valid value range for the parameter. Supply the valid value.

4. Set Homing parameters based on the description in Table 20. Click

Homing.
Table 20 - Homing Parameters

Parameter Value Range
Homing Direction Positive (clockwise) or negative (counterclockwise).
Range: 1…100,000 pulse/sec
Homing Velocity(1) Default: 5,000.0 pulse/sec (25.0 mm/sec)
NOTE: Homing Velocity should not be greater than the maximum velocity.
Range: 1…10,000,000 pulse/sec2

Homing Acceleration(1) Default: 5000.0 pulse/sec2 (25.0 mm/sec2)
NOTE: Homing Acceleration should not be greater than Maximum Acceleration.

Homing Deceleration(1) Default: 5000.0 pulse/sec2 (25.0 mm/sec2)
NOTE: Homing Deceleration should not be greater than Maximum Deceleration.

Homing Jerk(1) Default: 0.0 pulse/sec3 (0.0 mm/sec3)
NOTE: Homing Jerk should not be greater than Maximum Jerk.
Range: 1…5,000 pulse/sec
Creep Velocity(1) Default: 1000.0 pulse/sec (5.0 mm/sec)
NOTE: Homing Creep Velocity should not be greater than Maximum Velocity.
Range: -1073741824…+1073741824 pulse
Homing Offset(1) Default: 0.0 pulse (0.0 mm)
Home Switch Input Enable home switch input by clicking the checkbox.
- Input Read-only value specifying the input variable for home switch input.
- Active Level High (default) or Low.
Home Marker Input Enable the setting of a digital input variable by clicking the checkbox.
- Input Specify digital input variable for home marker input.
- Active Level Set the active level for the home switch input as High (default) or Low.

Axis Start/Stop Velocity
Start/Stop velocity is the initial velocity when an axis starts to move, and the
last velocity before the axis stops moving. Generally, Start/Stop velocity is
configured at some low value, so that it is smaller than most velocity used in
the motion function block.
• When the target velocity is smaller than Start/Stop velocity, move the
axis immediately at the target velocity.
• When the target velocity is NOT smaller than Start/Stop velocity, move
the axis immediately at Start/Stop velocity.
Real Data Resolution
Certain data elements and axis properties use REAL data format (single-
precision floating point format). Real data has seven-digit resolution and digit
values entered by the user that are longer than seven digits are converted. See
the examples in Table 21.
Table 21 - REAL Data Conversion Examples

User Value Converted To
0.12345678 0.1234568
1234.1234567 1234.123
12345678 1.234568E+07 (exponential format)
0.000012345678 1.234568E-05 (exponential format)
2147418166 2.147418+E09
-0.12345678 -0.1234568
If the number of digits is greater than seven (7) and the eighth digit is greater
than or equal to 5, then the seventh digit is rounded up. For example:
21474185 rounded to 2.147419E+07

21474186 rounded to 2.147419E+07
If the eighth digit is <5, no rounding is done and the seventh digit remains the
same. For example:
21474181 rounded to 2.147418E+07
Table 22 - Examples for Motion Configuration

Converted Value in
Actual Value Connected
Parameter Entered by User Components Tooltip Error Value(1)
Workbench
8388608 Pulse per revolution must be in the
Pulses per revolution 8388608 (no conversion) range of 0.0001…8388607 user unit.
Upper Soft limit must be greater than
Upper Soft Limit 10730175 1.073018E+7 Lower Soft Limit. The range is from 0
(exclusive) to 1.073217E+07 user unit.
Lower Soft limit must be smaller than
Lower Soft Limit -10730175 -1.073018E+7 Upper Soft Limit. The range is from -
1.073217E+07...0 (exclusive) user unit.
(1) On the axis configuration page in Connected Components Workbench, an input field with a red border indicates that the value
that has been entered is invalid. A tooltip message should let you know the expected range of values for the parameter. The
range of values presented in the tooltip messages are also presented in REAL data format.

Variable Monitor Example
The Variable Monitor displays six significant digits with rounding, although
the real data type still contains seven significant digits.
In this example, the user has entered the Target

Position value of 2345.678.
This value is rounded up to six digits (2345.68) in
the Variable Monitoring screen.
Axis Monitor Example
The Axis Monitor displays seven significant digits with rounding.
ATTENTION: See Motion Axis Configuration in Connected Components

Workbench on page 163 to learn more about the different axis configuration
parameters.

PTO Pulse Accuracy
Micro800 motion feature is pulse-based and the value of distance and velocity
are designed in such a way that all PTO-related values are integers at the
hardware level, when converting to PTO pulse.
For example, if the user configures Motor Pulses per Revolution as 1,000 and
Travel per Revolution as 10 cm and the user wants to drive velocity at 4.504 cm/
sec. The target velocity is 4.504 cm/sec (that is, 450.4 pulse/sec). In this case, the
actual commanded velocity will be 4.5 cm/sec (that is, 450 pulse/sec), and the
0.4 pulse/sec is rounded off.
This rounding scheme also applies to other input parameters such as Position,
Distance, Acceleration, Deceleration, and Jerk. For instance, with above motor
revolution configuration, setting Jerk as 4.504 cm/sec3 is the same as setting
Jerk as 4.501 cm/sec3, as both are rounded off to 4.5 cm/sec3. This rounding
applies to both axis configuration input in the Connected Components
Workbench software and function block input.
Motion Axis Parameter Validation
Besides falling within the predetermined absolute range, motion axis

parameters are validated based on relationships with other parameters. These
relationships or rules are listed below. Error is flagged whenever there is
violation to these relationships.
• Lower Soft Limit should be less than the Upper Soft Limit.
• Start/Stop velocity should not be greater than the maximum velocity.
• Emergency Stop velocity should not be greater than the maximum
velocity.
• Homing velocity should not be greater than the maximum velocity.
• Homing acceleration should not be greater than maximum acceleration.
• Homing deceleration should not be greater than maximum deceleration.
• Homing jerk should not be greater than maximum jerk.
• Homing creep velocity should not be greater than maximum velocity.
Delete an Axis
1. On the device configuration tree, and under Motion, right-click the axis
name and select Delete.

2. A message box appears asking to confirm deletion. Click Yes.
Monitor an Axis To monitor an axis, the Connected Components Workbench software should
be connected to the controller and in DEBUG mode.
1. On the device configuration page, click Axis Monitor.
2. The Axis Monitor window appears with the following characteristics
available for viewing:
• Axis state
• Axis homed
• Movement
• Error description
• Command position in user unit
• Command velocity in user unit per second
• Target position in user unit
• Target velocity in user unit per second
Homing Function Block The homing function block MC_Home commands the axis to perform the
“search home” sequence. The Position input is used to set the absolute position
when the reference signal is detected, and configured home offset is reached.
This function block completes at StandStill if the homing sequence is
successful.
MC_Home only can be aborted by the function blocks MC_Stop or MC_Power.

Any abort attempt from other moving function blocks will result in function
block failure with Error ID = MC_FB_ERR_STATE. However, homing
operation is not interrupted, and can be executed as usual.
If MC_Home is aborted before it completes, the previously searched home

position is considered as invalid, and the axis Homed status is cleared.
After axis power on is done, the axis Homed status is reset to 0 (not homed).
On most scenarios, the MC_Home function block needs to be executed to
calibrate the axis position against the axis home configured after MC_Power
(On) is done.
Table 23 on page 174 describes five homing modes supported on Micro830,


Table 23 - Homing Modes

Homing Mode Homing Mode Name Homing Mode Description
Value
0x00 MC_HOME_ABS_SWITCH Homing process searches for Home Absolute switch.
0x01 MC_HOME_LIMIT_SWITCH Homing process searches for limit switch.
Homing process searches for Home Absolute switch plus
0x02 MC_HOME_REF_WITH_ABS
using encoder reference pulse.
Homing process searches for limit switch plus using
0x03 MC_HOME_REF_PULSE encoder reference pulse.
Static homing process with direct forcing a home position
from user reference. The function block will set current
0x04 MC_HOME_DIRECT position the mechanism is in as home position, with its
position determined by the input parameter, “Position”.
IMPORTANT If axis is powered On with only one direction enabled, the MC_Home
function block (in modes 0, 1, 2, 3) will generate an error and only
MC_Home function block (mode 4) can be executed. See MC_Power
function block for more details.
Conditions for Successful Homing
For homing operation to be successful, all configured switches (or sensors)

must be properly positioned and wired. The correct position order from the
most negative position to the most positive position—that is, from the
leftmost to the rightmost in the homing setup diagrams in this section—for
the switches are:
1. Lower Limit switch
2. ABS Home switch
3. Upper Limit switch
During MC_Home function block execution, the home position will be reset,
and the soft limits mechanical position will be recalculated. During homing
sequence, the motion configuration for the soft limits will be ignored.
The homing motion sequence discussed in this section has the following
configuration assumptions:
1. Homing direction is configured as negative direction;
2. The Lower limit switch is configured as enabled and wired;
The different homing modes, as defined in Table 23, can have different, but
still similar motion sequence. The concept discussed below is applicable to
various homing configurations.

MC_HOME_ABS_SWITCH
IMPORTANT If home switch is not configured as enabled, MC_HOME_ABS_SWITCH (0)

homing fails with MC_FB_ERR_PARAM.
MC_HOME_ABS_SWITCH (0) homing procedure performs a homing

operation against the home switch. The actual motion sequence is dependent
on the home switch, limit switch configuration, and the actual status for the
switches before homing starts—that is, when the MC_Home function block is
issued.
Scenario 1: Moving part at right (positive) side of home switch before homing starts
The homing motion sequence for this scenario is as follows:

1. Moving part moves to the left side (negative direction);
2. When home switch is detected, the moving part decelerates to stop;
3. Moving part moves back (positive direction) in creep velocity to detect
home switch On→Off edge;
4. Once home switch On→Off is detected, record the position as
mechanical home position, and decelerate to stop;
5. Move to the configured home position. The mechanical home position
recorded during moving back sequence, plus the home offset configured
for the axis in the Connected Components Workbench software.
Scenario 2: Moving part is in between Lower Limit and Home switch before homing starts

1. Moving part moves to its left side (negative direction);
2. When lower limit switch is detected, the moving part decelerates to stop,
or stop immediately, according to limit switch hard stop configuration;
3. Moving part moves back (in positive direction) in creep velocity to detect
home switch On→Off edge;
4. Once home switch On→Off edge is detected, record the position as
If Lower Limit switch is not configured, or not wired, the homing motion
fails, and moves continuously to the left until the drive or moving part
fails to move.
Scenario 3: Moving part on Lower Limit or Home switch before homing starts

1. Moving part moves to its right side (in positive direction) in creep
velocity to detect home switch On→Off edge;
2. Once home switch On→Off edge is detected, record the position as
recorded during moving right sequence, plus the home offset configured

Scenario 4: Moving part at left (negative) side of Lower Limit switch before homing starts
In this case, the homing motion fails and moves continuously to the left until
drive or moving part fails to move. User needs to make sure the moving part at
the proper location before homing starts.
MC_HOME_LIMIT_SWITCH
IMPORTANT If Lower Limit switch is not configured as Enabled,

MC_HOME_LIMIT_SWITCH (1) homing will fail (Error ID:
MC_FB_ERR_PARAM).
For Homing against Lower Limit switch, one positive home offset can be
configured; for Homing against Upper Limit switch, one negative home offset
can be configured.
MC_HOME_LIMIT_SWITCH (1) homing procedure performs a homing

operation against Limit switch. The actual motion sequence is dependent on
the limit switch configuration and the actual status for the switch before
homing starts—that is, when the MC_Home function block is issued.
Scenario 1: Moving part at right (positive) side of Lower Limit switch before homing starts

1. Moving part moves to its left side (in negative direction);
2. When Lower Limit switch is detected, the moving part decelerates to
stop, or stops immediately, according to Limit Switch Hard Stop
configuration;
Lower Limit switch On→Off edge;
4. Once Lower Limit switch On→Off edge is detected, record the position as
for the axis through the Connected Components Workbench software.
Scenario 2: Moving part on Lower Limit switch before homing starts

velocity to detect Lower Limit switch On→Off edge;
2. Once Lower Limit switch On→Off edge is detected, record the position as
for the axis through the software.
drive or moving part fails to move. User needs to make sure the moving part is
at the proper location before homing starts.

MC_HOME_REF_WITH_ABS
IMPORTANT If Home switch or Ref Pulse is not configured as Enabled,

MC_HOME_REF_WITH_ABS (2) homing fails with Error ID:
MC_FB_ERR_PARAM.
MC_HOME_REF_WITH_ABS (2) homing procedure performs a homing

operation against Home switch, plus fine Ref Pulse signal. The actual motion
sequence is dependent on the home switch, limit switch configuration, and the
actual status for the switches before homing starts—that is, when the
MC_Home function block is issued.
Scenario 1: Moving part at right (positive) side of Home switch before homing starts

2. When Home Abs switch is detected, the moving part decelerates to stop;
Home Abs On→Off edge;
4. Once Home Abs switch On→Off is detected, start to detect first Ref Pulse
signal coming in;
5. Once the first Ref Pulse signal comes, record the position as mechanical
home position, and decelerate to stop;
Scenario 2: Moving part between Lower Limit and Home switch before homing starts

configuration;
Home switch On→Off edge;
signal;
home position, and decelerate to stop.
IMPORTANT In this case, if Lower limit switch is not configured, or not wired, the
homing motion will fail and moves continuously to the left until the drive
or moving part fails to move.
Scenario 3: Moving part on Lower Limit or Home switch before homing starts

velocity to detect Home switch On→Off edge;

signal;
home position, and decelerate to stop;
drive or moving part fails to move. User needs to make sure the moving part is
at the proper location before homing starts.
MC_HOME_REF_PULSE
IMPORTANT If Lower Limit switch or Ref Pulse is not configured as Enabled,

MC_HOME_REF_PULSE (3) homing fails (ErrorID: MC_FB_ERR_PARAM).
For Homing against Lower Limit switch, one positive home offset can be
configured; for Homing against Upper Limit switch, one negative home offset
can be configured.
MC_HOME_REF_PULSE (3) homing procedure performs a homing operation

against Limit switch, plus fine Ref Pulse signal. The actual motion sequence is
dependent on the limit switch configuration, and the actual status for the
switches before homing starts—that is, when the MC_Home function block is
issued.
Scenario 1: Moving part at right (positive) side of Lower Limit switch before homing starts

configuration;
Lower Limit switch On→Off edge;
4. Once Lower Limit switch On→Off edge is detected, start to detect first
Ref Pulse signal;
5. Once the first Ref Pulse signal comes, record the position as the
Scenario 2: Moving part on Lower Limit switch before homing starts

1. Moving part moves to its right side (in Positive direction) in creep
velocity to detect Lower Limit switch On→Off edge;

2. Once Lower Limit switch On→Off edge is detected, start to detect first
Ref Pulse signal;
3. Once the first Ref Pulse signal comes, record the position as the
drive or moving part fails to move. User needs to make sure the moving part at
the proper location before homing starts.
MC_HOME_DIRECT
MC_HOME_DIRECT (4) homing procedure performs a static homing by

directly forcing an actual position. No physical motion is performed in this
mode. This is equivalent to a MC_SetPosition action, except that Axis Homed
status will be on once MC_Home (mode = 4) is performed successfully.
Use PTO for PWM Control The example shows in you how to use a PTO axis as a PWM.
Launch Connected Components Workbench and create the following

ladder program.
Figure 12 - Example 1: PTO Axis as a PWM
1 Enable/power up the PWM axis immediately after going to RUN mode. PWM axis will remain powered ON (until Program mode, and so on).
MC_Power_1
__SYSVA_FIRST_SCAN MC_Power
EN ENO
PWM0 Axis Axis
TRUE Enable Status
TRUE Enable_Positive Busy
TRUE Enable_Negative Active
Error
ErrorID

2 Continually use MC_WriteParameter (Parameter 1005) to change the Duty Cycle from global variable G_PWM_Duty_Cycle (example: 0.5 => 50%)
Update_PWM_Duty_Cycle Update_PWM_Duty_Cycle
MC_WriteParameter_1
MC_WriteParameter
EN ENO
PWM0 AxisIn Axis
Update_PWM_Duty_Cycle Execute Done
1005 Parameter_Number Busy
G_PWM_Duty_Cycle Value Error
0 MC_ExecutionMode ErrorID
3
After first scan, use MC_MoveVelocity to continually set the PWM frequency (for example: 50,000 => 50 KHz) from global variable G_PWM_Frequency. PWM axis will run
forever (until Program Mode, MC_Halt, and so on).
MC_MoveVelocity_1
__SYSVA_FIRST_SCAN MC_MoveVelocity
EN ENO
PWM0 AxisIn Axis
TRUE Execut InVelocity
G_PWM_Frequency Velocity Busy
50000.0 Acceleration Active
50000.0 Acceleration Direction
0.0 Deceleration CommandAborted
1 Jerk Error
0 DirectionIn ErrorID

POU PWM_Program
The POU defines four variables.
Variable MC_Power_1 Variable MC_MoveVelocity_1

(* *) (* *)
Direction: VAR Direction: VAR
Data Type: MC_Power Data Type: MC_MoveVelocity
Attribute: ReadWrite Attribute: ReadWrite
Direct variable (Channel): Direct variable (Channel):
Variable Update_PWM_Duty_Cycle Variable MC_Power_1

(* *) (* *)
Direction: Var Direction: VAR
Data type: BOOL Data Type: MC_Power
Attribute: ReadWrite Attribute: ReadWrite
Direct variable (Channel): Direct variable (Channel):
HSC Feedback Axis From Connected Components Workbench software version 8.0 onwards,
support has been added for an HSC (High-Speed Counter) Feedback Axis that
uses the same instructions as the PTO Motion Axis. UDFBs are still supported.
You can use either one but you cannot select both for the same plug-in.
EXAMPLE: Example of Selecting Feedback Axis or UDFB with 2080-MOT-HSC Plug-in
The HSC Feedback Axis provides ease-of-use as you no longer need to program
the function blocks, and it also uses up less memory on the controller. The HSC
Feedback Axis uses only the administrative function blocks from the PTO
Motion Axis and they share the same Axis Monitor.
IMPORTANT The counters are not reset to zero for program download. For example, if
using the feedback axis, use the MC_ResetPosition function block to
reset the position to zero.
IMPORTANT If the feedback axis is in the error state because the configured position
limits have been exceeded, using the MC_Reset function block to reset
the axis may not clear the error as there may still be pulse detected from
the encoder.

Notes:

Chapter 9
Use the High-Speed Counter and Programmable

Limit Switch
High-Speed Counter All Micro830, Micro850, and Micro870 controllers, except for 2080-LCxx-AWB,
Overview support up to six high-speed counters (HSC). The HSC feature in Micro800
consists of two main components: the high-speed counter hardware
(embedded inputs in the controller), and high-speed counter instructions in
the application program. High-speed counter instructions apply configuration
to the high-speed counter hardware and updates the accumulator.
ATTENTION: To use the Micro800 HSC feature effectively, you need to

have a basic understanding of the following:
• HSC components and data elements.
The first sections of the chapter provides a detailed description of these
components. Quickstart instructions (see page 257) are also available to
guide you through setting up a sample HSC project.
• Programming and working with elements in Connected Components
Workbench software.
The user needs to have a working knowledge of programming through
ladder diagram, structured text, or function block diagram to be able to
work with the HSC function block and variables.
ATTENTION: Additional information is available on the HSC function block

and its elements in the Connected Components Workbench software
Online Help that comes with your Connected Components Workbench
software installation.
This chapter describes how to use the HSC function and also contains sections
on the HSC and HSC_ SET_STS function blocks, as follows:
• High Speed Counter (HSC) Data Structures
• High-Speed Counter (HSC) Function Block
• HSC_SET_STS Function Block
• Programmable Limit Switch (PLS) Function
• HSC Interrupts
Programmable Limit Switch The Programmable Limit Switch function allows you to configure the High-
Overview Speed Counter to operate as a PLS (Programmable Limit Switch) or rotary cam
switch. For more information, see Programmable Limit Switch (PLS) Function
on page 205.

Chapter 9 Use the High-Speed Counter and Programmable Limit Switch
What is High-Speed High-Speed Counter is used to detect narrow (fast) pulses, and its specialized
Counter? instructions to initiate other control operations based on counts reaching
preset values. These control operations include the automatic and immediate
execution of the high-speed counter interrupt routine and the immediate
update of outputs based on a source and mask pattern you set.
The HSC functions are different than most other controller instructions. Their
operation is performed by custom circuitry that runs in parallel with the main
system processor. This is necessary because of the high-performance
requirements of these functions.
Features and Operation
The HSC is extremely versatile; you can select or configure the master HSC for
any one of ten (10) modes and the sub HSC for any one of five (5) modes of
operation. See HSC Mode (HSCAPP.HSCMode) on page 189 for more
information.
Some of the enhanced capabilities of the High-Speed Counters are:

• 100 kHz operation
• Direct control of outputs
• 32-bit signed integer data (count range of ± 2,147,483,647)
• Programmable High and Low presets, and Overflow and Underflow set
points
• Automatic Interrupt processing based on accumulated count
• Change parameters on-the-fly (from the user control program)
The High-Speed Counter function operates as described in the following

diagram.
Figure 15 - High-Speed Counter Operation

Variable
HscAppData.OFSetting Overflow +2,147,483,647 maximum
HscAppData.HPSetting High Preset
HscAppData.LPSetting Low Preset
HscAppData.UFSetting Underflow -2,147,483,648 minimum
You must set a proper value for the variables OFSetting, HPSetting, and
UFSetting before triggering Start/Run HSC. Otherwise, the controller will
be faulted. (Setting a value for LPSetting is optional for certain counting
modes.)
To learn more about HscAppData variable input, see HSC APP Data
Structure on page 187.

When using HSC function blocks, it is recommended that you:

• Set HSCAppData underflow setting (UFSetting) and low preset setting
(LPSetting) to a value less than 0 to avoid possible HSC malfunction
when the HSC accumulator is reset to 0.
• Set HSCAppData overflow setting (OFSetting) and high preset setting
(HPSetting) to a value greater than 0 to avoid possible HSC malfunction
when the HSC accumulator is reset to 0.
In some cases, a sub counter will be disabled by master counter mode. For
more information, see HSC Mode (HSCAPP.HSCMode) on page 189.
HSC0 is used in this document to define how any HSC works.
IMPORTANT The HSC function can only be used with the controller’s embedded I/O.
It cannot be used with expansion I/O modules.
HSC Inputs and All Micro830, Micro850, and Micro870 controllers, except 2080-LCxx-xxAWB,
Wiring Mapping have 100 kHz high-speed counters. Each main high-speed counter has four
dedicated inputs and each sub high-speed counter has two dedicated inputs.
Table 24 - Micro830, Micro850, and Micro870 High Speed Counters

10/16-point 24-point 48-point
Number of HSC 2 4 6
Main high-speed counters 1 (counter 0) 2 (counter 0,2) 3 (counters 0, 2 and 4)
Sub high-speed counters 1 (counter 1) 2 (counter 1,3) 3 (counters 1, 3 and 5)
High-Speed Counter Inputs Used

HSC0 0, 1, 2, 3
HSC1 2, 3
HSC2 4, 5, 6, 7
HSC3 6, 7
HSC4 8, 9, 10, 11
HSC5 10, 11
HSC0's sub counter is HSC1, HSC2's sub counter is HSC3, and HSC4's sub
counter is HSC5. Each set of counters share the input. The following table
shows the dedicated inputs for the HSCs depending on the mode.
Table 25 - HSC Input Wiring Mapping
Embedded Input
0 01 02 03 04 05 06 07 08 09 10 11
HSC0 A/C B/D Reset Hold
HSC1 A/C B/D

Table 25 - HSC Input Wiring Mapping (Continued)

Embedded Input
0 01 02 03 04 05 06 07 08 09 10 11
HSC3 A/C B/D
HSC5 A/C B/D
The following tables show the input wiring mapping for the different
Micro830, Micro850, and Micro870 controllers.
Table 26 - Micro830 10 and 16-point Controller HSC Input Wiring Mapping
Mode Value in
Input 0 (HSC0) Input 1 (HSC0)
Modes of Operation Input 2 (HSC0) Input 3 (HSC0) User Program
Input 2 (HSC1) Input 3 (HSC1) (HSCAppData.HSCMode)
Counter with Internal Direction Count Up Not Used 0
(mode 1a)
Counter with Internal Direction,
Count Up Not Used Reset Hold 1
External Reset and Hold (mode 1b)
Counter with External Direction Count Up/Down Direction Not Used 2
(mode 2a)
Counter with External Direction, Count Direction Reset Hold 3
Reset, and Hold (mode 2b)
Two Input Counter (mode 3a) Count Up Count Down Not Used 4
Two Input Counter with External Count Up Count Down Reset Hold 5
Reset and Hold (mode 3b)
Quadrature Counter (mode 4a) A Type input B Type input Not Used 6
Quadrature Counter with External A Type input B Type input Z Type Reset Hold 7
Quadrature X4 Counter A Type input B Type input Not Used 8
(mode 5a)
Quadrature X4 Counter with External A Type input B Type input Z Type Reset Hold 9
Reset and Hold
Table 27 - Micro830/Micro850/Micro870 24-point Controller HSC Input Wiring Mapping

Input 0 (HSC0) Input 1 (HSC0) Input 3 (HSC0)
Input 2 (HSC1) Input 3 (HSC1) Input 2 (HSC0) Mode Value in User
Modes of Operation Input 7 (HSC2)
Input 4 (HSC2) Input 5 (HSC2) Input 6 (HSC2) Program
(mode 1a)
Counter with Internal Direction, Count Up Not Used Reset Hold 1
(mode 2a)
Counter with External Direction, Count Up/Down Direction Reset Hold 3

Table 27 - Micro830/Micro850/Micro870 24-point Controller HSC Input Wiring Mapping (Continued)

Input 0 (HSC0) Input 1 (HSC0) Input 3 (HSC0)
Input 2 (HSC1) Input 3 (HSC1) Input 2 (HSC0) Mode Value in User
Modes of Operation Input 7 (HSC2)
Input 4 (HSC2) Input 5 (HSC2) Input 6 (HSC2) Program
(mode 5a)
Quadrature X4 Counter with A Type input B Type input Z Type Reset Hold 9
External Reset and Hold
Table 28 - Micro830/Micro850 48-point Controller HSC Input Wiring Mapping

Input 2 (HSC1) Input 3 (HSC1) Input 2 (HSC0) Input 3 (HSC0)
Input 4 (HSC2) Input 5 (HSC2) Mode Value in User
Modes of Operation Input 6 (HSC2) Input 7 (HSC2)
Input 6 (HSC3) Input 7 (HSC3) Program
(mode 1a)
Counter with Internal Direction, Count Up Not Used Reset Hold 1
(mode 2a)
Counter with External Direction, Count Up/Down Direction Reset Hold 3
(mode 5a)
Quadrature X4 Counter with A Type input B Type input Z Type Reset Hold 9
External Reset and Hold
High Speed Counter (HSC) The following section describes HSC data structures.
Data Structures
HSC APP Data Structure
Define an HSC App Data (configuration data, data type HSCAPP) when
programming an HSC. During HSC counting, you should not change the data,
except if you need to reload the configuration.
To reload HSC configuration, change the HSC APP Data, then call HSC
function block with command 0x03 (set/reload). Otherwise, the change to HSC
App Data during HSC counting is ignored.

HSC1, HSC3, and HSC5 support mode 0, 2, 4, 6, and 8 only, and HSC0,
HSC2, and HSC4 support all counting modes.
PLS Enable (HSCAPP.PLSEnable)

Description Data Format User Program Access
PLSEnable bit read/write
This bit enables and disables the HSC Programmable Limit Switch (PLS)
function.
When the PLS function is enabled, the setting in

• HSCAPP.HpSetting
• HSCAPP.LpSetting
• HSCAPP.HPOutput
• HSCAPP.LPOutput
are superseded by corresponding data values from PLS data. See

Programmable Limit Switch (PLS) Function on page 205 for more
information.
HSCID (HSCAPP.HSCID)
HSCID Word (UINT) read/write
Table 29 lists the definition for HSCID.

Table 29 - HSCID Definition

Bits Description
HSC Module Type:
0x00: Embedded
15…13 0x01: Expansion (not yet implemented)
0x02: Plug-in module
Module Slot ID:
0x00: Embedded
12…8 0x01…0x1F: Expansion (not yet implemented)
0x01…0x05: Plug-in module
Module internal HSC ID:
0x00-0x0F: Embedded
7…0 0x00-0x07: Expansion (not yet implemented)
0x00-0x07: Plug-in module
For Embedded HSC, valid HSCID value is only 0…5.
HSC Mode (HSCAPP.HSCMode)

HSC Mode word (UINT) read/write
The HSCMode variable sets the High-Speed Counter to one of 10 types of

operation. This integer value is configured through the programming device
and is accessible in the control program.
HSC Operating Modes

Mode Type
Number
Up Counter – The accumulator is immediately cleared (0) when it reaches the high preset. A low
0 preset cannot be defined in this mode.
Up Counter with external reset and hold – The accumulator is immediately cleared (0) when it
1 reaches the high preset. A low preset cannot be defined in this mode.
2 Counter with external direction
3 Counter with external direction, reset, and hold
4 Two input counter (up and down)
5 Two input counter (up and down) with external reset and hold
6 Quadrature counter (phased inputs A and B)
7 Quadrature counter (phased inputs A and B) with external reset and hold
8 Quadrature X4 counter (phased inputs A and B)
9 Quadrature X4 counter (phased inputs A and B) with external reset and hold
The main high-speed counters support 10 types of operation mode and the sub
high-speed counters support 5 types (mode 0, 2, 4, 6, 8). If the main high-speed
counter is set to mode 1, 3, 5, 7 or 9, then the resub high-speed counter will be
disabled.
For more information on HSC Function Operating Modes and Input

Assignments, see HSC Inputs and Wiring Mapping on page 185.

HSC Mode 0 – Up Counter

Table 30 - HSC Mode 0 Examples
Input Terminals Embedded Input 0 Embedded Input 1 Embedded Input 2 Embedded Input 3 CE Bit Comments
Function Count Not Used Not Used Not Used
Example 1  on (1) HSC Accumulator + 1 count
Example 2  on (1) ß off (0) off (0) Hold accumulator value
Blank cells = don’t care, = rising edge,  = falling edge
Inputs 0…11 are available for use as inputs to other functions regardless
of the HSC being used.
HSC Mode 1 – Up Counter with External Reset and Hold

Function Count Not Used Reset Hold
Example 1  on (1)  off (0) off (0) on (1) HSC Accumulator + 1 count
Example 2 on (1)  off (0) on (1) Hold accumulator value
Example3 on (1)  off (0) off (0) Hold accumulator value
Example 4 on (1)  off (0) on (1)  off (0) Hold accumulator value
Example 5  Clear accumulator (=0)
HSC Mode 2 – Counter with External Direction

Function Count Direction Not Used Not Used
Example 1  off (0) on (1) HSC Accumulator + 1 count
Example 2  on (1) on (1) HSC Accumulator - 1 count
Example3 off (0) Hold accumulator value
HSC Mode 3 – Counter with External Direction, Reset, and Hold

Function Count Direction Reset Hold
Example 1  off (0) on (1)  off (0) off (0) on (1) HSC Accumulator + 1 count
Example 2  on (1) on (1)  off (0) off (0) on (1) HSC Accumulator - 1 count
Example3 on (1)  off (0) on (1) Hold accumulator value
Example 4 on (1)  off (0) off (0) Hold accumulator value

Inputs 0…11 are available for use as inputs to other functions

regardless of the HSC being used.
HSC Mode 4 – Two Input Counter (up and down)

Function Count Up Count Down Not Used Not Used
Example 1  on (1)  off (0) on (1) HSC Accumulator + 1 count
Example 2 on (1)  off (0)  on (1) HSC Accumulator - 1 count
Blank cells = don’t care,  = rising edge,  = falling edge
Inputs 0 through 11 are available for use as inputs to other functions regardless of the HSC being used.
HSC Mode 5 – Two Input Counter (up and down) with External Reset and Hold
Function Count Direction Reset Hold
Example 1  on (1)  off (0) on (1)  off (0) off (0) on (1) HSC Accumulator + 1 count
Example 2 on (1)  off (0)  on (1)  off (0) off (0) on (1) HSC Accumulator - 1 count
Example3 on (1)  off (0) on (1) Hold accumulator value
Example 4 on (1)  off (0) off (0) Hold accumulator value
Inputs 0…11 are available for use as inputs to other functions regardless of the HSC being used.
Using the Quadrature Encoder
The Quadrature Encoder is used for determining direction of rotation and

position for rotating, such as a lathe. The Bidirectional Counter counts the
rotation of the Quadrature Encoder.
Figure 16 shows a quadrature encoder connected to inputs 0, 1, and 2. The

count direction is determined by the phase angle between A and B. If A leads B,
the counter increments. If B leads A, the counter decrements.
The counter can be reset using the Z input. The Z outputs from the encoders
typically provide one pulse per revolution.

Figure 16 - Quadrature Encoder Connected to Inputs
A
A Input 0
Input 0
B
Input 1
Z
Input 2
Reset
Quadrature Encoder Input 1
B
Forward Rotation Reverse Rotation
B
1 2 3 2 1
Count
HSC Mode 6 – Quadrature Counter – Phased Inputs A and B

Function Count A Count B Not Used Not Used
Example 1(1)  off (0) on (1) HSC Accumulator + 1 count
Example 2(2) ß off (0) on (1) HSC Accumulator - 1 count
Example 4 on (1) Hold accumulator value
Example 6 off (0) Hold accumulator value
(1) Count input A leads count input B.
(2) Count input B leads count input A.
HSC Mode 7 – Quadrature Counter – Phased Inputs A and B with External Reset and Hold
Function Count A Count B Z reset Hold
Example 1(1)  off (0) off (0) on (1) HSC Accumulator + 1 count
Example 2(2) ß off (0) off (0) off (0) on (1) HSC Accumulator - 1 count
Example3 ß off (0) off (0) on (1) Reset accumulator to zero
Example 6 off (0) on (1) Hold accumulator value
Example 7 off (0) off (0) Hold accumulator value
(1) Count input A leads count input B.
(2) Count input B leads count input A. Blank cells = don’t care, = rising edge, = falling edge

HSC Mode 8 – Quadrature X4 Counter

Embedded Input 1(HSC0) (A) Embedded Input 1(HSC0) (B) Value of CE Bit Accumulator and Counter Action
 OFF TRUE Count Up Acc. Value
 ON TRUE Count Down Acc. Value
 OFF TRUE Count Down Acc. Value
 ON TRUE Count Up Acc. Value
OFF  TRUE Count Down Acc. Value
ON  TRUE Count Up Acc. Value
OFF  TRUE Count Up Acc. Value
ON  TRUE Count Down Acc. Value
OFF or ON OFF or ON X Hold Acc. Value
X X FALSE Hold Acc. Value
HSC Mode 9 – Quadrature X4 Counter with External Reset and Hold

Embedded Input Embedded Input Embedded Input Embedded Input Value of CE Bit Accumulator and Counter Action
0(HSC0) (A)) 1(HSC0) (B) 2(HSC0) (Reset) 3(HSC0) (Hold)
 OFF X - TRUE Count Up Acc. Value
 ON X - TRUE Count Down Acc. Value
 OFF X - TRUE Count Down Acc. Value
 ON X - TRUE Count Up Acc. Value
OFF  X - TRUE Count Down Acc. Value
ON  X - TRUE Count Up Acc. Value
OFF  X - TRUE Count Up Acc. Value
ON  X - TRUE Count Down Acc. Value
OFF or ON OFF or ON OFF X X Hold Acc. Value
OFF OFF ON X X Reset Acc. to Zero
X X OFF ON X Hold Acc. Value
X X OFF X FALSE Hold Acc. Value
Accumulator (HSCAPP. Accumulator)

HSCAPP.Accumulator long word (32-bit INT) read/write
This parameter is the initial HSC Accumulator value that need to be set when
starting the HSC. This parameter is updated by the HSC sub-system
automatically when the HSC is in Counting mode, reflecting the actual HSC
accumulator value.
High Preset (HSCAPP.HPSetting)

HSCAPP.HPSetting long word (32-bit INT) read/write

The HSCAPP.HPSetting is the upper setpoint (in counts) that defines when the
HSC sub-system generates an interrupt.
The data loaded into the high preset must be less than to the data resident in
the overflow (HSCAPP.OFSetting) parameter or an HSC error is generated.
Low Preset (HSCAPP.LPSetting)

HSCAPP.LPSetting long word (32-bit INT) read/write
The HSCAPP.LPSetting is the lower setpoint (in counts) that defines when the
HSC sub-system generates an interrupt.
The data loaded into the low preset must be:

1. Less than or equal to 0 for HSC Mode (HSCAPP.HSCMode) parameter
values 0 and 1 or an HSC error is generated.
2. Greater than or equal to the data resident in the underflow
(HSCAPP.UFSetting) parameter for all HSC Mode (HSCAPP.HSCMode)
or an HSC error is generated.
If the underflow and low preset values are negative numbers, the low preset
must be a number with a smaller absolute value.
Overflow Setting (HSCAPP.OFSetting)

Description Data Format Type User Program Access
HSCAPP.OFSetting long word (32-bit INT) control read/write
The HSCAPP.OFSetting defines the upper count limit for the counter. If the
counter’s accumulated value increments past the value specified in this
variable, an overflow interrupt is generated. When the overflow interrupt is
generated, the HSC sub-system rolls the accumulator over to the underflow
value and the counter continues counting from the underflow value (counts
are not lost in this transition). The user can specify any value for the overflow
position, provided it is greater than the underflow value and falls between
-2,147,483,648 and 2,147,483,647.
Data loaded into the overflow variable must be greater than the data
resident in the high preset (HSCAPP.HPSetting) or an HSC error is
generated.
Underflow Setting (HSCAPP.UFSetting)

HSCAPP.UFSetting long word (32-bit INT) read/write
The HSCAPP.UFSetting defines the lower count limit for the counter. If the
counter’s accumulated value decrements past the value specified in this
variable, an underflow interrupt is generated. When the underflow interrupt is
generated, the HSC sub-system resets the accumulated value to the overflow
value and the counter then begins counting from the overflow value (counts
are not lost in this transition). The user can specify any value for the underflow
position, provided it is less than the overflow value and falls between
-2,147,483,648 and 2,147,483,647.

Data loaded into the underflow variable must be less than or equal to
the data resident in the low preset (HSCAPP.LPSetting) or an HSC error
is generated.
Output Mask Bits (HSCAPP.OutputMask)

HSCAPP.OutputMask word (32 bit binary) read/write
The HSCAPP.OutputMask defines which embedded outputs on the controller

can be directly controlled by the high-speed counter. The HSC sub-system has
the ability to directly (without control program interaction) turn outputs ON
or OFF based on the HSC accumulator reaching the High or Low presets. The
bit pattern stored in the HSCAPP.OutputMask variable defines which outputs
are controlled by the HSC and which outputs are not controlled by the HSC.
For example, if the user wants to control outputs 0, 1, 3, using HSC then the
user needs to assign,
HscAppData.OutputMask = 2#1011
(OR using Decimal Value: HscAppData.OutputMask = 11)
The bit pattern of the HSCAPP.OutputMask variable directly corresponds to

the output bits on the controller. Bits that are set (1) are enabled and can be
turned on or off by the HSC sub-system. Bits that are clear (0) cannot be
turned on or off by the HSC sub-system. The mask bit pattern can be
configured only during initial setup.
Table 40 shows example of how HPOutput and OutputMask controls

Embedded output.
Table 40 - Effect of HSC Output Mask on Embedded Outputs
Output Variable 32-Bit Signed Integer Data Word
32…20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
HSCAPP.HPOutput (high 0 1 0 1 0 1 0 1 0 0 1 1 0 0 0 1 1 0 0 1
preset output)
HSCAPP.OutputMask (output
1 1 0 0 0 0 0 0 0 1 1 0 0 0 1 1 0 0 1 1
mask)
Embedded output (10-point) 0 1
Embedded output (16-point) 0 1 0 1
Embedded output (24-point) 1 0 1 0 1
Embedded output (48-point) 0 1 0 1 0 1 0 1
The outputs shown in the black boxes are the outputs under the control of the
HSC sub-system. The mask defines which outputs can be controlled. The high
preset output or low preset output values (HSCAPP.HPOutput or
HSCAPP.LPOutput) define if each output is either ON (1) or OFF (0). Another
way to view this is that the high or low preset output is written through the
output mask, with the output mask acting like a filter.

The bits in the gray boxes are unused. For the 10-point controller, the first 4
bits of the mask word are used and the remaining mask bits are not functional
because they do not correlate to any physical outputs on the base unit. For the
16, 24 and 48-point controllers, the first 6, 10 and 20 bits of the mask word are
used, respectively.
The mask bit pattern can be configured only during initial setup.
High Preset Output (HSCAPP.HPOutput)

HSCAPP.HPOutput long word (32 bit binary) read/write
The High Preset Output defines the state (1 = ON or 0 = OFF) of the outputs on
the controller when the high preset is reached. For more information on how
to directly turn outputs on or off based on the high preset being reached, see
Output Mask Bits (HSCAPP.OutputMask) on page 195.
The high output bit pattern can be configured during initial setup, or while the
controller is operating. Use the HSC function block to load the new parameters
while the controller is operating.
Low Preset Output (HSCAPP.LPOutput)

HSCAPP.LPOutput long word (32 bit binary) read/write
The Low Preset Output defines the state (1 = “on”, 0 = “off”) of the outputs on
the controller when the low preset is reached. See Output Mask Bits
(HSCAPP.OutputMask) on page 195 for more information on how to directly
turn outputs on or off based on the low preset being reached.
The low output bit pattern can be configured during initial setup, or while the
controller is operating. Use the HSC function block to load the new parameters
while the controller is operating.
HSC STS (HSC Status) Data Define an HSC STS data (HSC status information data, data type HSCSTS)
Structure when programming an HSC.

Counting Enabled (HSCSTS.CountEnable)

Description Data Format HSC Modes(1) User Program Access
HSCSTS.CountEnable bit 0…9 read only
(1) For Mode descriptions, see HSC Mode (HSCAPP.HSCMode) on page 189.
The Counting Enabled control bit is used to indicate the status of the High-
Speed Counter, whether counting is enabled (1) or disabled (0, default).
Error Detected (HSCSTS.ErrorDetected)

HSCSTS.ErrorDetected bit 0…9 read/write
The Error Detected flag is a status bit that can be used in the control program
to detect if an error is present in the HSC sub-system. The most common type
of error that this bit represents is a configuration error. When this bit is set (1),
you should look at the specific error code in parameter HSCSTS.ErrorCode.
This bit is maintained by the controller and is set when there is an HSC error.
This bit can be cleared by the user, if necessary.
Count Up (HSCSTS.CountUpFlag)
HSCSTS.CountUpFlag bit 0…9 read only
The Count Up bit is used with all of the HSCs (modes 0…9). If the
HSCSTS.CountEnable bit is set, the Count Up bit is set (1). If the
HSCSTS.CountEnable is cleared, the Count Up bit is cleared (0).
Count Down (HSCSTS.CountDownFlag)

SCSTS.CountDownFlag bit 2…9 read only

The Count Down bit is used with the bidirectional counters (modes 2…9). If the
HSCSTS.CountEnable bit is set, the Count Down bit is set (1). If the
HSCSTS.CountEnable bit is clear, the Count Down bit is cleared (0).
Mode Done (HSCSTS.Mode1Done)

HSCSTS.Mode1Done bit 0 or 1 read/write
The Mode Done status flag is set (1) by the HSC sub-system when the HSC is
configured for Mode 0 or Mode 1 behavior, and the accumulator counts up to
the High Preset.
Overflow (HSCSTS.OVF)
HSCSTS.OVF bit 0…9 read/write
The HSCSTS.OVF status flag is set (1) by the HSC sub-system whenever the
accumulated value (HSCSTS.Accumulator) has counted through the overflow
variable (HSCAPP.OFSetting).
This bit is transitional and is set by the HSC sub-system. It is up to the control
program to utilize, track if necessary, and clear (0) the overflow condition.
Overflow conditions do not generate a controller fault.
Underflow (HSCSTS.UNF)
HSCSTS.UNF bit 0…9 read/write
The Underflow status flag is set (1) by the HSC sub-system whenever the
accumulated value (HSCSTS.Accumulator) has counted through the underflow
variable (HSCAPP.UFSetting).
This bit is transitional and is set by the HSC sub-system. It is up to the control
program to utilize, track if necessary, and clear (0) the underflow condition.
Underflow conditions do not generate a controller fault.
Count Direction (HSCSTS.CountDir)

HSCSTS.CountDir bit 0…9 read only
The Count Direction status flag is controlled by the HSC sub-system. When the
HSC accumulator counts up, the direction flag is set (1). Whenever the HSC
accumulator counts down, the direction flag is cleared (0).
If the accumulated value stops, the direction bit retains its value. The only time
the direction flag changes is when the accumulated count reverses.

This bit is updated continuously by the HSC sub-system whenever the

controller is in a run mode.
High Preset Reached (HSCSTS.HPReached)

HSCSTS.HPReached bit 2…9 read/write
(1) For Mode descriptions, see Count Down (HSCSTS.CountDownFlag) on page 197.
The High Preset Reached status flag is set (1) by the HSC sub-system whenever
the accumulated value (HSCSTS.Accumulator) is greater than or equal to the
high preset variable (HSCAPP.HPSetting).

controller is in an executing mode. Writing to this element is not
recommended.
Low Preset Reached (HSCSTS.LPReached)

HSCSTS.LPReached) bit 2…9 read only
The Low Preset Reached status flag is set (1) by the HSC sub-system whenever
the accumulated value (HSCSTS.Accumulator is less than or equal to the low
preset variable HSCAPP.LPSetting).

controller is in an executing mode. Writing to this element is not
recommended.
Overflow Interrupt (HSCSTS.OFCauseInter)

HSCSTS.OFCauseInter bit 0…9 read/write
The Overflow Interrupt status bit is set (1) when the HSC accumulator counts
through the overflow value and the HSC interrupt is triggered. This bit can be
used in the control program to identify that the overflow variable caused the
HSC interrupt. If the control program needs to perform any specific control
action based on the overflow, this bit is used as conditional logic.
This bit can be cleared (0) by the control program and is also cleared by the
HSC sub-system whenever these conditions are detected:
• Low Preset Interrupt executes
• High Preset Interrupt executes
• Underflow Interrupt executes
Underflow Interrupt (HSCSTS.UFCauseInter)
HSCSTS.UFCauseInter bit 2…9 read/write
The Underflow Interrupt status bit is set (1) when the HSC accumulator counts
through the underflow value and the HSC interrupt is triggered. This bit can

be used in the control program to identify that the underflow condition caused
the HSC interrupt. If the control program needs to perform any specific
control action based on the underflow, this bit is used as conditional logic.
• Low Preset Interrupt occurs
• High Preset Interrupt occurs
• Overflow Interrupt occurs
High Preset Interrupt (HSCSTS.HPCauseInter)
HSCSTS.HPCauseInter bit 0…9 read/write
The High Preset Interrupt status bit is set (1) when the HSC accumulator
reaches the high preset value and the HSC interrupt is triggered. This bit can
be used in the control program to identify that the high preset condition
caused the HSC interrupt. If the control program needs to perform any
specific control action based on the high preset, this bit is used as conditional
logic.
• Low Preset Interrupt occurs
• Underflow Interrupt occurs
Low Preset Interrupt (HSCSTS.LPCauseInter)
HSCSTS.LPCauseInter bit 2…9 read/write
The Low Preset Interrupt status bit is set (1) when the HSC accumulator
reaches the low preset value and the HSC interrupt has been triggered. This bit
can be used in the control program to identify that the low preset condition
caused the HSC interrupt. If the control program needs to perform any
specific control action based on the low preset, this bit would be used as
conditional logic.
This bit can be cleared (0) by the control program and is also be cleared by the
• High Preset Interrupt occurs
• Underflow Interrupt occurs
Programmable Limit Switch Position (HSCSTS.PLSPosition)
HSCSTS.PLSPosition Word (INT) 0…9 read only

When the HSC is in Counting mode, and PLS is enabled, this parameter
indicates which PLS element is used for the current HSC configuration.
Error Code (HSCSTS.ErrorCode)

HSCSTS.ErrorCode Word (INT) 0…9 read only
The Error Codes detected by the HSC sub-system are displayed in this word.
Errors include:
HSC Counting Error

Error Code Sub-element Error Description
Code
The non-zero value for high byte indicates that the HSC
Bit 15…8 (high byte) 0…255 error is due to PLS data setting. The value of high byte
indicates which element of PLS data triggers the error.
0x00 No error
0x01 Invalid HSC counting mode
0x02 Invalid High preset
Bit 7…0 (low byte)
0x03 Invalid overflow
0x04 Invalid underflow
0x05 No PLS data
Writing to this element is not recommended except for clearing existing errors
and to capture new HSC errors.
Accumulator (HSCSTS.Accumulator)
HSCSTS.Accumulator long word (32-bit INT) read only
HSCSTS.Accumulator contains the number of counts detected by the HSC

sub-system. If either mode 0 or mode 1 is configured, the accumulator is reset
to 0 when a high preset is reached or when an overflow condition is detected.
High Preset (HSCSTS.HP)

HSCSTS.HP long word (32-bit INT) read only
The HSCSTS.HP is the upper set point (in counts) that defines when the HSC
sub-system generates an interrupt.
The data loaded into the high preset must be less than or equal to the data
resident in the overflow (HSCAPP.OFSetting) parameter or an HSC error is
generated.
This is the latest high preset setting, which may be updated by PLS function
from the PLS data block.
Low Preset (HSCSTS.LP)

HSCSTS.LP long word (32-bit INT) read only
The HSCSTS.LP is the lower set point (in counts) that defines when the HSC
sub-system generates an interrupt.

The data loaded into the low preset must greater than or equal to the data
resident in the underflow (HSCAPP.UFSetting) parameter, or an HSC error is
generated. If the underflow and low preset values are negative numbers, the
low preset must be a number with a smaller absolute value.
This is the latest low preset setting, which may be updated by PLS function
from the PLS data block.
High Preset Output (HSCSTS.HPOutput)

HSCSTS.HPOutput long word (32 bit binary) read only
The High Preset Output defines the state (1 = ON or 0 = OFF) of the outputs on
the controller when the high preset is reached. See Output Mask Bits
turn outputs on or off based on the high preset being reached.
This is the latest high preset output setting, which may be updated by PLS
function from the PLS data block.
Low Preset Output (HSCSTS.LPOutput)

HSCSTS.LPOutput long word (32 bit binary)) read only
The Low Preset Output defines the state (1 = “on”, 0 = “off”) of the outputs on
the controller when the low preset is reached. See Output Mask Bits
turn outputs on or off based on the low preset being reached.
This is the latest low preset output setting, which may be updated by PLS
function from the PLS data block.
High-Speed Counter (HSC) The HSC function block can be used to start/stop HSC counting, to refresh
Function Block HSC status, to reload HSC setting, and to reset HSC accumulator.
HSC
Enable STS
HscCmd
HscAppData
HscStsInfo
PlsData
Table 41 - HSC Parameters

Parameter Parameter Type Data Type Parameter Description
Enable function block.
Enable Input BOOL When Enable = TRUE, perform the HSC operation specified in “HSC command” parameter.
When Enable = FALSE, there is no HSC operation, and no HSC status update.
HscCmd Input USINT See HSC Commands on page 203
See HSC APP Data Structure on page
HscAppData Input HSC application configuration. Only initial configuration is needed usually.
187

Table 41 - HSC Parameters (Continued)

Parameter Parameter Type Data Type Parameter Description
See array of Programmable Limit
PlsData Input Programmable Limit Switch (PLS) Data
Switch (PLS) Function on page 205
See HSC STS (HSC Status) Data
HscStsInfo Output HSC dynamic status. Status info is usualy continuously updated during HSC counting.
Structure on page 196
Sts Output UINT HSC function block execution status
HSC Commands (HScCmd)
HscCmd is an input parameter with data type USINT. All HSC commands
(1…4) are Level commands. Users are advised to disable the instruction before
updating the command.
HscCmd = 1 starts the HSC mechanism. Once the HSC is in running mode, the
HscCmd = 2 must be issued to stop counting. Setting the Enable input
parameter to False does not stop counting while in running mode.
HscCmd = 3 reloads the following parameter values: HighPreset, LowPreset,

OverFlow, UnderFlow, HighPreset Output, and LowPreset Output.
The parameter values shown in the Variable Monitor may not match the values
in the Hardware. Command 3 must be executed to load the values from the
variables to the hardware without stopping the HSC.
If the HSC Enable is True, HscCmd = 3 will continuously load the parameters.
Trigger HscCmd = 3 only once.
HscCmd = 4 (reset) sets the Acc value to the HSC AppData.Accumalator value.
The HscCmd =4 does not stop HSC counting. If HSC is counting when the
HscCmd =4 is issued, some counting may be lost.
To reset the Acc value and then continue the counting, trigger the HscCmd =4
only once. If the command is enabled continuously, it may cause errors.
HSC AppData.Accumalator value is updated automatically by the HSC

mechanism with the same value as the HSC Sts.Accumulator. To set one
specific value to HSC Acc while counting, write the value to HSC
AppData.Accumalator immediately before HscCmd =4 is issued.
Table 42 - HSC Commands

HSC Command Description
0x00 Reserved
HSC RUN
• Start HSC (if HSC in Idle mode and Rung is Enabled)
0x01
• Update HSC Status Info only (if HSC already in RUN mode and Rung is Enabled)
• Update HSC status Info only (if Rung is disabled)

Table 42 - HSC Commands (Continued)

HSC Command Description
0x02 HSC Stop: Stop an HSC counting (if HSC is in RUN mode and Rung is Enabled.)
HSC Load: reload HSC Configuration (if Rung is Enabled) for 6 input elements:
0x03 HPSetting, LPSetting, HPOutput, LPOutput, OFSetting, and UFSetting. HSC accumulator
is NOT reloaded by cmd = 0x03.
HSC Reset: set Accumulator to assigned value, and reset HSC status information (if
0x04 Rung is Enabled)
Table 43 - HSC Function Block Status Codes

HSC Status Code Description
0x00 No action from Controller because the function block is not enabled
0x01 HSC function block successfully executed
0x02 HSC command invalid
0x03 HSC ID out of range
0x04 HSC Configuration Error
HSC_SET_STS Function
Block HSC
Enable STS
HscId
Mode1Done
HPReached
LPReached
OFOccured
UFOccured
The HSC Set Status function block can be used to change the HSC counting
status. This function block is called when the HSC is not counting (stopped).
Table 44 - HSC Parameters

Parameter
Parameter Data Type Parameter Description
Type
Enable function block.
Enable Input BOOL When Enable = TRUE, set/reset the HSC status.
When Enable = FALSE, there is no HSC status change.
See HSC APP Data
HscId Input Structure on page Describes which HSC status to set.
187
Mode1Done Input BOOL Mode 1A or 1B counting is done.
High Preset reached.
HPReached Input BOOL This bit can be reset to FALSE when HSC is not counting.
Low Preset reached.
LPReached Input BOOL This bit can be reset to FALSE when HSC is not counting.

Table 44 - HSC Parameters (Continued)

Parameter
Parameter Data Type Parameter Description
Type
Overflow occurred.
OFOccurred Input BOOL This bit can be reset to FALSE when necessary.
Underflow occurred.
UFOccurred Input BOOL This bit can be reset to FALSE when necessary.
HSC function block execution status
Refer to HSC Function Block Status Codes on page 204
Sts Output UINT for HSC status code description (except 0x02 and
0x04).
Programmable Limit Switch The Programmable Limit Switch function allows you to configure the High-
(PLS) Function Speed Counter to operate as a PLS (programmable limit switch) or rotary cam
switch.
When PLS operation is enabled (HSCAPP.PLSEnable = True), the HSC (High-

Speed Counter) uses PLS data for limit/cam positions. Each limit/cam position
has corresponding data parameters that are used to set or clear physical
outputs on the controller’s base unit. The PLS data block is illustrated in
Figure 17 on page 206.
IMPORTANT The PLS Function only operates in tandem with the HSC of a Micro830
controller. To use the PLS function, an HSC must first be configured.
PLS Data Structure
The Programmable Limit Switch function is an additional set of operating

modes for the High-Speed Counter. When operating in these modes, the
preset and output data values are updated using user supplied data each time
one of the presets is reached. These modes are programmed by providing a PLS
data block that contains the data sets to be used.
PLS data structure is a flexible array, with each element defined as follows,
Element Order Data Type Element Description

Word 0…1 DINT High preset setting
Word 2…3 DINT Low preset setting
Word 4…5 UDINT High preset Output data
Word 6…7 UDINT Low preset Output data
The total number of elements for one PLS data cannot be larger than 255.
When PLS is not enabled, PLS data are still required to be defined, but can be
not initialized.

Figure 17 - PLS Data Block
PLS Operation
When the PLS function is enabled, and the controller is in the run mode, the
HSC counts incoming pulses. When the count reaches the first preset (HSCHP
or HSCLP) defined in the PLS data, the output source data (HSCHPOutput or
HSCLPOutput) is written through the HSC mask (HSCAPP.OutputMask).
At that point, the next presets (HSCHP and HSCLP) defined in the PLS data
become active.
When the HSC counts to that new preset, the new output data is written
through the HSC mask. This process continues until the last element within
the PLS data block is loaded. At that point, the active element within the PLS
data block is reset to zero. This behavior is referred to as circular operation.
The HSCHPOutput is only written when HSCHP is reached. The

HSCLPOutput is written when HSCLP is reached.
Output High Data is only operational when the counter is counting up.
Output Low Data is only operational when the counter is counting
down.
If invalid data is loaded during operation, an HSC error is generated and

causes a controller fault.
You can use the PLS in Up (high), Down (low), or both directions. If your
application only counts in one direction, ignore the other parameters.
The PLS function can operate with all of the other HSC capabilities. The ability
to select which HSC events generate a user interrupt are not limited.

PLS Example
Setting Up the PLS Data
Using Connected Components Workbench software, define the PLS data

HSC_PLS’s dimension as [1…4].
PLS Data Definition

Data Description Data Format
HSCHP High Preset
32 bit signed integer
HSCLP Low Preset
HSCHPOutput Output High Data 32 bit binary
HSCLPOutput Output Low Data (bit 31--> 0000 0000 0000 0000 0000 0000 0000 0000 <--bit 0)
Once the values above for all 4 PLS data elements have been entered, the PLS is
configured.
Assume that HSCAPP.OutputMask = 31 (HSC mechanism controls Embedded

Output 0...4 only), and HSCAPP.HSCMode = 0.
PLS Operation for This Example
When the ladder logic first runs, HSCSTS.Accumulator = 1, therefore all the
outputs are turned off. The value of HSCSTS.HP = 250
When HSCSTS.Accumulator = 250, the HSC_PLS[1].HscHPOutput is sent

through the HSCAPP.OutputMask and energizes the outputs 0 and 1.
This will repeat as the HSCSTS.Accumulator reaches 500, 750, and 1000. The
controller energizes outputs 0...2, 0...3, and 0...4 respectively. Once completed,
the cycle resets and repeats from HSCSTS.HP = 250.
HSC Interrupts An interrupt is an event that causes the controller to suspend the task it is
currently performing, perform a different task, and then return to the
suspended task at the point where it suspended. Micro800 supports up to six
HSC interrupts.
An HSC interrupt is a mechanism that Micro830, Micro850, and Micro870

controllers provide to execute selected user logic at a pre-configured event.
HSC0 is used in this document to define how HSC interrupts work.
HSC Interrupt Configuration
In the User Interrupt configuration window, select HSC, and HSC ID, which is
the interrupt triggering the User Interrupt.
Figure 18 shows the selectable fields in the Interrupt configuration window.
Figure 18 - Interrupt Configuration Window

HSC Interrupt POU
This is the name of the Program Organizational Unit (POU) which is executed
immediately when this HSC Interrupt occurs. You can choose any pre-
programmed POU from the drop-down list.
Auto Start (HSC0.AS)

AS - Auto Start bit 0…9 read only
The Auto Start is configured with the programming device and stored as part
of the user program. The auto start bit defines if the HSC interrupt function
automatically starts whenever the controller enters any run or test mode.
Mask for IV (HSC0.MV)

MV - Overflow Mask bit 0…9 read only
The MV (Overflow Mask) control bit is used to enable (allow) or disable (not
allow) an overflow interrupt from occurring. If this bit is clear (0), and an
overflow reached condition is detected by the HSC, the HSC user interrupt is
not executed.
This bit is controlled by the user program and retains its value through a power
cycle. It is up to the user program to set and clear this bit.
Mask for IN (HSC0.MN)

MN - Underflow Mask bit 2…9 read only
The MN (Underflow Mask) control bit is used to enable (allow) or disable (not
allow) a underflow interrupt from occurring. If this bit is clear (0), and a
Underflow Reached condition is detected by the HSC, the HSC user interrupt
is not executed.
Mask for IH (HSC0.MH)

MH - High Preset Mask bit 0…9 read only
The MH (High Preset Mask) control bit is used to enable (allow) or disable (not
allow) a high preset interrupt from occurring. If this bit is clear (0), and a High
Preset Reached condition is detected by the HSC, the HSC user interrupt is not
executed.

Mask for IL (HSC0.ML)

ML - Low Preset Mask bit 2…9 read only
The ML (Low Preset Mask) control bit is used to enable (allow) or disable (not
allow) a low preset interrupt from occurring. If this bit is clear (0), and a Low
Preset Reached condition is detected by the HSC, the HSC user interrupt is not
executed.
HSC Interrupt Status

Information User Interrupt Enable (HSC0.Enabled)
HSC0.Enabled bit 0…9 read only
The Enabled bit is used to indicate HSC interrupt enable or disable status.
User Interrupt Executing (HSC0.EX)

HSC0.EX bit 0…9 read only
The EX (User Interrupt Executing) bit is set (1) whenever the HSC sub-system
begins processing the HSC subroutine due to any of the following conditions:
• Low preset reached
• High preset reached
• Overflow condition – count up through the overflow value
• Underflow condition – count down through the underflow value
The HSC EX bit can be used in the control program as conditional logic to
detect if an HSC interrupt is executing.
The HSC sub-system will clear (0) the EX bit when the controller completes its
processing of the HSC subroutine.
User Interrupt Pending (HSC0.PE)

HSC0.PE bit 0…9 read only
The PE (User Interrupt Pending) is a status flag that represents an interrupt is

pending. This status bit can be monitored or used for logic purposes in the
control program if you need to determine when a subroutine cannot be
executed immediately. This bit is maintained by the controller and is set and
cleared automatically.

User Interrupt Lost (HSC0.LS)

HSC0.LS bit 0…9 read/write
The LS (User Interrupt Lost) is a status flag that represents an interrupt has
been lost. The controller can process 1 active and maintain up to 1 pending user
interrupt conditions before it sets the lost bit.
This bit is set by the controller. It is up to the control program to utilize, track
the lost condition if necessary.

Notes:

Chapter 10
Controller Security
Micro800 security generally has two components:

• Exclusive Access that prevents simultaneous configuration of the
controller by two users
• Controller Password Protection that secures the Intellectual Property
contained within the controller and prevents unauthorized access
Protected Mode To maintain the secure operation of your Micro800 controllers, operations
that can disrupt controller operation are restricted based on the controller
operating mode.
Table 45 - Protected Operations on Micro800 Controllers
Activity
Ethernet Port
Configuration
Current Controller Setting(1) (through Serial and USB
Firmware Update
Port Configuration Lost Password Password Change Controller
Operation Mode I/O Configuration
Request Connected Recovery Change Change
Components Changes
Workbench or
RSLinx)
Controller in Accepted Not Allowed Accepted Not Allowed
Program Mode
Controller with
Password Protected Rejected Not Allowed(2) Not Allowed Rejected Rejected Rejected Not Allowed
in Run Mode
Controller in Hard
Rejected Not Allowed Not Allowed Rejected Rejected Rejected Not Allowed
Run Mode(3)
(1) Ethernet configuration includes IP address, subnet mask, gateway, port speed/duplex and so on.
(2) Difference between Not Allowed and Rejected is that Not Allowed activities can only be done during offline while Rejected activities can be performed but do not take effect.
(3) Hard Run Mode can only be in Micro830, Micro850 and Micro870 controllers with Mode switch to RUN.
Exclusive Access Exclusive access is enforced on the Micro800 controller regardless of whether
the controller is password-protected or not. This means that only one
Connected Components Workbench software session is authorized at one
time and only an authorized client has exclusive access to the controller
application. This ensures that only one software session has exclusive access to
the Micro800 application-specific configuration.
Exclusive access is enforced on Micro800 firmware revision 1 and 2. When a

Connected Components Workbench software user connects to a Micro800
controller, the controller is given exclusive access to that controller.

Chapter 10 Controller Security
Password Protection By setting a password on the controller, a user effectively restricts access to the
programming software connections to the controller to software sessions that
can supply the correct password. Essentially, Connected Components
Workbench software operation such as upload and download are prevented if
the controller is secured with a password and the correct password is not
provided.
Micro800 controllers with firmware revision 2 and later are shipped with no
password but a password can be set through the Connected Components
Workbench software (version 2 or later).
In Connected Components Workbench software version 10 or later, a stronger

password algorithm is introduced to provide better security. To take full
advantage of this enhancement, the Micro800 controller must have firmware
revision 10 or later, and the project must also be software version 10 or later.
In Connected Components Workbench software version 20.01.00 or later, the

password algorithm is further enhanced to increase the password encryption
on the new Micro850 (2080-L50E) and Micro870 (2080-L70E) controllers.
When the password is changed, or removed and restored back in the
controller, the encrypted code in the controller is different. Therefore the
backup copy of the program in the 2080-MEMBAK-RTC2 module must be
updated before it can be used for restoring the program, otherwise the restore
fails.
The controller password is also backed up to the memory backup module

(2080-MEMBAK-RTC and 2080-MEMBAK-RTC2).
IMPORTANT 2080-MEMBAK-RTC is not supported on Micro850 (2080-L50E) and

Micro870 controllers.
For instructions on how to set, change, and clear controller passwords,

see Configure Controller Password on page 267.
Compatibility The Controller Password feature is supported on:

• Connected Components Workbench software version 2 and later
• Micro800 controllers with firmware revision 2
For users with earlier versions of the software and/or revisions of the
hardware, see the compatibility scenarios below.
Connected Components Workbench Software Version 1 with Micro800 Controller

Firmware Revision 2
Connection to a Micro800 controller with firmware revision 2 using an earlier

version of the Connected Components Workbench software (version 1) is
possible and connections will be successful. However, the software will not be
able to determine whether the controller is locked or not.
If the controller is not locked, access to the user application will be allowed,
provided the controller is not busy with another session. If the controller is

locked, access to the user application will fail. You need to upgrade to version 2
of the Connected Components Workbench software.
Connected Components Workbench Software Version 2 with Micro800 Controller

Firmware Revision 1
Connected Components Workbench software version 2 is capable of

“discovering” and connecting to Micro800 controllers with firmware revision
earlier than revision 2 (that is, not supporting the Controller Password
feature). However, the Controller Password feature will not be available to
these controllers. The user will not be able see interfaces associated with the
Controller Password feature in the Connected Components Workbench
software session.
Users are advised to upgrade the firmware. See Flash Upgrade Your Micro800
Firmware on page 257 for instructions.
ATTENTION: Connected Components Workbench software version 9 or

earlier with Micro800 controller firmware revision 10 or later
If a Micro800 controller with firmware revision 10 or later is locked using the
new password algorithm introduced in Connected Components Workbench
software version 10 or later, it cannot be accessed using Connected
Components Workbench software version 9 or earlier. Users are advised to
upgrade to the latest version of Connected Components Workbench
software.
Work with a Locked The following workflows are supported on compatible Micro800 controllers
Controller (firmware revision 2) and Connected Components Workbench software
version 2.
Upload from a Password-Protected Controller

1. Launch the Connected Components Workbench software.
2. In the Project Organizer, expand Catalog by clicking the + sign.
3. Select the target controller.
4. Select Upload.
5. When requested, provide the controller password.
IMPORTANT When using Connected Components Workbench software version 9

or earlier:
• You cannot upload a version 10 or later project from the controller.
• You can upload a version 9 or earlier project from the controller if it was
downloaded to the controller using Connected Components Workbench
software version 10 or later, but you cannot go online.
Debug a Password-Protected Controller
To debug a locked controller, you have to connect to the controller through the
Connected Components Workbench software and provide the password
before you can proceed to debug.

2. In the Project Organizer, expand Catalog by clicking the + sign.

3. Select the catalog number of your controller.
5. Build and save your project.
6. Debug.
Download to a Password-Protected Controller

2. Click Connect.
5. Build and save the project, if needed.
6. Click Download.
7. Click Disconnect.
IMPORTANT If the controller has a password locked version 10 or later project, you
cannot access the controller using Connected Components Workbench
software version 9 or earlier. If you use Connected Components
Workbench software version 10 or later to download a version 9 or
earlier project, the password in the controller will be automatically
converted to the old algorithm.
IMPORTANT If the controller has a password locked version 9 or earlier project and
you use Connected Components Workbench software version 10 or later,
to download a version 10 or later project, the password in the controller
will be automatically converted to the new algorithm.
IMPORTANT If communication is lost during the download, repeat the download and
verify that the controller is password protected.
Transfer Controller Program and Password-Protect Receiving

Controller
In this scenario, the user needs to transfer user application from controller1
(locked) to another Micro800 controller with the same catalog number. The
transfer of the user application is done through the Connected Components
Workbench software by uploading from controller1, then changing the target
controller in the Micro800 project, and then downloading to controller2.
Finally, controller2 will be locked.
1. In the Project Organizer, click the Discover icon.
The Browse Connections dialog appears.
2. Select target controller1.
3. When requested, enter the controller password for controller1.
4. Build and save the project.
5. Click Disconnect.
6. Power down controller1.
7. Swap controller1 hardware with controller2 hardware.
8. Power up controller2.

9. Click Connect.
10. Select target controller2.
11. Click Download.
12. Lock controller2. See Configure Controller Password on page 267.
Back Up and Restore a Password-Protected Controller
In this workflow, user application will be backed up from a Micro800

controller that is locked to a memory plug-in device.
1. In the Project Organizer, click the Discover icon.
The Browse Connections dialog appears.
3. When requested, enter the controller password.
4. Back up controller contents to the memory module.
The project in the memory module is now password locked.
5. Remove the memory module from controller1 and insert into controller2.
6. Restore contents from the memory module to controller2.
This operation succeeds only if:
• the controller has no password – the project can be restored to the
controller by setting the “Load on power up” option for the memory
module to Load Always.
• the controller’s password matches the project’s password.
IMPORTANT Even though the password matches, the restore operation will fail if
either one of the controller or project in the memory module is
protected using the old password algorithm, and the other is protected
using the new password algorithm. You can flash update the controller
using the Reset option to clear the password before restoring the
project to the controller.
IMPORTANT In Connected Components Workbench software version 20.01.00 or

later, if the same password is removed and restored back on the new
Micro850 (2080-L50E) and Micro870 (2080-L70E) controllers, the
backup copy of the program in the 2080-MEMBAK-RTC2 plug-in module
must be updated before it can be used to restore the program.
Otherwise the restore fails as the internal encryption code changes
once the password is removed.
Configure Controller To set, change, and clear controller password, see the quickstart instructions
Password Configure Controller Password on page 267.
IMPORTANT After creating or changing the controller password, you need to power
down the controller in order for the password to be saved.
Recover from a Lost If the controller is secured with a password and the password has been lost,
Password then it becomes impossible to access the controller using the Connected
To recover, the controller must be set to Program Mode using the keyswitch for
Micro830, Micro850, and Micro870 controllers, the 2080-LCD for Micro810

controllers, or the 2080-REMLCD for Micro820 controllers. Then,

ControlFLASH™ can be used to update the controller firmware, which also
clears the controller memory. In Connected Components Workbench software
version 10 or later, the Reset option must be selected for the controller memory
to be cleared during the firmware update. If the Upgrade or Downgrade option
is selected, the password is retained.
ATTENTION: The project in the controller will be lost but a new project can be
downloaded.
Using the Memory Module You can use the memory module (2080-MEMBAK-RTC and 2080-MEMBAK-
Plug-in RTC2) to download a program into different controllers.
IMPORTANT 2080-MEMBAK-RTC is not supported on Micro850 (2080-L50E) and

Micro870 controllers.
Back up the project
To perform a project backup from a controller to the memory module, follow

these steps:
1. Create a new program and choose the desired controller.
The Micro850 controller is used for this example.
2. Double-click the controller icon under Project Organizer to bring up the
controller properties window.
3. Add the memory module to the first slot in the controller.

4. Click Configuration under the MEMBAK-RTC properties and select

“Load Always” or “Load on Memory Error” for the Load on power up
option.
5. Build and Download the project to the controller.

6. While connected to the controller and being in the MEMBAK-RTC
properties, make sure that the controller is changed to Program Mode
and click “Backup to Memory Module” under Memory Module Settings.
Select Yes to download the program into the Memory Module. A window
should pop up stating that the operation has been completed
successfully.
IMPORTANT The Password Mismatch status must be at “False”, this means that the
Controller and Backup project have the same security condition.
If the status is “True” then the Controller will not load from the Memory
module as the security condition is mismatched.
Restore the Project
To restore the project from the memory module to the controller, follow these
steps:
1. While connected to the controller and being in the MEMBAK-RTC
properties, make sure that the controller is changed to Program Mode
and click “Restore from Memory Module” under Memory Module

Settings. Select Yes to download the program into the controller. A

window should pop up stating that the operation has been completed
successfully.
Using the Memory Module to Copy a Project to Multiple Controllers
You can use the memory module to download a project to multiple controllers
without connecting them to a PC with Connected Components Workbench
software installed. To do this:
1. Back up a project with “Load Always” option enabled.
2. Remove the module and plug it into a different controller.
3. Cycle the power. Observe the Status LED on the module lights up for a
few seconds while the project is being downloaded from the module to
the controller.
4. When the operation is finished you can unplug the module and leave the
slot empty, or plug in a different MEMBAK-RTC module if you want to
use the RTC functionality.

Chapter 11
Using microSD Cards
This chapter provides a description of microSD card support on Micro830,

Topic Page
Overview 221
Project Backup and Restore 222
Backup and Restore Directory Structure 223
Power-up Settings in ConfigMeFirst.txt 224
General Configuration Rules in ConfigMeFirst.txt 226
ConfigMeFirst.txt Errors 226
Data Log 229
Recipe 235
Quickstart Projects for Data Log and Recipe Function Blocks 238
The last section provides quickstart projects for the data log and recipe
functions.
Overview With firmware revision 12.011 or later, Micro830, Micro850, and Micro870
controllers support microSD cards through the use of the microSD card plug-
in (a PartnerNetwork™ Technology partner product) for Micro800 controllers
for the following purposes:
• Project backup and restore
• Data log and Recipe
We recommend using the Allen-Bradley 2080-SD-2GB microSD card.
IMPORTANT For Micro850 (2080-L50E) and Micro870 (2080-L70E) controllers, do not

use any microSD card with less than 2 GB of memory.
IMPORTANT For optimum performance, the microSD card should not be more than 90%
full. Regularly check available space on your microSD card and ensure that
the card is exclusively used for the Micro800 controller and no unnecessary
files are present. Regularly delete old data log files and directories.

Chapter 11 Using microSD Cards
IMPORTANT Do not remove the microSD card or power down while operations such as
upload, download, delete, search, backup, and restore are ongoing to
prevent data loss. A blinking SD status LED indicates that these operations
are ongoing.
Note the following:
• The SD status LED will not blink when flash upgrading the firmware from the
microSD card.
• The SD status LED does not blink continuously for the entire duration of the
restore operation.
IMPORTANT To prevent data loss, recipe and data log function blocks must indicate Idle
status before microSD card is removed.
Project Backup and Restore Project backup and restore on Micro830, Micro850, and Micro870 controllers
are mainly supported through the microSD card. Both backup and restore can
be initiated or manually triggered and configured through the Connected
Components Workbench software, and the ConfigMeFirst.txt file in the
microSD card. These backup files are not the same as Connected Components
Workbench project files.
Backup and restore can only occur when the controller is in PROGRAM mode.
On controller power-up, restore automatically occurs if the Load Always or
Load on Memory Error option has been configured in the Connected
In Connected Components Workbench software version 20.01.00 or later,

when you use the Micro850 (2080-L50E) and Micro870 (2080-L70E) controllers
with the microSD card plug-in module, the encryption functionality option is
added to help enhance the encryption capability on your programs for better
security protection.
If you select the option “Enable Encryption on user backup project”, the time it
takes to restore the program can increase up to 10 times, depending on the size
and content of the program.
IMPORTANT To learn about restore and backup using the Connected Components
Workbench software, see the software Online Help.

IMPORTANT For Micro800 controllers that support microSD cards, IP protection of user
project can only be achieved through the POU password protection
mechanism in Connected Components Workbench Developer Edition
software and NOT via Controller Lock feature.
IMPORTANT If the Load Always setting is enabled and power is lost when restoring a
project from the microSD card, the controller will attempt to load the project
using the default project name and directory after power is restored. If your
project is not using the default name and directory, the operation will fail
and a fault occurs, or the wrong project will be loaded.
The default project name is the name of the controller, for example
“Micro850”, and the default directory is “Micro850\USERPRJ”.
If you change the name of the controller from the default, you must
configure the UPD setting in the ConfigMeFirst.txt file.
The microSD card stores the controller password in encrypted format. When
the password is mismatched, the contents of the microSD card is not restored
on the controller.
Backup and restore can be configured to trigger through the following ways:
Method Backup Restore

Online with Connected Components Yes Yes
Workbench software
Project configuration on memory Load Always and/or Load on Memory
No
card at power-up Error options
Yes Yes
ConfigMeFirst.txt at power-up (Through the [BKD] command) (Through the [RSD] command)
Backup and Restore Directory Structure
When a user project is backed up, a subdirectory named

<Micro800>\USERPRJ is created on the microSD card. The folder name takes
the name of the project specified in the General Page in the Connected
Components Workbench software, which is the name of the controller by
default. However, if the ConfigMeFirst.txt file specifies a different
subdirectory (example: MyProject), the project is backed up to that directory.
See General Configuration Rules in ConfigMeFirst.txt on page 226.

Project restore is done from the subdirectory specified in ConfigMeFirst.txt

file or the <Micro800>/USERPRJ default folder, if none is specified in the
ConfigMeFirst.txt file. The user needs to ensure that the directory is populated
with correct contents before restoring.
The ConfigMeFirst.txt file is a configuration file stored on the microSD card

that the user can optionally create to customize backup, restore, recipe, and
data log directories. The following sections include information on how to
configure the ConfigMeFirst.txt properly.
IMPORTANT The Micro800 controller reports a major fault when project backup does not
succeed because the memory card size is exceeded.
Power-up Settings in ConfigMeFirst.txt
On power-up, the controller reads and carries out configuration settings

described in the ConfigMeFirst.txt file. However, the UPD setting also takes
effect when the microSD card is inserted. The configuration settings for the
ConfigMeFirst.txt file are shown in the following table.
ConfigMeFirst.txt Configuration Settings

Setting Takes Effect On... Description
Firmware update settings
File path location of the firmware revision on the microSD
[FWFILE] Power-up card. The default location is in the following format:
firmware\<catalog number>\<filename of firmware>
Sets whether to upgrade or downgrade the controller
firmware from the current revision.
0 = Upgrade firmware; 1 = Downgrade firmware
[FWDOWN] Power-up IMPORTANT: Firmware Upgrade will happen if [FWFILE]
setting points to a newer revision of firmware file compared
to current firmware in the controller, irrespective of
[FWDOWN] setting.
Controller settings
[PM] Power-up Power up and switch to PROGRAM mode.
[CF] Power-up Power up and attempt to clear fault.

ConfigMeFirst.txt Configuration Settings (Continued)

Project settings
Power up and save the controller project into backup
directory,
[BKD = My Proj1] Power-up My Proj1\USERPRJ. Require extra power cycle to clear
existing fault first using [CF] setting or other means.
Power up and read the project from restore directory
MyProj2\USERPRJ into controller. Require extra power
[RSD = MyProj2] Power-up cycle to clear existing fault first using [CF] setting or other
means. This setting overwrites UPD (or its default) load
always or load on error restore function.
For normal usage of backup and restore (that is, through
Connected Components Workbench software, Load
Always, or Load on Memory Error settings), set the user
Power-up and
[UPD = My Proj] project directory name. For example, My Proj, during
Insertion power-up or when the microSD card is inserted.
This directory is also used by data logging and recipe
function.
Network settings
Embedded Serial Factory Defaults.
[ESFD] Power-up Power up and revert embedded serial comms to factory
defaults.
Power up and set IP address to xxx
[IPA = xxx.xxx.xxx.xxx] Power-up (must be numbers only).
Power up and set subnet mask to xxx
[SNM = xxx.xxx.xxx.xxx] Power-up (must be numbers only).
Power up and set gateway address to xxx
[GWA = xxx.xxx.xxx.xxx] Power-up
(must be numbers only).
General settings
End of setting.
This setting is always required even when the
[END] Power-up ConfigMeFirst.txt file does not contain any other setting.
The SD LED goes off when this setting is not present.
IMPORTANT Flash Upgrade Settings

With Connected Components Workbench software version 12 or later,
you can flash upgrade your Micro800 controller from the microSD card in
addition to using ControlFLASH. See Flash Upgrade From MicroSD Card
on page 259 for instructions.
• [FWFILE] and [FWDOWN] settings must be placed at the beginning of the
file.
IMPORTANT Directory Settings

• If no directory has been specified in the ConfigMeFirst.txt file, then
backup and restore will occur in the controller name directory
(<Micro800>/USERPRJ, by default).
• If [UPD] is configured in the ConfigMeFirst.txt file, then backup and
restore will occur in the [UPD] directory specified.
• [BKD] setting is implemented even when the controller is locked or
password protected.
• [BKD] directory is automatically created if it does not yet exist.

IMPORTANT Powerup Network Parameter Settings

• [IPA], [SNM] and [GWA] follow the general IP configuration rules.
• [IPA], when set in ConfigMeFirst.txt, should always be configured with a
valid [SNM] and vice versa.
• When optional [GWA] setting is used, make sure that [IPA] and [SNM]
settings are also present in ConfigMeFirst.txt.
• The [ESFD], [IPA], [SNM], and [GWA] settings overwrite the respective
communication settings from project restore due to [RSD], Load Always
or Load on Memory Error.
Sample ConfigMeFirst.txt File
General Configuration Rules in ConfigMeFirst.txt

• All settings must be in upper case and enclosed in brackets [ ].
• Each line must contain only one setting.
• Settings must always appear first in a line.
• Comments are started with the # symbol.
• No action related to the setting will be carried out when the setting does
not exist, or a # symbol appears before the setting (example, #[PM]).
ConfigMeFirst.txt Errors
The SD status LED goes off when the microSD card is inserted during
PROGRAM or RUN mode (or on power-up) and the ConfigMeFirst.txt file is
either unreadable or invalid. The ConfigMeFirst.txt file will be invalid when it
has the following errors:
• unrecognized setting (that is, the first three configuration rules have not
been followed),
• the setting parameters after the = symbol is invalid, does not exist, or out
of range,
• the same setting exists twice or more,
• one or more non-setting characters exist within the same bracket,
• space in between setting characters (example, [P M]), or
• space in between IP address, subnet mask, and gateway address (for
example, xxx. x xx.xxx.xxx)
• only one of the network parameter settings ([IPA], [SNM], or [GWA]) is
assigned

• [END] setting does not exist (even if there are no other settings in the
configuration file).
The microSD card becomes unusable until the ConfigMeFirst.txt file becomes
readable or the errors are corrected.
Deliver Project Updates to Customers Through Email

A benefit of using the project backup and restore feature is to allow you to
deliver project updates to customers through email. You can do so by following
the example shown below.
Backup project to microSD card
The first step is to back up the project from the controller into the microSD
card.
1. In the Connected Components Workbench software, verify that you have
downloaded the updated project to your controller.
2. Insert a microSD card into the microSD card slot.
3. Set the controller to program mode.
4. Under the Memory Card option in your controller settings, click Backup
to Memory Card.
IMPORTANT The Backup to Memory Card button is enabled when the controller
is in program mode and a microSD card is in the microSD card
slot.
5. After the backup is completed, click OK.
The image files are stored in the default location on the microSD card
<Micro800>\USERPRJ. This location is where the controller loads from when
the Load on power up setting is configured to “Load Always” or “Load on
Error”.
Alternatively, if you do not want to use Connected Components Workbench

software to create the project backup, you can also use the ConfigMeFirst.txt
file.
Figure 19 - Example Configuration for Project Backup
The ConfigMeFirst.txt file also allows you to restore from the backup if you
want to configure the Load on power up setting to “Disable”.
Send Image Files Through Email
The next step is to retrieve the image files from the microSD card and send
them to your customer through email.

1. Remove the microSD card from the controller and read the card using
your computer.
2. Navigate to the location where the image files are stored (default is
<Micro800>\USERPRJ).
3. Use a compression program to zip these image files and send them to
your customer through email.
The customer must unzip these image files into the root directory of their
microSD card and verify that the location is identical to the original (default is
<Micro800>\USERPRJ).
Restore Project from Backup
The last step is to restore the project to your controller from the microSD card.
There are two methods to restore the backup, depending on the configuration
of the controller.
Existing Controller - Load Always / Load on Error
For this example, the Load on power up setting was configured to “Load
Always”. This means that the controller loads the project from the memory
card whenever it is powered on.
1. Insert the microSD card into the microSD card slot.
2. Cycle power to the controller.
3. When the SD LED displays a steady green light, the project restore is
complete.
This method is used for an existing controller that has been configured and
you want to update the program.
New Controller
If your controller is new, you can use the ConfigMeFirst.txt file to restore the
project backup.

Figure 20 - Example Configuration for Project Restore
In the example shown above, the ConfigMeFirst.txt file configures the IP

address, subnet mask, and gateway of the controller, and restores the project
from the location specified on the microSD card.
The ConfigMeFirst.txt file must be placed in the same root directory as the
backup folder in the microSD card.
1. Insert the microSD card into the microSD card slot.

2. Cycle power to the controller.
3. When the SD LED displays a steady green light, the project restore is
complete.
Data Log The data logging feature allows you to capture global and local variables with
timestamp from the Micro800 controller into the microSD card. You can
retrieve the recorded datasets on the microSD card by reading the contents of
the microSD card through a card reader or by doing an upload through the
A maximum number of 10 datasets is supported for a Micro800 program. Each

dataset can contain up to 128 variables, with a maximum of four data string
variables per dataset. String variables can have a maximum of 252 characters.
All datasets are written to the same file. For more information on how data
logs are stored on the microSD card, see the Data Log Directory Structure on
page 230.
You can retrieve data log files from the microSD card using a card reader or by
uploading the data logs through the Connected Components Workbench
software.
IMPORTANT Uploading data log files in PROGRAM mode is recommended for optimum
performance and to prevent file access conflict. For example, if the data
log instruction is executing, Connected Components Workbench
software will not upload the last data log file.
See the sample quickstart project to get you started on the Data Log feature,
Use the Data Log Feature on page 239.

IMPORTANT Data log execution time depends on the user application and its
complexity. Users are advised to data log no faster than every 2 seconds
for typical applications. Note that housekeeping takes at least 5 ms per
program scan. See Program Execution in Micro800 on page 133 for more
information on program scan and execution rules and sequence.
See also Data Log – Data Payload vs. Performance Time on page 234.
IMPORTANT Note that in cases where there are simultaneous RCP and DLG function
block execution or uploads/downloads/searches, the activities are
queued up and handled one by one by the program scan. You will notice a
slowdown in performance in these cases.
Data Log Directory Structure

The DATALOG folder is created under the current project directory in the microSD card. In
this example, the current project directory is MYPROJECT. By default, the current project
directory name is taken from the downloaded project’s controller name or from the
ConfigMeFirst.txt. See ConfigMeFirst.txt Configuration Settings on page 224.
Subdirectories are also created following the controller RTC timestamp. This means that
if RTC date at the time of function block execution is February 02, 2019, the subfolder 2019
is created under DATALOG. Under the 2019 folder, the subfolder 02 (which stands for the
month of February) is created. Under 02, another subfolder 02 is created, corresponding
to the current date.
These data log files are
for February 2, 2019.
Under the current working folder, the subfolder Grp01 is created. A maximum of 50 Grpxxx
folders can be generated on the microSD card per day.
Under the current Grpxxx working folder, the data log file File01.txt is created. Once this
file reaches more than 4 KB, another file, File02.txt, is automatically created to store
data. The file size is kept small in order to minimize data loss in case the card is removed
or when there is unexpected power off.
Each Grpxx folder can accommodate up to 50 files. This means that, for example, when
the Grp01 folder already stores 50 files, a new folder Grp02 is automatically created to
store the next data log files for that day. This automatic folder and file generation goes
on until the Grpxx folder reaches 50 for that day.
When a microSD card is inserted, the DLG function block looks for the last Grpxx folder
and filexx.txt file, and proceeds to do the data logging based on that information.
The following table summarizes data logging performance on Micro800

controllers.
Data Log Specifications

Attribute Value
Maximum datasets 10 All datasets are stored in the same file.
Maximum variables per dataset 128 Configured in Connected Components Workbench

software.
Minimum size per file 4 KB

Data Log Specifications (Continued)

Attribute Value
When directory is full, a new directory is automatically
Maximum files per Grpxx folder(1) 50 created in RUN mode.
When file reaches maximum size, a new file is
Maximum files (Filexx.txt) per day 50 automatically created in RUN mode.
Typical data per day 10 MB
(1) Once the data log limits is reached (that is, 50 Grpxx folders per day, then an error (ErrorID 3: DLG_ERR_DATAFILE_ACCESS) is
returned.
Data Log Function (DLG) Block
The data logging function block lets a user program to write run-time global
values into the data logging file in microSD card.
DLG
Enable Status
TSEnable ErrorID
CfgId
DLG Input and Output Parameters

Parameter
Parameter Data Type Description
Type
Data logging write function enable.
On rising edge (that is, Enable value is triggered from low to
Enable INPUT BOOL high), the function block executes. The precondition for
execution is that the last operation has completed.
TSEnable INPUT BOOL Date and timestamp logging enable flag.
CfgId INPUT USINT Configured dataset (DSET) number (1…10).
Status OUTPUT USINT Data logging function block current status.
ErrorID OUTPUT UDINT Error ID if DLG Write fails.
DLG Function Block Status

Status Code Description
0 Data logging IDLE status.
1 Data logging BUSY status.
2 Data logging COMPLETE SUCCEED status.
3 Data logging COMPLETE ERROR status.
DLG Function Block Errors

Status Code Name Description
0 DLG_ERR_NONE No error.
1 DLG_ERR_NO_SDCARD microSD card is missing.
2 DLG_ERR_RESERVED Reserved.
3 DLG_ERR_DATAFILE_ACCESS Error accessing data log file in microSD card.

DLG Function Block Errors (Continued)

Status Code Name Description
4 DLG_ERR_CFG_ABSENT Data log configuration file is absent.
Configuration ID is missing in data log configuration
5 DLG_ERR_CFG_ID file.
Same Configuration ID is used with other data log
6 DLG_ERR_RESOURCE_BUSY function block call at the same time
7 DLG_ERR_CFG_FORMAT Data log configuration file format is wrong.
8 DLG_ERR_RTC Real time clock is invalid.
9 DLG_ERR_UNKNOWN Unspecified error has occurred.
IMPORTANT File access error will be returned during DLG function block execution
when card is full.
Figure 21 - Data Log Function Block Timing Diagram
Enable(1) Enable(1)
Enable(1)
Disable(0) Disable(0) Disable(0)
Error(3)
Succeed(2)
Busy(1) Busy(1)
Status(0)
Idle(0)
Idle(0) Idle(0)

IMPORTANT Data Log Function Block Execution

• There are three possible states for the Data Log function block: Idle,
Busy, and Complete (which includes Complete with Succeed and
Complete with Error).
• For one Data Log function block execution, the typical status starts from
Idle, then Busy and finishes with Complete. To trigger another function
block execution, the status needs to go back to Idle first.
• Idle status changes to Busy status only when Enable input signal is in
rising edge. Complete status enters Idle status when Enable input signal
is Disable status only.
• TSEnable and CfgId input parameters are only sampled at Enable input
parameter's rising edge when a new function block execution starts.
During function block execution, the input parameters of TSEnable and
CfgId are locked and any changes are ignored.
• When execution completes, the status changes from Busy to Complete. At
this stage, if input Enable is False, status changes to Idle after indicating
Complete for exactly one scan time. Otherwise function block status is
kept as Complete until input Enable changes to False.
• The data log file can only be created by the DLG instruction block. The
Connected Components Workbench software can only upload and delete
the data log file.
• There are separators in between every data variable in the data file that
is defined during configuration in the Connected Components Workbench
software.
See Supported Data Types for Data Log and Recipe Function Blocks on
page 233.
• Data variable values are sampled when data logging function block is in
Busy state. However, data logging file is only created when data logging
function block is in Complete state.
Table 46 - Supported Data Types for Data Log and Recipe Function Blocks
Data Type Description Example Format in Output Data Log File
Logical Boolean with values 0: FALSE
BOOL(1) TRUE and FALSE 1: TRUE)
SINT Signed 8-bit integer value -128, 127
INT Signed 16-bit integer value -32768, 32767
DINT Signed 32-bit integer value -2147483648, 2147483647
LINT Signed 64-bit integer value -9223372036854775808, 9223372036854775807
USINT(BYTE) Unsigned 8-bit integer value 0, 255
UINT(WORD) Unsigned 16-bit integer value 0, 65535
UDINT(DWORD) Unsigned 32-bit integer value 0, 4294967295
ULINT(LWORD) Unsigned 64-bit integer value 0, 18446744073709551615
REAL 32-bit floating point value -3.40282347E+38, +3.40282347E+38
LREAL 64-bit floating point value -1.7976931348623157E+308, +1.7976931348623157E+308
character string
STRING(2) (1 byte per character) '"Rotation Speed"
1234567
Unsigned 32-bit
DATE(1) integer value (Date variables are stored as 32-bit words, a positive number
of seconds beginning at 1970-01-01 at midnight GMT.)
1234567
Unsigned 32-bit
TIME(1) integer value (Time variables are stored as 32-bit words, positive number
of milliseconds).

(1) BOOL, DATE, TIME data variables are presented in decimal digital format in the microSD Card. You have the option to convert
this format to a more friendly format. For example, use ANY_TO_STRING function block to convert BOOL data type (0, 1) to
FALSE or TRUE. You can similarly do the same for DATE and TIME data types.
DATE data type is presented in differential decimal digital value between system baseline time (1970/01/01,00:00:00) and
current date value. Unit is millisecond.
Time should be absolute time value. Unit is second.
(2) String data variables are enclosed in double quotation marks in the data log file.
The example below shows DSET1 using string variables and DSET2 using integers.
Data Log Performance

Data Log – Data Payload vs. Performance Time
Number of Characters
Parameter
28 502 518 1028 1493 3676
Average write time per data log 541.75 ms 1043.75 ms 1086.67 ms 1632.36 ms 1972.9 ms 2696.22 ms
file including all overheads
Average write time excluding first 500.40 ms 963.86 ms 999.14 ms 1472.37 ms 1818.33 ms 2545.92 ms
sample
Average write time excluding all 479.10 ms 493.03 ms 502.78 ms 505.54 ms 519.91 ms 715.68 ms
overheads
Time (msec)
2750 2692.22
2545.918367
2250 Average write time per
1972.9 data log including all
overheads
1750 1632.36 1818.326531 Average write time

excluding first sample
1472.367347
Average write time
1250 1086.67 excluding all overheads
1043.75
999.1414141
963.858859
750
541.75 715.68
502.7840909
500.40
479.10 493.0344828 505.5405405 519.9090909
250 Data Payload
0 500 1000 1500 2000 2500 3000 3500 4000

Time (msec)
2900
2400
Average write time per
data log including all
overheads
1900
Average write time

excluding first sample
1400
Average write time

excluding all overheads
900
400 Data Payload

28-characters 502-characters 518-characters 1028-characters 1493-characters 3676-characters
Recipe Micro800 controllers support the Recipe feature and allows users to store and
load a list of data to and/or from recipe data files using the RCP instruction. It
also allows users to download, upload, and delete Recipe data on the microSD
card through the Connected Components Workbench software.
A maximum number of 10 recipe sets is supported for a Micro800 program.

Each recipe can contain up to 128 variables, with a maximum of four data
string variables per recipe. String variables can have a maximum of 252
characters. Variations of the recipe are stored in separate files with unique file
names. For more information on how recipes are stored on the microSD card,
see the Recipe Directory Structure on page 236.
Table 47 - Recipe Specifications

Attribute Value
Maximum number of recipe sets 10 Recipe sets are stored in 10 directories
Maximum number of recipes (Rcp_Id01...Rcp_Id10) with a maximum number of 50
50 recipe files in each directory.
in each set
Maximum number of variables Configured in Connected Components Workbench
128
per recipe software.
Maximum bytes per recipe file 4 KB

Recipe Directory Structure

On first execution of RCP, it creates the RECIPE folder under the current project
directory on the microSD card.
It also creates 10 subdirectories for each recipe set with a name following the CfgID
input value (1…10). If the CfgID value is 1, then the subfolder Rcp_Id01 is created.
Recipe files are then created/written into the folder, with file names that correspond
to the input value of RcpName parameter for the RCP function block, as configured in
the Connected Components Workbench software. Each Recipe set can contain up to
50 recipe files or variations. Filenames for recipe files should not exceed 30
characters.
Recipe Configuration and Retrieval
You can retrieve recipe files from the microSD card using a card reader or by
uploading and downloading the recipe sets through the Connected
Recipe Function (RCP) Block
The RCP function block allows a user program to read variable values from an
existing recipe data file that is in the recipe folder of the microSD card and
update run-time global or local variable values in the controller. The RCP
function block also allows the user program to write run-time global or local
variable values from smaller controller into the recipe data file in the
microSD card.
RCP
Enable Status
RWFlag ErrorID
CfgId
RcpName

Table 48 - RCP Input and Output Parameters

Parameter
Type
Recipe read/write function enable. If Rising Edge (Enable
is triggered from “low” to “high”), starts recipe function
Enable INPUT BOOL block and the precondition is that last operation is
completed.
TRUE:
Recipe write data variables to recipe files into the
microSD card.
RWFlag INPUT BOOL
FALSE:
Recipe reads saved data variables from the microSD
card and update these variables accordingly.
CfgId INPUT USINT Recipe set number (1…10).
RcpName INPUT STRING Recipe data filename (maximum 30 characters).
Status OUTPUT USINT Current state of Recipe function block.
ErrorID OUTPUT UDINT Detailed error ID information if RCP read/write fails.
Table 49 - RCP Function Block Status

Status Code Description
0 Recipe Idle status.
1 Recipe Busy status.
2 Recipe Complete Succeed status.
3 Recipe Complete Error status.
Table 50 - RCP Function Block Errors

Error ID Error Name Description
0 RCP_ERR_NONE No error.
1 RCP_ERR_NO_SDCARD microSD card is absent.
2 RCP_ERR_DATAFILE_FULL Recipe files exceed maximum number of files per recipe set
folder.
3 RCP_ERR_DATAFILE_ACCESS Error to access recipe data file in microSD card.
4 RCP_ERR_CFG_ABSENT Recipe configuration file is absent.
5 RCP_ERR_CFG_ID Configure ID is absent in recipe configuration file.
The Recipe operation resource linked to this Recipe ID is used
6 RCP_ERR_RESOURCE_BUSY by another function block operation.
7 RCP_ERR_CFG_FORMAT Recipe configuration file format is invalid.
8 RCP_ERR_RESERVED Reserved.
9 RCP_ERR_UNKNOWN Unspecified error has occurred.
10 RCP_ERR_DATAFILE_NAME Recipe data file name is invalid.
11 RCP_ERR_DATAFOLDER_INVALID Recipe dataset folder is invalid.
12 RCP_ERR_DATAFILE_ABSENT Recipe data file is absent.
13 RCP_ERR_DATAFILE_FORMAT Recipe data file contents are wrong.
14 RCP_ERR_DATAFILE_SIZE Recipe data file size is too big (>4K).
IMPORTANT File access error will be returned during RCP function block execution
when card is full.

Figure 22 - Recipe Function Block Timing Diagram
Enable(1) Enable(1)
Enable(1)
Disable(0) Disable(0) Disable(0)
Error(3)
Succeed(2)
Busy(1) Busy(1)
Status(0)
Idle(0)
Idle(0) Idle(0)
IMPORTANT RCP Function Block Execution

• There are three possible states for Recipe function block: Idle, Busy,
Complete (Complete with Succeed and Complete with Error)
• For one Recipe function block execution, the typical status starts from
Idle then Busy and finishes with Complete. To trigger another function
block execution, the status needs to go back to Idle first.
• Idle status changes to Busy status only when Enable input signal is in
rising edge. Complete status enters Idle status when Enable input signal
is on Disable status.
• RWFlag, CfgId, and RcpName input parameters are only sampled at
Enable input parameter's rising edge when a new function block
execution starts. During function block execution, input parameters of
RWFlag, CfgId, and RcpName are locked and any changes are ignored.
• When the function block execution finishes, the function block status
changes from Busy to Complete. At this stage, if input Enable is False,
function block status changes to Idle after staying as Complete for
exactly one scan time. Otherwise, function block status remains
Complete until input Enable changes to False.
• Recipe function block file name supports a maximum of 30 bytes in
length, and only supports upper and lower case letters Aa…Zz, numbers
0…9 and underscore (_).
• The RcpName input parameter does not allow file extension (for example,
.txt) to be added to its value. The recipe data file is written to the microSD
card with the .txt extension.
• There are separators in between every data variable in the recipe data
file that is defined during configuration in Connected Components
Workbench software. Redundant tab, space, carriage return, and line
feed characters are strictly not allowed.
See Supported Data Types for Data Log and Recipe Function Blocks on
page 233.
• Double quotes are not allowed within a string in a recipe file.
Quickstart Projects for Data The following sample quickstart projects provide step-by-step instructions on
Log and Recipe Function how to use the Data Log and Recipe function blocks in the Connected
Components Workbench software to generate and manage your recipe files
Blocks and data logs.

Use the Data Log Feature
Configure Data Log
Create Data Log Ladder Program
Build and Download
Execute DLG Function Block
Upload Data Log File
Configure Data Log

1. In the Connected Components Workbench software, go to the Properties
pane to configure your data log.
2. Select Data Log. Click Add Dataset to add a dataset. Note that each
dataset will be stored in the same file. You can add up to 10 datasets per
configuration.
3. Click Add Variable to add variables to the dataset. You can add up to 128
variables to each dataset.
For this quickstart sample project, add the following variables that you
have previously created to Dataset 1.
Local Variables
Variable Name Data Type
data_bool BOOL
data_int8 INT
data_string STRING

Create Data Log Ladder Program
1. Launch the Connected Components Workbench software. Create a user

program for your Micro800 controller.
2. Right-click Programs. Select Add New LD: Ladder Diagram. Name the
Program (for example, Prog1).
3. From the Toolbox, double-click Direct Contact to add it to the rung.
4. From the Toolbox, double-click Block to add it to the rung.

5. On the Block Selector window that appears, type DLG to filter the DLG
function block from the list of available function blocks. Click OK.

6. Create the following local variables for your project.
Local Variables
EnDlg BOOL
cfg_id USINT
data_time_enable BOOL
error UDINT
status USINT
data_bool BOOL
data_int8 INT
data_string STRING
7. Assign the variables to the DLG input and output parameters as follows:
Note: For CfgID input parameter, you can choose a predefined variable by
choosing from the Defined Words in the Connected Components Workbench
software. To do so, click the CfgID input box. From the Variable Selector
window that appears, click the Defined Words tab and choose from the list of
defined words. For example, DSET1 that corresponds to DSET1 in your recipe
configuration. See Figure 23.

Figure 23 - Choose a Predefined Variable
Build and Download
After configuring data log properties, build the program and download to the
controller.
Execute DLG Function Block
Execute the DLG function block. Notice the Status output go from 0 (Idle) to
1 (Enable), and 2 (Succeed).

Upload Data Log File
You can retrieve data log files from the microSD card using a card reader or by
uploading the data logs through the Connected Components Workbench
software.
1. To use the Upload feature, go to the Properties section of your project in
the Connected Components Workbench software.
2. Select Data Log. Click Manage and then choose Upload.
IMPORTANT The Manage button is not available in DEBUG mode. You need to stop
DEBUG mode to use the Manage button to upload data log files.
Uploading data log files in PROGRAM mode is recommended for
performance and file locking reasons.
3. From the Upload window that appears, select the date of the data log files
that you would like to upload. You can upload data logs for the entire
month by clicking Whole Month option button.
4. If the file already exists in your destination folder, select whether you
would like to Overwrite file, Skip file, or Preserve both files.
5. Click Upload. The progress bar should tell you whether the upload is
successful or not.
IMPORTANT Do not take out the microSD card from the slot while data is being
written or retrieved from the card. Ongoing write and retrieval
operations are indicated by a flashing SD status LED.
IMPORTANT For better data log file management, you can use a third-party tool or
DOS CMD to merge all your data log files into a single file and import as a
CSV file in Excel®.

Use the Recipe Feature
Configure Recipe
Create Recipe Ladder Program
Build and Download
Execute RCP Function Block
Upload Recipe Files
Configure Recipe
1. In the Connected Components Workbench software, go to the Properties
pane to configure Recipe.
2. Select Recipe. Click Add Recipe to add a recipe. Note that each recipe will
be stored in separate files. You can add up to 10 recipes per
configuration.
3. Click Add Variable to add variables to the recipe. You can add up to 128
variables to each recipe.
For this quickstart sample project, add the following variables that you
have previously created to RCP 1:
Local Variables
data_bool BOOL
data_int8 INT

Create Recipe Ladder Program
1. Launch the Connected Components Workbench software. Create a user

program for your Micro800 controller.
2. Right-click Programs. Select Add New LD: Ladder Diagram. Name the
Program (for example, Prog2).
3. From the Toolbox, double-click Direct Contact to add it to the first rung.
4. From the Toolbox, double-click Block to add it to the rung.

5. On the Block Selector window that appears, type RCP to filter the Recipe
function block from the list of available function blocks. Click OK.
6. From the Toolbox, double-click rung to add another rung.

7. Add a Direct Contact and RCP function block to this second rung by
following steps 3…5.
8. Create the following local variables for your program, in addition to the
ones that you have already created for data log.
Local Variables
recipe_file STRING
recipe_file2 STRING
cfg_id2 USINT
read BOOL
write BOOL

9. Assign the variables to the RCP input and output parameters as follows:
Rung 2
Rung 3
Note: For CfgID input parameter, you can choose a predefined variable by
choosing from the Defined Words in the Connected Components Workbench
software. To do so, click the CfgID input box. From the Variable Selector
window that appears, click the Defined Words tab and choose from the list of
defined words. For example, RCP1 that corresponds to RCP1 in your recipe
configuration. See Figure 24.
Figure 24 - Choose a Predefined Variable

Build and Download
After configuring Recipe, build the program and download to the controller.
Execute RCP Function Block
Execute the RCP function block. Notice the Status output go from 0 (Idle) to
1 (Enable), and 2 (Succeed).
Upload Recipe Files
You can retrieve recipe files from the microSD card using a card reader or by
uploading the recipe files through the Connected Components Workbench
software.
1. To use the Upload feature, go to the Properties section of your project in
the Connected Components Workbench software.
2. Select Recipe. Click Manage and then choose Upload.
Through Manage, you can also choose to Download and Delete recipe
files.
3. From the Upload window that appears, select the batch of recipe files
that you would like to upload.

4. If the file already exists in your destination folder, select whether you
would like to Overwrite file, Skip file, or Preserve both Files.
5. Click Upload. The progress bar should tell you whether the upload is
successful or not.
IMPORTANT Do not remove the microSD card from the slot while data is being written
or retrieved from the card. Ongoing write and retrieval operations are
indicated by a flashing SD status LED.
A recipe header file is saved with the uploaded recipes.

Notes:

Appendix A
Modbus Mapping for Micro800
Modbus Mapping All Micro800 controllers (except the Micro810 12-point models) support
Modbus RTU over a serial port through the embedded, non-isolated serial port.
The 2080-SERIALISOL isolated serial port plug-in module also supports
Modbus RTU. Both Modbus RTU master and slave are supported. Although
performance may be affected by the program scan time, the 48-point
controllers can support up to six serial ports (one embedded and five plug-ins),
and so consequently, six separate Modbus networks.
In addition, the Micro850 and Micro870 controller support Modbus TCP

Client/Server through the Ethernet port.
Endian Configuration
Modbus protocol is big-endian in that the most significant byte of a 16-bit

word is transmitted first. Micro800 is also big-endian, so byte ordering does
not have to be reversed. For Micro800 data types larger than 16 bits (for
example, DINT, LINT, REAL, LREAL), multiple Modbus addresses may be
required but the most significant byte is always first.
Mapping Address Space and Supported Data Types

Since Micro800 uses symbolic variable names instead of physical memory
addresses, a mapping from symbolic Variable name to physical Modbus
addressing is supported in Connected Components Workbench software, for
example, InputSensorA is mapped to Modbus address 100001.
By default Micro800 follows the six-digit addressing specified in the latest

Modbus specification. For convenience, conceptually the Modbus address is
mapped with the following address ranges. The Connected Components
Workbench mapping screen follows this convention.
Table 51 - Mapping Table
0 - Coils 1 - Discrete Inputs 3 - Input Registers 4 - Holding Registers
000001…065536 100001…165536 300001…365536 400001…465536
Variable Data Type
Modbus Address Modbus Address Modbus Address Modbus Address
Supported Supported Supported Supported
Used Used Used Used
BOOL Y 1 Y 1
SINT Y 8 Y 8
BYTE Y 8 Y 8

Appendix A Modbus Mapping for Micro800
Table 51 - Mapping Table (Continued)

0 - Coils 1 - Discrete Inputs 3 - Input Registers 4 - Holding Registers
000001…065536 100001…165536 300001…365536 400001…465536
Variable Data Type
Modbus Address Modbus Address Modbus Address Modbus Address
Supported Supported Supported Supported
Used Used Used Used
USINT Y 8 Y 8
INT Y 16 Y 16 Y 1 Y 1
UINT Y 16 Y 16 Y 1 Y 1
WORD Y 16 Y 16 Y 1 Y 1
REAL Y 32 Y 32 Y 2 Y 2
DINT Y 32 Y 32 Y 2 Y 2
UDINT Y 32 Y 32 Y 2 Y 2
DWORD Y 32 Y 32 Y 2 Y 2
LWORD Y 64 Y 64 Y 4 Y 4
ULINT Y 64 Y 64 Y 4 Y 4
LINT Y 64 Y 64 Y 4 Y 4
LREAL Y 64 Y 64 Y 4 Y 4
NOTE: Strings are not supported.
In order to make it easier to map variables to five-digit Modbus addresses, the

Connected Components Workbench mapping tool checks the number of
characters entered for the Modbus Address. If only five-digits are entered, the
address is treated as a five-digit Modbus address. This means that the Coils are
mapped from 00001…09999, Discrete Inputs are mapped from 10001…19999,
Input Registers are mapped from 30001…39999, and Holding Registers are
mapping from 40001…49999.
Example 1, PanelView 800 HMI (Master) to Micro800 (Slave)
The embedded serial port is targeted for use with HMIs using Modbus RTU.
The maximum recommended cable distance is 3 meters. Use the 2080-
SERIALISOL serial port plug-in module if longer distances or more noise
immunity is needed.
The HMI is typically configured for Master and the Micro800 embedded serial
port is configured for Slave.
From the default Communications Settings for a PanelView 800 HMI (PV800),
there are three items that must be checked or modified in order to set up
communications from PV800 to Micro800.

1. Change from DF1 to Modbus protocol.
2. Set the Address of Micro800 slave to match the serial port configuration
for the controller.
3. Deactivate Tags on Error. This is to prevent the requirement of power

cycling PV800 when new Modbus Mappings are downloaded from the
Connected Components Workbench software to the Micro800
controller.
Example 2, Micro800 (Master) to PowerFlex 4M Drive (Slave)
The following is the overview of the steps to be taken for configuring a

PowerFlex 4M drive.
Parameter numbers listed in this section are for a PowerFlex 4M and will be
different if you are using another PowerFlex 4-Class drive.

Table 52 - Parameters
Parameter Number
Parameter Name
4M 4 40 40P 400 400N 400P
Start Source P106 P36
Speed Reference P108 P38
Comm Data Rate C302 A103 C103
Comm Node Addr C303 A104 C104
Comm Loss Action C304 A105 C105
Comm Loss Time C305 A106 C106
Comm Format C306 A107 C102
• Connect the 1203-USB to the PowerFlex Drive and to the Computer.

• Launch the Connected Components Workbench software, Connect to
the Drive and set parameters.
To configure PowerFlex 4M, perform the following steps:

1. Double-click the PowerFlex 4M if it is not already open in the Connected
2. Click Connect.
3. In the Connection Browser, expand the AB_DF1 DH+™ Driver.
Select the AB DSI (PF4 Port) and click OK.
4. Once the Drive has connected and been read in, select the Start up
wizard and change the following items. Select Finish to save the changes
to the drive.
• Select the Comm Port as the Speed Reference. Set P108 [Speed
Reference] to 5 (Comm Port).
• Set Start Source to Comm Port. Set P106 [Start Source] to 5 (Comm
Port).
• Defaults for the remaining Inputs
• Accept Defaults for the remainder and click Finish.
5. Select Parameters from the Connected Components Workbench
window.
6. The Parameter window opens. Resize it to view the parameters. From

this window, you can view and set data values of Parameters.

7. From the Parameter window, change the following Parameters to set the
communications for Modbus RTU so that the PowerFlex 4M Drive
communicates with Micro830/850/870 via Modbus RTU communication.
Table 53 - Modbus RTU Parameters

Parameter Description Setting
C302 Comm. Data Rate (Baud Rate) 4 = 19200 bps 4
C303 Communication Node Address (address range is 1…127) 2
Comm. Loss Action (Action taken when loss communication) 0 = Fault with coast 0
C304 stop
Comm. Loss Time (Time remain in communication before taking action set in
C305 5
C304) 5 sec (Max. 60)
C306 Comm. Format (Data/Parity/Stop) RTU:8 Data Bit, Parity None, 1 Stop bit 0
8. Disconnect the Communications and save your project.
9. Turn off the power to the drive until the PowerFlex 4M display blanks out
completely, then restore power to the PowerFlex 4M.
The drive is now ready to be controlled by Modbus RTU communication
commands initiated from the Micro830/850/870 controller.
Modbus devices can be 0-based (registers are numbered starting at 0), or 1-

based (registers are numbered starting at 1). When PowerFlex 4-Class drives
are used with Micro800 family controllers, the register addresses listed in the
PowerFlex user manuals need to be offset by n+1.
For example, the Logic Command word is located at address 8192, but your
Micro800 program needs to use 8193 (8192+1) to access it.
EXAMPLE: Modbus Address (n+1 value shown)

8193 Logic Command word (Stop, Start, Jog, and so on)
8194 Speed Reference word
xxx.x format for 4/4M/40, where "123" = 12.3 Hz
xxx.xx format for 40P/400/400N/400P, where "123" = 1.23 Hz
8449 Logic Status word (Read, Active, Fault, and so on.)
8452 Speed Feedback word (uses same format as Speed Reference)
8450 Error Code word
(n+1) To access Parameter
If the respective PowerFlex drive supports Modbus Function Code 16 Preset

(Write) Multiple Registers, use a single write message with a length of "2" to
write the Logic Command (8193) and Speed reference (8194) at the same
time.
Use a single Function Code 03 Read Holding Registers with a length of "4" to
read the Logic status (8449), Error Code (8450), and Speed Feedback (8452)
at the same time.
See the respective PowerFlex 4-Class drive User Manual for additional
information about Modbus addressing. See Appendix E – Modbus RTU
Protocol, on publication 22C-UM001.

Performance
The performance of MSG_MODBUS (Micro800 is master) is affected by the

Program Scan because messages are serviced when the message instruction is
executed in a program. For example, if the program scan is 100 ms and six
serial ports are used, then the theoretical maximum for serial ports is 60
messages/second total. This theoretical maximum may not be possible since
MSG_MODBUS is a master/slave request/response protocol, so performance is
affected by several variables such as message size, baud rate, and slave
response time.
The performance of Micro800 when receiving Modbus request messages

(Micro800 is slave) is also affected by the Program Scan. Each serial port is
serviced only once per program scan.

Appendix B
Quickstarts
This chapter covers some common tasks and quickstart instructions that are
aimed to make you familiar with the Connected Component Workbench
software. The following quickstarts are included:
Topic Page
Flash Upgrade Your Micro800 Firmware 257
Establish Communications Between RSLinx and a Micro830/Micro850/ 262
Micro870 Controller through USB
Configure Controller Password 267
Use the High-Speed Counter 270
Forcing I/Os 280
Use Run Mode Change 282
Flash Upgrade Your This quick start will show you how to flash update the firmware for a Micro800
Micro800 Firmware controller using Connected Components Workbench software version 10 or
later.
From Connected Components Workbench software release 10 onwards, there

are two options you can select when flash updating the firmware:
• Upgrade or Downgrade – This option retains the controller’s existing
configuration, Ethernet settings, and password.
• Reset – This option clears the controller’s existing configuration,
Ethernet settings, and password.
The procedure to flash update the controller is similar for both options.
ATTENTION: Retention of the controller’s existing configuration,

Ethernet settings, and password is only available when flash updating
from firmware revision 10 to the same or later revision. If updating from
firmware revision 10 to 9 or earlier, or updating to firmware revision 10
from an earlier revision, the controller’s existing configuration, Ethernet
settings, and password will be cleared.
IMPORTANT If you have forgotten the password for the controller, use the Reset
option to clear the password.
On Micro850 and Micro870 controllers, users can use flash update their
controllers through the Ethernet port, in addition to the USB.
IMPORTANT To successfully flash update your controller over USB, connect only one
controller to your computer, and do not perform the flash update in a
virtual machine such as VMware.

Appendix B Quickstarts
IMPORTANT Flash update over USB using FactoryTalk Linx software with a 32-bit
operating system is not supported. Use either a 64-bit operating system
or RSLinx Classic software.
To begin, launch the Connected Components Workbench software:

1. In the menu, select Device → Update Firmware → Upgrade or
Downgrade...
Alternatively, in the Project Organizer, right-click the controller and
select Update Firmware → Upgrade or Downgrade...
2. If your project does not have a connection path to the controller, the
Connection Browser dialog appears. Select your controller, then click
OK.
3. In the Upgrade or Downgrade Firmware dialog box, select the desired

Target Revision to flash update the controller.
If the desired firmware revision is not shown in the drop-down list, you
can download that firmware revision by clicking the “Get the firmware
files online” link.
You can also change the Connection Path by clicking the “Change” link.
4. When you have confirmed the settings, click Update to begin flash
updating the controller.
The update progress is shown in the dialog box.

5. After the update is completed, the status is shown in the dialog box.
IMPORTANT After control flashing the controller, some microSD cards may not be
detected. Remove and insert the microSD card, or power cycle the
controller if this issue is encountered.
Flash Upgrade From MicroSD Card
With Connected Components Workbench software version 12 or later, and the

microSD card plug-in for Micro800 controllers, you can flash upgrade your
Micro830, Micro850, and Micro870 controller from the microSD card in
addition to using ControlFLASH. This is two-step process – first you have to
transfer the firmware to the microSD card using the SD Card Utility, then you
need to edit the ConfigMeFirst.txt file to initiate the flash upgrade process. See
the following instructions for performing the flash upgrade from the microSD
card.
Step 1 – Transfer the Firmware to the microSD Card


2. Click Tools → SD Card Utility.
The SD Card Utility window appears.
3. Select the drive letter that points to the microSD card on your computer
from the pull-down list.
You can check the drive letter by looking in Windows® Explorer. For this
example, the microSD card uses the drive letter “G”.
4. Select the catalog number of your Micro800 controller.

5. Select the firmware revision you want to flash your Micro800 controller
with.
The list of firmware revisions are installed together with the Connected
Components Workbench software. If you require a revision that is not
listed, download the firmware from the Product Compatibility and
Download Center (PCDC) at rok.auto/pcdc and install the included
ControlFLASH kit.
IMPORTANT You must sign in to the Rockwell Automation website before

downloading a firmware revision.
Close and relaunch the Connected Components Workbench software,

then open the SD Card Utility again. The revision should now appear in
the list.
6. Click Transfer.
The file is copied to the microSD card.
7. Close the SD Card Utility and proceed to the next step to edit the
ConfigMeFirst.txt file.
Step 2 – Edit the ConfigMeFirst.txt File
To flash upgrade the controller with the firmware that you have transferred to
the microSD card, you need to edit the ConfigMeFirst.txt file with the settings
listed below. These settings must be added at the beginning of the file.

Table 54 - New ConfigMeFirst.txt Configuration Settings for Flash Upgrade

Firmware update settings
File path location of the firmware revision on the microSD
[FWFILE] Powerup card. The default location is in the following format:
firmware\<catalog number>\<filename of firmware>
Sets whether to upgrade or downgrade the controller
firmware from the current revision.
0 = Upgrade firmware; 1 = Downgrade firmware
[FWDOWN] Powerup IMPORTANT: Firmware Upgrade will happen if [FWFILE]
setting points to a newer revision of firmware file
compared to current firmware in the controller,
irrespective of [FWDOWN] setting.
Example of ConfigMeFirst.txt File for Flash Upgrade
After you have edited the file, insert the microSD card into the controller.
Power cycle the controller and the flash upgrade process will begin. Note that
the SD status LED will not blink when flash upgrading the firmware from the
microSD card is in progress.
When using the ControlFLASH software to downgrading the firmware of a

Micro830 or Micro850 series B controller to firmware revision 10.011, the
program reports an error and fails at the initial stage. However when
upgrading a Micro800 controller using the microSD card with a firmware
revision that is not compatible with the series, the controller hard faults. There
is no error code reported after you have cycled power to the controller. The
controller retains the old firmware.
Table 55 - Fault Status Indicator Description

State Indicates
Steady Red Fault
Flashing Green Run
For a list of firmware and series compatibility, see the release notes for
firmware revision 11.011 or later, on the Product Compatibility and Download
Center (PCDC) at rok.auto/pcdc.
Establish Communications This quick start shows you how to get RSLinx® RSWho to communicate with a
Between RSLinx and a Micro830, Micro850, or Micro870 controller through USB. Micro830,
Micro850, and Micro870 controllers use the AB_VBP-x driver.
Micro830/Micro850/
Micro870 Controller RSLinx Classic is installed as part of the Connected Components Workbench
through USB software installation process. The minimum version of RSLinx Classic with full
Micro800 controller support is 2.57, build 15 (released March 2011).

1. Power up the Micro830/Micro850/Micro870 controller.

2. Plug USB A/B cable directly between your PC and the Micro830/
Micro850/Micro870 controller.
3. Windows should discover the new hardware. Click No, not this time and
then click Next.
4. Click Install the software automatically (Recommended), and then click

Next.
5. The Wizard searches for new hardware.

6. Click Finish when the wizard completes the installation.
7. Open RSLinx Classic and run RSWho by clicking the icon.
If the proper EDS file is installed, the Micro830/Micro850/Micro870

controller should be properly identified and show up under both the
Virtual Backplane (VBP) driver and the USB driver, which was
automatically created.
If instead the Micro830/Micro850/Micro870 shows up as a "1756 Module"

under the AB_VBP-1 Virtual Chassis driver, then the proper EDS file for
this major revision of firmware has not yet been installed or the
controller is running pre-release firmware (Major Revision=0).

Since Micro830/Micro850/Micro870 controllers support embedded EDS

files, right-click this device, and select Upload EDS file from device.
8. On the EDS wizard that appears, click Next to continue.
9. Follow the prompts to upload and install the EDS file.

10. Click Finish to complete.

If the Micro830/Micro850/Micro870 still shows up as a 1756 Module, then

you are probably running pre-release firmware that is reporting itself as
Major Revision 0, which does not match the embedded EDS file. To
confirm, right-click the device and select Device Properties (firmware
Revision is Major.Minor).
Configure Controller Set, change, and clear the password on a target controller through the
Password Connected Components Workbench software.
IMPORTANT The following instructions are supported on Connected Components

Workbench software version 2 and Micro800 controllers with firmware
revision 2.
For more information about the controller password feature on Micro800
controllers, see Controller Security on page 213.
Set Controller Password
IMPORTANT After creating or changing the controller password, you need to power
down the controller in order for the password to be saved.

In the following instructions, the Connected Components Workbench

software is connected to the Micro800 controller.
1. On the Connected Components Workbench software, open the project
for the target controller.
2. Click Connect to connect to the target controller.
On the Device Details toolbar, the Secure tooltip message “Set, Change,
or Clear Micro800 Controller Password Protection” is displayed.
3. Click Secure. Select Set Password.
4. The Set Controller Password dialog appears. Provide password. Confirm

the password by providing it again in the Confirm field.
Passwords must have at least eight characters to be valid.
5. Click OK.
Once a password is created, any new sessions that try to connect to the
controller will have to supply the password to gain exclusive access to the
target controller.

Change Password
With an authorized session, you can change the password on a target

controller through the Connected Components Workbench software. The
target controller must be in Connected status.
6. On the Device Details toolbar, click Secure. Select Change Password.
7. The Change Controller Password dialog appears. Enter Old Password,

New Password and confirm the new password.
8. Click OK.
The controller requires the new password to grant access to any new session.
Clear Password
With an authorized session, you can clear the password on a target controller
through the Connected Components Workbench software.
1. On the Device Details toolbar, click Secure. Select Clear Password.

2. The Clear Password dialog appears. Enter Password.

3. Click OK to clear the password.
The controller requires no password on any new session.
Use the High-Speed Counter To use a HSC device, you first need to establish the HSC counting mode
required by your application. See HSC Mode (HSCAPP.HSCMode) on page 189
for available modes on Micro800 controllers.
The following sample project guides you through the creation of a project that
uses HSC mode 6, a quadrature counter with phased inputs A and B. It shows
you how to write a simple ladder program with the HSC function block, create
variables, and assign variables and values to your function block. It also guides
you through a step-by-step process on how test your program, and enable a
Programmable Light Switch (PLS).
This sample project makes use of a quadrature encoder. The quadrature

encoder is used for determining direction of rotation and position for
rotating, such as a lathe. The Bidirectional Counter counts the rotation of the
Quadrature Encoder.
Figure 25 on page 271 shows a quadrature encoder connected to inputs 0 and 1.

The count direction is determined by the phase angle between A and B. If A
leads B, the counter increments. If B leads A, the counter decrements.

Figure 25 - Quadrature Encoder on Inputs 0 and 1
A
Input 0
Quadrature Encoder Input 1

B
Forward Rotation Reverse Rotation
B
1 2 3 2 1
Count
This quickstart includes the following sections:

• Create the HSC Project and Variables on page 271
• Assign Values to the HSC Variables on page 274
• Assign Variables to the Function Block on page 276
• Run the High-Speed Counter on page 277
• Use the Programmable Limit Switch (PLS) Function on page 279
Create the HSC Project and Variables

1. Start the Connected Components Workbench software and open a new
project. From the Device Toolbox, go to Catalog → Controllers. Double-
click your controller(1) or drag and drop it onto the Project Organizer
window.
2. Under Project Organizer, right-click Programs. Click Add New LD:

Ladder Diagram to add a new ladder logic program.
(1) The HSC module is supported on all Micro830, Micro850, and Micro870 controllers, except
on 2080-LCxx-xxAWB types.
3. Right-click UntitledLD and select Open.
4. From the Toolbox, double-click Direct Contact to add it to the rung or

drag and drop Direct Contact onto the Rung.
5. Double-click the Direct Contact you have just added to bring up the
Variable Selector dialog. Click I/O Micro830 tab. Assign the Direct
Contact to input 5 by selecting _IO_EM_DI_05. Click OK.

6. To the right of the Direct Contact, add a function block by double-

clicking function block from the Toolbox or dragging and dropping the
function block onto the rung.
7. Double-click the function block to open up the Instruction Selector

dialog. Choose HSC. You can do a quick search for HSC function block by
typing “HSC” on the name field. Click OK.
Your ladder rung appears as shown:
8. On the Project Organizer pane, double-click Local Variables to bring up

the Variables window. Add the following variables with the
corresponding data types, as specified in Table 56 on page 274.

Table 56 - Variable Data Types

MyCommand USINT
MyAppData HSCAPP
MyInfo HSCSTS
MyPLS PLS
MyStatus UINT
After adding the variables, your Local Variables table should look like
this:
Assign Values to the HSC Variables
Next, you need to assign values to the variables you have just created. Typically,
a routine is used to assign values to your variables. For illustration purposes,
this quickstart assigns values through the Initial Value column of the Local
Variables table.
In a real program, you should write a routine to assign values to your

variable according to your application.
1. On the Initial Value field for the MyCommand variable, type 1.
See HSC Commands (HScCmd) on page 203 for more information on the
description for each value.
2. Assign values to the MyAppData variables. Expand the list of MyAppData
subvariables clicking the + sign. Set the values of the different
subvariables as shown in the following screenshot.

IMPORTANT MyAppData variable has subvariables that determine the settings of the
counter. It is crucial to know each one in order to determine how the
counter will perform. A quick summary is provided below but you can
also see HSC APP Data Structure on page 187 for detailed information.
MyAppData.PlsEnable allows the user to either enable o disable the PLS

settings. It should be set to FALSE (disabled) if the MyAppData variable is to be
used.
MyAppData.HscID allows the user to specify which embedded inputs will be

used depending on the mode and the type of application. See the table HSC
Inputs and Wiring Mapping on page 185 to know the different IDs that can be
used as well as the embedded inputs and its characteristics.
If ID 0 is used, ID 1 cannot be used on the same controller since the inputs are
being used by the Reset and Hold.
MyAppData.HscMode allows the user to specify the type of operation in which

the HSC will use to count. See HSC Mode (HSCAPP.HSCMode) on page 189 for
more information about HSC modes. See Table 57 for the list available modes.
Table 57 - HSC Operating Modes

Mode Type
Number
Up Counter – The accumulator is immediately cleared (0) when it reaches the high preset. A low
0 preset cannot be defined in this mode.
Up Counter with external reset and hold – The accumulator is immediately cleared (0) when it
1 reaches the high preset. A low preset cannot be defined in this mode.
2 Counter with external direction
3 Counter with external direction, reset, and hold
4 Two input counter (up and down)
5 Two input counter (up and down) with external reset and hold
6 Quadrature counter (phased inputs A and B)
7 Quadrature counter (phased inputs A and B) with external reset and hold
8 Quadrature X4 counter (phased inputs A and B)
9 Quadrature X4 counter (phased inputs A and B) with external reset and hold
Modes 1, 3, 5, 7, and 9 will only work when an ID of 0, 2, or 4 is set due to the fact
that these modes use reset and hold. Modes 0, 2, 4, 6, and 8 will work on any ID.
Modes 6…9 will only work when an encoder is connected to the controller. Use
the HSC ID chart as a reference to wire the encoder to the controller.
MyAppData.HPSetting, MyAppData.LPSetting, MyAppData.OFSetting, and

MyAppData.UFSetting are all user-defined variables that represent the
counting range of the HSC. Figure 26 on page 276 gives an example of a range
of values that can be set for these variables.

Figure 26 - Range of Values
Variable
HscAppData.OFSetting Overflow +2,147,483,647 maximum
HscAppData.HPSetting High Preset
HscAppData.LPSetting Low Preset
HscAppData.UFSetting Underflow -2,147,483,648 minimum
MyAppData.OutputMask along with MyAppData.HPOutput and

MyAppData.LPOutput allows the user to specify which embedded outputs can
be turned on when a High Preset or Low Preset is reached. These variables use
a combination of decimals and binary numbers to specify the embedded
outputs that are able to turn on/off.
Thus, in our example, we first set the Output Mask to a decimal value of 3
which, when converted to binary, is equal to 0011. This means that now outputs
O0 and O1 can be turned On/Off.
We have set the HPOutput to a decimal value of 1, which, when converted to

binary, is equal to 0001. This means that when a High Preset is reached, output
O0 will turn on and stay on until the HSC is reset or the counter counts back
down to a Low Preset. The LPOutput works same way as the HPOutput except
an output will be turned on when a Low Preset is reached.
Assign Variables to the Function Block

1. Go back to the ladder diagram and assign the variables you have just
configured to the corresponding elements of the HSC function block.
The HSC function block should appear as shown:
To assign a variable to a particular element in your function block,

double-click the empty variable block. On the Variable selector that
appears, choose the variable you have just created. For example, for the
input element HSCAppData, select the variable MyAppData.

2. Next, click the Micro830 controller under the Project Organizer pane to
bring up the Micro830 Controller Properties pane. Under Controller
Properties, click Embedded I/O. Set the input filters to a correct value
depending on the characteristics of your encoder.
3. Make sure that your encoder is connected to the Micro830 controller.

4. Power up the Micro830 controller and connect it to your PC. Build the
program in the Connected Components Workbench software and
download it to the controller.
Run the High-Speed Counter

1. To test the program, go into debug mode by doing any of the following:
• Click Debug menu, then choose Start Debugging,
• Click the green play button below the menu bar, or
• Press the F5 Windows key.
Now that we are on debug mode we can see the values of the HSC output.
The HSC function block has two outputs, one is the STS (MyStatus) and
the other is the HSCSTS (MyInfo).
2. Double-click the Direct Contact labeled _IO_EM_DI_05 to bring up the
Variable Monitoring window.

3. Click the I/O Micro830 tab. Select the _IO_EM_DI_05 row. Check the
boxes Lock and Logical Value so that this input will be forced in the ON
position.
4. Click the Local Variables tab to see any real time changes being made to
the variables. Expand the MyAppData and MyInfo variable list by
clicking the + sign.
5. Turn On the encoder to see the counter count up/down. For example, if
the encoder is attached to a motor shaft then turn on the motor to trigger
the HSC count. The counter value will be displayed on
MyInfo.Accumulator. MyStatus variable should display a Logical Value
of 1, which means that the HSC is running.
See HSC Function Block Status Codes on page 204 for the complete list
of status codes. For example, if the MyStatus value is 04, a configuration
error exists and the controller will fault. You need to check your
parameters in this case.

For this example, once the Accumulator reaches a High Preset value of 40,
output 0 turns on, and the HPReached flag turns on. Once the Accumulator
reaches a Low Preset value of -40, output 1 turns on and the LPReached flag
turns on as well.
Use the Programmable Limit Switch (PLS) Function
The Programmable Limit Switch function allows you to configure the High-
Speed Counter to operate as a PLS (programmable limit switch) or rotary cam
switch. The PLS is used when you need more than one pair of high and low
presets (up to 255 pairs of high and low presets are supported by the PLS).
1. Start a new project following the same steps and values as the previous
project. Set the values for the following variables as follows:
• HSCAPP.PlsEnable variable should be set to TRUE.
• Set a value only for UFSetting and OFSetting (OutputMask is optional
depending if an output is to be set or not). Your new values should
follow the example in Figure 27:

Figure 27 - PLS Values
In this example, the PLS variable is given a dimension of [1..4]. This

means that the HSC can have four pairs of High and Low Presets.
Once again, your High Presets should be set lower than the OFSetting
and the Low Preset should be greater than the UFSetting. The
HscHPOutPut and HscLPOutPut values will determine which outputs
will be turned on when a High Preset or Low Preset is reached.
2. You can now build and download the program into the controller then
debug and test it following the instructions for the last project.
Forcing I/Os Inputs are logically forced. Status indicators do not show forced values, but the
inputs in the user program are forced.
Forcing is only possible with I/O and does not apply to user-defined variables
and non-I/O variables, and special functions such as HSC and Motion that
execute independently from the User Program scan. For example, for motion,
Drive Ready input cannot be forced.
Unlike inputs, outputs are physically forced. Status indicators do show forced
values and the user program does not use forced values.

Figure 28 illustrates forcing behavior.
Figure 28 - Forcing I/O Behavior
HSC
User Program
Physical Logical Logical Physical

Force Force
Inputs Inputs Outputs Outputs
Normal
Variables
Motion
• LED status indicators always match the physical value of I/O

• Normal, non-physical internal variables cannot be forced
• Special functions such as HSC and Motion cannot be forced
ATTENTION: Forcing variable can result in sudden machine

movement, possibly injuring personnel or equipment. Use extreme
caution when forcing variables.
Checking if Forces (locks) are Enabled

If the Connected Components Workbench software is available, check the
Variable Monitor while debugging online. Forcing is performed by first
Locking an I/O variable and then setting the Logical Value for Inputs and
Physical Value for Outputs. Remember you cannot force a Physical Input and
cannot force a Logical Output.

In many cases, the front of the controller is not visible to the operator and the
Connected Components Workbench software is not online with the controller.
If you want the force status to be visible to the operator, then the User Program
must read the force status using the SYS_INFO function block and then
display the force status on something that the operator can see, such as the
human machine interface (HMI), or stack light. Figure 29 is an example
program in Structured Text.
Figure 29 - Structured Text Example Program
If the front of the controller is visible, and not blocked by the cabinet enclosure,
Micro830, Micro850, and Micro870 controllers have a Force LED indicator.
I/O Forces After a Power Cycle
After a controller is power cycled, all I/O forces are cleared from memory.
Use Run Mode Change Run Mode Change allows the user to make small changes to the logic of a
running project and immediately testing it out on the controller, without
having to go into Program mode or disconnecting from the controller.
IMPORTANT The following requirements must be met to use Run Mode Change:
• Micro820/Micro830/Micro850 controller firmware revision 8 or higher,
and
• Connected Components Workbench Developer Edition software, version 8
or higher.
The following sample project guides you through the creation of a simple
application for a Micro850 controller without any plug-in modules, and how to
use the Run Mode Change feature.

Create the Project

1. Create a new project for a Micro830/Micro85/Micro8700 controller
without any plug-ins.
Observe that the controller is disconnected.
2. Right-click Programs and select Add → New LD: Ladder Diagram.

3. From the Toolbox, double-click Direct Coil to add it to the rung, or drag
and drop Direct Coil onto the rung.
4. Double -click the newly added Direct Coil to bring up the Variable
Selector dialog and select “_IO_EM_DO_00”.
5. Build the project.

6. Download the project to the controller.

In the Connection Browser dialog, select the Micro850 controller.
7. Select Download current project to the controller.
8. Select Download to confirm.
9. When the project has been downloaded to the controller, a prompt

asking to change the controller to Remote Run mode appears. Click Yes.

10. Observe that the controller is now in Debug mode.
IMPORTANT From Connected Components Workbench software version 8

onwards, selecting “Yes” to change the controller to Remote Run
mode after a downloading a project automatically switches it to
Debug mode.
Edit the Project Using Run Mode Change

Run Mode Change Toolbar
Run Mode Change Test Logic Changes Accept Changes Undo Changes
1. Click the Run Mode Change icon.

Observe that the controller goes into Edit mode and is still connected.
If you add a new variable during RMC, external data access and changing
the access type (default is Read/Write) of this new variable is not
available until you have chosen to Accept or Undo the Test Logic changes.
2. From the Toolbox, double-click Instruction Block to add it to the rung, or
drag and drop Instruction Block onto the rung.

3. Double-click the newly added Instruction Block and select

“Timer On/Off “(TONOFF).
Configure the Instruction Block to trigger every one second.
4. From the Toolbox, double-click Reverse Contact to add it to the rung, or

drag and drop Reverse Contact onto the run. Place it to left of the recently
added Instruction Block.
5. Click the Test Logic Changes icon to build the project and download
it to the controller.
IMPORTANT When a Test Logic is performed, or undoing changes after the

Test Logic is completed, any active communication instructions
will be aborted while the changes are downloaded to the
controller.

6. The controller will automatically go into Debug mode and display the
updated project.
7. You can now choose to either Undo or Accept the changes to the project.
To Undo the Changes

1. Click the Undo Changes icon.
2. The changes will be discarded and the original project will be restored to
the controller.
IMPORTANT When a Test Logic is performed, or undoing changes after the

Test Logic is completed, any active communication instructions
will be aborted while the changes are downloaded to the
controller.
Observe that original project is shown and the controller is in Debug

mode.
To Accept the Changes

1. Click the Accept Changes icon.
2. Observe that only the Run Mode Change icon is now enabled and the
controller remains in Debug mode.

Notes:

Appendix C
User Interrupts
Interrupts allow you to interrupt your program based on defined events. This
chapter contains information about using interrupts, the interrupt
instructions, and interrupt configuration. The chapter covers the following
topics:
Topic Page
Information About Using Interrupts 289
User Interrupt Instructions 292
Using the Selectable Timed Interrupt (STI) Function 297
Selectable Time Interrupt (STI) Function Configuration and Status 298
Using the Event Input Interrupt (EII) Function 299
For more information on HSC Interrupt, see Use the High-Speed Counter and
Programmable Limit Switch on page 183.
Information About Using The purpose of this section is to explain some fundamental properties of the
Interrupts User Interrupts, including:
• What is an interrupt?
• When can the controller operation be interrupted?
• Priority of User Interrupts
• Interrupt Configuration
• User Fault Routine
What is an Interrupt?
An interrupt is an event that causes the controller to suspend the Program

Organization Unit (POU) it is currently performing, perform a different POU,
and then return to the suspended POU at the point where it suspended. The
Micro830, Micro850, and Micro870 controllers support the following User
Interrupts:
• User Fault Routine
• Event Interrupts (8)
• High-Speed Counter Interrupts (6)
• Selectable Timed Interrupts (4)
• Plug-in Module Interrupts (5)
An interrupt must be configured and enabled to execute. When any one of the
interrupts is configured (and enabled) and subsequently occurs, the user
program:

Appendix C User Interrupts
1. suspends its execution of the current POU,

2. performs a predefined POU based on which interrupt occurred, and
3. returns to the suspended operation.
Interrupt Operation Example POU 2
POU 2 is the main control program.
rung 0
POU 10 is the interrupt routine. POU 10
• An Interrupt Event occurs at rung 123.
• POU 10 is executed.
• POU 2 execution resumes immediately after POU 10 rung 123
is scanned.
rung 275
Specifically, if the controller program is executing normally and an interrupt

event occurs:
1. The controller stops its normal execution.
2. Determines which interrupt occurred.
3. Goes immediately to the beginning of the POU specified for that User
Interrupt.
4. Begins executing the User Interrupt POU (or set of POU/function blocks
if the specified POU calls a subsequent function block).
5. Completes the POU.
6. Resumes normal execution from the point where the controller program
was interrupted.
When Can the Controller Operation be Interrupted?

The Micro830 controllers allow interrupts to be serviced at any point of a
program scan. Use UID/ UIE instructions to protect program block that should
not be interrupted.
Priority of User Interrupts
When multiple interrupts occur, the interrupts are serviced based on their
individual priority.
When an interrupt occurs and another interrupt(s) has already occurred but
has not been serviced, the new interrupt is scheduled for execution based on
its priority relative to the other pending interrupts. At the next point in time
when an interrupt can be serviced, all the interrupts are executed in the
sequence of highest priority to lowest priority.
If an interrupt occurs while a lower priority interrupt is being serviced

(executed), the currently executing interrupt routine is suspended, and the
higher priority interrupt is serviced. Then the lower priority interrupt is
allowed to complete before returning to normal processing.
If an interrupt occurs while a higher priority interrupt is being serviced

(executed), and the pending bit has been set for the lower priority interrupt,

the currently executing interrupt routine continues to completion. Then the

lower priority interrupt runs before returning to normal processing.
Table 58 - Priorities From Highest to Lowest

User Fault Routine highest priority
Event Interrupt0
Event Interrupt1
Event Interrupt2
Event Interrupt3
High-Speed Counter Interrupt0
Event Interrupt4
Event Interrupt5
Event Interrupt6
Event Interrupt7
Selectable Timed Interrupt0
Plug-In Module Interrupt0, 1, 2, 3, 4 lowest priority
User Interrupt Configuration
User interrupts can be configured and set as AutoStart from the Interrupts
window.

User Fault Routine
The user fault routine gives you the option of doing the cleanup before a
controller shutdown, when a specific user fault occurs. The fault routine is
executed when any user fault occurs. The fault routine is not executed for non-
user faults.
The controller goes to Fault mode after a User Fault Routine is executed, and
the User Program execution stops.
Creating a User Fault Subroutine
To use the user fault subroutine:

1. Create a POU.
2. In the User Interrupt Configuration window, configure this POU as a
User Fault routine.
User Interrupt Instructions

Instruction Used To: Page
Use the STIS (Selectable Timed Interrupt Start) instruction to the
STIS – Selectable Timed Start start the STI timer from the control program, rather than starting 293
automatically.
UID – User Interrupt Disable Use the User Interrupt Disable (UID) and the User Interrupt Enable 293
(UIE) instructions to create zones in which user interrupts cannot
UIE – User Interrupt Enable occur. 294
Use the UIF instruction to remove selected pending interrupts from
UIF – User Interrupt Flush 295
the system.
Use this function to clear Interrupt Lost bit for the selected User
UIC – User Interrupt Clear 296
Interrupt(s).

STIS - Selectable Timed Start

STIS
Enable STIS(name or Pin ID)

IRQType or ENO(Pin ID)
SetPoint
STI0 is used in this document to define how STIS works.
Table 59 - STIS Parameters
Parameter Parameter Type Data Parameter Description

Type
Enable Function.
Enable Input BOOL When Enable = TRUE, function is performed.
When Enable = FALSE, function is not performed.
Use the STI defined DWORD
IRQType Input UDINT IRQ_STI0, IRQ_STI1, IRQ_STI2, IRQ_STI3
The user timer interrupt interval time value in milliseconds.
SetPoint Input UINT When SetPoint = 0, STI is disabled.
When SetPoint = 1…65535, STI is enabled.
STIS or ENO Output BOOL Rung Status (same as Enable)
The STIS instruction can be used to start and stop the STI function or to
change the time interval between STI user interrupts. The STI instruction has
two operands:
• IRQType — This is the STI ID that a user wants to drive.
• SetPoint — This is the amount of time (in milliseconds) which must
expire prior to executing the selectable timed user interrupt. A value of
zero disables the STI function. The time range is from 0…65,535
milliseconds.
The STIS instruction applies the specified set point to the STI function as
follows (STI0 is used here as an example):
• If a zero set point is specified, the STI is disabled and STI0.Enable is
cleared (0).
• If the STI is disabled (not timing) and a value greater than 0 is entered
into the set point, the STI starts timing to the new set point and
STI0.Enable is set (1).
• If the STI is currently timing and the set point is changed, the new
setting takes effect immediately, restarting from zero. The STI continues
to time until it reaches the new set point.
UID - User Interrupt Disable

UID
Enable UID (name or Pin ID)

The UID instruction is used to disable selected user interrupts. The table below
shows the types of interrupts with their corresponding disable bits:

Table 60 - Types of Interrupts Disabled by the UID Instruction

Interrupt Type Element Decimal Value Corresponding Bit
Plug-In Module UPM4 8388608 bit 23
STI - Selectable Timed Interrupt STI3 262144 bit 18
EII - Event Input Interrupt Event 7 16384 bit 14
HSC - High-Speed Counter HSC5 1024 bit 10
UFR - User Fault Routine Interrupt UFR 1 bit 0 (reserved)
To disable interrupt(s):
1. Select which interrupts you want to disable.
2. Find the Decimal Value for the interrupt(s) you selected.
3. Add the Decimal Values if you selected more than one type of interrupt.
4. Enter the sum into the UID instruction.
For example, to disable EII Event 1 and EII Event 3:

EII Event 1 = 4, EII Event 3 = 16
4 + 16 = 20 (enter this value)
UIE - User Interrupt Enable

UIE
Enable UIE (name or Pin ID)

The UIE instruction is used to enable selected user interrupts. The table below
shows the types of interrupts with their corresponding enable bits:

Table 61 - Types of Interrupts Enabled by the UIE Instruction

1 bit 0 (reserved)
To enable interrupt(s):
1. Select which interrupts you want to enable.
4. Enter the sum into the UIE instruction.
For example, to enable EII Event 1 and EII Event 3:

UIF - User Interrupt Flush

UIF
Enable UIF (name or Pin ID)

The UIF instruction is used to flush (remove pending interrupts from the
system) selected user interrupts. The table below shows the types of interrupts
with their corresponding flush bits:

Table 62 - Types of Interrupts Disabled by the UIF Instruction

To flush interrupt(s):
1. Select which interrupts you want to flush.
4. Enter the sum into the UIF instruction.
For example, to disable EII Event 1 and EII Event 3:

UIC – User Interrupt Clear

UIC
Enable UIC (name or Pin ID)

This C function clears Interrupt Lost bit for the selected User Interrupt(s).

Table 63 - Types of Interrupts Disabled by the UIC Instruction

Using the Selectable Timed Configure the STI function from the Interrupt Configuration window.
Interrupt (STI) Function
The Selectable Timed Interrupt (STI) provides a mechanism to solve time

critical control requirements. The STI is a trigger mechanism that allows you
to scan or solve control program logic that is time sensitive.
Example of where you would use the STI are:

• PID type applications, where a calculation must be performed at a

specific time interval.
• A block of logic that needs to be scanned more often.
How an STI is used is typically driven by the demands/requirements of the

application. It operates using the following sequence:
1. The user selects a time interval.
2. When a valid interval is set and the STI is properly configured, the
controller monitors the STI value.
3. When the time period has elapsed, the controller’s normal operation is
interrupted.
4. The controller then scans the logic in the STI POU.
5. When the STI POU is completed, the controller returns to where it was
prior to the interrupt and continues normal operation.
Selectable Time Interrupt This section covers the configuration and status management of the STI
(STI) Function function.
Configuration and Status
STI Function Configuration
STI Program POU
immediately when this STI Interrupt occurs. You can choose any pre-
STI Auto Start (STI0.AS)
Sub-Element Description Data Format User Program Access

AS - Auto Start binary (bit) read only
The AS (Auto Start) is a control bit that can be used in the control program. The
auto start bit is configured with the programming device and stored as part of
the user program. The auto start bit automatically sets the STI Timed Interrupt
Enable (STI0.Enabled) bit when the controller enters any executing mode.
STI Set Point Milliseconds Between Interrupts (STI0.SP)
Sub-Element Description Data Format Range User Program Access

SP - Set Point Msec word (INT) 0…65,535 read/write
When the controller transitions to an executing mode, the SP (set point in

milliseconds) value is loaded into the STI. If the STI is configured correctly,
and enabled, the POU in the STI configuration is executed at this interval. This
value can be changed from the control program by using the STIS instruction.
The minimum value cannot be less than the time required to scan the STI
POUplus the Interrupt Latency.

STI Function Status Information
STI Function status bits can be monitored either in the User Program, or in the
Connected Components Workbench software, in Debug mode.
STI User Interrupt Executing (STI0.EX)

EX - User Interrupt Executing binary (bit) read only
The EX (User Interrupt Executing) bit is set whenever the STI mechanism
completes timing and the controller is scanning the STI POU. The EX bit is
cleared when the controller completes processing the STI subroutine.
The STI EX bit can be used in the control program as conditional logic to detect
if an STI interrupt is executing.
STI User Interrupt Enable (STI0.Enabled)

Enabled - User Interrupt Enable binary (bit) read only
The User Interrupt Enable bit is used to indicate STI enable or disable status.
STI User Interrupt Lost (STI0.LS)

LS - User Interrupt Lost binary (bit) read/write
The LS is a status flag that indicates an interrupt was lost. The controller can
process 1 active and maintain up to 1 pending user interrupt conditions before
it sets the lost bit.
This bit is set by the controller. It is up to the control program to utilize, track,
the lost condition if necessary.
STI User Interrupt Pending (STI0.PE)

PE - User Interrupt Pending binary (bit) read only
The PE is a status flag that represents an interrupt is pending. This status bit
can be monitored or used for logic purposes in the control program if you need
to determine when a subroutine cannot execute immediately.
This bit is automatically set and cleared by the controller. The controller can
Using the Event Input The EII (Event Input Interrupt) is a feature that allows the user to scan a
Interrupt (EII) Function specific POU when an input condition is detected from a field device.
EII0 is used in this document to define how EII works.

Configure EII Input Edge from the Embedded I/O configuration window.
Configure the EII from the Interrupt Configuration window.
Event Input Interrupt (EII) EII Function Configuration

Function Configuration and
Status The Event Input Interrupt Function has the following related configuration
parameters.
EII Program POU
immediately when this EII Interrupt occurs. You can choose any pre-
EII Auto Start (EII0.AS)

AS - Auto Start binary (bit) read only
AS (Auto Start) is a control bit that can be used in the control program. The
auto start bit is configured with the programming device and stored as part of
the user program. The auto start bit automatically sets the Event User
Interrupt Enable bit when the controller enters any executing mode.
EII Input Select (EII0.IS)

IS - Input Select word (INT) read only
The IS (Input Select) parameter is used to configure each EII to a specific input
on the controller. Valid inputs are 0…N, where N is either 15, or the maximum
input ID, whichever is smaller.
This parameter is configured with the programming device and cannot be

changed from the control program.

EII Function Status Information
EII Function status bits can be monitored either in the User Program, or in the
Connected Components Workbench software, in Debug mode.
EII User Interrupt Executing (EII0.EX)

EX - User Interrupt Executing binary (bit) read only
The EX (User Interrupt Executing) bit is set whenever the EII mechanism
detects a valid input and the controller is scanning the EII POU. The EII
mechanism clears the EX bit when the controller completes its processing of
the EII subroutine.
The EII EX bit can be used in the control program as conditional logic to detect
if an EII interrupt is executing.
EII User Interrupt Enable (EII0.Enabled)

Enabled - User Interrupt Enable binary (bit) read only
The Enabled (User Interrupt Enable) bit is used to indicate the EII enable or
disable status.
EII User Interrupt Lost (EII0.LS)

LS - User Interrupt Lost binary (bit) read/write
LS (User Interrupt Lost) is a status flag that represents an interrupt has been
lost. The controller can process 1 active and maintain up to 1 pending user
interrupt conditions before it sets the lost bit.
This bit is set by the controller. It is up to the control program to utilize or

track, the lost condition if necessary.
EII User Interrupt Pending (EII0.PE)

PE - User Interrupt Pending binary (bit) read only
PE (User Interrupt Pending) is a status flag that represents an interrupt is

pending. This status bit can be monitored, or used for logic purposes, in the
control program if you need to determine when a subroutine cannot execute
immediately.
This bit is automatically set and cleared by the controller. The controller can

Notes:

Appendix D
Troubleshooting
Status Indicators on the Micro830 Controllers

Controller 10/16-point Controllers 24-point Controllers 48-point Controllers
1 1 1
2
3 2
4 2 3
3
5 4 4
6 5 5
6 6
7
7 7
24-point Controllers 48-point Controllers
1 1
8
8 9
9 2
2 3
3 4
4
5 5
6 6
7 7
24-point Controllers
8
9
2
3
4
5
6

Appendix D Troubleshooting
Status Indicator Description

Description State Indicates
Off Input is not energized
1 Input status
On Input is energized (terminal status)
Off No input power, or power error condition
2 Power status
Green Power on
Off Not executing the user program
3 Run status Green Executing the user program in run mode
Flashing green Memory backup/restore in progress
Off No fault detected.
4 Fault status Red Non-recoverable fault that requires a power cycle.
Flashing Red Recoverable fault.
Off No force conditions are active.
5 Force status
Amber Force conditions are active.
Off No traffic for RS-232/RS-485.
Serial communications Traffic through RS-232/RS-485.
6 status Green The indicator only blinks when transmitting data. It does not
blink when receiving data.
Off Output is not energized.
7 Output status
On Output is energized (logic status).
Steady Off No power.
Flashing Green Standby.
Steady Green Device operational.
Minor fault
Flashing Red (minor and major recoverable faults).
8 Module status
Steady Red Major Fault (non-recoverable fault).
Self-test.
The device is performing power-on self-test (POST). During
Flashing Green and POST, the network status indicator alternates flashing green
Red and red. The duration of the self-test depends on the size of
the project in the controller.
Not powered, no IP address.
Steady Off The device is powered off, or is powered on but with no IP
address.
No connections.
Flashing Green An IP address is configured, but no Ethernet application is
connected.
Connected.
Steady Green At least one EtherNet/IP session is established.
Flashing Red Connection timeout (not implemented).
9 Network status
Duplicate IP.
The device has detected that its IP address is being used by
Steady Red another device in the network. This status is applicable only
if the device's duplicate IP address detection (ACD) feature
is enabled.
Self-test.
The device is performing power-on self-test (POST). During
Flashing Green and POST, the network status indicator alternates flashing green
Red and red. The duration of the self-test depends on the size of
the project in the controller.

Normal Operation
The POWER and RUN indicators are on. If a force condition is active, the
FORCE indicator turns on and remains on until all forces are removed.
Error Codes This section lists possible error codes for your controller, as well as
recommended actions for recovery. Information about the fault is stored in a
fault log, which can be accessed from the Diagnostics page in Connected
Components Workbench software. The fault log contains brief information
about the last fault, and detailed information about the last 10 non-recoverable
faults that occurred.
If an error persists after performing the recommended action, contact your

local Rockwell Automation technical support representative. For contact
information, go to rok.auto/support.
Fault Types
There are two basic types of faults that can occur:

• Recoverable – A recoverable fault can be cleared without having to power
cycle the controller. The fault LED flashes red when a recoverable fault
occurs.
• Non-recoverable – A non-recoverable fault requires the controller to be
power cycled before clearing the fault. After the controller has been
power cycled or reset, check the fault log in the Diagnostic page of the
Connected Components Workbench software, then clear the fault. The
fault LED is solid red when a non-recoverable fault occurs.
Table 64 - List of Error Codes for Micro800 controllers
Error Code Fault Type Description Recommended Action
The controller was unexpectedly reset due to a noisy
environment or an internal hardware failure. Perform one of the following:
If the system variable _SYSVA_USER_DATA_LOST is • See Corrective Actions for Recoverable Faults on page 310.
0xF000 Recoverable set, the controller is able to recover the user
program but the user data is cleared. If not, the • Check wiring to eliminate any noise.
Micro800 controller program is cleared.
The controller program has been cleared. This
happened because:
• a power-down occurred during program Perform one of the following:
download or data transfer from the memory
0xF001 Recoverable module • See Corrective Actions for Recoverable Faults on page 310.
• the cable was removed from the controller during • Transfer the program using the memory module restore utility.
program download.
• the RAM integrity test failed.
The controller hardware watchdog was activated.
The controller hardware watchdog timeout happens
if program scan is more than 3 seconds.
Non-
0xF002 If the system variable _SYSVA_USER_DATA_LOST is See Corrective Actions for Non-recoverable Faults on page 310.
recoverable set, the controller is able to recover the user
program but the user data is cleared. If not, the

Table 64 - List of Error Codes for Micro800 controllers (Continued)

Perform one of the following:
One of the following occurred: • Remove the memory module and plug it in again.
• The memory module hardware faulted. • Obtain a new memory module.
0xF003 Recoverable • The memory module connection faulted. • See Corrective Actions for Recoverable Faults on page 310.
• The memory module was incompatible with the • Upgrade the Micro800 controller’s firmware revision to be compatible with the
Micro800 controller’s firmware revision. memory module. For information on firmware revision compatibility, go to rok.auto/
pcdc.
A failure occurred during the memory module data • See Corrective Actions for Recoverable Faults on page 310.
0xF004 Recoverable transfer. • Attempt the data transfer again. If the error persists, replace the memory module.
• For Embedded RTC failure, restart the controller.
The user program failed an integrity check while the • See Corrective Actions for Recoverable Faults on page 310.
0xF005 Recoverable Micro800 controller was in Run mode.
• Check wiring.
The user program is incompatible with the Micro800 • See Corrective Actions for Recoverable Faults on page 310.
0xF006 Recoverable controller’s firmware revision.
• Contact your local Rockwell Automation technical support representative.
The user program contains a function/function block • See Corrective Actions for Recoverable Faults on page 310.
0xF010 Recoverable that is not supported by the Micro800 controller.
• Contact your local Rockwell Automation technical support representative.
• See Corrective Actions for Recoverable Faults on page 310.
0xF014 Recoverable A memory module memory error occurred.
• Reprogram the memory module. If the error persists, replace the memory module.
Non-
0xF015 An unexpected software error occurred. • See Corrective Actions for Non-recoverable Faults on page 310.
recoverable
• Check wiring.
Non-
0xF016 An unexpected hardware error occurred. • See Corrective Actions for Non-recoverable Faults on page 310.
recoverable
• Check wiring.
An unexpected software error occurred due to
unexpected hardware interrupt. Perform one of the following:
Non- If the system variable _SYSVA_USER_DATA_LOST is
0xF017 • See Corrective Actions for Non-recoverable Faults on page 310.
program but the user data is cleared. If not, the • Check wiring.
An unexpected software error occurred due to SPI
communication failure. Perform one of the following:
Non- If the system variable _SYSVA_USER_DATA_LOST is
0xF018 • See Corrective Actions for Non-recoverable Faults on page 310.
program but the user data is cleared. If not, the • Check wiring.
Non- An unexpected software error occurred due to
0xF019 See Corrective Actions for Non-recoverable Faults on page 310.
recoverable memory or other controller resource issue.
The controller was unexpectedly reset during Run
Mode Change (RMC) due to a noisy environment or an
internal hardware failure.
0xF01A Recoverable If the system variable _SYSVA_USER_DATA_LOST is See Corrective Actions for Recoverable Faults on page 310.
set, the controller is able to recover the user
program but the user data is cleared. If not, the
The base hardware faulted or is incompatible with
0xF020 Recoverable See Corrective Actions for Recoverable Faults on page 310.
the Micro800 controller’s firmware revision.
The I/O configuration in the user program is invalid
or does not exist in the Micro800 controller.
The user program in the memory module is Perform one of the following:
0xF022 Recoverable incompatiblewiththeMicro800controller’sfirmware • See Corrective Actions for Recoverable Faults on page 310.
revision. • Replace the memory module.


The controller program has been cleared. This
happened because: Perform one of the following:
Non-
0xF023 • a power down occurred during program download • See Corrective Actions for Non-recoverable Faults on page 310.
recoverable or transfer from the memory module. • Download or transfer the program.
• the Flash Integrity Test failed (Micro810 only).
Power down information in persistent memory may
not be written properly due to a noisy environment
0xF030 or an internal hardware failure.
0xF031 Recoverable If the system variable _SYSVA_USER_DATA_LOST is See Corrective Actions for Recoverable Faults on page 310.
0xF032 set, the controller is able to recover the user
0xF033 program but the user data is cleared. If not, the
The embedded I/O configuration in the user program See Corrective Actions for Recoverable Faults
0xF050 Recoverable on page 310.
is invalid.
There is general configuration error detected in the
motion configuration downloaded from the Perform the following:
0xF100 Recoverable Connected Components Workbench software, such • See Corrective Actions for Recoverable Faults on page 310.
as number of axis, or motion execution interval being • Correct the axes configuration in the user program.
configured out of range.
Perform the following:
There is motion resource missing, such as
0xF110 Recoverable • See Corrective Actions for Recoverable Faults on page 310.
Motion_DIAG variable not defined.
• Correct the axes configuration in the user program.
Motion configuration for axis z cannot be supported Perform the following:
by this controller model, or the axis configuration has • See Corrective Actions for Recoverable Faults on page 310.
0xF12z(1) Recoverable some resource conflict with some other motion axis,
which has been configured earlier. • Remove all axes and reconfigure motion with the guidance from the User Manual.
There is a motion engine logic error (firmware logic

(1) issue or memory crash) for one axis detected during See Corrective Actions for Recoverable Faults on page 310.
0xF15z Recoverable motion engine cyclic operation. One possible reason
can be motion engine data/memory crash.
1. Power off the controller.
0xF210 Recoverable The expansion I/O terminator is missing. 2. Attach the expansion I/O terminator on the last expansion I/O module on the system.
3. Power on the controller.
4. See Corrective Actions for Recoverable Faults on page 310.
1. Power off the controller.
The maximum number of expansion I/O modules has 2. Check that the number of expansion I/O modules is not more than four.
0xF230 Recoverable been exceeded.
3. Power on the controller.
There is a non-recoverable error and the expansion
I/O module(s) could not be detected.
An expansion I/O master fault is detected on the
0xF26z(2) Recoverable system. See Corrective Actions for Recoverable Faults on page 310.

A non-recoverable communication fault has
0xF27z(2) Recoverable occurred on the expansion I/O module. • See Corrective Actions for Recoverable Faults on page 310.
• Replace the slot number z module.
0xF28z(2) Recoverable Expansion I/O baudrate error. • See Corrective Actions for Recoverable Faults on page 310.
A module fault is detected on your expansion I/O
0xF29z(2) Recoverable module. • See Corrective Actions for Recoverable Faults on page 310.
0xF2Az(2) Recoverable Expansion I/O power failure • See Corrective Actions for Recoverable Faults on page 310.


• Correct the expansion IO module configuration in the user program to match that of
0xF2Bz(2) Recoverable Expansion I/O configuration fault. the actual hardware configuration.
• Check the expansion I/O module operation and condition.
• Replace the expansion I/O module.
The memory module is present but memory module • See Corrective Actions for Recoverable Faults on page 310.
0xF300 Recoverable is empty and restore operation is requested. • Check to make sure there is a valid project in the memory module.
• Download a user program and use the backup function to the memory module.
The memory module’s project is not compatible with
0xF301 Recoverable • Check to make sure there is a user program with a controller that has the correct
the controller.
controller catalog configured.
• Download a user program and use the backup function to the memory module.
The password is mismatched between memory • See Corrective Actions for Recoverable Faults on page 310.
module and controller. Only applies to Micro820 • Check to make sure that the user program in the memory module has the correct
controller when Remote LCD performs the restore password.
0xF302 Recoverable operation. • Download a user program with a password and use the backup function to the
This fault does not apply to Micro800 controller memory module.
firmware revision 10 and later. • Use Connected Components Workbench software to enter the correct password into
the controller and perform the restore operation again.
The memory module is not present and restore
0xF303 Recoverable Check to make sure the memory module is present.
operation is requested.
The plug-in I/O module experienced an error during
0xF0Az(3) Recoverable operation. • Check the condition and operation of the plug-in I/O module.
The plug-in I/O module configuration does not match • Correct the plug-in I/O module configuration in the user program to match that of the
0xF0Bz(3) Recoverable the actual I/O configuration detected. actual hardware configuration.
• Check the condition and operation of the plug-in I/O module.
• Replace the plug-in I/O module.
When power was applied to the plug-in I/O module 1. See Corrective Actions for Recoverable Faults on page 310.
0xF0Dz(3) Recoverable or the plug-in I/O module was removed, a hardware 2. Correct the plug-in I/O module configuration in the user program.
error occurred. 3. Build and download the program using Connected Components Workbench software.
4. Put the Micro800 controller into Run mode.
The plug-in I/O module configuration does not match
0xF0Ez(3) Recoverable the actual I/O configuration detected. 2. Correct the plug-in I/O module configuration in the user program.
3. Build and download the program using Connected Components Workbench software.
0xF830 Recoverable An error occurred in the EII configuration. • See Corrective Actions for Recoverable Faults on page 310.
• Review and change the EII configuration in the Micro800 controller properties.
0xF840 Recoverable An error occurred in the HSC configuration. • See Corrective Actions for Recoverable Faults on page 310.
0xF850 Recoverable An error occurred in the STI configuration. • See Corrective Actions for Recoverable Faults on page 310.
A data overflow occurred. 1. See Corrective Actions for Recoverable Faults on page 310.
A data overflow error is generated when the ladder, 2. Correct the program to ensure that there is no data overflow.
0xF860 Recoverable structured text, or function block diagram execution
encounters a divide-by-zero. 3. Build and download the program using Connected Components Workbench software.


2. Correct the program to ensure that there is no index used to access an array element
0xF870 Recoverable An index address was out of data space. beyond the array boundaries.
An index used to access a bit is beyond the 2. Correct the program to ensure that there is no index used to access a bit beyond the
0xF0878 Recoverable boundaries of the data type it is used on. boundaries of the data type.
0xF880 Recoverable A data conversion error occurred. 2. Correct the program to ensure that there is no data conversion error.
The call stack of the controller cannot support the Perform the following:
0xF888 Recoverable sequence of calls to function blocks in the current • See Corrective Actions for Recoverable Faults on page 310.
project. Too many blocks are within another block. • Change the project to reduce the quantity of blocks being called within a block.
An error occurred in the user interrupt configuration • See Corrective Actions for Recoverable Faults on page 310.
0xF898 Recoverable for the plug-in I/O module. • Correct the user interrupt configuration for plug-in I/O module in the user program to
match that of the actual hardware configuration.
0xF8A0 Recoverable The TOW parameters are invalid. 2. Correct the program to ensure that there are no invalid parameters.
0xF8A1 Recoverable The DOY parameters are invalid. 2. Correct the program to ensure that there are no invalid parameters.
A user-created fault from the Connected
0xFFzz(4) Recoverable Components Workbench software has occurred. See Corrective Actions for Recoverable Faults on page 310.
A particular hardware type (for example, embedded

0xD00F Recoverable I/O) was selected in the user program configuration, See Corrective Actions for Recoverable Faults on page 310.
but did not match the actual hardware base.
• Determine if the program is caught in a loop and correct the problem.
Fault may occur if your Structured Text program contains a For loop with the upper limit
set to the maximum value of the variable. For example, the variable is a USINT and the
limit is set to 255, or the variable is a UINT and the limit is set to 65535.
To correct the fault, perform the following:
The program scan time exceeded the watchdog
0xD011 Recoverable 1. Correct the program to ensure that the upper limit is not reached. One method is to
timeout value.
use a data type with a larger maximum value.
If your program is designed to have a scan time of longer than 3 seconds, in the user
program, increase the watchdog timeout value that is set in the system variable
_SYSVA_TCYWDG and then build and download the program using Connected
(1) z indicates the logic axis ID. (0...3)
(2) z indicates the slot number of the expansion I/O. If z=0, then the slot number cannot be identified.
(3) z is the slot number of the plug-in module. If z = 0, then the slot number cannot be identified.
(4) zz indicates the last byte of the program number. Only program numbers up to 0xFF can be displayed. For program numbers 01x00 to 0xFFFF, only the last byte is displayed.)

Corrective Action for Recoverable and Non-recoverable Faults
Corrective Actions for Recoverable Faults

1. Optionally save the fault log from Connected Components Workbench
software.
2. Clear the recoverable fault using Connected Components Workbench
software.
3. If problem persists, contact technical support with the fault log.
Corrective Actions for Non-recoverable Faults

1. Power cycle your Micro800 controller.
2. Controller will go to recoverable fault. Optionally save the fault log from
3. Clear the recoverable fault using Connected Components Workbench
software.
4. If program is lost, build and download your program using Connected
5. If problem persists, contact technical support with the fault log.
Retrieve a Fault Log You can retrieve a fault log for your controller by using the Connected
Components Workbench software, version 9 or later.

2. Connect to your Micro800 controller.
3. In Project Organizer, right-click the Micro800 controller.
4. Select Diagnose > Fault.
The Fault Diagnostics tab displays.
5. Click the Get Fault Log button.
6. Save the fault log (.txt) file.
Controller Error Recovery Use the following error recovery model to help you diagnose software and
Model hardware problems in the micro controller. The model provides common
questions you might ask to help troubleshoot your system. See the
recommended pages within the model for further help.

Start
Is the Power No
LED on? Check the wiring.
Yes
Check the Fault LED.

Flashing red = Recoverable
Solid red = Non-recoverable
No
Is fault recoverable? Power cycle the controller.
Yes
Diagnose fault in Connected Components

Workbench software and see page 305 for
probable cause and recommended action.
Clear the fault.
Correct the condition

causing the fault.
Test and verify

system operation.
End
Calling Rockwell If you need to contact Rockwell Automation or local distributor for assistance,
Automation for Assistance it is helpful to obtain the following (prior to calling):
• controller type, series letter, revision letter, and firmware (FRN) number
of the controller
• controller indicator status

Notes:

Appendix E
PID Function Blocks
The PID function block has parameter naming similar to RSLogix 500 and is
recommended for users who are already familiar with programming in
RSLogix 500. The IPIDCONTROLLER function block has the advantage of
supporting auto tune.
Table 65 - Comparison Between IPIDCONTROLLER and PID

IPIDCONTROLLER PID Description
Common parameters
Process PV Process Variable feedback
Setpoint SP Set Point input
Output CV CV output
Gains.DirectActing Control Control direction of process (cooling versus heating).
Gains.ProportionalGain Gains.Kc Controller gain for both P and I
Gains.TimeIntegral Gains.Ti Time integral value for I
Gains.TimeDerivative Gains.Td Time derivative value for D
A higher filter constant makes CV output more
Gains.DerivativeGain Gains.FC responsive to error. Acts like a derivative gain.
AbsoluteError AbsoluteError Absolute value of error
PID-specific parameters
CVMin For limiting CV
CVMax For limiting CV
TRUE = Normal operation of PID.
AutoManual FALSE = Manual operation using CVManual.
CVManual CV when in manual mode
– TRUE = Start execution with current input parameters.
Enable FALSE = CV equals zero.
TRUE = PID state is running.
Active FALSE = PID state is stopped.
TRUE = PID has an error.
Error FALSE = PID has no errors.
ErrorID PID Error ID

Appendix E PID Function Blocks
Table 65 - Comparison Between IPIDCONTROLLER and PID (Continued)

IPIDCONTROLLER PID Description
IPIDCONTROLLER-specific parameters
TRUE = Normal operation of PID.
Auto FALSE = Output tracks Feedback.
Feedback of the control being applied to the process.
Feedback Usually it’s the PID’s CV after any limits or manual
control has been applied.
TRUE = Autotune.
AutoTune – FALSE = No Autotune.
ATParameters Autotune parameters
ATWarning Autotune warning
OutGains Gains from Autotune
Initialize Used for AutoTune
PID Function Block This function block diagram shows the arguments in the PID function block.
PID
Enable Active
PV CV
SP AbsoluteError
AutoManual Error
CVManual Error ID
CVMax
CVMin
Gains
Control
Llnit
The following table explains the arguments used in this function block.
Table 66 - PID Arguments

Parameter
Type
Enable instruction.
Enable Input BOOL TRUE = Start execution with current input parameters.
FALSE = CV equals zero.
Process Value. This value is typically read from an analog input

PV Input REAL module.
The SI unit must be the same as Setpoint.
SP Input REAL The set point value for the process.
Auto or manual mode selection:
AutoManual Input BOOL TRUE = Normal operation of PID.
FALSE = Manual operation using CVManual.
Control value input defined for manual mode operation. The
CVManual Input REAL valid range for CVManual is:
CVMin < CVManual < CVMax
Control value minimum limit.
CVMin Input REAL If CV < CVMin, then CV = CVMin.
If CVMin > CVMax, and error occurs.
Control value maximum limit.
CVMax Input REAL If CV > CVMax, then CV = CVMax.
If CVMax < CVMin, an error occurs.

Table 66 - PID Arguments (Continued)

Parameter
Type
Gains of PID for controller.
Gains Input PID_GAINS Use the PID_GAINS data type to configure the Gains parameter.
Control direction of the process:
Control Input BOOL TRUE = Direct acting, such as Cooling.
FALSE = Reverse acting, such as Heating.
Llnit Input BOOL Reserved for future use.
Status of the PID controller:
Active Output BOOL TRUE = PID state is running.
FALSE = PID state is stopped.
The control value output.
CV Output REAL If any error occurred, CV is 0.
Absolute error is the difference between process value (PV) and
AbsoluteError Output REAL setpoint (SV) value.
Indicates the existence of an error condition.
Error Output BOOL TRUE = PID has an error.
FALSE = PID has no errors.
A unique numeric that identifies the error. The errors are
ErrorID Output USINT defined in PID error codes.
Table 67 - GAIN_PID Data Type

Parameter
Type
Controller gain for PID.
Proportional and Integral are dependent on this gain (>=
0.0001).
Kc Input REAL Increasing Kc improves response time but also increases
overshoot and oscillation of the PID.
If Kc is invalid, an error occurs.
Time integral constant in seconds (>= 0.0001).
Ti Input REAL Increasing Ti decreases overshoot and oscillation of the PID.
If Ti is invalid, an error occurs.
Time derivative constant in seconds (>= 0.0).
When Td equals 0, then there is no derivative action and PID
becomes a PI controller.
Td Input REAL Increasing Td reduces the overshot and removes the oscillation
of the PID controller.
If Td is invalid, an error occurs.
Filter constant (>= 0.0).
Recommended range for FC is 0...20.
FC Input REAL Increasing FC smooths the response of the PID controller.
If FC is invalid, an error occurs.
Table 68 - PID Error Codes

Error Code Description
0 PID is working normally.
1 Kc is invalid.
2 Ti is invalid.
3 Td is invalid.
4 FC is invalid.

Table 68 - PID Error Codes (Continued)

Error Code Description
5 CVMin > CVMax, or CVMax < CVMin
CVManual < CVMin
6 CVManaul is invalid.
CVManual > CVMax
7 CVManual is invalid.
IPIDCONTROLLER Function This function block diagram shows the arguments in the IPIDCONTROLLER
Block function block.
IPIDCONTROLLER
EN ENO
Process Output
SetPoint AbsoluteError
FeedBack ATWarning
Auto OutGains
Initialize
Gains
AutoTune
ATParameters
The following table explains the arguments used in this function block.
Table 69 - IPIDCONTROLLER Arguments

Parameter
Type
Function block enable
TRUE = Execute function.
EN Input BOOL FALSE = Do not execute function.
Applicable to Ladder Diagram programs.
Process value, which is the value measured from the process
Process Input REAL output.
SetPoint Input REAL The set point value for the process.
Feedback signal, which is the value of the control variable
Feedback Input REAL applied to the process.
For example, the feedback can be IPIDCONTROLLER output.
Operating modes of PID controller:
Auto Input BOOL TRUE = Normal operation of PID.
FALSE = Output tracks Feedback.
A change in value (TRUE to FALSE or FALSE to TRUE) causes the
Initialize Input BOOL controller to eliminate any proportional gain during that cycle. It
also initializes AutoTune sequences.
Gains PID for IPIDCONTROLLER.
Gains Input GAIN_PID Use the GAIN_PID data type to define the parameters for the
Gains input.
TRUE = Autotune.
AutoTune Input BOOL FALSE = No Autotune.
AutoTune parameters
ATParameters Input AT_Param Use AT_Param data type to define the parameters for the
ATParameters input.
Output Output Real Output value from the controller.
AbsoluteError Output Real Absolute error (Process - SetPoint) from the controller.

Table 69 - IPIDCONTROLLER Arguments (Continued)

Parameter
Type
Warning for the AutoTune sequence. Possible values are:
0 = No auto tune done.
1 = In auto tune mode.
ATWarnings Output DINT 2 = Auto tune done.
-1 = Error 1: Input automatically set to TRUE, no auto tune
possible.
-2 = Error 2: Auto tune error, the ATDynamSet expired.
Gains calculated from AutoTune Sequences.
OutGains Output GAIN_PID Use GAIN_PID data type to define the OutGains output.
Enable output.
ENO Output BOOL Applicable to Ladder Diagram programs.
Table 70 - GAIN_PID Data Type

Parameter Type Description
Types of acting:
TRUE = Direct acting, output moves same direction as error. That is, the actual
process value is greater than the SetPoint and the appropriate controller action is
DirectActing BOOL to increase the output. For example, Chilling.
FALSE = Reverse acting, output moves opposite direction as error. That is, the
actual process value is greater than the Setpoint and the appropriate controller
action is to decrease the output. For example, Heating.
Proportional gain for PID (>= 0.0001).
Proportional gain for PID (P_Gain)
A higher proportional gain causes a larger change in the output based on the
difference between the PV (measured process value) and SV (set point value).
ProportionalGain REAL The higher the gain, the faster the error is decreased, but this may result in
instability such as oscillations. The lower the gain, the slower the error is
decreased, but the system is more stable and less sensitive to large errors. The
P_Gain usually is the most important gain to adjust and the first gain to adjust
while tuning.
Time integral value for PID (>= 0.0001).
Time integral value for PID
A smaller integral time constant causes a faster change in the output based on
the difference between the PV (measured process value) and SV (set point value)
TimeIntegral REAL integrated over this time. A smaller integral time constant decreases the steady
state error (error when SV is not being changed) but increases the chances of
instability such as oscillations. A larger integral time constant slows down the
response of the system and make it more stable, but PV approaches the SV at a
slower rate.
Time derivative value for PID (> 0.0).
Time derivative value for PID (Td)
A smaller derivative time constant causes a faster change in the output based on
the rate of change of the difference between PV (measured process value) and
SV (set point value). A smaller derivative time constant makes a system more
TimeDerivative REAL responsive to sudden changes in error (SV is changed) but increases the chances
of instability such as oscillations. A larger time constant makes a system less
responsive to sudden changes in error and the system is less susceptible to
noise and step changes in PV. TimeDerivative (Td) is related to the derivative gain
but allows the derivative contribution to PID to be tuned using time so the sample
time must be taken into consideration.
Derivative gain for PID (>= 0.0).
Derivative gain for PID (D_Gain)
A higher derivative gain causes a larger change in the output based on the rate of
change of the difference between the PV (measured process value) and SV (set
point value). A higher gain makes a system more responsive to sudden changes
DerivativeGain REAL in error but increases the chances of instability such as oscillations. A lower gain
makes a system less responsive to sudden changes in error and makes the
system less susceptible to noise and step changes in the PV.
If derivative gain is set to zero, it disables the derivative portion of the
PID.

Table 71 - AT_Param Data Type

Parameter Type Description
Load REAL Load parameter for auto tuning. This is the output value when starting AutoTune.
Deviation for auto tuning. This is the standard deviation used to evaluate the
Deviation REAL
noise band needed for AutoTune (noise band = 3* Deviation)(1)
Step REAL Step value for AutoTune. Must be greater than noise band and less than ½ load.
ATDynamSet REAL Waiting time in seconds before abandoning auto tune.
Determines whether the output value is reset to zero after an AutoTune
sequence:
ATReset BOOL TRUE = Reset output to zero.
FALSE = Leaves output at Load value.
(1) The application engineer can estimate the value of ATParams.Deviation by observing the value of Process input. For example,
in a project that involves the control of temperature, if the temperature stabilizes around 22 °C, and a fluctuation of
21.7…22.5 °C is observed, the value of ATParams.Deviation will be (22.5…21.7)/2=0.4.
How to Autotune Before you autotune, you need to:

• Verify that your system is constant when there is no control. For
example, for temperature control, process value should remain at room
temperature when there is no control output.
• Configure the set point to 0.
• Set Auto Input to False.
• Set the Gain parameter as follows:
Table 72 - GAIN Parameter Values

GAIN Parameter Value
According to operation:
DirectActing TRUE (for example, Cooling), or
FALSE (for example, Heating)
DerivativeGain 0.5
ProportionalGain 0.0001
TimeIntegral 0.0001
TimeDerivative 0.0
• Set the AT_Parameter as follows:
Table 73 - AT_Parameter Values

AT Parameter Recommendation
Every ‘Load’ provides a saturated process value over a period of time. Adjust the load to the
value for the saturated process value you want.
Load
IMPORTANT: If a load of 40 gives you a process value of 30 °C over a period of time, and you
want to tune your system to 30 °C, you should set the load to 40.
This parameter plays a significant role in the autotune process. The method of deriving this
Deviation value is explained later in this section. It is not necessary to set this parameter prior to
autotuning. However, if you already know the deviation, it is fine to set it first.

Table 73 - AT_Parameter Values (Continued)

AT Parameter Recommendation
Step value should be between 3*Deviation and ½ load. The step provides an offset for the
Step load during autotuning. It should be set to a value high enough to create a significant change
in process value.
Set this value to a reasonably long time for the autotune process. Every system is different,
ATDynamSet so allow more time to a system with a process value that takes longer to react to change.
Set this parameter to TRUE to reset the output to zero after the autotune process completes.
ATReset Set this parameter to FALSE to leave the output at load value after the autotune process
completes.
During autotune, the controller will automatically set the process value to zero.
To autotune, perform the following steps:
1. Set the Initialize input to TRUE.
2. Set the AutoTune input to TRUE.
3. Wait for the Process input to stabilize or reach a steady state.
4. Note the temperature fluctuation of the process value.
5. Calculate deviation value with reference to the fluctuation. For example,
if the temperature stabilizes around 22 °C (72 °F) with a fluctuation of
21.7…22.5 °C (71…72.5 °F), the value of ‘ATParams.Deviation’ is:
22.5...21.7 72.5...71
For °C: = 0.4 For °F: = 0.75
2 2
6. Set the deviation value, if you have not set it yet.

7. Change the initialize input to FALSE.
8. Wait until the ‘AT_Warning’ shows 2. The autotune process is successful.
9. Get the tuned value from the ‘OutGains’.
How Autotune Works
The auto tune process begins when the ‘Initialize’ is set to FALSE (Step 7.) At
this moment, the control output increases by the amount of ‘Step’ and the
process waits for the process value to reach or exceeds ‘first peak’.
First peak is defined as:
For Direct Operation: First peak = PV1 - (12 x Deviation)

For Reverse Operation: First peak = PV1 + (12 x Deviation)
Where PV1 is the process value when Initialize is set to FALSE.
Once the process value reaches first peak, the control output reduces by the
amount of Step and waits for the process value to drop to the second peak.
Second peak is defined as:
For Direct Operation: Second peak = PV1 - (3 x Deviation)

For Reverse Operation: Second peak = PV1 + (3 x Deviation)
Once the process value reaches or falls below second peak, calculations
commence and a set of gain will be generated to parameter OutGains.

Troubleshooting an You can tell what is going on behind the autotune process from the sequences
Autotune Process of control output. Here are some known sequences of control output and what
it means if autotune fails. For the ease of illustrating the sequence of control
output, we define:
• Load: 50
• Step: 20
Output Sequence 1: 50 → 70 → 30
Sequence Condition Autotune Result Action for Autotune Fail
Process value reached 'first peak' and 'second' Likely successful NA
peak in time
Output Sequence 2: 50 → 70 → 50
Process value not able to reach 'first peak' Likely unsuccessful Reduce Deviation or Increase Step
Output Sequence 3: 50 → 70 → 30 → 50
Process value not able to reach second peak Likely unsuccessful Increase Deviation or increase Step
Output Sequence 4: 50 → 70
Process value not able to reach First peak in Likely unsuccessful Increase ATDynamSet
time
PID Application Example

Water In
Water Level
Tank Water Out
The illustration above shows a basic water level control system, to maintain a
preset water level in the tank. A solenoid valve is used to control incoming
water, filling the tank at a preset rate. Similarly, outflowing water is controlled
at a measurable rate.
IPID Autotuning for First and Second Order Systems
Autotune of IPID can only work on first and second order systems.
A first order system can be described by a single independent energy storage

element. Examples of first order systems are the cooling of a fluid tank, the

flow of fluid from a tank, a motor with constant torque driving a disk flywheel
or an electric RC lead network. The energy storage element for these systems
are heat energy, potential energy, rotational kinetic energy and capacitive
storage energy, respectively.
This may be written in a standard form such as f(t) = dy/dt + y(t), where  is
the system time constant, f is the forcing function and y is the system state
variable.
In the cooling of a fluid tank example, it can be modeled by the thermal

capacitance C of the fluid and thermal resistance R of the walls of the tank. The
system time constant will be RC, the forcing function will be the ambient
temperature and the system state variable will be the fluid temperature.
A second order system can be described by two independent energy storage

elements that exchange stored energy. Examples of second order systems are a
motor driving a disk flywheel with the motor coupled to the flywheel via a shaft
with torsional stiffness or an electric circuit composed of a current source
driving a series LR (inductor and resistor) with a shunt C (capacitor). The
energy storage elements for these systems are the rotational kinetic energy
and torsion spring energy for the former and the inductive and capacitive
storage energy for the latter. Motor drive systems and heating systems can be
typically modeled by the LR and C electric circuit.
PID Code Sample
The illustration PID Code Sample shows sample code for controlling the PID
application example shown before. Developed using Function Block Diagrams,
it consists of a pre-defined function block, IPIDCONTROLLER, and four use-
defined function blocks. These four are:

• PID_OutputRegulator
This user-defined function block regulates the output of
IPIDCONTROLLER within a safe range to ensure that there is no
damage to the hardware used in the process.
IF RMIN ≤ RIN ≤ RMAX, then ROUT = RIN,

IF RIN < RMIN, then ROUT = RMIN,
IF RIN > RMAX, then ROUT = RMAX.
• PID_Feedback
This user defined function block acts as a multiplexer.
IF "FB_RST" is false, FB_OUT=FB_IN;

If "FB_RST" is true, then FB_OUT=FB_PREVAL.
• PID_PWM
This user defined function block provides a PWM function, converting a
real value to a time-related ON/OFF output.
• SIM_WATERLVL
This user defined function block simulates the process depicted in the
application example shown before.
IMPORTANT User Program Scan Time is Important

The autotuning method needs to cause the output of the control loop to
oscillate. In order to identify the oscillation period, the IPID must be called
frequently enough to be able to sample the oscillation adequately. The scan
time of the user program must be less than half the oscillation period. In
essence the Shannon, or Nyquist-Shannon, or the sampling theorem must be
adhered to.
In addition, it is important that the function block is executed at a relatively
constant time interval. One can typically achieve this using STI interrupt.

Appendix F
System Loading
Table 74 - Micro830, Micro850, and Micro870 Power Requirements

Controller/Module Power Requirement
Micro830, Micro850, and Micro870
(without plug-in/expansion I/O)
10/16-point 5W
24-point 8W
48-point 11 W
Plug-in modules, each 1.44 W
2085-IQ16 – 0.85 W
2085-IQ32T – 0.95 W
2085-IA8 – 0.75 W
2085-IM8 – 0.75 W
2085-OA8 – 0.90 W
2085-OB16 – 1.00 W
Expansion I/O 2085-OV16 – 1.00 W
(system bus power consumption) 2085-OW8 – 1.80 W
2085-OW16 – 3.20 W
2085-IF4 – 1.70 W
2085-IF8 – 1.75 W
2085-OF4 – 3.70 W
2085-IRT4 – 2.00 W
Calculate Total Power for Your Micro830/Micro850/Micro870

Controller
To calculate Total Power for your Micro830, Micro850, and Micro870

controller, use the following formula:
Total Power =Main Unit Power + No. of Plug-ins * Plug-in Power +

Sum of Expansion I/O Power
Example 1:
Derive Total Power for a 24-point Micro830 controller with two plug-ins.
Total Power = 8 W+ 1.44 W * 2 + 0 = 10.88 W
Example 2:
Derive Total Power for a 48-point Micro850 controller, with 3 plug-ins, and
2085-IQ16 and 2085-IF4 expansion I/O modules attached.
Total Power = 11 W + 3*1.44 W + 0.85 W + 1.7 W = 17.87 W

Appendix F System Loading
Calculate External AC Power Supply Loading for your Micro830 Controller
To calculate External AC Power Supply Loading:

• Get total sensor current loading. For this example, assume it is 250 mA.
• Calculate Total Power Loading by Sensor using this formula:
(24V * 250 mA) 6 W.
• Derive External AC Power Supply Loading using this formula:
AC Power Supply Loading = Total Power calculated for a Micro800
system with Plug-in + Total power loading by Sensor.
As an example, a 48-point Micro850 controller with2 plug-ins, and 2085-IQ16

and 2085-IF4 expansion I/O, and 250 mA sensor current (6 W sensor power)
will have the following Total Loading for AC Power Supply:
Total loading for AC power supply = 17.87 W + 6 W = 23.87 W
ATTENTION: Maximum loading to AC Power Supply is limited to 38.4 W with

maximum surrounding ambient temperature limited to 65 °C.

Appendix G
Connect to Networks using DF1
IMPORTANT This appendix only applies to Micro850 (2080-L50E) and Micro870

(2080-L70E) controllers.
Topic Page
DF1 Full-Duplex Protocol 325
DF1 Half-Duplex Protocol 326
Modem Control Line Operation 328
Configure DF1 Half-Duplex Parameters 330
Configure a Standard-Mode DF1 Half-Duplex Master Station 330
Configure a Message-based Mode DF1 Half-Duplex Master 334
Station
Configure a Slave Station 336
Configure Poll Timeout 337
Configure a Radio Modem Station 338
The following protocols are supported on the embedded serial port, including
any 2080-SERIALISOL plug-in module that is installed, on the newer Micro850
(2080-L50E) and Micro870 (2080-L70E) controllers.
• DF1 Full Duplex
• DF1 Half-Duplex Master/Slave
• DF1 Radio Modem
DF1 Full-Duplex Protocol DF1 Full-Duplex protocol provides a point-to-point connection between two
devices. DF1 Full-Duplex protocol combines data transparency (American
National Standards Institute ANSI – X3.28-1976 specification subcategory D1)
and 2-way simultaneous transmission with embedded responses
(subcategory F1).
The controller supports the DF1 Full-Duplex protocol via RS-232 connection to
external devices, such as computers, or other controllers that support DF1 Full-
Duplex.
DF1 support is achieved through the CIP serial interface in the Micro800
controllers.
DF1 Full-Duplex protocol (also referred to as DF1 point-to-point protocol) is

useful where RS-232 point-to-point communication is required. DF1 protocol
controls message flow, detects and signals errors, and retries if errors are
detected.

Appendix G Connect to Networks using DF1
Example DF1 Full-Duplex Connections

Micro870 controller
Computer
CH0
Computer
Modem cable USB

Micro870 controller
Modem
CH0
Modem 1761-CBL-PM02 with null modem adapter
DF1 Half-Duplex Protocol DF1 Half-Duplex protocol is a multi-drop single master/multiple slave
network. DF1 Half-Duplex protocol supports data transparency (American
National Standards Institute ANSI – X3.28-1976 specification subcategory D1).
In contrast to DF1 Full-Duplex, communication takes place in one direction at
a time. You can use the RS-232/RS-485 port on the controller as both a Half-
Duplex programming port and a Half-Duplex peer-to-peer messaging port.
DF1 Half-Duplex Operation

A DF1 Half-Duplex master device initiates all communication by “polling” each
slave device. The slave device may only transmit when it is polled by the
master. It is the master’s responsibility to poll each slave on a regular and
sequential basis to allow slave devices an opportunity to communicate.
An additional feature of the DF1 Half-Duplex protocol is that it is possible for a

slave device to enable a MSG write or read to/from another slave. When the
initiating slave is polled, the MSG is sent to the master. The master recognizes
that the message is not intended for it, but for another slave, so the master
immediately forwards the message to the intended slave. The master does this
automatically; you do not need to program the master to move data between
slave nodes. This slave-to-slave transfer can also be used by programming
software to allow slave-to-slave upload and download of programs to
controllers (including the master) on the DF1 Half-Duplex link.
The controller can act as the master or as a slave on a Half-Duplex network.

When the controller is a slave device, a master device is required to run the
network. Several other Allen-Bradley products support DF1 Half-Duplex
master protocol.
DF1 Half-Duplex supports up to 255 devices (address 0…254) with address 255
reserved for master broadcasts. As a DF1 Half-Duplex slave device, the
controller supports broadcast reception. As a DF1 Half-Duplex master, the
controller supports both the reception and initiation of broadcast write
commands (via the MSG instruction). The controller also supports Half-
Duplex modems using RTS/CTS hardware handshaking.
IMPORTANT Firmware revision 20 for Micro850 and Micro870 controllers does not
support the broadcast function in Half-Duplex Master. This feature will
be supported in a future firmware revision.

Considerations When Communicating as a DF1 Slave on a Multi-drop

Link
When communication is between either your programming software and a
Micro800 controller or between two Micro800 controllers via slave-to-slave
communication on a larger multi-drop link, the devices depend on a DF1 Half-
Duplex Master to give each of them access in a timely manner. As the number
of slave devices increases, the time between when slave devices are polled also
increases. This increase in time may also be large if you are using low baud
rates. As these time periods grow, you may need to increase the poll timeout
and reply timeout values for slave devices.
IMPORTANT Program download is not supported in DF1 Half-Duplex and Radio

Modem for Micro850 (2080-L50E) and Micro870 (2080-L70E) controllers
firmware revision 20 or later.
Using Modems with Micro800 Programmable Controllers

The types of modems you can use with Micro800 controllers include the
following:
• Dial-up phone modems.
A Micro800 controller, on the receiving end of the dial-up connection,
can be configured for DF1 Full-Duplex protocol with or without
handshaking. The modem connected to the Micro800 controller should
support auto-answer.
• Leased-line modems.
Leased-line modems are used with dedicated phone lines that are
typically leased from the local phone company. The dedicated lines may
be in a point-to-point topology supporting Full-Duplex communications
between two modems or in a multi-drop topology supporting Half-
Duplex communications between three or more modems.
• Radio modems.
Radio modems may be implemented in a point-to-point topology
supporting either Half-Duplex or Full-Duplex communications, or in a
multi-drop topology supporting Half-Duplex communications between
three or more modems. Micro800 controllers also support DF1 Radio
Modem protocol.
• Line drivers.
Line drivers, also called short-haul modems, do not actually modulate the
serial data, but rather condition the electrical signals to operate reliably
over long transmission distances (up to several miles). Line drivers are
available in Full-Duplex and Half-Duplex models.
For point-to-point Full-Duplex modem connections that do not require any

modem handshaking signals to operate, use DF1 Full-Duplex protocol with no
handshaking. For point-to-point Full-Duplex modem connections that require
RTS/CTS handshaking, use DF1 Full-Duplex protocol with handshaking.
For radio modem connections, use DF1 Radio Modem protocol, especially if
store and forward capability is required.
For general multi-drop modem connections, or for point-to-point modem

connections that require RTS/CTS handshaking, use DF1 Half-Duplex slave
protocol. In this case, one (and only one) of the other devices must be
configured for DF1 Half-Duplex master protocol.

Micro850 (2080-L50E) and Micro870 (2080-L70E) controllers support RTS/CTS

modem handshaking when configured for DF1 Full-Duplex protocol with the control
line parameter set to Full-Duplex Modem Handshaking or DF1 Half-Duplex slave
protocol with the control line parameter set to Half-Duplex Modem.
These controllers also support DCD (Data Carrier Detect) line for DF1 Radio Modem
protocol. No other modem handshaking lines (such as Data-Set™ Ready and Data
Terminal Ready) are supported by Micro800 controllers.
Modem Control Line The following explains the operation of the Micro800 controllers when you
Operation configure the RS-232 serial port for the following applications.
DF1 Full-Duplex
When configured for DF1 full-duplex, the following control line operation
takes effect:
No Handshake Selected
RTS is always inactive (low). Receptions and transmissions take place

regardless of the state of CTS input. Only make this selection when the
Micro800 controllers are directly connected to another device that does not
require handshaking signals.
Full-Duplex (RTS always ON) Selected
RTS is always active (high).

Transmissions require CTS to be active.
DF1 Half-Duplex Slave

When configured for DF1 half-duplex slave, the following control line
operation takes effect:
RTS is always inactive. Receptions and transmissions take place regardless of

the state of CTS input. Only make this selection when the controller is directly
connected to another device that does not require handshaking signals.
Half-Duplex without Continuous Carrier (RTS/CTS) Selected
RTS is only activated during transmissions (and any programmed delays

before or after transmissions). Transmissions require CTS to be active.

DF1 Half Duplex Master

When configuring for DF1 half-duplex master, the following control line
operation takes effect:

the state of CTS input. Only make this selection when the controller is directly
connected to another device that does not require handshaking signals.
Full-Duplex Modem (RTS always ON) Selected
RTS is always active (high).
Transmissions require CTS to be active.
RTS is only active during transmissions (and any programmed delays before
and after transmissions).
Transmissions require CTS to be active
DF1 Radio Modem

When you configure the Micro800 controllers for DF1 Radio Modem, the
following control line operation takes effect:

the state of CTS input. This selection should only be made when the controller
is directly connected to another device that does not require handshaking
signals.
RTS is activated during transmission and during any programmed delays

before or after transmissions. Programmed delays include RTS Send Delay
and RTS Off Delay.
Transmissions require CTS to be active. If CTS is inactive at the onset of

transmission, one second will be provided to wait for CTS to become active
before the message packet is discarded.
Half-Duplex with DCD Handshake Selected
RTS is activated during transmissions and during any programmed delays

before and after transmissions. Programmed delays include RTS Send Delay
and RTS Off Delay. The DCD input signal is monitored to determine if
transmissions are acceptable. If DCD is active, receptions are possible.
Transmissions require CTS to be active and DCD to be inactive. If DCD is

active at the onset of transmission, a configured delay (DCD Wait Delay) will
wait for DCD to become inactive before discarding the packet. If CTS is
inactive at the onset of transmission, one second will be provided to wait for
CTS to become active before the message packet is discarded.

Configure DF1 Half-Duplex RTS Send Delay and RTS Off Delay
Parameters
Through your programming software, the parameters RTS Send Delay and
RTS Off Delay let you set how long RTS is on prior to transmission, as well as
how long to keep it on after transmission is complete. These parameters only
apply when you select half-duplex modem. For maximum communication
throughput, leave these parameters at zero.
For use with half-duplex modems that require extra time to turnaround or key-
up their transmitter even after they have activated CTS, the RTS Send Delay
specifies (in 20 millisecond increments) the amount of delay time after
activating RTS to wait before checking to see if CTS has been activated by the
modem. If CTS is not yet active, RTS remains active, and as long as CTS is
activated within one second, the transmission occurs. After one second, if CTS
is still not activated, then RTS is set inactive and the transmission is aborted.
For modems that do not supply a CTS signal but still require RTS to be raised
prior to transmission, jumper RTS to CTS and use the shortest delay possible
without losing reliable operation.
IMPORTANT If an RTS Send Delay of 0 is selected, then transmission starts as soon

as CTS is activated. If CTS does not go active within one second after
RTS is raised, RTS is set inactive and the transmission is aborted.
Certain modems will drop their carrier link when RTS is set inactive even
though the transmission has not quite been finished. The RTS Off Delay
parameter specifies in 20 millisecond increments the delay between when the
last serial character is sent to the modem and when RTS is deactivated. This
gives the modem extra time to transmit the last character of a packet.
ATTENTION: For almost all modem applications, the RTS Off Delay should be
left at 0. Never select an RTS Off Delay that is greater than the RTS Send Delay
in the other devices on the network, or you may incur two devices trying to
transmit simultaneously.
Configure a Standard-Mode Choose standard mode if you want to query slave stations for information
DF1 Half-Duplex Master based upon user-configured polling ranges. This mode is used most often in
general point-to-multipoint configurations.
Station
To configure the controller as a master station using standard-
communication, place the controller into program mode and follow the steps
below using your programming software:
1. To bring up the configuration page, click

Serial Port.

2. On the Serial Port configuration page, select

Half-Duplex Master for DF1 Mode.
3. Choose a Standard Polling Mode.
4. Configure the rest of the communication
driver according to Table 75.
The following table shows the parameters for configuring a Micro850 (2080-
L50E) or Micro870 (2080-L70E) controller as a master station using standard-
communication mode to talk to slave stations.
Table 75 - Configure a Micro800 Controller as a Master Using Standard-communication
Mode
Parameter Selections
Select a communication rate that all devices in your system support. Configure all
Baud Rate devices in the system for the same communication rate.
Parity provides additional message packet error detection. To implement even
Parity parity checking, choose Even. To implement no parity checking, choose None.
A node address identifies the controller on the DF1 half-duplex link. Each station
on a link must have a unique address. Choose an address between 010 and 25410.
Node Address Node address 25510 is the broadcast address, and cannot be selected as a
station’s individual address.
This parameter defines the mode in which the driver operates. Choose a method
appropriate for your system’s configuration:
• If you are not using a modem, choose NO HANDSHAKE.
Control Line • If the master modem is full duplex, choose FULL-DUPLEX (RTS ALWAYS ON).
• If all the modems in the system are half-duplex, choose HALF-DUPLEX WITHOUT
CONTINUOUS CARRIER (RTS/CTS).
See Modem Control Line Operation on page 328 for a description of the control
line operation settings.
With this selection, you choose how the controller checks the accuracy of each
DF1 packet transmission.
BCC: This algorithm provides a medium level of data security. It cannot detect:
– transposition of bytes during transmission of a packet
Error Detection – the insertion or deletion of data values of zero within a packet
CRC: This algorithm provides a higher level of data security.
Select an error detection method that all devices in your configuration can use.
When possible, choose CRC.
If you want to receive:
• only one message from a slave station per its turn, choose STANDARD (SINGLE
MESSAGE TRANSFER PER NODE SCAN). Choose this method only if it is critical to
Polling Mode keep the poll list scan time to a minimum.
• as many messages from a slave station as it has, choose STANDARD (MULTIPLE
MESSAGE TRANSFER PER NODE SCAN).
Duplicate Detect lets the controller detect if it has received a message that is a
duplicate of its most recent message from another station. If you choose
duplicate detect, the controller will acknowledge (ACK) the message but will not
act on it since it has already performed the message’s task when it received the
Duplicate Packet Detect command from the first message.
If you want to detect duplicate packets and discard them, check this parameter.
If you want to accept duplicate packets and execute them, leave this parameter
unchecked.
The amount of time, in 20 millisecond increments, that you want the controller to
wait for an acknowledgment to the message it has sent before the controller
ACK Timeout retries the message or the message errors out. This timeout value is also used for
the poll response timeout. See page G-332 for recommendations to minimize this
value.

Table 75 - Configure a Micro800 Controller as a Master Using Standard-communication

Mode (Continued)
Defines the amount of time, in 20 millisecond increments, that elapses between
the end of the message transmission and the de-assertion of the RTS signal. This
RTS Off Delay time delay is a buffer to make sure that the modem has transmitted the message
but should normally be left at zero. See RTS Send Delay and RTS Off Delay on
page 330 for further guidelines for setting this parameter.
Defines the amount of time, in 20 millisecond increments, that elapses between
the assertion of the RTS signal and the beginning of the message transmission.
RTS Send Delay This time allows the modem to prepare to transmit the message. The Clear-to-
Send (CTS) signal must be high for transmission to occur. See RTS Send Delay and
RTS Off Delay on page 330 for further guidelines for setting this parameter.
Defines the amount of time in 1 millisecond increments that elapses between
Pre-Transmit Delay when the controller has a message to send and when it asserts the RTS signal.
Defines the number of times a master station retries either:
• a message before it declares the message undeliverable
Message Retries
• or a poll packet to an active station before the master station declares that
station to be inactive.
Priority Polling Range – High Select the last slave station address to priority poll.
Select the first slave station address to priority poll. Entering 255 disables priority
Priority Polling Range – Low polling.
Normal Polling Range – High Select the last slave station address to normal poll.
Select the first slave station address to normal poll. Entering 255 disables normal
Normal Polling Range – Low polling.
Enter the quantity of active stations located in the normal poll range that you
want polled during a scan through the normal poll range before returning to the
Normal Poll Group Size priority poll range. If no stations are configured in the Priority Polling Range, leave
this parameter at 0.
IMPORTANT The unconnected timeout value in the Message instruction should

always be larger than the pre-transmit delay.
Minimum DF1 Half-Duplex Master ACK Timeout

The governing timeout parameter to configure for a DF1 Half-Duplex Master is
the serial port ACK Timeout. The ACK Timeout is the amount of time you want
the controller to wait for an acknowledgment of its message transmissions. Set
in 20 millisecond intervals, the value is the amount of time the master will wait
for:
• an ACK to be returned by a slave when the master has just sent it a
message, or
• a poll response or message to be returned by a slave when the master has
just sent it a poll packet.
The timeout must be long enough that after the master has transmitted the
last character of the poll packet, there is enough time for a slave to transmit
(and the master receive) a maximum-sized packet before the time expires.
To calculate the minimum ACK timeout, you must know:

• the modem baud rate
• maximum-sized data packet (the maximum number of data words that a
slave write command or read reply packet might contain)
• the RTS/CTS or turnaround delay of the slave modem
• the configured RTS Send Delay in the slave
• the program scan time of the slave

Determining Minimum Master ACK Timeout

To determine the minimum ACK Timeout, you must first calculate the
transmission time by multiplying the maximum-sized data packet for your
controller by the modem rate in ms/byte. For an example we will assume a
Micro800 controller (103 data words or 224 bytes total packet size including
overhead) and a 9600 bps modem, which transmits at approximately 1 ms/
byte. Therefore, the message transmission time is 224 ms. For approximate
modem transmission rates, see the following table.
Table 76 - Approximate Modem Transmission Rates
Speed (bps) Rate, approx (ms/byte)
4800 2 ms/byte
9600 1 ms/byte
19200 0.5 ms/byte
Next, you need to determine the average slave program scan time. In
Connected Components Workbench software, double-click the controller
variables in the Controller Organizer and locate the system tag
_SYSVA_TCYCYCTIME in the Variable tab. For this example, assume the
program scan time is 20 ms. The program scan time varies by application.
Finally, you must determine the larger of two values, either the configured
slave RTS Send Delay or the turnaround time of the slave modem. The RTS
Send Delay time can be found by in the Configuration screen of the Micro800
embedded serial port. Note that the RTS Send Delay time is in intervals of 20
ms, so with a value of 3 in the box, the RTS Send Delay time would be 20 ms
multiplied by 3. Using this value (60 ms) for our example, and assuming that
the turnaround time of the modem is 50 ms (which will vary by modem), you
would choose to use the RTS Send Delay time of 60 ms for your calculation.
Having determined the maximum message transmission time (224 ms), the
average slave program scan time (20 ms) and the largest of either RTS Send
Delay (60 ms) or the modem turnaround time, the minimum ACK timeout is
simply the sum of these values.
Parameter Example Values (in ms)
Max Message Transmission Time 224
Average Program Scan Time 20
RTS Send Delay 60
Modem Turnaround Time 50
Calculated ACK Timeout 304 Use only the largest of these two values.
Round up to Nearest 20 ms 320
DF1 Half-Duplex Master Communication Diagnostics

Communication diagnostics is available while connected to the controller by
clicking the Diagnose communication status button. Table 77 explains
information regarding the diagnostic counter data displayed.
1. Click Diagnose communication status to bring
up the DF1 Half-Duplex Master diagnostics.

2. See Table 77 for details concerning the DF1

Half-Duplex Master Communication
Diagnostics screen.
Table 77 - DF1 Half-Duplex Master Communication Diagnostics Parameters

Status Field Definition
The total number of DF1 messages sent by the controller (including message
Packets Sent retries).
Packets Received The number of messages received with no errors.
Last Normal Scan Time (ms) Time in millisecond increments of last scan through Normal Poll List.
Last Priority Scan Time (ms) Time in millisecond increments of last scan through Priority Poll List.
Message Retried The number of message retries sent by the controller.
The number of messages that were sent by the controller but not acknowledged by
Undelivered Packets the destination device.
The number of times the controller received a message packet identical to the
Duplicate Received previous message packet.
The number of incorrect data packets received by the controller for which no ACK
Bad Packet Received was returned.
Max Normal Scan Time (ms) Maximum time in millisecond increments to scan the Normal Poll List.
Max Priority Scan Time (ms) Maximum time in millisecond increments to scan the Priority Poll List.
Configure a Message-based Choose message-based communication mode if you want to use MSG
Mode DF1 Half-Duplex instructions in user programming to communicate with one station at a time.
If your application uses satellite transmission or cellular transmission,
Master Station consider choosing message-based. Communication to a slave station can be
initiated on an as-needed basis.
With message-based mode, you do not have an active node file that you can use
to monitor station status. Also, you cannot implement slave station-to-slave
station messaging or slave programming.
To configure the controller for a master station using message-based

communication, place the controller in program mode and follow the steps
below in Connected Components Workbench software.

Serial Port.
Half-Duplex Master for your DF1 Mode.
3. Choose a Message-based Polling Mode.

Define the parameters shown in Table 78 when configuring a Micro800

controller as a master station using message-based communication mode to
talk to slave stations.
Table 78 - Configure a Micro800 Controller as a Master Using Message-based
Communication Mode
Select a communication rate that all devices in your system support. Configure all devices
Baud Rate in the system for the same communication rate.
Parity provides additional message packet error detection. To implement even parity
Parity checking, choose Even. To implement no parity checking, choose None.
A node address identifies the controller on the DF1 half-duplex link. Each station on a link
Node Address must have a unique address. Choose an address between 010 and 25410. Node address 25510
is the broadcast address, and cannot be selected as a station’s individual address.
Select the communication media for the DF1 protocol:
Media • RS-232
• RS-485 (only available when DF1 mode is Half-Duplex)
Control Line • If the master modem is full duplex, choose FULL-DUPLEX (RTS ALWAYS ON).
• If all the modems in the system are half-duplex, choose HALF-DUPLEX WITHOUT
CONTINUOUS CARRIER (RTS/CTS).
See Modem Control Line Operation on page 328 for descriptions of control line operation
settings.
With this selection, you choose the how the controller checks the accuracy of each DF1
packet transmission.
If you want to:
• accept unsolicited messages from slave stations, choose MESSAGE BASED (ALLOW SLAVES
TO INITIATE MESSAGES)
Slave station-initiated messages are acknowledged and processed after all master
station-initiated (solicited) messages.
Note: Slave stations can only send messages when they are polled. If the message-based
master station never sends a slave station a message, the master station will never send
Polling Mode the slave station a poll. Therefore, to regularly obtain a slave station-initiated message
from a slave station, you should choose to use standard communication mode instead.
• ignore unsolicited messages from slave stations, choose MESSAGE BASED (DO NOT ALLOW
SLAVES TO INITIATE MESSAGES)
Slave station-initiated messages are acknowledged and discarded. The master station
acknowledges the slave station-initiated message so that the slave station removes the
message from its transmit queue, which allows the next packet slated for transmission
into the transmit queue.
Duplicate Detect lets the controller detect if it has received a message that is a duplicate of
its most recent message from another station. If you choose duplicate detect, the controller
Duplicate Packet will acknowledge (ACK) the message but will not act on it since it has already performed the
Detect message’s task when it received the command from the first message.
If you want to detect duplicate packets and discard them, check this parameter. If you want
to accept duplicate packets and execute them, leave this parameter unchecked.
Defines the amount of time, in 20 millisecond increments, that the master station will wait
Reply Message Wait after receiving an ACK (to a master-initiated message) before polling the slave station for a
reply.
Timeout Choose a time that is, at minimum, equal to the longest time that a slave station needs to
format a reply packet. This would typically be the maximum scan time of the slave station.
The amount of time, in 20 millisecond increments, that you want the controller to wait for an
acknowledgment to the message it has sent before the controller retries the message or the
ACK Timeout message errors out. This timeout value is also used for the poll response timeout. See
See Minimum DF1 Half-Duplex Master ACK Timeout on page 332 for recommendations to
minimize this value.
Defines the amount of time, in 20 millisecond increments, that elapses between the end of
the message transmission and the de-assertion of the RTS signal. This time delay is a buffer
RTS Off Delay to make sure that the modem has transmitted the message but should normally be left at
zero. See RTS Send Delay and RTS Off Delay on page 330 for further guidelines for setting
this parameter.

Table 78 - Configure a Micro800 Controller as a Master Using Message-based

Communication Mode (Continued)
Defines the amount of time, in 20 millisecond increments, that elapses between the
assertion of the RTS signal and the beginning of the message transmission. This time allows
RTS Send Delay the modem to prepare to transmit the message. The Clear-to-Send (CTS) signal must be
high for transmission to occur. See RTS Send Delay and RTS Off Delay on page 330 for
further guidelines for setting this parameter.
Defines the amount of time, in 1 millisecond increments, that elapses between when the
Pre-Transmit Delay controller has a message to send and when it asserts the RTS signal.
Defines the number of times a master station retries a message before it declares the
Message Retries message undeliverable.
IMPORTANT The unconnected timeout value in the Message instruction should

always be larger than the pre-transmit delay.
Configure a Slave Station To choose the controller as a slave station, follow the steps below using your
programming software:

Serial Port.
Half-Duplex Slave for your DF1 Mode.
Define these parameters when configuring a Micro800 controller as a slave

station.
Table 79 - Configure a Micro800 Controller as a Slave Station
Select a communication rate that all devices in your system support. Configure all
Baud Rate devices in the system for the same communication rate.
Parity provides additional message packet error detection. To implement even parity
Parity checking, choose Even. To implement no parity checking, choose None.
A node address identifies the controller on the DF1 half-duplex link. Each station on a
link must have a unique node address. Choose an address between 010 and 25410.
Node Address Node address 25510 is the broadcast address, which you cannot select as a station’s
individual address.
Control Line • If the master modem is full duplex and the slave modem is half-duplex, choose
HALF-DUPLEX WITHOUT CONTINUOUS CARRIER (RTS/CTS).
See page Modem Control Line Operation on page 328 for descriptions of the control
line operation settings.

Table 79 - Configure a Micro800 Controller as a Slave Station (Continued)

With this selection, you choose how the controller checks the accuracy of each DF1
packet transmission.
Duplicate Detect lets the controller detect if it has received a message that is a
duplicate of its most recent message from the master station. If you choose
duplicate detect, the controller will acknowledge (ACK) the message but will not act
on it since it has already performed the message’s task when it received the
Duplicate Packet Detect command from the first message.
If you want to detect duplicate packets and discard them, check this parameter. If
you want to accept duplicate packets and execute them, leave this parameter
unchecked.
The timer keeps track of how often the station is polled. If the station has a message
to send, it starts a timer.
If the poll timeout expires before the message timeout, which you specify in the MSG
control block, the MSG error bit is set and the message is removed from the transmit
Poll Timeout queue.
If the message timeout, which you specify in the MSG control block, expires before
the poll timeout expires, the MSG error bit and MSG timeout bit are set.
The poll timeout can be disabled by entering a zero. See Configure Poll Timeout on
page 337 for recommendations to minimize this value.
end of the message transmission and the de-assertion of the RTS signal. This time
RTS Off Delay delay is a buffer to make sure that the modem has transmitted the message, but
should normally be left at zero. See RTS Send Delay and RTS Off Delay on page 330 for
further guidelines for setting this parameter.
assertion of the RTS signal and the beginning of the message transmission. This time
RTS Send Delay allows the modem to prepare to transmit the message. The Clear-to-Send (CTS) signal
must be high for transmission to occur. See RTS Send Delay and RTS Off Delay on
Defines the number of times a slave station resends its message to the master
Message Retries station before the slave station declares the message undeliverable.
Defines the amount of time in 1 millisecond increments that elapses between when
Pre-Transmit Delay the controller has a message to send and when it asserts the RTS signal.
If you want to minimize traffic on the network, you can choose to have the slave
station not send EOT packets to the master station. When EOT packets are
suppressed, the master station automatically assumes a slave station has no data to
give if the slave station does not send a message packet as a response to a poll.
A disadvantage of suppressing EOTs is that the master station cannot distinguish
EOT Suppression between an active station that has no data to transmit and an inactive station.
A possible application for suppressing EOTs is the following: conserving power with a
radio modem because the radio transmitter does not have to power-up to transmit a
DLE EOT packet (”no data to give” packet).
To suppress EOTs, check this parameter. To have the controller send EOTs, leave this
parameter unchecked.
Configure Poll Timeout The Poll Timeout is only used when the DF1 half-duplex slave is initiating MSG
instructions in ladder logic. This implies that the Master is most likely
configured for Standard Polling Mode. The minimum Poll Timeout value is
dependent on the maximum Master poll scan rate. Since the Master’s polling
and the Slave’s triggering of a MSG instruction are asynchronous events, it is
possible that in the instant just after the slave was polled, the MSG instruction
gets triggered. This means the MSG instruction will remain queued-up for
transmission until the Master has polled every other slave first. Therefore, the
minimum Slave Serial port Poll Timeout value is equal to the maximum Master
poll scan rate rounded up to the next 20 ms increment.
Minimum Serial Port Poll Timeout = Maximum Master Scan Poll Rate

DF1 Half-Duplex Slave Communication Diagnostics

up the DF1 Half-Duplex Slave diagnostics.

Half-Duplex Slave Communication
Diagnostics screen.
Table 80 - DF1 Half-Duplex Slave Communication Diagnostics Parameters

The total number of DF1 messages sent by the controller (including message
Packets Sent retries).
NAKs Received The number of NAKs received by the controller.
The number of times the controller could not receive a message because it did not
No Memory for Receiving have available memory.
Messages Retried The number of message retries sent by the controller.
The number of incorrect data packets received by the controller for which no ACK
Bad Packets Received was returned.
Configure a Radio Modem To configure a Micro800 controller channel 1 for DF1 Radio Modem, do the
Station following using your programming software:

Serial Port.
Radio Modem for your DF1 Mode.

Table 81 - Configure a Micro800 controller for DF1 Radio Modem communication

Parameter Default Selections
Select a communication rate that all devices in your system support. Configure all devices in the system for
Baud Rate 19,200 the same communication rate.
Parity provides additional message packet error detection. To implement even parity checking, choose Even.
Parity None To implement odd parity checking, choose Odd. To implement no parity checking, choose None.
A node address identifies the controller on the DF1 half-duplex link. Each station on a link must have a unique
Node Address 1 node address. Choose an address between 010 and 25410. Node address 25510 is the broadcast address, which
you cannot select as a station’s individual address.
Enable Store and Forward Not selected (Disabled) See Configure the Store and Forward Table on page 340 for more information.
This parameter defines the mode in which the driver operates. Choose a method appropriate for your
system’s configuration:
Control Line No Handshake
• Half-Duplex without Continuous Carrier (RTS/CTS)
• Half-Duplex with DCD Handshaking
See Modem Control Line Operation on page 328 for descriptions of the control line operation settings.
With this selection, you choose the how the controller checks the accuracy of each DF1 packet transmission.
Error Detection CRC – the insertion or deletion of data values of zero within a packet
Defines the amount of time, in 20 millisecond increments, that elapses between the end of the message
transmission and the de-assertion of the RTS signal. This time delay is a buffer to make sure that the modem
RTS Off Delay 0 has transmitted the message, but should normally be left at zero. See RTS Send Delay and RTS Off Delay on
Defines the amount of time, in 20 millisecond increments, that elapses between the assertion of the RTS
signal and the beginning of the message transmission. This time allows the modem to prepare to transmit
RTS On Delay 0 the message. The Clear-to-Send (CTS) signal must be high for transmission to occur. See RTS Send Delay and
RTS Off Delay on page 330 for further guidelines for setting this parameter.
Defines the amount of time, in 1 millisecond increments, that elapses between when the controller has a
Pre-Transmit Delay 0 message to send and when it asserts the RTS signal (if handshaking is selected) or begins transmitting (if no
handshaking is selected).
DF1 Radio Modem Communication Diagnostics

up the DF1 Radio Modem diagnostics.

Radio Modem Communication Diagnostics
screen.
Table 82 - DF1 Radio Modem Communication Diagnostics Parameters

Packets Sent The total number of DF1 messages sent by the controller.
The number of times the controller could not receive a message because it did not
No Memory for Receiving have available memory.

Table 82 - DF1 Radio Modem Communication Diagnostics Parameters (Continued)

Bad Characters Received The number of data characters received with transmission errors by the controller.
Configure the Store and Forward Table

The Store and Forward function in Micro800 controllers provide two methods
to configure – Dynamic, which requires creating a Store & Forward table, or
Static, which you can directly configure in Connected Components
Workbench software.
Use the static method when you want to configure the Store and Forward
tables while the controller is offline. Use the dynamic method when you want
to configure the Store and Forward tables while the controller is in RUN mode.
The dynamic Store and Forward table occupies a BOOL array [0…255] or
DWORD array [0…7] data type. Each bit in this array corresponds to a DF1
Radio Modem node address.
In order to configure a Micro800 controller to Store and Forward message
packets between two other nodes, the bits corresponding to the addresses of
those two other nodes must be set. For instance, if node 2 is used to Store and
Forward message packets between nodes 1 and 3, then both Bit 1 and Bit 3
would have to be set in the Store and Forward table (see Figure 30).
IMPORTANT Once Store and Forward is enabled, duplicate packet detection is also
automatically enabled. Whenever Store and Forward is used within a
radio modem network, every node should have Store and Forward
enabled, even if all of the bits in the file are cleared, so that duplicate
packets will be ignored.
Figure 30 - Applying Store and Forward with DF1 Radio Modem Protocol
(2nd Rebroadcast) Note 4
REPLY 1 (1st Rebroadcast)
REPLY 1 Note 3
Node 1 Node 2 Node 3 Node 4

REPLY 1
CMD 1
No Bits 1, 3, 4 1, 2, 4 (DST = 1, SRC = 4) No Bits
(DST = 4, SRC = 1)
Note 1
CMD1 CMD 1
(1st Rebroadcast) (2nd Rebroadcast)
Note 2
Note 1 – The link layer of Node 1 blocks the re-transmission of a packet that is received with the SRC byte equal to the receiving node’s station
address. Packets received that originate from the receiving node should never be re-transmitted.
Note 2 – To prevent Node 2 from re-transmitting a duplicate packet, the link layer of Node 2 updates the duplicate packet table with the last 20
packets received.
Note 3 – The link layer of Node 4 blocks the re-transmission of a packet that is received with the SRC byte equal to the receiving node’s station
address. Packets received that originate from the receiving node should never be re-transmitted.
Note 4 – To prevent Node 3 from re-transmitting a duplicate packet, the link layer of Node 3 updates the duplicate packet table with the last 20
packets received.

Figure 31 - Store and Forward Table for Node 2, Static Method
Figure 32 - Store and Forward Table for Node 2, Dynamic Method

Dynamic method with BOOL array
Dynamic method with DWORD array

Notes:

Index
Symbols Communication
configuring DF1 radio modem station 339
__SYSVA_CYCLECNT 134 configuring slave station 336
__SYSVA_TCYCURRENT 134 communication connections 59, 75
__SYSVA_TCYMAXIMUM 134 communication protocols 59
DF1 Full-Duplex 325
DF1 Half-Duplex 326
Numerics Communication rate 331, 335, 336, 339
1761-CBL-PM02 65 communications
2080-PS120-240VAC 40 ports 59
2711P-CBL-EX04 22 ConfigMeFirst.txt
errors 226
configure
A DF1 radio modem communication 339
About Your Controller 23 Configuring 334
absolute home switch 141, 142 DF1 Half-Duplex Master
Message-based 334
Additional Resources 13
Standard Mode 330
Addressing Minimum Channel 0 ACK Timeout 332
defining 331, 335, 336 Minimum DF1 Half-Duplex Master 332
analog cable grounding 56 Minimum Master ACK Timeout 333
analog channel wiring guidelines 55 Poll Timeout 337
analog inputs Slave Station 336
Connected Components Workbench 13, 23, 133,
analog channel wiring guidelines 55
ASCII 59, 61, 66 137, 153, 215, 216, 217, 229, 235
configuration 70 connection limits 60
AutoTune 318 Control line 331, 335, 336, 339
axis 140 ControlFLASH 218
axis output controller
general rules 146 description 17
axis state diagram 153 grounding 50
axis state update 154 I/O wiring 55
minimizing electrical noise 55
axis states 153
preventing excessive heat 34
Controller Error Recovery Model 310
B controller load 135
Controller Mounting Dimensions 39
Baud rate 331, 335, 336, 339 controller password 213
BCC 331, 335, 337, 339
recover 217
before calling for assistance 311 controller security 213
CRC 331, 335, 337, 339
C
cables D
programming 21 data log 229, 230
serial port 21
data types 233
calling for assistance 311
directory structure 230
Checking if Forces (locks) are Enabled 281 execution rules 233
CIP Client Messaging 63 specifications 230
CIP communications pass-thru 64 timing diagram 232
CIP Serial 66 datasets 229, 230
CIP Serial Client/Server 59, 61 deceleration 145
CIP Serial Driver DF1 Full-Duplex
configure 66 Communication Diagnostics 339
CIP Symbolic Addressing 63 DF1 full-duplex driver 339
CIP Symbolic Client/Server 59, 62 DF1 Full-Duplex protocol
collision avoidance 122 description 325
using a modem 327
DF1 half-duplex driver 335, 336

Index
DF1 Half-Duplex protocol F

description 326
fault routine
DF1 point-to-point connection 65
description of operation 292
DHCP Client 60 operation in relation to main control
DIN Rail Mounting 41 program 289
DIN rail mounting 41 priority of interrupts 291
direction input 145 faults
disconnecting main power 32 recoverable and non-recoverable 292
DLG force status 304
function block status 231 Forcing I/Os 280
function error ID list 231 Full-duplex station 339
input and output parameters 231
DLG_ERR_DATAFILE_ACCESS 231
DNP3 G
device attribute object 116 generating DNP3 events 117
diagnostics 124 grounding the controller 50
objects 105
Guidelines and Limitations for Advanced Users
slave application layer 100
slave application layer configuration 137
parameters 86
Duplicate packet detection 331, 335, 337
H
Hardware Features 16
E Hardware Overview 15
EII Function Configuration 300 heat protection 34
EII function file 299 High-Speed Counter (HSC) 184
EII Function Status Information 301 high-speed counter function file 202
Embedded Serial Port Cables 21 High-Speed Counter Overview 183
Embedded Serial Port Wiring 57 home marker 141
enable and valid status housekeeping 133, 230
general rules 148 HSC (High Speed Counter) Function Block 202,
encoder 299
quadrature 191 HSC APP Data Structure 187
Endian Configuration 251
HSC function file 202
EOT suppression 331, 335, 337 HSC Interrupt Configuration 208
error 148 HSC Interrupt POU 209
error codes 305 HSC Interrupt Status Information 210
Error detection 331, 335, 337, 339 HSC Interrupts 208
error handling HSC STS Data Structure 196
general rules 148
HSC_SET_STS Function Block 204
error recovery model 310
ErrorStop 153
Establishing Communications Between RSLinx I
and a Micro830 via USB 262
implementation table 127
Ethernet Information About Using Interrupts 289
configuration settings 71
in-position signal 142
EtherNet/IP Client/Server 60
input parameters 145
event generation control 120
input states on power down 34
Event Input Interrupt (EII) Function
Configuration and Status 300 Installing Your Controller 39
INT instruction 292, 293
event input interrupt (EII) function file 299
interrupt subroutine instruction 292, 293
exclusive access 213
interrupts
Execution Rules 134
interrupt instructions 292
execution rules 230
overview 289
selectable timed start (STS) instruction 293
user fault routine 292
user interrupt disable (UID) instruction 293
user interrupt enable (UIE) instruction 294
user interrupt flush (UIF) instruction 295

Index
IP address microSD card 230

exclusions 73 flash upgrade 259
rules 72 minimizing electrical noise 55
IPIDCONTROLLER 316 minimizing electrical noise on analog
parameters 314, 315, 316 channels 56
isolation transformers Modbus Mapping 251
power considerations 33 Modbus Mapping for Micro800 251
Modbus RTU 59, 61, 66
J configuration 68
Modbus TCP Client/Server 60, 61
jerk inputs
Modbus/TCP server 61
general rules 145
modems
using with Micro800 controllers 327
K Module Spacing 40
keyswitch 217 motion control 139, 140
administrative function blocks 144
general rules 145
L wiring input/output 142
motion control function blocks 144
link layer configuration parameters 78 motion function blocks 140
lower (Negative) Limit switch 141 motor starters (bulletin 509)
lower (negative) limit switch 142 surge suppressors 49
mounting dimensions 39
M
Mapping Address Space and supported Data N
Types 251 network status 304
master control relay 35 Normal Operation 305
emergency-stop switches 35 North American Hazardous Location Approval
using ANSI/CSA symbols schematic 37 32
using IEC symbols schematic 36
master control relay circuit
periodic tests 33
MC_AbortTrigger 144
O
MC_Halt 145, 148, 151, 152 object quality flags 114
MC_Home 144 output active
MC_MoveAbsolute 144, 148 general rules 147
output exclusivity 146
MC_MoveRelative 144, 148
output status 304
MC_MoveVelocity 144, 148
Overview of Program Execution 133
MC_Power 144
MC_ReadAxisError 144
MC_ReadBoolParameter 144 P
MC_ReadParameter 144 panel mounting 41
MC_ReadStatus 144 dimensions 42
MC_Reset 144, 153 Parity 331, 335, 336, 339
MC_SetPosition 144 Performance, MSG_MODBUS 256
MC_Stop 144, 148, 152 PID 314
MC_TouchProbe 144 PID Application Example 320
MC_WriteBoolParameter 144 PID Code Sample 321
MC_WriteParameter 144 PID Function Blocks 313
Micro800 PLS Data structure 205
Communication Diagnostics 333 PLS Example 207
Micro800 cycle or scan 133 PLS Operation 206
Micro800 remote station 336 Point-to-point 339
Micro830 Controllers 16 Poll timeout 331, 335
Micro830 controllers position/distance input 145
inputs/outputs types 20 POU (Program Organizational Unit) 134
Micro850 controllers
inputs/outputs types 20, 21
Micro870 controllers
inputs/outputs types 21

Index
power considerations Run Mode Change (RMC) 24

input states on power down 34 benefits 24
isolation transformers 33 limitations 27
loss of power source 34 RMC memory 25
other line conditions 34 uncommitted changes 25
overview 33 using 282
power supply inrush 33 Run Mode Configuration Change (RMCC) 28
power distribution 33 loop-back message 28
power source using EtherNet/IP 30
loss of 34 using Modbus RTU 29
power status 304 verify IP address change 31
power supply inrush verify node address change 29
power considerations 33
preventing excessive heat 34 S
Priority of User Interrupts 290
safety circuits 32
program mode 229
Safety Considerations 32
program scan 230
safety considerations 32
program scan cycle 135
disconnecting main power 32
programmable limit switch 183 hazardous location 32
Programmable Limit Switch (PLS) Function master control relay circuit
205 periodic tests 33
Programmable Limit Switch Overview 183 periodic tests of master control relay circuit
PTO 139 33
power distribution 33
configurable input/output 141 safety circuits 32
fixed input/output signals 141 Selectable Time Interrupt (STI) Function
PTO direction 141, 142
Configuration and Status 298
PTO pulse 141, 142
selectable timed start instruction 293
serial communications status 304
Q serial port
quadrature encoder 191 configure 66
servo drive 139
Quickstarts 257
servo/drive on 141, 142
servo/drive ready 141, 142
R Shutdown 66
recipe 235 Sockets Client/Server 60, 63
data types 233 Station address 331, 335, 336
directory structure 236 status indicator 16
function block errors 237 Ethernet 22
function block parameters 236 fault status 304
function block status 237 input status 304
specifications 235 module status 22, 304
recipe sets 235 network status 22, 304
relative move versus absolute move output status 304
general rules 148 power status 304
Remote station run status 304
serial communications 304
available modes 331, 335, 336 Status Indicators on the Controller 303
configuration 334
configuring 335 STI Function Configuration 298
configuring Micro800 336 STI Function Status Information 299
Remote station driver 331, 336 STS instruction 293
reporting event by polled response 121 surge suppressors
reporting event by unsolicited response 121 for motor starters 49
Retries 332, 336, 337 recommended 49
RJ-45 Ethernet port 22, 59 using 48
system assembly
RS-232/RS-485 combo port 59
Micro830 and Micro850 24-point controllers
RS-232/RS-485 serial port 59 44
RTS off delay 332, 335, 337 Micro830, Micro850, and Micro870 24-point
RTS send delay 332, 336, 337 controllers 43

Index
T
time synchronization 123
timing diagrams
quadrature encoder 191
touch probe input switch 141, 142
troubleshooting 303
U
UID instruction 293
UIE instruction 294
UIF instruction 295
upper (Positive) Limit switch 141
upper (positive) limit switch 142
User Defined Function (UDF) 133, 137
User Defined Function Block (UDFB) 133, 137
user fault routine
creating a user fault routine 292
recoverable and non-recoverable faults 292
User Interrupt Configuration 291
user interrupt disable instruction 293
user interrupt enable instruction 294
user interrupt flush instruction 295
using emergency-stop switches 35
Using Interrupts 289
Using the High-Speed Counter and
Programmable Limit Switch 183
Using the Selectable Timed Interrupt (STI)
Function 297
V
validate IP address 72
variable retainment 137
velocity input 145
W
wiring diagrams 51
Wiring Examples 56
wiring recommendation 47
Wiring Your Controller 47

Index
Notes:

Micro830, Micro850, and Micro870 Programmable Controllers User Manual

Rockwell Automation Support
Use these resources to access support information.
Technical Support Center Find help with how-to videos, FAQs, chat, user forums, and product notification updates. rok.auto/support
Knowledgebase Access Knowledgebase articles. rok.auto/knowledgebase
Local Technical Support Phone Numbers Locate the telephone number for your country. rok.auto/phonesupport
Literature Library Find installation instructions, manuals, brochures, and technical data publications. rok.auto/literature
Product Compatibility and Download Center Download firmware, associated files (such as AOP, EDS, and DTM), and access product release rok.auto/pcdc
(PCDC) 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.
Waste Electrical and Electronic Equipment (WEEE)
At the end of life, this equipment should be collected separately from any unsorted municipal waste.
Rockwell Automation maintains current product environmental information on its website at rok.auto/pec.
Allen-Bradley, CompactBlock LDX I/O, CompactLogix, Connected Components Workbench, ControlFLASH, ControlLogix, Data-Set, DH+, expanding human possibility, FactoryTalk, FactoryTalk Linx,
FactoryTalk Linx Gateway, Kinetix, Micro800, Micro810, Micro820, Micro830, Micro850, Micro870, PanelView Component, PanelView Plus, PartnerNetwork, PowerFlex, Rockwell Automation,
RSLinx, RSLinx Classic, RSLogix 500, and TechConnect are trademarks of Rockwell Automation, Inc.
CIP, DeviceNet, and EtherNet/IP are trademarks of ODVA, Inc.
Excel, Microsoft, Visual Studio, and Windows are trademarks of Microsoft Corporation.
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
Connect with us.
Publication 2080-UM002M-EN-E - April 2022

Supersedes Publication 2080-UM002L-EN-E - November 2021 Copyright © 2022 Rockwell Automation, Inc. All rights reserved.

Micro830-850-870 Manual

Uploaded by

Copyright:

Available Formats

Micro830-850-870 Manual

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Micro830-850-870 Manual

Uploaded by

Copyright:

Available Formats

Micro830, Micro850, and Micro870

User Manual Original Instructions

Important User Information

2 Rockwell Automation Publication 2080-UM002M-EN-E - April 2022

Rockwell Automation Publication 2080-UM002M-EN-E - April 2022 3

4 Rockwell Automation Publication 2080-UM002M-EN-E - April 2022

Rockwell Automation Publication 2080-UM002M-EN-E - April 2022 5

Axis States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

6 Rockwell Automation Publication 2080-UM002M-EN-E - April 2022

Use the High-Speed Counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270

8 Rockwell Automation Publication 2080-UM002M-EN-E - April 2022

Rockwell Automation Publication 2080-UM002M-EN-E - April 2022 9

10 Rockwell Automation Publication 2080-UM002M-EN-E - April 2022

You should have a basic understanding of electrical circuitry and familiarity

This manual is a reference guide for Micro800 controllers, plug-in modules,

See the Online Help provided with Connected Components Workbench™

Rockwell Automation Publication 2080-UM002M-EN-E - April 2022 11

12 Rockwell Automation Publication 2080-UM002M-EN-E - April 2022

You can view or download publications at rok.auto/literature.

You can download the latest version of Connected Components Workbench

Rockwell Automation Publication 2080-UM002M-EN-E - April 2022 13

14 Rockwell Automation Publication 2080-UM002M-EN-E - April 2022

This chapter provides an overview of the Micro830®, Micro850®, and

Rockwell Automation Publication 2080-UM002M-EN-E - April 2022 15

See Troubleshooting on page 303 for descriptions of status indicator operation

Micro830 24-point controllers and status indicators

16 Rockwell Automation Publication 2080-UM002M-EN-E - April 2022

Micro830 48-point controllers and status indicators

Status Indicator Description(1)

Rockwell Automation Publication 2080-UM002M-EN-E - April 2022 17

Status Indicator Description(1)

Micro850 48-point controllers and status indicators

18 Rockwell Automation Publication 2080-UM002M-EN-E - April 2022

Status Indicator Description(1)

Status Indicator Description(1)

Rockwell Automation Publication 2080-UM002M-EN-E - April 2022 19

Status Indicator Description(1) (Continued)

You can order replacement terminal blocks, catalog number 2080-RPL24RTB,

Table 1 - Micro830 Controllers – Number and Types of Inputs/Outputs

Table 2 - Micro850 Controllers – Number and Types of Inputs/Outputs

20 Rockwell Automation Publication 2080-UM002M-EN-E - April 2022

Table 2 - Micro850 Controllers – Number and Types of Inputs/Outputs (Continued)

Table 3 - Micro870 Controllers – Number and Types of Inputs/Outputs

Micro800 controllers have a USB interface, making standard USB cables

Embedded Serial Port Cables

Rockwell Automation Publication 2080-UM002M-EN-E - April 2022 21

Table 4 - Embedded Serial Port Cable Selection Chart

Embedded Ethernet Support

RJ-45 Ethernet Port Pin Mapping yellow LED

Micro850 and Micro870 controllers support Ethernet crossover cables

Ethernet Status Indication

See Troubleshooting on page 303 for descriptions of Module and Network

22 Rockwell Automation Publication 2080-UM002M-EN-E - April 2022

About Your Controller

Connected Components Workbench software provides a choice of IEC 61131-3

Obtain Connected Components Workbench Software

A free download is available at rok.auto/ccw.

Use Connected Components Workbench Software

To help you program your controller through the Connected Components

IMPORTANT The new Micro850 (2080-L50E) and Micro870 (2080-L70E) controllers