Allen-Bradley 2080-LC70-24QWB Owners Manual

Page 1

Micro830, Micro850, and Micro870 Programmable Controllers

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

Page 2

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.

These labels may also be on or inside the equipment to provide specific precautions.

SHOCK HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that dangerous voltage may be present.

BURN HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that surfaces may reach dangerous temperatures.

ARC FLASH HAZARD: Labels may be on or inside the equipment, for example, a motor control center, to alert people to potential Arc Flash. Arc Flash will cause severe injury or death. Wear proper Personal Protective Equipment (PPE). Follow ALL Regulatory requirements for safe work practices and for Personal Protective Equipment (PPE).

The following icon may appear in the text of this document.

Identifies information that is useful and can help to make a process easier to do or easier to understand.

2 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 3

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 1

Hardware Overview Hardware Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Micro830 Controllers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Micro850 Controllers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Micro870 Controllers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

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) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Uncommitted Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

RMC Memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Limitations of RMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Using Run Mode Configuration Change (RMCC). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Using Modbus RTU Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Using EtherNet/IP Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Safety Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Disconnect Main Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Safety Circuits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Power Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Periodic Tests of Master Control Relay Circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Power Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Isolation Transformers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Power Supply Inrush. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Loss of Power Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Input States on Power Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Other Types of Line Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Preventing Excessive Heat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Master Control Relay. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Using Emergency-Stop Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 3

Page 4

Table of Contents

Chapter 3

Install Your Controller Controller Mounting Dimensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Mounting Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

DIN Rail Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Panel Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Panel Mounting Dimensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

System Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Chapter 4

Wire Your Controller Wiring Requirements and Recommendation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Use Surge Suppressors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Recommended Surge Suppressors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Grounding the Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Wiring Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Controller I/O Wiring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Minimize Electrical Noise. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Analog Channel Wiring Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Minimize Electrical Noise on Analog Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Grounding Your Analog Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Wiring Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Embedded Serial Port Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Chapter 5

Communication Connections Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Supported Communication Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Modbus RTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

CIP Serial Client/Server – DF1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

ASCII . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Modbus TCP Client/Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

CIP Symbolic Client/Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

CIP Client Messaging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Sockets Client/Server TCP/UDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

CIP Communications

Pass-thru. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Examples of Supported Architectures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Use Modems with Micro800 Controllers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Making a DF1 Point-to-Point Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Construct Your Own Modem Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Configure Serial Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Configure CIP Serial Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Configure Modbus RTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Configure ASCII . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Configure Ethernet Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Validate IP Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Ethernet Host Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Configure CIP Serial Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

OPC Support Using FactoryTalk Linx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

4 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 5

Chapter 6

Table of Contents

Micro870 Controller Distributed Network Protocol

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Channel Configuration for DNP3 Slave. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Serial Port Link Layer Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Ethernet Layer Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

DNP3 Slave Application Layer Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Serial Link Layer Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Ethernet Layer Configuration Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

DNP3 Slave Application Layer Configuration Parameters . . . . . . . . . . . . . . . . . . . . 79

DNP3 Slave Application Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Function Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Internal Indications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

DNP3 Objects and Controller Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

DNP3 Object Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

DNP3 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

DNP3 Data Set Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Object Quality Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

DNP3 Device Attribute Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Event Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Generate Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

DNP3 10K Event Logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Control Generating Event. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Report Event By Polled Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Report Event By Unsolicited Response. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Collision Avoidance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Time Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Diagnostics for Ethernet Channel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Diagnostics for Secure Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Function Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Implementation Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Chapter 7

Program Execution in Micro800 Overview of Program Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Execution Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Optional Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Controller Load and Performance Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Periodic Execution of Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Power Up and First Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Variable Retention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Memory Allocation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Guidelines and Limitations for Advanced Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Chapter 8

EtherNet/IP Network Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

EtherNet/IP Network Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Star Network Topology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Implicit Messaging I/O Nodes on an EtherNet/IP Network . . . . . . . . . . . . . . . . . . . . . . 130

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 5

Page 6

Table of Contents

Devices Included in the Node Count. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Devices Excluded from the Node Count. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

How to Add PowerFlex 520-series and Kinetix 5100 Drives over EtherNet/IP. . . . . . . 131

Add a PowerFlex 523 or PowerFlex 525 Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Add a Kinetix 5100 Drive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Modify an Existing Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Module Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Requested Packet Interval. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Type Definition in Module Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Module Inhibiting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Predefined Tags in PowerFlex 520-series and Kinetix 5100 Drives . . . . . . . . . . . . . . . 138

Use of the User-defined Function Block Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Download the User-defined Function Block Instruction Files. . . . . . . . . . . . . . . . . . . . 144

Import the User-defined Function Block Instruction Files . . . . . . . . . . . . . . . . . . . . . . 144

Connection Fault Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Chapter 9

Motion Control PTO Motion Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Use the Micro800 Motion Control Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Input and Output Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Motion Control Function Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

General Rules for the Motion Control Function Blocks . . . . . . . . . . . . . . . . . . . . . . 163

Motion Axis and Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Axis States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Motion Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Motion Direction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Axis Elements and Data Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Axis Error Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

MC_Engine_Diag Data Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Function Block and Axis Status Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Major Fault Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Motion Axis Configuration in Connected Components Workbench. . . . . . . . . . . . . . . . 180

Add New Axis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Edit Axis Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Axis Start/Stop Velocity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Real Data Resolution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

PTO Pulse Accuracy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Motion Axis Parameter Validation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Delete an Axis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Monitor an Axis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Homing Function Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Conditions for Successful Homing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

MC_HOME_ABS_SWITCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

MC_HOME_LIMIT_SWITCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

MC_HOME_REF_WITH_ABS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

MC_HOME_REF_PULSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

MC_HOME_DIRECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Use PTO for PWM Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

6 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 7

Table of Contents

POU PWM_Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

HSC Feedback Axis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Chapter 10

Use the High-Speed Counter and Programmable Limit Switch

High-Speed Counter Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Programmable Limit Switch Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

What is High-Speed Counter? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Features and Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

HSC Inputs and Wiring Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

High-Speed Counter (HSC) Data Structures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

HSC APP Data Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

HSC STS (HSC Status) Data Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

High-Speed Counter (HSC) Function Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

HSC Commands (HScCmd) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

HSC_SET_STS Function Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

Programmable Limit Switch (PLS) Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

PLS Data Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

PLS Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

PLS Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

HSC Interrupts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

HSC Interrupt Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

HSC Interrupt POU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

HSC Interrupt Status Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

Chapter 11

Controller Security Protected Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Exclusive Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Password Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

Work with a Locked Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

Upload from a Password-Protected Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

Debug a Password-Protected Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

Download to a Password-Protected Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

Transfer Controller Program and Password-Protect Receiving Controller . . . . . 228

Back Up and Restore a Password-Protected Controller. . . . . . . . . . . . . . . . . . . . . 228

Configure Controller Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Recover from a Lost Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Using the Memory Module Plug-in. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Chapter 12

Using microSD Cards Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

Project Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

Backup and Restore Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

Power-up Settings in ConfigMeFirst.txt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

General Configuration Rules in ConfigMeFirst.txt . . . . . . . . . . . . . . . . . . . . . . . . . . 237

ConfigMeFirst.txt Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

Deliver Project Updates to Customers Through Email . . . . . . . . . . . . . . . . . . . . . . 238

Data Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 7

Page 8

Table of Contents

Data Log Directory Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

Data Log Function (DLG) Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

Recipe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

Recipe Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

Quickstart Projects for Data Log and Recipe Function Blocks . . . . . . . . . . . . . . . . . . . 248

Use the Data Log Feature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

Use the Recipe Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254

Appendix A

Modbus Mapping for Micro800 Modbus Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Endian Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Mapping Address Space and Supported Data Types. . . . . . . . . . . . . . . . . . . . . . . . 261

Example 1, PanelView 800 HMI (Master) to Micro800 (Slave) . . . . . . . . . . . . . . . . . 262

Example 2, Micro800 (Master) to PowerFlex 4M Drive (Slave) . . . . . . . . . . . . . . . . 263

Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

Appendix B

Quickstarts Flash Upgrade Your Micro800 Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

Flash Upgrade From MicroSD Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

Establish Communications Between RSLinx and a Micro830/Micro850/Micro870

Controller through USB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272

Configure Controller Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

Set Controller Password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

Change Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

Clear Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278

Use the High-Speed Counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

Create the HSC Project and Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

Assign Values to the HSC Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283

Assign Variables to the Function Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

Run the High-Speed Counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

Use the Programmable Limit Switch (PLS) Function . . . . . . . . . . . . . . . . . . . . . . . 287

Forcing I/Os. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288

Checking if Forces (locks) are Enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289

I/O Forces After a Power Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

Use Run Mode Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

Create the Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

Edit the Project Using Run Mode Change. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292

Appendix C

User Interrupts Information About Using Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295

What is an Interrupt? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295

When Can the Controller Operation be Interrupted?. . . . . . . . . . . . . . . . . . . . . . . . 296

Priority of User Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296

User Interrupt Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297

User Fault Routine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297

User Interrupt Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298

STIS - Selectable Timed Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298

UID - User Interrupt Disable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299

8 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 9

Table of Contents

UIE - User Interrupt Enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300

UIF - User Interrupt Flush . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301

UIC – User Interrupt Clear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302

Using the Selectable Timed Interrupt (STI) Function . . . . . . . . . . . . . . . . . . . . . . . . . . . 302

Selectable Time Interrupt (STI) Function Configuration and Status. . . . . . . . . . . . . . 303

STI Function Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303

STI Function Status Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304

Using the Event Input Interrupt (EII) Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305

Event Input Interrupt (EII) Function Configuration and Status . . . . . . . . . . . . . . . . . . 305

EII Function Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305

EII Function Status Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306

Appendix D

Troubleshooting Status Indicators on the Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307

Normal Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308

Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309

Fault Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309

Corrective Action for Recoverable and Non-recoverable Faults. . . . . . . . . . . . . . 313

Retrieve a Fault Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314

Controller Error Recovery Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315

Ethernet Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316

