modicon m251/m580 distributed pacs and altivar drives with

59
EIO0000004217.01 www.schneider-electric.com Modicon M251/M580 Distributed PACs and Altivar Drives with EIO0000004217 12/2020 Modicon M251/M580 Distributed PACs and Altivar Drives with EcoStruxure TM Automation Expert Hardware Reference Guide Original instructions 12/2020

Upload: others

Post on 06-Nov-2021

13 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Modicon M251/M580 Distributed PACs and Altivar Drives with

Modicon M251/M580 Distributed PACs and Altivar Drives with

EIO0000004217 12/2020

EIO

0000

0042

17.0

1

www.schneider-electric.com

Modicon M251/M580 Distributed PACs and Altivar Drives withEcoStruxureTM Automation ExpertHardware Reference GuideOriginal instructions

12/2020

Page 2: Modicon M251/M580 Distributed PACs and Altivar Drives with

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.© 2020 Schneider Electric. All rights reserved.

2 EIO0000004217 12/2020

Page 3: Modicon M251/M580 Distributed PACs and Altivar Drives with

Table of Contents

Safety Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5About the Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 1 Functionalities of Modicon M251/M580 dPACs and Altivar 6•• Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11IEC 61499 Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Firmware Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Operating States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Chapter 2 Network Topology Planning . . . . . . . . . . . . . . . . . . . . . . 29Project Life Cycle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Planning a Network Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Planning a Star Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Chapter 3 Configuring the M251/M580 dPAC or ATV6•• Drive . . . . 33Creating a Solution in EcoStruxureTM Automation Expert. . . . . . . . . . 34Configuring the M251/M580 dPAC or Altivar Drive Parameters . . . . . 37Configuring the NTP Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Integrating Modbus TCP Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Debug Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Chapter 4 Modbus Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Modbus Diagnostic Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

EIO0000004217 12/2020 3

Page 4: Modicon M251/M580 Distributed PACs and Altivar Drives with

4 EIO0000004217 12/2020

Page 5: Modicon M251/M580 Distributed PACs and Altivar Drives with

Safety Information

Important Information

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

EIO0000004217 12/2020 5

Page 6: Modicon M251/M580 Distributed PACs and Altivar Drives with

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

BEFORE YOU BEGINDo not use this product on machinery lacking effective point-of-operation guarding. Lack of effective point-of-operation guarding on a machine can result in serious injury to the operator of that machine.

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.

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

6 EIO0000004217 12/2020

Page 7: Modicon M251/M580 Distributed PACs and Altivar Drives with

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.

START-UP AND TESTBefore using electrical control and automation equipment for regular operation after installation, the system should be given a start-up test by qualified personnel to verify correct operation of the equipment. It is important that arrangements for such a check be made and that enough time is allowed to perform complete and satisfactory testing.

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.

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

EIO0000004217 12/2020 7

Page 8: Modicon M251/M580 Distributed PACs and Altivar Drives with

OPERATION AND ADJUSTMENTSThe 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.

8 EIO0000004217 12/2020

Page 9: Modicon M251/M580 Distributed PACs and Altivar Drives with

About the Book

At a Glance

Document ScopeThis guide provides detailed information about characteristics common to Modicon M251/M580 Distributed PACs and Altivar drives in a standalone distributed system when configured with EcoStruxure™ Automation Expert software.NOTE: The specific configuration settings contained in this guide are for instructional purposes only. The settings required for your specific configuration may differ from the examples presented in this guide.This guide is intended for users with knowledge of: IEC 61499 standards, content of services, data model, engineering process, etc. EcoStruxure Automation Expert software

Validity NoteThis document is valid for Modicon M251/ M580 dPACs, as well as ATV6•• drives when used with EcoStruxure™ Automation Expert 1.0 or later.The technical characteristics of the devices described in the present document also appear online. To access the information online:

The characteristics that are described 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.

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

EIO0000004217 12/2020 9

Page 10: Modicon M251/M580 Distributed PACs and Altivar Drives with

Related DocumentsYou can search and download related technical publications and other technical information from our website at https://www.se.com/us/en/download/.

10 EIO0000004217 12/2020

Page 11: Modicon M251/M580 Distributed PACs and Altivar Drives with

Modicon M251/M580 Distributed PACs and Altivar Drives withFunctionalitiesEIO0000004217 12/2020

Functionalities of Modicon M251/M580 dPACs and Altivar 6•• Drives

Chapter 1Functionalities of Modicon M251/M580 dPACs and Altivar 6•• Drives

OverviewThis chapter provides information on the functionalities of Modicon M251/M580 dPACs and Altivar 6•• drives when configured with EcoStruxure Automation Expert software.

What Is in This Chapter?This chapter contains the following topics:

Topic PageIEC 61499 Functionality 12

Firmware Update 20

Operating States 22

EIO0000004217 12/2020 11

Page 12: Modicon M251/M580 Distributed PACs and Altivar Drives with

Functionalities

IEC 61499 Functionality

OverviewNOTE: This topic assumes you have basic knowledge of IEC 61499 standards, content of services, data model, engineering process, and so forth.You can instantiate every function block described in the IEC 61499 standard in your application in an M251/M580 dPAC or Altivar drive system.

IEC61499 Function BlocksThis figure shows the function blocks that are part of the IEC 61499 Standard in the EcoStruxure Automation Expert configuration software.

12 EIO0000004217 12/2020

Page 13: Modicon M251/M580 Distributed PACs and Altivar Drives with

Functionalities

E_CTUThe E_CTU function block behavior in an M251/M580 dPAC or Altivar drive system is as follows: The CU event input: Increments the value of the CV output by one. Captures the value of the PV input. Fires the CUO event. Shows the Q output as true if the PV input value is equal or greater than the CV output value.

Confirm that the maximum value at PV is smaller than 65535. The R event input: Sets the CV output to the value 0. Sets the Q output to FALSE. Fires the RO event.

E_CYCLEThe E_CYCLE function block behavior in an M251/M580 dPAC or Altivar drive system is as follows: When a START event is detected, the value of the DT input is captured, and a cyclic timer starts. The EO event is fired every time the DT period expires. The time restarts and remains active until a STOP event is applied. If a timer is already active and a new START event is applied, the event is ignored. A STOP event cancels a current active timer and will be ignored when no timer is active. If the DT input is set to 0, the minimum cycle time is internally set to a default value. The minimum value on the DT input is possible.

NOTE: A small value on the DT input generates a high frequency of output events that significantly increases the processor load.

The maximum value on the DT input is possible. The EO event fires every time the DT period expires.

E_DELAYThe E_DELAY function block behavior in an M251/M580 dPAC or Altivar drive system is as follows: When a START event is detected, the value of the DT input is captured and a delay-timer starts. The EO event is fired when the timer expires. The timer does not restart. Only a new START event activates the timer again. If a delay timer is already active a new START event is applied, the event is ignored. A STOP event cancels and RESETS the current active timer. A STOP event is ignored when no timer is active. If the DT input is set to 0, the START event is immediately passed through to the EO event

output within a minimum internal delay. The minimum value on the DT input is possible. The maximum value on the DT input is possible. The EO event fires when the timer expires.

EIO0000004217 12/2020 13

Page 14: Modicon M251/M580 Distributed PACs and Altivar Drives with

Functionalities

E_DEMUXThe E_DEMUX function block behavior in an M251/M580 dPAC or Altivar drive system is as follows: This function block implements an event demultiplexer. An input event is passed to different

selectable outputs. At every EI event, the K input value selects the EOn event output line where the input event

is passed. Regarding EO0, EO1, and EO2 event outputs, depending on the value of the K input, only

one of the event outputs pass the event through. The K input value selects which EOn event output passes through. The K input value is

limited to the maximum number of EO event outputs. If the value exceeds the limit, then no output event is fired.

