Quantum Using Ecostruxure™ Control Expert: Ethernet Network Modules User Manual
Quantum Using Ecostruxure™ Control Expert: Ethernet Network Modules User Manual
33002479 10/2019
Quantum using
EcoStruxure™
Control Expert
Ethernet Network Modules
User Manual
Original instructions
10/2019
33002479.20
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 33002479 10/2019
Table of Contents
Safety Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
About the Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Part I Modicon Quantum with Control Expert Ethernet
Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Chapter 1 Product Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.1 Module Description 140 CPU 651 x0 . . . . . . . . . . . . . . . . . . . . . . . . . 20
140 CPU 651 x0 Product Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Physical Presentation and Mounting of Standard High End Modules . 22
CPU Controls and Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Using the CPU LCD Display Screens . . . . . . . . . . . . . . . . . . . . . . . . . 30
1.2 Module Description 140 NOE 771 xx and 140 NWM 100 00 . . . . . . . 41
Modicon Quantum Ethernet Modules Overview . . . . . . . . . . . . . . . . . 42
Indicators for Ethernet Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Connectors and Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Using the 140 NOE 771 11 Ethernet Module in a Quantum Safety
Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
1.3 Installing the Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Cable Schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Mounting the Module in the Quantum PLC Backplane . . . . . . . . . . . . 57
Connecting the Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Assigning Ethernet Address Parameters. . . . . . . . . . . . . . . . . . . . . . . 60
Establishing the FTP Password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Establishing HTTP and Write Passwords for NOE . . . . . . . . . . . . . . . 66
Using BOOTP Lite to Assign Address Parameters . . . . . . . . . . . . . . . 69
1.4 Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Customer Support Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Chapter 2 Ethernet Communication Services . . . . . . . . . . . . . . . . . 73
Modicon Quantum with Control Expert Ethernet Services . . . . . . . . . 74
Address Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
SNMP and Schneider Private MIB Overview . . . . . . . . . . . . . . . . . . . 78
Modbus Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
33002479 10/2019 3
I/O Scanner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Global Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Time Synchronization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Electronic Mail Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Bandwidth Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
FTP Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Embedded Web Pages (HTTP Server, Web Configuration and
Diagnostics) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Additional Ethernet Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Part II Modicon Quantum with Control Expert Ethernet
Modules Services. . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Chapter 3 Start Communication with Control Expert. . . . . . . . . . . . . 93
3.1 How to Configure the Communication . . . . . . . . . . . . . . . . . . . . . . . . . 94
Add a New Network to the Communication Folder . . . . . . . . . . . . . . . 95
Configure Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Properties of a Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Delete an Existing Network Folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
3.2 Control Expert Communication Links. . . . . . . . . . . . . . . . . . . . . . . . . . 99
Communication Configuration Principle . . . . . . . . . . . . . . . . . . . . . . . . 100
Link between Configuration and Communication. . . . . . . . . . . . . . . . . 101
Link between Data and Communication . . . . . . . . . . . . . . . . . . . . . . . 102
3.3 Selecting the Ethernet Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Selecting the Quantum NOE Ethernet Module . . . . . . . . . . . . . . . . . . 104
Security (Enable / Disable HTTP, FTP, and TFTP) . . . . . . . . . . . . . . . 107
IP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Quantum NOE Ethernet Messaging Configuration . . . . . . . . . . . . . . . 109
3.4 Selecting the Ethernet Coprocessor . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Selecting the Modicon Quantum with Control Expert Ethernet
Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Configuring the IP Address of the Ethernet Controller . . . . . . . . . . . . . 115
Modicon Quantum with Control Expert Ethernet Controller Messaging
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
4 33002479 10/2019
Part III Using the Modicon Quantum with Control Expert
Ethernet Services . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Chapter 4 Transferring Data Using Communication Blocks . . . . . . 119
4.1 IEC Data Transfer Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
CREAD_REG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
CWRITE_REG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
READ_REG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
WRITE_REG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
TCP_IP_ADDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
4.2 MBP_MSTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Block Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Operational Function Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Network Control Block Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Modbus Plus, SY/MAX, and Ethernet TCP/IP Error Codes. . . . . . . . . 143
CTE Error Codes for SY/MAX and TCP/IP Ethernet . . . . . . . . . . . . . . 147
SY/MAX-Specific Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Read Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Write Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Get Local Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Clear Local Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Get Remote Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Clear Remote Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
TCP/IP Ethernet Network Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
TCP/IP Ethernet Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Reset Optional Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Read CTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Write CTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Send Email . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Send Modbus Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Close Connection Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Change Modbus Plus Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Read/Write Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Enable / Disable HTTP or FTP/TFTP Services . . . . . . . . . . . . . . . . . . 182
33002479 10/2019 5
Chapter 5 Global Data (Publish/Subscribe) Utility. . . . . . . . . . . . . . . 185
Planning the Global Data (Publish/Subscribe) System . . . . . . . . . . . . 186
Multicast Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Quantum NOE Global Data Configuration . . . . . . . . . . . . . . . . . . . . . . 192
Configuration of Global Data (Publish/Subscribe) by the Web for NOE
771 x1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Chapter 6 I/O Scanner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
I/O Scanner Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Configuring the Quantum I/O Scanner. . . . . . . . . . . . . . . . . . . . . . . . . 204
I/O Scanning Contextual Menu for Copy/Cut/Paste. . . . . . . . . . . . . . . 210
I/O Scanning with Multiple Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Introduction to Configuring Advantys from Control Expert . . . . . . . . . . 214
Introduction to Configuring the PRM Master DTM . . . . . . . . . . . . . . . . 218
Introduction to Configuring a BMX PRA 0100 from Control Expert . . . 220
Property Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Saving an Advantys Configuration in an Control Application . . . . . . . . 230
Managed Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
I/O Scanner Response Times: Remote Input to Remote Output . . . . . 233
Chapter 7 Address Server Configuration/Fast Device Replacement 237
Address Server Configuration/Fast Device Replacement . . . . . . . . . . 238
Understanding Fast Device Replacement . . . . . . . . . . . . . . . . . . . . . . 240
Configuring Fast Device Replacement. . . . . . . . . . . . . . . . . . . . . . . . . 242
Chapter 8 Network Management Service (SNMP) . . . . . . . . . . . . . . 247
SNMP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
ASN.1 Naming Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Configuring an NOE with SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Configuring an NOE with TFE Private MIB . . . . . . . . . . . . . . . . . . . . . 254
Chapter 9 NTP Time Synchronization Service . . . . . . . . . . . . . . . . . 263
Introducing the NTP Time Synchronization Service. . . . . . . . . . . . . . . 264
Using the R_NTPC Block for Time Synchronization . . . . . . . . . . . . . . 267
NTP Time Synchronization Service Operating Conditions. . . . . . . . . . 269
Configuring the NTP Time Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Chapter 10 Electronic Mail Notification Service . . . . . . . . . . . . . . . . . 275
Introducing the Electronic Mail Notification Service . . . . . . . . . . . . . . . 276
Mail Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Using the MBP_MSTR Block for Mail Service Communication . . . . . . 279
Mail Service Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Electronic Mail Notification Service Subtree . . . . . . . . . . . . . . . . . . . . 282
6 33002479 10/2019
Chapter 11 Embedded Web Pages. . . . . . . . . . . . . . . . . . . . . . . . . . 283
Quantum Home Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
Monitoring Home Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Diagnostics Home Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Setup Home Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
Accessing the Web Utility Home Page . . . . . . . . . . . . . . . . . . . . . . . . 290
Configured Local Rack Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Controller Status Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
CPU Configuration Screen: Data Field Descriptions . . . . . . . . . . . . . . 293
Remote I/O Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
Quantum PLC Data Monitor Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
SNMP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Global Data (Publish/Subscribe) Utility Configuration . . . . . . . . . . . . . 299
Configure Address Server Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Configuring the Time Synchronization Service . . . . . . . . . . . . . . . . . . 305
Mail Service Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
Ethernet Module Diagnostic Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
NTP Diagnostics Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Properties Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
Contacting Schneider Electric Page . . . . . . . . . . . . . . . . . . . . . . . . . . 323
Chapter 12 Hot Standby . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Quantum Hot Standby for Control Expert . . . . . . . . . . . . . . . . . . . . . . 326
Hot Standby Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
NOE Module Configuration and Hot Standby . . . . . . . . . . . . . . . . . . . 329
140 NOE 771 x1 / 140 NOC 78• 00 IP Address Assignment . . . . . . . 330
140 NOE 771 x1 / 140 NOC 78• 00 Operating Modes in Quantum Hot
Standby System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
NOE IP Address Swap Times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
Network Effects of Modicon Quantum Hot Standby with Control Expert
Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
Appendices ......................................... 341
Appendix A Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
Responding to Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Reading and Clearing the Crash Log . . . . . . . . . . . . . . . . . . . . . . . . . 349
Downloading a New NOE Exec. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Downloading a New NOE Exec via FTP . . . . . . . . . . . . . . . . . . . . . . . 351
Downloading a New NOE Kernel . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
Appendix B Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
33002479 10/2019 7
Appendix C Quantum Ethernet TCP/IP Modbus Application Protocol . 357
Modbus Application Protocol Overview . . . . . . . . . . . . . . . . . . . . . . . . 358
Modbus Application Protocol PDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
Modbus Application Protocol Service Classes. . . . . . . . . . . . . . . . . . . 362
Modbus Application Protocol PDU Analysis. . . . . . . . . . . . . . . . . . . . . 363
TCP/IP Specific Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Closing a TCP Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Reference Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
Appendix D Installation and Configuration of a Modicon Quantum
Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
Configuring the Rack with Control Expert . . . . . . . . . . . . . . . . . . . . . . 372
Configuring the Ethernet Network with Control Expert. . . . . . . . . . . . . 375
Configuring the I/O Scanning Service . . . . . . . . . . . . . . . . . . . . . . . . . 378
Building and Downloading the Configuration Program . . . . . . . . . . . . 384
Diagnosing the Ethernet Module Using the Web Server . . . . . . . . . . . 388
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
8 33002479 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.
33002479 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 33002479 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.
33002479 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 33002479 10/2019
About the Book
At a Glance
Document Scope
This document is for users who want their Quantum PLC to communicate with devices over an
Ethernet network. It assumes that you have some knowledge of PLC systems and a working
knowledge of Modsoft, Concept, ProWORX, or Control Expert programming tools. You also need
to understand the use of Ethernet networks and TCP/IP.
This document describes the functionality of the Modicon Quantum Ethernet modules, the
104 NOE 771 xx and 140 NWM 100 00 modules, and the Ethernet port of the 140 CPU 651 x0
modules.
This document describes how to install, set up, and use Ethernet-enabled modules in a Modicon
Quantum control system. These modules allow the Quantum system to communicate with devices
over an Ethernet network. Topics addressed in this manual include:
the hardware architecture of a Modicon Quantum Ethernet module, which is designed to fit into
a single slot on the standard Modicon Quantum backplane
capabilities and installation of 140 NOE 771 xx and 140 NWM 100 00 modules in a Modicon
Quantum system
capabilities of the Ethernet port on the 140 CPU 651 x0 CPU modules
33002479 10/2019 13
This document describes the procedures for:
setting up the modules to transfer data using either the Global Data modules (140 NOE 771 01,
140 NOE 771 11, or 140 CPU 651 x0 mobules) or the I/O scanner utility (in the
140 NOE 771 00/01/11 modules and the 140 CPU 651 50/60 modules)
using an embedded Web server to access diagnostics and online configurations for the module
and its associated controller
using the FactoryCast Web server to customize your configuration via embedded Web pages
(in 140 NOE 771 10/11 and 140 NWM 100 00 modules)
using an NOE module in a Hot Standby solution for fault-tolerant remote I/O and
communications
Nomenclature
The following table describes the naming rules for various groups of modules:
NOTE: Before adding a node to an existing corporate network, consult with your information
technology (IT) department about any possible consequences.
14 33002479 10/2019
Validity Note
This document is valid for EcoStruxure™ Control Expert 14.1 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.
Related Documents
33002479 10/2019 15
Title of Documentation Reference Number
Quantum using EcoStruxure™ Control Expert, Discrete and Analog I/O, 35010516 (English),
Reference Manual 35010517 (French),
35010518 (German),
35013970 (Italian),
35010519 (Spanish),
35012185 (Chinese)
Quantum using EcoStruxure™ Control Expert, Experts and Communication, 35010574 (English),
Reference Manual 35010575 (French),
35010576 (German),
35014012 (Italian),
35010577 (Spanish),
35012187 (Chinese)
Communication Services and Architectures, Reference Manual 35010500 (English),
35010501 (French),
35006176 (German),
35013966 (Italian),
35006177 (Spanish),
35012196 (Chinese)
Schneider Automation BOOTP Lite Ethernet IP Address Download Utility for 31002087
Schneider Automation Ethernet Products Instruction Sheet
FactoryCast for Quantum, Premium and Micro User Guide 31001229
Quantum using EcoStruxure™ Control Expert, Hot Standby System, User 35010533 (English),
Manual 35010534 (French),
35010535 (German),
35013993 (Italian),
35010536 (Spanish),
35012188 (Chinese)
Modbus Protocol Reference Guide PI-MBUS-300
Open Modbus Specification http://www.modbus.org/
FactoryCast HMI 1.7, Setup Manual, Premium and Quantum HMI Modules 35007632 (English),
35007634 (French),
35007633 (German),
35007635 (Spanish),
35007636 (Italian)
You can download these technical publications and other technical information from our website
at https://www.schneider-electric.com/en/download
16 33002479 10/2019
Quantum using EcoStruxure™ Control Expert
Ethernet Products
33002479 10/2019
Part I
Modicon Quantum with Control Expert Ethernet Products
Purpose
This part introduces the Modicon Quantum with Control Expert products used for Ethernet
communication.
33002479 10/2019 17
Ethernet Products
18 33002479 10/2019
Quantum using EcoStruxure™ Control Expert
Product Description
33002479 10/2019
Chapter 1
Product Description
Product Description
Overview
This chapter includes product overviews for:
the 140 NOE 771 xx modules
the 140 NWM 100 00 module
the built-in Ethernet port of the 140 CPU 651 x0 modules
When inserted in the backplane, these modules allow your Quantum PLC to communicate over
Ethernet networks.
33002479 10/2019 19
Product Description
Section 1.1
Module Description 140 CPU 651 x0
Overview
This is a discussion of the the Modicon Quantum High-End CPU (HE CPU) (140 CPU 651 x0).
20 33002479 10/2019
Product Description
General Description
The Quantum-140 CPU 651 x0 module (see page 22) is among the newest in a series of Quantum
processor modules. It combines standard PLC functions with the diagnostic possibilities of a Web
server. The 140 CPU 651 x0 communicates using an RJ45 connection.
The 140 CPU 651 x0 module is in a double-width standard Quantum housing, which requires 2
sequential slots in a Quantum rack. Its server functions are diagnostic only, so use software to
configure services.
The table shows the key Ethernet services that are implemented:
33002479 10/2019 21
Product Description
Illustration
The figure shows a standard High End module and its components.
NOTE: Quantum High End processors are equipped with one PCMCIA slot (B) or two PCMCIA
slots (A and B) in which to install Schneider PCMCIA cards (other cards are not accepted).
22 33002479 10/2019
Product Description
Mounting
Mounting the module onto the central back plane:
33002479 10/2019 23
Product Description
Lens Cover
The protective lens cover (2 on the CPU front panel (see Quantum using EcoStruxure™ Control
Expert, Hot Standby System, User Manual)) can be opened by sliding it upwards.
With the lens cover open you have access to the following items:
key switch
battery
reset button
Key Switch
The key switch (4) is a security feature and a memory protection switch. The key switch has two
positions: locked and unlocked. The key switch is only read and deciphered by the PLC OS portion
of the firmware and not by the OS loader portion.
The Quantum processors have a set of system menus that enable the operator to:
perform PLC operations (i.e., start PLC, stop PLC)
display module parameters (i.e., communications parameters)
switch to the maintenance mode (in Safety processors)
locked: No system menu operations can be invoked and module parameters are
read-only.
Memory protection is ON.
Safe mode forced (in Safety processors).
Switching the key switch position from locked to unlocked or vice versa turns on the LCD's
backlight.
NOTE: For more explanations about Maintenance and Safe modes, refer to the Modicon Quantum,
Quantum Safety PLC, Safety Reference Manual.
24 33002479 10/2019
Product Description
Unity Pro is the former name of Control Expert for version 13.1 or earlier.
The following table provides information on switch position for high end Quantum 140 CPU 6•• •••
with firmware ≥ 3.12 and Unity Pro < V8:
Unity Pro is the former name of Control Expert for version 13.1 or earlier.
The following table provides information on switch position for high end Quantum 140 CPU 6•• •••
with firmware ≥ 3.2 and Unity Pro ≥ V8:
33002479 10/2019 25
Product Description
Reset Button
Pressing the reset button (12) forces a cold start of the PLC.
LCD Display
The liquid crystal display (LCD - 3) has 2 lines with 16 characters each with changeable backlight
state and contrast:
The backlight handling is entirely automated to save the life of the LCDs. The backlight turns on
when one of the following occurs:
a key is pressed
the key switch state is changed
an error message is displayed on the LCD
The backlight stays on for error messages as long as the error message is displayed otherwise,
the backlight automatically turns off after five minutes.
Step Action
1 Press the MOD key:
26 33002479 10/2019
Product Description
Keypad
The keypad (5) has five keys that are mapped to hardware addresses. Each of the two arrow keys
includes an LED:
1 5 keys
2 2 LEDs
Key Function
To cancel an entry, suspend or stop an action in progress
To display the preceding screens successively (move up the menu tree)
LED: flashing Key active: The modify mode field can be scrolled.
LED: off Key inactive: No menu options and no field options.
LED on Key active:
to move around in a screen, field to field
to go to the sub-menu
LED flashing Key active: Used to move digit to digit in a modify mode
field.
LED off Key inactive, there is no:
sub-menu for menu option
scrolling around a screen
scrolling around a field
33002479 10/2019 27
Product Description
Indicators
Overview
The High End processors use two types of indicators:
1. LCD display: The Default Screen (see page 31) serves as a Controller status screen.
2. LED Indicators: The functionality of the LEDs is described in a table after the figure.
The following figure shows the two types of indicators.
28 33002479 10/2019
Product Description
LED Description
The following table shows the description for the LED indicators of the different High End CPU
modules.
LEDs Indication
Standard Processors 140 CPU 65• •0 / Hot StandBy Processors 140 CPU 67• 6• /
140 CPU 651 60S 140 CPU 671 60S
COM Controlled by the Coprocessor hardware Controlled by the Coprocessor hardware
(yellow) Indicates Ethernet activity Indicates Primary or Standby activity
33002479 10/2019 29
Product Description
Introduction
The controller LCD displays messages. These messages indicate the controller status. There are
four levels of menus and submenus. Use the keypad (see page 27) on the front of the controller to
access the menus.
For detailed information about the menus and submenus see:
PLC Operations Menus and Submenus (see page 33)
Using the Communications Menus and Submenus (see page 36)
Using the LCD Settings Menus and Submenus (see page 39)
Using the System Info Menus and Submenus (see page 40)
1 default screen
2 system menus
3 sub menus
4 sub screens
30 33002479 10/2019
Product Description
Step Action
1 To access the screens, confirm that the key switch is in the unlocked position.
33002479 10/2019 31
Product Description
32 33002479 10/2019
Product Description
33002479 10/2019 33
Product Description
34 33002479 10/2019
Product Description
33002479 10/2019 35
Product Description
Communications Menu
Communications menu and submenus:
36 33002479 10/2019
Product Description
1)Parameters
can be modified only if no applications have been downloaded (in NO CONF state).
2)When
a new PLC application has been downloaded, the Ethernet address on the screen is
updated only after accessing the highest level of the menu structure.
Modbus Plus PLC Communications submenus:
33002479 10/2019 37
Product Description
38 33002479 10/2019
Product Description
33002479 10/2019 39
Product Description
40 33002479 10/2019
Product Description
Section 1.2
Module Description 140 NOE 771 xx and 140 NWM 100 00
Overview
This section contains the module descriptions for 140 NOE 771 xx and 140 NWM 100 00.
33002479 10/2019 41
Product Description
Overview
The following information provides overviews of all Modicon Quantum Ethernet modules.
General Description
The Modicon Quantum Ethernet module, shown below, is one of the latest models in a line of
Modicon Quantum Ethernet TCP/IP modules designed to make it possible for a Modicon Quantum
PLC to communicate with devices over an Ethernet network. The electronics for the Ethernet
modules are contained in a standard Modicon Quantum single-width case that takes up one slot in
a Modicon Quantum backplane. The module, which is capable of being hot swapped, can be
plugged into any available slot in the backplane.
The NOE 771 x0 and NOE 771 x1 modules provide real-time peer-to-peer communications and
I/O scanning and a Modbus/TCP server. The included HTTP services provide maintenance and
configuration utilities to the module.
42 33002479 10/2019
Product Description
Front View
The following figure shows the front of the NOE 771 00 Ethernet module as an example for all
Ethernet modules.
33002479 10/2019 43
Product Description
NOTE: In the detailed description of the key features, only modules in the NOE family are named.
The features are also available for the 140 NWM 100 00 module, depending on the listed
properties in the above table.
NOTE: In Control Expert software, the 140 NWM 100 00 module is set in the TCP/IP Regular
Network family, although it belongs to the TCP/IP FactoryCast network family. So, the services
listed above (I/O scanning, Global Data, address server, Bandwidth monitoring) are not supported
by the module. However, they can be selected in the TCP/IP regular network configuration in
Control Expert. (Even if they are configured, those services won't work with the module.)
44 33002479 10/2019
Product Description
Component Description
LED Indicator Panel Indicates the operating status of the module, and the fiber optic
(see page 46) or Ethernet communications network to which it is connected.
IP Address Area Provides a writable area to record the module’s assigned IP
address.
Global Address Label Indicates the module’s global Ethernet MAC address assigned
at the factory.
100 BASE-FX Connector Provides an MT-RJ socket for connection to a 100-megabit
fiber-optic Ethernet cable.
10/100 BASE-T Connector Provides an RJ45 socket for connection to a shielded, twisted
pair Ethernet cable.
33002479 10/2019 45
Product Description
Illustration
The following figure shows the NOE 771 00 LED indicators as a placeholder for all other Ethernet
modules:
Description
The following table shows the LED descriptions:
46 33002479 10/2019
Product Description
33002479 10/2019 47
Product Description
Overview
The following information describes the 10/100 BASE-T and 100 BASE-FX connectors.
Schneider Electric recommends that you use Category 5 STP cabling, which is rated to 100 Mbps,
with an RJ-45 connector.
The eight pins are arranged vertically and numbered in order from the bottom to the top. The RJ-
45 pinout used by this module is:
Receive Data (+) 3
Receive Data (-) 6
Transmit Data (+) 1
Transmit Data (-) 2
100 BASE-FX
The 100 BASE-FX connector for the NOE 771 xx, NWM 100 00, and CPU 651 60 modules is an
MT-RJ socket or a mating fiber optic cable connector.
For the NOE 771 xx and NWM 100 00, you may need an MT-RJ to SC (duplex) multimode fiber
optic cable assembly 62.5/125mm. Schneider Electric recommends cable number 490NOC00005
to connect to fiber hubs/switches.
NOTE: The NOE 771 xx and NWM 100 00 are one-channel devices that can communicate over
either 10/100 BASE-T or 100 BASE-FX Ethernet networks at any given time, but not over both at
the same time.
48 33002479 10/2019
Product Description
Using the 140 NOE 771 11 Ethernet Module in a Quantum Safety Project
Overview
Version 4.2 and higher of the 140 NOE 771 11 Ethernet module can be included in one of the
following:
Quantum safety applications
non-safety applications
Only safety modules can write data to a safety-restricted memory area. For more information about
restricted versus unrestricted memory areas, refer to the topic Safety PLC Write Protection in the
Unity Pro XLS Operating Mode Manual.
The 140 NOE 771 11 Ethernet module–as a non-interfering module–cannot write data to safety-
restricted memory areas. Instead, the 140 NOE 771 11 Ethernet module can write data only to
unrestricted memory areas.
The memory areas of a Quantum safety project are user-configurable. Using Control Expert, you
can designate address ranges as either safety-restricted or unrestricted. For instructions on how
to configure memory areas, refer to the topic Configuration of Quantum Processors with Unity Pro
XLS in the Unity Pro XLS Operating Mode Manual.
33002479 10/2019 49
Product Description
CAUTION
RISK OF DATA LOSS
The default address assignments for the following data blocks overlap:
Global Data Health Bit block (%MW1)
I/O Scanning Health Bit block (%MW1)
I/O Scanning Device Control block (%MD1)
You must edit these address assignments so they do not overlap. If these address assignments
overlap, the PLC will overwrite data and the overwritten data will be lost.
Failure to follow these instructions can result in injury or equipment damage.
The 140 NOE 771 11 makes different address assignments–regarding both I/O Scanning and
Global Data Health Bit Blocks–for safety and non-safety applications, as follows:
50 33002479 10/2019
Product Description
Section 1.3
Installing the Module
Introduction
This section contains installation and configuration information for the NOE 771 xx Ethernet
modules.
33002479 10/2019 51
Product Description
Initial Checks
CAUTION
UNINTENTIONAL OPERATION
If you do not enter the correct address pairs into the BOOTP server, you could communicate to
the wrong device.
Confirm that the MAC address matches the intended IP address in your BOOTP server.
Having two or more devices with the same IP address may cause unpredictable operation of your
network.
Confirm that your Ethernet module receives a unique IP address.
Failure to follow these instructions can result in injury or equipment damage.
If the administrator assigns new address parameters, configure the module through the Control
Expert interface module configuration screen.
52 33002479 10/2019
Product Description
33002479 10/2019 53
Product Description
Cable Schemes
Overview
The following information provides guidelines on proper cabling schemes for your Ethernet
configuration.
Device Type Max. Cable Length from Max. Number of Hubs/Switches Max. Distance Between Network
Node to Hub/Switch Between Any Two Nodes Nodes
hub 10 BASE-T: 100 m 3 500 m
switch 10/100 BASE-T: 100 m unlimited unlimited
100 BASE-FX: 2 km
54 33002479 10/2019
Product Description
100BASE-FX
The maximum cable segment length for 100BASE-FX multimode cable (1300 nm) is 2 km. The
number of switches you can implement over that distance is unlimited.
33002479 10/2019 55
Product Description
Security
Overview
The following information describes firewalls. A firewall is a gateway that controls access to your
network. To restrict access to your Ethernet controller and I/O network, you may want to consider
a firewall.
Types of Firewalls
There are network-level and application-level firewalls:
Network-level firewalls: These firewalls are frequently installed between the Internet and a
single point of entry to an internal, protected network.
Application-level firewalls: An application-level firewall acts on behalf of an application. It
intercepts all traffic destined for that application and decides whether to forward that traffic to
the application. Application-level firewalls reside on individual host computers.
You may need to provide the information in this table to your system administrator so that the
firewall configuration will allow access to your PLC from outside of your facility.
56 33002479 10/2019
Product Description
Tools Required
You will need one medium-size, Phillips-head screw driver.
Step Action
1 Holding the module at an angle, mount it on the two hooks located near the top of
the backplane. The following figure shows the correct way to hold the module.
2 Swing the module down so its connector engages the backplane connector.
3 Using a Phillips-head screw driver, tighten the screw at the bottom of the module
between 2 and 4 in-lbs or between .22 and .45 Newton meters of torque.
33002479 10/2019 57
Product Description
58 33002479 10/2019
Product Description
Overview
The following information pertains to cabling.
NOTE: The 140 NOE 771 xx is capable of communicating over either a 10/100BASE-T or a
100BASE-FX Ethernet network at any given time, but not both at the same time.
Accessories
Schneider Electric sells the following switches:
The following Schneider Electric cables support multicast filtering (see page 190):
Cable Description
490NTW000 02/05/12/40/80 U StraightThru cable
490NTC000 05/15/40/80 U Crossover cable
Fiber Optic
Remove the protective cap from the module’s MT-RJ connector port and the protective cap from
the tip of the black connector on the MT-RJ fiber optic cable (as shown in the following figure). The
plug only fits to the socket in one way. It should snap into place.
33002479 10/2019 59
Product Description
Overview
CAUTION
UNINTENTIONAL OPERATION
If you do not enter the correct address pairs into the BOOTP server, you could communicate to
the wrong device.
Ensure that the MAC address matches the intended IP address in your BOOTP server.
Having two or more devices with the same IP address can cause unpredictable operation of your
network.
Ensure that your Ethernet module receives a unique IP address.
Failure to follow these instructions can result in injury or equipment damage.
60 33002479 10/2019
Product Description
Step Action
1 Be sure the NOE module is running.
2 Obtain the default IP address of the NOE derived from its MAC address (for example,
84.0.0.2).
3 Open an MS-DOS window.
4 Add an active route for the local NOE by typing:
C:\>ROUTE ADD <target> MASK <mask> <gateway>
e.g.
C:\>ROUTE ADD 84.0.0.0 MASK 255.0.0.0 205.217.193.205
Use the default IP address of the NOE module as target address. Use a class A subnet
mask for connecting to every 84.0.0.0 address. The gateway address is the IP of your
PC. The result is that MS Windows will now talk to any address that starts with an 84
that is directly connected to a hub or switch directly accessible to your machine, or that
can be seen by the specified route/gateway.
5 Confirm that there is a new entry in the active route table by typing:
C:\>route print:
The following figure confirms that the new entry was added to the active route table.
33002479 10/2019 61
Product Description
Automatic ARP
If there are no replies to its requests, the NOE 771 xx automatically sends three ARP requests at
2-second intervals to announce its presence on the network.
62 33002479 10/2019
Product Description
33002479 10/2019 63
Product Description
Step Action
1 Enter the URL, for example,
http://hostname/secure/embedded/ftp_passwd_config.htm
2 At that URL, supply a user name and password:
Note: The default User name is USER, and the default Password is USERUSER.
Both should be changed by the system administrator during module installation.
3 Upon supplying the user name, password, and clicking the OK button, the Modify
FTP Server User Name and Password page displays.
64 33002479 10/2019
Product Description
Step Action
1 Type in the new Username in the New User Name field.
2 Type in the new Password in the New Password field.
3 Click the Submit FTP Password Change button.
The following figure shows the message that is generated if you click on the Submit FTP Password
Change button:
Clicking the Reboot Device button will reset the username and password for the NOE board.
NOTE: The reboot requires about 40 seconds. (With large applications, reboot may require up to
one (1) minute.)
During the reboot, all services provided by the NOE module are not available.
33002479 10/2019 65
Product Description
Overview
The following information describes how to set the passwords for HTTP and Data Monitor Write for
the NOE.
Step Action
1 Enter the URL, for example,
http://hostname/secure/embedded/http_passwd_config.htm
2 At that URL, supply a user name and password in the dialog box. The size of the user
name and password is a maximum of 16 characters in non-extended ASCII.
Note: The default User Name is USER, and the default Password is USER. Both
should be changed by the system administrator during module installation.
3 Upon supplying the user name, password, and clicking the OK button, the Modify
Passwords page displays.
66 33002479 10/2019
Product Description
33002479 10/2019 67
Product Description
Step Action
1 Type a new username in the New User Name field.
2 Type a new password in the New Password field.
3 Confirm the new password in the Confirm Password field.
4 Click the Change HTTP Access button.
Step Action
1 Type the old password in the Write Password field.
2 Type a new password in the New Password field.
3 Confirm the new password in the Confirm Password field.
4 Click the Change Write Password button.
Clicking the Reboot Device button will reset the username and password for the NOE board.
NOTE: The Reboot will take about 40 seconds. Larger applications can take up to one (1) minute.
During the reboot all services provided by the NOE are not available.
68 33002479 10/2019
Product Description
Overview
CAUTION
UNINTENTIONAL OPERATION
Ensure that the MAC address matches the intended IP address in your BOOTP server. If you do
not enter the correct address pairs into the BOOTP server, you could communicate to the wrong
device.
Failure to follow these instructions can result in injury or equipment damage.
The following information describes how to use the BOOTP Lite utility software.
33002479 10/2019 69
Product Description
Section 1.4
Customer Support
Customer Support
Overview
This section tells you how to get customer support from Schneider Electric’s documentation and
regional help centers.
70 33002479 10/2019
Product Description
Support Documentation
If you have any problems, please first consult the documentation listed above or the MS-Windows
documentation.
For the most up-to-date NOE Ethernet controller information, please:
Step Action
1 Access the Schneider Electric Web site.
2 Search technical information.
3 Select Quantum from the list of cross-product families.
4 Access either:
resolutions for resolutions to product issues
product manuals for the most recently published user documentation
product announcements
33002479 10/2019 71
Product Description
Contact Information
Contact Information
Please find the nearest Schneider Electric sales office by visiting http://www.schneider-
electric.com. In the Select a country list, click the country closest to you for customer support.
72 33002479 10/2019
Quantum using EcoStruxure™ Control Expert
Ethernet Communication Services
33002479 10/2019
Chapter 2
Ethernet Communication Services
Introduction
This chapter describes the Ethernet communications services available on 140 NOE 771 x1 and
140 CPU 651 x0.
33002479 10/2019 73
Ethernet Communication Services
74 33002479 10/2019
Ethernet Communication Services
33002479 10/2019 75
Ethernet Communication Services
Address Server
Overview
The following information describes the services provided by the address server.
BOOTP server
DHCP server
BOOTP Server
NOTE: The BOOTP server is available on the 140 NOE 771 xx models.
The BOOTstrap Protocol (BOOTP) software, compliant with RFC 951, is used to assign IP
addresses to nodes on an Ethernet network. Devices (hosts) on the network send BOOTP
requests during their initialization sequence. A BOOTP server that receives the request will extract
the required IP address information from its database and place it in BOOTP response messages
to the requesting devices. The devices will use the assigned IP addresses from the BOOTP server
for all network communication.
NOTE: In order for BOOTP to work properly, you need to correctly configure the following:
IP address
subnetwork mask
gateway address
76 33002479 10/2019
Ethernet Communication Services
DHCP Server
NOTE: The DHCP server is available on the 140 NOE 771 x1 models.
The Dynamic Host Configuration Protocol (DHCP) is a superset of the BOOTP protocol. Your
140 NOE 771 x1 has a DHCP server. The DHCP server is compliant with RFC 1531. The DHCP
server can be used to provide the IP configuration to devices using BOOTP or devices using
DHCP.
The DHCP server has entries that use the MAC address to serve the IP configuration and entries
in the server that use the role name to serve the IP configuration. Elsewhere in this book are details
for the NOE address server configuration (see page 237).
If you are migrating a BOOTP configuration from a 140 NOE 771 x0 module to the new
140 NOE 771 x1 module, see Address Server Configuration/Fast Device Replacement
(see page 237) for details on the automatic upgrade of your configuration for the new DHCP
server.
NOTE: Before placing the NOE on a corporate network, Schneider Electric recommends that you
discuss the installation with your MIS department. It is likely that your company's corporate network
has at least one DHCP server running already. If the NOE's DHCP server is running on the same
network, it may disturb the network.
To avoid any possible problem related to the NOE's DHCP server on the corporate network, ensure
that the DHCP server is not running in the NOE by not having address entries in the configuration.
If there are no configured devices in the address server configuration page (see page 237), then
the NOE will not start the DHCP server.
Device Replacement
Fast device replacement and the address server are discussed in detail at Address Server
Configuration/Fast Device Replacement (see page 237).
33002479 10/2019 77
Ethernet Communication Services
Overview
Simple Network Management Protocol (SNMP) is configured on your NOE or 140 CPU 651 x0.
Introduction
Network management software allows a network manager to:
monitor and control network components
isolate problems and find their causes
query devices, such as a host computer(s), routers, switches, and bridges, to determine their
status
obtain statistics about the networks to which they are attached
MIB
Each object to which SNMP has access must be defined and given a unique name. Manager and
agent programs must both agree on the names and meanings of the fetch and store operations.
The set of all objects SNMP can access is known as a Management Information Base (MIB).
Private MIB
Schneider obtained a private MIB, Groupe_Schneider (3833). Under the Groupe Schneider private
MIB is a Transparent Factory Ethernet (TFE) private MIB. The Transparent Factory SNMP
embedded component controls the Schneider private MIB function.
78 33002479 10/2019
Ethernet Communication Services
Modbus Messaging
Overview
The following information describes the functionality of the Modbus/TCP server.
The Client
The node that initiates a data transaction is called a client. All Modicon Quantum Ethernet modules
provide the user with the capability to transfer data to and from nodes on a TCP/IP network using
a communication instruction. All PLCs that support networking communication capabilities over
Ethernet can use either the MBP_MSTR Ladder Logic instruction to read or write controller
information or IEC communication blocks.
The Server
The node that receives an inquiry is the server. Using the standard Modbus/TCP protocol, all
Modicon Quantum Ethernet modules provide access to controller data. Any device, PC, HMI
package, another PLC, or any Modbus/TCP compliant device, can access data from the PLC. The
Modbus/TCP server also allows programming panels to log into the controller over Ethernet.
The maximum register size for read requests, write requests, or read/write requests made using
either a MBP_MSTR or Modbus command is as follows:
33002479 10/2019 79
Ethernet Communication Services
Performance
The following table shows the performance characteristics of the NOE Ethernet module’s
Modbus/TCP server.
Parameter Value
Typical Response Time (ms) 0.6
Number of Modbus connections (client and server) 64 (NOE 771 x1, NWM 100 00,
HE CPU 651 x0), 16 Client
(NOE 771 x0), 32 Server
(NOE 771 x0)
Number of simultaneous login channels 1
NOTE: Ethernet module’s Modbus/TCP performance measurements are made with a Modicon
Quantum 140 CPU 534 14A PLC.
80 33002479 10/2019
Ethernet Communication Services
I/O Scanner
Introduction
The functionality of your Ethernet module is further enhanced by the addition of an I/O Scanner,
which you can configure with the Schneider Electric programming panels.
33002479 10/2019 81
Ethernet Communication Services
Parameter Value
Max. No. of Devices 64: 140 NOE 771 00 (Version 2.2 or earlier)
128: 140 NOE 771 00 (Version 3.0 or later), 140 NOE 771 01,
and 140 NOE 771 11 only
128: HE CPU 651 x0
Max. No. of Input Words 4000
Max. No. of Output Words 4000
Health Timeout Value User configured: 1...65535 ms in 1 ms increments
Last Value (Input) User configured (zero or Hold)
IP Address User configured
IP address of scanned device (Slave IP)
Local and Remote Register User configured
Reference
Repetitive Rate User configured: 0...65535 in multiples of:
16 ms, for 140 NOE 771 x1
10 ms, for 140 CPU 651 x0
The I/O Scanner Concepts topic (see page 200) explains how to configure the I/O scanner.
Performance
Performance data details are provided at I/O Scanner Response Times topic (see page 233).
82 33002479 10/2019
Ethernet Communication Services
Global Data
Overview
The Global Data service is a real-time publisher/subscriber mechanism providing the most efficient
data exchange for PLC application coordination.
Devices that support Global Data are arranged in a distribution group for the purpose of application
variable exchange and synchronization. Each Global Data device can publish up to one network
(application) variable and subscribe up to 64 network (application) variables.
The Quantum NOE module’s embedded Global Data Configuration Page provides a configuration
screen to determine which and how many application variables are exchanged with this service.
After configuration, the exchanges between all stations belonging to the same distribution group
are done automatically.
The Global Data service uses %MW words (4x registers) or unlocated variables for Global Data
exchanges.
33002479 10/2019 83
Ethernet Communication Services
Time Synchronization
General
The time service synchronizes computer clocks over the Internet. For example, the time of one
client is synchronized either with another server or to a referenced time source like a radio or
satellite receiver.
Typical time service configurations utilize multiple redundant servers and diverse network paths to
achieve high accuracy and reliability. Time service accuracy can be within a millisecond on LANs
and up to a few tenths of milliseconds on WANs.
Use the time service for:
event recording: sequence events
event synchronization: trigger simultaneous events
alarm and I/O synchronization: time stamp alarms
84 33002479 10/2019
Ethernet Communication Services
General
The electronic mail notification service allows controller-based projects to report alarms or events.
The automation controller monitors the system and can automatically create an electronic mail
message alert with data, alarms, and/or events. Mail recipients can be either local or remote.
Based on predefined events or conditions, messages are created using the MBP_STR function
block.
The email message is constructed from predefined headers plus variables and text (a maximum
of 238 bytes). This message is sent directly from the automation system to the local email
server.
Mail headers contain common predefined items—recipient list, sender name, and subject.
These items can be updated by an authorized administrator.
33002479 10/2019 85
Ethernet Communication Services
Bandwidth Monitoring
Overview
Bandwidth Monitoring allows the user to access and monitor the NOE module’s CPU allocation for
each of the following services:
Global Data (see page 185)
I/O scanning (see page 199)
Modbus messaging (see page 79)
The Bandwidth Monitoring service retrieves workload data and returns one of two pieces of
information: whether the module has free resources or whether the module is working at capacity.
Knowing the resource allocation helps you:
assess resource allocation
determine the number of NOEs needed in a system
NOTE: Users who want to use Bandwidth Monitoring do not need to develop a new set of access
functions. The actual NOE CPU load is computed each second.
CPU time spent in other services is shown as "Other" or "Free." Bandwidth Monitoring uses the
same functions as used by SNMP.
The three service rates, Global Data, I/O Scanner, and Messaging, are computed using the
following formula:
(Current load * 100) / Maximum Load
The table shows the (dynamically computed) Maximum Load Rate for the NOE module:
NOTE: The loads depend on controller scan times. Each application has an expected scan time.
Therefore, when evaluating loads, ensure that the controller scan time is set to the expected scan
time for the modeled application.
86 33002479 10/2019
Ethernet Communication Services
FTP Server
Overview
The following information describes the services provided by the FTP Server. The FTP server is
available on all:
140 NOE 771 xx communications modules (including the NOE module)
CPU 651 x0 modules
FTP Server
The FTP server on the NOE module and CPU 651 x0s is available as soon as the module receives
an IP address. Any FTP client can log on to the module, which requires the client use the correct
user name and password.
The FTP Server can:
update the NOE module’s firmware by downloading a new Exec
provide error log visibility by uploading error log files
upload/download BOOTP server and SNMP configuration files
33002479 10/2019 87
Ethernet Communication Services
HTTP Server
The Modicon Quantum with Control Expert Ethernet modules’ Hypertext Transport Protocol
(HTTP) server is available as soon as the module receives an IP address.
Use the HTTP Server to:
1. view . . .
the module's Ethernet statistics
the controller and I/O information
the server information (BOOTP/DHCP/FDR)
the diagnostic information for some Ethernet services
2. configure the module's Ethernet services
Use Internet Explorer version 4.0 or later. For a complete list of services, see the Key Features
table (see page 44).
The HTTP server is protected with a default user name and password.
NOTE: The NOE 771 xx and CPU 651 xx support a maximum of 32 HTTP simultaneous
connections. Browsers may open multiple connections so 32 HTTP connections do not indicate 32
simultaneous users.
NOTE: The NOE 771 00 and NOE 771 01 modules do not support user downloaded Web pages.
You will need to purchase either the NOE 771 10, NOE 771 11, or the NWM 100 00 module to
support user downloaded Web pages.
88 33002479 10/2019
Ethernet Communication Services
Web Diagnostics
The embedded Web server provides Web pages to diagnose the following Transparent
Factory/Real Time services.
I/O Scanning (see page 81) status of all I/O Scanning services
status of individual scanned devices
actual I/O scanning rate
Messaging (see page 79) diagnostic information for Port 502 messaging
NOTE: All these pages are protected by the general HTTP password.
Web Configuration
Elsewhere in this guide is a description of the web configuration pages (see page 88).
33002479 10/2019 89
Ethernet Communication Services
Hot Standby
The Ethernet Hot Standby system consists of two identical Modicon Quantum systems. Each
Quantum system contains:
a Modicon Quantum Hot Standby with Control Expert controller (140 CPU 671 xx0),
(140 CPU 672 xx0) or (140 CPU 678 61)
a remote I/O head
NOE 771 xx modules (no more than six)
a power supply
The Hot Standby modules are connected to each other via a fiber-optic cable. Both remote I/O
heads are connected to the remote I/O network and to each other.
Schneider Electric recommends:
1. remote I/O networks use redundant cables (drops are not redundant)
2. switch connecting the NOEs to the network (available switches):
499NES17100
499NOS17100
90 33002479 10/2019
Quantum using EcoStruxure™ Control Expert
Ethernet Services
33002479 10/2019
Part II
Modicon Quantum with Control Expert Ethernet Modules Services
33002479 10/2019 91
Ethernet Services
92 33002479 10/2019
Quantum using EcoStruxure™ Control Expert
Start Communication with Control Expert
33002479 10/2019
Chapter 3
Start Communication with Control Expert
Introduction
This chapter tells you how to begin Ethernet network configuration with Control Expert.
33002479 10/2019 93
Start Communication with Control Expert
Section 3.1
How to Configure the Communication
Overview
This section describes how to configure the communication.
94 33002479 10/2019
Start Communication with Control Expert
33002479 10/2019 95
Start Communication with Control Expert
Configure Network
Configure Network
On the network folder, by a double-clicking action or by the Open item on contextual menu, the
editor of the corresponding communication screen is opened in order to set the specific network
services.
The figure shows the contextual menu to start network properties.
96 33002479 10/2019
Start Communication with Control Expert
Properties of a Network
Properties of a Network
The contextual menu proposes the user to see again the properties of a configured network. Here,
the user can change the NetLink name and the associated comment.
The figure shows the Ethernet property window:
33002479 10/2019 97
Start Communication with Control Expert
NOTE: If this removed network was previously attached to a communication module, this module
loses its link and it will work with its default parameters.
98 33002479 10/2019
Start Communication with Control Expert
Section 3.2
Control Expert Communication Links
Overview
This section presents the principle of communication implementation and describes the
relationship between software configuration of networks and the hardware configuration of the
network controllers.
33002479 10/2019 99
Start Communication with Control Expert
Introduction
The configuration of communication links between different devices with Control Expert includes
three different configuration parts.
configuration of the network controller
configuration of the logical network
configuration of network variables
Configuration
The communication configuration supports the free mode of Control Expert. That means the user
can first configure the module and then the communication or the user can configure the
communication and then the module.
This will be provided through a NetLink that must be selected in the module configuration. The
network variables including in the VAR folder are linked with a group name that defines an IP
domain over Internet network.
The illustration shows the three parts involved in communication configuration:
NetLinks
During Control Expert application design, the NetLinks are created and inserted on sub-folder
Communication under Network. These are the names of logical networks.
Under configuration folder, on the communication module node included in the current station, the
list of existing NetLinks is proposed to select and attach one network to one module. Only the
NetLink that can be managed by this module, are displayed in the list box on module configuration
screen. No NetLink can be edited and created here (no edit box), but this list contains at least the
No_Link field.
The following figure shows the window for the Ethernet link for the Quantum NOE module.
Section 3.3
Selecting the Ethernet Module
Introduction
This chapter contains the software pages for the NOE module.
General Description
After configuring Ethernet communication (see page 95), the Ethernet module parameters can be
configured.
When you select the model family, all the corresponding communication module configuration
options are displayed automatically. The module services allow the following settings to be made:
Setting Description
No Setting deactivated.
Yes Setting activated. Parameters are set using the Control Expert menu window.
Web Setting activated. Parameters are set using the configured NOE Web pages.
Control Expert menu window deactivated.
Note: Not available for every model family.
NOTE: The availability of the displayed settings depends on the selected model family and can
vary.
The screen shot shows an example of the menu window of the NOE Ethernet module (TCP/IP
10/100 Regular connection).
Parameter description:
Parameter Description
Model Family Quantum NOE Ethernet Module settings
Module Address Not used
Module Utilities For module service configuration options, see above
Module IP Address Overview of the IP address parameter set
After selecting the model family TCP/IP 10/100 Regular Connection, the following mask appears.
The image also displays the activated module services.
NOTE: The availability of the displayed register depends on the selected model family and can
vary.
After selecting the Yes option in module services, the tab corresponding to the module is activated.
Using Control Expert to Enable and Disable Firmware Upgrade & FDR and Web Access Services
Perform the following steps to enable or disable FTP/TFTP or HTTP services on the module.
Step Action
1 In the Control Expert Project Browser → Structural View, double-click the desired network in the
Communication → Networks directory to open the Network Editor.
2 Click the Security tab.
3 On the Security screen, choose the appropriate setting: (Enabled or Disabled) for the service or
services.
The edits will not take effect until they are successfully downloaded from your PC to the CPU and
from the CPU to the communication modules and network devices.
IP Configuration
General Description
The IP configuration tab enables you to configure IP address settings for the Quantum Ethernet
module. IP address settings become active after:
the hardware is connected
the configuration is downloaded to the PLC in the Quantum Ethernet module
The following figure shows the IP configuration for the Quantum Ethernet model family:
Selection Description
Configured Activate the IP address, subnet mask, and gateway address. The data
is activated after the configuration is downloaded to the PLC.
Client / Server The Quantum NOE Ethernet module receives its IP address parameter
through a BOOTP server on startup.
Ethernet Select the default protocol as Ethernet or 802.3.
configuration
Introduction
Ethernet messaging gives the user the opportunity to send and receive Ethernet messages. Data
traffic is handled by the client/server procedure.
Parameter description:
Setting Description
Connection configuration Activates general data transfer.
Access Activates data transfer between specific nodes.
IP Address Defines the node for the Ethernet Messaging procedure.
Access Control Activates or deactivates control of remote devices that are
attempting to open a TCP connection to the module.
Messaging Tab
The following procedure shows how to access the Messaging page:
Step Action
1 In the Control Expert project browser, go to the Structural view. Expand (+) the
Communication folder until you locate the name of the Ethernet logical network
associated with the module.
2 Right click the Ethernet logical network and select Open.
Result: The module configuration screen appears.
3 Select the Messaging tab. (See the illustration below.)
Configuration parameters can be accessed in two areas on the Messaging tab screen:
the Connection Configuration area
the Access Control area
Access Control
The Access Control box is used to activate or deactivate control of remote devices that are
attempting to open a TCP connection to the module. The functionality depends on whether the box
is checked or not:
checked: Access control management is activated and the Access column of the table is active
(no longer grayed out).
The module can only communicate to the addresses entered in the 128 available spaces in
the Slave IP Address column.
With the module in client mode it can only connect to remote devices selected by the Access
column in the Connection Configuration table.
unchecked: Access control management is inoperative and the Access column of the table is
not active (grayed out).
With the module in server mode, remote third-party devices can connect as clients (before
communication with the module) without being declared in the table.
NOTE: Access control is only effective on the TCP/IP profile and assists module operations in
server and client mode.
Section 3.4
Selecting the Ethernet Coprocessor
Introduction
This section describes configuring the Modicon Quantum with Control Expert coprocessor, 140
CPU 651 x0.
General Description
After configuring Ethernet communication (see page 95), the Ethernet module parameters can be
configured.
When you select the model family, all the corresponding communication-module configuration
options display automatically. The module services allow the following settings to be made:
Setting Description
No Setting deactivated.
Yes Setting activated. Parameters are set using the Control Expert menu window.
NOTE: The availability of the displayed settings varies and depends on the selected model family.
The screen shot shows an example of the menu window of the Ethernet module CPU 651 x0
(TCP/IP 10/100 Extended connection).
Parameter description:
Parameter Description
Model Family Modicon Quantum with Control Expert Ethernet module settings.
Module Address Not used.
Module Utilities For module service configuration options, see above.
Module IP Address Overview of the IP address parameter set.
After selecting the model family TCP/IP 10/100 Extended Connection, the following mask appears.
The image also displays the activated module services.
NOTE: The availability of the displayed register depends on the selected model family and can
vary.
After selecting the Yes option in module services, the tab corresponding to the module is activated.
General Description
The IP configuration tab enables you to configure the IP address settings. The settings are
activated after the connection to the hardware and the configuration is downloaded to the Modicon
Quantum with Control Expert Ethernet controller, 140 CPU 651 x0.
The diagram shows the IP configuration for the Modicon Quantum with Control Expert Ethernet
controller, 140 CPU 651 x0.
Selection Description
Configured Activate the IP address, Subnet mask and Gateway address. The data is activated
after the configuration is downloaded to the controller.
Client / Server The Modicon Quantum with Control Expert Ethernet controller receives its IP address
parameter through a BOOTP server on startup.
Introduction
Use the Messaging tab in Control Expert to send and receive messages via Ethernet. The data
traffic is handled by the client / server procedure.
The following illustration shows the Messaging dialog box.
Parameter description:
Setting Description
Connection configuration Activates general data transfer.
Access Activates data transfer between specific nodes.
IP address Defines the node for the Ethernet messaging procedure.
Access Control Activates or deactivates control of remote devices that are
attempting to open a TCP connection to the module.
Part III
Using the Modicon Quantum with Control Expert Ethernet Services
Purpose
This part describes how to use the Ethernet services available on Modicon Quantum with Control
Expert Ethernet modules.
Chapter 4
Transferring Data Using Communication Blocks
Introduction
This chapter describes how to transfer data to and from nodes on a TCP/IP network using
communication blocks. You transfer the data using either a special MBP_MSTR instruction or an
IEC Logic function. Operational statistics and error codes for reading and writing the controller
information are included.
Section 4.1
IEC Data Transfer Functions
Overview
This section describes several IEC function blocks that manage data transfer to and from nodes
on a TCP/IP network.
CREAD_REG
Function Description
The CREAD_REG block reads register data continuously from an addressed node via TCP/IP-
Ethernet.
EN and ENO can be projected as additional parameters.
NOTE: About this function block:
When programming this function, you must be familiar with the routing procedures used by your
network.
For technical reasons, this function block does not allow the use of ST and IL programming
languages.
Representation
Block representation:
Parameter Description
Description of parameters:
NOTE: This function block puts a heavy load on the network; therefore the network load must be
carefully monitored. If the network load is too high, the program logic should be reorganized in
order to work with the READ_REG function block, a variation of this function block that does not
operate in a continuous mode, but under command control.
SLAVEREG
SLAVEREG is the start of the area in the addressed slave from which the source data is read. The
source area always resides within the %MW word (4x register) area. SLAVEREG expects the
source reference as offset within that area. (In 4x registers, the leading "4" must be omitted. For
example, "59" (contents of the variables or value of the literal) = 40059).
The parameter can be specified as direct address, located variable, unlocated variable, or literal.
NO_REG
NO_REG is the number of registers to be read from the addressed slave (1 ... 100). The parameter
can be entered as a direct address, located variable, unlocated variable, or literal.
REG_READ
The REG_READ word parameter addresses the first register in a series of NO_REG registers,
listed one after the other, which are used as a destination data area. The parameter must be
entered as a direct address or located variable.
STATUS
Error code, see Runtime errors.
The STATUS parameter can be specified as direct address, located variable, or unlocated
variable.
CWRITE_REG
Function Description
The CWRITE_REG block writes data to a register area continuously, transferring data from the
PLC via TCP/IP Ethernet to an addressed slave.
EN and ENO can be configured as additional parameters.
NOTE: About this function block:
When programming this function, you must be familiar with the routing procedures used by your
network.
For technical reasons, this function block does not allow the use of ST and IL programming
languages.
Symbol
Block representation:
Parameter Description
Description of parameters:
SLAVEREG
SLAVEREG is the start of the area in the addressed slave to which the source data are written.
The destination area always resides within the %MW word (4x register) area. SLAVEREG expects
the destination address as offset within that area. In 4x registers, the leading 4 must be omitted.
For example, 59 (contents of the variables or value of the literal) = 40059.
The parameter can be specified as direct address, located variable, unlocated variable, or literal.
NO_REG
NO_REG is the number of registers to be written to slave processor (1...100). The parameter can
be specified as direct address, located variable, unlocated variable, or literal.
STATUS
Error code, see Runtime errors.
The STATUS parameter can be specified as direct address, located variable or unlocated variable.
REG_WRIT
The REG_WRIT word parameter addresses the first register in a series of NO_REG Successive
registers used as source data area.
The parameter must be entered as a direct address or located variable.
READ_REG
Function Description
Upon request, the READ_REG block reads a register area once (rising edge of the REQ input). It
reads data from an addressed slave via TCP/IP Ethernet.
EN and ENO can be projected as additional parameters.
NOTE: About this function block:
When programming this function, you must be familiar with the routing procedures used by your
network.
For technical reasons, this function block does not allow the use of ST and IL programming
languages.
Symbol
Block representation:
Parameter Description
Description of block parameters:
REQ
A rising edge triggers the read transaction.
The REQ parameter can be specified as direct address, located variable, unlocated variable, or
Literal.
SLAVEREG
SLAVEREG is the start of the area in the addressed slave from which the source data is read. The
source area always resides within the %MW word (4x register) area. SLAVEREG expects the
source reference as offset within that area. In 4x registers, the leading 4 must be omitted. For
example, 59 (contents of the variables or value of the literal) = 40059.
The parameter can be specified as direct address, located variable, unlocated variable, or literal.
NO_REG
Number of registers to be read from the addressed slave (1 ... 100).
The NO_REG parameter can be specified as direct address, located variable, unlocated variable,
or literal.
NDR
Transition to ON state for one program cycle signifies receipt of new data ready to be processed.
The NDR parameter can be specified as direct address, located variable, or unlocated variable.
ERROR
Transition to ON state for one program cycle signifies detection of a new error.
The ERROR parameter can be specified as direct address, located variable, or unlocated variable.
REG_READ
This word parameter addresses the first register in a series of NO_REG registers lying in series
used as destination data area.
The REG_READ parameter must be entered as a direct address or located variable.
STATUS
Error code, see Runtime errors.
The STATUS parameter can be specified as direct address, located variable or unlocated variable.
WRITE_REG
Function Description
Upon request, the WRITE_REG block writes a register area once (rising edge of the REQ input).
It transfers data from the PLC via TCP/IP Ethernet to an addressed slave.
EN and ENO can be configured as additional parameters.
NOTE: About this function block:
When programming this function, you must be familiar with the routing procedures used by your
network.
For technical reasons, this function block does not allow the use of ST and IL programming
languages.
Symbol
Block representation:
Parameter Description
Description of parameters:
REQ
A rising edge triggers the read transaction.
The REQ parameter can be specified as direct address, located variable or unlocated variable.
SLAVEREG
SLAVEREG is the start of the area in the addressed slave from which the source data is read. The
source area always resides within the %MW word (4x register) area. SLAVEREG expects the
source reference as offset within that area. In 4x registers, the leading 4 must be omitted. For
example, 59 (contents of the variables or value of the literal) = 40059.
The parameter can be specified as direct address, located variable, unlocated variable, or literal.
NO_REG
Number of registers to be read from the addressed slave (1...100).
The parameter can be specified as direct address, located variable, unlocated variable, or literal.
REG_WRIT
The REG_WRIT word parameter addresses the first register in a series of NO_REG registers used
as source data area.
The parameter must be entered as a direct address or located variable.
DONE
Transition to ON state for one program scan signifies data have been transferred.
The DONE parameter can be specified as direct address, located variable or unlocated variable.
ERROR
Transition to ON state for one program scan signifies detection of a new error.
The parameter can be specified as direct address, located variable or unlocated variable.
STATUS
Error code, see Runtime errors.
The parameter can be specified as direct address, located variable, or unlocated variable.
TCP_IP_ADDR
Function Description
The TCP_IP_ADDR block enables the input of TCP/IP addresses for the READ_REG
(see page 127), CREAD_REG (see page 121), WRITE_REG (see page 130), and CWRITE_REG
(see page 124) blocks. The address is transferred in the form of a data structure.
EN and ENO can be projected as additional parameters.
NOTE: When programming the TCP_IP_ADDR function, you must be familiar with your network’s
routing procedures.
Symbol
Block representation:
Parameter Description
Description of parameters:
Map_Idx
The MBP on Ethernet Transporter (MET) mapping index is given at the Map_Idx input. That is, if
MET is 6, the value appears as follows:
Slot_ID
If an NOE in the rack of a Quantum controller is addressed as destination node, the value at the
Slot_ID input represents the physical NOE slot. That is, if the NOE is plugged in at Slot 7 of the
rack, the value appears as follows:
NOTE: When using an integrated Ethernet CPU module such as the 140 CPU 651 x0, the slot ID
must be 254 (FE hex) regardless of the CPU slot.
AddrFld
If an NOE in the rack of a Quantum controller is addressed as a destination node, the value in the
High value byte represents the physical slot of the NOE and the Low value byte represents the
MBP on Ethernet Transporter (MET) mapping index. That is, if the NOE is inserted in slot 7 of the
rack and the MET mapping index is 6, the first element of the data structure looks as follows:
Section 4.2
MBP_MSTR
MBP_MSTR
Overview
This section describes the 14 different communication function provided in the MBP_MSTR
function block.
Block Description
Function Description
You can select one of 14 available network communication operations (see page 139) using the
MBP_MSTR function block.
The MBP_MSTR block is supported on various hardware platforms (see EcoStruxure™ Control
Expert, Communication, Block Library).
EN and ENO can be configured as additional parameters.
NOTE: Verify that the programmer is familiar with the routing procedures of your network when
programming an MBP_MSTR function block. Modbus Plus routing path structures are described in
detail in the communication architectures manual (see Communication Services and
Architectures, Reference Manual) and the Modbus Plus Network Planning and Installation Guide.
If TCP/IP or SY/MAX Ethernet routing is implemented (see Quantum using EcoStruxure™Control
Expert, TCP/IP Configuration, User Manual), use standard EtherNet IP router products.
CREAD_REG, CWRITE_REG, READ_REG, WRITE_REG, and MBP_MSTR function blocks use one data
transaction path and require multiple cycles to complete an operation. The number of transaction
paths available by module and by MAST cycle depends on the communication port used:
Modbus Plus embedded port or NOM modules support up to 4 blocks at the same time.
TCP/IP Ethernet embedded port support up to 4 blocks at the same time.
TCP/IP Ethernet NOE, NOC, and 140 CRP 312 00 modules support up to 16 blocks at the same
time.
More communication function blocks may be programmed on the same communication port.
However, a communication block exceeding the maximum number on that port is not serviced until
one of the transaction paths is available. Then, the next block on the same port becomes active
and begins using an available path.
NOTE: In FBD and LD sections, this function block can be used on the program level and with
derived function blocks (DFBs). When using DFBs, verify that the parameters CONTROL and
DATABUF are directly connected to the I/O pins of the DFB.
NOTE: A TCP/IP communication between a Quantum PLC and a Momentum PLC is only possible
when one read or write job is carried out in every cycle. If several jobs are sent per PLC cycle, the
communication stops without generating a detected error message in the status register of the
function block.
NOTE: In Quantum or Premium Hot Standby, to help prevent the former standby CPU from
executing communication functions (now in RUN offline state), add a condition on the status bits
to disable the function if the CPU is offline.
Example:
You can send MBP_MSTR.Enable:=(HSBY_NOEPLCMSTR_ON) AND (%SW61.1) AND NOT
(%SW61.0)
or
You can create a boolean variable, primary_state:=(%SW61.1) AND NOT (%SW61.0), and
insert it for executing the section
NOTE: In M580 Hot Standby, to help prevent the former standby CPU from executing
communication functions (now in RUN offline state), add a condition on the status bits to disable
the function if the CPU is offline.
Example:
You can set MBP_MSTR.Enable:=(HSBY_NOEPLCMSTR_ON AND
ECPU_HSBY_1.LOCAL_HSBY_STS.RUN_PRIMARY)
or
Use the boolean variable ECPU_HSBY_1.LOCAL_HSBY_STS.RUN_PRIMARY as condition
for executing the section
NOTE: Several copies of this function block can be used in the program. However, multiple
instancing of these copies is not possible.
Representation in FBD
Representation in LD
Input Parameters
Output Parameters
Runtime Error
In the event of a detected error occurring during an MBP_MSTR operation, a hexadecimal error code
is displayed in the CONTROL[2] register of the control block for one cycle.
NOTE: Function error codes (see EcoStruxure™ Control Expert, I/O Management, Block Library)
are network-specific.
NOTE: For a list of all block error codes and values, refer to the tables of error codes for the
communication library (see EcoStruxure™ Control Expert, Communication, Block Library).
where:
X indicates Yes
- indicates No
Summary
The structure of the MBP_MSTR control block varies according to the type of network you are using.
Structures for Modbus Plus, TCP/IP Ethernet, and SyMax Ethernet are described below.
Register Contents
CONTROL[1] Indicates an operation that is valid for Modbus Plus
CONTROL[2] Indicates the error status
CONTROL[3] Indicates the length, i.e., the number of data units transferred (max. 100)
CONTROL[4] Indicates MSTR operation-dependent information
CONTROL[5] Routing register 1: used to specify a destination node during network
transfer (routing path addresses one of five)
Most significant byte: source node address, i.e., the slot for the Modbus
Plus Network Options Module (NOM)
When using the Modbus Plus Port on the CPU, this byte must be set to 0
(regardless of the CPU slot).
Least significant byte: destination node address, i.e., a value that
represents a direct or a bridge address. If there is no bridge, this value
contains the destination node address. If there is a bridge, this value
contains the address of the bridge.
If the NOM is inserted in slot 7 on the module rack, the most significant byte
of routing register 1 looks as follows (value 0x0706):
Register Contents
CONTROL[1] Indicates an operation that is valid for TCP/IP
CONTROL[2] Indicates the error status
CONTROL[3] Indicates the length, i.e., the number of data units transferred (max. 100)
CONTROL[4] Indicates MSTR operation-dependent information
CONTROL[5] Routing register: used to specify a destination node during network transfer
Most significant byte: source node address, i.e., the NOE slot for the NOE
module
When using an integrated Ethernet on the CPU, this byte must be set to
254 (FE hex) regardless of the CPU slot.
Least significant byte: destination node address, i.e, a value that
represents a direct or bridge address. If there is no bridge the value in the
least significant byte is set to 0. If there is a bridge, this value contains the
MBP for the Ethernet mapping index (MET).
If the NOE is inserted in slot 7 on the module rack and the Ethernet
mapping index (MET) is 6, the routing register looks as follows (value
0x0706):
NOTE: CONTROL[10] and CONTROL[11] are used when configuring the MBP_MSTR block for a
Read/Write Data operation (function code 23).
Register Contents
CONTROL[1] Indicates an operation that is valid for SY/MAX
CONTROL[2] Indicates the error status
CONTROL[3] Indicates the length, i.e., the number of registers transferred (max. 100)
CONTROL[4] Indicates MSTR operation-dependent information
CONTROL[5] Routing register: used to specify a destination node during network transfer
Most significant byte: source node address, ie.e, the slot for the NOE
module
Least significant byte: destination node address, i.e, a value that
represents a direct or bridge address. If there is no bridge the value in the
least significant byte is set to 0. If there is a bridge, this value contains the
MBP for the Ethernet mapping index (MET).
If NOM is inserted in slot 7 on the module rack and the Ethernet mapping
index (MET) is 6, the routing register looks as follows (value 0x0706):
NOTE:
Error code 5055 can occur before a 503C error.
No remote device takes precedence over a timeout.
Read Data
Description
A read operation transfers data from a specified slave source device to a master destination device
on the network. The operation uses a master transaction path, and may require several cycles to
complete. To program an MBP_MSTR block to perform a write operation, use function code 2
(see page 139).
NOTE: Do not attempt to program an MBP_MSTR to read to its own station address. This action
causes the function block to generate an error in the CONTROL[2] register of the control block
(see page 140).
You can perform a read operation on a nonexistent slave register. The slave detects and logs the
status, which can last for several cycles.
NOTE: For Quantum PLC communication with a Premium/Atrium PLC, confirm that the addressing
is made with an offset of 1. In order to access an address object n of a Premium PLC, confirm that
the communication function of the Quantum PLC uses the n+1 address. IEC addressing starts at
0, and Modbus addressing starts at 1.
Network Implementation
The read operation can be performed on Modbus Plus, TCP/IP Ethernet, and SY/MAX Ethernet
networks.
Register Meaning
CONTROL[1] 2 = read data
CONTROL[2] Indicates the error status.
CONTROL[3] Number of registers to be read from the slave.
CONTROL[4] Determines the %MW starting register in the slave from which the data is read, e.g.,
1 = %MW1, 49 = %MW49.
CONTROL[5] Routing register 1 is used to specify the address (routing path address 1 of 5) of the node
... during a network transfer.
CONTROL[9] The last byte in the routing path that is not 0 is the destination node.
Register Meaning
CONTROL[1] 2 = read data
CONTROL[2] Indicates the error status.
CONTROL[3] Number of addresses to be read from the slave.
CONTROL[4] Determines the %MW starting register in the slave from which the data is read,
e.g., 1 = %MW1, 49 = %MW49.
CONTROL[5] Routing register
most significant byte: network adapter module slot
least significant byte: MBP on Ethernet Transporter (MET) mapping index
CONTROL[6] Each address contains 1 byte of the 32-bit IP address, where the MSB is in
... CONTROL[6] and the LSB is in CONTROL[9].
CONTROL[9]
Register Meaning
CONTROL[1] 2 = read data
CONTROL[2] Indicates the error status.
CONTROL[3] Number of addresses to be read from the slave.
CONTROL[4] Determines the %MW starting register in the slave to which the data is written,
e.g., 1 = %MW1, 49 = %MW49.
CONTROL[5] Routing register:
most significant byte: network adapter module slot
least significant byte: destination drop number
Write Data
Description
A write operation transfers data from a master source device to a specified slave destination device
on the network. The operation uses a master transaction path, and may require several cycles to
complete. To program an MBP_MSTR block to perform a write operation, use function code 1
(see page 139).
NOTE: Do not attempt to program an MBP_MSTR to write to its own drop address. This action
causes the function block to generate an error in the CONTROL[2] register of the control block
(see page 140).
You can perform a write operation to a nonexistent slave register. The slave detects and logs the
status, which can last for several cycles.
NOTE: For Quantum PLC communication with a Premium/Atrium PLC, confirm that the addressing
is made with an offset of 1. In order to access an address object n of a Premium PLC, confirm that
the communication function of the Quantum PLC uses the n+1 address. IEC addressing starts at
0, and Modbus addressing starts at 1.
Network Implementation
The write operation can be performed on Modbus Plus, TCP/IP Ethernet, and SY/MAX Ethernet
networks.
Register Meaning
CONTROL[1] 1 = write data
CONTROL[2] Indicates the error status.
CONTROL[3] Number of addresses sent to the slave.
CONTROL[4] Determines the %MW starting register in the slave to which the data is written,
e.g. 1 = %MW1, 49 = %MW49.
CONTROL[5] Routing register 1 is used to specify the address (routing path address 1 of 5) of
... the node during a network transfer.
CONTROL[9] The last byte in the routing path that is not 0 is the destination node.
Register Meaning
CONTROL[1] 1 = write data
CONTROL[2] Indicates the error status.
CONTROL[3] Number of addresses sent to the slave.
CONTROL[4] Determines the %MW start address of the slave to which the data is written.
CONTROL[5] Routing register:
most significant byte: network adapter module slot
least significant byte: MBP on Ethernet transporter (MET) mapping index
Register Meaning
CONTROL[1] 1 = write data
CONTROL[2] Indicates the error status.
CONTROL[3] Number of addresses sent to the slave.
CONTROL[4] Determines the %MW starting register in the slave to which the data is written,
e.g., 1 = %MW1, 49 = %MW49.
CONTROL[5] Routing register:
most significant byte: network adapter module slot
least significant byte: destination drop number
Description
A Get Local Statistics operation reads the data from the local node in one cycle and does
not require a master transaction path.To program an MBP_MSTR block to
Get Local Statistics, use function code 3 (see page 139).
Network Implementation
A Get Local Statistics operation can be performed on Modbus Plus and TCP/IP Ethernet
networks (see page 159).
Register Meaning
CONTROL[1] 3 = get local statistics
CONTROL[2] Indicates the error status
CONTROL[3] Number of addresses to be read from local statistics (1 ... 54)
Note: The size of databuf must be at least the size of this entry.
CONTROL[4] First address from which the statistics table must be read (Reg1=0)
CONTROL[5] Routing register 1 is used to specify the address (routing path address 1 of
5) of the node during a network transfer.
The last byte in the routing path that is not 0 is the destination mode.
Register Meaning
CONTROL[1] 3 = get local statistics
CONTROL[2] Indicates the error status
CONTROL[3] Number of addresses to be read from local statistics (1 ... 38)
Note: The size of databuf must be the size of this entry.
CONTROL[4] First address from which the statistics table must be read (Reg1=0)
CONTROL[5] Routing register
Most significant byte: Network adapter module slot
CONTROL[6] Not used
...
CONTROL[9]
Description
A clear local statistics operation clears the values from words 13 ... 22 in the statistics table of the
local node. The operation is carried out in one cycle and does not require a master transaction
path. To program an MBP_MSTR block to clear local statistics, use function code 4 (see page 139).
Network Implementation
A clear local statistics operation can be performed on Modbus Plus and TCP/IP Ethernet networks
(see page 159).
Register Meaning
CONTROL[1] 4 = clear local statistics
CONTROL[2] Indicates the error status
CONTROL[3] Reserved
CONTROL[4] Reserved
CONTROL[5] Routing register 1 is used to specify the address (routing path address 1 of
5) of the node during a network transfer.
The last byte in the routing path that is not 0 is the destination mode.
Register Meaning
CONTROL[1] 4 = clear local statistics
CONTROL[2] Indicates the error status
CONTROL[3] Reserved
CONTROL[4] Reserved
CONTROL[5] Routing register
Most significant byte: network adapter module slot
CONTROL[6] Reserved
...
CONTROL[9]
Description
A get remote statistics operation can be used to read data from remote nodes on the network. With
each query, the remote communications processor supplies a complete table of statistics even if
the query does not refer to the entire table. It then copies only the words that you queried into
identified $MW addresses.
An operation can take several cycles to complete; it does not require a master data transaction
path. To program an MBP_MSTR block to get remote statistics, use function code 7 (see page 139).
Network Implementation
A get remote statistics operation can be performed on Modbus Plus and TCP/IP Ethernet
networks.
Register Meaning
CONTROL[1] 7 = get remote statistics
CONTROL[2] Indicates the error status
CONTROL[3] Number of addresses to be read from the statistics data field (1 ... 54).
Note: The size of databuf must be at least the size of this entry.
CONTROL[4] First address from which the node statistics must be read. The number of
available statistics registers cannot be exceeded.
CONTROL[5] Routing address 1 ... 5 of the node.
... The last byte in the routing path that is not 0 is the destination node.
CONTROL[9]
Register Meaning
CONTROL[1] 7 = get remote statistics
CONTROL[2] Indicates the error status
CONTROL[3] Number of addresses to be read from the statistics data field (1 ... 38).
Note: The size of databuf must be at least the size of this entry.
CONTROL[4] First address from which the node statistics must be read. The number of
available statistics registers cannot be exceeded.
CONTROL[5] Routing register
Most significant byte: network adapter module slot
CONTROL[6] Each address contains 1 byte of the 32-bit IP address, where the value in
... CONTROL[6] is the MSB and the value in CONTROL[9] is the LSB.
CONTROL[9]
Description
A clear remote statistics operation clears remote-node values from words 13 ... 22 in the statistics
table of the local node. It uses a master transaction path and may require several cycles to
complete. To program an MBP_MSTR block to perform a clear remote statistics operation, use
function code 8 (see page 139).
Network Implementation
A clear remote statistics operation can be performed on Modbus Plus and TCP/IP Ethernet
networks (see page 159).
Register Meaning
CONTROL[1] 8 = clear remote statistics
CONTROL[2] Indicates the error status
CONTROL[3] Reserved
CONTROL[4] Reserved
CONTROL[5] Routing register 1 is used to specify the address (routing path address 1 of
... 5) of the destination node during a network transfer.
CONTROL[9] The last byte in the routing path that is not 0 is the destination mode.
Register Meaning
CONTROL[1] 8 = clear remote statistics
CONTROL[2] Indicates the error status
CONTROL[3] Reserved
CONTROL[4] Reserved
CONTROL[5] Routing Register
Most significant byte: network adapter module slot
CONTROL[6] Each address contains one byte of the 32-bit IP address, where the MSB
... is in CONTROL[6] and the LSB is in CONTROL[9].
CONTROL[9]
Word Meaning
00 to 02 MAC address Word Contents
e.g. MAC address 00 00 54 00 12 34 is 00 00 00
displayed as follows: 01 54 00
02 12 34
03 Board status (refer to the following table)
04 and 05 Number of receiver interrupts
06 and 07 Number of transfer interrupts
08 and 09 Transfer timeout error count
10 and 11 Collision detection error count
12 and 13 Omitted packets
14 and 15 Memory error count
16 and 17 Number of restarts performed by the driver
18 and 19 Receive framing error count
20 and 21 Overflow error count receiver
22 and 23 Receive CRC error counter
24 and 25 Receive buffer error counter
26 and 27 Transfer buffer error counter
28 and 29 Transfer bin underflow counter
30 and 31 Late collision counter
32 and 33 Lost carrier counter
34 and 35 Number of retries
36 and 37 IP address Word Contents
e.g. the IP address 198.202.137.113 (or 36 89 71
C6 CA 89 71) is represented as follows: 37 C6 CA
Bit # Definition
15 0 = Link LED off 1 = Link LED on
14 0 = Appl LED off 1 = Appl LED on
13 0 = twisted pair 1 = fiber
12 0 = 10 Mbit 1 = 100 Mbit
11 ... 8 (Reserved)
7 ... 4 Module type (see table, below)
3 (Reserved)
2 0 = half duplex 1 = full duplex
1 0 = not configured 1 = configured
0 0 = not running 1 = running
NOTE: Bits are numbered from right to left, starting with bit 0 (low bit). For example, PLC running
= 0000 0000 0000 0001 and LED connection = 1000 0000 0000 0000.
The following table describes the word bit definitions for board status for the:
140 NOE 771 x1, version 3.5
140 NOE 771 x0, versions 1.02 and 2.0
140 CPU 651 x0
Bit # Definition
15 ... 12 Module type (see table below)
11 (Reserved)
10 0 = half duplex 1 = full duplex
9 0 = not configured 1 = configured
8 0 = PLC not running 1 = PLC/NOE running
7 0 = Link LED off 1 = Link LED on
6 0 = Appl LED off 1 = Appl LED on
5 0 = twisted pair 1 = fiber
4 0 = 10 Mbit 1 = 100 Mbit
3 ... 0 (Reserved)
NOTE: Bits are counted from right to left, starting with bit 0 (low bit). For example, PLC running =
0x0100, Application LED = 0x0040, and LED Connection = 0x0080.
Description
A reset optional module operation causes a Quantum NOE Ethernet communications module or
the Ethernet port on a 140CPU65150/60 CPU module to enter a cycle that resets its working
environment. To program an MBP_MSTR block to perform a reset option module operation, use
function code 10 (see page 139).
Network Implementation
A reset optional module operation can be performed on TCP/IP Ethernet (see page 159) and
SY/MAX Ethernet networks.
Register Meaning
CONTROL[1] 10 = reset optional module
CONTROL[2] Indicates the error status
CONTROL[3] No significance
CONTROL[4] No significance
CONTROL[5] Routing register (see page 141)
CONTROL[6] No significance
...
CONTROL[9]
Register Meaning
CONTROL[1] 10 = reset optional module
CONTROL[2] Indicates the error status
CONTROL[3] No significance
CONTROL[4] No significance
CONTROL[5] Routing register (see page 142)
CONTROL[6] No significance
...
CONTROL[9]
Read CTE
Description
A read CTE operation reads a specified number of bytes from the Ethernet configuration extension
table in the specified buffer of PLC memory. These bytes start with a byte offset at the CTE table
start. The CTE table contents are displayed in the DATABUF output parameter (see page 138). To
program an MBP_MSTR block to perform a clear remote statistics operation, use function code 11
(see page 139).
Network Implementation
A read CTE operation can be performed on TCP/IP Ethernet and SY/MAX Ethernet networks.
Register Meaning
CONTROL[1] 11 = read CTE
CONTROL[2] Indicates the error status
CONTROL[3] The length setting: a value from 12 to 37
CONTROL[4] No significance
CONTROL[5] Routing register
Least significant byte = mapping index
Either a value displayed in the byte of the register or is not used.
or Most significant byte = network adapter module slot
CONTROL[6]... No significance
CONTROL[9]
Register Meaning
CONTROL[1] 11 = read CTE
CONTROL[2] Indicates the error status
CONTROL[3] Number of words transferred
CONTROL[4] Byte offset in the PLC register structure, specifying from where the CTE
bytes are read
CONTROL[5] Routing register
MSB: slot of the NOE module
CONTROL[6] Terminator: FF hex
...
CONTROL[9]
Write CTE
Description
A write CTE operation writes the CTE configuration table from the specified data (DATABUF) to a
specified Ethernet configuration extension table or to a specific slot. To program an MBP_MSTR
block to perform a write CTE operation, use function code 12 (see page 139).
Network Implementation
A write CTE operation can be performed on TCP/IP Ethernet (see page 159) and SY/MAX
Ethernet networks.
Register Meaning
CONTROL[1] 12 = write CTE
CONTROL[2] Indicates the error status
CONTROL[3] The length setting: a value from 12 to 37.
CONTROL[4] No significance
CONTROL[5] Routing register
Least significant byte = mapping index
Either a value displayed in the byte of the address or is not used.
or
Most significant byte = network adapter module slot
CONTROL[6] No significance
...
CONTROL[9]
Register Meaning
CONTROL[1] 12 = Write CTE (Config extension table)
CONTROL[2] Indicates the error status
CONTROL[3] Number of words transferred
CONTROL[4] Byte offset in the PLC address structure specifying where the CTE bytes
are written
CONTROL[5] Routing register
Most significant byte = NOE module slot
Least significant byte = Destination drop number
CONTROL[6] Terminator: FF hex
CONTROL[7] No significance
...
CONTROL[9]
Send Email
Description
The electronic mail notification service allows controller-based projects to report alarms or events.
The controller monitors the system and dynamically creates an electronic mail message, which
alerts local or remote users.
A user-defined event or condition triggers the MSTR block to create a message. Each message
uses one of three user-defined headers. Each message sent from the controller can contain text
and variable information (with a maximum of 238 bytes).
The project selects the appropriate header. Each header contains:
sender name
list of recipients
subject
To program an MBP_MSTR block to send email, use function code 13 (see page 139).
Network Implementation
A send email operation can be performed on a TCP/IP Ethernet network.
Register Meaning
CONTROL[1] 13 = send Email
CONTROL[2] Indicates the email-specific error codes (see EcoStruxure™ Control
Expert, I/O Management, Block Library)
CONTROL[3] Number of words transferred
CONTROL[4] Not used
CONTROL[5] High byte: slot address of the NOE module or 0xFE for the 140 CPU 651 60
Low byte: always 0
CONTROL[6] Not used
...
CONTROL[9]
Register Contents
DATABUF 1 The mail header is the least significant byte with a value of 1, 2, or
3.
The most significant byte contains the number (n) of characters in
the subject, a value between 0 and 238.
DATABUF 2 The data (in ASCII format) that will be copied into the Email
... message.
DATABUF 119 The first n characters are added to the configured Email subject.
The remaining characters (2 * N -2 - n) are part of the message
body, where N is the number of words transferred.
At a Glance
Use MSTR operation 15 to send generic Modbus requests on the network.
NOTE: This operation is not available on Modbus Plus ports (embedded port on CPU or NOM
modules) and the embedded Ethernet port on a CPU.
Block Operation
The MBP_MSTR block can send requests and receive responses up to 253 bytes long.
For the operation, refer to Block Operation (see page 136):
When the ENABLE input pin is turned ON, operation 15 begins.
If the ABORT input pin is turned ON or if the ENABLE input pin is turned OFF, the operation
ends.
The ACTIVE output pin is ON during the operation.
The ERROR output pin turns ON if the operation aborts without success.
The SUCCESS output pin turns ON if the operation completes with success.
The CONTROL and DATABUF output pins define the operation (refer to the Control Block
(see page 173) and Data Buffer (see page 174)).
EN and ENO can be configured as additional parameters.
Control Block
The format of the Control block is described in the following table:
Word Description
CONTROL[1] 15 = Send Modbus Request
CONTROL[2] Indicates detected error status
CONTROL[3] DATABUF length (WORDs)
CONTROL[4] Offset for the beginning of the response in the DATABUF (WORDs).
NOTE: To avoid overwriting the request, the Response Offset value
multiplied by 2 must be greater than the Request Length
(CONTROL[10]).
CONTROL[5] Routing register:
High byte = Ethernet communication module slot
Low byte = MBP on Ethernet transporter (MET) mapping index (also
known as Unit ID)
CONTROL[6] Byte 4 of the IP address (MSB)
CONTROL[7] Byte 3 of the IP address
CONTROL[8 Byte 2 of the IP address
CONTROL[9] Byte 1 of the IP address (LSB)
Word Description
CONTROL[10] Length of the DATABUF Request data (bytes)
CONTROL[11] Length of the DATABUF Response received (bytes)
NOTE: This is read only, it is set by option module after operation
completion.
Data Buffer
The MODBUS protocol defines a simple protocol data unit (PDU) independent of the underlying
communication layers.
The data buffer (DATABUF) consists of contiguous registers that include both the Modbus Request
PDU and the Modbus Response PDU:
CAUTION
LOSS OF DATA
Verify that the Response Offset is greater than the Data Request Length.
Failure to follow these instructions can result in injury or equipment damage.
NOTE: Both the Request and Response must be structured in little endian order. Each word of 2
bytes of data in little endian format, where the least significant byte is stored in the smallest memory
address.
Modbus Request
The Modbus Request PDU format is:
Modbus Response
The Modbus Response PDU format is:
Modbus Specification
The standard Modbus function codes are defined in the MODBUS Application Protocol
Specification, V1.1b, which can be downloaded from www.modbus-ida.org.
At a Glance
Use MBP_MSTR operation 16 to close a Modbus TCP/IP connection on the network.
NOTE: This operation is not available on Modbus Plus ports (embedded port on CPU or NOM
modules).
Block Operation
The MBP_MSTR block can send requests and receive responses up to 253 bytes long. For block
operation, refer to the block description (see page 136):
When the ENABLE input pin is turned ON, operation 15 begins.
If the ABORT input pin is turned ON or if the ENABLE input pin is turned OFF, the operation
ends.
The ACTIVE output pin is ON during the operation.
The ERROR output pin turns ON if the operation aborts without success.
The SUCCESS output pin turns ON if the operation completes with success.
The CONTROL and DATABUF output pins (see page 138) define the operation.
EN and ENO can be configured as additional parameters.
Control Block
The format of the CONTROL block is described below:
Description
Use MSTR Operation 17 (Change Modbus Plus Address) to change the Modbus Plus address
associated with the embedded Modbus Plus port of the CPU.
On Low End CPUs, this function overrides the address switch (the hardware rotary switch behind
the CPU) as long as the CPU is powered on. The address of hardware switch is restored when the
CPU is restarted.
On High End CPUs, a new address set with this function is saved in the configuration table and is
restored on subsequent CPUs starts.
Setting an address to a station that is already used by another station on the network disconnects
the station already on the network and may cause unpredictable operation on the network.
CAUTION
UNINTENTIONAL EQUIPMENT OPERATION
Ensure that the Modbus Plus address to be set is not assigned to another station before using
Operation 17.
Failure to follow these instructions can result in injury or equipment damage.
Network Implementation
The Operation 17 can only be performed for a Modbus Plus CPU embedded port. This operation
is not available on the Modbus Plus ports of NOM modules.
Control Block
The following table describes the format of the Operation 17 Control Block:
Register Meaning
Control[1] 17 (Change Modbus Plus Address operation)
Control[2] Detected error status, see Modbus Plus, SY/MAX, and
Ethernet TCP/IP Error Codes (see page 143)
Control[3] 16#1234
Control[4] 16#5678
Control[5] 16#00AA
Control[6 16#00BB
Control[7] 16#00CC
Control[8] 16#00DD
Control[9] 16#00EE
NOTE: The constant values in CONTROL[3] to CONTROL[9] consist of a signature that prevents
unintentional use of this operation.
Data Buffer
The following table describes the format of the Operation 17 Data Buffer:
Register Meaning
DADABUF[1] Low byte: new address (range: 1 to 64)
Read/Write Data
Introduction
In a single transaction, the MSTR read and write operations can transfer data from a master source
device to a specified slave destination device, then transfer data from this specified slave source
to the master. It uses a master transaction path and may require several cycles to complete. To
program an MBP_MSTR block to perform a combined read/write operation, use function code 23
(see page 139).
The combined read/write operation can be used only with these models:
Quantum: NOE 771 01 (3.0 or later) or NOE 771 11 (3.0 or later)
Momentum: M1E CPU (1.0 or later)
Register Content
CONTROL[1] 23 = read/write data.
CONTROL[2] Indicates the error status.
CONTROL[3] Number of registers to be sent to the slave.
CONTROL[4] Specifies the %MW starting register in the slave to which the data will be
written, e.g. 1 = %MW1, 49 = %MW49.
CONTROL[5] Routing register:
Most significant byte: network adapter module slot.
Least significant byte: MBP on Ethernet Transporter (MET) mapping
index.
CONTROL[6] Each address contains 1 byte of the 32-bit IP address, where the MSB is
... in CONTROL[6] and the LSB is in CONTROL[9].
CONTROL[9]
CONTROL[10] Number of registers to be read from slave.
CONTROL[11] Specifies the %MW starting register in the slave from which the data is
read, e.g. 1 = %MW1, 49 = %MW49.
NOTE:
When configuring the MBP_MSTR block for a read/write data operation, note that
The DATABUF output parameter is used to store, in the following sequence, both:
1 the data to be written
2 the data to be read
The size of the DATABUF output parameter must equal the combined size of the data to be
written and the data to be read; if the size is smaller, data will be overwritten and may be lost.
Both the CONTROL and DATABUF parameters must be stored at located addresses, for example
%MW addresses.
Description
An Enable Disable HTTP or FTP/TFTP Services operation changes the enabled state of
the module’s HTTP or FTP/TFTP services.
Network Implementation
An Enable Disable HTTP or FTP/TFTP Services operation can be performed on TCP/IP
Ethernet networks (see page 159).
Register Meaning
CONTROL[1] 65520 (dec) FFF0 (hex) = enable / disable HTTP or FTP/TFTP
CONTROL[2] Indicates the error status. Possible return codes include:
0x000 (Success): MSTR block with operational code 65520 was called and
the enabled state of HTTP or FTP/TFTP was changed.
0x5068 (Busy): MSTR block with operational code 65520 was called within
2 seconds of the previous call (regardless of return code from previous
call).
0x4001 (Same state): MSTR block with operational code 65520 was called
to change the enabled state of HTTP and FTP/TFTP to the states they were
already in.
0x2004 (Invalid data): MSTR block with operational code 65520 was called
and the data in the control block did not match the specifications.
0x5069 (Disabled): If the HTTP or FTP/TFTP service was already disabled
via the Control Expert interface when the MSTR block with operational
code 65520 was called to change the state of the disabled service.
CONTROL[3] Set this register to 1
CONTROL[4]
CONTROL[5] Module slot number and destination ID
High byte = Module slot number communication module slot
Low byte = Destination ID
CONTROL[6] Request mode
Bit 0 (LSB) = 1: Enable FTP/TFTP
Bit 0 (LSB) = 0: Disable FTP/TFTP
Bit 1 = 1: Enable HTTP
Bit 1 = 0: Disable HTTP
Register Meaning
CONTROL[7] Set this register to 0
CONTROL[8]
CONTROL[9]
HTTP, FTP, and TFTP service state changes made by MSTR with operation code 65520 (dec) 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:
Chapter 5
Global Data (Publish/Subscribe) Utility
Introduction
The material in this section presents the Global Data (Publish/Subscribe) utility available on the
following modules.
140 NOE 771 01
140 NOE 771 11
140 CPU 651 x0
Overview
Global Data service is a real-time publisher/subscriber mechanism that provides the most efficient
data exchange for PLC application coordination.
Devices that support Global Data are arranged in a distribution group for the purpose of application
variable exchange and synchronization. Each Global Data device can publish up to one network
(application) variable and subscribe to up to 64 network (application) variables.
The Quantum NOE’s embedded Global Data Configuration Web page provides a configuration
screen (see page 192) to determine which and how many application variables are exchanged
with this service. After configuration, exchanges between all stations belonging to the same
distribution group are done automatically.
The Global Data service uses %MW (4x registers) or unlocated variables for Global Data
exchanges.
Global Data has an advantage over client/server services when more than one subscriber is
receiving the same data since only one transaction is necessary for all subscribers to receive the
data. There are two benefits:
the reduction of overall network traffic
tighter synchronization of multiple subscribers
Parameter Limit
Maximum number of publish variables per 1
device
Maximum size for the publish variable 512 registers = 512 Words (16 bits) = 1024 bytes
Maximum number of subscription variables 64 (63 if this device is publishing)
per device
Maximum size for the subscribe variables per 2048 registers = 2048 Words (16 bits) = 4096 bytes
device
Parameter Description
Parameter Checking Reserved
Variable Id Represents the Data ID on the NOE’s Global Data Configuration Web page
Symbol Symbolic name for Global Data exchange.
Length Words (Registers) Length of Global Data information. Number of %MW words (4x registers) or unlocated
variables.
Device Number Number of devices (up to 64) for the Global Data network.
Variable Public. Status Automatic information of the correct publication status of the Global Data network. Only
by using the Microsoft ExcelTM spreadsheet. Information per symbol.
Device Publication Status Automatic information of the correct publication status of the Global Data network. Only
by using the Microsoft ExcelTM spreadsheet. Information per device.
Total Publication Size per Publication size for the specific node. The maximum publication size is 512 words
Node (registers) per node
Total Subscription Size per Subscription size for the specific node. The maximum subscription size is 2048 words
Node (registers) per node
Group IP Address Enabled IP address for multicast networking. Identifies the stations distribution group. The
address range is from 224.0.0.0 to 239.255.255.255
Multicast Filtering Enabled A check box for Ethernet switches that support multicast filtering.
Default Address for %MW (4x register) address for the Health bits. This is the memory area where the
Health%MW (4x register) Health bits are stored. It has the size of 4 words (registers).
Distribution Period Is the minimum number of controller scan times before an update will occur.
Parameter Description
Health Timeout Is the maximum time between received subscriptions before a subscription is declared
unhealthy (faulty). The value is measured in milliseconds and can be set from 50 to
15000 ms in 50 ms increments.
Data Zone The starting address for the data. This are the registers where the data information are
stored.
Multicast Filtering
Overview
Your NOE may offer the multicast filtering functionality.
The global data service synchronizes several stations located in a distribution group. A distribution
group is a set of stations identified by using the same IP multicast address for all stations in the
group. By using the same IP address for multiple devices, multicast exchanges can be used to
distribute global data. Several independent distribution groups can coexist on the same sub-
network. Each distribution group possesses its own unique IP multicast address.
Early versions of switches treat multicast packets as a broadcast, thereby broadcasting to all nodes
and suppressing all benefits of both switching and multicasting. Newer versions of switches
provide automatic multicast filtering, and consequently only forward multicast traffic to ports that
are connected to registered end stations.
Reducing Traffic
Multicast filtering helps to reduce the traffic on a network, because broadcasts are sent only to
interested, or subscribed, devices.
For distributed applications and one to many communications, multicast affords advantages over
unicast because it:
utilizes the network bandwidth more efficiently
sends a single transmission instead of multiple transmissions.
reduces collisions
optimizes the performance of Ethernet module processing
Switch Description
499NES17100 Managed Switch with 7 ports 10/100 BASE-TX
499NOS17100 Managed Switch with 5 ports 10/100 BASE-TX and 2 ports 100 BASE-FX
Introduction
Global data configuration is carried out in the network configuration as well as the data editor. The
variables for the publish/subscribe procedure are configured in the data editor.
The screen shot shows the network configuration global data configuration settings:
Parameter description:
Parameter Description
Health time out After this time period expires, the received data becomes invalid.
Group address Class D multicast IP address. All nodes in the global data procedure
use the same multicast address for distributing or receiving data. The
address range is: 224.0.0.0 to 239.255.255.255.
Distribution period Time after which the data is received or sent. Minimum scan time of
the PLC.
Group name Logical name. Defines the varibale allocation to different
communication configurations in the variable editor.
Health bit block Address for retrieving the status information of the global data
procedure.
Parameter Description
Multicast filtering Activates an Ethernet module that supports multicast filtering. From
the drop down list, select:
None: disable both GMRP & IGMP
(Data will be sent to all end devices in the network.)
GMRP
Make sure your client, server and switches, and routers support
and enable GMRP.
IGMP V1
Make sure your client, server and switches, and routers support
and enable IGMP.
Note: The following modules support IGMP V1:
140 NOE 771 01 V4.4 or later
140 NOE 771 11 V4.4 or later
140 CPU 651 50/60 V2.7 or later
NOTE: The IGMP and None features are only available in Unity 4.1
or later.
NOTE: Unity Pro is the former name of Control Expert for version
13.1 or earlier.
NOTE: A Quantum PLC does not update health bits in STOP mode.
The screen shot shows an image of the data editor:
Parameter description:
Parameter Description
Name Variables symbols
Type Variable type
Address Variable address
Global Data Type of Global Data Variable. Options: No/Publish/Subscribe
Group Group name for allocating the variables of the existing network
description. When creating the different Ethernet networks, a logical
connection is arranged here between the network and the variable
declaration.
ID Variable ID
Step Action
1 Select one NOE.
2 Using your browser, navigate to that NOE’s Global Data Configuration page.
Follow these links: | Setup | Global Data |
3 Enter the configuration’s variable IDs, symbols (description), and lengths.
4 Click the Update Global Data Configuration button to update the file. This creates
the file glbdata.ini.
Full path follows:
ftp://NOE_IP_ADDRESS/wwwroot/conf/glbdata/glbdata.ini
Note: You substitute NOE_IP_ADDRESS with an address like 192.168.000.010.
Please check the address with your system administrator.
5 Using the FTP process, upload the glbdata.ini file to a PC. (See the information
below at Uploading a glbdata.ini file.)
6 Stop each controller before you do the customization.
7 Using the same path, download the glbdata.ini file to the other devices. (See
the information below at Downloading a glbdata.ini file.)
8 Connect your Web browser to each device to customize start address and the
Publish/Subscribe setting.
NOTE: The Global Data Configuration page is populated with data from the glbdata.ini
configuration file.
Step Action
1 At the DOS prompt type FTP followed by the IP address and press Enter.
2 At the User prompt type FTP Username and press Enter.
3 At the password prompt enter your FTP Password and press Enter.
4 At the FTP prompt type cd wwwroot/conf/glbdata and press Enter.
5 At the FTP prompt type get and press Enter.
6 At the local file prompt type glbdata.ini and press Enter.
7 At the remote file prompt type glbdata.ini and press Enter.
Step Action
1 At the DOS prompt type FTP followed by the IP address and press Enter.
2 At the User prompt type the FTP username and press Enter.
3 At the password prompt enter your FTP Password and press Enter.
4 At the FTP prompt type cd wwwroot/conf/glbdata and press Enter.
5 At the FTP prompt type put and press Enter.
6 At the local file prompt type glbdata.ini and press Enter.
7 At the remote file prompt type glbdata.ini and press Enter.
Step Action
1 Verify all controllers are running.
2 Look at the health of all variables using the Global Data Diagnostic page.
Follow these links: | Diagnostics | NOE Diagnostics | Global Data
Chapter 6
I/O Scanner
I/O Scanner
Introduction
This chapter discusses the Ethernet modules’ I/O scanner capabilities.
Introduction
The I/O Scanner is a feature that resides in Ethernet (NOE 771 00, -01, -11, and CPU 651 x0)
modules. The I/O Scanner allows, through a controller, repeated reading from and/or writing to
scanned devices.
Use the I/O scanner to transfer data between network devices.
Configure the I/O Scanner with Schneider Electric’s programming package Control Expert. (I/O
Scanner configuration information (see page 204) appears elsewhere in this guide.)
NOTE: We recommend you program with words if your project involves both 140 CPU 651 x0
modules and 140 NOE 771 01 modules in the same application. Due to the unique manner in
which each of these modules were developed, they both correctly scan towards %I, but they
interpret the data in different programming languages. The NOE module reads in IEC format;
whereas, the controller module reads in LL984 format.
Parameter Value
Max. No. of Devices 64: 140 NOE 771 00 (Version 2.2 or earlier)
128: 140 NOE 771 00 (Version 3.0 or later), 140 NOE 771 01, and
140 NOE 771 11 only
128: 140 CPU 651 x0
Max. No. of Input Words 4000
Max. No. of Output Words 4000
Health Timeout Value User configured: 1...65535 ms in 1 ms increments
Last Value (Input) User configured (Zero or Hold)
IP Address User configured
IP address of scanned device (Slave IP)
Local and Remote Register User configured
Reference
Repetitive Rate The rate at which data will be scanned, from 0...65535 in multiples of:
If you are running Unity Pro V2.0 or higher
140 NOE 771 01/11: 16 ms
140 CPU 651 x0: 10 ms
Elsewhere in this guide is information about I/O scan response times for high-performance
communications modules (see page 233).
Registers The Device Control Block consists of registers either 8 single words or 4 double
words. Contents of the registers are mapped in the controller’s memory. Each bit
corresponds to an entry in the table (see the tables below.)
Disabling Devices Each I/O Scanner device can be disabled. To disable individual devices:
1. Select the Device Control Block option on the I/O Scanner tab in Control
Expert. (Insert a check mark in the box.)
2. Set the associated bit = 1.
Mapping Device Control See the table for mapping entry numbers to bits.
Block Bits to I/O Scanner Each entry number represents a logical device on the network.
Entry Numbers (#)
Setting Bits If Device Control Block bit is set to
0 = Device is enabled
1 = Device is disabled
Mapping Device Control Block Bits to I/O Scanner Entry Numbers (#)
NOTE: Bits are counted from right to left starting from bit 0 (low bit). Examples: to configure
%MD1:4 as a device control block in the I/O Scanner table, use %MW2, bit 15 to enable or disable
table entry 1. Use %MW3, bit 15 to enable or disable table entry 17.
NOTE: Quantum and Premium co-processors follow Premium Ethernet module control bit
operation.
NOTE: Bits are counted from right to left starting from bit 0 (low bit). For example, to configure
%MD1:4 as a device control block in the I/O scanner table, use %MD1[0], bit 31 to enable or
disable table entry 1. Use %MD1[1], bit 15 to enable or disable table entry 17.
NOTE: This screen shows I/O Scanner services for an 140 NOE 771 01 or -11 module. The I/O
Scanner screen is slightly different for the CPU 651 x0 module, which does not display a Health
Block field.
Health Block
The Health Block field (number 1 in previous figure) lets you define the first word or bit in a health
table. That table can be up to 8 words (%IW) or 128 bits (%I) in length. Each bit in the table
represents the status of an individual device. The following table shows how the bits are displayed
based on the data type you use:
By default, the table comprises words starting at %IW1.0. If you want to set the table to bits, you
need to specify a %I value in an increment of 16 (%I1, %I16, %I32, etc.).
NOTE: The Health Block field is available only for the NOE 771 00, -01, and -11. It is not available
for the CPU 651 x0.
NOTE: For Safety Monitor applications, the Health Block is mapped on %M/%MW from the UMA
zone instead of %I/%IW.
If you attempt to enable the Device Control Block with an earlier version of the firmware, the I/O
scanning service is disabled.
If the check box is not selected, the I/O scanner service is enabled, and you cannot disable the I/O
scanning of individual devices.
Disabling I/O scanning with the Device Control Block is equivalent to ending communication
between the scanner and the device.
Therefore:
The fallback positions are applied to the inputs by the scanner.
Communication with the device stops.
All entries in the IN and OUT tables still transfer between the CPU and the scanner on each
scan.
As a consequence of the last point above, if you modify a %MWi attached to an input, this %MWi
is overwritten by the values coming from the I/O scanner in the next scan (with either 0 or the last
input value).
It is possible (but meaningless) to access %MW attached to the outputs because they are not
transmitted to the device.
NOTE:
When using a bridge, enter the bridge index (1 to 255)
in this field.
If you are copying the I/O scanning configuration from
a 140 NOE 771 •• to a 140 NOC 771 ••, set the Unit ID
to a value from 1 to 254.
Slave Syntax Use this drop-down menu to pick the way RD Ref Slave Index (default value)
and WR Ref Slave values are displayed. There are 4
types of display available:
Index: 100
Modbus: 400101
(Modbus register)
IEC 0: %MW100
M340 and Premium PLC slaves
IEC 1: %MW101
Quantum PLC slaves
NOTE: For more information, refer to the Contextual Menu for Copy/Cut/Paste topic
(see page 210).
NOTE: For more information, refer to the I/O Scanning with Multiple Lines topic (see page 212).
At a Glance
A right-click on a line in the I/O Scanning table opens the I/O Scanning Contextual Menu. Use this
menu to perform common operations on the lines of the I/O Scanning table, such as, delete a
device, copy & paste, cut & paste, insert a new line, etc.
Contextual Menu
The following illustration is the I/O Scanning contextual menu:
At a Glance
Modbus exchanges are limited to a maximum of 125 input words and 100 output words. If an
application needs to exchange more than these limits for a device, more than one I/O Scanning
line can be used: multiple lines for one device.
When the length is higher than the authorized limit for one Modbus exchange, the length is divided
into 2 or more Modbus exchanges. New lines are created for each Modbus exchanges with the
PLC.
The following I/O Scanning table is used for the multiple device lines example:
NOTE: This example shows an Advantys island, but DTM and PRA devices work the same way.
The second line 2, line 3, and line 4 correspond to the Modbus exchange queries.
When multiple lines are used, only the RD length and WR length columns of these new lines can
be edited. In the case of Advantys or DTM, the software supplies the RD length and the WR length,
and they cannot be changed in the I/O Scanning table.
NOTE: It is not necessary to have a Device Name defined to use multiple lines.
WARNING
UNEXPECTED SYSTEM BEHAVIOR
Verify that multiple word variables are completely on the same I/O Scanning line to avoid sending
parts of a variable data in 2 non-synchronized I/O Scanning Modbus exchanges.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
At a Glance
The Advantys Configuration Software (ACS) is integrated in Control Expert. This allows you to
configure Advantys STB and OTB islands from the Control Expert Ethernet I/O scanning tab.
WARNING
UNEXPECTED SYSTEM BEHAVIOR
Always launch ACS from Control Expert in order to synchronize variables and data between
Control Expert and ACS.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
WARNING
UNEXPECTED SYSTEM BEHAVIOR
Stop the PLC before transferring an ACS configuration and/or I/O scanning modifications.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
Step Action
1 From Control Expert, open a new Advantys island in ACS.
2 In ACS, select File menu → Copy Island Contents.
3 In the Open island window, select the island file (*.isl) to copy.
4 Click on Yes in the “Do you want to proceed?” message box.
5 The message “Island file has been saved.” in the Log Window verifies that the operation was
successful.
Step Action
1 In ACS, open an island configuration, for example, STB1.
2 Select File menu => Copy STB1 Contents
3 In the Copy STB1.isl to window, select the target directory.
4 The message “A copy of the island file has been saved with another name.” includes in the
Log Window verifies that the operation was successful. The name is new because its path has
changed.
At a Glance
The PRM Bus Master uses the Control Expert I/O Scanner to communicate with the CPU through
an Ethernet port. This requires configuring the PRM Master DTM in the Control Expert Ethernet I/O
Scanning tab.
Step Action
1 Install the PRM Master DTM on the Host PC.
NOTE: After installing new DTMs, the Hardware Catalog must be updated.
2 Add a PRM Master DTM to the connectivity tree in the DTM Browser using the contextual Device
menu service.
3 In the DTM Browser, select the PRM Master and use the contextual Device menu function to
open the DTM PRM Offline Parameter screen.
4 In the General Setting part of this screen set the IP address of the PRM device.
5 Open the I/O Scanning configuration editor (tab).
6 In the Module Utilities zone select YES for IO Scanning.
7 Select the I/O Scanning tab.
Results: I/O Scanning configuration editor opens.
8 Enter, on a free line, the IP address for the connection to be used to communicate with the PRM
Bus Master.
9 Set correct values for the Read Ref. and Write Ref. parameters.
10 Enter RD length and WR length for the IP address line (within the Read Ref. and Write Ref.
constraints).
NOTE: The lengths must be long enough for the expected configuration PRM Master DTM and
its subnode DTMs.
11 Validate the I/O Scanning screen.
12 Click on the ... button (next to Device Name cell).
Results: The Property box (see page 224) opens.
13 Select DTM in the Device Type drop-down menu.
14 Select the protocol in the DTM Protocol drop-down menu.
15 Select a PRM Master DTM in the DTM Name drop-down menu.
16 Click on OK to validate the choices you made.
Results:
The Device Type, Device Protocol and Device Name are verified and saved.
The Property box closes.
Step Action
17 Update the I/O Scanning line, refer to Updating I/O Scanning for a PRM Master DTM
(see page 219).
18 Build the Control Expert application.
19 Stop the PLC.
20 Transfer the Control Expert application to the PLC.
21 In the DTM Browser, right click on PRM Master and select the Connect function.
22 In the DTM Browser, right click on PRM Master and select the Store data to device function.
23 Run the application in the PLC.
Step Action
1 Configure and validate the PRM Bus Masters in the DTM Browser using the contextual Device
menu function.
2 Open the I/O Scanning configuration editor (tab).
3 Click on the ... button (that is next to the Device Name of the PRM Master DTM to update).
4 In the open Property box (see page 224), click on the Update button.
Results:
The PRM Master DTM modifications are synchronized with the Control Expert application.
The PRM Master DTM symbols are imported into the Control Expert Data editor.
The DTM Name is displayed in the I/O Scanning configuration tab in black. This indicates that
the PRM configuration is synchronized.
The Property box closes.
At a Glance
Control Expert allows configuration of BMX PRA 0100 modules through the Ethernet I/O scanning
tab. The PRA device configuration is done in a second instance of Control Expert.
Configuring a PRA
The following procedure configures a PRA device:
NOTE: When the second (PRA) instance of Control Expert is closed, there is no indication if the
PRA application has been built or not.
Step Action
1 From the Control Expert I/O Scanning table using the ... button, open an existing PRA
application.
2 In the second Control Expert instance, save the existing PRA application with a new name as a
*.sta or .xef file.
3 Close this second Control Expert instance.
4 In the Control Expert I/O Scanning table create a new PRA application on a new line.
5 Import or Open the *.xef or *.sta file previously saved.
6 If desired, build the new PRA application and transfer it to the PRA device.
7 Close the second Control Expert instance.
Property Box
At Glance
The Property box is the link between Control Expert and a device configuration tool. It is used to
select and name a device and to launch the configuration tool for the device.
Property Box
The following illustration is the Property box before selecting the Device Type.
For details on how top use the Property box, refer to:
Advantys (see page 225)
DTM (see page 228)
BMX PRA 0100 (see page 226)
Element Description
Device Type Selection of a STB or OTB device is made from this drop-down list.
After the first validation (using the OK or Launch Advantys button) the Device Type
cannot be changed.
Device Name The Device Name (see page 227) is used as a prefix to all variables created for an
Advantys island in ACS. This allows unique variables for duplicated islands.
After validation (using the OK or Launch Advantys button) the Device Name cannot be
changed.
Data Exchange These are the minimum number of words necessary for communication between the
Required Control Expert module and the Advantys island.
These values cannot be changed via the Property box.
NOTE: Increasing the RD/WR lengths via the I/O Scanning tab leaves enough data
exchange words for the future expansion of your Advantys island. Expanding an island
that does not use the last line in the I/O Scanning table requires changing the values for
all the lines below the line that needs the additional exchange words.
Use Device Name If this checkbox is unchecked, the user is in charge of giving unique names to the
as prefix variables and symbols in all Advantys islands.
This checkbox is only available for ASC V5.5 or higher. For versions less than 5.5 the
Device Name is automatically added to all variables and symbols in all Advantys islands.
Element Description
OK This button is only available after entering the Device Type and Device Name.
When clicked, the Device Type and Device Name are checked to see if they are valid.
If there is a problem, a message box opens explaining the why they were not valid.
OK is only available during the first use of the Property box for a new island.
Launch Advantys This button is only available if both:
Configuration The Device Type and Device Name have been entered
Software ACS is installed
Update When clicked, the ACS modifications are synchronized with your Control Expert
application (after these modifications have been validated in ACS).
It also imports and updates all ACS symbols and variables into the Control Expert
variable manager.
NOTE: All variables modified in ACS are deleted and rewritten in the Control Expert
Data Editor. But they are not updated in the program.
Close This button closes the Property box without saving anything.
Element Description
Device Type Selection of the PRA device is made from this drop-down list.
After the first validation (using the OK or Launch PRA button) the Device Type cannot
be changed.
Device Name The Device Name (see page 227) is the name of PRA application.
Data Exchange This is not used when configuring a PRA device.
Required
OK This button is only available after entering the Device Type and Device Name.
When clicked, the Device Type and Device Name are checked to see if they are valid.
If there is a problem, a message box opens explaining why they are not valid.
OK is only available during the first use of the Property box for a new PRA configuration.
Launch PRA This button is only available if the Device Type and Device Name has been entered.
This button does two things:
It carries out the action of the OK button
If there is no problem during validation, it launches another instance of Control
Expert, which is used to do the actual configuration of the PRA.
Close This button closes the Property box without saving anything.
Valid Name
A valid Device Name for a configuration:
Does not already exist in the application
Is not a empty name
Starts with a letter
Has a maximum of 8 characters
Only ASCII characters, not Unicode characters
Has no spaces
Follows the Windows file naming conventions: no slashes, question marks, etc.
Follows Control Expert variable naming conventions
Element Description
Device Type Selection of DTM device type is made from this drop-down list.
DTM Protocol Select the protocol to be used from this drop-down list.
This list contains the DTM protocols of all the DTMs in the DTM Browser that can be
linked with I/O Scanning.
Device Name Select a PRM Master DTM from this drop-down list.This list uses the DTM Browser Alias
names.
This list contains all the PRM Master DTMs in the DTM Browser that support the
selected DTM Protocol.
To validate the choices, click on the OK button.
Data Exchange These are the minimum number of words necessary for communication between Control
Required Expert and the PRM Master DTMs.
These values cannot be changed via the Property box.
NOTE: Increasing the RD/WR lengths via the I/O Scanning tab leaves enough data
exchange words for the future expansion of your DTM topology tree. Expanding a tree
that does not use the last line in the I/O Scanning table requires changing the values for
all the lines below the line that needs the additional exchange words.
Element Description
OK The OK button is only available after selecting the Device Type, DTM Protocol and DTM
Name.
When clicked, the DTM Protocol and DTM Name are checked to see if they are valid.
If there is a problem, a message box opens explaining the why they were not valid.
The OK button is only available during the first use of the Property box for a new PRM
Master DTM.
Launch No Tool This button is never available for PRM Master DTMs.
Update Use the Update button after validating or changing the configuration of the linked PRM
Master DTM. Refer to Update I/O Scanning for a PRM Master DTM (see page 219).
Close The Close button closes the Property box without saving anything.
At a Glance
ACS saves an island configuration in an *.isl file. To add the island to an application, it is necessary
for Control Expert to know the location of the island configuration information.
Uploading or Importing
There are 2 situations where the information contained in the *.isl file is not available:
1. Uploading the application running in the PLC
2. Importing an *.xef file
In these 2 cases, if ACS is launched from the Property box (see page 224), it automatically tries to
open the latest Device Name.isl file the Control Expert General Path => Project Path directory:
If the same PC is used for the import (upload) and export (download) and the Control Expert
Project Path has not changed, the island configuration is synchronized with ACS.
If the same PC is not used for the import (upload) and export (download) or if the Control Expert
Project Path has changed, either:
Create a new island
Use the File menu => Copy Island Contents function
NOTE: The new Device Name.isl file is copied to the Project Path directory.
Managed Variables
At a Glance
Variables of devices that are linked to Control Expert through I/O Scanning or DTM are managed
variables. They are created by the device configuration tool or by the DTM and are imported into
Control Expert. They are named as a concatenation of the Property box (see page 224) Device
Name + device symbol name.
Managed variables follow the usual rules for Control Expert and ACS or DTM naming.
The optional Owner column lists the owner attribute of the managed variables. This allows you to
filter the variables according to their Device Name.
The Control Expert managed variables are locked and cannot be modified through the Data Editor.
You have to use the device configuration tool (ACS or the DTM) to modify these variables.
Measurement Setup
The set of curves below illustrates Quantum PLC response times when a signal is sent from a
remote input module to a remote output module through a Quantum PLC:
The plot shows four lines representing the number of scanned devices:
1 device
8 devices
16 devices
32 devices
The four lines are indistinguishable at this scale because the response times are so similar. You
can see the similarity in the following table of data from which the above graph was plotted:
Number of Devices to Scan Time from Scanned Device Input to Scanned Device Output (ms)
434 12A + NOE 771 x1 (v3.3) 10 ms scan 20 ms scan 50 ms scan 100 ms scan 200 ms scan
1 device 41 73 179 358 665
8 devices 42 75 180 360 666
16 devices 44 77 182 361 668
32 devices 46 79 185 364 671
The plot shows four lines representing the number of scanned devices:
1 device
8 devices
16 devices
32 devices
The four lines are indistinguishable at this scale because the response times are so similar. You
can see the similarity in the following table of data from which the above graph was plotted:
Number of Devices to Scan Time from Scanned Device Input to Scanned Device Output (ms)
65150 + NOE 771x1 (v3.3) 10 ms scan 20 ms scan 50 ms scan 100 ms scan 200 ms scan
1 device 35 61 153 302 602
8 devices 36 62 154 303 603
16 devices 38 64 155 305 606
32 devices 40 66 157 307 609
Chapter 7
Address Server Configuration/Fast Device Replacement
Introduction
This chapter covers the Address Server Configuration/Fast Device Replacement service available
on the NOE 771 01 and -11 (Transparent Factory/Real Time modules) and HE CPU modules. The
Fast Device Replacement service offers you a method of handling device replacement without
disrupting the system or service.
Overview
The address server provides two capabilities:
1. Standard BOOTP server behavior: Enter the MAC address and IP configuration. The NOE
BOOTP server will provide the IP configuration when the device sends a BOOTP request.
2. Fast Device Replacement (FDR) behavior: Enter the role name or the MAC address of the
device. The device will send its role name or the MAC address with its DHCP request. With the
DHCP response from the NOE, the device will receive its IP Configuration, plus the name and
location of a configuration file.
The next step for an FDR-compliant device is to download its configuration from the NOE.
NOTE: Consult your Schneider Electric sales representative for the current list of FDR-compliant
devices.
The address server in the NOE supports both modes at the same time. You select a mode by
entering either the MAC address or the role name in the Address Server Node Configuration
(see page 302) page. You may enter only one or the other, but not both.
The Fast Device Replacement capability allows automatic configuration of FDR-compliant devices.
Role Name
The logical role name should be written on devices. The technician can get the new device from
stores, enter the corresponding role name into the device, and place the device in the system. The
device automatically gets its configuration and starts running with no further input from the
technician. This process is designed to get your machine up and running quickly. All the technician
has to do for any FDR compliant device is to enter the role name into the new device.
Parameter Limit
Maximum number of address server entries 128
Maximum size of the configuration file per device 4K bytes
Total size of Fast Device Replacement storage 512K bytes
Maximum role name size 16 Characters
NOTE: For the DHCP server to work correctly the following must be observed.
Address class and subnet class configured for the devices must match.
Address class of the NOE and of the devices must be the same.
The role-name.prm configuration files are stored in the NOE in non-volatile memory. Therefore,
after a power failure all configurations will be available.
Error Messages Error messages, appearing as icons in the seventh column, display on the
Address Server Configuration page (see page 302), or in a dialog box.
Error Icon If an entry is not loaded in the DHCP server or loaded with a different configuration, an
icon of an exclamation point displays in the seventh column. The icon informs you of the
difference between the current and stored information.
Present configuration:
Error Dialog Box If you entered an existing role name or MAC address, you will receive an alert
message asking you to correct the entry.
Choose either the Role Name or Device MAC address field. When one field is selected, the other
is made unavailable.
Adding Entries If you are adding a device, the page appears with values. You need to enter either
a Role Name or a MAC Address.
If you are adding an entry, submit your selection using the Add the Entry button.
Modifying Entries If you are modifying an entry, the Device IP address, Subnet Mask, and Gateway
fields display with the current configuration.
If you are modifying an entry, submit your selection using the Reset the Form button.
Each field of the Address Server Node Configuration page has restrictions, which are detailed
below.
Role Name: Each role name must be unique. Only letters, numerals, and underscores are
allowed. No more than 16 characters are allowed, and no spaces are allowed.
Device MAC Address: This address must be in hexadecimal format and six (6) bytes long (6x2
characters). The MAC address can be entered with or without a delimiting character between
each pair of lower- or upper-case hexadecimal characters. The delimiting characters improve
readability. There are three choices for a delimiting character:
Space " " (spacebar)
Colon ":"
Hyphen "-"
Device IP Address: The IP address must use the standard numeric Internet Protocol address
that uniquely identifies each computer on the network. The IP address is a 32-bit identifier made
up of four groups of numbers (from 0 through 255), each number separated by a period, for
example 123.456.78.9.
Subnet Mask: The subnet mask must be entered in IP address format.
Gateway: The gateway must be entered in IP address format. The gateway must be on the
same subnet as the device.
An additional, unnamed column indicates any difference between the current and stored
configuration. If a difference exists, an exclamation point is displayed.
This is the Address Server Configuration page. In this sample page, the configured and stored
configurations are the same for each device.
Choosing Options
The Address Server Configuration page allows you to choose different options for adding or
altering the configurations of your NOE. The options available to you are:
select an entry
add an entry
change an entry
delete an entry
Below we describe the method and options chosen to perform any of the four options listed above.
Screen shots are presented to accompany the Adding an entry section.
Selecting an Entry When the page displays, by default no entries are selected. Use the radio
buttons in the first column to select an entry. Only one entry may be selected at a time.
Adding an Entry When the Add a New Entry button is selected, the Address Server Node
Configuration page appears. This page displays information about a device.
If you selected a device, this page displays the device’s configuration. Configuration information
appears in four of the five fields of the dialog box. Only the Role information field is blank. You
should enter a Role name, for example ENT_7.
If no device is selected, default values appear in each field.
Changing an Entry Before using this button, you must select an entry in the database by choosing
one of the radio buttons in the first column. If you do not choose an entry, a message appears.
When the Change an Entry button is selected, the Address Server Node Configuration page
appears. The information displayed is for the device selected.
Deleting an Entry Before using this button, select an entry in the database by choosing one of the
radio buttons in the first column. If you do not choose an entry, a message appears.
The entry selected will be removed from the database. Before completely deleting an entry, a
warning message appears. Click Yes if you want to delete the entry, No if you don’t.
Click OK. Another dialog box appears notifying you that the deletion was successful.
Highlighting Anomalies
If there are anomalies with the entered configuration parameter information, the system indicates
anomalies using a highlighting mechanism. Valid device configurations appear in purple and italic.
A device with configuration anomalies appears in red and bold.
The system detects the following anomalies:
Bad Role Name
The valid Role Name characters are:
a through z (lower case)
A through Z (upper case)
"_" (underscore)
Wrong IP Address
Wrong Subnet Mask
Wrong Gateway
Double Entry
Each entry needs a unique Role Name or MAC Address. If a duplicate Role Name or MAC
Address is entered, the system highlights the duplication.
Erroneous entries are not loaded into the DHCP server. Therefore, correct erroneous before
loading. There are two ways of correcting the erroneous entries:
Correcting through Web page: Make the changes on the Web page and submit the change.
Correcting through the Address Server configuration file: Make the changes in the file and
reboot the server.
Chapter 8
Network Management Service (SNMP)
Introduction
The following material describes SNMP and the Schneider private MIB. Under the Schneider
private MIB is the Transparent Factory Ethernet private MIB.
SNMP
Introduction
This topic describes the Simple Network Management Protocol (SNMP), which is configured on
your NOE or 140 CPU 651 x0. Network management software allows a network manager to:
monitor and control network components
isolate problems and identify their causes
query the status of devices such as a host computer, routers, switches, and bridges
obtain statistics about the networks to which devices are connected
Manager/Agent Paradigm
Network management software follows the conventional client-server model. To avoid confusion
with other network communication protocols that use the client/server terminology, network
management software uses the following terms:
manager: the client application that runs on the manager’s computer
agent: the application that runs on a network device
The manager uses conventional transport protocols (for example, TCP or UDP) to establish
communication with the agent. Managers and agents then exchange requests and responses
according to the network management protocol.
The MIB
Each SNMP object has to be defined and given a unique name. Both the manager and agent
programs must agree on the names and the meanings of the fetch and store operations. The set
of all objects SNMP can access is known as a Management Information Base (MIB).
Private MIB
Schneider obtained a private MIB, Groupe_Schneider (3833). Under the Groupe Schneider private
MIB is a Transparent Factory Ethernet (TFE) private MIB. The Transparent Factory SNMP
embedded component controls the Schneider private MIB function.
Step Action
1 Get Schneider .mib file from the NOE Web page.
Find the .mib file as a packed file under /wwwroot/SchneiderTFE.zip on your NOE
module.
2 Load .mib file to the SNMP manager.
3 When you are done, you will see the Schneider private MIB manager in your
manager.
ASN.1 Overview
Abstract Syntax Notation One (ASN.1) is a formal language for abstractly describing messages to
be exchanged between distributed computer systems.
An Example
Objects in a MIB are defined with the ASN.1 naming scheme that assigns each object a long prefix
that guarantees that the name will be unique. For example, an integer that counts the number of
IP datagrams that a device has received is named: iso.org.dod.internet.mgmt.mib.ip.ipinReceives.
The following figure depicts the ASN.1 naming scheme example.
This object name is represented in an SNMP message by assigning each part an integer. So, the
above message would appear as 1.3.6.1.2.2.4.3.
The PDUs within the SNMP initiate the communication between the manager and the agents.
The SNMP installed on your NOE module uses the following three PDUs:
GetRequest
SetRequest
Trap
GetRequest PDU
The GetRequest (shortened to Get) PDU is used by the SNMP manager to retrieve the value of
one or more objects (OIDs) from an agent.
SetRequest PDU
The SetRequest (shortened to Set) PDU is used by the SNMP manager to assign a value to one
or more objects (OIDs) residing in an agent.
Trap PDU
The Trap PDU is used by the agent to alert the manager that a predefined event has occurred.
Introduction
A MIB, a Management Information Base, is an element used in network management. Network
management services are based on the need to monitor and manage:
performance
fault occurrences
security
Each MIB contains a finite number of objects. Manage your MIB with a management station
running an SNMP management application. The management application uses GETs and SETs
to retrieve system information and to set system environment variables.
iso(1)
org(3)
dod(6)
internet(1)
private(4)
enterprise(1)
GroupeSchneider(3833)
Transparent_Factory_Ethernet(1)
Under the GroupeSchneider private MIB is a Transparent Factory Ethernet (TFE) private MIB,
Transparent_Factory_Ethernet(1).
The diagram following illustrates the Schneider Electric (Groupe_Schneider (3833)) private
enterprise MIB subtree.
The Groupe_Schneider (3833) subtree is the root of Groupe Schneider's private MIB in the
Structure of Management Information (SMI) used by SNMP and defined in RFC-1155, which is a
specification that defines the structure and identification of management information for TCP/IP-
based networks.
As devices are added to Schneider's catalog, Schneider's private MIB will be extended in the
following manner:
If needed, a Transparent Factory, communication-service object will be added for the new
device in the corresponding Equipment_Profiles(7) subtree. This subtree can hold as many
objects as are required.
If needed, a new branch will be added at the same level as Transparent_Factory_Ethernet(1).
This subtree will be created for product-specific objects (such as the ATV58 object under the
IndustrialControlProducts (3) subtree).
When a new device is created, a corresponding object description is created in the ASN.1 format.
The ASN.1 file(s) are then given to producers of SNMP manager software for inclusion in their
products.
Service Indicates . . .
port502Status(1) status of the service (idle, operational)
port502SupportedProtocol(2) supported protocols (MODBUS, Xway)
port502IpSecurity(3): status of the Port502 IP Security service (enabled/disabled)
port502MaxConn(4) maximum number of TCP connections supported by the Port502 entity
port502LocalConn(5) TCP connection number currently opened by the local Port502 entity
port502RemConn(6) TCP connection number currently opened by the remote entity to the local
Port502 entity
port502IpSecurityTable(7) a table containing the number of unsuccessful TCP connection open tries from
a remote TCP entity
port502ConnTable(8) a table containing Port502 TCP specific information (MsgIn, MsgOut)
port502MsgIn(9) total number of Port502 messages received from the network
port502MsgOut(10) total number of Port502 messages sent from the network
port502MsgOutErr(11) total number of error messages built by the Port502 messaging entity and sent
to the network
port502AddStackStat(12) the support of additional port502 stack statistics:
1 - disabled
2 - enabled
Service Indicates . . .
ioScanStatus(1) global status of the I/O scanning service:
1 - idle
2 - operational
3 - stopped
ioScanDeviceTable(6) a table containing information on each remote devices polled by the I/O scanning entity
Service Indicates . . .
glbDataStatus(1) global status of the Global Data service:
1 - idle
2 - operational
3 - stopped
glbDataMaxPub(2) maximum number of published variables configured by the Global Data entity
glbDataMaxSub(3) maximum number of subscribed variables configured by the Global Data entity
glbDataPub(4) total number of publications sent to the network
glbDataSub(5) total number of subscriptions received from the network
glbDataPubErr(6) total number of publication errors detected by the local entity
glbDataSubErr(7) total number of subscription errors detected by the local entity
glbDataGlbSubHealth(8) global status of health for the Global Data subscribed variables:
2 - OK: The health status of all subscribed variables is OK
4 - Warning: At least one subscribed variable has a health fault
glbDataPubTable(9) a table containing information on each published variable (the number of publications,
the source IP address, the number of errors)
glbDataSubTable(10) a table containing information on each subscribed variable (the number of subscriptions,
the source IP address, the number of errors, Health)
Web Subtree
The Web (5) subtree, or group, contains the objects related to the Web server service.
Service Indicates . . .
webStatus(1) global status of the Web service:
1 - idle
2 - operational
Service Indicates . . .
addressServerStatus(1) global status of the address server service:
1 - idle
2 - operational
Service Indicates . . .
profileProductName(1) the commercial name of the communication product in a string form (for
example, 140 NOE 771 11)
profileVersion(2) the software version of the communication product in a string form (for
example, Vx.y or V1.1)
profileCommunicationServices(3) the communication services supported by the profile (Port502Messaging, I/O
scanning Messaging, Global Data, Web, and Address Server)
profileGlobalStatus(4) the global status of the communication module:
1 - NOK
2 - OK
profileRoleName(6) rthe ole name for the IP address management if it exists (empty string if there
is none)
profileBandwidthMgt(7) the status of Bandwidth Management:
1 - disabled
2 - enabled
profileBandwidthDistTable(8) the CPU time distribution between Global Data, Port502 Messaging, I/O
scanning
profileLedDisplayTable(9) a table giving the name and the state of each module’s LEDs
profileSlot(10) the position of the communication module inside the rack if there is one. If
there is no rack, the profileSlot value will be zero
profileCPUType(11) the host for which that communication module is a part when a CPU type
exists (if there is no host, the string is empty)
profileTrapTableEntriesMax(12) the maximum numbers of entries in the Trap Table (equal to the number of
possible remote managers)
profileTrapTable(13) a table allowing you to enable or disable the private traps for each of the
communication services
Service Indicates . . .
profileSpecificId(14) a unique Profile Specific Identification inside the equipmentProfile object of
the Schneider Transparent Factory MIB (for example, the PLC Premium
family is 100)
profileIpAddress(15) the IP address of the SNMP agent
profileIpNetMask(16) the subnet mask associated with the IP address of the SNMP agent (the value
of the mask is an IP address with all the network bits set to 1 and all the host
bits set to 0)
profileIpGateway(17) the default Gateway IP address of the SNMP agent
profileMacAddress(18) the Ethernet media-dependent address of the SNMP agent
NTP Subtree
The NTP (1) subtree contains a set of common objects.
Service Indicates . . .
ntpStatus(1) the status of NTP service (not server):
1. 1 = Idle
no configuration
2. 2 = Operational
ntpSrvAddr(2) the IP address of NTP server in dot notation format
ntpLnkSrvStatus(3) the status of link between module and NTP server:
1. 1 = NOK (module can not reach NTP server)
2. 2 = OK
ntpReqCnt(4) the number of requests sent to NTP server
ntpRespCnt(5) the number of responses received from NTP server
ntpErrCnt(6) the total number of communication errors
ntpDate(7) date of the day
ntpTime(8) time of the day
ntpTimeZone(9) current time zone
ntpDSTStatus(10) Daylight Savings Time status:
1. 1 = ON (Daylight Savings Time)
2. 2 = OFF (Standard Time)
ntpLastErr(11) Last error code generated by system
SMTP Subtree
The SMTP (1) subtree contains a set of common objects.
Service Indicates . . .
emailIndex(1) the index value in the email service table
smtpStatus(2) the status of SMTP service (not server):
1 = Idle (no configuration)
2 = operational
See the Electronic Mail Notification Service subtree table (see page 282).
NOTE: A diagram of the Schneider Electric private enterprise MIB subtree appears in Simple
Network Management Service (SNMP) (see page 247).
The following list describes the characteristics of private traps, which means that they can:
send messages to the two managers whose IP addresses are configured in the SNMP
configuration (either the PL7 or the Web page)
use the community name given to this configuration
enable or disable each of the Transparent Factory Ethernet Private MIB groups: Switch (1),
Port502_Messaging (2), I/O_Scanning (3), Global_Data (4), Web (5), Address_Server (6),
Equipment_Profiles (7), NTP (8), and SMTP (9)
Private traps are described in the MIB ASN.1 description, which is contained in a .mib text file.
NTP Traps
1. DST Change Trap: notifies the manager that the NTP server time has changed either from (a)
standard time to daylight saving time or (b) daylight saving time to standard time
2. NTP Status Change Trap: sent when the NTP component status changes (ntpStatus(1))
3. Leap Second Trap: sent when leap seconds are inserted
SMTP Traps
1. SMTP Status Change Trap: sent when SMTPStatus changes
2. SMTP Link to Server Status Change: sent when tSMTPLnkSrvStatus changes. Trap is sent
when service tries to send an email. Every 30 minutes a periodic test checks the connection to
the SMTP server.
Chapter 9
NTP Time Synchronization Service
Introduction
This chapter describes the NTP time synchronization service, which provides an accurate local
clock using NTP.
General
The NTP time service synchronizes computer clocks over the Internet. For example, the time of
one client is synchronized either with another server or to a referenced time source like a radio or
satellite receiver.
Typical time service configurations utilize redundant servers and diverse network paths to achieve
high accuracy and reliability. Time service accuracy can be within a millisecond on LANs and up
to a few tenths of milliseconds on WANs.
Use the time service for:
event recording (sequence events)
event synchronization (trigger simultaneous events)
alarm and I/O synchronization (time stamp alarms)
local time zone is configurable and customizable including daylight savings time
Web page diagnostics for the time synchronization service
Action Result
NTP Client requests a time synchronization NTP Server responds with a signal.
signal from an NTP server. (Request is sent
over an Ethernet network.)
NTP Client stores the time.
NTP Client sends a message to the The controller updates its internal clock with
controller’s clock system counter. the following granularity:
1 ms
On an Ethernet network, all controllers should be synchronized with the same NTP server.
Time accuracy Local Time error is < 10 ms compared to the reference NTP server:
Typical: under 5 ms
Worst case: <10 ms
Note:
1. Settling Time: The maximum accuracy is obtained after 2 updates from the NTP server.
2. Polling Period Dependency: The accuracy is dependent upon the polling period. Less than
10 mSec of error is guaranteed for polling periods of 120 seconds or less. To obtain the best
possible accuracy and if your network bandwidth will allow, reduce the polling period to a
small value.
3. For example, choosing a polling time of 5 seconds provides better accuracy than a time of
30 seconds.
Time zone Default format: Universal Time, Coordinated (UTC)
Optional: Configure the service to use a local time zone. For example, GMT+1 for Barcelona or
Paris
Daylight savings Automatic: module adjusts time in spring and fall
time
R_NTPC Representation
The block reads the Ethernet network system time and transfers it into specified parameters. The
additional parameter EN should be configured.
Set = 1
The date/time is updated within the last two minutes.
The date/time is acceptable.
Set = 1
The updated date/time is received from server and sent to
the module (at least once).
within two-minute time interval
acceptable (10 ms or less error)
For a valid time in the CPU, the low and high bytes of the
STATUS parameter must be set to 1.
Introduction
This material describes special operating conditions related to:
powering up
stop or run PLC
downloading applications
configuring the time service
Power up
To establish the accurate Ethernet system network time, the system does the following at power-
up:
requires the Ethernet module to boot
uses the Ethernet module to obtain the time from the NTP server
requires a predefined interval until time is accurate; user’s configuration determines how long
before time is accurate
may require several updates to achieve peak accuracy
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 module.
Download Application
The status clock value associated with the time service register in the CPU is reinitialized after an
application is downloaded or after an NTP server swap.
There will be two polling periods before the time is accurate.
NTP Configuration
Elsewhere in this section is information about the NTP configuration.
Automatically adjust clock for daylight This parameter is selected by default (check mark
saving change appears) if daylight saving time is chosen.
Step Action
1 Enter changes in the appropriate field on the NTP configuration page for one or all of the
configurable parameters.
2 Click Save.
Chapter 10
Electronic Mail Notification Service
Introduction
This chapter describes the electronic mail notification service, which uses SMTP to allow the
controller’s project to send e-mail messages.
General
The electronic mail notification service allows controller-based projects to report alarms or events.
The automation controller monitors the system and can automatically create an electronic mail
message alert with data, alarms, and/or events. Mail recipients can be either local or remote.
Based on predefined events or conditions, messages are created using the MSTR function
block.
The email message is constructed from predefined headers plus variables and text (a maximum
of 238 bytes). This message is sent directly from the automation system to the local email
server.
Mail headers contain common predefined items—recipient list, sender name, and subject.
These items can be updated by an authorized administrator.
Mail Service
Elsewhere in this guide is detailed information about configuring the electronic mail service
(see page 310).
NOTE: Default TCP Port: The default TCP port number for SMTP is 25. Ensure that you configure
the port specified by your local mail server.
Header Examples
The text and variable information can be defined and updated by an authorized administrator using
an embedded Web page (SMTP Configuration page). Define mail headers to indicate different
levels of importance. For example:
Header 1 could be "Urgent problem reported by PLC 10"
Header 2 could be "NOTIFICATION from substation 10"
Header 3 could be "INFO message from water system"
Listing different recipients in each of the three headers ensures that the right information quickly
flows to the right recipients. The project adds pertinent information such as the specific device,
process, or location. This pertinent information is added to the body of the mail message. Then the
complete message is sent to an electronic mail server for distribution to recipients. These
recipients could be engineers, managers, or process owners.
Security (Authentication)
An optional login (system ID) and password can be used to authenticate the connection to the
SMTP mail server. The SMTP-supported authentication method is LOGIN.
System Diagnostics
The SMTP Diagnostic Web page displays the status of the service. Diagnostic information is also
available for remote management using the SNMP network management standard.
Block Representation
Each operation is designated by a code. To send an email message, use the MBP_MSTR block
with function code 13 (see page 171).
Parameter Description
The following table describes the MBP_MSTR parameters:
The second and subsequent words (maximum 119) contain the data (ASCII format) that will be
copied into the email message. The first n characters will be added to the configured email subject.
The remaining characters (2*N-2-n) will be part of the message body. N represents the number of
words transferred.
Error Codes
The electronic mail notification service supports the following error codes:
Summary
The electronic mail delivery service subtree contains the following objects:
Service Description
emaillndex (1) index value in the email service table
smtpStatus (2) global status of the SMTP service:
idle(1): no configuration
operational(2): operational and running
stopped(3): stopped
smtpSrvChkFailCnt (9) number of times link to SMTP server has been detected as
down
Chapter 11
Embedded Web Pages
Introduction
This chapter presents the contents of the embedded Web pages contained in the Quantum 140
NOE 771 xx modules. These Web pages enable you to access diagnostic information, view
configuration information, and change the online configurations for the module.
Home Page
To access the Quantum home page enter the IP address of the module in his web browser. No
password is required to display the home page:
Links
From the Quantum home page, you can access the following pages:
Monitoring (see page 285)
Diagnostics (see page 287)
Setup (see page 288)
Documentation
Enter a user name and a password to access the services on these pages.
Language
In the Quantum home page, you can display the Quantum web pages in either English or Chinese.
Home Page
This page lists the various viewer services supported by the default Web site of the module and
provides links for accessing the services you require.
Illustration
The Monitoring home page looks like this:
PLC Program viewer (see Modicon M340, FactoryCast, User Manual): Display Control Expert
programs in run mode using a web browser.
Password-protected custom pages (see Modicon M340, FactoryCast, User Manual): for
restricting access to web pages created by the user.
Custom pages without password protection (see Modicon M340, FactoryCast, User Manual):
for unrestricted access to web pages created by the user.
Silverlight pages (see Modicon M340, FactoryCast, User Manual): for viewing user-defined
pages created with Microsoft Expression Blend® software that have been added to the web site
Home Page
This page lists the various services supported by the default Web site of the module and provides
links for accessing the services you require.
Illustration
The Diagnostics home page looks like this:
Links
To access the service you require, click on a link:
Rack Viewer
Controller Status (see page 292)
RIO Status (see page 294)
Alarm Viewer
Ethernet (see page 312)
Properties (see page 322)
Home Page
The NOE 771 11 Setup page lists the various services used to configure the module. You can
navigate to this page from the link on the Home Page (see page 284).
Illustration
The Setup page looks like this:
Link Result
SNMP Provides the ability to configure the SNMP Agent in the NOE
Address Server Configure the IP assignments, including showing the BOOTP and DHCP
(see page 302) database
Global Data Displays the Global Data Configuration page. Configure the Group Address,
(see page 195) Multicast filtering, Distribution period, Health Time Out, Health Bits, and Data
Zones. The Global Data Configuration page also displays a Variable Table.
NTP (see page 305) Configure the IP address of the primary and secondary NTP server. Set a
polling period. Select a time zone from the drop-down list, and automatic
adjustment for daylight savings time.
Email (see page 85) Configure the email server’s IP and Port (default port is 25). If security is
required, select Enable and set a Login and Password. Create three mail
headers.
Security View and edit:
the username and password for accessing the home page
the password for writing variables to the data editor
FTP View and edit the username and password for the FTP service.
Introduction
Each Modicon Quantum 10-/100-Megabit Ethernet module contains an embedded Web server that
allows you to access diagnostics and online configurations for the module and its associated
controller (PLC).
Pages on the embedded Web site display the following information:
Configurable menus of the Address Server both BOOTP and DHCP and for SNMP
(see page 302)
Ethernet statistics for the node (see page 283)
Controller’s configuration (Controller Status on menu) (see page 292)
Controller’s register values
Remote I/O status and configuration (see page 294)
Remote I/O register values
Remote I/O distributed values
The FactoryCast/Real Time modules (see page 90) offer these additional pages:
Configuration and status for Global Data (publish/subscribe) (see page 299)
Bandwidth monitoring (see page 86)
I/O Scanner status (see page 314)
MODBUS Messaging status (see page 79)
NTP configuration and status (see page 317)
SMTP configuration and status (see page 318)
The web pages can be viewed using Internet Explorer 4.0 or higher. Either browser supports JRE
1.4.2_04 or higher.
For information about the additional functionality provided by the FactoryCast system in the
Ethernet modules, see the FactoryCast Manual (31001229).
Step Action
1 Obtain the full IP address or URL from your system administrator.
2 Type the address or URL in the address or location box in the browser window. The
Schneider Electric Web Utility home page displays.
3 On the Quantum home page (see page 284), click Diagnostics.
4 You will be requested to supply a user name and password.
5 After supplying the user name, password, and clicking OK, the Quantum Welcome
Page appears. The Quantum Welcome Page provides the links to all the Quantum
configuration and diagnostic pages and to the Data Editor / Data Monitor.
NOTE: The default User Name is USER, and the default password is USER. Both
should be changed by the system administrator during module installation.
Overview
The Configured Local Rack page shows the current configuration:
Link Display
Global Data (see page 313) general diagnostics of the global data and a table of all
published/subscribed variables in a distribution group
I/O Scanning (see page 314) general diagnostics of the I/O scanning utility and a summary of the
status of all modules
Messaging (see page 315) current information on open TCP connections on Port502
Bandwidth Monitoring load distribution of the Embedded Server module between the global
(see page 316) data utilities, I/O scanning, messaging, and other utilities
Statistics (see page 316) Ethernet module statistics with the reset counters link
NTP (see page 317) time synchronization service parameters
Email (see page 318) Email notification service parameters
Upload MIB file upload the private MIB source file
Crash Log file (see page 319) crash message (after crash) and status message (normal
operations)
Overview
The Controller Status Page provides up-to-date information about the controller and its
configuration. Access this page by selecting the CPU model from the Rack Viewer (see page 291)
or the hyperlink Controller Status.
Sample Page
Here is an example of a Controller Status page.
Dynamic Data
Some of the data provided on this page is dynamic. Dynamic data is constantly refreshed at a rate
determined by the performance of the Embedded Server, network, and client CPU.
Description Fields
The following table describes the description fields on the CPU Configuration Screen
(see page 292):
Field Description
System Memory [Kb] Amount of system memory used
Extended Memory [Kb] Amount of extended memory used
Total Memory [Bytes] Total memory used in bytes
I/O Map Words Number of I/O words mapped.
Segments Number of segments
DCP Drop ID Drop number for distributed control
Memory Protect Position of the memory protect switch
Constant Sweep Current status of constant sweep
Optimize Current status of optimization
Word Fields
The following table describes the Word fields on the CPU Configuration Screen (see page 292):
Field Description
%M valid address of %M
%I valid address of %I
%IW valid address of %IW
%MW valid address of %MW
Battery Coil address of battery bit
Timer Register address of timer word
Time of Day Clock address of timer of day clock
Stopped Codes reason for controlled stopping
ASCII Fields
The ASCII column on the CPU Configuration Screen (see page 292) contains information about
the ASCII fields.
Overview
The Remote I/O Status page gives an overview of the status and health of the Remote I/O network
communications. Access this page by selecting the CRP Drop down menu item Remote I/O Status
or using the hyperlink RIO Status.
Sample Page
Here is an example of a Remote I/O Status page.
Dynamic Data
Some of the data provided on this page is dynamic. Dynamic data is constantly refreshed at a rate
determined by the performance of the embedded server, network, and client CPU.
You can add, delete, and copy Quantum PLC data as described in the following list:
Insert additional rows of data by clicking on the Insert Rows button.
Delete specific rows of data by clicking on the Cut Rows button.
Copy in rows of data by clicking on the Paste Rows button.
SNMP Configuration
Overview
This topic describes SNMP configuration for the Quantum Ethernet module through the SNMP
Configuration page.
The following table describes the SNMP configuration tasks that you can perform through the Web
page:
Task How To
To display the current SNMP configuration Click Show SNMP Configuration.
To clear the fields Click Reset the Form.
To change the SNMP configuration Change the information on the page and click
Update SNMP.
After you make your modifications to any of the above parameters, click Update SNMP. A new
page displays the following message: "Successfully updated SNMP database." Note that this page
contains the same links as those on the Configure SNMP page.
NOTE: Reset the module to implement the changes.
Step Action
1 Enter the following URL into your browser:
http://hostname/secure/embedded/builtin?submit=Configure+SNMP
or click the SNMP link in the Setup home page to navigate to the SNMP Configuration
page.
2 Enter the Community names for Set, Get, and Trap into the SNMP Configuration page
as shown below.
Overview
Whether you use either the Configure Each Device Separately or the Copy Configuration method
(see page 195), the procedure to configure individual parameters is the same. Therefore, in order
to use the Global Data (publish/subscribe) utility in the NOE, you need to configure the Global Data
parameters including:
Distribution period
Multicast filtering
Health bit location
Global Data base address
Group IP address
The following sections describe in detail the exact steps to configure each parameter on the Global
Data Configuration page.
Illustration
You can change the configuration in the Global Data Configuration page:
Step Action
1 Adjust the Distribution Period cycle. Enter a value from 1 through 50.
Note: Distribution Period is the minimum number of controller scan times before an
update occurs.
2 Before entering a value in the Group Address field, identify the station’s distribution
group. The Group Address entry will be an IP address from 224.0.0.0 through
239.255.255.255.
Group Address: the Class D Multicast IP address used for a distribution group.
Members of this distribution group are configured to use the same group address;
therefore, members can communicate with each other using Global Data.
3 Set the timeout in the Health Time Out field. This value is measured in milliseconds
and can be set to a value that ranges from 50 through 15000 ms (in 50 ms
increments)
Note: Health Time Out is the maximum time between received subscriptions before
a subscription is declared unhealthy (inoperable).
4 In the 4x starting address, set the Data Zone field.
5 If you are connected to an Ethernet switch that supports multicast filtering, click the
Multicast filtering check box.
6 Enter %MW word (4x register) location for the Health Bits. This is the location for
storing health bits.
Step Action
1 Highlight the identification number in the Data ID column.
2 In the Type column select the publish/subscribe variable type from the drop down
list. Three options are available publish, subscribe, or none, displayed as:
NONE
SUB
PUB
3 In the Symbol column you may enter text to describe the variable.
4 In the Address column you see the application address for this variable.
Note: This is a read only field.
5 In the Length column for each row, type a value, which represents the number of
4x registers. The ending 4x register field is automatically updated. If you are using
the second method, Copy Configuration, update Length the first time only.
6 When you are finished, click the Update Global Data Configuration button.
Step Action
1 Verify that every controller is running.
2 Look at the health of variables using the Global Data Diagnostics page.
Follow these links: Diagnostics → Ethernet → Global Data
Overview
This topic describes the DHCP and BOOTP address server configuration for the Transparent
Factory Ethernet modules.
NOTE: To configure the address server for the 140 NOE 771 x FactoryCast Web server modules,
see Address Server Configuration/Fast Device Replacement (see page 238), which describes the
BOOTP process.
Adding Entries
Create new address server configurations with these steps:
Step Action
1 Press Add a New Entry. A dialog appears in the web frame:
Note: The system does not allow you to enter text in both the Role Name and Device
MAC Address text fields. Create either a DHCP configuration (Role Name) or a
BOOTP (Device MAC Address) configuration.
2 For the address server configuration type (DHCP or BOOTP), enter text in the
appropriate field:
Role Name: variable name for DHCP address server configuration
Device MAC Address: MAC address for BOOTP address server configuration
3 Enter an address in the Device IP Address field. (We have provided an example
address.)
4 Enter an address in the Subnet Mask field. (We have provided an example address.)
5 Enter an address in the Gateway field. (We have provided an example address.)
6 Press the Add the Entry button.
When you press the Add the Entry button, a new entry that corresponds to your input appears in
the table in the web frame:
When you use the same Add the Entry procedure to add subsequent entries, multiple entries
appear in the table:
In the above figure, a user has highlighted the radio button for test_1. That item can now be edited
with the last row of buttons:
Button Function
Change an Entry Change the table data for the entry.
Delete an Entry Delete the entry from the table data for the entry.
Note: The selected radio button has no effect on the Add a New Entry function.
Note: You can press the Refresh Address Server Database Table button to refresh the table
data at any time.
Button Description
Save Stores new NTP (time service) configuration. Previous configuration is no longer valid.
Cancel Cancels new NTP (time service) configuration. Previous configuration is valid.
Disable NTP IP of Primary and Standby set = 0.
NTP server not polled.
Time in controller not updated.
4. Time Zone
Select from drop-down menu
Universal Time, Coordinated (GMT) = default
Custom time zone
Step Action
1 Enter changes in the appropriate field on the NTP Configuration page for one or
all of the configurable parameters.
2 Click Save.
Button Description
Save Saves the new Email configuration.
Note: The previous configuration is no longer valid and it is not stored.
Cancel Cancels the entries in the fields.
The previous configuration is valid.
Disable Email Clears the stored configuration, and disables the email service.
Note: The next time the service is enabled, a new configuration is required.
Parameter Description
IP address of Email Enter a valid IP address. (This parameter identifies the SMTP
server.)
Port Default = 25 (If necessary, you may enter a new value.)
Password Authentication If you want to restrict access, enable Password Authentication
by entering a check mark in the box.
Enter values for:
Login:
Any printable character allowed
64 character maximum
Password:
Any printable character allowed
64 character maximum
Overview
The Ethernet menu contains a list of links for accessing the different diagnostic pages for the
Ethernet module:
Global Data
I/O Scanning (see page 199)
Messaging
Bandwidth Monitoring (see page 86)
Statistics
NTP (network time protocol)
Email
Upload MIB File
Crash Log File
This page also shows a table of published and subscribed variables in the same distribution group.
Each variable is identified by its Identifier:
Green for the subscribed variables
Black for the published variables
White for unconfigured variables
Red for variables with communication interruptions
A value of NOK in the I/O Scanning Status field indicates that the local system is not scanning. In
this case, any data that appears in the Scanned Device Status display is meaningless.
A value of OK in the I/O Scanning Status field indicates that the values in the Scanned Device
Status display are reporting the state of scanned devices.
In the Scanned Device Status display, the colors that appear in each block indicate the following
states for specific remote devices:
Green indicates that a device is being scanned
Black indicates that I/O scanning of the specific device has been intentionally disabled via the
Device Control Block
White indicates an unconfigured device
Red indicates a suspect device
NOTE: Be aware that the green Scanning indicator may incorrectly remain green for a remote
scanned device after the Ethernet cable gets removed from that device. This inaccurate indication
occurs when the health timeout value in the I/O Scanning configuration screen is set to 0
(see page 204).
You should configure an operational health timeout value in the range 1...65535 (in 1 ms
increments). If the health timeout value is set to any value in this range, the Scanning indicator
reports I/O scanning health correctly.
Messaging Page
This page provides current information on the open TCP connections on port 502.
The number of sent/received messages on the port can be found at the top of this page.
A table provides, for each connection (numbered from 1 to 64):
remote IP Address
remote TCP port
local TCP port
number of messages sent from this connection
number of messages received from this connection
detected event number on this connection
NOTE: Following a request to close a connection, the PLC may hold the connection open in its
memory for a few minutes, during which the table will reflect the open connection.
Number of Messages received is not reset after a port 502 connection is closed. Therefore, the
count indicates the total number of messages that have been received since the module was
started.
The remote address ‘127.0.0.1’ is used as Private System Connection For Diagnostic Feature or
SOAP Communications.
NOTE: Refer to Modicon Quantum Ethernet TCP/IP Module User Guide (840 USE 107) and
Modicon Quantum Ethernet TCP/IP Module User Guide (840 USE 115) for definitions of terms.
Parameter Description
NTP status Service is correctly configured (OK)
NTP server status NTP client is connected to the NTP server, and if the server is Primary
or Standby
NTP requests Total number of client requests sent to the NTP server
NTP responses Total number of server responses sent from the NTP server
Number of errors Total number of unanswered NTP requests
Last error code Last detected error code received from the NTP client
Date Date in d/m/y format
Time Time
Time zone Time zone plus or minus Universal Time, Coordinated (UTC)
DST Daylight saving time (DST) parameter is either
1. on (enabled)
2. off (disabled)
Last Error field displays values, which indicate the type of detected event.
Parameter Description
Email status Email service is correctly configured (OK).
Link to Server Status Ethernet module is connected to the SMTP server.
Status is checked at start-up and at least every 30 minutes
after start-up:
Green = module connected to server
Red = module NOT connected to server
Parameter Description
Number of Responses from Total number of SMTP messages received from the SMTP
SMTP Server server
Number of Errors Total number of e-mails not sent because of a detected error
Last Errors Reason for the last detected error with a code in
hexadecimal.
0 indicates no detected error.
Last Mail Header Used Last header used by giving the number.
Number of seconds elapsed Counts the number of seconds since the last email was
since last e-mail successfully successfully sent.
sent
Number of times the link to the Number of times the SMTP server could not be reached.
server has been detected (Link checked every 30 minutes.)
down
Parameter Description
NTP status Service is correctly configured (OK)
NTP server status NTP client is connected to the NTP server, and if the server is Primary
or Standby
NTP requests Total number of client requests sent to the NTP server
NTP responses Total number of server responses sent from the NTP server
Number of errors Total number of unanswered NTP requests
Last error code Last error code received from the NTP client
Date Date in d/m/y format
Time Time
Time zone Time zone plus or minus Universal Time, Coordinated (UTC)
DST Daylight saving time (DST) parameter is either
1. on (enabled)
2. off (disabled)
The dialog:
Properties Page
NOTE: This page only reports this information. The fields cannot be changed.
Chapter 12
Hot Standby
Hot Standby
Overview
The Quantum Ethernt module offers a Hot Standby configuration available for Quantum
controllers.
CAUTION
RISK OF INCREASE OF TIME TO SWAP
Whenever possible, use of a switch (not a hub) to connect the NOE modules to each other or to
the network.
Schneider Electric offers switches. Contact a local sales office for more information.
Failure to follow these instructions can result in injury or equipment damage.
WARNING
UNINTENDED EQUIPMENT OPERATION
Design your application so that unmonitored modules support communication only to noncritical
parts of the application.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
In the hot standby solution, two identically configured PLC systems are set up to control the same
application. One PLC, the primary, runs the application and updates the other secondary (standby)
PLC. The standby maintains awareness of the application status but does not perform any control
functions. In the event of a failure in the primary PLC, the standby PLC takes over the primary PLC
responsibilities. When the PLC that has failed becomes operational again, it comes back up in the
hot standby system as the new secondary PLC.
The NOEs coordinate the swapping of IP addresses. After closing both the client and the server
connections, each NOE sends a swap UDP message to its peer NOE. The sending NOE then
waits a specified timeout (500 ms) for the peer swap of UDP messages. Either after receiving the
messages or after a timeout, the NOE changes its IP address.
NOTE: NOEs must communicate with each other in order to swap IP addresses. Schneider Electric
recommends that you connect the primary and secondary NOEs to the same switch because:
Communication failures between the NOEs increases the time to swap.
Connecting 2 NOEs to the same switch minimizes the probability of a communication failure.
NOTE: Schneider Electric recommends that you use a switch (not a hub) to connect the NOEs to
each other or to the network. Schneider Electric offers switches; please contact a local sales office
for more information.
The NOE waits for either a change in the controller’s Hot Standby state or the swap of UDP
messages. Then the NOE performs 1 of 2 Hot Standby actions.
All client/server services (I/O scanner, global data, messaging, FTP, SNMP, and HTTP) continue
to run after the switch from the old to the new primary NOE.
NOTE: Failure of an NOE module is not a condition for the primary system to leave the primary
state.
NOTE: Only the 140 NOE 771 01 or 140 NOE 771 11 (TCP/IP Ethernet modules) support a
Modicon Quantum Hot Standby with Unity V2.0 system.
The other requirement for the switches is that they are on the same sub-network.
TCP/IP Configuration
When the NOE module goes into service the first time, it attempts to get its IP address from a
BOOTP server. If a BOOTP server is not available, the NOE module derives its IP address from
its MAC address. Connecting to a BOOTP server or deriving the IP address from a MAC address
gives you a connection to the NOE, and you can then download a project to the PLC.
All standard rules apply to IP addressing with the additional restriction that the IP address cannot
be greater than 253 or broadcast address minus 2. Also, no other device can be assigned the
configured IP + 1 address.
IP Address Restrictions
Do not use either the broadcast IP address -1 or broadcast IP address - 2 to configure a
140 NOE 771 •1 / 140 NOC 78• 00 module.
For example, do not configure the primary CPU address as nnn.nnn.nnn.254. This causes the
standby CPU IP address to be nnn.nnn.nnn.255. The standby CPU would then return the
diagnostic code Bad IP configuration.
IP Address Transparency
WARNING
UNINTENDED EQUIPMENT OPERATION
For a Quantum Hot Standby configuration:
Do not use the IP address configured in Control Expert + 1.
Do not use consecutive IP addresses of the IP address configured in Control Expert.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
When a switchover occurs, the new primary PLC takes the IP address of the old primary PLC.
When the PLC that has stopped becomes operational again and rejoins the Hot Standby system,
it takes the IP address of the standby PLC.
The new primary 140 NOE 771 •1 / 140 NOC 78• 00 module has the same IP address as the
former primary module. The IP address in the secondary module is IP address + 1.
The 140 NOE 771 •1 / 140 NOC 78• 00 modules integrated into the Quantum Hot Standby
configuration coordinate this swapping of IP addresses with the management of Ethernet services
used.
MAST Cycle Time (ms) Recommended RPI (ms) Timeout Multiplier Connection Timeout
(ms)
20 10 16 160
50 25 8 200
100 50 4 200
200 50 4 200
255 50 4 200
NOTE: The maximum swap time may increase if the end device does not respond in a timely
manner.
NOTE: During the swap, there may be disruption in communication between the 140 NOE 771 •1
/ 140 NOC 78• 00 module and the end device. Confirm that the application can tolerate this
communication disruption.
140 NOE 771 x1 / 140 NOC 78• 00 Operating Modes in Quantum Hot Standby System
Operating Modes
The 140 NOE 771 x1 / 140 NOC 78• 00 module modes are:
primary mode:
The Hot Standby mode is primary CPU and client/server services are active.
standby mode:
The Hot Standby mode is standby CPU and server services are active except DHCP.
standalone mode:
The 140 NOE 771 x1 / 140 NOC 78• 00 module is in a non-redundant system, or the CPU is not
present or not healthy.
offline mode:
The CPU is stopped.
The Quantum Hot Standby and the 140 NOE 771 x1 / 140 NOC 78• 00 operating modes are
synchronized by these conditions:
CPU Module Status Hot Standby State 140 NOE 771 x1 / 140 NOC 78• 00
Operating Mode
present and healthy primary CPU primary
present and healthy standby CPU standby
present and healthy offline offline
present and healthy unassigned standalone
Not present or unhealthy N/A standalone
Any of the following events affect the 140 NOE 771 x1 / 140 NOC 78• 00 operating mode:
a 140 NOE 771 x1 / 140 NOC 78• 00 module is powered up
a 140 NOE 771 x1 / 140 NOC 78• 00 module executes a Hot Standby switchover
a 140 NOE 771 x1 / 140 NOC 78• 00 module goes to offline mode
a new application is downloaded to the 140 NOE 771 x1 / 140 NOC 78• 00 module
If the Hot Standby state is... Then the IP address assigned is...
unassigned Default IP address
primary CPU IP address configured in Control Expert
standby CPU IP address configured in Control Expert + 1
unassigned to offline transition See the Offline Mode at Power-up Sequence topic in the next table.
If two 140 NOE 771 x1 / 140 NOC 78• 00 modules power-up simultaneously, then:
Their mode (primary or standby) is determined by the mode of CPU in their rack.
The primary 140 NOE 771 x1 / 140 NOC 78• 00 has the IP address configured in Control
Expert.
The standby 140 NOE 771 x1 / 140 NOC 78• 00 has the IP address configured in Control
Expert + 1.
The 140 NOE 771 x1 / 140 NOC 78• 00 module detects a duplicate IP address, the IP address
remains at the default IP and the 140 NOE 771 x1 / 140 NOC 78• 00 module blinks a diagnostic
code.
If no IP configuration exists, 140 NOE 771 x1 / 140 NOC 78• 00 modules remains in the
standalone mode. The IP address must be obtained for the:
140 NOE 771 x1 via a BOOTP server
140 NOC 78• 00 based on the MAC address
Hot Standby State Status of 140 NOE 771 x1 / 140 NOC 78• 00 Services
Client Services Client/Server Server Services
Services
EIP Global Modbus/EIP FTP SNMP HTTP
Scanner Data Messaging
unassigned not running run run run run run
primary CPU run run run run run run
standby CPU stop stop run run run run
offline stop stop run run run run
Step Action
1 In a Hot Standby configuration NOE A is running in the primary PLC and NOE B is in the standby
PLC.
2 NOE A detects that its PLC has changed from primary CPU to the offline mode.
3 NOE A changes from primary NOE to offline with the same Ethernet services running and starts
its watchdog timer (with a 500 ms time-out setting). It waits for a message to swap IP addresses
from NOE B.
4 NOE B detects that its PLC has changed state from standby PLC to primary CPU.
5 NOE B stops all its Ethernet services, sends a request to NOE A for the synchronization of the
IP address swap, starts its watchdog timer (with a 500 ms time-out setting) and waits for a
response from NOE A.
6 When NOE A receives the request from NOE B (or after the NOE A watchdog timer times out),
it stops all its Ethernet services:
If it has received a request, NOE B sends a response to NOE A.
If its watchdog timer has timed out, NOE B does not send a response.
NOE A then swaps its IP address and starts the secondary services.
7 NOE B swaps IP addresses and starts Ethernet services as the primary NOE.
8 After NOE A senses that its local CPU changes from offline to standby, it takes the secondary
IP address.
9 NOE B now becomes the primary NOE.
Step Action
10 NOE B opens all client connections, listens for all server connections, and reestablishes those
connections.
11 NOE A listens for all server connections and reestablishes those connections.
NOTE: During the Hot Standby switchover, there is a loss of communication during 500 ms
between the PLC and the HMI and/or Control Expert.
Going to Offline
When either the CPU stops or the Hot Standby CPU goes to offline mode, 2 events occur:
1. the 140 NOE 771 x1 / 140 NOC 78• 00 module goes to the offline mode
2. the 140 NOE 771 x1 / 140 NOC 78• 00 module uses the IP address of the present configuration
The IP address assignment when going offline:
NOTE: For more information, refer to the 140 NOE 771 x1 / 140 NOC 78• 00 IP Address
Assignment topic (see page 330).
Description
The following table details the 140 NOE 771 •1module address swap times, such as the time to
close connections, time to swap IP addresses or time to establish connections:
Network Effects of Modicon Quantum Hot Standby with Control Expert Solution
Overview
The Modicon Quantum Hot Standby with Control Expert solution is a powerful feature of NOEs, a
feature that increases the reliability of your installation. Hot Standby uses a network, and using the
Hot Standby feature over a network can affect the behavior of:
browsers
remote and local clients
I/O scanning service
global data service
FTP/TFTP server
The following are factors you may encounter while using the Modicon Quantum Hot Standby with
Control Expert solution.
Browsers
If a browser requests a page and during the process of downloading that page an IP address
switchover occurs, the browser either hangs or times out. Click the Refresh or Reload button.
Remote Clients
Hot Standby switchover affect remote clients.
A NOE module resets under the following conditions:
Remote Connection Request during Hot Standby : If a remote client establishes a TCP/IP
connection during a Hot Standby switchover, the server closes the connection using a TCP/IP
reset.
Hot Standby Switchover during Remote Connection Request : If a remote client makes a
connection request and a Hot Standby switchover occurs during the connection request, the
sever rejects the TCP/IP connection by sending a reset.
Outstanding Requests : If there is an outstanding request, the NOE module does not respond to
the request, but the NOE module does reset the connection.
The NOE module does a Modbus logout if any connection has logged in.
Local Clients
During a switchover, the NOE module resets all client connections using a TCP/IP reset.
WARNING
UNINTENDED EQUIPMENT OPERATION - DEVICES GO TO THEIR FALLBACK STATES
DURING SWITCHOVER
Configure Ethernet output devices to their Hold Last Value fallback state whenever possible.
Output devices that support only a Set to Zero fallback state may produce a pulse during
switchover.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
NOTE: When you select hold last in a 140 CPU 651 •0 coprocessor, the input data may fall back
to 0 when the I/O scanner health bits are NOT OKAY. Confirm that the I/O scanner health bits are
valid (OK=1) before removing the Ethernet cable to maintain hold last value.
I/O scanning provides the repetitive exchange of data with remote TCP/IP nodes I/O devices.
While the PLC is running, the primary CPU NOE sends Modbus read/write, read, or write requests
to remote I/O devices, and transfers data to and from the PLC memory. In the secondary controller,
the I/O scanning service is stopped.
When the Hot Standby switchover occurs, the primary CPU NOE closes all connections with I/O
devices by sending a TCP/IP reset. The I/O scanning service in this NOE is standby CPU.
After the switchover, the new primary CPU NOE re-establishes the connection with each I/O
devices. It restarts the repetitive exchange of data with these re-connections.
The module provide the I/O scanning feature. Configure this feature with the Control Expert
software.
Using either method, the configuration and transfer of data between network addresses can be
done without using the MSTR/IEC function block.
NOTE:
Account for the following Ethernet I/O scanning considerations during a switchover.
If MSTR/IEC function block is used for TCP/IP, only some of the opcode is used. Therefore, the
block does not complete its transaction, and it returns error code 0•8000.
While the NOE module is in the process of performing the transaction, a new MSTR/IEC
function block may become active.
The output states of the scanned I/Os follows the state defined in the last value option
configured in the I/O scanning table of the NOE module (in Control Expert software).
These 2 states are either:
a. set to 0
b. hold last
With the above considerations, we recommend using switchover with Ethernet I/O scanning for
less critical applications.
FTP/TFTP Server
The FTP/TFTP server is available as soon as the module receives an IP address. Any FTP/TFTP
client can logon to the module. Access requires the correct user name and password. Modicon
Quantum Hot Standby with Control Expert allows only 1 active FTP/TFTP client session per NOE
module.
When the Hot Standby switchover occurs, the primary CPU and secondary NOEs close the
FTP/TFTP connection. If you send an FTP/TFTP request during the switchover, the
communication is closed.
Whenever you re-open communication, you must re-enter a user name and a password.
33002479 10/2019
Appendices
Introduction
The appendices provide supplementary reference information for the Quantum 140 NOE 771 xx
series of modules and the 140 NWM 100 00 module.
Appendix A
Maintenance
Maintenance
Introduction
This chapter details information about system maintenance including accessing and clearing the
crash log and downloading the new NOE exec.
Responding to Errors
Overview
The following information describes how to respond to errors on the NOE module.
Detecting Errors
When faults occur, the NOE module’s LED display can help you determine what went wrong. The
following figure shows the pattern that the LEDs should display during normal operation.
The Run indicator will be solid. The Coll (collision) LED may flash, indicating that collisions are
occurring on the Ethernet network. Such collisions are normal.
If a fault occurs, the normal LEDs may be extinguished or other indicators may light. This topic
discusses errors reported by the Active, Ready, Coll, Link, Kernel, Appl and Fault indicators.
For each type of error, try the suggested remedies in the order given. If no remedy suggested here
overcomes the error, call your local service representative or call Schneider Electric customer
service at 1-800-468-5342 for further directions.
Step Action
1 Make sure the NOE module and the controller are installed properly.
2 Verify that the controller is working; if it is not, replace it.
3 If neither the new controller nor the NOE module functions, replace the backplane.
4 Make sure that the number of network option modules (including NOE, NWM, NOM,
and CRP 811 modules) in the backplane is not exceeded:
140 CPU 311 10: 2 modules
140 CPU 670 60: 3 modules
140 CPU 434 12A, 140 CPU 534 14A, 140 CPU 651 x0, 40 CPU 652 60,
140 CPU 658 60, 140 CPU 671 60, 140 CPU 672 60, 140 CPU 672 61,
140 CPU 678 61: 6 modules
5 Check the version of the controller executive. You must have version 2.0 or later to
support the Ethernet module. Earlier versions do not recognize the module.
6 If steps 4 and 5 above check out ok, replace the NOE module.
Step Action
1 Make sure that power has been applied to the backplane.
2 If step 1 checks out ok, replace the NOE module.
Step Action
1 Make sure that the cable has been installed correctly and the module is functioning
properly.
2 Verify that the hub/switch is working properly.
3 If steps 1 and 2 check ok, replace the NOE module.
If Then
The Ready LED is on and the Kernel LED is The module has detected an invalid software
flashing image.
The Ready LED is on and the Kernel LED is An attempt to download a software image has
shining steadily, failed and the module is in kernel mode.
Either of the above conditions exists. Download a new NOE Exec (see page 350).
Fault LED
The Fault LED will flash briefly following an error as the module attempts to recover.
The following figure shows the Fault LED.
Step Action
1 Make sure that the cable has been installed and is working properly.
2 Verify that the Ethernet Hub/Switch is working properly.
Run LED
The following table describes the action to be taken if the Run LED is flashing. The action depends
on the number of flashes in sequence.
Application LED
If the module crashes, it will note the reason in a log. If the module is able to recover, the Appl LED
will light, indicating that an entry has been made in the crash log. You can read and clear the crash
log (see page 349).
Overview
The following information describes the crash log.
Introduction
The crash log provides you with the ability to capture conditions that lead to an anomalous
condition. By providing the crash log to Schneider Electric technical support, you can facilitate their
assistance in resolving your problems.
NOTE: The crash log is provided with the understanding that, with a complex product in thousands
of customer applications, there may be conditions that require advance diagnostics. The crash log
is one of the tools used to solve complex problems.
Step Action
1 Log in to the module’s FTP server.
2 Change the directory to wwwroot/conf/diag.
3 Perform an FTP to get the crash log file: get crash.log
Step Action
1 Log in to the module’s FTP Server.
2 Change the directory to wwwroot/conf/diag.
3 Perform an FTP to delete the crash log file: rm crash.log
Introduction
The following tools can be used to download a new NOE Exec:
Schneider Electric programming packages (see corresponding manuals)
FTP
Use the OS loader to update the NOE Executive and web pages. (Refer to the Control Expert
documentation.)
Exec Version
Please check the current NOE Exec file version on the NOE Properties Web page.
Follow these links: | Diagnostics | NOE Properties |
Procedure
The following procedure describes the steps to use to download a new NOE Exec via FTP. An
example follows the procedure.
Step Action
1 At the DOS prompt, type FTP, followed by the IP Address and press Enter.
2 At the User prompt, type: USER and press Enter.
3 At the password prompt, enter your FTP Password and press Enter.
4 At the FTP prompt, type cd wwwroot/conf/exec and press Enter.
5 At the FTP prompt, type put and press Enter.
Note: Pay attention that the NOE771xx.bin has to be to the local path on your PC
(default path: c:\).
6 At the local file prompt, type NOE771xx.bin and press Enter.
7 At the remote file prompt, type NOE771xx.bin and press Enter.
8 After the transfer is complete you must reboot the NOE to allow the new EXEC to
become operational.
Note: The file name is case-sensitive and must be entered with the name in
uppercase and the extension in lowercase as shown in the figure below.
For example: NOE771xx.bin
Procedure
The NOE Executive (Exec) adds a new feature that allows updating of the low level Kernel within
the NOE module’s firmware. For the proper installation of new kernel firmware, use the following
procedure.
Step Action
1 Check the current version of the NOE module’s Executive firmware (Exec file).
2 If the Exec is not the appropriate version, the Exec must be updated before updating
the Kernel.
3 Use the EXECLoader to load the latest version of the EXEC.
4 After loading the new Exec and before loading the Kernel, make sure to cycle power
to the NOE module.
5 Load the Kernel using the EXECLoader.
6 After the transfer displays as Successful, the NOE module needs approximately
1 minute to burn the new Kernel into its Flash memory.
7 The NOE module goes go through a reboot sequence.
Kernel Version
CAUTION
UNINTENDED EQUIPMENT OPERATION
Failure to perform the preceding update procedure will render the NOE module inoperable.
Failure to follow these instructions can result in injury or equipment damage.
Appendix B
Specifications
Specifications
Specifications
Communication Ports One auto-sensing 10/100 BASE-T shielded twisted pair (RJ-45 connector)
port and one 100 BASE-FX (MT-RJ connector) port. Both ports transmit
and receive Modbus commands encapsulated in TCP/IP protocol
Bus Current Required 750 mA
Power Dissipation 3.8 W
Fuse None
Programming Software
Type and version Concept, Ver. 2.2, or higher
Unity Pro, Ver. 1.0, or higher
Modlink, Ver. 2.0, or higher
Modsoft, Ver. 2.6, or higher
ProWORX NxT, Ver. 2.1, or higher
Firmware
CPU Type and version Quantum Executive, Ver. 2.0, or higher
NOE Upgradeable Field Upgradeable via FTP or Programming Panel.
Operating Conditions
Temperature 0 to +60° C
Humidity 0 to 95% Rh non condensing @ 60° C
Altitude 15,000 ft (4500 m)
Vibration 10-57 Hz @ 0.0075 mm d.a
57-150 Hz @ 1 g
Storage Conditions
Temperature -40 to +85°C
Humidity 0 to 95% Rh non condensing @ 60°C
Free Fall 1 m unpackaged
Shock 3 shocks / axis, 15 g, 11 ms
Specification Description
Communication Ports One auto-sensing 10/100 BASE-T shielded twisted pair (RJ-45
connector) port and one 100 BASE-FX (MT-RJ connector) port.
Both ports transmit and receive Modbus commands encapsulated
in TCP/IP protocol
Bus Current Required 900 mA
Power Dissipation 4.5 W
Fuse None
Programming Software
Type and version Concept, Ver. 2.6, or higher
Unity Pro, Ver. 1.0, or higher
Firmware
CPU Type and version Quantum Executive, Ver. 2.6, or higher
NOE Upgradeable Field Upgradeable via FTP or Programming Panel.
Operating Conditions
Temperature 0 to +60° C
Humidity 0 to 95% Rh non-condensing @ 60° C
Altitude 15,000 ft (4500 m)
Vibration 10-57 Hz @ 0.0075 mm d.a
57-150 Hz @ 1 g
Storage Conditions
Temperature -40 to +85°C
Humidity 0 to 95% Rh non-condensing @ 60°C
Free Fall 1 m unpackaged
Shock 3 shocks/axis, 15 g, 11 ms
Immunity
International Standard IEC 61131-2
US Standard UL 508
European Standard EN61131-2, EN50081-2
Canadian Standard CAN/CSA C22.2 No. 142
Agency Approvals UL: UL 508
CSA: CSA 142
CE: EN61131-2
Factory Mutual Class 1 Division 2
Appendix C
Quantum Ethernet TCP/IP Modbus Application Protocol
Introduction
This chapter describes the Quantum Ethernet TCP/IP Modbus Application Protocol.
Introduction
The following information describes the Modbus Application Protocol (MBAP).
The Modbus Application Protocol (MBAP) is a layer-7 protocol providing peer-to-peer
communication between programmable logic controllers (PLCs) and other host-based nodes on a
LAN. Collectively, these nodes implement all or part of a control application used for industrial
automation applications in the automotive, tire and rubber, food and beverage, and utilities
industries, to name a few
Client-Server Communications
Modbus protocol transactions are typical request-response message pairs between a client node
and a server node. These nodes function as follows
Client : The node that initiates a data transaction is called a client. The Modicon Quantum Ethernet
module provides the user with the capability to transfer data to and from nodes on a TCP/IP
network using a communication instruction. All PLCs that support networking communication
capabilities over Ethernet can use either the MBP_MSTR Ladder Logic instruction to read or
write controller information or IEC communication blocks.
Server : The node that receives an inquiry is the server. Using the standard Modbus/TCP protocol,
the Modicon Quantum Ethernet module provides access to controller data. Any device, PC, HMI
package, another PLC, or any Modbus/TCP compliant device can access data from the PLC.
The Modbus/TCP server also allows programming panels to log into the controller over
Ethernet.
Modbus requests contain function codes representing several classes of service including data
access, online programming, and program download and upload classes. Modbus responses can
be ACKs with and without data, or NACKs with error information.
The Modbus Application Protocol can be transmitted over any communication system that
supports messaging services. However, the current Quantum implementation transports Modbus
Application Protocol PDUs over TCP/IP. The Quantum PLC accommodates both Ethernet II and
IEEE 802.3 framing, although Ethernet II framing is the default.
Limitations
The Modicon Quantum Ethernet module supports up to 64 simultaneous Modbus/TCP server
connections. To guarantee consistency of changes to the controller configuration, the module
allows only one programming panel to be logged in at a time.
The module supports these Modbus/TCP commands:
Read Data
Write Data
Read/Write Data
Get Remote Statistics
Clear Remote Statistics
Modbus 125 Commands (used by programming panels to download a new exec to the module
Overview
The following information describes the structure and content of the Modbus Application Protocol
PDU.
Description
The Modbus Application Protocol PDU, mbap_pdu, is received at TCP port number 502. The
current maximum size of the mbap_pdu for this class of services is 256 bytes. The structure and
content of the mbap_pdu is defined to be:
mbap_pdu::={inv_id[2], proto_id[2], len[2],dst_idx[1], data=mb_pdu}
The header is seven bytes long and includes the fields listed in the following table:
Field Description
inv_id [2 bytes] invocation id used for transaction pairing
proto_id [2 bytes] used for intra-system multiplexing, default is 0 for Modbus services
len [2 bytes] the len field is a byte count of the remaining fields, and it includes the
dst_id and data fields
Field Description
dst_idx [1 byte] destination index is used for intra-system routing of packets (currently
not implemented)
data [n bytes] this is the service portion of the Modbus pdu, mb_pdu, and it is defined
below
The service portion of the Modbus Application Protocol, called mb_pdu, contains two fields:
mb_pdu::={func_code[1], data[n]}
The following table describes the fields in mb_pdu.:
Field Description
func_code{1 byte Modbus function code
data [n bytes] this field is function code dependent and usually
contains information such as variable references, variable
counts, and data offsets
The size and content of the data field are dependent on the value of the function code.
Example
Here are the values for a sample mbap_pdu for reading a register:
00 01 00 00 00 06 01 03 00 00 00 01
The following table shows the structure and content for this example:
inv_id 00 01
proto_id 00 00
len 00 00
dst_idx 01
func_code 03
data 00 00 00 01
Introduction
There are several classes of service that are part of the Modbus Application Protocol. Each of
these classes is described below.
Data Access
Read/write both discrete and analog data values from PLC register files.
Online Programming
Services make relatively minor alterations to ladder logic programs with a highly controlled
introduction of these changes into the executing program.
Image Download/Upload
Image download services support the downloading of a ladder logic control program to the PLC.
Image upload services support the uploading of a ladder logic control program from a PLC to PC
host for archival/backup purposes.
Configuration
Configuration services allow the user to define parameter values which affect the PIC’s register
files, I/O map, communication port configuration and scan attributes, to name a few.
Overview
The following information provides an analysis of the Modbus Application Protocol.
Analysis
The Modbus Application Protocol PDU is transmitted over a TCP/IP Ethernet stack. Both Ethernet
II and IEEE 802.3 framing will be accommodated. Ethernet II framing is the default.
. . . from the wire in for IEEE 802.3 framing . . .
. . . is IEEE 802.3 framing if length <=1500 . . .802.3_pdu ::=
{dst_addr[6], src_addr[6], length[2], data=802.2_pdu} *an IEEE 802.3
PDU has a maxFrameSize of 1518 octets
*an IEEE 802.3 PDU has a minFrameSize of 64 octets802.2_pdu : {dsap[1],
ssap[1], frm_cntrl[1], snap_hdr[5], data=ip_pdu} *the snap_hdr is
associated with a "well-known" 802.2 sap snap_hdr
::={org_code[3], ethertype[2] }
*the snap hdr (sub network access protocol) allows the older style
Ethernet protocols to run on the newer IEEE 802.2 interface. The
ethertype parameter indicates the service, ex. ip or arp. IP has a
value
0x800. . . . from the wire in for Ethernet II framing . . .
. . . is Ethernet II framing if length >1500 . . .802.3_pdu ::=
{dst_addr[6], src_addr[6], length[2], data=ip_pdu} . . . the common
part of the packet begins here . . .ip_pdu ::= {ip_hdr[20],
data=tcp_pdu}tcp_pdu ::= {tcp_hdr[24], data=appl_pdu=mbap_pdu}
The mbap_pdu is the Modbus Application Protocol whose messages are received at a well-known
port. The current maximum size of the mbap_pdu for this class of services in 256 bytes.
Overview
The following information describes some TCP/IP specific issues.
Broadcast/Multicast
Although broadcast and/or multicast are supported by both IP network address and IEEE 802.3
MAC address, the Modbus Application Protocol does not support either broadcast or multicast at
the application layer.
Schneider Electric’s Quantum PLCs use broadcast addressing because they use ARP as the
means of locating the destination node. The client interface to the Modbus Application Protocol
service on the PLC, the MBP_MSTR block, requires the user to provide the destination IP address.
Also the embedded stack does use a pre-configured default gateway IP address in the case where
ARP does not succeed.
Overview
A TCP connection can be closed by one of the following:
a remote station (which closes a connection by sending a TCP/IP connection closure message)
the local PLC
To identify which connection to close, the PLC examines groups of connections for inactive open
connections, in the following sequence:
1 non-referenced connections to devices that are not configured as part of the Control Expert
application
2 client connections
3 server connections
If the PLC discovers one or more inactive connections in the first group, it closes the oldest inactive
connection in that group then opens a new connection.
If no inactive connection is discovered in the first group, the PLC examines the second group of
connections and, if it discovers one or more inactive connections in the second group, the PLC
closes the oldest inactive connection in that group and opens a new connection.
If no inactive connection is discovered in the first and second groups, the PLC examines the third
group and, if it discovers one or more inactive connections in the third group, the PLC closes the
oldest inactive connection in that group and opens a new connection.
If the PLC fails to discover an inactive connection in any of the three groups, no open connection
is closed and no new connection can be opened.
NOTE: Closure of a connection is indicated to the application by means of a status report
(message refused) on any exchanges in progress.
Reference Documents
Overview
The following information provides a list of reference documents that you may find helpful.
Introduction
Following is a list of related documentation.
ANSI/IEEE Std 802.3-1985, ISO DIS 8802/3, ISBN - 0-471-82749-5, May 1988
ANSI/IEEE Std 802.2-1985, ISO DIS 8802/2, ISBN 0-471-82748-7, Feb 1988
RFC793, TCP (Transmission Control Protocol) DARPA Internet Program Protocol
Specification, Sep 1981
RFC 791, IP (Internet Protocol) DARPA Internet Protocol Specification, Sep 1981
RFC826, An Ethernet Address Resolution Protocol (ARP), David Plummer, NIC Sep 1982
RFC1042, A Standard for the Transmission of IP Datagrams over IEEE 802.2 Networks, Postel
& Reynolds, ISI, Feb 1988
RFC 792, ICMP (Internet Control Message Protocol) DARPA Internet C Control Message
Protocol Specification, Jon Postel, Sep 1981
RFC951, BOOTSTRAP PROTOCOL (BOOTP), Bill Croft and John Gilmore, September 1985
RFC783, The Trivial File Transfer Protocol (TFTP) rev 2, K.R. Solons MIT, June 1981
Appendix D
Installation and Configuration of a Modicon Quantum Platform
Overview
This quick start guide describes how to install and configure a Modicon Quantum Ethernet module.
It also sets up the I/O scanning service to allow data transfer to occur between the PLC and a
remote slave device. Instructions for connecting to the module’s embedded web server pages are
also provided at the end of the guide.
Overview
Introduction
This quick start guide explains how to install and configure Modicon Quantum Ethernet modules
and set up a I/O scanning communication service. The following types of modules are applicable
to this guide:
140 NOE 771 01
140 NOE 771 11
140 CPU 651 50
140 CPU 651 60
Hardware/Software Requirements
For the example discussed in this guide, the following Modicon Quantum Ethernet modules are
required:
140 CPS 114 x0 power supply
140 CPU 651 50 CPU
140 NOE 77101 communication module
Also, a PC running Windows 2000 or XP with Schneider’s Control Expert configuration software
installed on it is required.
Finally, either a USB or a Modbus cable is required to connect the PC to the network PLC.
Intended Audience
This user guide is intended for anyone who is involved in installing and configuring Modicon
Quantum Ethernet modules in a network arrangement that can perform a variety of communication
services.
Anyone reading this guide should:
be familiar with Ethernet networks and the TCP/IP protocol
understand the operation of PLCs
Installation
Introduction
The Modicon Quantum Ethernet modules used for the example in this guide may vary from the
ones available at your site. You can substitute the appropriate power supply, CPU, and Ethernet
communication module(s) and other Quantum modules to make up a rack similar to the one
described below.
Step Action
1 Insert the power supply into the leftmost slot (1) on the rack.
2 Add the CPU to the next two slots (2 & 3)on the right of the power supply.
3 Place the remaining Quantum communication modules, beginning with slot 4,
to complete your installation.
In our example (see below), we use a CPS 114 x0 power supply, a CPU 651 50 processor, and a
single NOE 771 01 Ethernet module to make up our rack.
Introduction
We begin this procedure by configuring the Modicon Quantum Ethernet module rack using
Control Expert configuration program.
Step Action
1 Start Control Expert software.
4 Select New in the File menu to create a New Project dialog box.
5 In the New Project dialog box, expand the Quantum family to select the installed processor (the
140 CPU 65150 in our example).
Step Action
6 In the project browser, double-click Station → Configuration → PLC bus to access the configuration of
the local rack (shown below).
Step Action
7 Double-click slot 4 to bring up the New Device menu to show the hardware catalog.
8 Double-click the module that goes in slot 4 (140 NOE 771 01 in our example, shown above).
Note: Alternately, you can click the module and drag it to the selected slot on the rack.
9 Repeat step 8 for each module included in your configuration.
The figure below shows the completed rack assembly for our example with the 140 NOE
771 01 module in slot 4.
Introduction
The following procedure describes how to add a new Ethernet network and link it to the Modicon
Quantum module we configured in the previous section.
Step Action
1 Locate the Communications directory in the Project browser.
2 Right-click the Network subdirectory located under the Communications
directory.
3 Select the New Network option to bring up the Add Network dialog box.
4 Scroll to Ethernet in the List of available Networks box.
5 Enter a meaningful name for your network in the Change Name field
(NOE77101 was used in our example).
6 Click OK.
Step Action
1 Double-click Local Bus in the Project browser to show the rack configuration.
2 Expand the Local Quantum Drop to show the ETHERNET port under the 140
NOE 77101.
5 Click the validate check box in the upper toolbar to confirm the network link
configuration.
Step Action
1 Locate the Communications\Networks directory in the Project browser.
2 Double-click your new logical network (NOE77101 in our example) to open the
NOE077101 configuration screen.
Introduction
The Modicon 140 NOE 771 01 module supports Ethernet communication services such as I/O
scanning, Global Data, Modbus messaging, SNMP, etc. This example shows you how to configure
the I/O scanning service. This service is used to:
transfer data between network devices
allow a CPU to regularly read data from and write data to scanned devices
Step Action
1 Open the Control Expert program on your PC.
2 In the Project Browser, locate the Communication → Networks sub-directory.
3 Click the network name (140 NOE 771 01 in our example) to open the module configuration table.
4 In the Module Utilities dialog, select Yes in the I/O Scanning field:
5 Click the I/O Scanning tab to display the I/O scanning configuration screen:
6 Type in the parameter settings under each of the column headings for the I/O Scanner Configuration.
Refer to the parameter definitions below.
Step Action
7 Click the validate check box in the upper tool bar to confirm the I/O scanning parameter settings.
Health Block
The Health Block (number 1 in previous figure) lets you define the first word or bit in a health table.
That table can be up to 8 words (%IW) or 128 bits (%I) in length. Each bit in the table represents
the status of an individual device. The table below shows how the bits are displayed based on the
data type you use.
By default, the table comprises words starting at %IW1.0. If you want to set the table to bits, you
need to specify a %I value in an increment of 16 (%I1, %I16, %I32, etc.).
NOTE: The Health Block is available only for the NOE 771 00, -01, and -11. It is not available for
the CPU 651 x0.
NOTE: For Safety Monitor applications, the Health Block is mapped on %M/%MW from the UMA
zone instead of %I/%IW.
If you attempt to enable the Device Control Block with an earlier version of the firmware, the I/O
scanning service is disabled.
If the check box is not selected, the I/O scanner service is enabled, and you cannot disable the I/O
scanning of individual devices.
Disabling I/O scanning with the Device Control Block is equivalent to ending communication
between the scanner and the device. Therefore:
The fallback positions are applied to the inputs by the scanner.
Communication with the device stops.
All entries in the IN and OUT tables transfer between the CPU and the scanner on each scan.
As a consequence of the last point above, if you modify a %MWi attached to an input, this %MWi
is overwritten by the values coming from the I/O scanner in the next scan (with either 0 or the last
input value).
It is possible (but meaningless) to access %MW attached to the outputs because they are not
transmitted to the device.
NOTE:
When using a bridge, enter the bridge index (1 to 255) in this
field.
If you are copying the I/O scanning configuration from a
140 NOE 771 •• to a 140 NOC 771 ••, set the Unit ID to a
value from 1 to 254.
Slave Syntax Use this drop-down menu to pick the way RD Ref Slave and WR Index (default value)
Ref Slave values are displayed. There are 4 types of display
available:
Index: 100
Modbus: 400101
(Modbus register)
IEC 0: %MW100
M340 and Premium PLC slaves
IEC 1: %MW101
Quantum PLC slaves
NOTE: For more information, refer to the Contextual Menu for Copy/Cut/Paste topic
(see page 210).
NOTE: For more information, refer to the I/O Scanning with Multiple Lines topic (see page 212).
Connection Options
In order to run the configuration program it must first be downloaded to the PLC. Prior to
downloading the program, the PLC must be connected to the PC containing the Control Expert
software. The connection can be accomplished using a communication network such as Ethernet,
USB, Modbus, or Modbus Plus cabling. We describe both the USB and Modbus cable setups in
the following examples.
Step Action
1 Ensure that the Quantum system is powered up.
2 Connect the PLC to the PC with a USB cable.
3 On the PC, click the Control Expert PLC\Set Address tab to bring up the Set Address dialog box.
Step Action
1 Ensure that the Quantum system is powered up.
2 Connect the PLC to the PC with a Modbus cable.
3 On the PC, click the Control Expert PLC\Set Address tab to bring up the Set Address menu.
Step Action
1 On the PC, select PLC \Connect on the Control Expert screen.
2 Click the PLC\Transfer Project to PLC tab to bring up the Transfer Project to PLC dialog box.
5 Click Run on the Control Expert upper toolbar to start the program.
Introduction
Quantum Ethernet modules have an embedded web server that provides web pages to diagnose
the Ethernet module services, such as statistics, I/O scanning, Messages, global data, etc. You
can access an Ethernet module's web pages by entering the IP address of the module in the web
browser. No password is required to display the home page. From the NOE home page, you can
access the Monitoring, Diagnostics, and Setup pages.
You can also use the module’s LED display to diagnose problems. For information regarding the
module’s LED display refer to the Quantum NOE 771xx Ethernet Modules User Manual.
Step Action
1 At the PC, start a Web browser such as Internet Explorer.
2 Enter the NOE 771 01’s currently assigned IP address in the Address field of
the browser to bring up the NOE’s home page.
Step Action
5 Click OK to bring up the NOE diagnostic web page.
6 Click the I/O Scanning link on the left-hand side of the screen to access the I/O
scanning diagnostics web page.
Glossary
A
ACK
Acknowledgement
address
On a network, the identification of a station. In a frame, a grouping of bits that identifies the frame’s
source or destination.
API
Application Program Interface. The specification of functions and data used by one program
module to access another; the programming interface that corresponds to the boundary between
protocol layers.
ARP
Address Resolution Protocol. A network layer protocol used to determine the physical address that
corresponds to the IP address for a host on the network. ARP is a sub-protocol that operates under
TCP/IP.
ASN.1
Abstract Syntax Notation. Grammar used to define a protocol (OSI scope)
B
BOOTP
BOOTstrap Protocol. A protocol used at power-up in order to get an IP address that is provided by
a BOOTP server and is based on the module’s MAC address.
bps
Bits per second.
bridge
A device that connects two or more physical networks that use the same protocol. Bridges read
frames and decide whether to transmit or block them based on their destination address.
BSP
Board Support Package. A software package that maps a specific real-time operating system
(RTOS0 onto a specific hardware.
C
client
A computer process requesting service from other computer processes.
D
default gateway
The IP address of the network or host to which all packets addressed to an unknown network or
host are sent. The default gateway is typically a router or other device.
DHCP
Dynamic Host Configuration Protocol. An improved version of BOOTP.
DHCP Client
Host on the network obtaining its configuration from a DHCP Server.
DHCP Server
Server providing configuration parameters to a DHCP Client.
DNS
Domain Name System. A protocol within TCP/IP used to find IP addresses based on host names
F
FactoryCast
An embedded Web server that the user customizes, permitting user access to controller
diagnostics and Ethernet configuration.
field
A logical grouping of contiguous bits that convey one kind of information, such as the start or end
of a message, an address, data, or an error check.
firewall
A gateway that controls access to a network or an application.
frame
A group of bits that form a discrete block of information. Frames contain network control
information or data. The size and composition of a frame is determined by the network technology
being used.
framing types
Two common framing types are Ethernet II and IEEE 802.3.
FTP
File Transfer Protocol. The protocol (over TCP) used to read or write a file into a remote station
(the FTP server side).
G
gateway
A device that connects networks with dissimilar network architectures and that operates at the
Application Layer. This term may refer to a router.
Global Data (Publish / Subscribe)
Service of inter PLC synchronization (shared databases).
H
half duplex
(HDX) A method of data transmission capable of communication in two directions, but only one
direction at a time.
host
A node on a network.
hostname
A domain name given to a specific computer on a network and used to address that computer.
HTTP
A domain name given to a specific computer on a network and used to address that computer.
hub
A device that connects a series of flexible and centralized modules to create a network.
I
I/O Drop
One or two (depending on the system type) Remote I/O Channels consisting of a fixed number of
I/O points.
I/O Map
An area in the controller configuration memory used to map input and output points. Previously
called traffic cop.
I/O Scan
A procedure the processor follows to monitor inputs and control outputs.
I/O Scan List
A configuration table that identifies the targets with which repetitive communication is authorized.
I/O scanner
Software component that is in charge of scanning Ethernet based Momentum IO in order to get
inputs and set outputs.
ICMP
Internet Control Message Protocol. A protocol within TCP/IP used to report errors in datagram
transmission.
Internet
The global interconnection of TCP/IP based computer communication networks.
IP
Internet Protocol. A common network layer protocol. IP is most often used with TCP.
IP Address
Internet Protocol Address. A 32-bit address assigned to hosts using TCP/IP.
L
layer
In the OSI model, a portion of the structure of a device that provides defined services for the
transfer of information.
Legacy
In the sense of network communication: Existing Components (PLC products etc.) that do not
provide special (hardware) support for Control Intranet.
M
MAC Address
Media Access Control address. The hardware address of a device. A MAC address is assigned to
an Ethernet TCP/IP module in the factory.
MBAP
Modbus Application Protocol
MBP_MSTR
A special master instruction that uses ladder logic to read and write controller information.
MIB
Management Information Base. Database that holds the configuration of a SNMP enabled device.
Modbus
A communication system that links Modicon controllers with intelligent terminals and computers
over common carrier or dedicated lines
N
NACK
Negative acknowledgment indicating an error.
NDDS
Network Data Delivery Services.
NetLink
The logical name of a network.
network
Interconnected devices sharing a common data path and protocol for communication.
node
An addressable device on a communications network.
NTP
Network Time Protocol. A protocol used to synchronize the time of a client or server to the time of
another server or referenced source like a satellite receiver.
O
OIT / OID
Object Information True / Object ID (identify OIT) Contain databases managing SNMP (MIBs)
OSI model
Open System Interconnection model. A reference standard describing the required performance
of devices for data communication. Produced by the International Standards Organization.
P
packet
The unit of data sent across a network.
Peer Cop
Software that allows you to configure data blocks to be transferred between controllers on a
Modbus Plus network.
PING
Packet Internet Groper. A program used to test whether a destination on a network can be
reached.
PLC
Programmable Logic Controller
port
An access point for data entry or exit within a host using TCP services.
protocol
Describes message formats and a set of rules used by two or more devices to communicate using
those formats.
R
repeater
A device that connects two sections of a network and conveys signals between them without
making routing decisions or filtering packets.
RFC
Request For Comment. Paper identified by a number in Internet world. They define the state of art
regarding Internet protocols (ruled by IETF = Internet Engineering Task Force) http://www.ietf.org
router
A device that connects two or more sections of a network and allows information to flow between
them. A router examines every packet it receives and decides whether to block the packet from the
rest of the network or transmit it. The router will attempt to send the packet through the network by
the most efficient path.
S
server
Provides services to clients. This term may also refer to the computer on which the service is
based.
SMTP
Simple Mail Transfer Protocol. A common protocol used to transfer e-mail messages.
SNMP
Simple Network Management Protocol
socket
The association of a port with an IP address, serving as an identification of sender or recipient.
stack
The software code that implements the protocol being used. In the case of the NOE modules it is
TCP/IP.
STP
Shielded Twisted Pair. A type of cabling consisting of several strands of wire surrounded by foil
shielding, twisted together.
subnet
A physical or logical network within an IP network that shares a network address with other portions
of the network.
subnet mask
A bit mask used to identify or determine which bits in an IP address correspond to the network
address and which bits correspond to the subnet portions of the address. The subnet mask is the
network address plus the bits reserved for identifying the subnetwork.
switch
A network device that connects two or more separate network segments and allows traffic to be
passed between them. A switch determines whether a frame should be blocked or transmitted
based on its destination address.
T
TCP
Transmission Control Protocol.
TCP/IP
A protocol suite consisting of the Transmission Control Protocol and the Internet Protocol; the suite
of communications protocols on which the Internet is based.
Transparent Factory
Transparent Factory is a Schneider Electric initiative to bring Internet technologies to the factory
floor to "information enable" Schneider Products to provide easy "transparent" access to plant
operational data over open networks with open tools. Interfacing with products from other
manufacturers for similar access, customers can expect improved methods for monitoring and
controlling factory processes at reduced costs.
Transparent Ready
A Schneider Electric product line based on universal Ethernet TCP/IP and Web technologies.
These industrial automation products (Trademark Telemecanique) and electrical distribution
products (TrademarkMerlin Gerin) can be integrated into real-time data sharing systems with no
need for interfaces. The product line includes Sensor and preactuator type field products (simple
or intelligent), controllers and PLCs, HMI applications, and dedicated gateways and servers.
U
UDP
User Datagram Protocol. A protocol that transmits data over IP.
Uni-Te
Télémecanique unified application protocol (used in S7, Premium, and Micro PLC ranges).
URL
Uniform Resource Locator. The network address of a file.
UTP
Unshielded Twisted Pair. A type of cabling consisting of insulated cable strands that are twisted
together in pairs.
W
Web
Worldwide interconnection of stations based on Internet protocols. The most famous one is HTTP
(Web server).
WWW
World Wide Web. A hypertext-based, distributed information system in which clients and servers
are freely available.
Index
I O
operating modes, 332
I/O scanner, 81, 199
configure quantum, 204
I/O scanning, 338
140CPU651x0 and 140NOE77101 scan
P
differences, 200 PRA
140NOE771•• to 140NOC771•• transfer, Control Expert, 224
207, 381 Properties web page
configure140 NOE 771 01, 378 Quantum, 322
multiple lines, 212
installing Ethernet devices
140NOE77100, 51
Q
140NOE77101, 51 Quantum
140NOE77110, 51 140CPU651x0 and 140NOE77101 scan
140NOE77111, 51 differences, 200
IP addresses, 326 Diagnostics web page, 287
Properties web page, 322
K
key switches, 31
R
keypads, 27 READ_REG, 127
remote clients, 337
restriction, 330
L
local clients, 337
S
scanning
M 140CPU651x0 and 140NOE77101 differ-
maintaining Ethernet modules, 343 ences, 200
managed variables, 231
MBAP, 357
MBP_MSTR, 135
change modbus plus address, 179
menus
high-end CPUs, 30
services
140CPU65150, 73
140CPU65160, 73
140NOE77100, 44, 73
140NOE77101, 44, 73
140NOE77110, 44, 73
140NOE77111, 44, 73
140NWM10000, 44, 73
address server, 76, 237
bandwidth monitoring, 86
embedded web pages, 88, 283
FDR, 237
FTP, 87
global data, 83, 185
I/O scanner, 81, 199
Modbus messaging, 79
NTP time synchronization, 84, 263
SMTP electronic mail notification, 85, 275
SNMP, 78, 247
SMTP electronic mail notification, 85, 275
SNMP, 78, 247
specifications
Ethernet modules, 355
T
TCP_IP_ADDR, 133
TFTP servers, 339
time synchronization, 84, 263
transferring data
communication blocks, 119
W
web pages
embedded, 88, 283
WRITE_REG, 130