General Diagnostic Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

EtherNet/IP Overview Diagnostic Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319

System Diagnostic Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321

Controller Diagnostic Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322

Calling Rockwell Automation for Assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322

Appendix E

PID Function Blocks PID Function Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324

IPIDCONTROLLER Function Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326

How to Autotune . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328

How Autotune Works. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

Troubleshooting an Autotune Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

PID Application Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330

PID Code Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

Appendix F

System Loading Calculate Total Power for Your Micro830/Micro850/Micro870 Controller . . . . . . 333

Appendix G

Connect to Networks using DF1 DF1 Full-Duplex Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335

DF1 Half-Duplex Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336

DF1 Half-Duplex Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336

Considerations When Communicating as a DF1 Slave on a Multi-drop Link . . . . 337

Using Modems with Micro800 Programmable Controllers. . . . . . . . . . . . . . . . . . . 337

Modem Control Line Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338

DF1 Full-Duplex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338

DF1 Half-Duplex Slave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 9

Page 10

Table of Contents

User-defined Function Block Motion Instructions

DF1 Half Duplex Master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338

DF1 Radio Modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339

Configure DF1 Half-Duplex Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339

RTS Send Delay and RTS Off Delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339

Configure a Standard-Mode DF1 Half-Duplex Master Station . . . . . . . . . . . . . . . . . . . 340

Minimum DF1 Half-Duplex Master ACK Timeout. . . . . . . . . . . . . . . . . . . . . . . . . . . . 342

Determining Minimum Master ACK Timeout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342

DF1 Half-Duplex Master Communication Diagnostics. . . . . . . . . . . . . . . . . . . . . . . 343

Configure a Message-based Mode DF1 Half-Duplex

Master Station. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343

Configure a Slave Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346

Configure Poll Timeout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347

DF1 Half-Duplex Slave Communication Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . 347

Configure a Radio Modem Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348

DF1 Radio Modem Communication Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . 349

Configure the Store and Forward Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350

Appendix H

PowerFlex 520-series User-defined Function Block Details . . . . . . . . . . . . . . . . . . . . . 353

Kinetix 5100 Drive Device Object UDFB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355

Configure UDFBs for Kinetix 5100 Drives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357

raC_Dvc_K5100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357

raC_UDT_Itf_K5100_Cfg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357

raC_UDT_Itf_K5100_Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359

raC_UDT_Itf_K5100_Cmd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360

raC_UDT_Itf_K5100_Sts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360

UDFB Motion Instruction Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362

raC_Opr_K5100_MSO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362

raC_Opr_K5100_MSF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363

raC_Opr_K5100_MAFR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364

raC_Opr_K5100_MAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365

raC_Opr_K5100_MAJ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

raC_Opr_K5100_MAM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368

raC_Opr_K5100_MAI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372

raC_Opr_K5100_MAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374

raC_Opr_K5100_MAH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377

raC_Opr_K5100_MAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380

Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382

Index

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383

10 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 11

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.

Preface

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, EDS, and Other Files

Download firmware, associated files (such as AOP, EDS, and DTM), and access product release notes from the Product Compatibility and Download Center at rok.auto/pcdc.

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.

Top i c Page

Updated publication template Throughout Updated section Controller Load and Performance Considerations 124 Added chapter EtherNet/IP Network 129 Added section Ethernet Diagnostics to appendix Troubleshooting 316 Added appendix User-defined Function Block Motion Instructions 353

Additional Resources These documents contain additional information concerning related products from Rockwell

Automation. You can view or download publications at rok.auto/literature

Additional Resources

Resource Description

Micro800 Programmable Controller Family Selection Guide, publication 2080-SG001

Micro800 Programmable Controllers Technical Data, publication 2080-TD001

Micro800 Expansion I/O Modules User Manual, publication 2080-UM003

Micro800 Plug-in Modules User Manual, publication 2080-UM004

Micro800 Programmable Controllers General Instructions Reference Manual, publication 2080-RM001

Provides information to help you select the Micro800 controller, plug-ins, expansion I/O, and accessories, based on your requirements.

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 expansion I/O modules and power supply.

Information on features, configuration, installation, wiring, and specifications for the Micro800 plug-in modules.

Information on instruction sets for developing programs for use in Micro800 control systems.

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 11

Page 12

Additional Resources (Continued)

Resource Description

Micro800 Programmable Controllers: Getting Started with Motion Control Using a Simulated Axis Quick Start, publication 2080-QS001

Micro800 Programmable Controllers: Getting Started with CIP Client Messaging Quick Start, publication 2080-QS002

Micro800 Programmable Controllers: Getting Started with PanelView Plus Quick Start, publication 2080-QS003

Configuring Micro800 Controllers on FactoryTalk Linx Gateway Quick Start, publication 2080-QS005

Kinetix 3 Motion Control Indexing Application Connected Components Accel Toolkit Quick Start, publication CC-QS025

Motion Control PTO Application Building Block Quick Start, publication CC-QS033

Micro800 Programmable Controller External AC Power Supply Installation Instructions 2080-IN001

Micro800 Programmable Controllers Installation Instructions, publication 2080-IN013

Micro800 16-point and 32-point 12/24V Sink/Source Input Modules Installation Instructions, publication 2085-IN001

Micro800 Bus Terminator Module Installation Instruction, publication 2085-IN002

Micro800 16-Point Sink and 16-Point Source 12/24V DC Output Modules Installation Instructions, publication 2085-IN003

Micro800 8-Point and 16-Point AC/DC Relay Output Modules Installation Instructions, publication 2085-IN004

Micro800 8-Point Input and 8-Point Output AC Modules Installation Instructions, publication 2085-IN005

Micro800 4-channel and 8-channel Analog Voltage/current Input and Output Modules Installation Instructions, publication 2085-IN006

Micro800 4-channel Thermocouple/RTD Input Module Installation Instructions, publication 2085-IN007

Micro870 Programmable Controllers 24V DC Expansion Power Supply Installation Instructions, publication 2085-IN008

Micro800 RS-232/RS-485 Isolated Serial Port Plug-in Module Wiring Diagrams, publication 2080-WD002

Micro800 Non-isolated Unipolar Analog Input Plug-in Module Wiring Diagrams, publication 2080-WD003

Micro800 Non-isolated Unipolar Analog Output Plug-in Module Wiring Diagrams, publication 2080-WD004

Micro800 Non-isolated RTD Plug-in Module Wiring Diagrams, publication 2080-WD005

Micro800 Non-isolated Thermocouple Plug-in Module Wiring Diagrams, publication 2080-WD006

Micro800 Memory Backup and High Accuracy RTC Plug-In Module Wiring Diagrams, publication 2080-WD007

Micro800 6-Channel Trimpot Analog Input Plug-In Module Wiring Diagrams, publication 2080-WD008

Micro800 Digital Relay Output Plug-in Module Wiring Diagrams, publication 2080-WD010

Micro800 Digital Input, Output, and Combination Plug-in Modules Wiring Diagrams, publication 2080-WD011

Micro800 High-Speed Counter Plug-in Module Wiring Diagram, publication 2080-WD012

Micro800 DeviceNet Plug-in Module Wiring Diagram, publication 2080-WD013

EtherNet/IP Network Devices User Manual, publication ENET-UM006

Ethernet Reference Manual, publication ENET-RM002

System Security Design Guidelines Reference Manual, publication SECURE-RM001

Provides quick start instructions for implementing a motion control project in Connected Components Workbench software.

Provides quick start instructions for using CIP GENERIC and CIP Symbolic Messaging.

Provides quick start instructions for using global variables for Micro800 controllers together with PanelView™ Plus HMI terminals.

Provides quick start instructions for configuring a Micro800 controller on FactoryTalk Linx Gateway.

Provides quick start instructions for implementing a Kinetix 3 drive indexing application using Connected Components Workbench software and a Micro800 controller.

Provides quick start instructions for implementing PTO motion control of a Kinetix 3 drive using Connected Components Workbench software and a Micro800 controller.

Information on mounting and wiring the optional external power supply.

Information on mounting and wiring Micro800 Controllers

Information on mounting and wiring the expansion I/O modules (2085-IQ16, 2085-IQ32T)

Information on mounting and wiring the expansion I/O bus terminator (2085-ECR)

Information on mounting and wiring the expansion I/O modules (2085-OV16, 2085-OB16)

Information on mounting and wiring the expansion I/O modules (2085-OW8, 2085-OW16)

Information on mounting and wiring the expansion I/O modules (2085-IA8, 2085-IM8, 2085OA8)

Information on mounting and wiring the expansion I/O modules (2085-IF4, 2085-IF8, 2085OF4)

Information on mounting and wiring the expansion I/O module (2085-IRT4)

Information on mounting and wiring the optional external power supply for expansion I/O modules.

Information on mounting and wiring the Micro800 RS-232/RS-485 Isolated Serial Port Plugin Module.

Information on mounting and wiring the Micro800 Non-isolated Unipolar Analog Input Plugin Module.

Information on mounting and wiring the Micro800 Non-isolated Unipolar Analog Output Plugin Module.

Information on mounting and wiring the Micro800 Non-isolated RTD Plug-in Module.

Information on mounting and wiring the Micro800 Non-isolated Thermocouple Plug-in Module.

Information on mounting and wiring the Micro800 Memory Backup and High Accuracy RTC Plug-In Module.

Information on mounting and wiring the Micro800 6-Channel Trimpot Analog Input Plug-In Module.

Information on mounting and wiring the Micro800 Digital Relay Output Plug-in Module.

Information on mounting and wiring the Micro800 Digital Input, Output, and Combination Plug-in Modules.

Information on mounting and wiring the High-Speed Counter Plug-in module.

Information on mounting and wiring the Micro800 DeviceNet Describes how to configure and use EtherNet/IP devices to communicate on the EtherNet/IP