E_D_FFThe E_D_FF function block behavior in an M251/M580 dPAC or Altivar drive system is as follows: In a CLK input event, if the D input value is not equal to the Q output value, then Q is set to D. The EO event fires. In a CLK input event, if the D input value is equal to the Q output value, then Q does not change. The EO event does not fire.

E_F_TRIGThe E_F_TRIG function block behavior in an M251/M580 dPAC or Altivar drive system is as follows: When an EI input event occurs: The current status of the QI input is carried. The current status of the QI input is compared with the one captured at the previous EI event.

NOTE: If the QI input status did not change or transitioned from FALSE to TRUE, no EO event fires.

E_MERGEThe E_MERGE function block behavior i an M251/M580 dPAC or Altivar system is as follows: The E_MERGE function block passes incoming events of different inputs to one common event

output. Incoming events on EI1 event input or EI2 event inputs are immediately passed to the EO

event output. The order of events at EI1 and EI2 event inputs is not relevant. The sum of input events

equals the number of output events.

14 EIO0000004217 12/2020

Page 15: Modicon M251/M580 Distributed PACs and Altivar Drives with

Functionalities

E_N_TABLEThe E_N_TABLE function block behavior in an M251/M580 dPAC or Altivar system is as follows: When a START event arrives: The values of N input and DT input are read. Then, one output event at EO[0] is produced after period TIME[0].

The next event fires at EO[1] after TIME[1] period. This process continues until the N event outputs have been fired.

A subsequent START event can trigger a new set of output events. If a new START event arrives before the set of events has been fired entirely, the function block

starts up again from the beginning. Events that have not been fired within the last period (because the time between the two START events was too short) are discarded.

When a STOP event input arrives The event generation can be stopped. It is ignored when there was no prior START event.

A DT input value is interpreted as an array of the IEC-TIME duration format, for example t#1s,t#20ms,t#4s. The maximum number of entries is equal to the number of event outputs of the function block.

An N input defines the number of events to generate. If the value of N input is larger than the number of event outputs of the function block, N is

truncated. If the value of N input is smaller than the number of entries in the DT list, only the first entries

(as much as N) work. The remaining entries are ignored.

E_PERMITThe E_PERMIT function block behavior in an M251/M580 dPAC or Altivar system is as follows: This function block passes an incoming event to the output event when a condition is TRUE. An event at EI event input is passed to the EO event output when the status of the PERMIT

input is TRUE. If PERMIT is FALSE, then the input event is purged.

E_RENDThe E_REND function block behavior in an M251/M580 dPAC or Altivar drive system is as follows: EI1 event input: If an EI2 event is stored: Clear the EI2 event. Fire the EO event.

– or – Store the EI1 event internally.

EI2 event input: If an EI1 event is stored: Clear the EI1 event. Fire the EO event.

EIO0000004217 12/2020 15

Page 16: Modicon M251/M580 Distributed PACs and Altivar Drives with

Functionalities

– or – Store the EI2 event internally.

R event input: Clear a stored EI1 event. Clear a stored EI2 event.

E_RESTARTThe E_RESTART function block behavior in an M251/M580 dPAC or Altivar drive system is as follows: A COLD event is generated when a system is started (booted or full deploy). An ONLINECHANGE event is generated after successfully performing an online change.

E_RSThe E_RS function block behavior in an M251/M580 dPAC or Altivar drive system is as follows: If Q is FALSE, and an event at input S occurs: Q is TRUE. EO fires an event.

If an event at input S occurs: Q is TRUE (does not change its state). EO does not fire an event.

If Q is TRUE, and an event at input R occurs: Q is FALSE. EO fires an event.

If [x] events at input R occur: Q is FALSE (does not change its state). EO does not fire an event.

E_R_TRIGThe E_R_TRIG function block behavior in an M251/M580 dPAC or Altivar drive system is as follows: If an EI input event occurs: The current status of the QI input is captured. The current status of the QI input is compared with the one captured at the previous EI event.NOTE: If the QI input status did not change or transitioned from TRUE to FALSE, no EO event fires.

If an EI input event occurs: The current status of the QI input is captured. The current status of the QI input is compared with the one captured at the previous EI event.NOTE: If the QI input status transitioned from FALSE to TRUE, an EO event fires.

16 EIO0000004217 12/2020

Page 17: Modicon M251/M580 Distributed PACs and Altivar Drives with

Functionalities

E_SELECTThe E_SELECT function block behavior in an M251/M580 dPAC or Altivar drive system is as follows: This function block passes events of the selectable inputs to one common event output. If the G input is FALSE, then all events from EI0 are passed to the EO event output, or all

events from EI1 are passed to the EO event. The status of the G input selects which event is passed to the output.

E_SPLITThe E_SPLIT function block behavior in an M251/M580 dPAC or Altivar drive system is as follows: This function block passes events of two selectable inputs to one common event output. If the G input is FALSE, then all events from EI0 are passed to the EO event output, or all

events from EI1 are passed to the EO event output. The status of the G input selects which event is passed to the output.

E_SRThe E_SR function block behavior in an M251/M580 dPAC or Altivar drive system is as follows: If Q is FALSE, and an event at input S occurs: Q is TRUE. EO fires an event.

If an event at input S occurs: Q is TRUE (does not change its state). EO does not fire an event.

If Q is TRUE, and an event at input R occurs: Q is FALSE. EO fires an event.

If [x] events at input R occur: Q is FALSE (does not change its state). EO does not fire an event.

E_SWITCHThe E_SWITCH function block behavior in an M251/M580 dPAC or Altivar drive system is as follows This function block passes events of two selectable inputs to one common event output. If the G input is FALSE, then all events from EI0 are passed to the EO event output, or all

events from EI1 are passed to the EO event output. The status of the G input selects which event is passed to the output.

EIO0000004217 12/2020 17

Page 18: Modicon M251/M580 Distributed PACs and Altivar Drives with

Functionalities

E_TABLEThe E_TABLE function block behavior in an M251/M580 dPAC or Altivar drive system is as follows: The number of events is defined by the N input, and the time interval between the output events

is given by the time array set on the DT input. When a START event is detected, the values of the N input and the DT input are read. An output event at EO is produced after a period of TIME[0]. The CV output is set to 0, which is the current event index. The next event is produced after a period of TIME[1]. The CV output is set to 1. And so on, until the number of events fired at EO matches the value of N. A subsequent START event can trigger a new set of output events. The event generation can be stopped by the STOP event input. A STOP event is ignored when there was no prior START event. If a new START event arrives before the set of events has been fired completely, the function

block starts up again from the beginning. Events that have not been fired within the last period are discarded (because the time between

the two START events was too short). The DT input value is interpreted as an array of the IEC-TIME duration format, for example:

