Professional Documents
Culture Documents
Modicon M580: Hardware Reference Manual
Modicon M580: Hardware Reference Manual
EIO0000001578 10/2019
Modicon M580
Hardware
Reference Manual
Original instructions
10/2019
EIO0000001578.10
www.schneider-electric.com
The information provided in this documentation contains general descriptions and/or technical
characteristics of the performance of the products contained herein. This documentation is not
intended as a substitute for and is not to be used for determining suitability or reliability of these
products for specific user applications. It is the duty of any such user or integrator to perform the
appropriate and complete risk analysis, evaluation and testing of the products with respect to the
relevant specific application or use thereof. Neither Schneider Electric nor any of its affiliates or
subsidiaries shall be responsible or liable for misuse of the information contained herein. If you
have any suggestions for improvements or amendments or have found errors in this publication,
please notify us.
You agree not to reproduce, other than for your own personal, noncommercial use, all or part of
this document on any medium whatsoever without permission of Schneider Electric, given in
writing. You also agree not to establish any hypertext links to this document or its content.
Schneider Electric does not grant any right or license for the personal and noncommercial use of
the document or its content, except for a non-exclusive license to consult it on an "as is" basis, at
your own risk. All other rights are reserved.
All pertinent state, regional, and local safety regulations must be observed when installing and
using this product. For reasons of safety and to help ensure compliance with documented system
data, only the manufacturer should perform repairs to components.
When devices are used for applications with technical safety requirements, the relevant
instructions must be followed.
Failure to use Schneider Electric software or approved software with our hardware products may
result in injury, harm, or improper operating results.
Failure to observe this information can result in injury or equipment damage.
© 2019 Schneider Electric. All rights reserved.
2 EIO0000001578 10/2019
Table of Contents
Safety Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
About the Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Part I Modicon M580 CPUs . . . . . . . . . . . . . . . . . . . . . . . . 17
Chapter 1 M580 CPUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.1 Functional Characteristics of M580 CPUs . . . . . . . . . . . . . . . . . . . . . . 20
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Performance Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Standards and Certifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
States for M580 CPUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Hot Standby System States. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Electrical Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Real-Time Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Addressing Field Buses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
1.2 BMEP58xxxx CPU Physical Characteristics . . . . . . . . . . . . . . . . . . . . 42
Physical Description of M580 Standalone CPUs. . . . . . . . . . . . . . . . . 43
Physical Description of M580 Hot Standby CPUs . . . . . . . . . . . . . . . . 45
LED Diagnostics for M580 Standalone CPUs . . . . . . . . . . . . . . . . . . . 49
LED Diagnostics for M580 Hot Standby CPUs . . . . . . . . . . . . . . . . . . 52
USB Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Ethernet Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
SD Memory Card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Memory Card Access LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Data Storage Elementary Functions . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Firmware Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Part II Installing and Diagnosing Modules on the Local Rack 69
Chapter 2 Installing Modules in an M580 Rack . . . . . . . . . . . . . . . . 71
Module Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Installing the CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Installing an SD Memory Card in a CPU . . . . . . . . . . . . . . . . . . . . . . . 78
Chapter 3 M580 Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Blocking Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Non-blocking Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
CPU or System Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
CPU Application Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
EIO0000001578 10/2019 3
Chapter 4 Processor Performance . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Execution of Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
MAST Task Cycle Time: Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . 92
MAST Task Cycle Time: Program Processing. . . . . . . . . . . . . . . . . . . 93
MAST Task Cycle Time: Internal Processing on Input and Output . . . 94
MAST Task Cycle Time Calculation. . . . . . . . . . . . . . . . . . . . . . . . . . . 97
FAST Task Cycle Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Event Response Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Part III Configuring the CPU in Control Expert. . . . . . . . . . . 101
Chapter 5 M580 CPU Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 103
5.1 Control Expert Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Creating a Project in Control Expert. . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Helping Secure a Project in Control Expert . . . . . . . . . . . . . . . . . . . . . 107
Configuring the Size and Location of Inputs and Outputs . . . . . . . . . . 108
Project Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
DIO Scanner Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
5.2 Configuring the CPU with Control Expert. . . . . . . . . . . . . . . . . . . . . . . 118
Control Expert Configuration Tabs. . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
About Control Expert Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Security Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
IPConfig Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
RSTP Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
SNMP Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
NTP Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Switch Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
QoS Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Service Port Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Advanced Settings Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Safety Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
5.3 Configuring the M580 CPU with DTMs in Control Expert . . . . . . . . . . 139
About DTM Configuration in Control Expert. . . . . . . . . . . . . . . . . . . . . 140
Accessing Channel Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Configuring DHCP and FDR Address Servers. . . . . . . . . . . . . . . . . . . 143
5.4 Diagnostics through the Control Expert DTM Browser . . . . . . . . . . . . 146
Introducing Diagnostics in the Control Expert DTM . . . . . . . . . . . . . . . 147
Bandwidth Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
RSTP Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Network Time Service Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
4 EIO0000001578 10/2019
Local Slave / Connection Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . 155
Local Slave or Connection I/O Value Diagnostics . . . . . . . . . . . . . . . . 158
Logging DTM Events to a Control Expert Logging Screen . . . . . . . . . 159
Logging DTM and Module Events to the SYSLOG Server . . . . . . . . . 160
5.5 Online Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Online Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
EtherNet/IP Objects Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Service Port Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Pinging a Network Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
5.6 Diagnostics Available through Modbus/TCP . . . . . . . . . . . . . . . . . . . . 168
Modbus Diagnostic Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
5.7 Diagnostics Available through EtherNet/IP CIP Objects . . . . . . . . . . . 171
About CIP Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Identity Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Assembly Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Connection Manager Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Modbus Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Quality Of Service (QoS) Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
TCP/IP Interface Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Ethernet Link Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
EtherNet/IP Interface Diagnostics Object . . . . . . . . . . . . . . . . . . . . . . 189
EtherNet/IP IO Scanner Diagnostics Object . . . . . . . . . . . . . . . . . . . . 192
IO Connection Diagnostics Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
EtherNet/IP Explicit Connection Diagnostics Object . . . . . . . . . . . . . . 198
EtherNet/IP Explicit Connection Diagnostics List Object . . . . . . . . . . . 200
RSTP Diagnostics Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Service Port Control Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
5.8 DTM Device Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Device List Configuration and Connection Summary . . . . . . . . . . . . . 209
Device List Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Standalone DDT Data Structure for M580 CPUs . . . . . . . . . . . . . . . . 216
Hot Standby DDT Data Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
5.9 Explicit Messaging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Configuring Explicit Messaging Using DATA_EXCH . . . . . . . . . . . . . . 233
Configuring the DATA_EXCH Management Parameter . . . . . . . . . . . 235
Explicit Messaging Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Configuring EtherNet/IP Explicit Messaging Using DATA_EXCH . . . . 238
EtherNet/IP Explicit Message Example: Get_Attribute_Single . . . . . . 240
EIO0000001578 10/2019 5
EtherNet/IP Explicit Message Example: Read Modbus Object . . . . . . 243
EtherNet/IP Explicit Message Example: Write Modbus Object . . . . . . 247
Modbus TCP Explicit Messaging Function Codes . . . . . . . . . . . . . . . . 251
Configuring Modbus TCP Explicit Messaging Using DATA_EXCH . . . 252
Modbus TCP Explicit Message Example: Read Register Request . . . 254
Sending Explicit Messages to EtherNet/IP Devices. . . . . . . . . . . . . . . 257
Sending Explicit Messages to Modbus Devices. . . . . . . . . . . . . . . . . . 259
5.10 Explicit Messaging Using the MBP_MSTR Block in Quantum RIO
Drops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Configuring Explicit Messaging Using MBP_MSTR . . . . . . . . . . . . . . . 262
EtherNet/IP Explicit Messaging Services . . . . . . . . . . . . . . . . . . . . . . . 264
Configuring the CONTROL and DATABUF Parameters . . . . . . . . . . . 266
MBP_MSTR Example: Get_Attributes_Single . . . . . . . . . . . . . . . . . . . 269
Modbus TCP Explicit Messaging Function Codes . . . . . . . . . . . . . . . . 274
Configuring the Control Parameter for Modbus TCP Explicit Messaging 275
5.11 Implicit Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
Setting Up Your Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Adding an STB NIC 2212 Device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
Configuring STB NIC 2212 Properties . . . . . . . . . . . . . . . . . . . . . . . . . 288
Configuring EtherNet/IP Connections . . . . . . . . . . . . . . . . . . . . . . . . . 290
Configuring I/O Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
EtherNet/IP Implicit Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
5.12 Configuring the M580 CPU as an EtherNet/IP Adapter . . . . . . . . . . . . 309
Introducing the Local Slave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
Local Slave Configuration Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
Enabling Local Slaves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Accessing Local Slaves with a Scanner. . . . . . . . . . . . . . . . . . . . . . . . 314
Local Slave Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
Working with Device DDTs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
5.13 Hardware Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Introduction to the Hardware Catalog . . . . . . . . . . . . . . . . . . . . . . . . . 321
Adding a DTM to the Control Expert Hardware Catalog . . . . . . . . . . . 322
Adding an EDS File to the Hardware Catalog . . . . . . . . . . . . . . . . . . . 323
Removing an EDS File from the Hardware Catalog. . . . . . . . . . . . . . . 326
Export / Import EDS Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
6 EIO0000001578 10/2019
5.14 M580 CPU Embedded Web Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Introducing the Standalone Embedded Web Pages . . . . . . . . . . . . . . 331
Status Summary (Standalone CPUs) . . . . . . . . . . . . . . . . . . . . . . . . . 332
Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
Port Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
I/O Scanner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
NTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Alarm Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Rack Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
5.15 M580 Hot Standby CPU Web Pages. . . . . . . . . . . . . . . . . . . . . . . . . . 349
Introducing the M580 Hot Standby CPU Web Pages . . . . . . . . . . . . . 350
Status Summary (Hot Standby CPUs) . . . . . . . . . . . . . . . . . . . . . . . . 352
HSBY Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
Rack Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
Chapter 6 M580 CPU Programming and Operating Modes . . . . . . 361
6.1 I/O and Task Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
I/O Exchanges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
CPU Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
6.2 BMEP58xxxx CPU Memory Structure . . . . . . . . . . . . . . . . . . . . . . . . . 367
Memory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
6.3 BMEP58xxxx CPU Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . 368
Managing Run/Stop Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
Power Cut and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
Cold Start. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Warm Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
Appendices ......................................... 377
Appendix A Function Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
ETH_PORT_CTRL: Executing a Security Command in an Application. 379
Glossary ......................................... 383
Index ......................................... 391
EIO0000001578 10/2019 7
8 EIO0000001578 10/2019
Safety Information
Important Information
NOTICE
Read these instructions carefully, and look at the equipment to become familiar with the device
before trying to install, operate, service, or maintain it. The following special messages may appear
throughout this documentation or on the equipment to warn of potential hazards or to call attention
to information that clarifies or simplifies a procedure.
EIO0000001578 10/2019 9
PLEASE NOTE
Electrical equipment should be installed, operated, serviced, and maintained only by qualified
personnel. No responsibility is assumed by Schneider Electric for any consequences arising out of
the use of this material.
A qualified person is one who has skills and knowledge related to the construction and operation
of electrical equipment and its installation, and has received safety training to recognize and avoid
the hazards involved.
WARNING
UNGUARDED EQUIPMENT
Do not use this software and related automation equipment on equipment which does not have
point-of-operation protection.
Do not reach into machinery during operation.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
This automation equipment and related software is used to control a variety of industrial processes.
The type or model of automation equipment suitable for each application will vary depending on
factors such as the control function required, degree of protection required, production methods,
unusual conditions, government regulations, etc. In some applications, more than one processor
may be required, as when backup redundancy is needed.
Only you, the user, machine builder or system integrator can be aware of all the conditions and
factors present during setup, operation, and maintenance of the machine and, therefore, can
determine the automation equipment and the related safeties and interlocks which can be properly
used. When selecting automation and control equipment and related software for a particular
application, you should refer to the applicable local and national standards and regulations. The
National Safety Council's Accident Prevention Manual (nationally recognized in the United States
of America) also provides much useful information.
In some applications, such as packaging machinery, additional operator protection such as point-
of-operation guarding must be provided. This is necessary if the operator's hands and other parts
of the body are free to enter the pinch points or other hazardous areas and serious injury can occur.
Software products alone cannot protect an operator from injury. For this reason the software
cannot be substituted for or take the place of point-of-operation protection.
Ensure that appropriate safeties and mechanical/electrical interlocks related to point-of-operation
protection have been installed and are operational before placing the equipment into service. All
interlocks and safeties related to point-of-operation protection must be coordinated with the related
automation equipment and software programming.
10 EIO0000001578 10/2019
NOTE: Coordination of safeties and mechanical/electrical interlocks for point-of-operation
protection is outside the scope of the Function Block Library, System User Guide, or other
implementation referenced in this documentation.
WARNING
EQUIPMENT OPERATION HAZARD
Verify that all installation and set up procedures have been completed.
Before operational tests are performed, remove all blocks or other temporary holding means
used for shipment from all component devices.
Remove tools, meters, and debris from equipment.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
Follow all start-up tests recommended in the equipment documentation. Store all equipment
documentation for future references.
Software testing must be done in both simulated and real environments.
Verify that the completed system is free from all short circuits and temporary grounds that are not
installed according to local regulations (according to the National Electrical Code in the U.S.A, for
instance). If high-potential voltage testing is necessary, follow recommendations in equipment
documentation to prevent accidental equipment damage.
Before energizing equipment:
Remove tools, meters, and debris from equipment.
Close the equipment enclosure door.
Remove all temporary grounds from incoming power lines.
Perform all start-up tests recommended by the manufacturer.
EIO0000001578 10/2019 11
OPERATION AND ADJUSTMENTS
The following precautions are from the NEMA Standards Publication ICS 7.1-1995 (English
version prevails):
Regardless of the care exercised in the design and manufacture of equipment or in the selection
and ratings of components, there are hazards that can be encountered if such equipment is
improperly operated.
It is sometimes possible to misadjust the equipment and thus produce unsatisfactory or unsafe
operation. Always use the manufacturer’s instructions as a guide for functional adjustments.
Personnel who have access to these adjustments should be familiar with the equipment
manufacturer’s instructions and the machinery used with the electrical equipment.
Only those operational adjustments actually required by the operator should be accessible to
the operator. Access to other controls should be restricted to prevent unauthorized changes in
operating characteristics.
12 EIO0000001578 10/2019
About the Book
At a Glance
Document Scope
PlantStruxure is a Schneider Electric program designed to address the key challenges of many
different types of users, including plant managers, operations managers, engineers, maintenance
teams, and operators, by delivering a system that is scalable, flexible, integrated, and
collaborative.
This document provides detailed information about the M580 programmable automation
controller (PAC). These topics are also discussed:
Install a local rack in the M580 system.
Configure the M580 CPU.
The CPU performs Ethernet I/O scanning of both RIO and DIO logic without affecting network
determinism.
Validity Note
This document is valid for EcoStruxure™ Control Expert 14.1 or later and BMEP58•••• firmware
version 2.10 or later.
The technical characteristics of the devices described in the present document also appear online.
To access the information online:
Step Action
1 Go to the Schneider Electric home page www.schneider-electric.com.
2 In the Search box type the reference of a product or the name of a product range.
Do not include blank spaces in the reference or product range.
To get information on grouping similar modules, use asterisks (*).
3 If you entered a reference, go to the Product Datasheets search results and click on the
reference that interests you.
If you entered the name of a product range, go to the Product Ranges search results and click
on the product range that interests you.
4 If more than one reference appears in the Products search results, click on the reference that
interests you.
5 Depending on the size of your screen, you may need to scroll down to see the datasheet.
6 To save or print a datasheet as a .pdf file, click Download XXX product datasheet.
The characteristics that are presented in the present document should be the same as those
characteristics that appear online. In line with our policy of constant improvement, we may revise
content over time to improve clarity and accuracy. If you see a difference between the document
and online information, use the online information as your reference.
EIO0000001578 10/2019 13
Related Documents
14 EIO0000001578 10/2019
Title of Documentation Reference Number
M580 BMENOS0300, Network Option Switch, Installation and NHA89117 (English),
Configuration Guide NHA89119 (French),
NHA89120 (German),
NHA89121 (Italian),
NHA89122 (Spanish),
NHA89123 (Chinese)
Modicon eX80, BMEAHI0812 HART Analog Input Module & EAV16400 (English),
BMEAHO0412 HART Analog Output Module, User Guide EAV28404 (French),
EAV28384 (German),
EAV28413 (Italian),
EAV28360 (Spanish),
EAV28417 (Chinese)
Unity Loader, User Manual 33003805 (English),
33003806 (French),
33003807 (German),
33003809 (Italian),
33003808 (Spanish),
33003810 (Chinese)
EcoStruxure™ Control Expert, Operating Modes 33003101 (English),
33003102 (French),
33003103 (German),
33003104 (Spanish),
33003696 (Italian),
33003697 (Chinese)
EcoStruxure™ Control Expert, Program Languages and Structure, 35006144 (English),
Reference Manual 35006145 (French),
35006146 (German),
35013361 (Italian),
35006147 (Spanish),
35013362 (Chinese)
Modicon X80 Racks and Power Supplies, Hardware, Reference EIO0000002626 (English),
Manual EIO0000002627 (French),
EIO0000002628 (German),
EIO0000002630 (Italian),
EIO0000002629 (Spanish),
EIO0000002631 (Chinese)
Modicon Controllers Platform Cyber Security, Reference Manual EIO0000001999 (English),
EIO0000002001 (French),
EIO0000002000 (German),
EIO0000002002 (Italian),
EIO0000002003 (Spanish),
EIO0000002004 (Chinese)
EIO0000001578 10/2019 15
You can download these technical publications and other technical information from our website
at https://www.schneider-electric.com/en/download
16 EIO0000001578 10/2019
Modicon M580
M580 CPUs
EIO0000001578 10/2019
Part I
Modicon M580 CPUs
EIO0000001578 10/2019 17
M580 CPUs
18 EIO0000001578 10/2019
Modicon M580
CPUs
EIO0000001578 10/2019
Chapter 1
M580 CPUs
M580 CPUs
Introduction
This chapter introduces you to the physical and functional characteristics of the M580 CPUs.
EIO0000001578 10/2019 19
CPUs
Section 1.1
Functional Characteristics of M580 CPUs
Introduction
This section describes the functional characteristics of the M580 CPUs. Performance, electrical
characteristics, and memory capacities of the different CPU modules are detailed.
20 EIO0000001578 10/2019
CPUs
Introduction
Modules may reside in the local rack with the CPU or they may be installed in remote drops at a
distance from the local rack. The CPU has built-in capabilities to act as the RIO processor that
manages communications between the CPU and the Quantum and X80 EIO adapter modules that
are installed in each remote drop.
Devices can be connected to the PAC network as either DIO clouds or DIO sub-rings.
For detailed information about the various architectures that the M580 network supports, refer to
the Modicon M580 System Planning Guide (see Modicon M580 Standalone, System Planning
Guide for, Frequently Used Architectures). For a detailed description of the X80 EIO adapter
modules and the options they provide for installing a remote drop, refer to the Modicon M580,
Remote I/O Modules Installation and Configuration Guide (see Modicon M580, RIO Modules,
Installation and Configuration Guide).
Functional Considerations
The CPU solves control logic for the I/O modules and distributed equipment in the system. Choose
a CPU based on several operating characteristics:
memory size
processing power: the number of I/O points or channels that it can manage (see page 23)
the speed at which the CPU can execute the control logic (see page 31)
communication capabilities: the types of Ethernet ports on the CPU (see page 58)
the number of local I/O modules and RIO drops that it can support (see page 23)
the ability to function in harsh environments: (3 CPU modules are hardened to operate over
extended temperature ranges and in dirty or corrosive environments
network configuration (standalone or Hot Standby)
EIO0000001578 10/2019 21
CPUs
CPU modules ending with “S” are safety modules. Refer to the Modicon M580 Safety System
Planning Guide (see Modicon M580, Safety System Planning Guide) for a description of safety
CPUs.
NOTE: For detailed information about M580 Hot Standby configurations, refer to the Modicon
M580 Hot Standby System Planning Guide for Frequently Used Architectures (see Modicon M580
Standalone, System Planning Guide for, Frequently Used Architectures).
22 EIO0000001578 10/2019
CPUs
Performance Characteristics
Introduction
All M580 CPUs have an embedded DIO scanner service to manage distributed equipment on the
M580 device network. Some M580 CPUs also have an embedded RIO scanner service to manage
RIO drops.
To manage RIO drops on the device network, select one of these CPUs with Ethernet I/O scanner
service (both RIO and DIO scanner service):
BMEP582040, BMEP582040H
BMEP583040
BMEP584040
BMEP585040, BMEP585040C
BMEP586040, BMEP586040C
BMEH582040, BMEH582040C
BMEH584040, BMEH584040C
BMEH586040, BMEH586040C
Embedded Ethernet I/O scanner services are configured via CPU IP configuration (see page 125).
NOTE: Some of this information applies to M580 Hot Standby configurations. For more
information, refer to the Modicon M580 Hot Standby System Planning Guide for Frequently Used
Architectures (see Modicon M580 Standalone, System Planning Guide for, Frequently Used
Architectures).
CPU Characteristics
These tables show the key characteristics of the M580 standalone and Hot Standby CPUs. These
characteristics represent the maximum values that a specific CPU can manage in the M580
system.
NOTE:
The values in these tables may not be achieved depending on the I/O density and the number
of available rack slots.
The following tables do not include safety CPUs. Refer to the Modicon M580 Safety System
Planning Guide (see Modicon M580, Safety System Planning Guide) for the performance
characteristics of safety CPUs.
EIO0000001578 10/2019 23
CPUs
Standalone CPUs:
H (hardened)
C (coated version)
1. Only three of these modules can be BMENOC0301/BMENOC0311 modules. All other are BMX Ethernet modules.
2. Supports BM•CRA312•0 adapter modules.
3. Supports BM•CRA312•0 and 140CRA31200 adapter modules.
4. Of these connections: 3 are reserved for local slaves; the remainder are available for scanning distributed
equipment.
24 EIO0000001578 10/2019
CPUs
NOTE: The number of available channels could differ from the maximum values shown because
the values depend on the CPU reference and the other modules in the same drop. More
information is given in Modicon X80 I/O Modules (see Modicon M580, RIO Modules, Installation
and Configuration Guide).
To configure Quantum RIO drops, refer to the Quantum EIO installation and configuration guide
(see Quantum EIO, Remote I/O Modules, Installation and Configuration Guide).
EIO0000001578 10/2019 25
CPUs
Program and Data Memory (Hot Standby). This table shows the program and data memory
capacity for M580 Hot Standby CPUs:
Memory Areas (Standalone). This table shows the maximum memory size per area for M580
standalone CPUs:
program (KB) 4096 8162 8162 12288 12288 16384 16384 24576 65536(2)
1. 10 KB are reserved for the system
2. The sum of saved data, unsaved data, and program data is limited to 65536 KB.
26 EIO0000001578 10/2019
CPUs
Memory Areas (Hot Standby). This table shows the maximum memory size per area for M580 Hot
Standby CPUs:
2. The sum of saved data, unsaved data, and program data is limited to 65536 KB.
NOTE: Versions 2.30 and later of M580 processor firmware provide a maximum of 64 K words of
memory for State RAM. By contrast, firmware versions 2.20 and earlier seem to provide a
maximum of 128 K words; however, the display is incorrect. As a result, if you upgrade CPU
firmware from version 2.20 or earlier to version 2.30 or later for an existing project, the percentage
of State RAM used by the application will appear to have doubled. In some cases, the percentage
of State RAM used can exceed 100% and the application cannot be re-built. To re-build your
application in this case, you will need to perform one or both of the following edits:
Increase the amount of State RAM (the total of %M, %MW, %I, %IW), if possible.
Re-define some located variables as unlocated (by removing the assigned address), until the
total amount of State RAM used (the sum of %M, %MW, %I, %IW) no longer exceeds 100%.
Located Data (Standalone). This table shows the maximum and default size of located data (in KB)
for each M580 standalone CPU:
EIO0000001578 10/2019 27
CPUs
Located Data (Hot Standby). This table shows the maximum and default size of located data (in
KB) for each M580 Hot Standby CPU:
The size limit of unlocated data is the global maximum memory size for data (see page 26) minus
the size consumed by located data.
28 EIO0000001578 10/2019
CPUs
Overall Maximum
Requests per Request From USB Maximum requests sent to Maximum requests sent to
CPU FIFO Size IP address of the CPU IP address of comm.
Scan(1)
modules
BMXP581020 8 (16) 32 4 8 16
BMX•5820•0 16 (24) 32 4 12 16
BMXP5830•0 24 (32) 32 4 16 16
BMX•5840•0 32 (40) 50 4 24 16
BMEP5850•0 40 (48) 50 4 32 16
BME•5860•0 56 (64)(2) 50 4 32 16
1. This column shows the default limits for the number of requests served per cycle. The limit can be modified through
%SW90, between 2 and the number indicated between brackets.
2. The overall limit for the BME•5860•0 CPU is higher than the sum of the limits for the USB, CPU, and NOC modules.
This is a provision for future evolutions.
The MAST task cycle time may increase by up to 0.5 ms per incoming request. When the
communications load is high, you can limit the potential jitter of the MAST time by limiting the
number of requests that are processed per cycle in %SW90.
EIO0000001578 10/2019 29
CPUs
Example: This example local rack assembly includes a BMEP584040 CPU and two
BMENOC0301/11 Ethernet communication modules. Therefore, the maximum values in this
example apply to the BMEP584040 CPU (described above):
Number of Connections: This table shows the maximum number of simultaneous Modbus TCP,
EtherNet/IP, and UMAS connections for the embedded Ethernet port on these CPUs:
CPU Connections
BMXP581020 32
BMX•5820•0 32
BMXP5830•0 48
BMX•5840•0 64
BMEP5850•0 64
BME•5860•0 80
When an incoming connection request is accepted, the open connection that has been idle for the
longest time is closed.
30 EIO0000001578 10/2019
CPUs
Modbus TCP and EtherNet/IP Client: This table shows the maximum number (per cycle) of
communication EFs that support Modbus TCP and EtherNet/IP clients according to the selected
CPU:
EIO0000001578 10/2019 31
CPUs
Download
Click the link that corresponds to your preferred language to download standards and certifications
(PDF format) that apply to the modules in this product line:
Title Languages
Modicon M580, M340, and X80 I/O Platforms, English: EIO0000002726
Standards and Certifications French: EIO0000002727
German: EIO0000002728
Italian: EIO0000002730
Spanish: EIO0000002729
Chinese: EIO0000002731
32 EIO0000001578 10/2019
CPUs
Introduction
This topic describes the operating states for M580 standalone and Hot Standby CPUs.
EIO0000001578 10/2019 33
CPUs
Standby: The standby PAC maintains a state of readiness. It can take control of system
processes and devices if the primary PAC cannot continue to perform these functions:
It reads the data and the I/O states from the primary PAC.
It does not scan distributed equipment, but receives this information from the primary PAC.
It executes program logic. You can configure the standby PAC to execute:
- The first section of program logic (the default setting); or
- Specified sections of program logic, including all MAST and FAST task sections.
NOTE: You can specify if a section is to be executed in the Condition tab the Properties
dialog for each section.
On each scan, it checks the status of the primary PAC.
NOTE: When a PAC is in Standby mode, both the module health status (MOD_HEALTH) and
the channels health status (CH_HEALTH) of safety I/O modules are set to FALSE in the
Standby PAC DDDT. In this case, you can diagnose the health of safety I/O modules by
monitoring their status in the Primary PAC DDDT.
34 EIO0000001578 10/2019
CPUs
Wait: The PAC is in RUN mode, but cannot act as either primary or standby. The PAC
transitions from the wait state to either the primary or standby state, when all preconditions for
that state exist, including:
The state of the Hot Standby link.
The state of the Ethernet RIO link.
The presence of at least one connection with an Ethernet RIO drop.
The position of the A/B rotary selection switch on the rear of the CPU.
The state of the configuration. For example:
- If a firmware mismatch exists, the FW_MISMATCH_ALLOWED flag is set.
- If a logic mismatch exists, the LOGIC_MISMATCH_ALLOWED flag is set.
In the wait state, the PAC continues to communicate with other modules on the local rack, and
can execute program logic, if configured to do so. You can configure a PAC in wait state to
execute:
Specific sections of program logic in a non-safety PAC (or process program logic in a safety
PAC), specified in the Condition tab of the Properties dialog for each section.
The first section of program logic in a non-safety PAC (or the first section of process program
logic in a safety PAC).
No program logic for a non-safety PAC (or no process program logic for a safety PAC).
INIT: Both the PAC and the Hot Standby system are initializing.
STOP: The PAC is in STOP mode. On the STOP to RUN transition, the PAC may move to the
wait, standby, or primary state. This transition depends on the state of the Ethernet RIO and Hot
Standby links, and on the position of the A/B rotary selection switch on the rear of the CPU.
NOTE: In addition to the PAC operating states listed here, other operating states that are not
related to the Hot Standby system (see page 33) exist.
EIO0000001578 10/2019 35
CPUs
36 EIO0000001578 10/2019
CPUs
Electrical Characteristics
Introduction
The power supply module provides current to the modules installed on the local rack, including the
CPU. The CPU current consumption contributes to the total rack consumption.
EIO0000001578 10/2019 37
CPUs
Real-Time Clock
Introduction
Your CPU has a real-time clock that:
provides the current date and time
displays the date and time of the last application shut-down
Clock Accuracy
The resolution of the real-time clock is 1 ms. The clock accuracy is affected by the operating
temperature of the application:
Operating Temperature Maximum Daily Drift (Seconds/Day) Maximum Yearly Drift (Minutes/Year)
25 °C (77 °F) stabilized +/- 2.6 +/- 17.4
0...60 °C (32...140 °F) +/- 5.2 +/-33.1
Clock Back-Up
The accuracy of the real-time clock is maintained for 4 weeks when the CPU power is turned off if
the temperature is below 45 °C (113 °F). If the temperature is higher, the back-up time is shorter.
The real-time clock back-up does not need any maintenance.
If the back-up power is too low, system bit %S51 is set to 1. This value indicates a loss of time when
the power supply was OFF.
38 EIO0000001578 10/2019
CPUs
To read the current date and time, read system words %SW49 through %SW53. This operation sets
system bit %S50 to 0.
To write the current date and time, write system words %SW50 through %SW53. This operation sets
system bit %S50 to 1.
When system bit %S59 is set to 1, you can increment or decrement the current date and time values
with system word %SW59.
The function performed by each bit in word %SW59 is:
Bit Function
0 increments the day of the week
1 increments the seconds
2 increments the minutes
3 increments the hours
4 increments the days
5 increments the months
6 increments the years
7 increments the centuries
8 decrements the day of the week
9 decrements the seconds
10 decrements the minutes
11 decrements the hours
12 decrements the days
13 decrements the months
14 decrements the years
15 decrements the centuries
NOTE: The preceeding functions are performed when system bit %S59 is set to 1.
EIO0000001578 10/2019 39
CPUs
The reason for the last application shutdown can be displayed by reading the least significant byte
of system word %SW58, which can have these values (in BCD):
40 EIO0000001578 10/2019
CPUs
or
a Modicon STB island with an STBNIP2311 EtherNet/IP network interface modue
and an STBAHI8321 HART interface module.
Modbus TCP, Modbus TCP devices are connected to the Ethernet DIO network.
EtherNet/IP
Modbus Plus Modbus Plus is supported using a gateway module like TCSEGDB23F24FA or
TCSEGDB23F24FK.
PROFIBUS-DP A PROFIBUS remote master is connected to the Ethernet DIO network. The process
variables are exchanged via the DIO scanner service in the CPU.
PROFIBUS gateway modules: TCSEGPA23F14F or TCSEGPA23F14FK
PROFIBUS-PA A PROFIBUS remote master and a DP/PA interface are connected to an Ethernet
DIO network. The process variables are exchanged via the DIO scanner service in
the CPU.
PROFIBUS gateway modules: TCSEGPA23F14F or TCSEGPA23F14FK
EIO0000001578 10/2019 41
CPUs
Section 1.2
BMEP58xxxx CPU Physical Characteristics
Introduction
This section describes the physical elements that are displayed on the front panel of the M580
CPUs. The various communication ports, LED diagnostic information, and several options
available for industrial hardening and memory back-up are detailed.
42 EIO0000001578 10/2019
CPUs
Dimensions
This graphic shows the front and side dimensions of the M580 standalone CPUs:
NOTE:
Consider the height of the CPU when you are planning the installation of the local rack. The CPU
extends below the lower edge of the rack by:
29.49 mm (1.161 in.) for an Ethernet rack
30.9 mm (1.217 in.) for an X Bus rack
Front Panel
M580 standalone CPUs have similar front panels. Depending on the standalone CPU you choose,
these differences apply:
BMEP58•020: The embedded Ethernet I/O scanner service supports DIO only.
BMEP58•040: The embedded Ethernet I/O scanner service supports both RIO and DIO.
EIO0000001578 10/2019 43
CPUs
Physical features:
Legend:
4 Service RJ45 Ethernet connector (see page 58) for the service port
5 Device Network BMEP58•020: dual RJ45 Ethernet connectors (see page 58) that
6 support distributed equipment only
BMEP58•040: dual RJ45 Ethernet connectors (see page 58) that
support distributed equipment and RIO drops
7 — SD memory card (see page 62) slot
8 — This green LED indicates the status of the memory card:
ON: The CPU can access the SD memory card.
blinking: The CPU does not recognize the SD memory card.
flashing: The CPU attempts to access the SD memory card.
44 EIO0000001578 10/2019
CPUs
NOTE: The only visible difference between safety and non-safety CPUs is that safety CPUs are
colored red.
EIO0000001578 10/2019 45
CPUs
Use only the small, plastic screwdriver provided with the CPU to set the rotary switch according to
its role in a Hot Standby system.
NOTICE
RISK OF UNINTENDED OPERATION
Use only the small, plastic screwdriver that ships with the module to change the rotary switch
position. Using a metal screwdriver can damage the switch, rendering it inoperable.
Failure to follow these instructions can result in equipment damage.
Position Result
A Designates the PAC as PAC A (see Modicon M580 Hot Standby, System Planning Guide
for, Frequently Used Architectures), as referenced in Control Expert and the
T_M_ECPU_HSBY (see page 225) DDDT.
Assigns the PAC IP address A on Ethernet RIO network.
B Designates the PAC as PAC B (see Modicon M580 Hot Standby, System Planning Guide
for, Frequently Used Architectures), as referenced in Control Expert and the
T_M_ECPU_HSBY DDDT.
Assigns the PAC IP address B on Ethernet RIO network.
Clear Clears the application in the PAC, and places the PAC into the NO_CONF operational state.
If an SD memory card is inserted in the PAC, the application in the card is also cleared,
NOTE: Setting the switch for each Hot Standby PAC to the same A/B position can cause a
a conflict of PAC roles (see Modicon M580 Hot Standby, System Planning Guide for,
Frequently Used Architectures).
46 EIO0000001578 10/2019
CPUs
Step Action
1 Set the rotary switch to [Clear].
2 Power up the PAC.
3 Power down the PAC.
4 Set the rotary switch to [A] or [B].
When you next power up the PAC, if the remote PAC is primary, the primary PAC transfers the
application to the local PAC.
SFP Socket
Each CPU module includes one SFP socket, to which you can connect either a fiber optic or a
copper transceiver:
To insert a transceiver:
Step Action
1 Check that the CPU is powered off.
2 Position the transceiver so that its label is oriented to the left.
3 Press the SFP transceiver firmly into the socket until you feel it snap into place.
NOTE: If the SFP transceiver resists, check the orientation of the transceiver and repeat these
steps.
To remove a transceiver:
Step Action
1 Check that the CPU is powered off.
2 Pull out the latch to unlock the transceiver.
3 Pull on the transceiver to remove it.
EIO0000001578 10/2019 47
CPUs
NOTICE
POTENTIAL EQUIPMENT DAMAGE
Do not Hot Swap the SFP transceiver. Insert or remove the transceiver only when there is no
power to the CPU.
Failure to follow these instructions can result in equipment damage.
NOTE: For part numbers and other information regarding the available transceivers, refer to the
description of CPU Hot Standby link transceivers (see Modicon M580 Hot Standby, System
Planning Guide for, Frequently Used Architectures).
Each module comes with a stopper. When the SFP socket is not connected to a transceiver, cover
the unused socket with the cover to keep out dust
Grounding Considerations
Follow all local and national safety codes and standards.
DANGER
HAZARD OF ELECTRIC SHOCK
If you cannot prove that the end of a shielded cable is connected to the local ground, the cable
must be considered as dangerous and personal protective equipment (PPE) must be worn.
Failure to follow these instructions will result in death or serious injury.
48 EIO0000001578 10/2019
CPUs
LED Display
A 7-LED display is located on the front panel of the CPU:
LED Descriptions
BACKUP ON:
The memory card or CPU flash memory is missing or inoperable.
The memory card is not usable (bad format (see page 62), unrecognized type).
The memory card or CPU flash memory content is inconsistent with the current
application.
The memory card has been removed and reinserted.
A PLC → Project Backup... → Backup Clear command has been performed when no
memory card is present. The BACKUP LED remains ON until the project is
successfully backed up.
OFF: The memory card or CPU flash memory content is valid, and the application in the
execution memory is identical.
ETH MS MOD STATUS (green/red): Pattern indicates the Ethernet port configuration status.
NOTE: With the detection of a recoverable error, the ETH MS LED can be green or red
and on or off.
ETH NS NET STATUS (green/red): Pattern indicates the Ethernet connection status.
EIO0000001578 10/2019 49
CPUs
NOTICE
UNINTENDED EQUIPMENT BEHAVIOR
Confirm that each module has a unique IP address. Duplicate IP addresses can cause
unpredictable module/network behavior.
Do not assign an IP address equal to the Main IP Address, the Main IP Address + 1,
IP Address A, or IP Address B to any Ethernet device that potentially communicates with the
Hot Standby system. A duplicate IP address condition, causing unintended equipment operation,
can occur.
Failure to follow these instructions can result in equipment damage.
The LEDs provide detailed diagnostic information when you observe their pattern in combination:
50 EIO0000001578 10/2019
CPUs
unrecoverable –
detected error
power off –
–: any pattern
EIO0000001578 10/2019 51
CPUs
LED Panel
The front face of a BMEH58•040 Hot Standby CPU presents the following LED panel, which you
can use to diagnose the state of the M580 Hot Standby system:
NOTE: The SRUN and SMOD LEDs apply only to safety CPUs.
For a description of the safety PAC LEDs SRUN and SMOD, refer to the topic LED Displays for
the M580 Safety CPU and Copro (see Modicon M580, Safety System Planning Guide) in the
Modicon M580, Safety System Planning Guide.
For a presentation of LED diagnostics for safety CPUs, refer to the topic M580 Safety CPU LED
Diagnostics (see Modicon M580, Safety Manual) in the Modicon M580, Safety Manual.
52 EIO0000001578 10/2019
CPUs
Use the BMEH58•040 PPRIM, and STBY LEDs to identify the operational status of the local and
remote PAC:
EIO0000001578 10/2019 53
CPUs
Use this LED to diagnose the state of the Hot Standby link:
54 EIO0000001578 10/2019
CPUs
EIO0000001578 10/2019 55
CPUs
USB Port
Introduction
The USB port is a high-speed, mini-B USB connector, version 2.0 (480 Mbps) that can be used for
a Control Expert program or human-machine interface (HMI) panel. The USB port can connect to
another USB port, version 1.1 or later.
NOTE: Install M580 USB drivers before connecting the USB cable between the CPU and the PC.
Transparency
If your system requires transparency between the device connected to the USB port and the M580
device network, add a persistent static route in the device’s routing table.
Example of a command to address a device network with IP address X.X.0.0 (for a Windows
PC): route add X.X.0.0 mask 255.255.0.0 90.0.0.1 -p
(In this case, X.X.0.0 is the network address used by the M580 device network, and
255.255.0.0 is the corresponding subnet mask.)
Pin Assignments
The USB port has the following pin positions and pinouts:
Legend:
Pin Description
1 VBus
2 D-
3 D+
4 not connected
5 ground
shell chassis ground
56 EIO0000001578 10/2019
CPUs
Cables
Use a BMX XCA USB H018 (1.8 m/5.91 ft) or BMX XCA USB H045 (4.5 m/14.764 ft) cable to
connect the panel to the CPU. (These cables have a type A connector on one side and the mini-B
USB on the other side.)
In a fixed assembly with an XBT-type console connected to the CPU, connect the USB cable to a
protection bar (see Modicon X80, Racks and Power Supplies, Hardware Reference Manual). Use
the exposed part of the shield or the metal lug on the BMX XCA cable to make the connection.
EIO0000001578 10/2019 57
CPUs
Ethernet Ports
Introduction
There are three RJ45 Ethernet ports on the front of the CPU: one service port, and two device
network ports. The ports share the characteristics described below.
Common Characteristics
All three ports have the same RJ45 connector and all use the same type of Ethernet cables.
NOTE: The three Ethernet ports are connected to chassis ground, and the system requires an
equipotential ground (see Modicon X80, Racks and Power Supplies, Hardware Reference
Manual).
Dust Cover
To keep dust from entering the unused Ethernet ports, cover the unused ports with the stopper:
Ethernet Ports
Each RJ45 connector has a pair of LED indicators:
58 EIO0000001578 10/2019
CPUs
The pin positions, pinouts, and cable connections are the same on all three RJ45 Ethernet ports:
Pin Description
1 TD+ Pinout:
2 TD-
3 RD+
4 not connected
5 not connected
6 RD-
7 not connected
8 not connected
— shell/chassis ground
NOTE: The TD pins (pins 1 and 2) and the RD pins (pins 3 and 6) can be reversed to allow the
exclusive use of straight-through cables.
The ports have an auto MDIX capability that automatically detects the direction of the transmission.
Choose from these Ethernet cables to connect to the Ethernet ports:
TCSECN3M3M••••: Cat 5E Ethernet straight-through shielded cable, rated for industrial use,
CE- or UL-compliant
TCSECE3M3M••••: Cat 5E Ethernet straight-through shielded cable, rated for industrial use,
CE-compliant
TCSECU3M3M••••: Cat 5E Ethernet straight-through shielded cable, rated for industrial use,
UL-compliant
The maximum length for a copper cable is 100 m. For distances greater than 100 m, use fiber optic
cable. The CPU does not have any fiber ports on it. You may use dual ring switches (DRSs) or
BMX NRP •••• fiber converter modules (see Modicon M580 Standalone, System Planning Guide
for, Frequently Used Architectures) to handle the copper-fiber conversion.
EIO0000001578 10/2019 59
CPUs
Service Port
The service port is the uppermost of the three Ethernet ports on the front panel of the CPU. This
port can be used:
to provide an access point that other devices or systems can use to monitor or communicate
with the M580 CPU
as a standalone DIO port that can support a star, daisy chain, or mesh topology of distributed
equipment
to mirror the CPU ports for Ethernet diagnostics. The service tool that views activity on the
mirrored port may be a PC or an HMI device.
NOTE: Do not connect the service port to the device network, either directly or through a
switch/hub. The service port does not support the RSTP network protocol. Connecting the service
port to the device network can result in the creation of logical loops in the network, which can
adversely affect network performance.
NOTE: The service port does not support either VLANs or QoS tagging of Ethernet packets. The
service port is inherently non-deterministic.
CAUTION
RISK OF UNINTENDED OPERATION
Do not connect together the service ports of the Hot Standby CPUs. Connecting together the
service ports of the primary and standby CPUs can cause unintended system operation.
Failure to follow these instructions can result in injury or equipment damage.
60 EIO0000001578 10/2019
CPUs
You may use a Device Network port to support a star, daisy chain, or mesh topology of distributed
equipment. You may use both Device Network ports to support a ring topology.
For details about distributed equipment architectures, refer to the Modicon M580 Standalone
System Planning Guide for Frequently Used Architectures.
When a CPU supports RIO scanning, the two ports below the service port marked Device Network
are RIO ports. These CPUs support RIO scanning:
BMEP582040, BMEP582040H
BMEP583040
BMEP584040
BMEP585040, BMEP585040C
BMEP586040, BMEP586040C
BMEH582040, BMEH582040C
BMEH584040, BMEH584040C
BMEH586040, BMEH586040C
When used as RIO ports, both ports connect the CPU to the main ring in an Ethernet daisy-chain
loop or ring.
For more information about RIO architectures, refer to the Modicon M580 Hot Standby System
Planning Guide for Frequently Used Architectures (see Modicon M580 Standalone, System
Planning Guide for, Frequently Used Architectures).
Grounding Considerations
Follow all local and national safety codes and standards.
DANGER
HAZARD OF ELECTRIC SHOCK
If you cannot prove that the end of a shielded cable is connected to the local ground, the cable
must be considered as dangerous and personal protective equipment (PPE) must be worn.
Failure to follow these instructions will result in death or serious injury.
EIO0000001578 10/2019 61
CPUs
SD Memory Card
Characteristic Value
global memory size 4 GB
application backup size 200 MB
data storage size 3.8 GB
write/erase cycles (typical) 100,000
operating temperature range –40...+85 °C (–40...+185 °F)
file retention time 10 years
memory zone for FTP access data storage directory only
NOTE: Due to formatting, wearout, and other internal mechanisms, the actual available capacity
of the memory card is slightly lower than its global size.
62 EIO0000001578 10/2019
CPUs
Introduction
The green memory card access LED underneath the SD memory card door indicates the CPU
access to the memory card when a card is inserted. This LED can be seen when the door is open.
NOTE: Confirm that the LED is OFF before you remove the card from the slot.
Memory Card Status Conditions CPU State Memory Card BACKUP LED
Access LED
no memory card in — no configuration
the slot
EIO0000001578 10/2019 63
CPUs
Memory Card Status Conditions CPU State Memory Card BACKUP LED
Access LED
memory card with a An error is detected when no configuration during transfer: during transfer:
compatible project the project is restored from
the memory card to the CPU
RAM.
64 EIO0000001578 10/2019
CPUs
CPU
EF BMEP58•0•0 BMEH58•040 Description
EIO0000001578 10/2019 65
CPUs
CPU
EF BMEP58•0•0 BMEH58•040 Description
RD_FILE_TO_DATA X X The RD_FILE_TO_DATA function enables reading data
(see EcoStruxure™ from a file, at the current position in the file, and copies
Control Expert, the data to a direct address variable, a located variable,
System, Block or an unlocated variable.
Library)
SEEK_FILE X X The SEEK_FILE function sets the current byte offset in
(see EcoStruxure™ the file to a new specified offset position, which can be:
Control Expert, the offset, the current position plus the offset, the file
System, Block size plus the offset.
Library)
SET_FILE_ATTRIBUTES X — The SET_FILE_ATTRIBUTES function sets the read-
(see EcoStruxure™ only status of a file attribute. Read-only status can be
Control Expert, set or cleared. This function can be applies only to a file
System, Block that is already open via the CREATE_FILE or
Library) OPEN_FILE function.
WR_DATA_TO_FILE X — The WR_DATA_TO_FILE function enables the writing of
(see EcoStruxure™ the value of a direct address variable, a located
Control Expert, variable, or an unlocated variable to a file. The value is
System, Block written to the current position in the file. After the write,
Library) the current position in the file is updated.
X (supported)
— (not supported)
For additional information on each function, refer to the chapter Implementing File Management
(see EcoStruxure™ Control Expert, System, Block Library) in the EcoStruxure™ Control Expert,
System, Block Library.
66 EIO0000001578 10/2019
CPUs
Firmware Update
Introduction
You can update the CPU firmware by downloading a new firmware version with Unity Loader.
Download the firmware through a connection to one of these:
CPU mini-B USB connector (see page 56)
CPU Service port (see page 60)
Ethernet network
NOTE:
For a description of the download procedure, refer to the Unity Loader, User Manual.
When using an M580 Hot Standby configuration, refer to the Modicon M580 Hot Standby
System Planning Guide for Frequently Used Architectures (see Modicon M580 Standalone,
System Planning Guide for, Frequently Used Architectures).
Firmware File
Select the firmware file (*.ldx) that is compatible with your CPU.
Update Procedure
Interrupting the update procedure before it has completed can cause irreparable damage to the
CPU.
NOTICE
EQUIPMENT DAMAGE
During the transfer of the firmware file:
Do not power OFF the CPU.
Do not power OFF the PC.
Do not shut down Unity Loader.
Do not disconnect the communication cable.
Do not remove or insert the optional SD memory card.
EIO0000001578 10/2019 67
CPUs
Step Action
1 Install Unity Loader software.
2 Connect the PC that is running Unity Loader to the CPU.
3 Launch Unity Loader.
4 Click Firmware tab.
5 In the PC list box, select the .ldx file that contains the firmware file.
6 When connected with Ethernet, check that the MAC address indicated in the PLC box
corresponds to the MAC address marked on the CPU.
7 Check that transfer sign is green to allow transfer from PC to CPU.
8 Click Transfer.
9 Click Close.
68 EIO0000001578 10/2019
Modicon M580
Installation and Diagnostics
EIO0000001578 10/2019
Part II
Installing and Diagnosing Modules on the Local Rack
Introduction
This part provides instructions for installing and assembling M580 CPUs.
EIO0000001578 10/2019 69
Installation and Diagnostics
70 EIO0000001578 10/2019
Modicon M580
CPU Installation
EIO0000001578 10/2019
Chapter 2
Installing Modules in an M580 Rack
Overview
This chapter explains how to install a CPU module in an M580 rack.
EIO0000001578 10/2019 71
CPU Installation
Module Guidelines
Guidelines
NOTE: When your installation has more than one rack in the local rack or at a remote drop, the
BMX XBE 1000 rack exender module goes in the slot marked XBE of the X80 racks.
Check that the CPU is installed in the two slots marked 00 and 01 on the local rack before powering
up the system. If the CPU is not installed in these two slots, the CPU starts in NOCONF state
(see page 33) and uses the configured IP address (not the default IP address, which starts with
10.10 and uses the last two bytes of the MAC address).
72 EIO0000001578 10/2019
CPU Installation
MAC addresses: This table shows the availability of network services in terms of the relationship
between the CPU’s MAC addresses and its ports:
Rack Markings
Example of BMXXBP•••• (PV:02 or later) rack with slot markings:
EIO0000001578 10/2019 73
CPU Installation
Introduction
You can install any standard CPU (BMEP58•0•0) or any Hot Standby CPU (BMEH58•0•0) in these
racks:
BMXXBP•••• (PV:02 or later) X Bus rack
BMEXBP••00 or BMEXBP••02 Ethernet rack
Exception: You can install the BMXCPS4002 only on these dual-bus (Ethernet and X Bus) racks:
BMEXBP0602
BMEXBP1002
Installation Precautions
An M580 CPU is powered by the rack bus. Confirm that the rack power supply is turned off before
installing the CPU.
DANGER
HAZARD OF ELECTRIC SHOCK
Remove all power sources before installing the CPU.
Failure to follow these instructions will result in death or serious injury.
Remove the protective cover from the rack slot connectors before plugging the module in the rack.
WARNING
UNEXPECTED EQUIPMENT OPERATION
Check that the CPU does not contain an unsupported SD memory card before powering up the
CPU.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
NOTE: Check that the memory card slot door is closed after a memory card is inserted in the CPU,
and remains closed during operations.
NOTE: Refer to %SW97 to check the status of the SD card.
74 EIO0000001578 10/2019
CPU Installation
Grounding Considerations
Follow all local and national safety codes and standards.
DANGER
HAZARD OF ELECTRIC SHOCK
If you cannot prove that the end of a shielded cable is connected to the local ground, the cable
must be considered as dangerous and personal protective equipment (PPE) must be worn.
Failure to follow these instructions will result in death or serious injury.
NOTE: Refer to the ground protection information provided in the Electrical installation guide and
Control Panel Technical Guide, How to protect a machine from malfunctions due to
electromagnetic disturbance (see page 14).
EIO0000001578 10/2019 75
CPU Installation
76 EIO0000001578 10/2019
CPU Installation
DANGER
HAZARD OF ELECTRIC SHOCK
Connect the functional ground (FG) terminal of the power supply module directly to the
protective earth screw of the rack.
Do not chain the function ground (FG) terminals of redundant power supply modules together.
Do not connect anything else to the functional ground (FG) terminal of the power supply
module.
Failure to follow these instructions will result in death or serious injury.
DANGER
HAZARD OF ELECTRIC SHOCK
Use only cables with ring or spade lugs and check that there is a good ground connection.
Make sure that grounding hardware is tightened properly.
Failure to follow these instructions will result in death or serious injury.
Before you connect the two Hot Standby local racks, verify that an equipotential grounding system
(see Modicon X80, Racks and Power Supplies, Hardware Reference Manual) is in place that
includes the two racks (plus any other equipment you intend to connect to the two Hot Standby
local racks).
NOTICE
UNINTENDED EQUIPMENT OPERATION
When installing modules with fiber optic transceivers, do the following to help prevent dust and
pollution from disrupting light production into the fiber optic cable.
Keep caps on jumpers and transceivers when not in use.
Insert the optical cable into the transceivers carefully, respecting the longitudinal axis of the
transceiver.
Do not use force when inserting the cable into the optical transceivers.
Each Hot Standby CPU includes on its front face an SFP socket (see page 45). This socket can
accept an SFP transceiver module (see Modicon M580 Hot Standby, System Planning Guide for,
Frequently Used Architectures) for either copper or single mode fiber optic cabling of the Hot
Standby link. Your choice of SFP transceiver and cabling is determined by the distance between
the two Hot Standby local racks (see Modicon M580 Hot Standby, System Planning Guide for,
Frequently Used Architectures).
EIO0000001578 10/2019 77
CPU Installation
Introduction
The BME•58•••• CPUs support the use of the BMXRMS004GPF 4GB SD memory card.
Step Description
1 Open the SD memory card protective door.
2 Insert the card in its slot.
3 Push the memory card until you hear a click.
Result: The card should now be clipped into its slot.
Note: Insertion of the memory card does not force an application restore.
4 Close the memory card protective door.
78 EIO0000001578 10/2019
CPU Installation
Step Description
1 Generate a rising edge on bit %S65.
2 Check that the memory card access green LED is OFF.
3 Open the SD memory card protective door.
4 Push the memory card until you hear a click, then release the pressure on the card.
Result: The card should unclip from its slot.
5 Remove the card from its slot.
Note: The memory card access green LED is ON when the memory card is removed from the
CPU.
6 Close the memory card protective door.
EIO0000001578 10/2019 79
CPU Installation
80 EIO0000001578 10/2019
Modicon M580
Diagnostics
EIO0000001578 10/2019
Chapter 3
M580 Diagnostics
M580 Diagnostics
Introduction
This chapter provides information on diagnostics that can be performed via hardware indications
(based on LED status) and system bits or words when necessary. The entire M580 system
diagnostics is explained in the Modicon M580 System Planning Guide.
The CPU manages different types of detected error:
detected errors that can be recovered and do not change the PAC behavior unless specific
options are used
detected errors that cannot be recovered and lead the CPU to the halt state
CPU or system detected errors that lead the CPU to an error state
EIO0000001578 10/2019 81
Diagnostics
Blocking Conditions
Introduction
Blocking conditions caused during the execution of the application program do not cause system
errors, but they stop the CPU. The CPU goes into the HALT state (see page 33).
NOTE:
When a BMEH58•040 CPU is in the HALT state, the RIO and DIO outputs behave the same
way as they do when the CPU is in STOP state (see page 355).
For information about Hot Standby diagnostics, refer to the diagnostics chapter
(see Modicon M580 Hot Standby, System Planning Guide for, Frequently Used Architectures)
in the M580 Hot Standby installation guide.
Diagnostics
Visual indications of a blocking condition are the ERR LED on the CPU front panel (see page 49).
A description of the error is provided in system word %SW125.
The address of the instruction that was executing when the blocking condition occurred is provided
by system words %SW126 through %SW127.
%SW125 system word values and corresponding blocking condition description:
82 EIO0000001578 10/2019
Diagnostics
EIO0000001578 10/2019 83
Diagnostics
Non-blocking Conditions
Introduction
The system enters a non-blocking condition when it detects an input/output error on the backplane
bus (X Bus or Ethernet) or through execution of an instruction, which can be processed by the user
program and does not modify the CPU status.
system bits and words combined with the channel having an error detected (I/O channel number
and type of detected error) or I/O module Device DDT information (for modules configured in
Device DDT addressing mode):
bit %Ir.m.c.ERR set to 1: channel error detected (implicit exchanges)
word %MWr.m.c.2: the word value indicates the type of error detected on the specified
channel and depends on the I/O module (implicit exchanges)
NOTE: The CPU can be forced to the HALT state (see page 33) on program execution recoverable
condition.
There are 2 ways to force a CPU to stop when non-blocking errors linked to the execution of the
program are detected:
Use the diagnostic program function accessible through Control Expert programming software.
set the system bit %S78 (HALTIFERROR) to 1.
84 EIO0000001578 10/2019
Diagnostics
Introduction
CPU or system errors are related either to the CPU (equipment or software) or to the rack internal
bus wiring. The system can no longer operate correctly when these errors occur.
A CPU or system error causes the CPU to stop in ERROR mode and requires a cold restart. Before
applying a cold restart, set the CPU to STOP mode to keep the PAC from returning to ERROR
mode.
Diagnostics
A CPU or system error is diagnosed with the following indications:
CPU I/O LED pattern: steady on
system word %SW124 value defines the detected error source:
80 hex: system watchdog error or rack internal bus wiring error
81 hex: rack internal bus wiring error
90 hex: interruption not foreseen, or system task pile overrun
EIO0000001578 10/2019 85
Diagnostics
Application Compatibility
These tables show the standalone (BMEP58•0•0) and Hot Standby (BMEH58•0•0) CPUs that can
download and execute applications that are built on a different CPU.
These applications are built on standalone CPUs and transferred to standalone CPUs:
These applications are built on Hot Standby CPUs and transferred to Hot Standby CPUs:
Hot Standby CPUs Download and execute the application here (BMEH58...
Build the application 2040 4040 6040
here (↓).
BMEH582040 X X X
BMEP584040 – X X
BMEP586040 – – X
X yes
– no
86 EIO0000001578 10/2019
Modicon M580
Processor Performance
EIO0000001578 10/2019
Chapter 4
Processor Performance
Processor Performance
Introduction
This section describes BMEP58•0•0 processor performance.
EIO0000001578 10/2019 87
Processor Performance
Execution of Tasks
General
BME P58 •0•0 processors can execute single-task and multi-task applications. Unlike a single-task
application, which only executes master tasks, a multi-task application.defines the task execution
priorities.
Master Task
The master task represents the application program’s main task. You can choose from the
following MAST task execution modes:
Cyclical (default setup): Execution cycles are performed in sequence, one after the other.
Periodical: A new cycle is started periodically, according to a user-defined time period (1 -
255 ms).
If the execution time is longer than the period configured by the user, the bit %S19 is set to 1,
and a new cycle is launched.
The following illustration shows the cyclical execution of the MAST task:
The following illustration shows the periodical execution of the MAST task:
88 EIO0000001578 10/2019
Processor Performance
NOTE: Configuring the watchdog to a value that is less than the period is not allowed.
In periodical operating mode, an additional check detects when a period has been exceeded. The
PLC will not switch off if the period overrun remains less than the watchdog value.
Bit %S19 signals a period overrun. It is set to 1 by the system when the cycle time becomes longer
than the task period. Cyclical execution then replaces periodical execution.
The MAST task can be checked with the following system bits and system words:
Fast Task
The FAST task is for periodical processing and processing over short durations.
FAST task execution is periodical and must be quick so that no lower priority tasks overrun. The
FAST task period can be configured (1 - 255 ms). The FAST task execution principle is the same
as for periodical execution of the master task.
The FAST task can be checked with the following system bits and system words:
EIO0000001578 10/2019 89
Processor Performance
Event Tasks
With event processing, the application program’s reaction time can be reduced for events
originating from:
input/output modules (EVTi blocks)
events timers (TIMERi blocks)
Event processing execution is asynchronous. The occurrence of an event reroutes the application
program towards the process associated with the input/output channel, or to the event timer that
caused the event.
Event tasks can be checked with the following system bits and system words:
90 EIO0000001578 10/2019
Processor Performance
Multi-Task Execution
The following diagram shows the level of priority of the tasks in a multi-task structure:
EIO0000001578 10/2019 91
Processor Performance
General
The MAST task cycle time is the sum of the following:
internal processing time on input,
master task program processing time,
internal processing time on output.
Illustration
The following diagram defines the MAST task cycle time:
92 EIO0000001578 10/2019
Processor Performance
EIO0000001578 10/2019 93
Processor Performance
General
The internal processing time for inputs and outputs is the sum of the following:
MAST task system overhead time
maximum communication system reception time and input management time for implicit
inputs/outputs
maximum communication system transmission time and output management time for implicit
inputs/outputs
The table below shows the input (IN) and output (OUT) topological (T) and DDT (DDT)
management times for each module.
94 EIO0000001578 10/2019
Processor Performance
EIO0000001578 10/2019 95
Processor Performance
The MAST task cycle time is, therefore, affected by the communication traffic. The communication
time spent per cycle varies considerably, based on the following elements:
traffic generated by the processor: number of communication EFs active simultaneously
traffic generated by other devices to the processor, or for which the processor ensures the
routing function as master
This time is only spent in the cycles where there is a new message to be managed.
NOTE: These times may not all occur in the same cycle. Messages are sent in the same PLC cycle
as instruction execution when communication traffic is low. However, responses are never
received in the same cycle as instruction execution.
96 EIO0000001578 10/2019
Processor Performance
General
The MAST task cycle time can be calculated before the implementation phase, if the desired PLC
configuration is already known. The cycle time may also be determined during the implementation
phase, using the system words %SW30 - %SW32.
Calculation Method
The following table shows how to calculate the MAST task cycle time.
Step Action
1 Calculate the input and output internal processing time by adding the following
times:
MAST task system overhead time (see Modicon M340, Processors, Setup
Manual)
maximum communication system reception time and input management
time for implicit inputs/outputs (see Modicon M340, Processors, Setup
Manual)
maximum communication system transmission time and output
management time for implicit inputs/outputs (see Modicon M340,
Processors, Setup Manual)
2 Calculate the program processing time (see Modicon M340, Processors,
Setup Manual) according to the number of instructions and the type (Boolean,
digital) of program.
3 Add together the program processing time, and the input and output internal
processing time.
EIO0000001578 10/2019 97
Processor Performance
Definition
The FAST task cycle time is the sum of the following:
program processing time
internal processing time on input and output
98 EIO0000001578 10/2019
Processor Performance
General
The response time is the time between an edge on an event input and the corresponding edge on
an output positioned by the program in an event task.
Response Time
The following table gives the response time for the BMEP58•0•0 processors with an application
program of 100 Boolean instructions and the module.
EIO0000001578 10/2019 99
Processor Performance
Part III
Configuring the CPU in Control Expert
Introduction
This part describes how to configure a M580 system with Control Expert.
Chapter 5
M580 CPU Configuration
Introduction
The chapter describes the configuration of the M580 CPU.
Section 5.1
Control Expert Projects
Overview
Use this section to add an M580 CPU to your Control Expert application.
Introduction
If you have not created a project in Control Expert and installed a power supply and an M580 CPU,
use the following steps to create a new Control Expert project containing these components:
M580 CPU (see page 19)
power supply
Step Action
1 Open Control Expert.
2 Click File → New... to open the New Project window.
3 In the PLC window, expand the Modicon M580 node, and select a CPU.
NOTE: Refer to the CPU Scanner Service (see page 23) topic to select the appropriate CPU,
depending upon your DIO and RIO needs.
In the Rack window, expand the Modicon M580 local drop node, and select a rack.
4 Click OK.
Result: The Project Browser dialog opens.
5 Click File → Save to open the Save As dialog.
6 Enter a File name for your Control Expert project and click Save.
Result: Control Expert saves your project to the specified path location.
Step Action
1 Click Tools → Options to open the Options Management window.
2 In the left pane, navigate to Options → General → Paths.
3 In the right pane, type in a new path location for the Project path. You can also edit these items:
Import/Export file path
XVM path
Project settings templates path
Step Action
1 In the Project Browser, double-click PLC Bus to display a graphical representation of the
hardware rack:
The selected M580 CPU is in the second position.
A default power supply appears in the first position.
Control Expert automatically opens the Hardware Catalog that corresponds to the PLC bus
tab.
2 Select the power supply automatically added to the PLC bus.
3 Press the Delete key to remove the power supply.
4 Double-click the first slot of the PLC bus to open the New Device list.
5 Double-click the preferred power supply to make it appear in the PLC bus.
6 File → SaveClick to save your project.
More information about application password is given in Application Protection (see EcoStruxure™
Control Expert, Operating Modes) page.
NOTE: when Exporting a project to a .XEF or a .ZEF file, the application password is cleared.
Introduction
In the Control Expert Project Browser, double-click PLC Bus to display the main rack. Then click
on the CPU (but not on the Ethernet connectors) to open the CPU configuration window.
Step Action
1 Double-click the image of the M580 CPU in the PLC Bus to view its properties.
2 Select the Configuration tab.
3 In the Operating mode area, select the boxes to enable the following parameters in your application:
4 Run/Stop input Use these two parameters to place the PAC into Run or Stop mode. For more information
regarding the effect of these parameters, refer to the topic Managing Run/Stop Input
Run/Stop by
input only (see page 369). (default = de-selected)
Memory protect This function is activated by an input bit. It prohibits the transfer of a project into the PAC
and modifications in online mode, regardless of the communication channel. The Run
and Stop commands are authorized. (default = de-selected)
Automatic start in The enabling of this option automatically places the PAC into RUN mode in the event of
Run a cold start. (default = de-selected)
Initialize %MWi On a cold start (see page 372) or on download if you select the box (default state):
on cold start The %MWi are handled like other global variables (initialized to 0 or initial value,
according to current application) in all cold start cases.
On cold start or on download if you de-select the box:
If %MW were previously saved in internal flash memory (using the %SW96 word) they
are restored from internal flash memory,
If not:
If cold start is linked to a power-off or of a push on the reset button, the %MW are
initialized.
If not, the current values of %MW are maintained.
NOTE: if the new (or restored) application has more %MW than the previous one, the
added %MW are set to 0 (non-zero initial values are not applied)
Cold Start Only If selected, this option forces the cold start (see page 373)of the application, instead of
the normal warm start. By default, the Cold Start Only option is unchecked. An
application using this function is not:
Downloadable to a PAC with a previous version.
Executable on a PAC with a previous version.
Step Action
5 The option Support Quantum remote drops is only available for BMEP584040, BMEP585040,
BMEP586040, BMEH584040, and BMEH586040.
By default, this option is checked (allowing usage of Quantum remote drops) and the percentage of memory
usage is displayed (bar graph).
NOTE: The limitation of state ram depends on the Quantum memory structure.
When unchecked, adding Quantum drops in the configuration is not allowed. Also, unchecking this option is
not possible, if there is at least one Quantum drop in your configuration.
6 Configure the size of the memory locations in the Size of global address fields.
NOTE: High end standalone and Hot Standby CPUs (BMEP584040, BMEP585040, BMEP586040,
BMEH584040 and BMEH586040) include State RAM memory management for Quantum Ethernet RIO
drops. The State RAM feature supports LL984 logic sections for converted LL984 applications.
The following memory management options are presented in the Configuration tab:
Mem usage The percentage of CPU memory usage (bar graph), based on the cumulative values
input into the %M, %MW, %I, and %IW fields, below. (Supported only by high end
standalone and Hot Standby CPUs that support State RAM. For these CPUs, the option
Support Quantum remote drops has to be checked previously).
NOTE: Input values so that the percentage of CPU memory usage does not exceed
100%.
%M-0x Enter the appropriate value for each address field type. (%I and %IW are supported only
by high end standalone and Hot Standby CPUs that support State RAM.)
%MW-4x
%I-1x NOTE: The values for %IW and %MW, have to be divisible by 8 for version before 2.30
and divisible by 128 for other versions. The value for %KW have to be divisible by 8 for
%IW-3x all versions.
%KW
Viewer Opens the State RAM Viewer, which displays the allocation of used memory.
NOTE: To input:
Maximum values: Click the Maximum values button, select the appropriate boxes in the Max column, then
click OK.
Default values: Click the Default values button, select the appropriate boxes in the Default column, then
click OK.
NOTE: M580 / S908 applications:
In M580 CPUs that are compatible with Quantum S908 network adapter (see Modicon Quantum
140CRA31908, Adapter Module, Installation and Configuration Guide) and an OS version ≥ 02.30:
(number of %I + number of %M) ≤ 65535. The maximum number of %I is 65280. The maximum number of
%M is 65280.
7 Select the Online modification in RUN or STOP check box (in the Configuration Online Modification field) to
use the change configuration on the fly (CCOTF) feature.
8 Select Edit → Validate (or click the toolbar button) to save the configuration.
NOTE:
After you validate module settings for the first time, you cannot edit the module name. If you
subsequently decide to change the module name, delete the existing module from the
configuration, then add and rename a replacement module.
In addition to the Configuration tab, described above, the CPU configuration window presents
an I/O Objects tab, and an Animation tab with three sub-tabs: Task, Real-time Clock, and
Information.
Project Management
Method Connection
USB port If the CPU and the PC that are running Control Expert both have USB ports, you can
download the application to the CPU directly through the USB ports (see page 56)
(version 1.1 or later).
Ethernet port If the CPU and the PC that are running Control Expert both have Ethernet ports, you can
download the application to the CPU directly through the Ethernet ports.
communication You can download the application to the CPU by connecting Control Expert to the IP
module address of a communication module.
NOTE: For details, refer to Downloading CPU Applications (see Modicon M580 Standalone,
System Planning Guide for, Frequently Used Architectures) in the Modicon M580 Hot Standby
System Planning Guide for Frequently Used Architectures.
NOTE: If a memory card is inserted with a different application than the application in the CPU,
the application is transferred from the memory card to the CPU application RAM when the
restore function is carried out. If this is done unintentionally, the previous settings – including IP
address and FDR obtained settings – will be overwritten and lost.
Save the CPU project in the flash memory (and the memory card if inserted):
Automatically after an online modification is performed in the application RAM
Automatically after a download
Automatically on detection of %S66 system bit rising edge
Manually with a Control Expert command: PLC → Project Backup → Backup Save
NOTE: Backup begins after the completion of the current MAST cycle and before the start of
the next MAST cycle.
If MAST is configured as periodic, set the MAST period to a value larger than the actual MAST
execution time. This lets the processor complete an entire backup without interruption.
If the MAST period is set to a value less than the actual MAST execution time, backup
processing is fragmented and requires a longer time to finish.
Compare the CPU project and the flash memory project:
Manually with a Control Expert command: PLC → Project Backup → Backup Compare
NOTE: When a valid memory card is inserted (see page 62) with a valid application, the
application backup and restore operations are performed as follows:
The application backup is performed on the memory card first and then on the flash memory.
The application restore is performed from the memory card to the CPU application RAM first
and then copied from the application RAM to the flash memory.
Introduction
An embedded DIO scanner service in a standalone (BMEP58•0•0) or Hot Standby (BMEH58•0•0)
M580 CPU can manage distributed equipment. Through this service, Ethernet gateway devices
(like Profibus and CANopen masters) can operate as distributed equipment.
All DIO scanning communications occur over the Ethernet backplane or through an Ethernet port.
NOTE: The BMEP58•040 CPUs also manage RIO modules through the RIO scanner service, but
this discussion applies to the DIO scanner service.
1 A CPU on the main rack runs the Ethernet I/O communication server service.
2 A BMENOC0301/11 Ethernet communication module (Ethernet backplane connection disabled) manages
distributed equipment on the device network.
3 A BMENOC0301/11 Ethernet communication module (Ethernet backplane connection enabled) is
connected to a DIO cloud.
4 A BMENOS0300 network option switch module is connected to a DIO sub-ring.
Section 5.2
Configuring the CPU with Control Expert
Introduction
Use the instructions in this section to configure the M580 CPU in Control Expert.
NOTE: Some configuration features for the M580 CPU are accessed through the Control Expert
DTM Browser. Those configuration instructions appear elsewhere in this document
(see page 139).
NOTE: For improved security, some of the communication services (FTP, TFTP, and HTTP) are
disabled by default. You may wish to perform some actions (such as a firmware update, web
access, or remote I/O) that require the availability of one or more of these services. Before
configuring Ethernet parameters, set the security levels (see page 121) to meet your requirements.
When these services are not needed, you should disable them.
NOTE: To maintain RIO performance, you cannot access these tabs for BME•58•040 CPUs.
Step Action
1 Open Control Expert.
2 Open a Control Expert project that includes an M580 CPU in the configuration.
3 Open the Project Browser (Tools → Project Browser).
4 Double-click PLC bus in the Project Browser.
5 In the virtual rack, double-click the Ethernet ports of the M580 CPU to see these configuration
tabs:
Security
IPConfig
RSTP
SNMP
NTP
Switch (See note 1.)
QoS (See note 1.)
Service Port
Advanced Settings (See note 1.)
Safety (See note 2.)
These configuration tabs are described in detail in the pages that follow.
NOTE:
1. This tab is not available for CPUs that provide the RIO Ethernet scanning services.
2. This tab applies only to standalone M580 safety CPUs.
Security Tab
Introduction
Control Expert provides security services for the CPU. Enable and disable these services on the
Security tab in Control Expert.
Step Action
1 Open your Control Expert project.
2 Double-click the Ethernet ports on the CPU in the local rack (or right-click the Ethernet ports and
select Open Submodule.
3 Select the Security tab in the RIO DIO Communicator Head window to enable/disable Ethernet
services.
Field Comment
Enforce Security and Refer to the description, below, for details. (see page 122)
Unlock Security
FTP Enable or disable (default) firmware upgrade, SD memory card data
remote access, data storage remote access, and device configuration
management using the FDR service.
NOTE: Local data storage remains operational, but remote access to
data storage is disabled.
TFTP Enable or disable (default) the ability to read RIO drop configuration
and device configuration management using the FDR service.
NOTE: Enable this service to use eX80 Ethernet adapter modules.
HTTP Enable or disable (default) the web access service.
DHCP / BOOTP Enable or disable (default) the automatic assignment of IP addressing
settings. For DHCP, also enable/disable automatic assignment of
subnet mask, gateway IP address, and DNS server names.
SNMP Enable or disable (default) the protocol used to monitor the device.
EIP Enable or disable (default) access to the EtherNet/IP server.
Access Control Enable (default) or disable Ethernet access to the multiple servers in
the CPU from unauthorized network devices.
1
Set Access Control to Enabled to modify this field.
Field Comment
Authorized Subnet Yes/No
addresses (1) IP Address 0.0.0.0 ... 223.255.255.255
Subnet mask 224.0.0.0 ... 255.255.255.252
FTP Select this to grant access to the FTP server in the CPU.
TFTP Select this to grant access to the TFTP server in the CPU.
HTTP Select this to grant access to the HTTP server in the CPU.
Port 502 Select this to grant access to port 502 (typically used for Modbus
messaging) of the CPU.
EIP Select this to grant access to the EtherNet/IP server in the CPU.
SNMP Select this to grant access to the SNMP agent resident in the CPU.
1
Set Access Control to Enabled to modify this field.
NOTE: Refer to the ETH_PORT_CTRL topic (see page 379) for information regarding using this
function block to control the FTP, TFTP, HTTP, and DHCP/BOOTP protocols.
Step Action
1 Set Access Control to Enabled.
2 In the IP Address column of the Authorized Addresses list, enter an IP address.
3 Enter the address of the device to access the CPU’s Ethernet I/O scanner service with either of
these methods:
Add a single IP address: Enter the IP address of the device and select No in the Subnet
column.
Add a subnet: Enter a subnet address in the IP Address column. Select Yes in the Subnet
column. Enter a subnet mask in the Subnet Mask column.
NOTE:
The subnet in the IP Address column can be the subnet itself or any IP address in the subnet.
If you enter a subnet without a subnet mask, an on-screen message states that the screen
cannot be validated.
A red exclamation point (!) indicates a detected error in the entry. You can save the
configuration only after the detected error is addressed.
4 Select one or more of the following methods of access you are granting the device or subnet:
FTP, TFTP, HTTP, Port 502, EIP, SNMP.
5 Repeat steps 2 - 4 for each additional device or subnet to which you want to grant access to the
CPU’s Ethernet I/O scanner service.
NOTE: You can enter up to 127 authorized IP addresses or subnets.
6 Click Apply.
Step Action
1 In the Authorized Addresses list, select the IP address of the device to delete.
2 Press the Delete button.
3 Click Apply.
IPConfig Tab
IPConfig Parameters
IP address configuration field on the IPConfig tab:
IP address A 192.168.11.1 This address applies to the RIO scanner service in the CPU
designated as A. (See the note below.)
IP address B – For M580 Hot Standby CPUs only, this address applies to the RIO
scanner service in the CPU designated as B. (See the note below.)
Subnetwork mask 255.255.0.0 This bit mask identifies or determines the IP address bits that
correspond to the network address and the subnetwork portion of the
address. (The value can be changed to any valid value in the
subnetwork.)
Gateway address 192.168.10.1 This is the IP address of the default gateway to which messages for
other networks are transmitted.
NOTE:
If you change IP address A, the system may recalculate all IP addresses (including those of the drops) to
keep all devices in the same subnetwork.
In M580 Hot Standby systems, both CPU A and CPU B maintain a redundant owner connection with each
RIO device (BM•CRA312•0 adapter). For this reason, when a Hot Standby switchover occurs, the state of
RIO outputs is not affected – the Hot Standby switchover transition is bumpless.
Viewing and Editing the IP Address and Device Name of Network Devices
The CRA IP address configuration area on the IPConfig tab is provided for CPUs with Ethernet I/O
scanner service (CPUs with commercial references that end 40). Use this area to display a list of
RIO/DIO scanners and BM•CRA312•0 adapters, and view or edit the device IP address and device
Identifier:
Step Action
1 Click the CRA IP address configuration link to open the Ethernet Network window.
2 In the Subtype header, filter the device list by selecting:
Scanner RIO/DIO
CRA
... (select both)
This list applies the selected filter, and displays all detected network devices of the selected
type(s).)
3 The IP Address field displays the address that was automatically assigned when the device was
added to the network.
NOTE: Although the IP address is editable, Schneider Electric recommends that you accept the
automatically assigned IP address.
4 The Identifier field displays the identifier for the module, which is also the Device Name. To edit the
Identifier setting:
1. Double-click on the Identifier value. The value becomes editable.
2. Type in a new value.
3. Click the Control Expert Validate button.
The new Identifier setting is applied.
NOTE: All other fields in the Ethernet Network window are read-only.
Advanced Configuration
To configure DHCP and FDR services in the DTM browser, click the Services configuration link in
the Advanced configuration section of the window.
RSTP Tab
Introduction
The Ethernet DEVICE NETWORK ports on the front of the M580 CPU support rapid spanning tree
protocol (RSTP). RSTP is an OSI layer 2 protocol defined by IEEE 802.1D 2004. RSTP performs
these services:
RSTP creates a loop-free logical network path for Ethernet devices that are part of a topology
that includes redundant physical paths. When either DEVICE NETWORK port (ETH 2 or ETH 3)
on the CPU is disconnected, the RSTP service directs traffic to the other port.
RSTP automatically restores network communication by activating redundant links when a
network event causes a loss of service.
NOTE: When an RSTP link is disconnected, the RSTP service acts on an event and forwards traffic
through the correct port. During this re-connect time (50ms max), some packets may be lost.
The RSTP service creates a loop-free logical network path for Ethernet devices that are part of a
topology that includes redundant physical paths. When the network experiences a loss of service,
the RSTP-enabled module automatically restores network communication by activating redundant
links.
NOTE: RSTP can be implemented only when all network switches are configured to support RSTP.
Changing these parameters can affect sub-ring diagnostics, RIO determinism, and network
recovery times.
Step Action
1 Select RSTP to see the RSTP Operational State.
2 Select a Bridge Priority from the drop-down list in the RSTP Operational State area:
Root (0) (default)
Backup Root (4096)
Participant (32768)
RSTP Parameters for CPUs with RIO and DIO Scanner Service
RSTP tab:
RSTP Parameters for CPUs without RIO Scanner Service (DIO Scanner Service Only)
RSTP tab:
SNMP Tab
Introduction
Use the SNMP tab in Control Expert to configure individual SNMP parameters for these modules:
M580 CPU modules
(e)X80 EIO adapter modules on RIO drops
140CRA3120• RIO adapter modules in Quantum EIO systems
An SNMP v1 agent is a software component of the SNMP service that runs on these modules to
allow access to diagnostic and management information for the modules. You can use SNMP
browsers, network management software, and other tools to access this data. In addition, the
SNMP agent can be configured with the IP addresses of one or two devices (typically PCs that run
network management software) to be the targets of event-driven trap messages. Such messages
inform the management device of events like cold starts and the inability of the software to
authenticate a device.
Use the SNMP tab to configure the SNMP agents for communication modules in the local rack and
RIO drops. The SNMP agent can connect to and communicate with one or two SNMP managers
as part of an SNMP service. The SNMP service includes:
authentication checking by the Ethernet communication module, of any SNMP manager that
sends SNMP requests
management of events or traps
SNMP Parameters
View and edit these properties on the SNMP page:
Property Description
IP Address IP Address Manager 1 The IP address of the first SNMP manager to which the SNMP agent
Managers: sends notices of traps.
IP Address Manager 2 The IP address of the second SNMP manager to which the SNMP
agent sends notices of traps.
Agent: Location The device location (32 characters maximum)
Contact Information describing the person to contact for device maintenance
(32 characters maximum)
SNMP Manager Select one:
Disabled: You can edit the Location and Contact settings on this
page.
Enabled: You cannot edit the Location and Contact settings on
this page. (Those settings are managed by the SNMP Manager.)
Community Get Password required by the SNMP agent before executing read
Names: commands from an SNMP manager (default = public).
Set Password required by the SNMP agent before executing write
commands from an SNMP manager (default = private).
Trap Password an SNMP manager requires from the SNMP agent before
the manager accepts trap notices from the agent (default = alert).
Security: Enable Authentication TRUE causes the SNMP agent to send a trap notice to the SNMP
Failure Trap manager if an unauthorized manager sends a Get or Set command
to the agent (default = Disabled).
NTP Tab
Introduction
You can configure an M580 CPU as an NTP server or an NTP client in the Control Expert NTP tab.
The NTP service has these features:
A periodic time correction is obtained from the reference-standard time server.
There is an automatic switchover to a backup (secondary) time server if an error is detected with
the normal time server system.
Controller projects use a function block to read the accurate clock, allowing project events or
variables to be time stamped. (Refer to the System Time Stamping User Guide (see System
Time Stamping, User Guide) for detailed information about timestamping performance.)
NOTE:
When the M580 CPU is configured as either an NTP server or as an NTP client, the BM•CRA312•0
(e)X80 EIO adapter modules are NTP clients of the CPU:
When only BM•CRA31200 modules are configured as NTP clients, the accuracy of this server
allows time discrimination of 20 ms.
All BM•CRA31200 modules in the network have the same client configuration.
To begin, open the CPU configuration tabs in Control Expert (see page 119).
Once an accurate time is received, the service sets the status in the associated time service
register.
The time service clock value starts at 0 until fully updated from the CPU.
Value Comment
Disabled default: Both the NTP server and the NTP client services of the PAC are disabled.
NTP Client The PAC functions as the NTP client. In this case, configure the NTP Server
Configuration parameters.
NOTE: Enable the NTP client here to automatically enable the NTP client service on
all BM•CRA312•0 adapter modules.
NTP Server The Ethernet I/O scanner PAC acts as an NTP server.
NOTE: Enable the NTP client here to automatically enable the NTP client service on
all BM•CRA312•0 adapter modules and to configure the BM•CRA312•0 to use the PAC
as the NTP server.
Parameter Comment
Primary NTP Server the IP address of the NTP server, from which the PAC first requests a time value
IP address
Secondary NTP Server the IP address of the backup NTP server, from which the PAC requests a time value
IP address after not receiving a response from the primary NTP server
Polling Period The time (in seconds) between updates from the NTP server. Smaller values
typically result in better accuracy.
Switch Tab
Description
The Switch tab is only available for CPUs without RIO scanner service. It contains these fields:
NOTE: ETH1 port is a dedicated service port and the Ethernet backplane network is dedicated to
the communication between modules on the rack. The switch parameters for those two ports
cannot be configured in the Switch tab.
QoS Tab
Description
The M580 CPU can be configured to perform Ethernet packet tagging. The CPU supports the OSI
layer 3 quality of service (QoS) standard defined in RFC-2475. When you enable QoS, the CPU
adds a differentiated services code point (DSCP) tag to each Ethernet packet that it transmits to
indicate the priority of that packet.
QoS Tab
The QoS tab is available only on CPUs that do not support the RIO scanner service (only on CPUs
with commercial references that end with 20).
DSCP tagging lets you prioritize the Ethernet packet streams based on the type of traffic in that
stream.
To implement QoS settings in your Ethernet network:
Use network switches that support QoS.
Consistently apply DSCP values to network devices and switches that support DSCP.
Confirm that switches apply a consistent set of rules for sorting DSCP tags, when transmitting
and receiving Ethernet packets.
On-line Behavior
The Service Port parameters are stored in the application, but you can reconfigure the parameters
in connected mode. Values that you reconfigure in connected mode are sent to the PAC through
explicit messaging.
The changed values are not stored, so a mismatch can exist between the parameters that are
being used and those that are in the stored application.
Introduction
The Advanced Settings tab is only available for CPUs that do not support RIO scanning (DIO
scanner service only). The Advanced Settings contains these fields:
EtherNet/IP Timeout Settings
EtherNet/IP Scanner Behavior
Timeout Settings
These parameters are in the EtherNet/IP Timeout Settings field:
Scanner Behavior
These parameters are in the EtherNet/IP Scanner Behavior field:
Safety Tab
Introduction
A CIP Safety CPU is the originator of CIP Safety communications, and is identified by its originator
unique identifier (OUNID). Use this tab to configure an OUNID for the CIP Safety CPU. Each
OUNID is a 10 byte concatenated value, consisting of a:
Safety Network Number (6 bytes)
IP Address (4 bytes)
NOTE: Changes to the OUNID can be made only offline. After the changed configuration is built,
the application can be downloaded to the PAC.
You can update the OUNID by updating the auto-generated value, or changing the manual value.
IP Address
This is automatically set to the CPU Main IP address (see page 125). The OUNID is updated if the
IP address changes.
Parameter Description
Safety Network Number Click Advanced... to open the Safety Network Number dialog, where you can
enter this setting:
Automatically, by selecting Time-based, then clicking the Generate button.
The auto-generated value appears in the Number field.
Manually, by selecting Manual, then a 6 byte hexadecimal character string
in the Number field.
Click OK to close the dialog and save the Safety Network Number.
IP Address This read-only setting is automatically input, based on the configured
Main IP address CPU setting.
OUNID The auto-generated hexadecimal identifier: a concatenation of the Safety
Network Number and the IP Address.
Section 5.3
Configuring the M580 CPU with DTMs in Control Expert
Introduction
Some configuration features for the M580 CPU are accessed through its corresponding M580 DTM
in the Control Expert DTM Browser.
Use the instructions in this section to configure the M580 CPU through the DTM.
Introduction
The configuration of the M580 CPU through standard Control Expert features is described
elsewhere in this guide (see page 118).
Some configuration that is specific to a particular device (like the M580 CPU) is done through a
corresponding device type manager (DTM) in Control Expert. This section describes that
configuration.
Step Action
1 Open Control Expert.
2 Open a Control Expert project that includes a M580 CPU in the configuration.
3 Open the DTM Browser (Tools → DTM Browser).
4 Double-click the DTM that corresponds to the M580 CPU in the DTM Browser to open the device
editor of the DTM.
5 These headings appear in the configuration tree of the M580 DTM:
Channel Properties
Services
EtherNet/IP Local Slaves
Device List
Logging
Introduction
On the Control Expert Channel Properties page, you can select a Source IP Address (PC) from a
pull-down menu.
The Source IP Address (PC) menu is a list of IP addresses that are configured for a PC that has
the Control Expert DTM installed.
To make the connection, choose a Source IP Address (PC) that is in the same network as the CPU
and the device network.
You can execute these tasks through this connection:
Perform fieldbus discovery.
Execute Online Actions.
Send an explicit message to an EtherNet/IP device.
Send an explicit message to a Modbus TCP device.
Diagnose modules.
Step Action
1 Open a Control Expert project that includes a M580 CPU.
2 Open the DTM Browser (Tools → DTM Browser).
3 In the DTM Browser, find the name that you assigned to the CPU.
4 Double-click (or right-click Open) the name of the CPU to open the configuration window.
5 Select Channel Properties in the navigation pane.
Property Descriptions
This table describes the parameters for the Channel Properties:
Step Action
1 Select an IP address from the Source IP Address (PC) pull-down menu.
2 Press the Apply button.
3 In the DTM Browser, find the name that you assigned to the CPU.
4 Right-click the name of the CPU and scroll to Connect.
TCP/IP Monitoring
Expand (+) the Channel Properties heading in the configuration tree and select the TCP/IP item at
level 1.
The read-only information on this page monitors the IP parameters that were configured in Control
Expert.
Step Action
1 Open Control Expert.
2 Open a Control Expert project that includes a M580 CPU in the configuration.
3 Open the DTM Browser (Tools → DTM Browser).
4 Double-click the DTM that corresponds to the M580 CPU in the DTM Browser to open the device
editor of the DTM.
5 Expand (+) the Services heading in the configuration tree.
6 Select the Address Server item in the configuration tree to see the address server configuration.
Configuration
Configure the address server to perform these tasks:
Enable and disable the CPU FDR service.
View an automatically generated list of all devices included in the CPU configuration, displaying
for each device:
IP addressing parameters
whether the device IP addressing parameters are provided by the CPU embedded DHCP
server
Manually add remote devices that are not part of the CPU configuration to the CPU DHCP client
list.
NOTE: Remote devices added in this way are equipped with DHCP client software and are
configured to subscribe to the CPU IP addressing service.
Any networked Ethernet device equipped with FDR client functionality can subscribe to the CPU
FDR service.
The maximum size of the FDR client operating parameter files depends on the CPU reference.
When this capacity is reached, the CPU cannot store additional client FDR files
CPU Reference PRM File Size Concurrent Connections
BMEP581020 8 MB 64
BMEP582020 16 MB 128
BMEP582040 17 MB 136
BMEP583020 16 MB 128
BMEP583040 25 MB 208
BMEP584020 16 MB 128
BMEP584040 25 MB 208
BMEP585040 25 MB 208
BMEP586040 25 MB 208
BMEH582040 25 MB 208
BMEH584040 25 MB 208
BMEH586040 25 MB 208
NOTE: The FDR usage percentage is monitored by the FDR_USAGE variable in the DDDT
(see page 217).
NOTE: You cannot add devices to this list in this page. Instead, use the configuration pages for the
remote device to subscribe to this service.
This table describes the available properties:
Property Description
Device No The number assigned to the device in the Control Expert configuration.
IP Address The client device IP address.
DHCP TRUE indicates that the device subscribes to the DHCP service.
Identifier Type Indicates the mechanism used by the server to recognize the client (MAC address or
DHCP device name).
Identifier The actual MAC address or DHCP device name.
Netmask The client device subnet mask.
Gateway A DHCP client device uses the gateway IP address to access other devices that are not
located on the local subnet. A value of 0.0.0.0 constrains the DHCP client device by
allowing it to communicate only with devices on the local subnet.
Step Description
1 In the Address Server page, click the Add button in the Manually Added Devices field to instruct
Control Expert to add an empty row to the list.
2 In the new row, configure these parameters for the client device:
IP Address Type in the IP address of the client device.
Identifier Type Select the type of value the client device uses to identify itself to the FDR server:
MAC address
device Name
Identifier Depending upon the identifier type, type in the client device setting for the MAC
address or name.
Netmask Type in the client device subnet mask.
Gateway Type in the gateway address that remote devices can use to communicate with
devices located on other networks. Use 0.0.0.0 if remote devices do not
communicate with devices located on other networks.
3 Refer to the topic Configuring Properties in the Device Editor (see Modicon M580,
BMENOC0301/0311 Ethernet Communications Module, Installation and Configuration Guide) for
instructions on how to apply edited properties to networked devices.
Section 5.4
Diagnostics through the Control Expert DTM Browser
Introduction
The Control Expert DTM provides diagnostics information that is collected at configured polling
intervals. Use this information to diagnose the operation of the embedded Ethernet scanner
service in the CPU.
Step Action
1 Open a Control Expert project.
2 Open the Control Expert DTM Browser (Tools → DTM Browser).
3 Right-click the name that is assigned to your CPU in the DTM Browser.
4 Select Connect.
Step Action
1 Right-click the name that is assigned to your CPU in the DTM Browser.
2 Select Device Menu → Diagnosis to view the available diagnostics pages.
Diagnostics Information
The diagnostics window has two distinct areas:
left pane: LED icons indicate the operating status of modules, devices, and connections.
right pane: These pages show diagnostics data for these items:
CPU’s embedded scanner service
local slave nodes that are activated for the CPU’s embedded scanner service
EtherNet/IP connections between the CPU’s embedded scanner service and a remote
EtherNet/IP device
When the appropriate DTM is connected to the CPU, Control Expert sends an explicit message
request once per second to detect the state of the CPU’s embedded scanner service and of all the
remote devices and EtherNet/IP connections linked to the CPU.
Control Expert places one of these status icons over the module, device, or connection in the left
pane of the Diagnostic window to indicate its current status:
Bandwidth Diagnostics
Introduction
Use the Bandwidth page to view the dynamic and static data for the bandwidth use by the
embedded Ethernet scanner service in the CPU.
NOTE: Before you can open the diagnostics page, make the connection between the DTM for the
CPU’s embedded scanner service and the physical module.
Step Action
1 In the DTM Browser, right-click the name that is assigned to your CPU.
2 Select Device menu → Diagnosis.
3 In the left pane of the Diagnosis window, select the CPU node.
4 Select the Bandwidth tab to open that page.
Data Display
Use the Refresh Every 500ms checkbox to display the static or dynamic data:
Checkbox Description
Selected Display data that is dynamically updated every 500 ms.
Increment the number at the top of the table each time data is refreshed.
Parameter Description
I/O - Scanner:
EtherNet/IP Sent The number of EtherNet/IP packets the module has sent in packets/second.
EtherNet/IP Received The number of EtherNet/IP packets the module has received in
packets/second.
Modbus TCP Received The number of Modbus TCP requests the module has sent in packets/second.
Modbus TCP Responses The number of Modbus TCP responses that the CPU’s embedded scanner
service has received in packets/second.
I/O - Adapter:
EtherNet/IP Sent The number of EtherNet/IP packets (per second) that the CPU’s embedded
scanner service has sent in the role of a local slave.
EtherNet/IP Received The number of EtherNet/IP packets (per second) that the CPU’s embedded
scanner service has received in the role of a local slave.
I/O - Module
Module Capacity The maximum number of packets (per second) that the CPU’s embedded
scanner service can process.
Module Utilization The percentage of the CPU’s embedded scanner service capacity being used
by the application.
Messaging - Client:
EtherNet/IP Activity The number of explicit messages (packets per second) sent by the CPU’s
embedded scanner service using the EtherNet/IP protocol.
Modbus TCP Activity The number of explicit messages (packets per second) sent by the CPU’s
embedded scanner service using the Modbus TCP protocol.
Messaging - Server:
EtherNet/IP Activity The number of server messages (packets per second) received by the CPU’s
embedded scanner service using the EtherNet/IP protocol.
Modbus TCP Activity The number of server messages (packets per second) received by the CPU’s
embedded scanner service using the Modbus TCP protocol.
Module:
Processor Utilization The percentage of the CPU’s embedded scanner service processing capacity
used by the present level of communication activity.
RSTP Diagnostics
Introduction
Use the RSTP Diagnostic page to view the status of the RSTP service of the embedded Ethernet
scanner service in the CPU. The page displays dynamically generated and static data for the
module.
NOTE: Before you can open the diagnostics page, make the connection between the DTM for the
CPU’s embedded scanner service and the physical module.
Step Action
1 In the DTM Browser, right-click the name that is assigned to your CPU.
2 Select Device menu → Diagnosis.
3 In the left pane of the Diagnosis window, select the CPU node.
4 Select RSTP Diagnostic tab to open that page.
Data Display
Select the Refresh Every 500ms check box to display the static or dynamic data:
Checkbox Description
Selected Display data that is dynamically updated every 500 ms.
Increment the number at the top of the table each time data is refreshed.
Parameter Description
Bridge RSTP Diagnostic:
Bridge Priority This 8-byte field contains the two-byte value that is assigned to the CPU’s embedded
Ethernet switch.
MAC Address The Ethernet address of the CPU, found on the front of the CPU.
Designated Root ID The Bridge ID of the root device.
Root Path Cost The aggregate cost of port costs from this switch back to the root device.
Default Hello Time The interval at which Configuration BPDU messages are transmitted during a
network convergence. For RSTP this is a fixed value of 2 seconds.
Learned Hello Time The current Hello Time value learned from the root switch.
Configured Max Age The value (6 ... 40) that other switches use for MaxAge when this switch is acting as
the root.
Learned Max Age The maximum age learned from the root switch. This is the actual value currently
used by this switch.
Total Topology The total number of topology changes detected by this switch since the management
Changes entity was last reset or initialized.
Ports ETH 2 and ETH 3 RSTP Statistics:
Status The port's current state as defined by RSTP protocol. This state controls the action
the port takes when it receives a frame. Possible values are: disabled, discarding,
learning, forwarding.
Role: The port’s current role per RSTP protocol. Possible values are: root port, designated
port, alternate port, backup port, disabled port.
Cost The logical cost of this port as a path to the root switch. If this port is configured for
AUTO then the cost is determined based on the connection speed of the port.
STP Packets A value in this field indicates that a device on the network has the STP protocol
enabled.
NOTE:
Other devices that are enabled for STP can severely affect the network
convergence times. Schneider Electric recommends that you disable the STP
protocol (but not the RSTP protocol) on every network device that supports STP.
The CPU does not support the STP protocol. The CPU’s embedded switch
ignores STP packets.
Introduction
Use the Network Time Service Diagnostic page to display dynamically generated data describing
the operation of the simple network time protocol (SNTP) service that you configured in the network
time server page (see page 131) in Control Expert.
NOTE: Before you can open the diagnostics page, make the connection between the DTM for the
target communication module and the CPU.
Refer to the System Time Stamping User Guide (see System Time Stamping, User Guide) for
detailed diagnostic information.
Step Action
1 In the DTM Browser, find the name that is assigned to the CPU.
2 Right-click the CPU DTM, and select Device menu → Diagnosis.
3 In the left pane of the Diagnosis window, select the CPU node.
4 Select the NTP Diagnostic tab to open that page.
Click the Reset Counter button to reset the counting statistics on this page to 0.
Parameter Description
Refresh Every Check this box to dynamically update the page every 500ms. The number of times
500ms this page has been refreshed appears immediately to the right.
Network Time Monitor the operational status of the service in the module:
Service green: operational
orange: disabled
Network Time Server Monitor the communication status of the NTP server:
Status green: The NTP server is reachable.
red: The NTP server is not reachable.
Last Update Elapsed time, in seconds, since the most recent NTP server update.
Current Date System date
Current Time The system time is presented in the hh:mm:ss format.
Parameter Description
DST Status Set the status of the automatic daylight savings service:
ON: The automatic adjustment of daylight savings is enabled. The current date
and time reflect the daylight savings time adjustment.
OFF: The automatic adjustment of daylight savings is disabled. (The current date
and time may not reflect the daylight savings time adjustment.)
Quality This correction (in seconds) applies to the local counter at every NTP server update.
Numbers greater than 0 indicate increasingly excessive traffic condition or an NTP
server overload.
Requests This value represents the total number of client requests sent to the NTP server.
Responses This value represents the total number of server responses sent from the NTP server.
Errors This value represents the total number of unanswered NTP requests.
Last Error This value indicates the last detected error code received from the NTP client:
0: good NTP configuration
1: late NTP server response (can be caused by excessive network traffic or server
overload)
2: NTP not configured
3: invalid NTP parameter setting
4: NTP component disabled
5: NTP server is not synchronized (NTP server needs to be synchronized so that
the NTP accesses behave as defined in the client NTP settings)
7: unrecoverable NTP transmission
9: invalid NTP server IP address
15: invalid syntax in the custom time zone rules file
Primary / Secondary The IP addresses correspond to the primary and secondary NTP servers.
NTP Server IP
NOTE: A green LED to the right of the primary or secondary NTP server IP address
indicates the active server.
Auto Adjust Clock for Configure the daylight savings adjustment service:
Daylight Savings enabled
disabled
DST Start / DST End Specify the day on which daylight savings time begins and ends:
Month Set the month in which daylight savings time starts or ends.
Day of Week Set the day of the week on which daylight savings time starts or
ends.
Week# Set the occurrence of the specified day within the specified month.
Time Zone Select the time zone plus or minus Universal Time, Coordinated (UTC)
Offset Configure the time (in minutes) to be combined with the time zone selection (above)
to produce the system time.
Polling Period Set the frequency with which the NTP client requests an updated time from the NTP
server
Introduction
Use the Local Slave Diagnostic page and the Connection Diagnostic page to display the I/O status
and production/consumption information for a selected local slave or connection.
NOTE:
Before you can open the diagnostics page, make the connection between the DTM for the target
communication module and the CPU.
To get data from the primary CPU, make the connection to the Main IP address of the CPU
(see Modicon M580 Hot Standby, System Planning Guide for, Frequently Used Architectures).
Data Display
Use the Refresh Every 500ms checkbox to display the static or dynamic data:
Checkbox Description
Selected Display data that is dynamically updated every 500 ms.
Increment the number at the top of the table each time data is refreshed.
Parameter Description
Input An integer representing input status.
Output An integer representing output status.
General An integer representing basic connection status.
Extended An integer representing extended connection status.
The Input and Output status diagnostic parameters can present these values:
This table shows the Counter diagnostic parameters for the selected connection:
Parameter Description
Frame Error Increments each time a frame is not sent by missing resources or is impossible to
send.
Time-Out Increments each time a connection times out.
Refused Increments when connection is refused by the remote station.
Production Increments each time a message is produced.
Consumption Increments each time a message is consumed.
Production Byte Total of produced messages, in bytes, since the communication module was last
reset.
Consumption Byte Total of consumed messages, in bytes, since the communication module was last
reset.
Theoretical Packets per Packets per second calculated using current configuration value.
second
Real Packets per Actual number of packets per second generated by this connection.
second
This table shows the Diagnostic parameters for the selected connection:
Parameter Description
CIP Status An integer representing CIP status.
Extended Status An integer representing extended CIP status.
Production The connection ID for the data produced by the local slave.
Connection ID
Consumption The connection ID for the data produced by the local slave.
Connection ID
Parameter Description
O -> T API Actual packet interval (API) of the production connection.
T -> O API Actual packet interval (API) of the consumption connection.
O -> T RPI Requested packet interval (RPI) of the production connection.
T -> O RPI Requested packet interval (RPI) of the consumption connection.
This table shows the Socket Diagnostics diagnostic parameters for the selected connection:
Parameter Description
Socket ID Internal identification of the socket.
Remote IP Address IP address of the remote station for this connection.
Remote Port UDP port number of the remote station for this connection.
Local IP Address IP address of the communication module for this connection.
Local Port UDP port number of the communication module for this connection.
This table shows the Production diagnostic parameters for the selected connection:
Parameter Description
Sequence Number The number of the sequence in the production.
Max Time Maximum time between two produced messages.
Min Time Minimum time between two produced messages.
RPI Current production time.
Overrun Increments each time a produced message exceeds RPI.
Underrun Increments each time a produced message is less than RPI.
This table shows the Consumption diagnostic parameters for the selected connection:
Parameter Description
Sequence Number The number of the sequence in the consumption.
Max Time Maximum time between two consumption messages.
Min Time Minimum time between two consumption messages.
RPI Current consumption time.
Over Run Increments each time a consumed message exceeds RPI.
Under Run Increments each time a consumed message is less than RPI.
Introduction
Use the I/O Values page to display both the input data image and output data image for the
selected local slave or scanner connection.
NOTE: Before you can open the diagnostics page, make the connection (see page 314) between
the DTM and the target communication module.
Step Action
1 In the DTM Browser, find the name that is assigned to the CPU DTM.
2 Right-click the CPU DTM , and select Device menu → Diagnosis.
3 In the left pane of the Diagnosis window, select the CPU.
4 Select the I/O Values tab.
Data Display
Use the Refresh Every 500ms checkbox to display the static or dynamic data:
Checkbox Description
Selected Display data that is dynamically updated every 500 ms.
Increment the number at the top of the table each time data is refreshed.
Parameter Description
Input/Output A display of the local slave or remote device input or output data image.
data display
Length The number of bytes in the input or output data image.
Status The Scanner Diagnostic object’s status, with respect to the read of the input or output data
image.
Description
Control Expert maintains a log of events for:
the Control Expert embedded FDT container
each Ethernet communication module DTM
each EtherNet/IP remote device DTM
Events relating to the Control Expert FDT container are displayed in the FDT log event page of the
Output Window.
Events relating to a communication module or remote EtherNet/IP device are displayed:
in configuration mode: in the Device Editor, by selecting the Logging node in the left pane
in diagnostic mode: in the Diagnostics window, by selecting the Logging node in the left pane
Logging Attributes
The Logging window displays the result of an operation or function performed by Control Expert.
Each log entry includes the following attributes:
Attribute Description
Date/Time The time the event occurred, displayed in the format: yyyy-mm--dd hh:mm:ss
Log Level The level of event importance. Values include:
Information A successfully completed operation.
Warning An operation that Control Expert completed, but which may lead to a
subsequent error.
Error An operation that Control Expert was unable to complete.
Message A brief description of the core meaning of the event.
Detail Message A more detailed description of the event, which may include parameter names, location
paths, etc.
Step Action
1 Open a project that includes a BME •58 •0•0 Ethernet CPU.
2 Clock Tools → DTM Browser to open the DTM Browser.
3 In the DTM Browser, double-click the CPU (or right-click Open) to open the configuration
window.
4 Select Logging in the navigation tree in the left pane of the window.
Step Action
1 In Control Expert, select Tools → Project Settings.
2 In the left pane of the Project Settings window, select Project Settings → General → PLC
diagnostics.
3 In the right pane:
Select the PLC event logging check box.
In the SYSLOG server address field enter the IP address of the SYSLOG server.
In the SYSLOG server port number field, enter the port number.
NOTE: The SYSLOG server protocol is not configurable, and is set to tcp by default.
NOTE: Refer to the Modicon Controllers Platform Cyber Security Reference Manual for information
on setting up a SYSLOG server in your system architecture (see Modicon Controllers Platform,
Cyber Security, Reference Manual).
Section 5.5
Online Action
Online Action
Online Action
Introduction
You can view and configure the settings in the Online Action menu when the M580 CPU is
connected through the Control Expert DTM Browser.
Step Action
1 Open the DTM Browser in Control Expert (Tools → DTM Browser).
2 Select the M580 DTM in the DTM Browser.
3 Connect the DTM to the Control Expert application (Edit → Connect).
4 Right-click the M580 DTM.
5 Scroll to the Online Action menu (Device menu → Additional functions → Online Action).
6 3 tabs appear:
Ethernet/IP Objects
Port Configuration
Ping
EtherNet/IP Objects
Displays object parameters value when available.
Click Refresh to update the displayed values.
Port Configuration
Configure and read the service port mode:
Field Description
Service Port Mode Access (default)
Mirroring
NOTE: This mode can also be set in the CPU configuration tabs
(see page 135).
Access Port Configuration Displays the access port configuration information (refer to CPU configuration
tabs (see page 135)).
Port Mirroring Displays the port mirroring configuration (refer to CPU configuration tabs
Configuration (see page 135)).
Ping
Introduction
Use the EtherNet/IP Objects tab in the Online Action window:
Retrieve and display current data describing the state of CIP objects for the selected CPU or
remote EtherNet/IP device.
Reset the selected CPU or remote EtherNet/IP device.
Step Action
1 Connect the DTM to the module (see Modicon M580, BMENOC0301/0311 Ethernet
Communications Module, Installation and Configuration Guide).
2 Open the Online Action page (see Modicon M580, BMENOC0301/0311 Ethernet
Communications Module, Installation and Configuration Guide).
3 Select the EtherNet/IP Objects tab.
Introduction
Use the Service Port tab in the Online Action window to view and edit communication port
properties for a distributed EtherNet/IP device. Use this tab to execute these commands:
Refresh: Use a Get command to retrieve port configuration settings from a distributed
EtherNet/IP device.
Update: Use a Set command to write all or selected edited values to the same distributed
EtherNet/IP device
The configuration information on the Service Port tab is sent in EtherNet/IP explicit messages that
employ the address and messaging settings configured for Ethernet/IP explicit messaging (below).
Step Action
1 Connect the DTM to the module (see Modicon M580, BMENOC0301/0311 Ethernet
Communications Module, Installation and Configuration Guide).
2 Open the Online Action page (see Modicon M580, BMENOC0301/0311 Ethernet
Communications Module, Installation and Configuration Guide).
3 Select the EtherNet/IP Objects tab.
4 Configure the Service port with the instructions from the offline configuration
(see Modicon M580, BMENOC0301/0311 Ethernet Communications Module, Installation and
Configuration Guide).
5 Click the Update button to apply the new configuration.
Overview
Use the Control Expert ping function to send an ICMP echo request to a target Ethernet device to
determine:
if the target device is present, and if so
the elapsed time to receive an echo response from the target device
The target device is identified by its IP address setting. Enter only valid IP addresses in the IP
Address field.
The ping function can be performed in the Ping page of the Online Action window:
Step Action
1 In the DTM Browser, select the CPU upstream of the remote EtherNet/IP device you want to
ping.
2 Right-click and select Device Menu → Online Action.
Result: The Online Action window opens.
3 In the Online Action window, select the device you want to ping.
Result: The window displays pages containing online information for the selected device.
NOTE: The specific collection of displayed pages depends on the type of device selected:
the CPU
a remote EtherNet/IP device
a remote Modbus TCP device
Section 5.6
Diagnostics Available through Modbus/TCP
Introduction
CPUs and BMENOC0301/11 communication modules in M580 systems support the diagnostic
codes in these tables.
Function Code 3
Some module diagnostics (I/O connection, extended health, redundancy status, FDR server, etc.)
are available to Modbus clients that read the local Modbus server area. Use Modbus function code
3 with the unit ID set to 100 for register mapping:
For a description of available function codes refer to the list of supported Modbus diagnostic codes
in the topic Modbus Diagnostic Codes (see Quantum IEC61850, 140 NOP 850 00, Installation and
Configuration Guide) in the Quantum EIO Control Network Installation and Configuration Guide.
Function Code 8
Modbus function code 08 provides a variety of diagnostic functions:
This table provides sample responses to the Modbus request (function code 43, subcode 14):
Section 5.7
Diagnostics Available through EtherNet/IP CIP Objects
Introduction
Modicon M580 applications use CIP within a producer/consumer model to provide communication
services in an industrial environment. This section describes the available CIP objects for
Modicon M580 CPU modules.
Overview
The Ethernet communication module can access CIP data and services located in connected
devices. The CIP objects and their content depend on the design of each device.
CIP object data and content are exposed—and accessed—hierarchically in the following nested
levels:
NOTE:
You can use explicit messaging to access these items:
Access a collection of instance attributes by including only the class and instance values for the
object in the explicit message.
Access a single attribute by adding a specific attribute value to the explicit message with the
class and instance values for the object.
This chapter describes the CIP objects that the Ethernet communication module exposes to
remote devices.
Identity Object
Overview
The Identity object presents the instances, attributes and services described below.
Class ID
01
Instance IDs
The Identity object presents two instances:
0: class
1: instance
Attributes
Identity object attributes are associated with each instance, as follows:
Instance ID = 0 (class attributes):
Services
The Identity object performs the following services upon the listed object types:
Assembly Object
Overview
The assembly object consists of the attributes and services. Assembly instances exist only when
you configure local slaves (see page 309) for the M580 CPU modules.
You can send an explicit message to the assembly object only when no other connections have
been established that read from or write to this object. For example, you can send an explicit
message to the assembly object if a local slave instance is enabled, but no other module is
scanning that local slave.
Class ID
04
Instance IDs
The assembly object presents these instance identifiers:
0: class
101, 102, 111, 112, 121, 122: instance
Attributes
The assembly object consists of these attributes:
Instance ID = 0 (class attributes):
Instance attributes:
Services
The CIP assembly object performs these services upon the listed object types:
Overview
The Connection Manager object presents the instances, attributes and services described below.
Class ID
06
Instance IDs
The Connection Manager object presents two instance values:
0: class
1: instance
Attributes
Connection Manager object attributes are associated with each instance, as follows:
Instance ID = 0 (class attributes):
Services
The Connection Manager object performs the following services on the listed object types:
Modbus Object
Overview
The Modbus object converts EtherNet/IP service requests to Modbus functions, and Modbus
exception codes to CIP General Status codes. It presents the instances, attributes and services
described below.
Class ID
44 (hex), 68 (decimal)
Instance IDs
The Modbus object presents two instance values:
0: class
1: instance
Attributes
The Modbus object consists of the following attributes:
Instance ID = 0 (class attributes):
Services
The Modbus object performs the following services upon the listed object types:
Overview
The QoS object implements Differentiated Services Code Point (DSCP or DiffServe) values for the
purpose of providing a method of prioritizing Ethernet messages. The QoS object presents the
instances, attributes and services described below.
Class ID
48 (hex), 72 (decimal)
Instance IDs
The QoS object presents two instance values:
0: class
1: instance
Attributes
The QoS object consists of the following attributes:
Instance ID = 0 (class attributes):
NOTE: A change in the instance attribute value takes effect on device re-start, for configurations
made from flash memory.
Services
The QoS object performs the following services upon the listed object types:
Overview
The TCP/IP interface object presents the instances (per network), attributes and services
described below.
Class ID
F5 (hex), 245 (decimal)
Instance IDs
The TCP/IP interface object presents 2 instance values:
0: class
1: instance
Attributes
TCP/IP interface object attributes are associated with each instance, as follows:
Instance ID = 0 (class attributes):
Services
The TCP/IP interface object performs the following services upon the listed object types:
Overview
The Ethernet Link object consists of the instances, attributes, and services described below.
Class ID
F6 (hex), 246 (decimal)
Instance IDs
The Ethernet Link object presents these instance values:
101: backplane slot 1
102: backplane slot 2
103: backplane slot 3
...
112: backplane slot 12
255: internal port
Attributes
The Ethernet Link object presents the following attributes:
Instance ID = 0 (class attributes):
Services
The Ethernet Link object performs the following services upon the listed object types:
Overview
The EtherNet/IP Interface Diagnostics object presents the instances, attributes and services
described below.
Class ID
350 (hex), 848 (decimal)
Instance IDs
The EtherNet/IP Interface object presents two instance values:
0: class
1: instance
Attributes
EtherNet/IP Interface Diagnostics object attributes are associated with each instance, as follows:
Instance ID = 0 (class attributes):
Services
The EtherNet/IP Interface Diagnostics object performs the following services upon the listed object
types:
Overview
The EtherNet/IP IO Scanner Diagnostics object presents the instances, attributes and services
described below.
Class ID
351 (hex), 849 (decimal)
Instance IDs
The EtherNet/IP IO Scanner Diagnostics object presents two instances:
0: class
1: instance
Attributes
EtherNet/IP IO Scanner Diagnostics object attributes are associated with each instance, as
follows:
Instance ID = 0 (class attributes):
Services
The EtherNet/IP IO Scanner Diagnostics object performs the following services upon the listed
object types:
Overview
The IO Connection Diagnostics object presents the instances, attributes and services described
below.
Class ID
352 (hex), 850 (decimal)
Instance IDs
The IO Connection Diagnostics object presents two instance values:
0 (class)
257 ... 643 (instance): The instance number matches the connection number in the Connection
Settings configuration (see Modicon M580, BMENOC0301/0311 Ethernet Communications
Module, Installation and Configuration Guide).
NOTE: The Instance ID number = the Connection ID. For M580 specifically, you can look up the
Connection ID on the DTM Device List screen.
Attributes
IO Connection Diagnostics object attributes are associated with each instance, as follows:
Instance ID = 0 (class attributes):
The following values describe the structure of the instance attributes: CIP Connection State,
Input Communication Status, and Output Communication Status:
Services
The EtherNet/IP Interface Diagnostics object performs the following services upon the listed object
types:
Overview
The EtherNet/IP Explicit Connection Diagnostics object presents the instances, attributes and
services described below.
Class ID
353 (hex), 851 (decimal)
Instance IDs
The EtherNet/IP Explicit Connection Diagnostics object presents two instance values:
0: class
1...N: instance (N = maximum concurrent number of explicit connections)
Attributes
EtherNet/IP Explicit Connection Diagnostics object attributes are associated with each instance,
as follows:
Instance ID = 0 (class attributes):
Services
The EtherNet/IP Explicit Connection Diagnostics object performs the following services upon the
listed object type:
Overview
The EtherNet/IP Explicit Connection Diagnostics List object presents the instances, attributes and
services described below.
Class ID
354 (hex), 852 (decimal)
Instance IDs
The EtherNet/IP Explicit Connection Diagnostics List object presents two instance values:
0: class
1: instance
Attributes
EtherNet/IP Explicit Connection Diagnostics List object attributes are associated with each
instance, as follows:
Instance ID = 0 (class attributes):
Services
The EtherNet/IP Explicit Connection Diagnostics object performs the following services upon the
listed object types:
Overview
The RSTP Diagnostics object presents the instances, attributes and services described below.
Class ID
355 (hex), 853 (decimal)
Instance IDs
The RSTP Diagnostics object presents these instance values:
0: class
1: instance
Attributes
RSTP Diagnostics object attributes are associated with each instance.
Instance ID = 0 (class attributes):
State UINT X X
Enable UINT X X
Path Cost UDINT X X
Designated Root String X X
Designated Cost UDINT X X
Designated Bridge String X X
Designated Port String X X
Forward Transitions UDINT X X Refer to RFC-4188 for attribute definitions
Count and value range.
Services:
Get_and_Clear: The current value of
this parameter is returned with the
response message.
other services: The current value of this
parameter is returned without being
cleared.
03 Port Mode STRUCT X — —
Port Number UINT X — This attribute indicates the port number for
a data query. The value range is
configuration dependent. For a 4-port
Ethernet device, as an instance, the valid
range is 1...4.
Admin Edge Port UINT X — This attribute indicates if this is a user-
configured edge port:
1: true
2: false
Services
The RSTP Diagnostics object performs these services:
Overview
The Service Port Control object is defined for port control purposes.
Class ID
400 (hex), 1024 (decimal)
Instance IDs
The Service Port Control object presents these instance Values:
0: class
1: instance
Attributes
Service Port Control object attributes are associated with each instance.
Required class attributes (instance 0):
NOTE:
If the SERVICE port is not configured for port mirroring, the mirror attribute is ignored. If the
value of a parameter request is outside the valid range, the service request is ignored.
In port mirroring mode, the SERVICE port acts like a read-only port. That is, you cannot access
devices (ping, connection to Control Expert, etc.) through the SERVICE port.
Services
The Service Port Control object performs these services for these object types:
Section 5.8
DTM Device Lists
Introduction
This section describes the connection of an M580 CPU to other network nodes through the Control
Expert DTM Browser.
Introduction
The Device List contains read-only properties that summarize these items:
configuration data:
input data image
output data image
maximum and actual numbers of devices, connections, and packets
Step Action
1 Open your Control Expert project.
2 Open the DTM Browser (Tools → DTM Browser).
3 Double-click the CPU DTM in the DTM Browser to open the configuration window.
NOTE: You can also right-click the CPU DTM and select Open.
4 Select Device List in the navigation tree.
Expand (+) the Input row to view the Input Current Size values:
Description Source
This value is the sum of Modbus requests and This value is configured in the General page for a
EtherNet/IP connection sizes. selected distributed device and connection.
Expand (+) the Output row to view the Output Current Size values:
Description Source
This value is the sum of Modbus requests and This value is configured in the General page for a
EtherNet/IP connection sizes. selected distributed device and connection.
The maximum size of the X Bus input or output memory variable is 4 KB (2048 words). The variable
contains a 16-byte descriptor followed by a value that represents the number of input or output data
objects. Each data object contains a 3-byte object header followed by the input or output data. The
number of data objects and the size of the input or output data depend on the configuration. The
maximum overhead in the variable is 403 bytes (16 + 387), where 16 is the number of bytes in the
descriptor and 387 is the product of 3 x 129, where 3 is the number of bytes in the header and 129
is the number of input or output objects (128 maximum scanned devices or local slaves that the
BMENOC03•1 module supports plus one input or output object for the scanner DDDT). Therefore,
at least 3.6 KB of the 4-KB variable is available for the input or output current size.
NOTE: The input current size also includes 28 words of scanner DDT input data. The output
current size also includes 24 words of scanner DDT output data.
Expand (+) the Configuration Size row in the Connection Summary table to view these values:
Column Description
Connection Bit Connection health bits display the status of each device with one or more
connections.
Connection control bits can be toggled on and off using object IDs.
Address The target device IP address for remote devices (does not apply to local slaves).
Rate (msec) The RPI (for EtherNet/IP) or the repetitive rate (for Modbus TCP), in ms.
Input Packets per The number of input (T->O) packets per second exchanged over this connection.
Second
Output Packets per The number of output (O->T) packets per second exchanged over this connection.
Second
Packets per Second The total number of packets per second exchanged over this connection in both
Input and output directions.
Bandwidth Usage The total bandwidth used by this connection (total bytes per second traffic).
Size In The number of input words configured for this remote device.
Size Out The number of output words configured for this remote device.
NOTE: The numeric identifiers in the Input Object and Output Object columns represent the
objects associated with a single device connection (scan line). For example, if an EtherNet/IP
connection has an input object of 260 and an output object of 261, the corresponding control bits
for this connection are in the DIO_CTRL field in the M580 CPU device DDT. Object 260 is the fifth
bit and object 261 is the sixth bit in this field. There can be multiple connections for a device. Set
the corresponding bits to control the input and output objects for these connections.
Introduction
Configure parameters for devices in the Device List on these tabs:
Properties
Address Setting
Request Setting (Modbus devices only)
Step Action
1 In the DTM Browser (Tools → DTM Browser), double-click the DTM that corresponds to the
CPU.
2 In the navigation pane, expand (+) the Device List (see page 208) to see the associated Modbus
TCP and EtherNet/IP devices.
3 Select a device from the Device List to view the Properties, Address Setting, and Request
Setting tabs tabs.
NOTE: These tabs are described in detail below.
Properties Tab
Configure the Properties tab to perform these tasks:
Add the device to the configuration.
Remove the device from the configuration.
Edit the base name for variables and data structures used by the device.
Indicate how input and output items are created and edited.
Click Apply to save your edits and leave the window open for further edits.
NOTE: When the DHCP client software is enabled in a Modbus device, it obtains its IP address
from the DHCP server in the CPU.
In the Address Setting page, edit these parameters to conform to your application’s design and
functionality:
Click Apply to save your edits, and leave the window open for further edits.
Step Action
1 Press the Add Request button to see a new request in the table.
Press the Add Request button:
The new request appears in the table.
The corresponding request items appear in the Device List.
NOTE: The Add Request function is enabled only when Import Mode on the Properties tab is
set to Manual.
2 Configure the request settings according to the table below.
3 Repeat these steps to create additional requests.
4 Press the Apply to save the request.
This table describes the Request Settings parameters for Modbus devices:
Setting Description
Connection Bit This bit indicates the read-only offset for the health bit for this connection. Offset values
(starting at 0) are auto-generated by the Control Expert DTM based on the connection type.
Unit ID The Unit ID is the number used to identify the target of the connection.
NOTE: Consult the manufacturer’s user manual for the specific target device to find its
Unit ID.
Health Time Out This value represents the maximum allowed interval between device responses before a
(ms) time out is detected:
valid range: 5 ... 65535 ms
interval: 5 ms
default: 1500 ms
Repetitive Rate This value represents the data scan rate in intervals of 5 ms. (The valid range is 0...60000
(ms) ms. The default is 60 ms.)
RD Address This is the address of the input data image in the Modbus device.
RD Length This value represents the number of words (0...125) in the Modbus device that the CPU
reads.
Last Value This value represents the behavior of input data in the application if communications are
lost:
Hold Value (default)
Set To Zero
WR Address This is the address of the output data image in the Modbus device.
WR Length This value represents the number of words (0...120) in the Modbus device to which the
CPU writes.
Remove a request:
Step Action
1 Click a row in the table.
2 Press the Remove button to remove the request.
NOTE: The corresponding request items disappear from the Device List.
3 Press the Apply to save the configuration.
The next step is to connect the Control Expert project to the Modbus device.
Introduction
This topic describes the Control Expert Device DDT tab for an M580 CPU in a local rack. A derived
data type (DDT) is a set of elements with the same type (ARRAY) or with different types (structure).
NOTE: The device DDT type supported by a standalone M580 CPU depends on its firmware
version, and can be either T_BMEP58_ECPU or T_BMEP58_ECPU_EXT.
You can add this variable to an Animation Table (see page 242) to read the status and set the
object control bit.
NOTE: The red arrow and lock icons in the Device DDT table indicate that the variable name was
auto-generated by Control Expert based on the configuration of the communication module, local
slave, or distributed device. The variable name cannot be edited.
Name Description
Freshness This is a global bit:
1: All input objects below (Freshness_1, Freshness_2, etc.) for the associated device
are true (1) and provide up-to-date data.
0: One or more inputs (below) is not connected and does not provide up-to-date data.
Freshness_1 This bit represents individual input objects for the connection:
1: The input object is connected and provides up-to-date data.
0: The input object is not connected and does not provide up-to-date data.
Freshness_2 This bit represents an individual input object for the device:
1: The input object is true (1) and provides up-to-date data.
Freshness_3
0: The input object is not connected (0) and does not provide up-to-date data.
...
Name Description
(available) The rows after the Freshness data are organized in groups of Inputs and Outputs that
have user-defined names. The number of input and output rows depends on the number
of input and output requests configured for a particular device.
Parameters
Use the Control Expert Device DDT tab to configure parameters for the CPU RIO head on the local
rack:
Parameter Description
Implicit device DDT Name the default name of the device DDT
Type module type (uneditable)
Goto details link to the DDT data editor screen
Standalone Configuration
These tables describe the fields in the BMEP58_ECPU_EXT implicit device DDT type that is used
with the CPU RIO communication server in standalone configurations using Unity Pro 10.0 or later
and M580 CPU version 2.01 or later.
NOTE: Unity Pro is the former name of Control Expert for version 13.1 or earlier.
Input Parameters
The following tables describe the input parameters in the device DDT for the CPU.
ETH_STATUS (WORD):
NOTICE
UNEXPECTED EQUIPMENT BEHAVIOR
Confirm that each module has a unique IP address. Duplicate IP addresses can cause
unpredictable module/network behavior.
Failure to follow these instructions can result in equipment damage.
SERVICE_STATUS (WORD):
SERVICE_STATUS2 (WORD):
ETH_PORT_1_2_STATUS (BYTE):
ETH_PORT_3_BKP_STATUS (BYTE):
FDR_USAGE:
IN_PACKETS (UINT):
IN_ERRORS (UINT):
OUT_PACKETS (UINT):
OUT_ERRORS (UINT):
CONF_SIG (UDINT):
Output Parameters
Although the complete Hot Standby Device DDT is not exchanged from the primary CPU to the
standby CPU, these fields are transferred: DROP_CTRL; RIO_CTRL; DIO_CTRL
These tables describe those output parameters:
DROP_CTRL:
RIO_CTRL:
DIO_CTRL:
Values:
1 (true): A device is healthy. The input data from the device is received within the pre-configured
health timeout.
0 (false): A device is not healthy. The input data from the device is not received within the pre-
configured health timeout.
Introduction
The T_M_ECPU_HSBY DDT is the exclusive interface between the M580 Hot Standby system and
the application running in a BMEH58•040 or BMEH58•040S CPU. The DDT instance should
appear as: ECPU_HSBY_1.
NOTICE
RISK OF UNINTENDED OPERATION
Review and manage the T_M_ECPU_HSBY DDT for proper operation of the system.
Failure to follow these instructions can result in equipment damage.
T_M_ECPU_HSBY DDT
CAUTION
RISK OF UNINTENDED OPERATION
Before you execute a swap command (either by application logic or in the Control Expert GUI)
confirm that the standby PAC is ready to assume the primary role by verifying that the value of
its REMOTE_HSBY_STS.EIO_ERROR bit is 0.
Failure to follow these instructions can result in injury or equipment damage.
OFFLINE_BUILD_MISMATCH BOOL The two PACs are running different revisions of System
the same application.In this condition:
A data exchange between the two PACs may
not be possible.
A swap or switchover may not be bumpless.
Neither PAC can be standby
(Default = false)
WAIT BOOL True: The PAC is in Run state but waiting to go System
primary or standby.
False: The PAC is in standby, primary or stop state.
PLC_A BOOL True: the PAC A/B/Clear switch (see page 46) is in System
“A” position.
False: the PAC switch is not in “A” position.
PLC_B BOOL True: the PAC A/B/Clear switch (see page 46) is in System
“B” position.
False: the PAC switch is not in “B” position.
EIO_ERROR BOOL True: The PAC does not detect any of the System
configured Ethernet RIO drops.
False: The PAC detects at least one configured
Ethernet RIO drop.
NOTE: This bit is always false when no drop is
configured.
SD_CARD_PRESENT BOOL True: A valid SD card is inserted. System
False: No SD card, or an invalid SD card is
inserted.
LOCAL_RACK_STS BOOL] True: The local rack configuration is OK. Application
False: The local rack configuration is not OK (for
example, modules missing or in incorrect slots,
etc.)
MAST_TASK_STATE BYTE State of the MAST task: System
0: Not existent
1: Stop
2: Run
3: Breakpoint
4: Halt
REGISTER WORD[0...63] Unmanaged data added to the application via the Application
Exchange on STBY attribute.
Section 5.9
Explicit Messaging
Explicit Messaging
Introduction
You can configure EtherNet/IP and Modbus TCP explicit messages for the M580 CPU in the
following ways:
Connect the CPU to a Control Expert project (see Modicon M580 Standalone, System Planning
Guide for, Frequently Used Architectures).
Use the DATA_EXCH function block in application logic to transmit EtherNet/IP or Modbus TCP
explicit messages.
Use a WRITE_VAR or a READ_VAR function block to exchange Modbus TCP explicit
messages, for example, service data objects (SDOs).
NOTE: A single Control Expert application can contain more than 16 explicit messaging blocks, but
only 16 explicit messaging blocks can be active at the same time.
Overview
Use the DATA_EXCH function block to configure both Modbus TCP explicit messages and
connected and unconnected EtherNet/IP explicit messages.
The Management_Param, the Data_to_Send, and the Received_Data parameters define the
operation.
EN and ENO can be configured as additional parameters.
FBD Representation
Input Parameters
Input/Output Parameters
The Management_Param array is local:
Do not copy this array during a switchover from a primary to a standby CPU in a Hot Standby
system. Uncheck the Exchange On STBY variable in Control Expert when you configure a Hot
Standby system.
NOTE: Refer to the description of Hot Standby system data management and the
T_M_ECPU_HSBY DDT (see Modicon M580 Hot Standby, System Planning Guide for, Frequently
Used Architectures) in the M580 Hot Standby System Planning Guide (see Modicon M580 Hot
Standby, System Planning Guide for, Frequently Used Architectures).
Output Parameters
Introduction
The structure and content of the management parameter of the DATA_EXCH block is common to
both EtherNet/IP and Modbus TCP explicit messaging.
Activity Bit
The activity bit is the first bit of the first element in the table. The value of this bit indicates the
execution status of the communication function:
1: The bit is set to 1 when the function launches.
0: The bit returns to 0 upon the completion of the execution. (The transition from 1 to 0
increments the exchange number. If an error is detected during the execution, search for the
corresponding code in the operation and communication report (see Modicon M580
Standalone, System Planning Guide for, Frequently Used Architectures).)
For example, you can make this declaration in the management table:
Management_Param[0] ARRAY [0..3] OF INT
Overview
Every explicit message performs a service. Each service is associated with a service code. Identify
the explicit messaging service by its name, decimal number, or hexadecimal number.
You can execute explicit messages using the DATA_EXCH function block in the Control Expert
DTM.
Services
The services available in Control Expert include, but are not limited to, these service codes:
Overview
The following unconnected explicit messaging example shows you how to use the DATA_EXCH
function block to retrieve diagnostic data from a remote device (at IP address 192.168.1.6). This
example is executing a Get_Attribute_Single of assembly instance 100, attribute 3.
You can perform the same explicit messaging service using the EtherNet/IP Explicit Message
window (see Modicon M580, BMENOC0301/0311 Ethernet Communications Module, Installation
and Configuration Guide).
Step Action
1 In Control Expert, select Tools → Project Browser to open the Project Browser.
2 In the Project Browser, select the Animation Tables folder, then click the right mouse button. A pop-
up menu appears.
3 Select New Animation Table in the pop-up menu. A new animation table and its properties dialog
both open.
4 In the Properties dialog, edit the following values:
Name Type in a table name. For this example: ReceivedData.
Functional module Accept the default <None>.
Comment (Optional) Type your comment here.
Number of animated Type in 100, representing the size of the data buffer in words.
characters
5 Click OK to close the dialog.
6 In the animation table’s Name column, type the name of the variable assigned to the RECP pin:
ReceivedData and press Enter. The animation table displays the ReceivedData variable.
7 Expand the ReceivedData variable to display its word array, where you can view the CIP response
contained in the ReceivedData variable.
NOTE: Each array entry presents 2 bytes of data in little endian format, where the least significant
byte is stored in the smallest memory address. For example, ‘8E’ in word[0] is the lower byte, and
‘00’ is the upper byte.
Overview
The following unconnected explicit messaging example shows you how to use the DATA_EXCH
function block to read data from a remote device (for example, the STB NIP 2212 network interface
module at IP address 192.168.1.6) using the Read_Holding_Registers service of the Modbus
Object.
You can perform the same explicit messaging service using the EtherNet/IP Explicit Message
window (see Modicon M580, BMENOC0301/0311 Ethernet Communications Module, Installation
and Configuration Guide).
Declaring Variables
In this example, the following variables were defined. You can, of course, use different variable
names in your explicit messaging configurations.
Step Action
1 In Control Expert, select Tools → Project Browser to open the Project Browser.
2 In the Project Browser, select the Animation Tables folder, then click the right mouse button. A
pop-up menu appears.
3 Select New Animation Table in the pop-up menu. A new animation table and its properties dialog
both open.
4 In the Properties dialog, edit the following values:
Name Type in a table name. For this example: ReceivedData.
Functional module Accept the default <None>.
Comment (Optional) Type your comment here.
Number of animated Type in 49, representing the size of the data buffer in words.
characters
Step Action
5 The completed Properties dialog looks like this:
Note: Each array entry presents 2 bytes of data in little endian format, where the least significant
byte is stored in the smallest memory address. For example, ‘CE’ in word[0] is the lower byte, and
‘00’ is the upper byte.
Overview
The following unconnected explicit messaging example shows you how to use the DATA_EXCH
function block to write data to a remote device at IP address 192.168.1.6 using the Write_Hold-
ing_Registers service of the Modbus object.
You can perform the same explicit messaging service using the EtherNet/IP Explicit Message
window (see Modicon M580, BMENOC0301/0311 Ethernet Communications Module, Installation
and Configuration Guide) in the Control Expert DTM.
Declaring Variables
In this example, the following variables were defined. You can, of course, use different variable
names in your explicit messaging configurations.
Step Action
1 In Control Expert, select Tools → Project Browser to open the Project Browser.
2 In the Project Browser, select the Animation Tables folder, then click the right mouse button. A pop-
up menu appears.
3 Select New Animation Table in the pop-up menu. A new animation table and its properties dialog
both open.
4 In the Properties dialog, edit the following values:
Name Type in a table name. For this example: ReceivedData.
Functional module Accept the default <None>.
Comment (Optional) Type your comment here.
Number of animated Type in 49, representing the size of the data buffer in words.
characters
Step Action
5 The completed Properties dialog looks like this:
Note: Each array entry presents 2 bytes of data in little endian format, where the least significant
byte is stored in the smallest memory address. For example, ‘D0’ in word[0] is the lower byte, and
‘00’ is the upper byte.
Overview
You can execute Modbus TCP explicit messages using either a Control Expert DATA_EXCH
function block or the Modbus Explicit Message Window.
NOTE: Configuration edits made to an Ethernet module are not saved to the operating parameters
stored in the CPU and, therefore, are not sent by the CPU to the module on startup.
Function Codes
The function codes supported by the Control Expert graphical user interface include the following
standard explicit messaging functions:
NOTE: You can use the DATA_EXCH function block to execute any Modbus function, via program
logic. Because the available function codes are too numerous to list here, refer instead to the
Modbus IDA website for more information about these Modbus functions, at
http://www.Modbus.org.
Introduction
When you use the DATA_EXCH block to create an explicit message for a Modbus TCP device,
configure this block the same way you would configure it for any other Modbus communication.
Refer to the Control Expert online help for instructions on how to configure the DATA_EXCH block.
The Unit ID value in a Modbus message indicates the destination of the message.
Refer to the Modbus diagnostic codes.
NOTE:
Structure the response in little endian order.
In some cases of detected errors, Received_Data is also used to judge the type of detected error
along with Management_Param.
Introduction
Use the DATA_EXCH function block to send a Modbus TCP explicit message to a remote device at
a specific IP address to read a single word located in the remote device.
The Management_Param, the Data_to_Send, and the Received_Data parameters define the
operation.
EN and ENO can be configured as additional parameters.
DataToSend[1] High byte = Most significant byte (MSB) of the number of registers to 16#000F
read: 16#00 (0 decimal)
Low byte = Least significant byte (LSB) of register address: 16#0F (15
decimal)
DataToSend[2] CIP request instance information: 16#0001
High byte = not used: 16#00 (0 decimal)
Low byte = Least significant byte (LSB) of the number of registers to
read: 16#01 (1 decimal)
NOTE: For detailed information about M580 network topologies, refer to the Modicon M580
Standalone System Planning Guide for Frequently Used Architectures and Modicon M580 System
Planning Guide for Complex Topologies.
Step Action
1 In Control Expert, select Tools → Project Browser.
2 In the Project Browser, select the Animation Tables folder, and click the right mouse button.
Result: A pop-up menu appears.
3 Select New Animation Table in the pop-up menu.
Result: A new animation table and its properties dialog open.
4 In the Properties dialog, edit the following values:
Name Type in a table name. For this example: ReceivedData.
Functional module Accept the default <None>.
Comment (Optional) Type your comment here.
Number of animated Type in 100, representing the size of the data buffer in words.
characters
5 Click OK to close the dialog.
6 In the animation table’s Name column, type in the name of the variable assigned to the databuffer:
ReceivedData and press Enter.
Result: The animation table displays the ReceivedData variable.
7 Expand the ReceivedData variable to display its word array, where you can view the CIP response
contained in the ReceivedData variable.
NOTE: Each array entry presents 2 bytes of data in little endian format. For example, ‘03’ in word[0]
is the low byte, and ‘02’ is the high byte.
Introduction
Use the EtherNet/IP Explicit Message window to send an explicit message from Control Expert to
the M580 CPU.
An explicit message can be connected or unconnected:
connected: A connected explicit message contains both path information and a connection
identifier to the target device.
unconnected: An unconnected message requires path (addressing) information that identifies
the destination device (and, optionally, device attributes).
You can use explicit messaging to perform many different services. Not every EtherNet/IP device
supports every service.
Step Action
1 Open the DTM Browser in Control Expert (Tools → DTM Browser).
2 Select the M580 DTM in the DTM Browser.
3 Right-click the M580 DTM.
4 Scroll to the EtherNet/IP explicit messaging page (Device menu → Additional functions →
EtherNet/IP Explicit Message).
Configuring Settings
Configure the explicit message using these settings on the EtherNet/IP Explicit Messaging page:
Field Setting
Address IP Address: The IP address of the target device that is used to identify the target of the
explicit message.
Class: The Class integer (1 ... 65535) is the identifier of the target device that is used in the
construction of the message path.
Instance: The Instance integer (0 ... 65535) is the class instance of the target device that
is used in the construction of the message path.
Attribute: Check this box to enable the Attribute integer (0 ... 65535), which is the specific
device property that is the target of the explicit message that is used in the construction of
the message path.
Service Number: The Number is the integer (1 ... 127) associated with the service to be performed
by the explicit message.
NOTE: If you select Custom Service as the named service, type in a service number. This
field is read-only for all other services.
Name: Select the service that the explicit message is intended to perform.
Enter Path(hex): Check this box to enable the message path field, where you can manually
enter the entire path to the target device.
Data(hex) Data(hex): This value represents the data to be sent to the target device for services that
send data.
Messaging Connected: Select this radial button to make the connection.
Unconnected: Select this radial button to end the connection.
Response(hex) The Response area contains the data sent to the configuration tool by the target device in
hexadecimal format.
Status The Status area displays messages that indicate whether or not the explicit message has
succeeded.
Button Send to Device: When your explicit message is configured, click Send to Device.
Click the Close button to save the changes and close the window.
Introduction
Use the Modbus explicit messaging window to send an explicit message from Control Expert to the
M580 CPU.
You can use explicit messaging to perform many different services. Not every Modbus TCP device
supports every service.
Step Action
1 Open the DTM Browser in Control Expert (Tools → DTM Browser).
2 Select the M580 DTM in the DTM Browser.
3 Right-click the M580 DTM.
4 Scroll to the EtherNet/IP explicit messaging page (Device menu → Additional functions →
Modbus Explicit Message).
Configuring Settings
Configure the explicit message using these settings on the Modbus Explicit Messaging page:
Field Setting
Address IP Address: The IP address of the target device that is used to identify the target of the
explicit message.
Start Address: This setting is a component of the addressing path.
Quantity: This setting is a component of the addressing path.
Read Device Id Code: This read-only code represents the service that the explicit message
is intended to perform.
Object Id: This read-only identifier specifies the object that the explicit message is intended
to access.
Unit Id: This integer represents the device or module that is the target of the connection:
255: (default): Use this value to access the M580 CPU itself.
0 ... 254: Use these values to identify the device number of the target device behind a
Modbus TCP to Modbus gateway.
Service Number: This integer (0 ... 255) represents the service to be performed by the explicit
message.
Name: Select the integer (0 ... 255) that represents the service that the explicit message is
intended to perform.
Data Data(hex): This value represents the data to be sent to the target device for services that
send data.
Field Setting
Response The Response area displays any data sent to the configuration tool by the target device in
hexadecimal format.
Status The Status area displays messages indicating whether or not the explicit message has
succeeded.
Button Send to Device: After your explicit message is configured, click Send to Device.
Click the Close button to save the changes and close the window.
Section 5.10
Explicit Messaging Using the MBP_MSTR Block in Quantum RIO Drops
Introduction
This section shows you how to configure both EtherNet/IP and Modbus TCP explicit messages in
Quantum RIO drops by including the MBP_MSTR function block in the logic of your Control Expert
project.
Overview
You can use the MBP_MSTR function block to configure both Modbus TCP and EtherNet/IP
connected and unconnected explicit messages.
The operation begins when the input to the EN pin is turned ON. The operation ends if the ABORT
pin is turned ON, or if the EN pin is turned OFF.
The CONTROL and DATABUF output parameters define the operation.
NOTE: The structure and content of the CONTROL and DATABUF output parameters differ for
explicit messages configured using the EtherNet/IP and Modbus TCP protocols. Refer to the topics
Configuring the Control Parameter for EtherNet/IP and Configuring the Control Parameter for
Modbus TCP for instructions on how to configure these parameters for each protocol.
The ACTIVE output turns ON during operation; the ERROR output turns ON if the operation aborts
without success; the SUCCESS output turns ON at the successful completion of the operation.
EN and ENO can be configured as additional parameters.
Representation in FBD
Input Parameters
Output Parameters
CONTROL1 WORD This parameter contains the control block. The first
element contains a code describing the operation to be
performed. The content of the control block depends on
the operation. The structure of the control block depends
on the protocol (EtherNet/IP or Modbus TCP).
Note: Assign this parameter to a located variable.
DATABUF1 WORD This parameter contains the data buffer. For operations
that:
provide data — e.g., a write operation — this
parameter is the data source
receive data — e.g., a read operation — this
parameter is the data destination
Note: Assign this parameter to a located variable.
1. Refer to the topics Configuring the Control Block for EtherNet/IP and Configuring the
Control Block for Modbus TCP for instructions on how to configure these parameters for the
EtherNet/IP and Modbus TCP communication protocols.
Overview
Every EtherNet/IP explicit message performs a service. Each service is associated with a service
code (or number). You will need to identify the explicit messaging service by its name, decimal
number, or hexadecimal number.
You can execute EtherNet/IP explicit messages using either a Control Expert MBP_MSTR function
block or the Control Expert Ethernet Configuration Tool’s EtherNet/IP Explicit Message Window.
NOTE: Configuration edits made to an Ethernet communication module from the Control Expert
Ethernet Configuration Tool’s EtherNet/IP Explicit Message Window are not saved to the operating
parameters stored in the CPU and, therefore, are not sent by the CPU to the module on startup.
You can use Control Expert to construct a request that executes any service supported by the
target device that is compliant with the EtherNet/IP protocol.
Services
The services supported by Control Expert include the following standard explicit messaging
services:
Overview
The CONTROL and DATABUF output parameters define the operation performed by the MBP_MSTR
function block. For the EtherNet/IP protocol, the structure of the CONTROL and DATABUF output
parameters remains the same for every explicit messaging service (see page 264).
CONTROL[1] Detected error Holds the event code (see Modicon M580
status Standalone, System Planning Guide for,
Frequently Used Architectures) (read-only).
CONTROL[2] Data buffer length Data buffer length, in words
CONTROL[3] Response offset Offset for the beginning of the response in the
data buffer, in 16-bit words
Note: To avoid overwriting the request, confirm
that the response offset value is greater than the
request length CONTROL[7].
CONTROL[4] Slot High byte = slot location on backplane
Low byte = 0 (not used)
CIP Request:
Request size: set in CONTROL[7]
Data Buffer:
CIP Response:
Variable size: set in CONTROL[2]
Starting position: set in CONTROL[3]
Response size: reported in CONTROL[8]
NOTE: If the response offset is smaller than the
request size, the response data overwrites part of
the request.
The format of the data buffer’s CIP request and CIP response is described, below.
NOTE: Structure both the request and response in little endian order.
Request:
Response:
Overview
The following unconnected explicit messaging example shows you how to use the MBP_MSTR
function block to retrieve diagnostic information for an STB island from an STB NIC 2212 network
interface module, by using the Get_Attributes_Single service.
You can perform the same explicit messaging service using the EtherNet/IP Explicit Message
Window of the Control Expert Ethernet Configuration Tool (see Quantum EIO, Control Network,
Installation and Configuration Guide).
Input Variables
Variables need to be created and assigned to input pins. For the purpose of this example, variables
have been created — and named — as described below. (You can use different variable names in
your explicit messaging configurations.)
Output Variables
Variables also need to be created and assigned to output pins. (The names assigned to output
variables apply only to this example, and can be changed in your explicit messaging
configurations.)
NOTE: To simplify configuration, you can assign the CONTROL and DATABUF output pins to a byte
array consisting of located variables. When configured in this manner, you will not need to be
aware of the location of data within a word (for example, high versus low byte, and big or little
endian format).
Control Array
The control array parameter (EIP_ControlBuf) consists of 9 contiguous words. You need to
configure only some control words; other control words are read-only and are written to by the
operation. In this example, the control array defines the operation as an unconnected explicit
message, and identifies the target device:
CIP Request
The CIP request is located at the beginning of the databuffer and is followed by the CIP response.
In this example, the CIP request calls for the return of a single attribute value (diagnostic data), and
describes the request path through the target device’s object structure leading to the target
attribute:
Combining the high and low bytes, above, the CIP request would look like this:
Step Action
1 In Control Expert, select Tools → Project Browser to open the Project Browser.
2 In the Project Browser, right-click Animation Tables → New Animation Table.
Result: A new animation table opens.
3 In the New Animation Table dialog, edit the following values:
Name Type in a table name. For this example: EIP_DataBuf.
Functional Mode Accept the default <None>.
Comment Leave blank.
Number of animated Type 100, representing the size of the data buffer in words.
characters
4 The completed dialog looks like this:
Step Action
5 In the animation table’s Name column, type in the name of the variable assigned to
the databuffer: EIP_DataBuf and press Enter. The animation table displays the
EIP_DataBuf variable.
6 Expand the EIP_DataBuf variable to display its word array, where you can view the
CIP response at words EIP_DataBuf(7-16):
Note: Each word presents 2 bytes of data in little endian format, where the least
significant byte is stored in the smallest memory address. For example, ‘0E’ in
EIP_DataBuf[0] is the low byte, and ‘03’ is the high byte.
Overview
Every Modbus TCP explicit message performs a function. Each function is associated with a code
(or number). You will need to identify the explicit messaging function by its name, decimal number,
or hexadecimal number.
You can execute Modbus TCP explicit messages using either a Control Expert MBP_MSTR function
block or the Control Expert Ethernet Configuration Tool’s Modbus Explicit Message Window.
NOTE: Configuration edits made to an Ethernet communication module from the Control Expert
Ethernet Configuration Tool are not saved to the operating parameters stored in the CPU and,
therefore, are not sent by the CPU to the module on startup.
Services
The function codes supported by Control Expert include the following standard explicit messaging
functions:
Overview
The CONTROL and DATABUF output parameters define the operation performed by the MBP_MSTR
(see page 262) function block. For the Modbus TCP protocol, both the structure and the content of
the CONTROL output parameter vary, depending upon the function code (see page 274).
The structure of the CONTROL parameter is described, below, for each supported function code.
Refer to the Quantum Ethernet I/O System Planning Guide for an example of an MSTR block
created in a Control Expert application to read the ports of a dual-ring switch (DRS) to diagnose a
sub-ring break.
When the Ethernet communication module acts as a server, the LSB indicates the destination of a
message received by the communication module:
messages with an LSB value from 0 to 254 are forwarded to and processed by the CPU
messages with an LSB value of 255 are retained and processed by the Ethernet communication
module
NOTE: Unit ID 255 should be used when requesting diagnostic data from the Ethernet
communication module.
Write Data
The control parameter consists of 9 contiguous words, as described below:
1. For example, the control parameter handles the IP address 192.168.1.7 in the following order: Byte 4 =
192, Byte 3 = 168, Byte 2 = 1, Byte 1 = 7.
Read Data
The control parameter consists of 9 contiguous words, as described below:
1. For example, the control parameter handles the IP address 192.168.1.7 in the following order: Byte 4 =
192, Byte 3 = 168, Byte 2 = 1, Byte 1 = 7.
Module Response: A TCP/IP Ethernet module responds to the Get Local Statistics
command with the following information:
Word Description
00...02 MAC Address
03 Board Status — this word contains the following bits:
Bit 15 0 = Link LED off; Bit 3 Reserved
1 = Link LED ON
Bits 14...13 Reserved Bit 2 0 = half duplex; 1 = full duplex
Bit 12 0 = 10 Mbit; Bit 1 0 = not configured; 1 = configured
1 = 100 Mbit
Bits 11...9 Reserved Bit 0 0 = PLC not running;
1 = PLC or NOC running
Bits 8...4 Module Type — this bit presents the following values:
0 = NOE 2x1 11 = 140 NOE 771 01
1 = ENT 12 = 140 NOE 771 11
2 = M1E 13 = (reserved)
3 = NOE 771 00 14 = 140 NOC 78• 00
4 = ETY 15...16 = (reserved)
5 = CIP 17 = M340 CPU
6 = (reserved) 18 = M340 NOE
7 = 140 CPU 651 x0 19 = BMX NOC 0401
8 = 140 CRP 312 00 20 = TSX ETC 101
9 = (reserved) 21 = 140 NOC 771 01
10 = 140 NOE 771 10
04 and 05 Number of receiver interrupts
06 and 07 Number of transmitter interrupts
08 and 09 Transmit_timeout detected error count
10 and 11 Collision_detect error count
12 and 13 Missed packets
14 and 15 (reserved)
16 and 17 Number of times driver has restarted
18 and 19 Receive framing detected error
20 and 21 Receiver overflow detected error
22 and 23 Receive CRC detected error
24 and 25 Receive buffer detected error
26 and 27 Transmit buffer detected error
28 and 29 Transmit silo underflow
30 and 31 Late collision
32 and 33 Lost carrier
34 and 35 Number of retries
36 and 37 IP address
1. For example, the control parameter handles the IP address 192.168.1.7 in the following order: Byte 4 =
192, Byte 3 = 168, Byte 2 = 1, Byte 1 = 7.
1. For example, the control parameter handles the IP address 192.168.1.7 in the following order: Byte 4 =
192, Byte 3 = 168, Byte 2 = 1, Byte 1 = 7.
Reset Module
The control parameter consists of 9 contiguous words, as described below:
Read/Write Data
The control parameter consists of 11 contiguous words, as described below:
HTTP, FTP, and TFTP service state changes made by MSTR with operation code FFF0 (hex) are
overridden by the configured value when the module is power-cycled or reset and when a new
application is downloaded to the module.
Here are some examples:
Section 5.11
Implicit Messaging
Implicit Messaging
Introduction
This section extends the sample Control Expert application and contains these instructions:
Add an STB NIC 2212 EtherNet/IP network interface module to your Control Expert application.
Configure the STB NIC 2212 module.
Configure EtherNet/IP connections to link the Ethernet communications module and the
STB NIC 2212 network interface module.
Configure I/O items for the Advantys island.
NOTE: The instructions in this section describe an example of a single, specific device
configuration. For other configuration choices, refer to the Control Expert help files.
Introduction
Use this example to establish communications between the M580 rack and an Advantys
STB NIC 2212 network interface module (NIM).
The STB NIC 2212 is Schneider Electric’s EtherNet/IP network interface module for Advantys
islands.
Network Topology
This sample network shows the Ethernet network devices used in this configuration:
1 The M580 CPU (with DIO scanner service) on the local rack is connected to a PC that runs the Control
Expert software.
2 The BMENOC0301/11 Ethernet communications module on the local rack is connected to an
STB NIC 2212 NIM on an Advantys island.
To re-create this example, use the IP addresses from your own configuration for these items:
M580 CPU
PC
BMENOC0301/11 Ethernet communication module
STB NIC 2212 network interface module
Overview
You can use the Control Expert device library to add a remote device—in this example the
STB NIC 2212 module—to your project. Only a remote device that is part of your Control Expert
device library can be added to your project.
Alternatively, with a remote device already added to your device library, you can use automatic
device discovery to populate your project. Perform automatic device discovery by using the Field
bus discovery command with a communication module selected in the DTM Browser.
Step Action
1 In the DTM Browser, right-click the DTM that corresponds to the Ethernet communication module.
2 Scroll to Add.
3 Select STBNIC2212 (from EDS):
NOTE: Click a column name to sort the list of available devices. (For example, click Device to view
the items in the first column in alphabetical order.)
4 Click the Add DTM button to see the association between the Ethernet communication module and
the STB NIC 2212 in the DTM Browser.
5 In the DTM Browser, right-click the STB NIC 2212 node that is associated with the Ethernet
communication module DTM.
6 Scroll to Properties.
Step Action
7 On the General tab, create a unique Alias name. (Using similar devices that use the same DTM can
result in duplicate module names.) In this example, type in the name NIC2212_01:
Control Expert uses the Alias name as the base for both structure and variable names.
NOTE: The Alias name is the only editable parameter on this tab. The other parameters are read-
only.
8 Click OK to add the STB NIC 2212 network interface module to the DTM Browser, beneath the
communication module.
The next step is to configure the device you have just added to the project.
Introduction
Use Control Expert to edit the settings for STB NIC 2212 device.
NOTE: To edit these settings, disconnect the DTM from a device.
Step Action
1 Double-click the DTM that corresponds to the BMENOC0301/11 module to access the
configuration.
2 In the navigation tree, expand the Device List (see page 209) to see the associated local slave
instances.
3 Select the device that corresponds to the name NIC2212_01.
4 Select the Properties tab.
Properties
Configure the Properties tab to perform these tasks:
Add the STB NIC 2212 to the configuration.
Remove the STB NIC 2212 from the configuration.
Edit the base name for variables and data structures used by the STB NIC 2212.
Indicate how input and output items are created and edited.
Click Apply to save your edits and leave the window open.
Address Setting
Use the Address Setting tab to enable the DHCP client in the STB NIC 2212 network interface
module. When the DHCP client is enabled in the remote device, it obtains its IP address from the
DHCP server in the Ethernet communication module.
Configure the Address Setting page to perform these tasks:
Configure the IP address for a device.
Enable or disable DHCP client software for a device.
The descriptions for parameters in the Address Setting tab are described in the configuration
chapter. Use these values and names from the sample configuration:
Field Parameter Description
Change IP Address In our continuing example, type in the address 192.168.1.6.
Address
Address DHCP for this Select Enabled.
Server Device
Identified by Select Device Name.
Identifier Accept the default setting of the STB NIC 2212 device (based on the Alias name).
Mask Accept the default value (255.255.0.0).
Gateway Configure the default value (192.168.10.1).
The next step is to configure the connection between the communication module and the remote
device.
Overview
An EtherNet/IP connection provides a communication link between 2 or more devices. Properties
for a single connection can be configured in the DTMs for the connected devices.
The following example presents settings for a connection between the CPU’s DIO scanner service
and a remote STB NIC 2212 network interface module. Configuration edits are made to the DTMs
for each device.
When making DTM edits, disconnect the selected DTM from the actual module or device
(see Modicon M580, BMENOC0301/0311 Ethernet Communications Module, Installation and
Configuration Guide).
Step Action
1 In Control Expert, double-click the DTM for the CPU’s DIO scanner service to access the
configuration.
2 In the navigation tree, expand the Device List (see Modicon M580, BMENOC0301/0311
Ethernet Communications Module, Installation and Configuration Guide) to see the associated
local slave instances.
3 Expand (+) the device that corresponds to the STB NIC 2212 module.
4 Select Read Input/ Write Output Data to see the Connection Settings and Connection
Information tabs.
Connection Settings
Control Expert automatically creates a connection between a communication module and remote
device when the remote device is added to the Control Expert project. Thereafter, many edits to
the connection can be made in the DTM for the remote device. However, some of the connection
parameters can also be configured in the DTM for the communication module, as demonstrated
below.
Edit these parameters on the Connection Settings tab. Use settings that are appropriate to your
application:
Parameter Description
Connection Bit The (read-only) offset for both the health bit and the control bit for this connection. Offset
values are auto-generated by the Control Expert DTM.
Request Packet The refresh period for this connection , from 2 to 65535 ms. Default = 12 ms. Type
Interval (RPI) 30 ms.
NOTE: This parameter can be set in the DTM for the communication module or the
remote device.
Parameter Description
Time-out Multiplier This setting, multiplied against the RPI, produces a value that triggers an inactivity
timeout. Setting selections include: x4, x8, x16, x32, x64, x128, x256 and x512.
For this example, accept the default (x4).
Input Fallback This parameter describes the behavior of inputs in the application in the event
Mode communication is lost. Select Set to Zero.
Step Action
1 Open the DTM for the remote device by selecting it in the Device Editor.
2 Open the Device Editor:
Use the main menu (Edit → Open) ... or ...
Right-click and scroll to Open.
3 In the navigation pane (on the left side of the Device Editor), confirm that the remote device
connection is of the type Read Input / Write Output Data. To view the connection type, select the
STB NIC 2212 module in the left pane of the Device Editor. If the connection type is not of the
type Read Input / Write Output Data, delete the existing connection and add a new one, as
follows:
a. With the connection selected in the left pane, click the Remove Connection button
Result:The existing connection is removed.
b. Click the Add Connection button.
Result:The Select the connection to add dialog opens.
c. Use the scroll buttons on the drop down list to display and select the Read Input / Write Output
Data connection type.
d. Click OK to close the Select the connection to add dialog.
Result:The new connection node appears.
e. Click Apply to save the new connection, leaving the Device Editor open for additional edits.
General Tab
This is the General tab of the DTM for the STB NIC 2212:
Parameter Description
RPI The refresh period for this connection. Accept the value of 30 ms. (This parameter can
be set in the DTM for the communication module or the remote device.)
Input size The number of bytes (0 ... 509) configured in the STB NIC 2212 module.
Input mode Transmission type:
Multicast
Point to Point
Parameter Description
Input priority The transmission priority value depends upon the device DTM. These are the available
values:
Low
High
Scheduled
Click Apply to save your settings and leave the window open.
Use the Check Identity parameter to set the rules that the CPU’s DIO scanner service uses to
compare the configured versus the actual remote device:
Must match exactly: The DTM or EDS file exactly matches the remote device.
Disable: No checking occurs. The identity portion of the connection is filled with zero values (the
default setting).
Must be compatible: If the remote device is not the same as defined by the DTM/EDS, it
emulates the DTM/EDS definitions.
None: No checking occurs. The identity portion of the connection is omitted.
Custom: Enable the following parameter settings, to be set individually.
Overview
The final task in this example is to add I/O items to the configuration of the STB NIC 2212 and its
eitht I/O modules:
Use the Advantys configuration software to identify the relative position of each I/O module’s
inputs and outputs.
Use the Control Expert Device Editor to create input and output items, defining each item’s:
name
data type
Step Action
1 In the Advantys configuration software, select Island → I/O Image Overview. The I/O Image
window opens to the Fieldbus Image page.
2 Select the first cell (word 1, cell 0) in the Input Data table to display (in the middle of the page)
a description of the cell data and its source module.
3 Make a note of the word, bit(s), module and item information for that cell.
4 Repeat steps 2 and 3 for each cell containing either an S or an integer.
NOTE: The Fieldbus Image presents input and output data in the form of 16-bit words (starting with
word 1). You need to rearrange this data for the Control Expert Ethernet Configuration Tool, which
presents the same data in the form of 8-bit bytes (starting with byte 0).
NOTE: When you create items, align items of data type WORD and DWORD:
WORD items: align these items on a 16-bit boundary
DWORD items: align these items on a 32-bit boundary.
This process yields the following tables of input and output data:
Input Data:
Output Data:
This example shows you how to create 19 bytes of inputs and 6 bytes of outputs. To efficiently use
space, this example creates items in the following sequence:
input bit items
input byte and word items
output bit items
output byte and word items
Step Action
1 In the DTM Browser, select the DTM for the BMENOC0301/11.
2 Do one of the following:
in the main menu, select Edit → Open.
— or —
Right-click and select Open in the pop-up menu.
Step Action
3 In the left pane of the Device Editor, navigate to and select the Items node for the STB NIC 2212
network interface module:
Step Action
7 In the Items List, select the first 2 rows in the table. (These rows represent bits 0-1 in byte.)
NOTE: The asterisk (*) indicates that a series of discrete items with the same root name will be
created.
Step Action
9 Accept the default Item Name, and click OK.
Result: 2 discrete input items are created:
10 Click Apply to save the items and leave the page open.
11 Repeat steps 6 - 10 for each group of discrete input items you need to create. In this example,
that includes items for each of the following groups:
Byte: 0, Bits: 2-3, Default Items Name Root: DDI3230_in_st
Byte: 0, Bits: 4-5, Default Items Name Root: DDO3200_out_echo
Byte: 0, Bits: 6-7, Default Items Name Root: DDO3200_out_st
Byte: 1, Bits: 0-3, Default Items Name Root: DDI3420_in_data
Byte: 1, Bits: 4-7, Default Items Name Root: DDI3420_in_st
Byte: 2, Bits: 0-3, Default Items Name Root: DDO3410_out_echo
Byte: 2, Bits: 4-7, Default Items Name Root: DDO3410_out_st
Byte: 3, Bits: 0-5, Default Items Name Root: DDI3610_in_data
Byte: 4, Bits: 0-5, Default Items Name Root: DDI3610_in_st
Byte: 5, Bits: 0-5, Default Items Name Root: DDO3600_out_echo
Byte: 6, Bits: 0-5, Default Items Name Root: DDO3600_out_st
Step Action
1 Select the Input tab to return to that page:
NOTE: In this example, both the Offset/Device and Offset/Connection columns represent the
byte address. The items you create will be either an 8-bit byte or a 16-bit word
2 In the Default Item Name Root input box type: NIC22212_01_LO_st.
3 Starting at the first available whole input word, select the single row at byte 8:
Step Action
4 Click the Define Item(s) button.
Result: The Item Name Definition dialog opens:
5 Select Byte as the New Item(s) Data Type, then click OK.
Result: A new byte item is created:
6 Click Apply to save the new items and leave the page open.
Step Action
7 Repeat steps 2 - 6 for each byte or word input item you need to create.
NOTE: The number of rows you select for a new item depends upon the item type. If the item
is a:
byte: select a single row
word: select two rows, beginning at the next available whole word
In this example, you will create items for each of the following:
Byte: 9, Default Items Name Root: NIC2212_01_HI_st
Word: 10, Default Items Name Root: AVI1270_CH1_in_data
Byte: 12, Default Items Name Root: AVI1270_CH1_in_st
Word: 14-15, Default Items Name Root: AVI1270_CH2_in_data
Byte: 16, Default Items Name Root: AVI1270_CH2_in_st
Byte: 17, Default Items Name Root: AVO1250_CH1_out_st
Byte: 18, Default Items Name Root: AVO1250_CH2_out_st
Step Action
1 Select the Output (bit) tab to open the following page:
NOTE: Both the Offset/Device and Offset/Connection columns represent the byte address of
an output, while the Position in Byte column indicates the bit position (within the byte) of each
discrete output item.
2 In the Default Items Name Root input box type: DDO3200_out_data.
Step Action
3 In the Items List, select the rows that correspond to bits 0-1 in byte 0—i.e., the first 2 rows:
NOTE: The asterisk (*) indicates that a series of discrete items with the same root name will
be created.
Step Action
5 Accept the default output name and click OK.
Result: 2 discrete output items are created:
6 Click Apply to save the new items and leave the page open.
7 Repeat steps 2 - 6 for each group of discrete output items you need to create. In this example,
that includes items for each of the following groups:
Byte: 0, Bits: 2-5, Default Items Name Root: DDO3410_out_data
Byte: 1, Bits: 0-5, Default Items Name Root: DDO3600_out_data
Step Action
1 Click on the Output tab to open the following page:
NOTE: In this example, both the Offset/Device and Offset/Connection columns represent the
byte address. The items you create will be 16-bit words comprising 2 bytes.
2 In the Default Item Name Root input box type: AVO1250_CH1_out_data.
3 Starting at the next available whole word, select 2 rows: 2 and 3:
Step Action
4 Click the Define Item(s) button.
Result: The Item Name Definition dialog opens:
6 Click Apply to save the new item and leave the page open.
7 Repeat steps 2 - 6 for the AVO 1250 channel 2 output data at bytes 4 and 5.
8 Click OK to close the Items window.
9 Select File → Save to save your edits.
Overview
The recommended RPI for EtherNet/IP implicit message connections are 1/2 of MAST cycle time.
If the resulting RPI is less than 25 ms, the implicit message connections may be adversely affected
when the diagnostic features of the CPU’s Ethernet I/O scanner service are accessed through
explicit messages or the DTM.
In this situation, these timeout multiplier (see page 235) settings are recommended:
NOTE: If you use values that are lower than those recommended in the table, the network can
consume unnecessary bandwidth, which can affect the performance of the module within the
system.
Section 5.12
Configuring the M580 CPU as an EtherNet/IP Adapter
Introduction
This section describes the configuration of an M580 CPU as an EtherNet/IP adapter using local
slave functionality.
Introduction
The embedded Ethernet I/O scanner service in the M580 CPU scans network modules.
However, you can enable the CPU’s scanner service as an EtherNet/IP adapter (or local slave).
When the local slave functionality is enabled, network scanners can access CPU data that is
mapped to local slave assembly objects in the CPU program.
NOTE:
The CPU’s scanner service continues to function as a scanner when it is enabled as an
EtherNet/IP adapter.
To get data from the primary CPU, make the connection to the Main IP address of the CPU
(see Modicon M580 Hot Standby, System Planning Guide for, Frequently Used Architectures).
The CPU’s scanner service supports up to 16 instances of local slaves (Local Slave 1 ... Local
Slave 3). Each enabled local slave instance supports these connections:
one exclusive owner connection
one listen-only connection
Process Overview
These are the steps in the local slave configuration process:
Stage Description
1 Enable and configure the CPU’s scanner service as a local slave.
2 Configure local slave instances in the scanner service. (Local slave instances correspond to
each enabled local slave that is scanned.)
3 Specify the size of local slave input and output assemblies in the scanner service. (Use sizes
that match the input and output sizes of the enabled local slave (see page 108).)
Implicit messaging is especially suited to the exchange of peer-to-peer data at a repetitive rate.
explicit messages: The CPU’s scanner service responds to explicit messaging requests that are
directed to CIP objects. When local slaves are enabled by the CPU, explicit messaging requests
can access the CPU’s scanner service CIP assembly instances. (This is a read-only function.)
Third-Party Devices
If the CPU’s scanner service that communicates with the local slave can be configured using
Control Expert, use DTMs that correspond to the CPU to add those modules to your configuration.
Third-party EtherNet/IP scanners that access the local slave assembly instances through the
CPU’s scanner service do so with respect to the assembly mapping table. The CPU’s scanner
service is delivered with its corresponding EDS file. Third-party scanners can use the contents of
the EDS file to map inputs and outputs to the appropriate assembly instances of the CPU’s scanner
service.
Introduction
Use these instructions to create a simple local slave configuration that includes a network scanner
(originator, O) and an M580 CPU that is enabled as a local slave (target, T).
1 M580 CPU: The CPU on the M580 local rack. In this example, you will enable this CPU’s embedded
scanner service as a local slave device (or target, T).
2 Modicon M340 rack: In this example, the scanner (or originator, O) on this rack scans the CPU data on the
M580 rack through the enabled local slave (M580 CPU’s scanner service).
Introduction
In a sample configuration, you will enable Local Slave 1 and Local Slave 2.
First, use these instructions to enable Local Slave 1 in the CPU’s embedded scanner service
configuration. At the end of this exercise, repeat these instructions to enable Local Slave 2.
Step Action
1 Open your M580 Control Expert project.
2 On the General tab, assign this Alias name to the CPU: BMEP58_ECPU_EXT.
3 In the DTM Browser (Tools → DTM Browser), double-click the DTM that corresponds to the alias
name of the BMENOC0301.2 module to open the configuration window.
4 In the navigation pane, expand (+) EtherNet/IP Local Slaves to see the 3 available local slaves.
5 Select a local slave to see its properties. (For this example, select Local Slave 1.)
6 In the drop-down list (Properties → Active Configuration), scroll to Enabled.
7 Click Apply to enable Local Slave 1.
8 Click OK to apply the changes and close the configuration window.
You now have enabled Local Slave 1 for the CPU’s scanner service at IP address 192.168.20.10.
EtherNet/IP scanners that scan the network for the CPU’s scanner service at that IP address can
use implicit messages to read from and write to the assembly instances that are associated with
the local slave instance.
Step Action
1 Repeat the steps above to enable a second local slave (Local Slave 2).
NOTE: The appropriate IP address for this example (192.168.20.10) was already assigned to
the CPU’s scanner service in the assignment of Local Slave 1.
2 Continue to the next procedure to configure the network scanner (originator, O).
Introduction
Use these instructions to map local slave instances in a network scanner to the enabled local
slaves in the CPU’s embedded scanner service (Local Slave 1, Local Slave 2, Local Slave 3).
This example uses a BMENOC0301 Ethernet communication module as a network scanner
(originator, O) that scans the CPU scanner service when it is enabled as a local slave (target, T).
Configure the BMENOC0301 module in an M580 Control Expert project.
The local slave (Local Slave 1) is now the target of a local slave instance with a context-sensitive
connection name (Local Slave 1 - Exclusive Owner).
Mapping IP Addresses
Associate the IP address of the local slave (target, T) with the local slave instances in the scanner
(originator, O) configuration:
Step Action
1 Double-click the BMENOC0301 module in the DTM Browser.
2 In the navigation pane, expand the Device List (see Modicon M580, BMENOC0301/0311
Ethernet Communications Module, Installation and Configuration Guide).
3 Select a local slave instance (BMEP58_ECPU_from_EDS_LS1).
4 Select the Address Setting tab.
5 In the IP Address field, enter the IP address of the local slave device (192.168.20.10).
6 Click inside the navigation pane to make the Apply button active.
NOTE: You may have to select Disabled in the drop-down menu (DHCP for this device) to
activate the OK and Apply buttons.
7 Configure the data size.
8 Click Apply.
Step Action
1 Repeat the preceeding steps (see page 315) to create a second local slave instance that
corresponds to Local Slave 2.
2 Build the Control Expert project.
Step Actiom
1 In the Project Browser (Tools → Project Browser), expand Variables & FB instances.
2 Double-click Device DDT Variables to see the device DDTs that correspond with the CPU’s
scanner service.
Step Action
1 Open the Control Expert project.
2 Open the DTM Browser (Tools → DTM Browser).
3 In the DTM Browser, double-click the CPU DTM to open the configuration window.
NOTE: You can also right-click the CPU DTM and select Open.
4 Expand (+) Device List in the navigation tree to see the local slave instances.
5 Select the local slave instance to view the Properties and Assembly configuration tabs.
Properties
Identify and enable (or disable) the local slave on the Properties tab:
Parameter Description
Number The Control Expert DTM assigns a unique identifier (number) to the device. These are
the default values:
local slave 1: 129
local slave 2: 130
local slave 3: 131
Active Enabled Enable the local slave with the configuration information in the Assembly
Configuration fields when the CPU scanner service is an adapter for the local slave
node.
Disabled Disable and deactivate the local slave. Retain the current local slave
settings.
Comment Enter an optional comment (maximum: 80 characters).
Connection Bit The connection bit is represented by an integer (769 ... 896).
NOTE:
This setting is auto-generated after the local slave settings are input and the network
configuration is saved.
The connection bit is represented by an integer:
385...387 (firmware v1.0)
769...896 (firmware v.2.10)
Assembly
Use the Assembly area of the Local Slave page to configure the size of the local slave inputs and
outputs. Each device is associated with these assembly instances:
Outputs
Inputs
Configuration
Heartbeat (The heartbeat assembly instance is for listen-only connections only.)
The Control Expert assembly numbers are fixed according to this table, where O indicates the
originator (scanner) device and T indicates the target device:
NOTE: When using explicit messaging to read the CPU’s scanner service assembly instance,
allocate sufficient room for the response. The size of the response equals the sum of: assembly
size + 1 byte (Reply service) + 1 byte (General Status).
Limitations (from the perspective of the local slave):
maximum RPI value: 65535 ms
maximum timeout value: 512 * RPI
outputs (T->O): 509 bytes maximum
inputs (O->T): 505 bytes maximum
configuration for the CPU scanner service: 0 (fixed)
Introduction
Use Control Expert to create a collection of device derived data types (DDDTs) and variables that
support communications and the transfer of data between the PAC and the various local slaves,
distributed devices, and corresponding I/O modules.
You can create DDDTs and corresponding variables in the Control Expert DTM. Those program
objects support your network design.
NOTE: The default device name depends on the firmware version installed in the selected CPU,
and may be one of the following:
T_BMEP58_ECPU
T_BMEP58_ECPU_EXT
T_M_ECPU_HSBY
You can double-click the name of the DDDT in the Project Browser at any time to view its properties
and open the corresponding EDS file.
NOTE: For applications that require multiple DDDTs, create an Alias name that logically identifies
the DDDT with the configuration (module, slot, local slave number, etc.).
DDDT Variables
You can access the DDDTs and the corresponding variables in Control Expert and add them to a
user-defined Animation Table. Use that table to monitor read-only variables and edit read-write
variables.
Use these data types and variables to perform these tasks:
Read the status of connections and communications between the Ethernet communication
module and distributed EtherNet/IP and Modbus TCP devices:
The status is displayed in the form of a HEALTH_BITS array consisting of 32 bytes.
A bit value of 0 indicates the connection is lost or the communication module can no longer
communicate with the distributed device.
Toggle a connection ON (1) or OFF (0) by writing to a selected bit in a 16-word DIO_CTRL array
Monitor the value of local slave and distributed device input and output items that you created
in Control Expert.
NOTE: The HEALTH_BITS array is not copied to the standby CPU in a Hot Standby switchover.
The DIO_CTRL array is copied to the standby CPU in a Hot Standby switchover.
Section 5.13
Hardware Catalog
Hardware Catalog
Introduction
The Control Expert Hardware Catalog displays the modules and devices that you can add to a
Control Expert project. Each module or device in the catalog is represented by a DTM that defines
its parameters.
Introduction
The Control Expert Hardware Catalog contains a list of modules and devices that you can add to
a Control Expert project. EtherNet/IP and Modbus TCP devices are located in the DTM Catalog
tab at the bottom of the Hardware Catalog. Each module or device in the catalog is represented by
a DTM that defines its parameters.
EDS Files
Not all devices in today’s market offer device-specific DTMs. Some devices are defined by device-
specific EDS files. Control Expert displays EDS files in the form of a DTM. In this way, you can use
Control Expert to configure devices that are defined by an EDS file in the same way you would
configure a device defined by its DTM.
Other devices lack both a DTM and an EDS file. Configure those devices by using the generic DTM
on the DTM Catalog page.
Step Action
1 Open Control Expert.
2 Find the PLC bus in the Project Browser.
3 Use one method to open the catalog:
Use the pull-down menu (Tools → Hardware Catalog).
Double-click an empty slot in the PLC bus.
A Manufacturer-Defined Process
Before a DTM can be used by the Control Expert Hardware Catalog, install the DTM on the host
PC (the PC that is running Control Expert).
The installation process for the DTM is defined by the device manufacturer. Consult the
documentation from the device manufacturer to install a device DTM on your PC.
NOTE: After a device DTM is successfully installed on your PC, update the Control Expert
Hardware Catalog to see the new DTM in the catalog. The DTM can then be added to a Control
Expert project.
Introduction
You may want to use an EtherNet/IP device for which no DTM is in the catalog. In that case, use
these instructions to import the EDS files into the catalog to create a corresponding DTM.
Control Expert includes a wizard you can use to add one or more EDS files to the Control Expert
Hardware Catalog. The wizard presents instruction screens to execute these commands:
Simplify the addition of EDS files to the Hardware Catalog.
Provide a redundancy check when you add duplicate EDS files to the Hardware Catalog.
NOTE: The Control Expert Hardware Catalog displays a partial collection of DTMs and EDS files
that are registered with the ODVA. This library includes DTMs and EDS files for products that are
not manufactured or sold by Schneider Electric. The non-Schneider Electric EDS files are identified
by vendor in the catalog. Please contact the identified device’s manufacturer for inquiries regarding
the corresponding non-Schneider Electric EDS files.
Step Action
1 Open a Control Expert project that includes an Ethernet communication module.
2 Open the DTM Browser (Tools → DTM Browser).
3 In the DTM Browser, select a communication module.
4 Right-click on the communication module and scroll to Device menu → Additional functions → Add
EDS to library.
5 In the EDS Addition window, click Next.
Step Action
1 Use these commands in the Select the Location of the EDS File(s) area of the EDS Addition dialog
box to identify the location of the EDS files:
Add File(s): Add one or more EDS files that are individually selected.
Add all the EDS from the Directory: Add all files from a selected folder. (Check Look in
Subfolders to add EDS files from the folders within the selected folder.)
2 Click Browse to open a navigation dialog box.
3 Select the location of the EDS file(s):
Navigate to at least one EDS file.
Navigate to a folder that contains EDS files.
Step Action
4 Click Select to close the navigation window.
NOTE: Your selection appears in the Directory or File Name field.
5 Choose the naming convention rule for the EDS DTM name creation.
The new naming convention is based on Model Name / Product Name and Revision. A random
character is automatically suffixed when Model Name / Product Name and Revision of an EDS file
in the library is identical. The new naming convention is irrespective of the order in which EDS files
are added to device library.
By default, the New Naming Convention check box is selected and the new naming rule applies.
NOTE: To keep backward compatibility with Unity Pro/Control Expert versions, unchecked the
New Naming Convention check box and the naming rule is based on Model Name / Product Name.
6 Click Next to compare the selected EDS files to the files in the library.
NOTE: If one or more selected EDS files is a duplicate, a File Already Exists message appears.
Click Close to hide the message.
7 The next page of the EDS Addition wizard opens. It indicates the status of each device you
attempted to add:
check mark (green): The EDS file can be added.
Introduction
You can remove a module or device from the list of available devices in the Control Expert
Hardware Catalog by removing its EDS file from the library.
When you remove an EDS file from the library, the device or module disappears from the DTM
Catalog. However, removing the file from the library does not delete the file from its stored location,
so you can import the file again later.
Step Action
1 Open the Control Expert DTM Browser (Tools → DTM Browser).
2 In the DTM Browser, select an Ethernet communication module.
3 Right-click the module and scroll to Device menu → Additional functions → Remove EDS from
library to open the EDS Deletion from Device Library window:
Step Action
4 Use the selection lists in the heading of this window to specify how EDS files are displayed:
Display Choose criteria to filter the list of EDS files:
All EDS (no filtering)
Only Devices
Only Chassis
Only Modules
5 Expand (+) the Device Library navigation tree and select the EDS file you want to remove.
NOTE: Click View Selected File to see the read-only contents of the selected EDS file.
6 Click the Delete Selected File(s) button to open the DeleteEDS dialog box.
7 Click Yes to remove the selected EDS file from the list.
8 Repeat these steps for each EDS file you want to delete.
9 Click Finish to close the wizard.
Result: The hardware catalog automatically updates.
Introduction
To use the same project on two Control Expert installations (for example a source, and a target
Host PCs), you may have to update the DTM Hardware Catalog of the target Host PC.
Instead of adding one by one the missing EDS files in the target Host PC, you can update the DTM
Hardware Catalog in two steps:
Exporting the EDS library from the source Host PC.
Importing the EDS library in the target Host PC.
NOTE: When you export the EDS library, the software generates an .DLB file which contains all
the DTM created form EDS files.
Step Action
1 Open a Control Expert project that includes an Ethernet communication module.
2 Open the DTM Browser (Tools → DTM Browser).
3 In the DTM Browser, select a communication module.
4 Right-click on the communication module and scroll to Device menu → Additional functions →
Export EDS library to open the Export EDS library window:
Step Action
1 Open the Control Expert DTM Browser (Tools → DTM Browser).
2 In the DTM Browser, select an Ethernet communication module.
3 Right-click the module and scroll to Device menu → Additional functions → Import EDS library to
open the Import EDS library window:
Section 5.14
M580 CPU Embedded Web Pages
Introduction
The M580 CPU includes a Hypertext Transfer Protocol (HTTP) server. The server transmits web
pages for the purpose of monitoring, diagnosing, and controlling remote access to the
communication module. The server provides easy access to the CPU from standard internet
browsers.
Introduction
Use the embedded web server pages to perform these tasks:
Display real-time diagnostic data for both the M580 CPU and other networked devices.
Read the values from and write values to Control Expert application variables.
Manage and control access to the embedded web pages by assigning separate passwords for
these functions:
View the diagnostic web pages.
Use the Data Editor to write values to Control Expert application variables.
Browser Requirements
The embedded web server in the M580 CPU displays data in standard HTML web pages. Access
the embedded web pages on a PC, iPad, or Android tablet with these browsers:
Internet Explorer (v8 or later) (v10 or later for Windows Phone OS)
Google Chrome (v11 or later) (v35 or later for Android OS v4 mini)
Mozilla Firefox (v4 or later)
Safari (v6.0 for Apple Mac. No support for Windows.)
Step Action
1 Open an Internet browser.
2 In the address bar, enter the IP address of the M580 CPU (see page 125).
3 Press Enter and wait for the Home page to open.
NOTE:
This page is updated every 5 seconds.
Refer to the Status Summary page for Hot Standby CPUs (see page 352).
Diagnostic Information
The objects on this page provide status information:
Parameters Description
LEDs The black field contains LED indicators (RUN, ERR, etc.).
NOTE: The diagnostics information is explained in the description of LED activity and
indications (see page 49).
Service Status green The available service is operational and running.
red An error is detected in an available service.
black The available service is not present or not configured.
Version Info. This field describes the software versions that are running on the CPU.
CPU Summary This field describes the CPU hardware and the applications that are running on the CPU.
Network Info. This field contains network and hardware address information and connectivity that
corresponds to the CPU.
Performance
NOTE:
Move the mouse over the dynamic graphs to see the current numeric values.
This page is updated every 5 seconds.
Diagnostic Information
This table describes the performance statistics:
Field Description
Module I/O Utilization This graph shows the total number of packets (per second) the CPU can handle at
once.
Messaging Statistics This graph shows the number of Modbus/TCP or EtherNet/IP messages per
second for the client or server.
Port Statistics
NOTE: This page is updated every 5 seconds. Click Reset Counters to reset all dynamic counters
to 0.
Diagnostic Information
This page shows the statistics for each port on the CPU. This information is associated with the
configuration of the Ethernet ports (see page 58) and the configuration of the service/extended
port (see page 135).
The frame color indicates the port activity:
green: active
gray: inactive
yellow: error detection
red: error detection
Expanded View
Click Detail View to see more statistics:
Statistic Description
Frames Transmitted number of frames successfully transmitted
Frames Received number of frames received
Excessive Collisions number of excessive Ethernet collisions
Late Collisions number of late Ethernet collisions
CRC Errors number of detected cyclic redundancy check errors
Bytes Received number of bytes received
Inbound Packet Errors number of detected inbound packet errors
Inbound Packets Discarded number of inbound packets discarded
Bytes Transmitted number of bytes transmitted
Outbound Packet Errors number of detected outbound packet errors
Outbound Packets Discarded number of outbound packets discarded
I/O Scanner
Diagnostic Information
This table describes the scanner status and connection statistics:
In the Scanned Device Status display, the colors that appear in each block indicate these states
for specific remote devices:
Hold the cursor over any block to get information for a specific device:
Messaging
Diagnostic Information
This page shows current information for open Modbus TCP connections on port 502:
Field Description
Messaging Statistics This field contains the total number of sent and received messages on port 502.
These values are not reset when the port 502 connection is closed. Therefore,
the values indicate the number of messages that have been sent or received
since the module was started.
Active Connections This field shows the connections that are active when the Messaging page is
refreshed.
QoS
NOTE:
Configure the QoS in Control Expert (see page 134).
Click Detail View to expand the list of parameters.
This page is updated every 5 seconds.
Service Status
This table shows the possible states for the Service Status:
Status Description
Running The service is correctly configured and running.
Disabled The service is disabled.
Unknown The status of the service is not known.
Diagnostic Information
This page displays information about the QoS service that you configure in Control Expert
(see page 134).
When you enable QoS, the module adds a differentiated services code point (DSCP) tag to each
Ethernet packet it transmits, thereby indicating the priority of that packet:
Considerations
Take measures to effectively implement QoS settings in your Ethernet network:
Use only network switches that support QoS.
Apply the same DSCP values to all network devices and switches.
Use switches that apply a consistent set of rules for handling the different DSCP values when
transmitting and receiving Ethernet packets.
NTP
Introduction
The NTP page displays information about the network time service. Configure this service in
Control Expert (see page 131).
NOTE:
Click Reset Counters to reset all dynamic counters to 0.
This page is updated every 5 seconds.
Diagnostic Information
The Network Time Service synchronizes computer clocks over the Internet for the purposes of
event recording (sequence events), event synchronization (trigger simultaneous events), or alarm
and I/O synchronization (time stamp alarms):
Field Description
Service Running The NTP service is correctly configured and running.
Status
Disabled The NTP service is disabled.
Unknown The NTP service status is unknown.
Server Status green The server is connected and running.
red A bad server connection is detected.
gray The server status is unknown.
Server Type Primary A primary server polls a master time server for the current time.
Secondary A secondary server requests the current time only from a primary server.
DST Status Running DST (daylight saving time) is configured and running.
Disabled DST is disabled.
Unknown The DST status is unknown.
Current Date This is the current date in the selected time zone.
Current Time This is the current time in the selected time zone.
Time Zone This field shows the time zone in terms of plus or minus Universal Time, Coordinated (UTC).
NTP Service These fields show the current values for service statistics.
Statistics
Number of This field shows the total number of requests sent to the NTP server.
Requests
Success Rate This field shows the percentage of successful requests out of the total
number of requests.
Number of This field shows the total number of responses received from the NTP
Responses server.
Last Error This field contains the error code of the last error that was detected during
the transmission of an email message to the network.
Number of This field contains the total number of email messages that could not be
Errors sent to the network or that have been sent but not acknowledged by the
server.
Redundancy
Diagnostic Information
This page displays values from the RSTP configuration in Control Expert (see page 127):
Field Description
Service Status Running The RSTP bridge on the corresponding CPU is properly
configured and running.
Disabled The RSTP bridge on the corresponding CPU is disabled.
Uknown The status of the RSTP bridge on the corresponding CPU is not
known.
Last Topology These values represent the date and time that the last topology change was received
Change for the corresponding Bridge ID.
Redundancy green The designated Ethernet port is learning or formatting information.
Status
yellow The designated Ethernet port is discarding information.
gray RSTP is disabled for the designated Ethernet port.
Router Bridge Bridge ID This unique bridge identifier is the concatenation of the bridge
Statistics RSTP priority and the MAC address.
Bridge Priority In Control Expert, configure the RSTP operating state
(see page 127) of the Bridge ID.
Alarm Viewer
Diagnostic Information
The Alarm Viewer page reports detected application errors. You can read, filter, and sort
information about alarm objects on this page. Adjust the type of information displayed by the Alarm
Viewer in the Filter Alarms box.
Each alarm has a timestamp, a description, and an acknowledgement status:
critical (red)
acknowledged (green)
information (blue) (These alarms do not require acknowledgement.)
Column Description
Type This column describes the alarm type.
Status STOP You need to acknowledge the alarm.
ACK An alarm has been acknowledged.
OK An alarm does not require acknowledgment.
Message This column contains the text of the alarm message.
Occurance This column contains the date and time that the alarm occurred.
Acknowledged This column reports the acknowledged status of the alarm.
Zone This column contains the area or geographical zone from which the alarm comes (0:
common area).
Rack Viewer
Example
This example of a Rack Viewer page shows the Hot Standby connection between a primary CPU
rack and a standby CPU rack. Both racks contain a power supply, a CPU, and a BMECRA312•0
communications module (in slot 7):
The Hot Standby connection (dashed line) is green when the Hot Standby link is healthy.
NOTE: Click the help button (blue question mark) at any time to get information about navigating
on the Rack Viewer page.
Click on any CPU in the Rack Viewer to see this information:
Section 5.15
M580 Hot Standby CPU Web Pages
Overview
This section describes the diagnostic web pages for the M580 BMEH58•040(S) Hot Standby CPU
modules.
Introduction
The M580 BMEH58•040(S) Hot Standby CPUs includes an embedded web server that provide
monitoring and diagnostic functions. All web pages are read-only.
These web pages are included:
Module:
Status Summary (Hot Standby) (see page 352)
HSBY Status (see page 354)
Performance (see page 334)
Port Statistics (see page 335)
Connected Devices:
I/O Scanner (see page 337)
Messaging (see page 339)
Services:
QoS (see page 340)
NTP (see page 342)
Redundancy (see page 344)
System:
Alarm Viewer (see page 345)
The embedded web site is accessible via WiFi, using a smartphone or tablet equipped with a:
Schneider Electric WiFi dongle, called the wifer, part number TCSEGWB13FA0.
PMXNOW0300 wireless module.
Introduction
The Status Summary web page provides this information about the CPU:
Ethernet service diagnostic information
Version descriptions for installed firmware and software
CPU description and operating state
IP addressing settings
Parameters Description
LEDs The web page displays the state of these LEDs:
RUN A
ERR B
I/O PRIM
DL STBY
REMOTE RUN FORCED_IO
BACKUP SRUN (safety PAC)
ETH MS SMOD (safety PAC)
ETH MS
NOTE: The LEDs on the web page behave the same as the LEDs on the CPU
(see page 52).
Service Status This area presents information describing the status of CPU Ethernet services. The
colored icons appearing to the left of some items indicate the following status:
green The available service is operational and running.
red An error is detected in an available service.
black The available service is not present or not configured.
The status of these Ethernet services is included:
DHCP Server Scanner Status
FDR Server NTP Status
Access Control FDR Usage
Version Info. This area describes the software versions that are running on the CPU, including:
Executable Version Web Site Version
Web Server Version CIP Version
CPU Summary This area describes the CPU hardware and the applications that are running on the
CPU, including:
Model
State
Scan Time
Network Info. This field contains IP addressing settings for the CPU, including:
IP Address
Subnet Address
Gateway Address
HSBY Status
Introduction
The HSBY Status web page provides this information about the Hot Standby system:
Hot Standby role and status of the Local CPU
Hot Standby role and status of the Remote CPU
General errors detected for the Hot Standby system
NOTE:
The local CPU is the CPU configured with the Main IP Address (primary) or Main IP Address + 1
(standby) used to access this web page.
The HSBY Status web page is refreshed every 5 seconds.
Area Description
Local/Remote This area displays the state of Hot Standby settings for the local and remote CPUs:
<Hot Standby Role> The Hot Standby system role of the CPU. Valid values include:
Primary
Standby
Wait
<Operating State> The operating state of the CPU. Valid values include:
RUN
STOP
NoConf
HALT
A/B switch setting The designation of the CPU, defined by the rotary switch
(see page 46) on the back of the CPU. Valid values include:
A
B
<Run Mode> The designation of the CPU, defined by the rotary switch on
the back of the CPU. Valid values include:
Online
Wait
IP Address The IP address used to communicate with the CPU for web
page access:
For the primary Hot Standby CPU, this is the
Main IP Address setting.
For the standby Hot Standby CPU, this is the
Main IP Address setting + 1.
OS Firmware Level Firmware version of the CPU operating system.
Sync Link Validity The status of the Hot Standby link (see Modicon M580 Hot
Standby, System Planning Guide for, Frequently Used
Architectures):
OK: the link is operational.
NOK: the link is not operational.
Supplementary Link The status of the Ethernet RIO link (see Modicon M580 Hot
Validity Standby, System Planning Guide for, Frequently Used
Architectures):
OK: the link is operational.
NOK: the link is not operational.
Detected Errors Detected errors for the CPU, including:
HSBY link error detected
RIO link error detected (the connection between PAC A
and PAC B over the Ethernet RIO network)
RIO error detected (the connection between a PAC and
(e)X80 EIO adapter modules over the Ethernet RIO
network.
Area Description
General Errors Detected errors for the Hot Standby system, including:
Application mismatch
Logic mismatch
Firmware mismatch
Data layout mismatch
Backup application mismatch
Safety logic mismatch (for safety PACs)
Rack Viewer
Chapter 6
M580 CPU Programming and Operating Modes
Overview
This chapter provides information on M580 CPU I/O exchanges, tasks, memory structure, and
operating modes.
Section 6.1
I/O and Task Management
Overview
This section presents information on M580 I/O addressing and management, tasks allowed, and
I/O scanning capabilities.
I/O Exchanges
I/O Vision
Each module uses a structure that represents inputs, outputs, control, and diagnostic data. The
structures can be represented using:
topological addressing / IODDT
Device DDT
NOTE: If you want to change the type of addressing you selected when you added an I/O module
to your application, delete the module from your application and then insert the module again
selecting the appropriate addressing type.
Exchange Types
I/O modules in an M580 system can be controlled, read, or written with 2 types of exchanges:
implicit exchanges
Implicit exchanges are performed automatically on each cycle of the task (MAST, FAST, AUX0,
AUX1) associated with the I/O modules. They are used to read inputs from and write outputs o
the modules.
explicit exchanges
Explicit exchanges are performed on application request. They are typically for detailed
diagnostics and to set/read command and adjust parameters. They use specific function blocks.
An acknowledgment or reply is sent once the requested action is performed. This reply may be
received a few cycles after the request was sent.
NOTE: Explicit exchanges are performed in the MAST task.
Explicit Exchanges
Function block usage depends on the module location and I/O vision selected for the module:
The function blocks mentioned in previous table are detailed in the Explicit Exchange part of
Control Expert, I/O Management, Block Library manual, and in the Extended part of Control Expert,
Communication, Block Library manual.
CPU Tasks
Introduction
An M580 CPU can execute single-task and multi-task applications. Unlike a single-task application
which only executes the MAST task, a multi-task application defines the priorities of each task.
There are four tasks available (see Application Program Structure chapter in Control Expert
Program Languages and Structure Reference Manual) and two types of event tasks:
MAST
FAST
AUX0
AUX1
I/O event in a local rack only
timer event in a local rack only
NOTE: The time to perform an update init values with current values operation is not taken into
account in the watchdog calculation.
Task Characteristics
The time model, task period, and maximum number of tasks per CPU are defined according to the
standalone or Hot Standby CPU reference.
Standalone CPUs:
Task Time Model Task Period (ms) CPU Reference (BMEH58 ...
Range Default 2040(C) 4040(C) 6040(C)
Value
MAST(1.) periodic(2.) 1...255 20 X X X
AUX0(4.) — — — — — —
AUX1(4.) — — — — — —
Section 6.2
BMEP58xxxx CPU Memory Structure
Memory Structure
CPU Memory
3 types of memories are available in a BMEP58•••• CPU:
non-persistent application RAM: run the application program and store temporary data
flash memory: back up the application program and a copy of %MW values
optional SD memory card: store application and data in parallel to the CPU flash memory,
allowing a fast CPU hardware replacement
NOTE: A write protected memory card inserted disables the application download.
NOTE: The online modification is disabled when a write protected memory card is inserted.
Section 6.3
BMEP58xxxx CPU Operating Modes
Overview
This section provides information on the CPU operating modes.
Input Run/Stop
The %lr.m.c input can be parameterized to switch the PAC to Run/Stop mode as follows:
Set %lr.m.c to 1: The PAC switches to Run mode (executing the program).
Set %lr.m.c to 0: The PAC switches to Stop mode (stopping program execution).
NOTE: A Stop command takes priority over a Run command. A Stop command sent from a
terminal or via the network has priority over the %lr.m.c input.
An error detected on the Run/Stop input causes the PAC to switch to Stop mode.
Do not enable this option if the associated discrete input is mapped in state RAM because this
inhibits the start-up of the PAC.
Memory Protect
The input %lr.m.c can be parameterized to protect the internal application RAM and the memory
card as follows:
%lr.m.c to 0: The internal application and the memory card are not protected.
%lr.m.c to 1: The internal application and the memory card are protected.
NOTE: If the input is in error, %lr.m.c is considered at 1 (memory is protected). To remove this
protection in the configuration screen, the input should not be in error.
Introduction
If the duration of the outage is shorter than the power supply filtering time, it has no effect on the
program which continues to run normally.
If the duration of the outage is longer than the power supply filtering time, the program is interrupted
and power restoration processing is activated. The CPU then restarts in warm restart or cold start
as described in the following diagram.
Illustration
Power cycle phases:
Phase Description
1 On power outage, the system saves the application context, the values of
application variables, and the state of the system on internal flash memory.
2 The system sets all the outputs into fallback state (state defined in
configuration).
3 On power restoral, some actions and checks are done to verify if warm restart
is available:
restore internal flash memory application context
verify application and context validity
If all checks are correct a warm restart (see page 375) is performed, otherwise
a cold start (see page 372) is carried out.
Cold Start
Overview
A cold start is an initialization initiated by the Reset button of the power supply or the Cold start
command in Control Expert.
The consequence of a cold start is the re-initialization of all the variables. They get their default
values.
NOTE: After an application download the variables are reinitialized like a cold start.
2. Automatic start in Run option does not set the CPU to RUN state.
You need to assign a topological address to the data if the process requires keeping the current
values of the data when transferring the application.
To save the located variables, avoid the initialization of the %MWi by unchecking Initialize %MWi
on cold start parameter in the CPU configuration screen.
NOTE: Pressing the RESET button on the power supply resets %MWi and initial values are loaded.
NOTE: Do not press the RESET button on the power supply if you do not want %MWi to be reset
and loaded with initial values.
Phase Description
1 The startup is performed in RUN or in STOP state depending on one of the 2 following conditions:
The status of the Automatic start in Run parameter defined in the CPU configuration. If the
parameter is selected, the start will be performed in RUN.
The state of the I/O defined in the Run/Stop input parameter in the CPU configuration.
NOTE: If the number of %MW words exceeds the backup size during the save operation the
remaining words are set to 0.
Initialize elementary function blocks (initial data).
Initialize data declared in the DFBs: either to 0 or to the initial value declared in the DFB type.
Initialize system bits and words.
Position charts to initial steps.
Cancel any forcing action.
Initialize message and event queues.
Send configuration parameters to all I/O and application-specific modules.
Output Changes
As soon as a power outage is detected the outputs are set in the fallback position configured
(programmed fallback value or current value).
On power down, the outputs are not driven and remain at 0.
After power restoral, the outputs remain at 0 until they are updated by the task.
Warm Restart
Introduction
A warm start is initiated by a power cut.
After a warm restart, the variables get the values that they had before the power cut as a restore
is done by the PLC.
Phase Description
1 Program execution does not resume from the element where the power outage occurred.
The remaining program is discarded during the warm restart. Each task restarts from the
beginning.
2 The system carries out the following:
Restore the application variable values,
Set %S1 system bit to 1.
Initialize message and event queues,
Send configuration parameters to all I/O and application-specific modules,
If the application was reserved, the CPU removes the reservation.
Reset communication.
If needed, the CPU configures the I/O modules with the current adjustment parameters.
Disable FAST, AUX, and event tasks.
NOTE: SFC interpreter is independent, if the transition is valid, the SFC chart evolves while
%S1 = 1.
Output Changes
As soon as a power outage is detected the outputs are set in the fallback position configured: either
programmed fallback value or current value.
After power restoral, the outputs remain at 0 until they are updated by the task.
EIO0000001578 10/2019
Appendices
Appendix A
Function Blocks
Function Blocks
Function Description
Use the ETH_PORT_CTRL function block to control the FTP TFTP, HTTP, and DHCP / BOOTP
protocols when they are enabled in the Control Expert Security screen (see Modicon M580,
BMENOC0301/0311 Ethernet Communications Module, Installation and Configuration Guide). (By
default, these protocols are disabled.) For cyber security reasons (to help protect data against
requests to modify in the monitoring mode), map the inputs on variables and on unlocated
variables in which the HMI property is disabled (the variable is not in the data dictionary).
The additional parameters EN and ENO may also be configured.
FBD Representation
Representation:
LD Representation
Representation:
IL Representation
CAL ETH_PORT_CTRL_Instance (ENABLE := EnableSecurityChange, ABORT :=
AbortSecurityChange, ADDR := ModuleAddress, ETH_SCE := ServiceToChange,
DONE => BlockExecutionDone, ACTIVE => BlockExecutionInProgress, ERROR
=> BlockExecutionError, STATUS => BlockErrorStatus, ETH_SCE_STATUS =>
ChangeServiceStatus)
ST Representation
ETH_PORT_CTRL_Instance (ENABLE := EnableSecurityChange, ABORT :=
AbortSecurityChange, ADDR := ModuleAddress, ETH_SCE := ServiceToChange,
DONE => BlockExecutionDone, ACTIVE => BlockExecutionInProgress, ERROR
=> BlockExecutionError, STATUS => BlockErrorStatus, ETH_SCE_STATUS =>
ChangeServiceStatus);
Description of Parameters
This table describes the input parameters:
(1) To address a module in the local rack, enter 0.0.10 (CPU main server address).
Execution Type
Synchronous:
When used on the following M580 CPU modules, the ETH_PORT_CTRL function block is
executed synchronously. As a result, the DONE output turns ON as soon as the ENABLE input is
set to ON. In this case, the ACTIVE output remains OFF.
BMEP581020
BMEP582020
BMEP582040
BMEP583020
BMEP583040
BMEP584020
BMEP584040
BMEP585040
BMEP586040
BMEH582040*
BMEH584040*
BMEH586040*
*
In BMEH58•040 Hot Standby CPUs, verify that the ETH_PORT_CTRL function block is
executed equally on both primary and standby CPUs.
Asynchronous:
When used on the following modules, the ETH_PORT_CTRL function block is executed asynchro-
nously and may take several cycles until the DONE output turns ON. Therefore, the ACTIVE output
is set to ON until the completion of the ETH_PORT_CTRL function block.
M340 modules:
BMXNOC0401
BMXNOE0100
BMXNOE0110
M580 modules:
BMENOC0301/11
Glossary
!
%MW
According to the CEI standard, %MW indicates a language object of type memory word.
A
adapter
An adapter is the target of real-time I/O data connection requests from scanners. It cannot send or
receive real-time I/O data unless it is configured to do so by a scanner, and it does not store or
originate the data communications parameters necessary to establish the connection. An adapter
accepts explicit message requests (connected and unconnected) from other devices.
B
BCD
(binary-coded decimal) Binary encoding of decimal numbers.
BOOTP
(bootstrap protocol) A UDP network protocol that can be used by a network client to automatically
obtain an IP address from a server. The client identifies itself to the server using its MAC address.
The server, which maintains a pre-configured table of client device MAC addresses and associated
IP addresses, sends the client its defined IP address. The BOOTP service utilizes UDP ports 67
and 68.
C
CCOTF
(change configuration on the fly) A feature of Control Expert that allows a module hardware change
in the system configuration while the system is operating. This change does not impact active
operations.
CIP™
(common industrial protocol) A comprehensive suite of messages and services for the collection
of manufacturing automation applications (control, safety, synchronization, motion, configuration
and information). CIP allows users to integrate these manufacturing applications with enterprise-
level Ethernet networks and the internet. CIP is the core protocol of EtherNet/IP.
CPU
(central processing unit) The CPU, also known as the processor or controller, is the brain of an
industrial manufacturing process. It automates a process as opposed to relay control systems.
CPUs are computers suited to survive the harsh conditions of an industrial environment.
D
determinism
For a defined application and architecture, you can predict that the delay between an event
(change of value of an input) and the corresponding change of a controller output is a finite time t,
smaller than the deadline required by your process.
Device DDT (DDDT)
A Device DDT is a DDT predefined by the manufacturer and not modifiable by user. It contains the
I/O language elements of an I/O module.
device network
An Ethernet-based network within an RIO network that contains both RIO and distributed
equipment. Devices connected on this network follow specific rules to allow RIO determinism.
DFB
(derived function block) DFB types are function blocks that can be defined by the user in ST, IL,
LD or FBD language.
Using these DFB types in an application makes it possible to:
simplify the design and entry of the program
make the program easier to read
make it easier to debug
reduce the amount of code generated
DHCP
(dynamic host configuration protocol) An extension of the BOOTP communications protocol that
provides for the automatic assignment of IP addressing settings, including IP address, subnet
mask, gateway IP address, and DNS server names. DHCP does not require the maintenance of a
table identifying each network device. The client identifies itself to the DHCP server using either its
MAC address, or a uniquely assigned device identifier. The DHCP service utilizes UDP ports 67
and 68.
DIO
(distributed I/O) Also known as distributed equipment. DRSs use DIO ports to connect distributed
equipment.
DIO cloud
A group of distributed equipment that is not required to support RSTP. DIO clouds require only a
single (non-ring) copper wire connection. They can be connected to some of the copper ports on
DRSs, or they can be connected directly to the CPU or Ethernet communications modules in the
local rack. DIO clouds cannot be connected to sub-rings.
DNS
(domain name server/service) A service that translates an alpha-numeric domain name into an IP
address, the unique identifier of a device on the network.
DRS
(dual-ring switch) A ConneXium extended managed switch that has been configured to operate on
an Ethernet network. Predefined configuration files are provided by Schneider Electric to
downloaded to a DRS to support the special features of the main ring / sub-ring architecture.
DSCP
(differentiated service code points) This 6-bit field is in the header of an IP packet to classify and
prioritize traffic.
DTM
(device type manager) A DTM is a device driver running on the host PC. It provides a unified
structure for accessing device parameters, configuring and operating the devices, and
troubleshooting devices. DTMs can range from a simple graphical user interface (GUI) for setting
device parameters to a highly sophisticated application capable of performing complex real-time
calculations for diagnosis and maintenance purposes. In the context of a DTM, a device can be a
communications module or a remote device on the network.
See FDT.
E
EDS
(electronic data sheet) EDS are simple text files that describe the configuration capabilities of a
device. EDS files are generated and maintained by the manufacturer of the device.
EF
(elementary function) This is a block used in a program which performs a predefined logical
function.
A function does not have any information on the internal state. Several calls to the same function
using the same input parameters will return the same output values. You will find information on
the graphic form of the function call in the [functional block (instance)]. Unlike a call to a function
block, function calls include only an output which is not named and whose name is identical to that
of the function. In FBD, each call is indicated by a unique [number] via the graphic block. This
number is managed automatically and cannot be modified.
Position and configure these functions in your program to execute your application.
You can also develop other functions using the SDKC development kit.
EFB
(elementary function block) This is a block used in a program which performs a predefined logical
function.
EFBs have states and internal parameters. Even if the inputs are identical, the output values may
differ. For example, a counter has an output indicating that the preselection value has been
reached. This output is set to 1 when the current value is equal to the preselection value.
EIO network
(Ethernet I/O) An Ethernet-based network that contains three types of devices:
local rack
X80 remote drop (using a BM•CRA312•0 adapter module), or a BMENOS0300 network option
switch module
ConneXium extended dual-ring switch (DRS)
NOTE: Distributed equipment may also participate in an Ethernet I/O network via connection to
DRSs or the service port of X80 remote modules.
Ethernet
A 10 Mb/s, 100 Mb/s, or 1 Gb/s, CSMA/CD, frame-based LAN that can run over copper twisted pair
or fiber optic cable, or wireless. The IEEE standard 802.3 defines the rules for configuring a wired
Ethernet network; the IEEE standard 802.11 defines the rules for configuring a wireless Ethernet
network. Common forms include 10BASE-T, 100BASE-TX, and 1000BASE-T, which can utilize
category 5e copper twisted pair cables and RJ45 modular connectors.
EtherNet/IP™
A network communication protocol for industrial automation applications that combines the
standard internet transmission protocols of TCP/IP and UDP with the application layer common
industrial protocol (CIP) to support both high speed data exchange and industrial control.
EtherNet/IP employs electronic data sheets (EDS) to classify each network device and its
functionality.
explicit messaging
TCP/IP-based messaging for Modbus TCP and EtherNet/IP. It is used for point-to-point,
client/server messages that include both data, typically unscheduled information between a client
and a server, and routing information. In EtherNet/IP, explicit messaging is considered class 3 type
messaging, and can be connection-based or connectionless.
F
FDR
(fast device replacement) A service that uses configuration software to replace an inoperable
product.
FDT
(field device tool) The technology that harmonizes communication between field devices and the
system host.
FTP
(file transfer protocol) A protocol that copies a file from one host to another over a TCP/IP-based
network, such as the internet. FTP uses a client-server architecture as well as separate control and
data connections between the client and server.
G
gateway
A gateway device interconnects two different networks, sometimes through different network
protocols. When it connects networks based on different protocols, a gateway converts a datagram
from one protocol stack into the other. When used to connect two IP-based networks, a gateway
(also called a router) has two separate IP addresses, one on each network.
H
HMI
(human machine interface) System that allows interaction between a human and a machine.
Hot Standby
A Hot Standby system uses a primary PAC (PLC) and a standby PAC. The two PAC racks have
identical hardware and software configurations. The standby PAC monitors the current system
status of the primary PAC. If the primary PAC becomes inoperable, high-availability control is
maintained when the standby PAC takes control of the system.
HTTP
(hypertext transfer protocol) A networking protocol for distributed and collaborative information
systems. HTTP is the basis of data communication for the web.
I
implicit messaging
UDP/IP-based class 1 connected messaging for EtherNet/IP. Implicit messaging maintains an
open connection for the scheduled transfer of control data between a producer and consumer.
Because an open connection is maintained, each message contains primarily data, without the
overhead of object information, plus a connection identifier.
IP address
The 32-bit identifier, consisting of both a network address and a host address assigned to a device
connected to a TCP/IP network.
L
local rack
An M580 rack containing the CPU and a power supply. A local rack consists of one or two racks:
the main rack and the extended rack, which belongs to the same family as the main rack. The
extended rack is optional.
local slave
The functionality offered by Schneider Electric EtherNet/IP communication modules that allows a
scanner to take the role of an adapter. The local slave enables the module to publish data via
implicit messaging connections. Local slave is typically used in peer-to-peer exchanges between
PACs.
M
MAST
A master (MAST) task is a deterministic processor task that is run through its programming
software. The MAST task schedules the RIO module logic to be solved in every I/O scan. The
MAST task has two sections:
IN: Inputs are copied to the IN section before execution of the MAST task.
OUT: Outputs are copied to the OUT section after execution of the MAST task.
MB/TCP
(Modbus over TCP protocol) This is a Modbus variant used for communications over TCP/IP
networks.
Modbus
Modbus is an application layer messaging protocol. Modbus provides client and server
communications between devices connected on different types of buses or networks. Modbus
offers many services specified by function codes.
N
NIM
(network interface module) A NIM resides in the first position on an STB island (leftmost on the
physical setup). The NIM provides the interface between the I/O modules and the fieldbus master.
It is the only module on the island that is fieldbus-dependent — a different NIM is available for each
fieldbus.
NTP
(network time protocol) Protocol for synchronizing computer system clocks. The protocol uses a
jitter buffer to resist the effects of variable latency.
P
PAC
programmable automation controller. The PAC is the brain of an industrial manufacturing process.
It automates a process as opposed to relay control systems. PACs are computers suited to survive
the harsh conditions of an industrial environment.
port 502
Port 502 of the TCP/IP stack is the well-known port that is reserved for Modbus TCP
communications.
R
RIO drop
One of the three types of RIO modules in an Ethernet RIO network. An RIO drop is an M580 rack
of I/O modules that are connected to an Ethernet RIO network and managed by an Ethernet RIO
adapter module. A drop can be a single rack or a main rack with an extended rack.
RIO network
An Ethernet-based network that contains 3 types of RIO devices: a local rack, an RIO drop, and a
ConneXium extended dual-ring switch (DRS). Distributed equipment may also participate in an
RIO network via connection to DRSs or BMENOS0300 network option switch modules.
RPI
(requested packet interval) The time period between cyclic data transmissions requested by the
scanner. EtherNet/IP devices publish data at the rate specified by the RPI assigned to them by the
scanner, and they receive message requests from the scanner at each RPI.
RSTP
(rapid spanning tree protocol) Allows a network design to include spare (redundant) links to provide
automatic backup paths if an active link stops working, without the need for loops or manual
enabling/disabling of backup links.
S
SFP
(small form-factor pluggable). The SFP transceiver acts as an interface between a module and
fiber optic cables.
SNMP
(simple network management protocol) Protocol used in network management systems to monitor
network-attached devices. The protocol is part of the internet protocol suite (IP) as defined by the
internet engineering task force (IETF), which consists of network management guidelines,
including an application layer protocol, a database schema, and a set of data objects.
SNTP
(simple network time protocol) See NTP.
sub-ring
An Ethernet-based network with a loop attached to the main ring, via a dual-ring switch (DRS) or
BMENOS0300 network option switch module on the main ring. This network contains RIO or
distributed equipment.
T
TCP
(transmission control protocol) A key protocol of the internet protocol suite that supports
connection-oriented communications, by establishing the connection necessary to transmit an
ordered sequence of data over the same communication path.
TFTP
(trivial file transfer protocol) A simplified version of file transfer protocol (FTP), TFTP uses a client-
server architecture to make connections between two devices. From a TFTP client, individual files
can be uploaded to or downloaded from the server, using the user datagram protocol (UDP) for
transporting data.
trap
A trap is an event directed by an SNMP agent that indicates one of these events:
A change has occurred in the status of an agent.
An unauthorized SNMP manager device has attempted to get data from (or change data on) an
SNMP agent.
U
UDP
(user datagram protocol) A transport layer protocol that supports connectionless communications.
Applications running on networked nodes can use UDP to send datagrams to one another. Unlike
TCP, UDP does not include preliminary communication to establish data paths or provide data
ordering and checking. However, by avoiding the overhead required to provide these features,
UDP is faster than TCP. UDP may be the preferred protocol for time-sensitive applications, where
dropped datagrams are preferable to delayed datagrams. UDP is the primary transport for implicit
messaging in EtherNet/IP.
UMAS
(Unified Messaging Application Services) UMAS is a proprietary system protocol that manages
communications between Control Expert and a controller.
UTC
(coordinated universal time) Primary time standard used to regulate clocks and time worldwide
(close to former GMT time standard).
Index
A BMEP583040
CPU, 19
access control
BMEP584020
security, 121
CPU, 19
add
BMEP584040
I/O module, 363
CPU, 19
add remote device, 286
BMEP585040
address
CPU, 19
field bus, 41
BMEP586040
advanced settings, 137
CPU, 19
tab, 119
BMXRMS004GPF, 62
alarm viewer web page
BMXXCAUSB018 USB cables, 56
CPU, 345
BMXXCAUSB045 USB cables, 56
application
BOOTP
legacy, 114
security, 121
password, 107
assembly object, 175, 179
asynchronous execution
ETH_PORT_CTRL, 379
C
certifications, 32
authorized address
channel properties, 141
security, 121
characteristics
AUTOTEST
current consumption, 37
state, 33
power consumption, 37
AUX0 task
CIP objects, 172
CPU, 365
clear
AUX1 task
application, 47
CPU, 365
clear local statistics, 279
clear remote statistics, 280
B cold
start, 372
backup, 114
compatibility
block service port
CPU, 86
Hot Standby, 135
CONF_SIG
blocking condition, 82
device DDT, 216
BMEP581020
configuration
CPU, 19
Control Expert, 101
BMEP582020
CPU, 119
CPU, 19
connection
BMEP582040
diagnostics, 155
CPU, 19
I/O, 158
BMEP583020
connection manager object, 177
CPU, 19
management OS DOWNLOAD
I/O, 362 state, 33
task, 362 OUNID, 138
MAST task OUT_ERRORS
CPU, 365 device DDT, 216
MBP_MSTR, 262, 266, 269, 275 OUT_PACKETS
Quantum RIO drops in M580, 261 device DDT, 216
memory
CPU, 367
memory card P
diagnostics, 63 panel
FTP, 62 CPU, front, 43
install, 78 password
memory protect for Control Expert application, 107
for CPU, 107 performance, 87
messaging web page performance web page
CPU, 339 CPU, 334
Modbus physical description
explicit message, 259 CPU, 42, 45
module events ping, 166
logging to syslog server, 160 port
modules Ethernet, 58
install, 71 port function
MTBF device DDT, 216
CPU, 37 port statistics web page
CPU, 335
power
N cycle, 370
NOCONF power consumption, 37
state, 33 project
non-blocking condition, 84 password, 107
NTP
diagnostics, 153
RIO scanner service, 132 Q
tab, 119 QoS, 134
NTP web page tab, 119
CPU, 342 QoS object, 181
QoS web page
CPU, 340
O Quantum RIO drops in M580
online action, 162 MBP_MSTR explicit message, 261
CIP object, 164
ping, 166
port configuration, 165 R
originator unique identifier, 138 read data, 276
summary USB
configuration, 321 cables, 56
connections, 321 pin assignments, 56
switch, 133 transparency, 56
Switch
tab, 119
synchronous execution W
ETH_PORT_CTRL, 379 WAIT
syslog server state, 33
logging, 160 warm
system error, 85 restart, 375
system states start, 375
Hot Standby, 34 web page
CPU alarm viewer, 345
CPU I/O scanner, 337
T CPU messaging, 339
T_BMEP58_ECPU, 216 CPU NTP, 342
device DDT, 216 CPU performance, 334
T_BMEP58_ECPU_EXT, 216 CPU port statistics, 335
device DDT, 216 CPU QoS, 340
T_M_ECPU_HSBY, 224 CPU redundancy, 344
tab CPU status summary, 332
advanced settings, 119 web pages, 331, 350
IPConfig, 119 rack viewer, 357
NTP, 119 write data, 276
QoS, 119
RSTP, 119
Safety, 119
Security, 119
Service Port, 119
SNMP, 119
Switch, 119
task
CPU, 365
management, 362
TCP/IP interface object, 183
TFTP
security, 121
U
update
firmware, 67
upgrade
firmware, 67