network. Describes basic Ethernet concepts, infrastructure components, and infrastructure features. Provides guidance on how to conduct security assessments, implement Rockwell

Automation products in a secure system, harden the control system, manage user access, and dispose of equipment.

plug-in module.

12 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 13

Additional Resources (Continued)

Resource Description

Industrial Components Preventive Maintenance, Enclosures, and Contact Ratings Specifications, publication IC-TD002

Safety Guidelines for the Application, Installation, and Maintenance of Solid-state Control, publication SGI-1.1

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.

Provides a quick reference tool for Allen-Bradley® industrial automation controls and assemblies.

Designed to harmonize with NEMA Standards Publication No. ICS 1.1-1987 and provides general guidelines for the application, installation, and maintenance of solid-state control in the form of individual devices or packaged assemblies incorporating solid-state components.

You can download the latest version of Connected Components Workbench software for your Micro800 controller at rok.auto/ccw

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 13

Page 14

Notes:

14 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 15

Hardware Overview

Chapter 1

This chapter provides an overview of the Micro830®, Micro850®, and Micro870® controller hardware features. It has the following topics:

Top ic Pa ge

Hardware Features 16 Micro830 Controllers 16 Micro850 Controllers 17 Micro870 Controllers 19 Programming Cables 21 Embedded Serial Port Cables 21 Embedded Ethernet Support 22

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 15

Page 16

Chapter 1 Hardware Overview

Micro830 10/16-point controllers and status indicators

Controller Status indicator

Micro830 24-point controllers and status indicators

Controller Status indicator

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 307 for descriptions of status indicator operation for

troubleshooting purposes.

Micro830 Controllers

12 3 4 5 6 7 8

15 16 17 18 19

79610111213

16 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

15 16 17 18 19

89910111213 6

Page 17

Chapter 1 Hardware Overview

Micro830 48-point controllers and status indicators

Status indicatorController

17 18 19 20

22 23

Status indicators

12 3 4 5 6 7 8

81061112131415 910

Micro850 24-point controllers and status indicators

Controller

12111013 6 9 8

34 5 6 7 88

15 16 17 18 19

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 7Right-side cover

Status Indicator Description

(1)

Description Description

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 307.

Micro850 Controllers

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 17

Page 18

Chapter 1 Hardware Overview

Status indicators

12 345 8 6 87

981061112131415

Micro850 48-point controllers and status indicators

Controller

Controller Description

Description Description

1 Status indicators 9 Expansion I/O slot cover 2 Optional power supply slot 10 DIN rail mounting latch 3 Plug-in latch 11 Mode switch 4 Plug-in screw hole 12 Type B connector USB port 5 40-pin high-speed plug-in connector 13 RS-232/RS-485 non-isolated combo serial port

6 Removable I/O terminal block 14

7 Right-side cover 15 Optional power supply 8 Mounting screw hole / mounting foot

RJ-45 Ethernet connector (with embedded green and yellow LED indicators)

Status Indicator Description

(1)

Description Description

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 307.

17 18 19 20 21 22

Controller Description

Description Description

18 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

6 Removable I/O terminal block 14

7 Right-side cover 15 Optional AC power supply 8 Mounting screw hole / mounting foot

RJ-45 EtherNet/IP connector (with embedded yellow and green LED indicators)

Page 19

Chapter 1 Hardware Overview

Status indicators

12 3 4 5 6 7 8

81061112131415 910

Micro870 24-point controllers and status indicators

Controller

Status Indicator Description

Description Description

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 these LED status indicators, see Troubleshooting on page 307.

(1)

You can order the following replacement terminal blocks separately:

• 2080-RPL24RTB for 24-point base controllers

• 2080-RPL48RTB for 48-point base controllers

Micro870 Controllers

17 18 19 20 21 22 23

Controller Description

6 Removable I/O terminal block 14

7 Right-side cover 15 Optional power supply 8 Mounting screw hole / mounting foot

Status Indicator Description

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 307.

Description Description

RJ-45 Ethernet connector (with embedded green and yellow LED indicators)

(1)

Description Description

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 19

Page 20

Chapter 1 Hardware Overview

You can order replacement terminal blocks, catalog number 2080-RPL24RTB, separately.

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

Catalog Number

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 110V AC 24V DC/V AC Relay 24V Sink 24V Source

PTO Support HSC Support

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

Catalog Number

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 –2820––– 6 2080-L50E-48QWBK –2820––– 6 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 120V AC 24V DC/V AC Relay 24V Sink 24V Source

PTO Support HSC Support

20 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 21

Table 3 - Micro870 Controllers – Number and Types of Inputs/Outputs

Chapter 1 Hardware Overview

Catalog Number

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

Inputs Outputs 120V AC 24V DC/V AC Relay 24V Sink 24V Source

PTO Support HSC Support

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)

8-pin Mini DIN to 8-pin Mini DIN 2 m (6.5 ft) 8-pin Mini DIN to 8-pin Mini DIN (with

lock mechanism on both connectors)

—

(1) Series C or later for Class 1 Div 2 applications.

2 m (6.5 ft) 1761-CBL-AH02

1761-CBL-AM00

1761-CBL-HM02

(1)

8-pin Mini DIN to 9-pin D Shell 0.5 m (1.5 ft)

8-pin Mini DIN to 9-pin D Shell 2 m (6.5 ft) 8-pin Mini DIN with lock mechanism to

9-pin D Shell 8-pin Mini DIN to 6-pin RS-485 terminal

block

2 m (6.5 ft) 1761-CBL-PH02

30 cm (11.8in.) 1763-NC01 series A

1761-CBL-AP00

1761-CBL-PM02

(1)

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 21

Page 22

Chapter 1 Hardware Overview

Yell ow LED

Green LED

RJ-45 connector

RJ-45 Ethernet Port Pin Mapping

Contact Number

Signal Direction Primary Function

1TX+OUTTransmit data + 2TX-OUTTransmit data -

3RX+IN

Differential Ethernet receive

data + 4Terminated 5Terminated

6RX-IN

Differential Ethernet receive

data 7Terminated 8Terminated Shield Chassis ground

The yellow status LED indicates Link (solid yellow) or No Link (off).

The green status LED indicates activity (blinking green) or no activity (off).

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.

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 307 for descriptions of Module and Network status indicators.

22 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 23

About Your Controller

Chapter 2

Programming Software for Micro800 Controllers

Connected Components Workbench software is a set of collaborative tools 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 Mode

Using Run Mode Change (RMC)

Micro820®/Micro830/Micro850/Micro870 controllers allow you to make 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)

• 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)

Run Mode Change (RMC) is a productivity enhancement feature supported in 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.

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 23

on page 23.

on page 27.

Page 24

Chapter 2 About Your Controller

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 Changes

136 29 5180 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

Time to Perform Conventional Download (seconds)

ATTENTION:

Use extreme caution when you use Run Mode Change. Mistakes

Time to Test Logic and Accept Changes (seconds)

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 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 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.

24 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 25

Chapter 2 About Your Controller

Controller Memory (for User Program + Data)

RMC Memory (Default size = 2KB)

Used memory

Free memory

Used RMC memory

Free RMC memory

1st change and Test Logic (Add logic)

2nd change and Test Logic (Remove logic)

3rd change and Test Logic (Add logic)

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

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 25

Page 26

Chapter 2 About Your Controller

Controller Memory (for User Program + Data)

RMC Memory (Default size = 2KB)

New used memory

Free memory

Free RMC memory

Used RMC memory is copied to controller memory

Controller Memory (for User Program + Data)

RMC Memory (Default size = 2KB)

Error will occur due to insufficient controller memory remaining

Free 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

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

26 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 27

Chapter 2 About Your Controller

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 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

• 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.

✟ Reset Initial Values of Instances.

(1)

) and user variables and

Using Run Mode Configuration Change (RMCC)

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

Run Mode Configuration Change (RMCC) is a productivity enhancement feature supported in Connected Components Workbench software for Micro820/Micro830/Micro850/Micro870 controllers. It allows users to reuse 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

on page 290 for an example on how to use this feature.

perform RMCC if the controller is performing time critical operations.

(1) Approximately 85 boolean instructions for Micro850 (2080-L50E) and Micro870 (2080-L70E) controllers.

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 27

Page 28

Chapter 2 About Your Controller

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

Instance

Attribute 100 ReqData New node address, 1 ReqLen 2

2 – Embedded serial port 5, 6, 7, 8, or 9 – Plug-in modules

28 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 29

Chapter 2 About Your Controller

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

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 29

Page 30

Chapter 2 About Your Controller

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

30 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 31

Chapter 2 About Your Controller

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.

WA RN I NG : Explosion Hazard Do not replace components, connect equipment, or disconnect equipment unless power has been switched off.

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 31

Page 32

Chapter 2 About Your Controller

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.

WA RN I NG : 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.

32 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 33

Chapter 2 About Your Controller

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 holdup 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 35

and Figure 2 on page 36.

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 33

Page 34

Chapter 2 About Your Controller

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 emergencystop 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 emergencystop 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. Emergencystop 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.

34 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 35

Figure 1 - Schematic – Using IEC Symbols

Disconnect

Isolation transformer

Emergency-stop push button

Fuse

MCR

230V AC I/O circuits

Operation of either of these contacts will remove power from the external I/O circuits, stopping machine motion.

Fuse

Overtravel limit switch

MCR

Stop

Start

Line terminals: Connect to terminals of power supply.

115V AC or 230V AC I/O circuits

L1 L2

230V AC

Master Control Relay (MCR) Cat. No. 700-PK400A1

Suppressor Cat. No. 700-N24

MCR

Suppr.

24V DC I/O circuits

(Lo)

(Hi)

DC power supply. Use IEC 950/EN 60950

X1 X2

115V AC or

230V AC

Line terminals: Connect to 24V DC terminals of power supply.