“[t#5s,t#120ms,t#4s]”. The maximum number of entries is implementation-dependent (standard is 16). The N input defines the number of events to generate. If the value of the N input is larger than the number of entries in the list of DT, N is truncated. If the value of the N input is smaller than the number of entries in the list of DT, only the first

entries work (as much as N). The remaining entries are ignored. N cannot be larger than the DT array. The time for generating events that are not parametrized at DT is not defined, but the events fire

anyway.

E_TRAINThe E_TRAIN function block behavior in an M251/M580 dPAC or Altivar drive system is as follows: When a START event is detected, the values of the N input and the DT input are read. The N output events at EO are generated with an interval defined by the DT input. The CV output is updated at every event with the event index, which starts: At the value 0 to N-1. For the first EO event, CV is 0. For the second EO event, CV is 1.

The event generation can be stopped by the STOP input event. A STOP event is ignored when there was no prior START event. A subsequent START event can trigger a new train of output events. According to the IEC61499-1 standard definition, the block creates one event even when N is 0.

18 EIO0000004217 12/2020

Page 19: Modicon M251/M580 Distributed PACs and Altivar Drives with

Functionalities

The CV value is not updated. If the DT input is set to 0, the START event immediately passes through to the EO output event

within a minimum internal delay.

EIO0000004217 12/2020 19

Page 20: Modicon M251/M580 Distributed PACs and Altivar Drives with

Functionalities

Firmware Update

OverviewUsing the EcoStruxure Automation Device Maintenance tool, you can update the firmware of discovered devices by selecting the firmware package of the devices to update. You can select firmware packages for more than one device, and the tool simultaneously updates the firmware of all devices selected.The tool alerts you regarding whether the selected firmware update is an upgrade, a downgrade, or the same version, which allows you to help prevent uploading incompatible firmware versions.

Updating the FirmwareFollow these steps to update the firmware using EcoStruxure Automation Device Maintenance:

Interrupting the UpdateInterrupting the update procedure before it has completed may cause irreparable damage to the device.

Step Action1 Select the CPU you want to update in the Package Name drop-down list.

2 Confirm that the information is in accordance with the selected package.

3 Select Device/Loading.4 Select Add a Device and enter the parameters in each field.

5 Use the default IP address: 10.10.xx.yy xx = the base 10 number of the fifth number of the MAC address yy = the base 10 number of the last number of the MAC address

6 A green light appears on the left side of the Device dialog.Enter the pass code, which indicates that the communication is established between the CPU and maintenance tool.

7 If the IP address is: valid: The green light stays on. invalid: The green light stays off.

8 Select Update Firmware and confirm that update begins.

20 EIO0000004217 12/2020

Page 21: Modicon M251/M580 Distributed PACs and Altivar Drives with

Functionalities

NOTICEEQUIPMENT DAMAGEDuring the transfer of the firmware file: Do not power OFF the device. Do not power OFF the PC. Do not shut down the EcoStruxure Automation Device Maintenance tool. Do not disconnect the communication cable.Failure to follow these instructions can result in equipment damage.

EIO0000004217 12/2020 21

Page 22: Modicon M251/M580 Distributed PACs and Altivar Drives with

Functionalities

Operating States

IntroductionThis topic describes the operating states of M251/M580 dPACs and Altivar drives when configured with EcoStruxure Automation Expert.

1 All outputs are at 0, which means that no energy is available to turn on actuators in this state.NOTE: A firmware suspended/system error state is managed by the device firmware.These are the different sequence of events that can affect the operating states of devices in M251/M580 dPAC and Altivar systems.

Device State RT State Application Outputs Modbus TCP OPCUA Server

Started Started Running Controlled Running RunningStopped Stopped Stopped Fallback

StateNot Running Not Running

Cleaned Cleaned No Security State1

Not Running Not Running

Halted Halted — Fallback State

Not Running Not Running

Suspended — — Security State1

Not Running Not Running

22 EIO0000004217 12/2020

Page 23: Modicon M251/M580 Distributed PACs and Altivar Drives with

Functionalities

NOTE: The fallback state is configurable on Modicon X80 I/O modules.

Cold Start

If a valid boot project does not exist, the device performs a cold start by: booting and accepting connections from EcoStruxure Automation Expert starting the newly deployed application with the default values and parametersIf a valid boot project does exist, the device performs a cold start by: booting automatically in Running state with the existing boot project that contains default valuesNOTE: Persistent configuration parameters (like NTP and IP address) are retained during a cold start.Performing a Cold StartFor example, if a device has the following state: The device is in Running state with a valid application and I/O modules configured in the system. A boot project archive has not been deployed to the device. A power off/on event is performed.After the power cycle, the device reboots without the application and configuration. Follow this process.

For details on device reboot, refer to the EcoStruxureTM Automation Expert online help.

WARNINGAUTOMATIC APPLICATION START AFTER DEVICE REBOOTEnsure that the application can start safely after a voluntary or involuntary device reboot.Failure to follow these instructions can result in death, serious injury, or equipment damage.

Step Procedure

1 Reconnect to the device with its IP address or via the USB port.Result: The diagnostic screen in EcoStruxure Automation Expert shows that the application and the device are not synced with each other.

2 Deploy the application to the device.3 Use STOP and START commands just as you would after a new power cycle.

4 The E_RESTART cold output is set to 1.

EIO0000004217 12/2020 23

Page 24: Modicon M251/M580 Distributed PACs and Altivar Drives with

Functionalities

Start/StopYou can perform a start-to-stop operation on the device.1. In the Deploy and Diagnostic tab, connect to the device.2. Click the drop-down arrow in the up/down field of the Action column (only if an application has

already been deployed and the device is synced) to perform.3. Select Device actions → Stop when the device is started.

Boot Power OnYou can boot a device in a known state as defined in your configuration and then connect to EcoStruxure Automation Expert.The system boots to a working state when you turn on power. The system then loads the last known configuration, gets ready to run the current program (if any exist), and accepts user connections for further configuration.The system retains the previous user configuration if that configuration is loaded before you turn off power.If a boot project exists in the target, the device reloads the boot project after a power cycle.

HaltThe device enters a HALT state if an application executes in an unexpected manner. The following items are some of the reasons a device can go to a HALT state: an external event broadcast storm throttling 750 ms warning and 20 ms pause excess of one million events event queue overflow from device overload or function blocks throttling function blocks throttling from device overload or endless loop in the system ST code

Forcing Inputs/Outputs

NOTE: When variables are forced using a watch event or logging off, no pop-up message is displayed indicating that forced variables are used in the application.

WARNINGUNEXPECTED FORCED VALUES BEHAVIOR Before connecting to devices, ensure that the values forced in the engineering tool are safe to

apply to these devices as soon as they are connected. When forcing values from an HMI, ensure you unforce the values before closing the HMI. When forcing values, do not disconnect the devices.Failure to follow these instructions can result in death, serious injury, or equipment damage.

24 EIO0000004217 12/2020

Page 25: Modicon M251/M580 Distributed PACs and Altivar Drives with

Functionalities

When forced and unforced events occur, only one variable can be selected. A forced output is possible only from an application, not from the hardware configuration. A forced output is lost after the device reboots and can be reapplied after you log in again to the

same application.

For details on forcing inputs/outputs, refer to the EcoStruxureTM Automation Expert online help.

Detected Error Management An invalid application that causes an unrecoverable error does not restart automatically. View the log to understand the detected errors in the application. Refer to the EcoStruxure

Automation Expert online help for details in the log. A critical error that causes the device to stop working is logged so that the product can be

analyzed by Schneider Electric experts.

FallbackYou can define safe defaults in your application in the event of detected errors or interruption of communications. You can select between fallback (i.e., predefined value) or maintain (i.e., keep current value) states for: analog outputs (per module) discrete outputs (per module)

Events Sent by EcoStruxure Automation Expert

Software event Description

Deploy Loads the created loading data on the selected device.Clear Deletes the currently loaded data on the device.

Query FB types Query the available functional blocks on the device.

Create Boot Project Archive Creates a boot project. Archive from the loading data.Delete with Boot Project Loads the created loading data and archives the boot project

(automatically started after the device is started).Delete Boot Project Deletes the current boot project on the device.

Start Device Sets the runtime system on the device to RUN.Stop Device Sets the runtime system on the device to STOP.

Deploy Via SCP Loads the created loading data via SCP.

Deploy License Loads the selected license on the device.Deploy Configuration Loads the current configuration on the device.

Fetch Log File Loads the current log files from the device on the engineering computer.

EIO0000004217 12/2020 25

Page 26: Modicon M251/M580 Distributed PACs and Altivar Drives with

Functionalities

Events Sent by Runtime or Device Firmware

Connectivity with the NTP ServerThe runtime moves to Started state if there is no connection recognized with the NTP server.

LED ManagementOperating state description via LEDs:

Fetch Persistent Data Loads the current persistence files from the device on the engineering computer.

Reboot Runtime Starts the entire device anew.

Forcing I/O Kept when the EcoStruxure Automation Expert software connection is lost.

Lost when the software powers off and then on.

Software event Description

Detected system error Effect

Suspended task The detected error is logged, and the device is rebooted in clean state.

Processor exception The detected error is logged, and the device is rebooted in clean state.

Hardware watchdog The device is rebooted in clean state and logs the detected error.

750 ms without IDLE task The data is logged by the EcoRT.Pause on event processing 20 ms The data is logged by the EcoRT.

Event queue full The device is halted.

Device description ATV M251 M580empty/cleaned MS

RUN (green)50 ms ON/1 s OFF

RUN (green)50 ms ON/1 s OFF

RUN (green)50 ms ON/1 s OFF

stopped MSRUN (green)500 ms flashing

RUN (green)500 ms flashing

RUN (green)500 ms flashing

started/running MSRUN (green)Continuous ON

RUN (green)Continuous ON

RUN (green)Continuous ON

reboot after suspended MSERR (red)500 ms flashing

ERR (red)500 ms flashing

ERR (red)500 ms flashing

26 EIO0000004217 12/2020

Page 27: Modicon M251/M580 Distributed PACs and Altivar Drives with

Functionalities

halted MSERR (red)Continuous ON

ERR (red)Continuous ON

ERR (red)Continuous ON

backup ON: SD card is missing or inoperable, or CPU flash memory is missing SD card is not usable SD card is inconsistent with the current application or CPU flash memory

is inconsistent with the current application.

OFF: SD card or CPU flash memory content is valid, and the application in the

execution memory is identical.

forced MSRUN (green)50 ms ON/50 ms OFF

I/O (green50 ms ON/50 ms OFF

FORCED I/O (red)50 ms ON/50 ms OFF

Device description ATV M251 M580

EIO0000004217 12/2020 27

Page 28: Modicon M251/M580 Distributed PACs and Altivar Drives with

Functionalities

28 EIO0000004217 12/2020

Page 29: Modicon M251/M580 Distributed PACs and Altivar Drives with

Modicon M251/M580 Distributed PACs and Altivar Drives withNetwork Topology PlanningEIO0000004217 12/2020

Network Topology Planning

Chapter 2Network Topology Planning

NOTE: The architectures described in this document have been tested and validated in various scenarios. If you intend to use architectures different than the ones described in this document, test and validate them thoroughly before implementing.

What Is in This Chapter?This chapter contains the following topics:

Topic Page

Project Life Cycle 30Planning a Network Topology 31

Planning a Star Topology 32

EIO0000004217 12/2020 29

Page 30: Modicon M251/M580 Distributed PACs and Altivar Drives with

Network Topology Planning

Project Life Cycle

Project Life CycleBefore you turn to the topic of planning your network topology, it may be helpful to see the life cycle of a project within a M251/M580 dPAC or Altivar drive system.

30 EIO0000004217 12/2020

Page 31: Modicon M251/M580 Distributed PACs and Altivar Drives with

Network Topology Planning

Planning a Network Topology

Key Points when Planning a TopologyConsider these key points when you plan a network topology: distributed equipment requirements isolation requirements (e.g., if the local rack and the distributed equipment are on different

grounding systems)Utilize optical fiber cables and conversion modules when distance between distributed equipment is greater than 100 m.These points are discussed in subsequent topics.

Isolation RequirementsFollow all local and national safety codes and standards.

If isolation is required in your network (e.g., if the distributed equipment you are trying to connect are on different grounding systems), use fiber cable to connect the devices.Refer to the ground connections information in the Electrical installation guide to comply with EMC certifications and deliver expected performance.

DANGERHAZARD OF ELECTRIC SHOCKIf you cannot prove that the end of a shielded cable is connected to the local ground, the cable must be considered as dangerous and personal protective equipment (PPE) must be worn.Failure to follow these instructions will result in death or serious injury.

EIO0000004217 12/2020 31

Page 32: Modicon M251/M580 Distributed PACs and Altivar Drives with

Network Topology Planning

Planning a Star Topology

OverviewThe following graphic represents an M251/M580 dPAC or Altivar drive network in a star topology for vertical and cross communication.

A EcoStruxure Automation Expert-basedB Control Expert-based1 PC on the control network programmed with EcoStruxure Automation Expert (EAE) + EcoStruxure

Automation Device Management (EADM) + EcoStruxure Control Expert 2 UMAS protocol to access unallocated and allocated memory from the dPAC to the SCADA system /

Modbus TCP3 EAE HMIs on the control network4 EAE fieldbus5 OPC UA6 SCADA on the control network7 Modbus TCP / Nxt fieldbus / OPC UA8 Modbus TCP9 switch/router10 device star topology11 Modbus TCP12 Ethernet IP + RSTP

32 EIO0000004217 12/2020

Page 33: Modicon M251/M580 Distributed PACs and Altivar Drives with

Modicon M251/M580 Distributed PACs and Altivar Drives withConfigurationEIO0000004217 12/2020

Configuring the M251/M580 dPAC or ATV6•• Drive

Chapter 3Configuring the M251/M580 dPAC or ATV6•• Drive

IntroductionThis chapter describes how to configure the M251/M580 dPAC or ATV6•• drive.

What Is in This Chapter?This chapter contains the following topics:

Topic Page

Creating a Solution in EcoStruxureTM Automation Expert 34

Configuring the M251/M580 dPAC or Altivar Drive Parameters 37Configuring the NTP Client 43

Integrating Modbus TCP Devices 44

Debug Function 45

EIO0000004217 12/2020 33

Page 34: Modicon M251/M580 Distributed PACs and Altivar Drives with

Configuration

Creating a Solution in EcoStruxureTM Automation Expert

IntroductionIf you have not created a solution in EcoStruxure Automation Expert and installed a power supply and a controller, use the following steps to create a new solution containing these components: M251/M580 dPAC or Altivar drive power supply

Creating and Saving an EcoStruxure Automation Expert Solution

Configuring the IP Address of an Identified DeviceBefore you download the solution to the M251/M580 dPAC or Altivar drive, configure the IP address using EcoStruxure Automation Device Management (EADM). You can add a new device if the device is automatically discovered by the tool.

Step Action

1 Open EcoStruxure Automation Expert.

2 Select File → New → Solution.3 In the New Solution dialog box, select your desired solution from the template list:

Proposal Full Solution Starter Kit

NOTE: Refer to the EcoStruxure Automation Expert help to select the appropriate solution, depending upon your distributed equipment requirements.

4 Type a name for your solution in the dialog box and select Save.Result: Your solution appears as a node in the structure; it shares the same name as the solution itself.

5 To create function blocks within your solution node, refer to the EcoStruxure Automation Expert help. If you want to use function blocks from other solutions, use the Export and Import options by right-clicking your solution node.

Step Action

1 To add an identified device, select the Device/Loading tab in EADM.2 Select the Add button in the Device/Loading window.

34 EIO0000004217 12/2020

Page 35: Modicon M251/M580 Distributed PACs and Altivar Drives with

Configuration

NOTE: EcoStruxure Automation Device Management (EADM) checks the consistency of the IP

address parameters before sending them to the M251/M580 dPAC or Altivar drive. The same IP address is set on the three Ethernet ports on the front face of the module and on

the Ethernet backplane port on the back of the module. The addresses are set the next time you reboot the M251/M580 dPAC or Altivar drive.

The IP address of the USB port cannot be modified (90.0.0.1).

Configuring the IP Address of an Unidentified DeviceConfigure the IP address of a new device that is not automatically discovered by the tool.

3 Enter appropriate data in the Add Device dialog: IP address: Type the desired IP address Identification via: Select the method for EADM to identify the device in the drop-down list: Modbus TCP DPWS (Device Profile for Web Services)

If you select Modbus TCP, Port and Slave node fields display beneath the Identification via field. Enter desired values: Port Slave Node

4 Select the Perform device discovery icon on the main toolbar.

5 These items that appear on the right side of the window are optional: Device Family Firmware Device Name Data Package

6 Select the OK button.

Step Action

Step Action1 To add an unidentified device, select the Device/Loading tab in EADM.

2 Select the Add button in the Device/Loading window.

3 Enter the IP Address in the Add Device dialog and click OK.Result: The Unidentified Device dialog opens asking if you want to add an unidentified device. Select Yes. The tool adds the unidentified device. the package list is not filtered for unidentified devices.

4 Select the compatible data device package from the Select Package drop-down list.

5 Select the Device login icon.Result: The Manage Setting dialog opens.

6 Enter the device name and password in the Device User Name and Device password fields.7 Select Save.

EIO0000004217 12/2020 35

Page 36: Modicon M251/M580 Distributed PACs and Altivar Drives with

Configuration

Downloading a Solution to the M251/M580 dPAC or Altivar DriveDownload the EcoStruxure Automation Expert application to the M251/M580 dPAC or Altivar drive by connecting the programming PC that contains the solution to the USB port on the device.NOTE: For details, refer to the EcoStruxure Automation Expert online help.

Downloading the Initial ConfigurationWhen you install the M251/M580 dPAC or Altivar drive for the first time, it: Sets the default IP address parameters. Sets the subnet mask and default gateway addresses.

36 EIO0000004217 12/2020

Page 37: Modicon M251/M580 Distributed PACs and Altivar Drives with

Configuration

Configuring the M251/M580 dPAC or Altivar Drive Parameters

IntroductionThe M251/M580 dPACs and Altivar drives have firmware plug-ins that allow a simple first-time plug-in deployment with EcoStruxure Automation Expert. The following features are pre-configured: discovery location provision IP address name setting

Configuration AccessFor detailed configuration once you install the controller device, follow these steps:

Configuration ParametersThe following features are configurable:

Step Action

1 Expand your solution in the Solution Overview dialog.2 Navigate to your solution and expand the System to display your devices.

3 Select the Device List tab in the configuration Editor.4 Select the desired value from the drop-down list for each parameter.

Parameter Sub-Parameter Description

AuthenticationPlugin Select the desired plug-in from the drop-down list.

Use encryption Websocket secure: True = Use. False = Do not use.

Ignore certificate errors True = Ignore certificate errors. False = Do not ignore certificate errors.

DiagnosticPlugin Select the desired plug-in from the drop-down list.

Use encryption Websocket secure: True = Use. False = Do not use.

Ignore certificate errors True = Ignore certificate errors. False = Do not ignore certificate errors.

EIO0000004217 12/2020 37

Page 38: Modicon M251/M580 Distributed PACs and Altivar Drives with

Configuration

DeployPlugin Select the desired plug-in from the drop-down list.

Use encryption Websocket secure: True = Use. False = Do not use.

Ignore certificate errors True = Ignore certificate errors. False = Do not ignore certificate errors.

Clear before deploy True = Clear device. False = Do not clear device.

Export deploy data path Select the ellipsis (...) to choose the path to where you want to export the deploy data.

IP Address Type the IP address of the device to which you want to connect.

PortsDeploy Port Type the port number (int 1...65535) from

which you want to deploy data to the device using the IP address.

Watch Profile Properties for watch plug-inMethod Select the method for communication and

commands.HMI Profile Properties for HMI plug-in

Method Select the method for communication and commands.

Parameter Sub-Parameter Description

38 EIO0000004217 12/2020

Page 39: Modicon M251/M580 Distributed PACs and Altivar Drives with

Configuration

Configuration Runtime configuration settings: Overwrite = Overwrite default settings. Default = Accept default settings.

Debug Debugging settings: Overwrite = Overwrite default settings. Default = Accept default settings.

Resource Resource runtime settings: Overwrite = Overwrite default settings. Default = Accept default settings.

Communication Communication settings: Overwrite = Overwrite default settings. Default = Accept default settings.

Persistence Persistence settings: Overwrite = Overwrite default settings. Default = Accept default settings.

Symlink Symbolic link settings: Overwrite = Overwrite default settings. Default = Accept default settings.

Parameter Sub-Parameter Description

EIO0000004217 12/2020 39

Page 40: Modicon M251/M580 Distributed PACs and Altivar Drives with

Configuration

OPCUA Configuration

OPC UA settings: Enabled = Enable settings. Disabled = Disable settings.

Security Settings Security settings: Enabled = Enable settings. Disabled = Disable settings.

Disable Anonymous Login By default, OPC UA clients can connect to the server anonymously. Select the check box to require that clients

provide a valid user name and password to connect to the OPC UA server.

Deselect the check box to allow clients to log in anonymously.

Security Policy Select the desired policy from the drop-down list to secure the exchanges by signing and encrypting the data you send and receive.

Message Security Select the desired type of message security, according to the Security Policy selected, from the drop-down list.

Server Configuration Enabled = Enable settings. Disabled = Disable settings.

Server Port OPC UA clients append this port number to the TCP URL of the M251/M580 dPAC or Altivar drive that connects to the OPC UA server.

Max Number of Sessions Enter the maximum number of clients that can connect simultaneously to the OPC UA server.

Max Parallel Service Calls Enter the maximum number of calls that request the OPC UA server.

Max Parallel Connections Enter the maximum number of connections to the OPC UA server.

Max Subscription Per Session

Enter the maximum number of subscriptions allowed within each session.

Max Monitored Items Per Subscription

Enter the maximum number of monitored items in each subscription that the server assembles into a notification package.

Min Publishing Interval The publishing interval defines how frequently the OPC UA server sends notification packages to clients. Enter the minimum time that elapses between notifications (in ms).

Min KeepAlive Interval The OPC UA server sends notifications only when the values of monitored items of data are modified. A KeepAlive notification is an empty notification sent by the server to inform the

Parameter Sub-Parameter Description

40 EIO0000004217 12/2020client that, although no data has been modified, the subscription is still active. Enter the minimum interval between KeepAlive notifications (in ms).

Page 41: Modicon M251/M580 Distributed PACs and Altivar Drives with

Configuration

NTP Server Select the ellipsis (...) to open the NTP Server Configuration dialog.Primary NTP Server Select the check box to enable the server. Enter the IP address of the server Select the min polling period(s) from the

drop-down list: 64 32 16 8 4 2 1

Select the max polling period(s) from the drop-down list: 1024 2048 4096 8192 16384 32768 65536 131072

Secondary NTP Server If you selected the check box to enable the

Primary NTP Server, deselect the check box to disable the secondary server. The parameters below are grayed out (disabled).

If you deselected the check box to disable the Primary NTP Server, select the check box to enable the secondary server. Populate the parameters as described for the Primary NTP Server.

Parameter Sub-Parameter Description

EIO0000004217 12/2020 41

Page 42: Modicon M251/M580 Distributed PACs and Altivar Drives with

Configuration

DST (Daylight Savings Time) Select the ellipsis (...) to open the Timezone and Daylight Savings Settings dialog. Select your time zone in the Time zone

drop-down list. Enter the offset value in minutes (from -

1439 to +1439) in the Time zone offset field.

In the Automatically adjust clock for daylight savings field: Enabled = automatically adjust Disabled = manually adjust

In the Start Daylight savings filed, enter the month, day of week, occurrence, and the hour to start.

In the End Daylight savings filed, enter the month, day of week, occurrence, and the hour to stop.

Select Save.

Parameter Sub-Parameter Description

42 EIO0000004217 12/2020

Page 43: Modicon M251/M580 Distributed PACs and Altivar Drives with

Configuration

Configuring the NTP Client

IntroductionYou can configure a M251/M580 dPAC or Altivar drive as an NTP client. The NTP service has these features: A periodic time correction is obtained from the reference-standard time server. There is an automatic switchover to a backup (secondary) time server if an error is detected with

the normal time server system. Controller projects use a function block to read the accurate clock, allowing project events or

variables to be time stamped.

NTP Client ModeWhen the dPAC is configured as an NTP client, the network time service synchronizes the clock in the M251/M580 dPAC or Altivar drive to that of the time server. The synchronized value is used to update the clock in the device. Typical time service configurations utilize redundant servers and diverse network paths to achieve high accuracy and reliability.To establish the accurate Ethernet system network time, the system requires a predefined interval until time is accurate, depending on system configuration. Optimal time accuracy may require several updates from the NTP server.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 M251/M580 dPAC or Altivar drive.

Download application: The status clock value associated with the time service register in the M251/M580 dPAC or

Altivar drive is reinitialized after an application is downloaded or after an NTP server swap. The time is accurate after two polling periods.

NTP Parameters for the M251/M580 dPAC or Altivar DriveRefer to the NTP Server table parameter in the Configuring the Parameters topic.

Model Starting DateM251/M580 dPAC or Altivar drive with EcoStruxure™ Automation Expert January 1st 1980 00:00:00.00

EIO0000004217 12/2020 43

Page 44: Modicon M251/M580 Distributed PACs and Altivar Drives with

Configuration

Integrating Modbus TCP Devices

OverviewIn an M251/M580 dPAC or Altivar drive system, you can perform the following via the service port or device ports of the controller: I/O scanning on Modbus devices Modbus explicit requestsThe types of explicit requests depend on the capabilities of the Modbus device.The M251/M580 dPAC or Altivar drive system reads and writes data from STB/OTB/ATV/Momentum devices via Modbus TCP.

Integrating STB/OTB/ATV/Momentum DevicesThe steps below summarize the process of integrating Modbus TCP devices into an M251/M580 dPAC or Altivar drive system.

NOTE: An M251/M580 dPAC or Altivar drive system does not support Momentum analog I/O devices.

Step Description

1 Configure the devices with the appropriate configuration software.2 Create and manage MODBUS (eaeControl.IO.Modbus.MODBUS).

Result: The settings (AutoStart, Name, and Bus Cycle Time) are defined.3 Create and manage STB/OTB/ATV/Momentum

(eaeControl.IO.Modbus:MODBUSGENTCPS) for the respective devices.Result: The settings (Device Name and IP address) are defined.

4 Create inputs (eaeControl.IO.Modbus:MODBUSRREGx) for the analog/discrete I/O modules.Select the eaeControl.IO.Modbus:MODBUSRREGx when you finish the configuration.

5 Create outputs (eaeControl.IO.Modbus:MODBUSWREGx) for the analog/discrete I/O modules.Select the eaeControl.IO.Modbus:MODBUSWREGX when you finish the configuration.

6 Manage the End Modbus BUS and the End Modbus SLOT.

7 Perform the I/O scanning and Modbus explicit requests on the analog/discrete output modules.

8 Perform the I/O scanning and Modbus explicit requests on the analog/discrete input modules.

44 EIO0000004217 12/2020

Page 45: Modicon M251/M580 Distributed PACs and Altivar Drives with

Configuration

Debug Function

OverviewAn M251/M580 dPAC or Altivar drive system supports online debug of these features: stepping watch trend log view breakpoint creation deletion global enable/disable

watch (at block or pin level) block/trigger events force data read counter events and data values creation deletion

instance tree pad

Accessing the Debug FunctionFollow this process in EcoStruxure Automation Expert:

Refer to the EcoStruxureTM Automation Expert help for detailed instructions on using the debug function.

Step Action

1 Deploy your program.2 Change to debug mode.

3 Select View from the main toolbar menu.

4 Select the drop-down on the Debug pads icon, and select the desired command. You can execute commands for an online program, including: Run to start a stopped process. Stop the current process. Break (pause) the current process. Continue debugging. Step over to execute the next line in the source code. Step in to execute the next line in the source code or jump to the called-up method, if possible. Step out to continue the current process until the jump is made to the current call-up level.

EIO0000004217 12/2020 45

Page 46: Modicon M251/M580 Distributed PACs and Altivar Drives with

Configuration

46 EIO0000004217 12/2020

Page 47: Modicon M251/M580 Distributed PACs and Altivar Drives with

Modicon M251/M580 Distributed PACs and Altivar Drives withDiagnosticsEIO0000004217 12/2020

Modbus Diagnostics

Chapter 4Modbus Diagnostics

Modbus Diagnostic Codes

IntroductionThe M251/M580 dPACs and Altivar drives support the diagnostic codes in these tables.

Function Code 3Some module diagnostics (I/O connection, extended health, etc.) are available to Modbus clients that read the local Modbus server area. Use Modbus function code 3 with the unit ID set to 100 for register mapping:

Function Code 3: Basic Network DiagnosticsBasic network diagnostics start at address 40001(decimal) as described in the following table.

Type Offset Modbus Address

Size (Words)

Basic Networks Diagnostic Data 0 39

Ethernet Port Diagnostics Data (Internal port) 39 103Ethernet Port Diagnostics Data (ETH 1) 142 103

Ethernet Port Diagnostics Data (ETH 2) 245 103

Ethernet Port Diagnostics Data (ETH 3) 348 103Ethernet Port Diagnostics Data (backplane) 451 103

Modbus TCP/Port 502 Diagnostic Data 554 114Modbus TCP/Port 502 Connection Table Data 668 515

Identify 2001 24

Starting Address (Decimal)

Length (Words)

Register Byte Order CommentsMS BYTE LS BYTE

40001 2 MS Byte 00 Byte 01 Basic network diagnostic validity

Byte 02 LS Byte40003 1 MS Byte LS Byte 03 Communication global status

40004 1 MS Byte LS Byte Supported communication services40005 1 MS Byte LS Byte Status of communication services

EIO0000004217 12/2020 47

Page 48: Modicon M251/M580 Distributed PACs and Altivar Drives with

Diagnostics

40006 2 IP 1 IP 2 IP address (IP1.IP2.IP3.IP4)IP 3 IP 4

40008 2 SM 1 SM 2 Subnet mask (SM1.SM2.SM3.SM4)

SM 3 SM 440010 2 GW 1 GW 2 Default gateway (GW1.GW2.GW3.GW4)

GW 3 GW 4

40012 3 MAC 1 MAC 2 MAC address (MAC1:MAC2:MAC3:MAC4:MAC5:MAC6.MAC 3 MAC 4

MAC 5 MAC 640015 3 MS Byte 00 01 Ether frame format capability / configuration /

operational02 03

04 LS Byte 0540018 2 C00 C01 Ethernet receive frames OK

C02 C03

40020 2 C00 C01 Ethernet transmit frames OKC02 C03

40022 1 MS Byte LS Byte Number of open client connections

40023 1 MS Byte LS Byte Number of open server connections40024 2 C00 C01 Number of Modbus detected error messages

sentC02 C0340026 2 C00 C01 Number of Modbus messages sent

C02 C03

40028 2 C00 C01 Number of Modbus messages receivedC02 C03

40030 8 Char 1 Char 2 Device name

Char 3 Char 4Char 5 Char 6

Char 7 Char 8Char 9 Char 10

Char 11 Char 12

Char 13 Char 14Char 15 Char 16

Starting Address (Decimal)

Length (Words)

Register Byte Order Comments

MS BYTE LS BYTE

48 EIO0000004217 12/2020

Page 49: Modicon M251/M580 Distributed PACs and Altivar Drives with

Diagnostics

Example: Reading Basic Network Diagnostics with Modbus Function Code 3Here is an example of how to read registers 40018 and 40019, the Ethernet receive frames OK count registers. The request contains 7 bytes. The starting address, shown as a hex value in byte 2 below, is calculated as follows:40018 – 40001 = 17 dec = (11 hex)The number of registers to be diagnosed (2 hex) is shown in byte 4:

The normal response is returned in 8 bytes. In this example, the expected response is 14229 hex; this value is shown in bytes 2 through 5 of the response:

40038 2 MS Byte 00 Byte 01 IP assignment mode capability / operationalByte 02 LS Byte 03

Byte Number Value0 Function code = 03 (hex)

1 Starting Address Hi = 00 (hex)

2 Starting Address Low = 11 (hex)3 No. of Registers Hi = 00 (hex)

4 No. of Registers Low = 2 (hex)

5 CRC high byte (inserted by the Modbus sending application)6 CRC low byte (inserted by the Modbus sending application)

Byte Number Value0 Function code = 03 (hex)

1 Byte count = 4 (hex)

2 1st register data, high byte = 00 (hex)3 1st register data, low byte = 01 (01 hex)

4 2nd register data, high byte = 42 (hex)

5 2nd register data, low byte = 29 (hex)6 CRC high byte

7 CRC low byte

Byte Number Value

0 Original function code + 80 hex (= 83 hex)1 Detected error code

Starting Address (Decimal)

Length (Words)

Register Byte Order Comments

MS BYTE LS BYTE

EIO0000004217 12/2020 49

Page 50: Modicon M251/M580 Distributed PACs and Altivar Drives with

Diagnostics

For more information on Modbus function code 3 and other function codes, refer to the Modicon Modbus Protocol Reference Guide (PI-MBUS-300).

Function Code 3: Ethernet Internal Port Diagnostic DataInternal port diagnostics start at address 40040 (decimal) as described in the following table.

2 CRC high byte

3 CRC low byte

Byte Number Value

Starting Address (Decimal)

Length (Words)

Register Byte Order Comments

MS BYTE LS BYTE40040 1 MS Byte LS Byte Internal port Diagnostics Data Validity

40041 1 MS Byte LS Byte Internal port Logical/Physical Port Number40042 1 MS Byte LS Byte Internal port Ethernet Control Capability

40043 1 MS Byte LS Byte Internal port Link Speed Capability

40044 1 MS Byte LS Byte Internal port Ethernet Control Configuration40045 1 MS Byte LS Byte Internal port Link Speed Configuration

40046 1 MS Byte LS Byte Internal port Ethernet Control Operational

40047 1 MS Byte LS Byte Internal port Link Speed Operational40048 3 MAC 1 MAC 2 MAC Address

(MAC1:MAC2:MAC3:MAC4:MAC5:MAC6)MAC 3 MAC 4MAC 5 MAC 6

40051 2 MSB C00 C01 Internal port Media Counters Data Validity

C02 LSB C0340053 2 MSB C00 C01 Internal port Num Frames Transmitted OK

C02 LSB C03

40055 2 MSB C00 C01 Internal port Num Frames Received OKC02 LSB C03

40057 2 MSB C00 C01 Internal port Num Ether Collisions

C02 LSB C0340059 2 MSB C00 C01 Internal port Carrier Sense Errors detected

C02 LSB C0340061 2 MSB C00 C01 Internal port Num Ether Excessive Collisions

C02 LSB C03

40063 2 MSB C00 C01 Internal port CRC Errors detectedC02 LSB C03

50 EIO0000004217 12/2020

Page 51: Modicon M251/M580 Distributed PACs and Altivar Drives with

Diagnostics

40065 2 MSB C00 C01 Internal port FCS Errors detectedC02 LSB C03

40067 2 MSB C00 C01 Internal port Alignment Errors detected

C02 LSB C0340069 2 MSB C00 C01 Internal port Num Internal MAC Tx Errors detected

C02 LSB C03

40071 2 MSB C00 C01 Internal port Late CollisionsC02 LSB C03

40073 2 MSB C00 C01 Internal port Num Internal MAC Rx Errors detectedC02 LSB C03

40075 2 MSB C00 C01 Internal port Multiple Collisions

C02 LSB C0340077 2 MSB C00 C01 Internal port Single Collisions

C02 LSB C03

40079 2 MSB C00 C01 Internal port Deferred TransmissionsC02 LSB C03

40081 2 MSB C00 C01 Internal port Frames Too Long

C02 LSB C0340083 2 MSB C00 C01 Internal port Frames Too Short

C02 LSB C0340085 2 MSB C00 C01 Internal port SQE Test Error detected

C02 LSB C03

40087 1 MS Byte LS Byte Internal port Interface Label Length40088 32 IL char64 IL char63 Internal port Interface Label characters

40089 IL char62 IL char61

... ... ...40118 IL char04 IL char03

40119 IL char02 IL char0140120 1 MS Byte LS Byte Internal port Interface Counters Diagnostic Validity

40121 2 MSB C00 C01 Internal port Num Octets Received

C02 LSB C0340123 2 MSB C00 C01 Internal port Num Unicast Packets Received

C02 LSB C03

Starting Address (Decimal)

Length (Words)

Register Byte Order Comments

MS BYTE LS BYTE

EIO0000004217 12/2020 51

Page 52: Modicon M251/M580 Distributed PACs and Altivar Drives with

Diagnostics

40125 2 MSB C00 C01 Internal port Num Non Unicast Packets ReceivedC02 LSB C03

40127 2 MSB C00 C01 Internal port Num Inbound Packets Discarded

C02 LSB C0340129 2 MSB C00 C01 Internal port Num Inbound Packets Error detected

C02 LSB C03

401331 2 MSB C00 C01 Internal port Num Inbound Packets UnknownC02 LSB C03

40133 2 MSB C00 C01 Internal port Num Octets SentC02 LSB C03

40135 2 MSB C00 C01 Internal port Num Unicast Packets Sent

C02 LSB C0340137 2 MSB C00 C01 Internal port Num Non Unicast Packets Sent

C02 LSB C03

40139 2 MSB C00 C01 Internal port Num Outbound Packets DiscardedC02 LSB C03

40141 2 MSB C00 C01 Internal port Num Outbound Packets Error detectedC02 LSB C03

Starting Address (Decimal)

Length (Words)

Register Byte Order Comments

MS BYTE LS BYTE

52 EIO0000004217 12/2020

Page 53: Modicon M251/M580 Distributed PACs and Altivar Drives with

Diagnostics

Function Code 3: Modbus TCP Port 502 Diagnostic DataModbus TCP port 502 diagnostics start at address 40555 (decimal) as described in the following table.

Starting Address

Length Register Byte Order Comments

MS BYTE LS BYTE

40555 2 MS Byte 00 Byte 01 Modbus TCP/Port 502 Diagnostic Data ValidityByte 02 LS Byte 03

40557 1 MS Byte LS Byte Port 502 Status40558 1 MS Byte LS Byte Num Open Connections

40559 2 MSB C00 C01 Num MB Messages Sent

C02 LSB C0340561 2 MSB C00 C01 Num MB Messages Received

C02 LSB C03

40563 1 MS Byte LS Byte Num MB Open Client Connections40564 1 MS Byte LS Byte Num MB Open Server Connections

40565 1 MS Byte LS Byte Max Num Connections

40566 1 MS Byte LS Byte Max Num Client Connections40567 1 MS Byte LS Byte Max Num Server Connections

40568 2 MSB C00 C01 Num MB Detected Error Messages SentC02 LSB C03

40570 1 MS Byte LS Byte Num Open Priority Connections

40571 1 MS Byte LS Byte Max Num Priority Connections40572 1 MS Byte LS Byte Num Entries in Unauthorized Table

40573 2 MSB - IP1 IP2 Remote IP Address 1 Connection 1

IP3 LSB - IP440575 1 MS Byte LS Byte Num Attempts to Open

Unauthorized Connection 140576 2 MSB - IP1 IP2 Remote IP Address 2 Connection 2

IP3 LSB - IP440578 2 MS Byte LS Byte Num Attempts to Open

Unauthorized Connection 2... ... ... ... ...

40663 2 MSB - IP1 IP2 Remote IP Address 31 Connection 31

IP3 LSB - IP440665 1 MS Byte LS Byte Num Attempts to Open

Unauthorized Connection 31

EIO0000004217 12/2020 53

Page 54: Modicon M251/M580 Distributed PACs and Altivar Drives with

Diagnostics

Function Code 3: Modbus TCP Port 502 Connection Table DataModbus TCP port 502 connection table data starts at address 40669 (decimal) as described in the following table.

40666 2 MSB - IP1 IP2 Remote IP Address 32 Connection 32IP3 LSB - IP4

40668 1 MS Byte LS Byte Num Attempts to Open Unauthorized Connection 32

Starting Address

Length Register Byte Order Comments

MS BYTE LS BYTE

Starting Address

Length Register Byte Order Comments

MS BYTE LS BYTE

40669 1 MS Byte LS Byte Connection Table Validity40670 1 MS Byte LS Byte Number of Entries

40671 1 MS Byte LS Byte Starting Entry Index

40672 1 MS Byte LS Byte Connection 1 Index Connection 140673 2 IP1 IP2 Connection 1 Remote IP Address

IP3 IP4

40675 1 MS Byte LS Byte Connection 1 Remote Port Number40676 1 MS Byte LS Byte Connection 1 Local Port Number

40677 1 MS Byte LS Byte Num MB Messages Sent on Connection 1

40678 1 MS Byte LS Byte Num MB Messages Received on Connection 1

40679 1 MS Byte LS Byte Num MB Detected Error Messages Sent on Connection 1

40680 1 MS Byte LS Byte Connection 2 Index Connection 240681 2 IP1 IP2 Connection 2 Remote IP Address

IP3 IP4

40683 1 MS Byte LS Byte Connection 2 Remote Port Number40684 1 MS Byte LS Byte Connection 2 Local Port Number

40685 1 MS Byte LS Byte Num MB Messages Sent on Connection 2

40686 1 MS Byte LS Byte Num MB Messages Received on Connection 2

40687 1 MS Byte LS Byte Num MB Detected Error Messages Sent on Connection 2

54 EIO0000004217 12/2020

Page 55: Modicon M251/M580 Distributed PACs and Altivar Drives with

Diagnostics

Function Code 8Modbus function code 08 provides a variety of diagnostic functions:

... ... ... ... ...41168 1 MS Byte LS Byte Connection 63 Index Connection 63

41169 2 IP1 IP2 Connection 63 Remote IP Address

IP3 IP441171 1 MS Byte LS Byte Connection 63 Remote Port

Number41172 1 MS Byte LS Byte Connection 63 Local Port Number

41173 1 MS Byte LS Byte Num MB Messages Sent on Connection 63

41174 1 MS Byte LS Byte Num MB Messages Received on Connection 63

41175 1 MS Byte LS Byte Num MB Detected Error Messages Sent on Connection 63

41176 1 MS Byte LS Byte Connection 64 Index Connection 6441177 2 IP1 IP2 Connection 64 Remote IP Address

IP3 IP4

415179 1 MS Byte LS Byte Connection 64 Remote Port Number

41180 1 MS Byte LS Byte Connection 64 Local Port Number

41181 1 MS Byte LS Byte Num MB Messages Sent on Connection 64

41182 1 MS Byte LS Byte Num MB Messages Received on Connection 64

41183 1 MS Byte LS Byte Num MB Detected Error Messages Sent on Connection 64

Starting Address

Length Register Byte Order Comments

MS BYTE LS BYTE

Operation Code

Diagnostic Control

Description

0x01 0x0100 network diagnostic data

0x0200 Read the Ethernet port diagnostic data from the switch manager.0x0300 Read the Modbus TCP/port 502 diagnostic data from the Modbus server.

0x0400 Read the Modbus TCP/port 502 connection table from the Modbus server.

0x07F0 Read the data structure offset data from the Modbus server.

EIO0000004217 12/2020 55

Page 56: Modicon M251/M580 Distributed PACs and Altivar Drives with

Diagnostics

Function Code 43A Modbus request associated with function code 43 (Read Device Identification) asks a Modbus server to return the vendor name, product name, version number, and other optional fields:

0x02 0x0100 Clear the basic network diagnostic data. NOTE: Only specific parameters of basic network diagnostic data are used to clear requests.

0x0200 Clear the Ethernet port diagnostic data. NOTE: Only specific parameters of basic network diagnostic data are used to clear requests.

0x0300 Clear the Modbus TCP/port 502 diagnostic data. NOTE: Only specific parameters of Modbus port 502 diagnostic data are used to clear requests.

0x0400 Clear the Modbus TCP/port 502 connection table. NOTE: Only specific parameters of Modbus port 502 connection data are use to clear requests.

0x03 0 Clear all diagnostic data. NOTE: Only specific parameters of each diagnostic data are used to clear requests.

Operation Code

Diagnostic Control

Description

Category Object ID Object Name Type Requirement

Basic 0x00 VendorName (vendor name) ASCII string mandatory0x01 ProductCode (product code) ASCII string mandatory

0x02 MajorMinorRevision (version number) ASCII string mandatoryRegular 0x03 VendorUrl (vendor URL) ASCII string optional

0x04 ProductName (product name) ASCII string optional

0x05 ModelName (model name) ASCII string optional0x06 UserApplicationName (user application

name)ASCII string optional

0x07...0x7F (reserved) ASCII string optional

Extended 0x80...0xFF device-dependent optional

56 EIO0000004217 12/2020

Page 57: Modicon M251/M580 Distributed PACs and Altivar Drives with

Modicon M251/M580 Distributed PACs and Altivar Drives withIndexEIO0000004217 12/2020

Index

Aauthentication

configuration, 37

Bblock/trigger events

debug, 45boot power

operating state, 22breakpoint

creation debug, 45deletion debug, 45global enable/disable debug, 45

Ccold

start, 22configuration, 37CPU

Modbus diagnostics, 47creating a solution, 34

Ddata values, read

debug, 45daylight savings time

configuration, 37

EIO0000004217 12/2020

debugblock/trigger events, 45breakpoint, 45force data, 45IEC 61499, 45instance tree pad, 45log view, 45read event counters and data values, 45step, 45watch, 45watch trend, 45

deploymentconfiguration, 37

diagnosticsconfiguration, 37Modbus, 47Modbus codes, 47

downloading a solution, 34

Eerror management, detected

operating state, 22event counters, read

debug, 45

Ffallback, 22firmware

updating, 20force data

debug, 45function codes, 47

Hhalt

operating state, 22HMI profile

diagnostics, 37

57

Page 58: Modicon M251/M580 Distributed PACs and Altivar Drives with

Index

II/O scanning, 44IEC 61499

debug, 45instance tree pad

debug, 45IP address

configuration, 37isolation, 31

Llife cycle, 30log view

debug, 45

MModbus diagnostics

CPU, 47Modbus TCP

integrating devices, 44Modicon OTB

integrating, 44Modicon STB

integrating, 44

Nnetwork topology

planning, 31star, 32

NTP, 43configuration, 37, 37

Ooperating states

boot power, 22cold start, 22detected error management, 22fallback, 22halt, 22start/stop, 22

58

OTBintegrating, 44

Pports

service, 20power, boot

operating state, 22

Rread event counters and data values

debug, 45

Ssecurity

configuration, 37service port

updating firmware, 20solution

creating, downloading, 34star topology, 32start

cold, 22start/stop, 22STB

integrating, 44step

debug, 45

Ttopology

star, 32trigger/block events

debug, 45

Uupdating firmware, 20USB

updating firmware, 20

EIO0000004217 12/2020

Page 59: Modicon M251/M580 Distributed PACs and Altivar Drives with

Index

Wwatch

debug, 45watch profile

diagnostics, 37watch trend

debug, 45

EIO0000004217 12/2020

59