Chapter 2 About Your Controller

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 35

Page 36

Chapter 2 About Your Controller

Emergency-stop push button

230V AC

Operation of either of these contacts will remove power from the external I/O circuits, stopping machine motion.

Fuse

MCR

Fuse

MCR

Stop

Start

Line terminals: Connect to terminals of power supply

Line terminals: Connect to 24V DC terminals of power supply.

230V AC output circuits

Disconnect

Isolation transformer

115V AC or 230V AC I/O circuits

Master Control Relay (MCR) Cat. No. 700-PK400A1

Suppressor Cat. No. 700-N24

(Lo)

(Hi)

DC power supply. Use NEC Class 2 for UL Listing.

X1 X2

115V AC or

230V AC

MCR

24 V DC I/O circuits

Suppr.

Overtravel limit switch

Figure 2 - Schematic – Using ANSI/CSA Symbols

36 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 37

Chapter 3

100 (3.94)

80 (3.15)

90 (3.54)

Measurements in mm (in.)

150 (5.91)

80 (3.15)

90 (3.54)

Measurements in mm (in.)

Install Your Controller

This chapter serves to guide the user on installing the controller. It includes the following topics.

Top ic Pa ge

Controller Mounting Dimensions 37 Mounting Dimensions 37 DIN Rail Mounting 39 Panel Mounting 39

Controller Mounting Dimensions

Mounting 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

Micro830 24-point Controllers 2080-LC30-24QW8B, 2080-LC30-24QVB, 2080-LC30-24QBB

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 37

Page 38

Chapter 3 Install Your Controller

230 (9.06)

80 (3.15)

90 (3.54)

Measurements in mm (in.)

158 (6.22)

80 (3.15)

90 (3.54)

Measurements in mm (in.)

238 (9.37)

80 (3.15)

90 (3.54)

Measurements in mm (in.)

Micro830 48-point Controllers 2080-LC30-48AWB, 2080-LC30-48QWB, 2080-LC30-48QVB, 2080-LC30-48QBB

Micro850 24-point Controllers 2080-LC50-24AWB, 2080-LC50-24QBB, 2080-LC50-24QVB, 2080-LC50-24QWB, 2080-L50E-24AWB, 2080-L50E-24QBB, 2080-L50E-24QVB, 2080-L50E-24QWB Micro870 24-point Controllers 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

Micro850 48-point Controllers 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,

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.

38 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 39

Chapter 3 Install Your Controller

86 mm (3.39 in.)

100 mm (3.94 in.)

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

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 39

Page 40

Chapter 3 Install Your Controller

131 mm (5.16 in.)

100 mm (3.94 in.)

108 mm (4.25 in.) 108 mm (4.25 in.)

100 mm (3.94 in.)

Micro830 24-Point Controllers 2080-LC30-24QWB, 2080-LC30-24QVB, 2080-LC30-24QBB Micro850 24-point Controllers 2080-LC50-24AWB, 2080-LC50-24QBB, 2080-LC50-24QVB, 2080-LC50-24QWB, 2080-L50E-24AWB, 2080-L50E-24QBB, 2080-L50E-24QVB, 2080-L50E-24QWB Micro870 24-point Controllers 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

Micro830 48-Point Controllers 2080-LC30-48AWB, 2080-LC30-48QWB, 2080-LC30-48QVB, 2080-LC30-48QBB Micro850 48-point Controllers 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

40 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 41

System Assembly

)

Expansion I/O slots

(Applicable to Micro850 and Micro870 only)

Single-width (1st slot) Double-width (2nd slot) 2085-ECR (terminator)

Micro830/Micro850/Micro870 24-pt controller with Micro800 power supply

Measurements in mm (in.)

80 (3.15)

87 (3.42)

Expansion I/O Slots

(Applicable to Micro850 and Micro870 only)

Single-width (1st slot) Double-width (2nd slot) 2085-ECR (terminator)

Micro830/Micro850/Micro870 24-pt controller with Micro800 power supply

Measurements in mm (in.)

Micro830, Micro850, and Micro870 24-point Controllers (Front)

45 (1.77) 145.2 (5.72)

27.8 (1.09)

Chapter 3 Install Your Controller

44.4 (1.75) 14.4 (0.567

110.8 (4.36)

7.2 (0.28)

100

(3.94)

(3.54)

33.8 (1.33)

7.2 (0.28)

131 (5.16)

7.8 (0.31) 7.8 (0.31)

36.6 (1.44)

22.8 (0.90)

Micro830, Micro850, and Micro870 24-point Controllers (Side)

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 41

Page 42

Chapter 3 Install Your Controller

45 (1.77)

33.8

(1.33)

7.2 (0.28)

7 (0.27)

108 (4.25)

230 (9.05)

7.8

(0.31)

27.8 (1.09)

7.8

44.4 (1.75)

14.4 (0.57)

216 (8.50)

7 (0.27)

22.8 (0.90)

36.6 (1.44)

100.1

110.8 (4.36)

(3.94)

(3.54)

Expansion I/O Slots

(Applicable to Micro850 only)

Single-width (1st slot) Double-width (2nd slot) 2085-ECR (terminator)

Micro830/Micro850 48 pt Controller with Micro800 Power Supply

Measurements in mm (in.)

80 (3.15)

87 (3.42)

Expansion I/O Slots

(Applicable to Micro850 only)

Single-width (1st slot) Double-width (2nd slot) 2085-ECR (terminator)

Micro830/Micro850 48-pt controller with Micro800 power supply

Measurements in mm (in.)

Micro830 and Micro850 48-point Controllers (Front)

Micro830 and Micro850 48-point Controllers (Side)

42 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 43

Chapter 4

Wire Your Controller

This chapter provides information on the Micro830, Micro850, and Micro870 controller wiring requirements. It includes the following sections:

Top ic Pa ge

Wiring Requirements and Recommendation 43 Use Surge Suppressors 44 Recommended Surge Suppressors 45 Grounding the Controller 46 Wiring Diagrams 46 Controller I/O Wiring 50 Minimize Electrical Noise 50 Analog Channel Wiring Guidelines 50 Minimize Electrical Noise on Analog Channels 50 Grounding Your Analog Cable 51 Wiring Examples 51 Embedded Serial Port Wiring 52

Wiring Requirements and Recommendation

WA RN I NG : Before you install and wire any device, disconnect power to the

controller system.

WA RN I NG : 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.

• 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.

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 43

Page 44

Chapter 4 Wire Your Controller

+DC or L1

Suppression device

DC COM or L2

AC or DC outputs

Load

VAC /DC Out 0

Out 1 Out 2

Out 3

Out 4 Out 5

Out 6

Out 7 COM

+24V DC

IN4004 diode

Relay or solidstate DC outputs

24V DC common

VAC /DC

Out 0 Out 1

Out 2 Out 3 Out 4 Out 5

Out 6 Out 7 COM

A surge suppressor can also be used.

Wire Requirements

Wire Size Type Min Max

Micro830/ Micro850/ Micro870 Controllers

Solid

Stranded

0.2 mm2 (24 AWG) 2.5 mm2 (12 AWG)

0.2 mm

(24 AWG) 2.5 mm2 (12 AWG)

rated @ 90 °C (194 °F) insulation max

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

If the outputs are DC, we recommend that you use an 1N4004 diode for surge suppression, as shown in Figure 4. 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 45. These surge suppression circuits connect directly across the

load device.

Figure 4 - DC Outputs with Surge Suppression

44 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

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 appropriately rated to suppress the switching transient characteristic of the particular inductive device. See Recommended Surge Suppressors suppressors.

. These components must be

on page 45 for recommended

Page 45

Output device Output deviceOutput device

Varistor

RC network

Surge suppressor

Recommended Surge Suppressors

Chapter 4 Wire Your Controller

Figure 5 - Surge Suppression for Inductive AC Load Devices

Recommended Surge Suppressors

Use the Allen-Bradley surge suppressors shown in the following table for use with relays, contactors, and starters.

Device Coil Voltage Suppressor Catalog Number

Type

(1)

24…48V AC 100-KFSC50

RC110…280V AC 100-KFSC280

380…480V AC 100-KFSC480

Bulletin 100/104K 700K

12…55 V AC, 12…77V DC 100-KFSV55

MOV56…136 VAC, 78…180V DC 100-KFSV136 137…277V AC, 181…250 V DC 100-KFSV277 12…250V DC 100-KFSD250 Diode

(2)

(1)

RC110…280V AC

MOV

Diode

MOV

(3)

(4)

MOV

Bulletin 100C, (C09…C97)

Bulletin 509 Motor Starter Size 0...5

Bulletin 509 Motor Starter Size 6

24…48V AC

100-FSC48

100-FSC280

380…480V AC

12…55V AC, 12…77V DC

56…136V AC, 78…180V DC

137…277V AC, 181…250V DC

278…575V AC

12…250V DC

100-FSC480

100-FSV55

100-FSV136

100-FSV277

100-FSV575

100-FSD250 12…120V AC 599-K04 240…264V AC 599-KA04

12…120V AC

199-FSMA1

199-GSMA1 AC coil Not Required

Bulletin 700 R/RM Relay

24…48V DC 199-FSMA9

MOV50…120V DC 199-FSMA10 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

MOV50…120V AC/DC 199-FSMA10 130…250V AC/DC 199-FSMA11 6…300V DC 199-FSMZ-1 Diode

Miscellaneous electromagnetic devices limited to 35 sealed VA

(1) RC Type not to be used with Triac outputs. Varistor is not recommended for use on the relay outputs. (2) 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. (3) For use on the interposing relay. (4) For use on the contactor or starter.

6…150V AC/DC 700-N24 RC

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 45

Page 46

Chapter 4 Wire Your Controller

Input terminal block

Output terminal block

Input terminal block

Output terminal block

Input terminal block

Output terminal block

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

COM0 I-01

I-03

I-04

123456789101112

I-00

+DC24 CM0

I-02

CM1

COM1

CM2

I-05 NC

CM3

123456789101112

O-00-DC24

O-01

O-02 O-03

2080-LC30-10QVB

COM0 I-01

123456789101112

I-00

+DC24 +CM0

123456789101112

I-03

I-02

O-01

O-00-DC24

COM1

-CM0

I-04

I-05 NC

+CM1

O-02 -CM1

O-03

2080-LC30-16AWB, 2080-LC30-16QWB

COM0 I-01

123456789101112

I-00

I-02

I-03

COM1

I-04

I-05 I-07

I-06

I-08

I-09

+DC24 CM0

CM1

CM2

CM3

123456789101112

O-00-DC24

2080-LC30-16AWB has no high-speed inputs.

O-01

O-02 O-03

46 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

O-04

O-05

Page 47

2080-LC30-16QVB

Input terminal block

Output terminal block

Input terminal block

Output terminal block

I-00

COM0 I-01

I-02

I-03

I-04

I-05

I-06 COM1

I-07

I-09

I-08

123456789101112

+DC24 CM0

O-00-DC24

CM1

O-01

CM2

O-02 O-04

O-03

CM3

O-05

123456789101112

I-11

I-10

I-13

I-12

13 14 15 16

O-07

O-06

O-09

O-08

13 14 15 16

-24 VDC

+24 VDC

L1 L2

2080-PS120-240VAC

Sourcing:+DC b Sinking: -DC b

Sourcing:-DC b Sinking: +DC b

Sourcing:+DC a Sinking: -DC a

Sourcing:-DC a Sinking: +DC a

-DC c

CR CR

+DC c

L2 c

L1 cL1 b

+DC c

-DC c

L2 b

Chapter 4 Wire Your Controller

COM0 I-01

I-03

I-04

I-06

I-08

123456789101112

I-00

+DC24 +CM0

I-02

O-01

COM1

+CM1

I-05 I-07

O-03

I-09

O-04

123456789101112

O-00-DC24

-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

123456789101112

I-00

+DC24 CM0

123456789101112

I-03

I-05

I-07

I-08

I-10

I-12

13 14 15 16

I-02

CM1

I-04

I-06 COM1

CM2

O-03

O-05

I-09

O-06

I-11

I-13

O-08

13 14 15 16

O-00-DC24

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

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

• In Micro870 systems that use more than four Micro800 Expansion I/O

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 47

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.

Page 48

Chapter 4 Wire Your Controller

I-00

COM0 I-01

I-02

I-03

I-04

I-05

I-06 COM1

I-07

I-09

I-08

123456789101112

+DC24 CM0

O-00-DC24

CM1

O-01

CM2

O-02 O-04

O-03

CM3

O-05

123456789101112

I-11

I-10

I-13

I-12

13 14 15 16

O-07

O-06

O-09

O-08

13 14 15 16

-24 VDC

+24 VDC

L1 L2

2080-PS120-240VAC

L2 a

-DC c

CR CR

+DC c

L2 c

L1 cL1 b

+DC c

-DC c

L2 b

L1 a

L2 b

L1 b

Input terminal block

Output terminal block

I-00

COM0 I-01

I-02

I-03

I-04

I-05

I-06 COM1

I-07

I-09

I-08

123456789101112

+DC24 +CM0

O-00-DC24

O-01

-CM0

+CM1

O-02 O-04

O-03

O-06

O-05

123456789101112

I-11

I-10

I-13

I-12

13 14 15 16

O-08

O-07

-CM1

O-09

13 14 15 16

-24 VDC

+24 VDC

L1 L2

2080-PS120-240VAC

-DC d

CR CR

Sourcing:+DC b Sinking: -DC b

Sourcing:-DC b Sinking: +DC b

Sourcing:+DC a Sinking: -DC a

Sourcing:-DC a Sinking: +DC a

-DC e

+DC e

+DC d

2080-LC50-24AWB, 2080-L50E-24AWB, 2080-LC70-24AWB, 2080-L70E-24AWB, DC Input Configuration

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

123456789101112

I-00

+DC24 +CM0

123456789101112

I-03

I-05

I-07

I-08

I-10

I-12

13 14 15 16

I-02

O-01

I-04

I-06 COM1

+CM1

O-03

O-05

I-09

O-07

I-11

I-13

O-09

13 14 15 16

O-00-DC24

-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, DC Input Configuration

48 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 49

Chapter 4 Wire Your Controller

I-00

COM0 I-01

I-02

I-03

I-04

I-05

I-06 COM1

I-07

I-09

I-08

123456789101112

+DC24 +CM0

O-00-DC24

O-01

-CM0

+CM1

O-02 O-04

O-03

O-06

O-05

123456789101112

I-11

I-10

I-13

I-12

13 14 15 16

O-08

O-07

-CM1

O-09

13 14 15 16

-24 VDC

+24 VDC

L1 L2

2080-PS120-240VAC

-DC d

CR CR

Sourcing:+DC b Sinking: -DC b

Sourcing:-DC b Sinking: +DC b

Sourcing:+DC a Sinking: -DC a

Sourcing:-DC a Sinking: +DC a

-DC e

+DC e+DC d

Input terminal blocks

Output terminal blocks

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

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

COM0 I-01

123456789101112

I-00

I-13 I-15

123456789101112

+DC24 CM0

123456789101112

-DC24

CM7 O-08

123456789101112

I-03

I-05

I-02

I-04

TERMINAL BLOCK 1

I-17

I-19

I-16I-14

I-18

TERMINAL BLOCK 3

CM1

CM2

O-10

O-01

O-11

TERMINAL BLOCK 2

CM8

TERMINAL BLOCK 4

O-00

O-09O-07

2080-LC30-48AWB has no high-speed inputs.

I-06

COM1

I-20

COM3 I-21

CM3

O-02 O-03

O-13

O-12 O-14

I-08

I-10

I-22

O-04

CM9

13 14 15 16

I-09

I-24

13 14 15 16

I-23

CM5

13 14 15 16

O-16

13 14 15 16

I-07

CM4

O-15

COM2

I-11

I-12

I-26

I-25

I-27

CM6

O-05

O-06

O-18

O-17

O-19

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 49

Page 50

Chapter 4 Wire Your Controller

I-00

COM0 I-01

I-02

I-03

I-04

I-05

COM1 I-07

I-06

I-09

I-08

123456789101112

I-13 I-15

I-16I-14

I-17

I-18

I-19

COM3 I-21

I-20

I-23

I-22

123456789101112

I-11

I-10

I-12

COM2

13 14 15 16

I-25

I-24

I-27

I-26

13 14 15 16

-DC24

+DC24 +CM0

O-00

O-01

O-02

O-03

-CM0 O-04

+CM1

O-06

O-05

123456789101112

+CM2 O-11

O-12O-10

O-13

O-14

O-15

-CM2 O-16

+CM3

O-18

O-17

123456789101112

O-08

O-07

-CM1

O-09

13 14 15 16

-CM3

O-19

13 14 15 16

TERMINAL BLOCK 1

TERMINAL BLOCK 3

TERMINAL BLOCK 2

TERMINAL BLOCK 4

Input terminal blocks

Output terminal blocks

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

Controller I/O Wiring This section contains some relevant information about minimizing electrical noise and also

includes some wiring examples.

50 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

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:

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.

• 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.

Page 51

Chapter 4 Wire Your Controller

Foil shield

Black wire

Drain wire

Clear wire

Insulation

DC COM

OUT

+V DC

–

24V supply

Logic side

User side

Load

Fuse

Sink output wiring example

Micro800 Sink output

Com

Fuse

24V DC

I/P

Sink input wiring example

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.

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.

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 51

Page 52

Chapter 4 Wire Your Controller

DC COM

OUT

+V DC

–

24V supply

Logic side

User side

Load

Fuse

Source output wiring example

Micro800 source output

Source input wiring example

678

Com

I/P

Fuse

24V DC

Embedded Serial Port Wiring

The embedded serial port is a non-isolated RS-232/RS-485 serial port, which is 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

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 8RS-485- A(-) (not used)

52 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 53

Chapter 4 Wire Your Controller

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.

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 53

Page 54

Chapter 4 Wire Your Controller

Notes:

54 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 55

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:

Top ic Pa ge

Supported Communication Protocols 55 CIP Communications Pass-thru 59 Use Modems with Micro800 Controllers 60 Configure Serial Port 60 Configure Ethernet Settings 66 Configure CIP Serial Driver 68 OPC Support Using FactoryTalk Linx 68

Supported Communication Protocols

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.

Micro830, Micro850, and Micro870 controllers support communication 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

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

(1)

(1) DNP3 is only supported on 2080-L70E-24QxBN controllers.

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 55

Page 56

Chapter 5 Communication Connections

Connection Limits for Micro830/Micro850/Micro870 Controllers

Description Micro830

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

Maximum number of EtherNet/IP connections

Maximum number of USB connections

Maximum number of Serial connections

TCP Connections

Total number of client plus server connections

Maximum number for EtherNet/IP

Maximum number for Modbus TCP

Maximum number for User Programmable Sockets 8

User Programmable Sockets

Total number of User Programmable Sockets (any combination of UDP plus TCP Client/Server)

Client Server 23 Client – – Server 15 23 Client 15 16 Server 15 23

Client 16 Server 16 Client 16 Server 16

–

–8

Micro850/ Micro870

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 To configure the serial port as Modbus RTU, see Configure Modbus RTU

on page 261.

on page 64.

Use MSG_MODBUS instruction to send Modbus messages over serial port.

56 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 57

Chapter 5 Communication Connections

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 65.

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

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.

on page 261.

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 FullDuplex 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.

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 57

Page 58

Chapter 5 Communication Connections

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 To configure for EtherNet/IP, see Configure Ethernet Settings For more information on DF1 protocol, see Connect to Networks using DF1

on page 61.

on page 66.

on page 335.

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

BOOL

SINT Signed 8-bit integer value INT Signed 16-bit integer value DINT Signed 32-bit integer value

LINT USINT Unsigned 8-bit integer value UINT Unsigned 16-bit integer value UDINT Unsigned 32-bit integer value

ULINT REAL 32-bit floating point value

LREAL STRING character string (1 byte per character)

DATE

TIME

(1) Logix MSG instruction can read/write SINT, INT, DINT, LINT, and REAL data types using “CIP Data Table Read” and “CIP Data

(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.

(1)

(2)

(3)

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.

Description

Logical Boolean with values TRUE(1) and FALSE(0) (Uses up 8 bits of memory)

Signed 64-bit integer value

Unsigned 64-bit integer value

64-bit floating point value

Unsigned 32-bit integer value

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

58 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 59

Chapter 5 Communication Connections

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.

For program download

Micro850

controller1

Micro830

controller2

EtherNet/IP

CIP Serial

For program download

Esc

Sel

For program download

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-thru

The Micro830, Micro850, and Micro870 controllers support pass-thru on any 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 to CIP Serial

Micro850

controller1

EtherNet/IP

Micro850

controller2

Micro850

controller3

USB to DeviceNet

USB

Micro850 controller

2080-DNET20 plug-in scanner

(Address 0)

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 59

with

DeviceNet

PowerFlex 525 drive

with

25-COMM-D adapter

(Address 1)

CompactBlock™ LDX I/O

(Address 2)

Page 60

Chapter 5 Communication Connections

DeviceNet

PowerFlex 525 drive

with

25-COMM-D adapter

(Address 1)

EtherNet/IP

Esc

Sel

Micro850 controller

with

2080-DNET20 plug-in scanner

(Address 0)

CompactBlock LDX I/O

(Address 2)

The user can use Connected Components Workbench software to configure the PowerFlex drives.

For program download

DTE Device (Micro830/850/870 Channel 0)

DCE Device (Modem, etc)

niP-9niP-52niP-8

32DXTDXT7

23DXRDXR4

57DNGDNG2

18DCD)+(B1

402RTD)-(A8

66RSDDCD5

85STCSTC6

74STRSTR3

EtherNet/IP to DeviceNet

IMPORTANT Micro800 controllers do not support more than one hop (for example,

from EtherNet/IP -> CIP Serial -> EtherNet/IP).

Use Modems with Micro800 Controllers

Serial modems can be used with the Micro830, Micro850, and Micro870 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 25pin or 9-pin connector. See the following typical pinout for constructing a straight-through cable:

Configure Serial Port You can configure the serial port driver as CIP Serial, Modbus RTU, ASCII, or Shutdown through

60 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

the Device Configuration tree in the Connected Components Workbench software.

Page 61

Chapter 5 Communication Connections

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.

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 61

Page 62

Chapter 5 Communication Connections

Table 5 - CIP Serial Driver Parameters

Parameter Options Default

Baud Rate

Parity

Station (Node) Address

(1)

DF1 Mode

Control Line

Duplicate Packet Detection

Error Detection Toggles between CRC and BCC. CRC

Embedded Responses

NAK Retries

ENQ Retries

Transmit Retries

ACK Timeout (x20 ms)

EOT Suppression

Poll Timeout (x20 ms)

RTS Off Delay (x20 ms)

RTS Send Delay (x20 ms)

Message Retries

Toggles between the communication rate of 1200, 2400, 4800, 9600, 19200, and 38400.

Specifies the parity setting for the serial port. Parity provides additional message-packet error detection. Select Even, Odd, or None.

Enter a value from 0…254. Enter 1 for DF1 Full-Duplex.

Defines the DF1 mode – Full-Duplex, Half-Duplex master, Half-Duplex slave, Radio Modem

(2)

• Full-Duplex: No Handshake, Full-Duplex (RTS always ON).

• Half-Duplex slave: No Handshake, Half-Duplex without continuous carrier (RTS/CTS).

• Half-Duplex master: No Handshake, Half-Duplex without 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 packets may be sent under noisy communication conditions when the sender’s retries are not set to 0. Toggles between Enabled and Disabled.

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 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 because the controller received a NAK response to the previous message packet transmission.

The number of enquiries (ENQs) that you want the controller to send after an ACK timeout occurs.

Specifies the number of times a message is retried after the first attempt before being declared undeliverable. Enter a value from 0…127.

Specifies the amount of time after a packet is transmitted that an ACK is expected.

Enabled, Disabled When EOT Suppression is enabled, the slave does not respond when polled if no message is queued. This saves modem 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 receive a poll within the Poll Timeout, a MSG instruction error is 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.

0...65,535 (can be set in 20 ms increments)

Specifies the delay time between when the last serial character is sent to the modem and when RTS is deactivated. Gives the modem extra time to transmit the last character of a packet.

0...65,535 (can be set in 20 ms increments)

Specifies the time delay between setting RTS until checking for the CTS response. For use with modems that are not ready to respond with CTS immediately upon receipt of RTS.

0...255

Specifies the number of times a slave device attempts to resend a message packet when it does not receive an ACK from the master device. For use in noisy environments where message packets may become corrupted in transmission.

38400

None

Configured as fullduplex by default.

Configured as no handshake by default.

Enabled

After One Received

Disabled

3000

62 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 63

Chapter 5 Communication Connections

Table 5 - CIP Serial Driver Parameters (Continued)

Parameter Options Default

Priority Polling Range – High

Priority Polling Range – Low

Normal Polling Range – High

Normal Polling Range – Low

Normal Poll Group Size

Reply Message Wait Timeout

Polling Mode

(1) For more information on DF1 protocol, see Connect to Networks using DF1 on page 335 (2) Half-Duplex and Radio Modem DF1 modes are only supported on Micro850 (2080-L50E) and Micro870 (2080-L70E) controllers.

Select the last slave station address to priority poll. 0

Select the first slave station address to priority poll. Entering 255 disables priority polling.

Select the last slave station address to normal poll. 0

Select the first slave station address to normal poll. Entering 255 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 range before returning to the priority poll range. If no stations 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 masterinitiated message) before polling the slave station for a reply. 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. 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 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.

255

MESSAGE BASED (ALLOW SLABES TO INITIATE MESSAGES)

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 63

Page 64

Chapter 5 Communication Connections

Configure Modbus RTU

1. Open your Connected Components Workbench project. On the device configuration tree, go to the Controller properties. Click Serial Port.

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

Parameter Options Default

Baud Rate 1200, 2400, 4800, 9600, 19200, 38400 19200 Parity None, Odd, Even None Modbus Role Master, Slave, Auto Master

64 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 65

Chapter 5 Communication Connections

4. Click Advanced Settings to set advanced parameters. See the table for available options and default configuration for advanced parameters.

Modbus RTU Advanced Parameters

Parameter Options Default

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

1. Open your Connected Components Workbench project. On the device configuration tree, go to Controller properties. Click Serial Port.

2. Select ASCII on the Driver field.

3. Specify baud rate and parity.

ASCII Parameters

Parameter Options Default

Baud Rate 1200, 2400, 4800, 9600, 19200, 38400 19200 Parity None, Odd, Even None

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 65

Page 66

Chapter 5 Communication Connections

4. Click Advanced Settings to configure advanced parameters.

ASCII Advanced Parameters

Parameters Options Default

Full Duplex

Control Line

Deletion Mode

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

Half-duplex with continuous carrier Half-duplex without continuous carrier No Handshake

CRT Ignore Printer

No Handshake

Ignore

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

66 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 67

Chapter 5 Communication Connections

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 AutoNegotiate 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

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 67

Page 68

Chapter 5 Communication Connections

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: 2080-LC50-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 configuration tree,

go to the Controller properties. Click Serial Port.

2. Select CIP Serial from the Driver field.

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 FactoryTalk Linx

Support for Open Platform Communications (OPC) using CIP symbolic has 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.

68 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 69

Chapter 6

Micro870 Controller Distributed Network Protocol

Overview This chapter describes how to configure the DNP3 communication settings. Topics include:

Top ic Pa ge

Channel Configuration for DNP3 Slave 69 DNP3 Slave Application Layer 92 DNP3 Objects and Controller Variables 96 DNP3 Device Attribute Object 106 Event Reporting 108 Collision Avoidance 112 Time Synchronization 113 Diagnostics 114 Function Codes 116 Implementation Table 117

Channel Configuration for DNP3 Slave

The default communication protocol for the serial ports is DF1 Full-Duplex. To 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.

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 69

Page 70

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.

70 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 71

Chapter 6 Micro870 Controller Distributed Network Protocol

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.

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 71

Page 72

Chapter 6 Micro870 Controller Distributed Network Protocol

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.

72 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 73

Chapter 6 Micro870 Controller Distributed Network Protocol

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

Valid selections are Enabled (Checked) and Disabled (Unchecked). Default value is Disabled (Unchecked).

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).

• Vend 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

The valid range is 0…65519. Default value is 0.

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 HalfDuplex without continuous carrier (CTS/RTS). If the controller is connected to an RS-485 network, you must select No Handshake.

Request LL Confirmation

Valid selections are Enabled (Checked) and Disabled (Unchecked). Default value is Disabled (Unchecked).

When the selection is Disabled (Unchecked), Primary Frames from the controller are sent out with the function code FC_UNCONFIRMED_USER_DATA (4).

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 73

Page 74

Chapter 6 Micro870 Controller Distributed Network Protocol

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

Valid selections are Enabled (Checked) and Disabled (Unchecked). Default value is Disabled (Unchecked).

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

Confirmation Timeout (x1 ms)

When Request LL Confirmation is enabled, the controller waits to receive a confirmation frame until this timeout has expired.

when the DNP3 Master sends confirmed user data. This function is not supported when the DNP3 Master sends unconfirmed user data.

The valid range is 1…65535. Default value is 20.

Message Retries

When Confirmation Timeout (x1 ms) has expired and this parameter was non-zero value, the controller tries to send retry packets.

The valid range is 0…255. Default value is 0.

Pre-transmit Delay (x1 ms)

The controller waits for the specified time before sending the packet.

The valid range is 0…65535. Default value is 0.

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.

The valid range is 0…65535. Default value is 0.

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.

The valid range is 0…65535. Default value is 0.

74 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 75

Chapter 6 Micro870 Controller Distributed Network Protocol

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 112.

The valid range is 0…65535. Default value is 0.

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 configuration.

for each

Table 6 - End Point Types

End Point Type Connection Description

Any of the requests are accepted and the responses

A single TCP server connection

Listening End Point

UDP datagram

A single TCP server connection

Dual End Point

A single TCP client connection

UDP datagram

Datagram End Point UDP datagram only

are transmitted via this connection. The unsolicited responses are transmitted via this connection when this connection is available.

Accepts only broadcast packets when DNP3 destination node is one of 0xFFFD, 0xFFFE and 0xFFFF in the request.

Any of the requests are accepted and the responses are transmitted via this connection. The unsolicited responses are transmitted via this connection when this connection is available. This connection has higher priority than the Client connection.

Any of the requests are accepted and the responses are transmitted via this connection. The unsolicited responses are transmitted via this 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 destination node is one of 0xFFFD, 0xFFFE and 0xFFFF in the request.

Any of the requests are accepted and the responses are transmitted via this connection. All responses can be transmitted to the different DNP3 Master port according to the configuration of the parameters Remote UDP Port Number and Master 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.

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 75

Page 76

Chapter 6 Micro870 Controller Distributed Network Protocol

DNP3 over IP Enable

The valid selections are Enabled (Checked) and Disabled (Unchecked). Default value is Disabled (Unchecked).

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

The 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 Node Address which is configured in the parameters Master Node0 and Master Node1, Master Node2, Master Node3, Master Node4 on page 73. The maximum number of Master Node Address for the Master Address Validation is 5.

on page 73,

Enable Self-Address

The valid selections are Enabled (Checked) and Disabled (Unchecked). Default value is Disabled (Unchecked).

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

The 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 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.

76 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 77

Chapter 6 Micro870 Controller Distributed Network Protocol

Master Node0

This value is used to:

• Validate 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 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).

The valid range is 0…65519. Default value is 0.

Master IP Address0

This value is used to:

• Validate Master IP address when the Enable Access Control 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 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.

The valid range is 0…65535. Default value is 20000.

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 77

Page 78

Chapter 6 Micro870 Controller Distributed Network Protocol

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.

The valid range is 0…65535. Default value is 20000.

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.

The valid range is 0…65535. Default value is 20000.

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.

The valid range is 1…65535. Default value is 10.

Slave Node Address

This value is a node address of this DNP3 Slave.

The valid range is 0…65519. Default value is 1.

Local Port Number (UDP)

This value is used to configure Local UDP Port Number which is used for UDP socket listening.

The valid range is 0…65535. Default value is 20000.

78 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 79

Chapter 6 Micro870 Controller Distributed Network Protocol

Local Port Number (TCP)

This value is used to configure Local TCP Port Number which is used for TCP socket listening.

The valid range is 0…65535. Default value is 20000.

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

Valid selections are Enabled (Checked) and Disabled (Unchecked). Default value is Disabled (Unchecked).

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

Valid selections are Enabled (Checked) and Disabled (Unchecked). Default value is Disabled (Unchecked).

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.

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 79

Page 80

Chapter 6 Micro870 Controller Distributed Network Protocol

Unsolicited Responses For Class2

Valid selections are Enabled (Checked) and Disabled (Unchecked). Default value is Disabled (Unchecked).

When the selection is Disabled (Unchecked), Unsolicited Response is disabled for Class 2 events. To prevent overflowing of the event buffer, DNP3 Master should poll for Class 2 events.

When the selection is Enabled (Checked), Unsolicited Response is enabled for Class 2 events.

Enable Unsolicited For Class3

Valid selections are Enabled (Checked) and Disabled (Unchecked). Default value is Disabled (Unchecked).

When the selection is Disabled (Unchecked), Unsolicited Response is disabled for Class 3 events. To prevent overflowing of the event buffer, DNP3 Master should poll for Class 3 events.

When the selection is Enabled (Checked), Unsolicited Response is enabled for Class 3 events.

Send Initial Unsolicited Null Response On Start Up

Valid selections are Enabled (Checked) and Disabled (Unchecked). Default value is Disabled (Unchecked).

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 96 for more information.

Enable Confirmation

Valid selections are Enabled (Checked) and Disabled (Unchecked). Default value is Disabled (Unchecked).

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.

80 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 81

Chapter 6 Micro870 Controller Distributed Network Protocol

Enable Time Synchronization

Valid selections are Enabled (Checked) and Disabled (Unchecked). Default value is Disabled (Unchecked).

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.

The valid range is 0…65535. Default value is 0.

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.

The valid range is 0…10000. Default value is 10. See DNP3 10K Event Logging

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 81

on page 110 for more information.

Page 82

Chapter 6 Micro870 Controller Distributed Network Protocol

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 valid range is 0…65535. Default value is 5.

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.

Number of Class2 Events

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.

If the controller is configured to generate Unsolicited Responses, and the number of queued Class 2 events reaches this value, an Unsolicited Response is initiated.

The valid range is 0…10000. Default value is 10. See DNP3 10K Event Logging

on page 110 for more information

Hold Time after Class2 Events (x 1s)

This parameter is only for a Class 2 Unsolicited Response. The controller holds the events during Hold Time after Class2 Events (x 1s) before initiating an Unsolicited Response.

The valid range is 0…65535. Default value is 5.

The value of 0 indicates that responses are not delayed due to this parameter.

The Parameters Number of Class2 Events and Hold Time after Class2 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.

Number of Class3 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.

If the controller is configured to generate Unsolicited Responses, and the number of queued Class 3 events reaches this value, an Unsolicited Response is initiated.

The valid range is 0…10000. Default value is 10. See DNP3 10K Event Logging

82 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

on page 110 for more information.

Page 83

Chapter 6 Micro870 Controller Distributed Network Protocol

Hold Time after Class3 Events (x 1s)

This parameter is only for a Class 3 Unsolicited Response. The controller holds the events during Hold Time after Class3 Events (x 1s) before initiating an Unsolicited Response.

The valid range is 0…65535. Default value is 5.

The value of 0 indicates that responses are not delayed due to this parameter.

The parameters Number of Class3 Events and Hold Time after Class3 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.

Select Timeout (x 1s)

The valid range is 1…65535. Default value is 10.

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 96 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.

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 83

Page 84

Chapter 6 Micro870 Controller Distributed Network Protocol

Enable Secure Authentication

The valid selections are Enabled (Checked) and Disabled (Unchecked). Default value is Disabled (Unchecked).

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

The valid selections are Enabled (Checked) and Disabled (Unchecked). Default value is Disabled (Unchecked).

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 3 (0x04) critical 23 (0x17) non-critical 4 (0x04) critical 24 (0x18) critical 5 (0x05) critical 25 (0x19) non-critical

84 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 85

Chapter 6 Micro870 Controller Distributed Network Protocol

Function Codes (Continued)

Function Code Critical FCs Function Code Critical FCs

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 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.

The valid range is 1…10000. Default value is 1000.

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.

The valid range is 0…10. Default value is 2.

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.

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 85

Page 86

Chapter 6 Micro870 Controller Distributed Network Protocol

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.

86 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 87

Chapter 6 Micro870 Controller Distributed Network Protocol

Symmetric Key

Public Key

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.

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.

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 87

Page 88

Chapter 6 Micro870 Controller Distributed Network Protocol

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.

88 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 89

Chapter 6 Micro870 Controller Distributed Network Protocol

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

1 Binary Input Static Object 1 - Packed format

2 Binary Input Change Object 3 - With relative time

3 Double Bit Binary Input Static Object 1 - Packed format

4 Double Bit Binary Input Change Object 3 - With relative time

10 Binary Output Static Object 2 - Output status with flag

11 Binary Output Change Object 2 - Status with time

13 Binary Output Command 2 - Command status with time

16-bit Counter Static Object 6 - 16-bit without flag

32-bit Counter Static Object 5 - 32-bit without flag

Frozen 16-bit Counter Static Object 10 - 16-bit without flag

Frozen 32-bit Counter Static Object 9 - 32-bit without flag

0 - All variation 2 - With flag

0 - All variation 1 - Without time 2 - With absolute time

0 - All variation 2 - With flag

0 - All variation 1 - Without time 2 - With absolute time

0 - All variation 1 - Packed format

0 - All variation 1 - Status without time

0 - All variation 1 - Command status without time

0 - All variation 1 - 32-bit with flag 2 - 16-bit with flag 5 - 32-bit without flag

0 - All variation 1 - 32-bit with flag 2 - 16-bit with flag 6 - 16-bit without flag

0 - All variation 1 - 32-bit with flag 2 - 16-bit with flag 5 - 32-bit with flag and time 6 - 16-bit with flag and time 9 - 32-bit without flag

0 - All variation 1 - 32-bit with flag 2 - 16-bit with flag 5 - 32-bit with flag and time 6 - 16-bit with flag and time 10 - 16-bit without flag

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 89

Page 90

Chapter 6 Micro870 Controller Distributed Network Protocol

Table 7 - DNP3 Default Variation Configuration File (Continued)

Group Default Variation for the following Objects Standard Default Variation Alternate Default Variations

0 - All variation

16-bit Counter Change Object 2 - 16-bit with flag

32-bit Counter Change Object 1 - 32-bit with flag

Frozen 16-bit Counter Change Object 2 - 16-bit with flag

Frozen 32-bit Counter Change Object 1 - 32-bit with flag

16-bit Analog Input Static Object 4 - 16-bit without flag

32-bit Analog Input Static Object 3 - 32-bit without flag

Short Float Analog Input 5 - Single-precision, floating-point with flag

16-bit Analog Input Change Object 2 - 16-bit without time

32-bit Analog Input Change Object 1 - 32-bit without time

Short Float Analog Input Change Object 5 - Single-precision, floating-point without time

1 - 32-bit with flag 5 - 32-bit with flag and time 6 - 16-bit with flag and time

0 - All variation 2 - 16-bit with flag 5 - 32-bit with flag and time 6 - 16-bit with flag and time

0 - All variation 1 - 32-bit with flag 5 - 32-bit with flag and time 6 - 16-bit with flag and time

0 - All variation 2 - 16-bit with flag 5 - 32-bit with flag and time 6 - 16-bit with flag and time

0 - All variation 1 - 32-bit with flag 2 - 16-bit with flag 3 - 32-bit without flag 5 - Single-precision, floating-point with flag 6 - Double-precision, floating-point with flag

0 - All variation 1 - 32-bit with flag 2 - 16-bit with flag 4 - 16-bit without flag 5 - Single-precision, floating-point with flag 6 - Double-precision, floating-point with flag

0 - All variation 1 - 32-bit with flag 2 - 16-bit with flag 3 - 32-bit without flag 4 - 16-bit without flag 6 - Double-precision, floating-point with flag

0 - All variation 1 - 32-bit without time 3 - 32-bit with time 4 - 16-bit with 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 2 - 16-bit without time 3 - 32-bit with time 4 - 16-bit with 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 1 - 32-bit without time 2 - 16-bit without time 3 - 32-bit with time 4 - 16-bit with time 6 - Double-precision, floating-point without time 7 - Single-precision, floating-point with time 8 - Double-precision, floating-point with time

90 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 91

Chapter 6 Micro870 Controller Distributed Network Protocol

Table 7 - DNP3 Default Variation Configuration File (Continued)

Group Default Variation for the following Objects Standard Default Variation Alternate Default Variations

0 - All variation 1 - 32-bit without time 3 - 32-bit with time

Frozen 16-bit Analog Input Change Object 2 - 16-bit without time

Frozen 32-bit Analog Input Change Object 1 - 32-bit without time

Frozen Short Float Analog Input Change Object 5 - Single-precision, floating-point without time

16-bit Analog Input Reporting Dead Band 1 - 16-bit

32-bit Analog Input Reporting Dead Band 2 - 32-bit

Short Float Analog Input Reporting Dead Band 3 - Single-precision, floating-point

16-bit Analog Output Static Object 2 - 16-bit with flag

32-bit Analog Output Static Object 1 - 32-bit with flag

Short Float Analog Output Status 3 - Single-precision, floating-point with flag

16-bit Analog Output Change Object 2 - 16-bit without time

32-bit Analog Output Change Object 1 - 32-bit without time

Short Float Analog Output Change Object 5 - Single-precision, floating-point without time

4 - 16-bit with 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 2 - 32-bit 3 - Single-precision, floating-point

0 - All variation 1 - 16-bit 3 - Single-precision, floating-point

0 - All variation 1 - 16-bit 2 - 32-bit

0 - All variation 1 - 32-bit with flag 3 - Single-precision, floating-point with flag 4 - Double-precision, floating-point with flag

0 - All variation 2 - 16-bit with flag 3 - Single-precision, floating-point with flag 4 - Double-precision, floating-point with flag

0 - All variation 1 - 32-bit with flag 2 - 16-bit with flag 4 - Double-precision, floating-point with flag

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 91

Page 92

Chapter 6 Micro870 Controller Distributed Network Protocol

Table 7 - DNP3 Default Variation Configuration File (Continued)

Group Default Variation for the following Objects Standard Default Variation Alternate Default Variations

0 - All variation 1 - 32-bit without time 3 - 32-bit with time

16-bit Analog Output Command Change Object 2 - 16-bit without time

32-bit Analog Output Command Change Object 1 - 32-bit without time

Short Float Analog Output Command Change Object 5 - Single-precision, floating-point without time

DNP3 Slave Application Layer

This section covers DNP3 Slave Application Layer Function Codes and Internal Indications. All of the Function Codes that are supported in the controller are summarized in Function Codes

for DNP3 in Micro870 Controllers on page 116.

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.

92 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 93

Chapter 6 Micro870 Controller Distributed Network Protocol

OPERATE (FC Byte = 0x04)

04 – Operate See SELECT (FC Byte = 0x03)

on page 92.

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) issued from a DNP3 master.

. No response message is returned when this request is

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) issued from a DNP3 master.

. No response message is returned when this request is

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.

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 93

Page 94

Chapter 6 Micro870 Controller Distributed Network Protocol

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 Connected Components Workbench software.

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.

94 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 95

Chapter 6 Micro870 Controller Distributed Network Protocol

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.

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 95

Page 96

Chapter 6 Micro870 Controller Distributed Network Protocol

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.

• IIN1.2: CLASS_2_EVENTS. This bit is set when Class 2 event data is available.

• IIN1.3: CLASS_3_EVENTS. This bit is set when Class 3 event data is 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 Variables

All of the DNP3 Objects that are supported in the controller are summarized in Implementation

Table for Micro870 controllers on page 117.

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

96 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 97

Chapter 6 Micro870 Controller Distributed Network Protocol

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 Output Object 256

Counter Object 20, 22 256

Frozen Counter Object 21, 23

Analog Input Object 30, 32 256

Analog Output Object 40, 41 256

BCD Object 101 256 Small BCD Object 256

Data-Set Object

85, 87, 88 86, 87, 88 Data-Set Descriptors Object

Reflection of Counter Object which was configured

16-bit Counter Object 32 bit Counter Object Reflection of 16-bit Counter Object Reflection of 32-bit Counter Object 16-bit Analog Input Object

Short Floating Point Analog Input Object 16-bit Analog Output Object

Short Floating Point Analog Output Object

Data-Set Prototypes Object

256

25632-bit Analog Input Object

25632-bit Analog Output Object

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 97

Page 98

Chapter 6 Micro870 Controller Distributed Network Protocol

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.

98 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Page 99

Chapter 6 Micro870 Controller Distributed Network Protocol

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

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 99

Page 100

Chapter 6 Micro870 Controller Distributed Network Protocol

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.

100 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022

Allen-Bradley 2080-LC70-24QWB Owners Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

About This Publication Use this manual if you are responsible for designing, installing, programming, or

Preface

Conformal Coated Catalogs Catalog numbers with the suffix ‘K’ are conformal coated and their specifications are the same

Download Firmware, AOP, EDS, and Other Files

Summary of Changes This publication contains the following new or updated information. This list includes

Additional Resources

Hardware Features Micro830, Micro850, and Micro870 controllers are economical brick style controllers with

Micro830 Controllers

Micro850 Controllers

Micro870 Controllers

Programming Cables

Embedded Serial Port Cables

Embedded Ethernet Support

Programming Software for Micro800 Controllers

Obtain Connected Components Workbench Software

Use Connected Components Workbench Software

Controller Changes in Run Mode

Using Run Mode Change (RMC)

Uncommitted Changes

RMC Memory

Limitations of RMC

Using Run Mode Configuration Change (RMCC)

Using Modbus RTU Communication

Using EtherNet/IP Communication

Safety Considerations Safety considerations are an important element of proper system installation. Actively

Disconnect Main Power

Safety Circuits

Power Distribution

Periodic Tests of Master Control Relay Circuit

Power Considerations The following explains power considerations for the micro controllers.

Isolation Transformers

Power Supply Inrush

Loss of Power Source

Input States on Power Down

Other Types of Line Conditions

Preventing Excessive Heat For most applications, normal convective cooling keeps the controller within the specified

Master Control Relay A hard-wired master control relay (MCR) provides a reliable means for emergency machine

Using Emergency-Stop Switches

Controller Mounting Dimensions

Mounting Dimensions

DIN Rail Mounting

Panel Mounting

Panel Mounting Dimensions

System Assembly

Wiring Requirements and Recommendation

Use Surge Suppressors Because of the potentially high current surges that occur when switching inductive load

Recommended Surge Suppressors

Grounding the Controller This product is intended to be mounted to a well grounded mounting surface such as a metal

Wiring Diagrams The following illustrations show the wiring diagrams for the Micro800 controllers. Controllers

Controller I/O Wiring This section contains some relevant information about minimizing electrical noise and also

Minimize Electrical Noise

Analog Channel Wiring Guidelines

Minimize Electrical Noise on Analog Channels

Grounding Your Analog Cable

Wiring Examples

Embedded Serial Port Wiring

Overview This chapter describes how to communicate with your control system and configure

Supported Communication Protocols

Modbus RTU

CIP Serial Client/Server – DF1

ASCII

Modbus TCP Client/Server

CIP Symbolic Client/Server

CIP Client Messaging

Sockets Client/Server TCP/UDP

CIP Communications Pass-thru

Examples of Supported Architectures

Use Modems with Micro800 Controllers

Making a DF1 Point-to-Point Connection

Construct Your Own Modem Cable

Configure Serial Port You can configure the serial port driver as CIP Serial, Modbus RTU, ASCII, or Shutdown through

Configure CIP Serial Driver

Configure Modbus RTU

Configure ASCII

Configure Ethernet Settings 1. Open your Connected Components Workbench project (for example, Micro850). On the

Validate IP Address