Schneider Electric EcoStruxure™ Control Engineering - Monitoring User Guide

Below you will find brief information for EcoStruxure Control Engineering Monitoring. It is a diagnostics solution offering live views of controller applications, aiding in downtime reduction by assisting operators and maintenance teams with issue diagnoses. The system provides representations of application structure via data flow and cross-references. These representations display values of running controller application variables showing inputs that determine output values, or outputs depending on a selected input.

PDF

Document

EcoStruxure

™

Control Engineering

Monitoring

User Guide

Original instructions

EIO0000004427.02

11/2022 www.se.com

Legal Information

The Schneider Electric brand and any trademarks of Schneider Electric SE and its subsidiaries referred to in this guide are the property of Schneider Electric SE or its subsidiaries. All other brands may be trademarks of their respective owners.

This guide and its content are protected under applicable copyright laws and furnished for informational use only. No part of this guide may be reproduced or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), for any purpose, without the prior written permission of

Schneider Electric.

Schneider Electric does not grant any right or license for commercial use of the guide or its content, except for a non-exclusive and personal license to consult it on an "as is" basis. Schneider Electric products and equipment should be installed, operated, serviced, and maintained only by qualified personnel.

As standards, specifications, and designs change from time to time, information contained in this guide may be subject to change without notice.

To the extent permitted by applicable law, no responsibility or liability is assumed by

Schneider Electric and its subsidiaries for any errors or omissions in the informational content of this material or consequences arising out of or resulting from the use of the information contained herein.

As part of a group of responsible, inclusive companies, we are updating our communications that contain non-inclusive terminology. Until we complete this process, however, our content may still contain standardized industry terms that may be deemed inappropriate by our customers.

Safety Information

.......................................................................................5

Before You Begin........................................................................................5

Start-up and Test ........................................................................................6

Operation and Adjustments .........................................................................7

About the Book

............................................................................................8

Introduction to EcoStruxure Control Engineering -

EIO0000004427.02

Safety Information

Important Information

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.

The addition of this symbol to a “Danger” or “Warning” safety label indicates that an electrical hazard exists which will result in personal injury if the instructions are not followed.

This is the safety alert symbol. It is used to alert you to potential personal injury hazards. Obey all safety messages that follow this symbol to avoid possible injury or death.

DANGER

DANGER indicates a hazardous situation which, if not avoided, will result in death or serious injury.

WARNING

WARNING indicates a hazardous situation which, if not avoided, could result in death or serious injury.

CAUTION

CAUTION indicates a hazardous situation which, if not avoided, could result in minor or moderate injury.

NOTICE

NOTICE is used to address practices not related to physical injury.

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.

Before You Begin

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

EIO0000004427.02

Safety Information

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-ofoperation protection must be coordinated with the related automation equipment and software programming.

NOTE: Coordination of safeties and mechanical/electrical interlocks for pointof-operation protection is outside the scope of the Function Block Library,

System User Guide, or other implementation referenced in this documentation.

Start-up and Test

Before 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 are made and that enough time is allowed to perform complete and satisfactory testing.

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.

EIO0000004427.02

Safety Information

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.

Operation and Adjustments

The following precautions are from the NEMA Standards Publication ICS 7.1-

1995:

(In case of divergence or contradiction between any translation and the English original, the original text in the English language will prevail.)

• 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 required by the operator should be accessible to the operator. Access to other controls should be restricted to prevent unauthorized changes in operating characteristics.

EIO0000004427.02

About the Book

Document Scope

The present user guide describes the functionality provided by EcoStruxure

Control Engineering - Monitoring.

Validity Note

This document has been updated for the release of EcoStruxure Control

Engineering V22.2.

The characteristics that are described in the present document, as well as those described in the documents included in the Related Documents section below, can be found online. To access the information online, go to the Schneider Electric home page www.se.com/ww/en/download/ .

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.

Product Related Information

WARNING

UNINTENDED EQUIPMENT OPERATION

• Perform a risk assessment as per ISO 12100 and/or other equivalent assessment in view of your use of EcoStruxure Control Engineering.

• In your risk assessment, consider all applicable regulations and standards that apply to your development process and to your machine/process.

• Verify that your use of EcoStruxure Control Engineering is fully covered in the definition of your software development process and that your software development process meets all applicable regulations and standards.

• After modifications of any type whatsoever to the source code of your application resulting from your use of EcoStruxure Control Engineering, commission or recommission the machine/process in compliance with all regulations, standards, and process definitions applicable to your machine/ process.

• During commissioning or recommissioning of the machine/process, verify the correct operation and effectiveness of all safety-related functions and non-safety-related functions by performing comprehensive tests for all operating states, for the defined safe state of your machine/process, and for all potential error situations.

Failure to follow these instructions can result in death, serious injury, or equipment damage.

EcoStruxure Control Engineering - Monitoring generates a representation of the source code of your controller application and uses the representation as a basis for providing information on your controller application. You must, therefore, ensure that the source code used for your application on the controller is the same as the source code used for EcoStruxure Control Engineering. You can do so by, for example, implementing automated version control routines, or by setting up appropriate organizational measures to meet the corresponding requirements.

WARNING

INCORRECT OR INCOMPLETE SOURCE CODE ANALYSIS

• In your risk assessment, consider all potential effects of inappropriate, incorrect, or incomplete input files used with EcoStruxure Control

Engineering.

• Verify that the source code exported from your software development environment and to be used by EcoStruxure Control Engineering is the identical to the source code used for the application running on your controller.

• Do not rely on the data provided by EcoStruxure Control Engineering -

Monitoring as the sole source of information in monitoring, verifying, validating or otherwise assessing the operation of your machine/process.

Failure to follow these instructions can result in death, serious injury, or equipment damage.

Machines, controllers, and related equipment are usually integrated into networks.

Unauthorized persons and malware may gain access to the machine as well as to other devices on the network/fieldbus of the machine and connected networks because of insufficiently secure access to software and networks.

EIO0000004427.02

About the Book

Schneider Electric adheres to industry best practices in the development and implementation of control systems. This includes a "Defense-in-Depth" approach to secure an Industrial Control System. This approach places the controllers behind one or more firewalls to restrict access to authorized personnel and protocols only.

WARNING

UNAUTHENTICATED ACCESS AND SUBSEQUENT UNAUTHORIZED

MACHINE OPERATION

• Evaluate whether your environment or your machines are connected to your critical infrastructure and, if so, take appropriate steps in terms of prevention, based on Defense-in-Depth, before connecting the automation system to any network.

• Limit the number of devices connected to a network to the minimum necessary.

• Isolate your industrial network from other networks inside your company.

• Protect any network against unintended access by using firewalls, VPN, or other, proven security measures.

• Monitor activities within your systems.

• Prevent subject devices from direct access or direct link by unauthorized parties or unauthenticated actions.

• Prepare a recovery plan including backup of your system and process information.

Failure to follow these instructions can result in death, serious injury, or equipment damage.

For more information on organizational measures and rules covering access to infrastructures, refer to ISO/IEC 27000 series, Common Criteria for Information

Technology Security Evaluation, ISO/IEC 15408, IEC 62351, ISA/IEC 62443,

NIST Cybersecurity Framework, Information Security Forum - Standard of Good

Practice for Information Security, and refer to Cybersecurity Guidelines for

EcoStruxure Machine Expert, Modicon and PacDrive Controllers and Associated

Equipment.

For reasons of Internet security, for those devices that have a native Ethernet connection, TCP/IP forwarding is disabled by default. Therefore, you must manually enable TCP/IP forwarding. However, doing so may expose your network to possible cyberattacks if you do not take additional measures to protect your enterprise. In addition, you may be subject to laws and regulations concerning cybersecurity.

WARNING

UNAUTHENTICATED ACCESS AND SUBSEQUENT NETWORK INTRUSION

• Observe and respect any and all pertinent national, regional and local cybersecurity and/or personal data laws and regulations when enabling

TCP/IP forwarding on an industrial network.

• Isolate your industrial network from other networks inside your company.

• Protect any network against unintended access by using firewalls, VPN, or other, proven security measures.

Failure to follow these instructions can result in death, serious injury, or equipment damage.

Consult the Schneider Electric Cybersecurity Best Practices for additional information.

EIO0000004427.02

About the Book

Terminology Derived from Standards

The technical terms, terminology, symbols and the corresponding descriptions in this manual, or that appear in or on the products themselves, are generally derived from the terms or definitions of international standards.

In the area of functional safety systems, drives and general automation, this may include, but is not limited to, terms such as safety , safety function , safe state , fault , fault reset , malfunction , failure , error , error message , dangerous , etc.

Among others, these standards include:

Standard

IEC 61131-2:2007

ISO 13849-1:2015

EN 61496-1:2013

ISO 12100:2010

EN 60204-1:2006

ISO 14119:2013

ISO 13850:2015

IEC 62061:2015

IEC 61508-1:2010

IEC 61508-2:2010

IEC 61508-3:2010

IEC 61784-3:2016

2006/42/EC

2014/30/EU

2014/35/EU

Description

Programmable controllers, part 2: Equipment requirements and tests.

Safety of machinery: Safety related parts of control systems.

General principles for design.

Safety of machinery: Electro-sensitive protective equipment.

Part 1: General requirements and tests.

Safety of machinery - General principles for design - Risk assessment and risk reduction

Safety of machinery - Electrical equipment of machines - Part 1: General requirements

Safety of machinery - Interlocking devices associated with guards -

Principles for design and selection

Safety of machinery - Emergency stop - Principles for design

Safety of machinery - Functional safety of safety-related electrical, electronic, and electronic programmable control systems

Functional safety of electrical/electronic/programmable electronic safetyrelated systems: General requirements.

Functional safety of electrical/electronic/programmable electronic safetyrelated systems: Requirements for electrical/electronic/programmable electronic safety-related systems.

Functional safety of electrical/electronic/programmable electronic safetyrelated systems: Software requirements.

Industrial communication networks - Profiles - Part 3: Functional safety fieldbuses - General rules and profile definitions.

Machinery Directive

Electromagnetic Compatibility Directive

Low Voltage Directive

In addition, terms used in the present document may tangentially be used as they are derived from other standards such as:

Standard

IEC 60034 series

IEC 61800 series

IEC 61158 series

Description

Rotating electrical machines

Adjustable speed electrical power drive systems

Digital data communications for measurement and control – Fieldbus for use in industrial control systems

Finally, the term zone of operation may be used in conjunction with the description of specific hazards, and is defined as it is for a hazard zone or danger zone in the

Machinery Directive ( 2006/42/EC ) and ISO 12100:2010 .

NOTE: The aforementioned standards may or may not apply to the specific products cited in the present documentation. For more information concerning the individual standards applicable to the products described herein, see the characteristics tables for those product references.

EIO0000004427.02

Introduction to EcoStruxure Control Engineering - Monitoring

Introduction to EcoStruxure Control Engineering -

Monitoring

Overview

EcoStruxure Control Engineering - Monitoring is a diagnostics solution that provides live views of your running controller application to help reduce the downtime of controller-based systems by supporting operators and maintenance teams in diagnosing an issue.

It provides a representation of the structure of your controller application in the form of a data flow dependence tree with the corresponding cross references (in

Ladder or Structured Text) that show the different equations relating to a selected variable. Based on these dependence tree and cross reference representations,

EcoStruxure Control Engineering - Monitoring displays the values of the variables of the running controller application. Views are available that show only those inputs that are instrumental in determining the values of a selected output, or only the outputs whose values depend on a selected input.

EcoStruxure Control Engineering - Monitoring is installed on a dedicated server in your industrial production network. It is a Software as a Service (SaaS) tool accessible using a web browser. This allows, for example, for access from distributed locations, enabling on-site maintenance staff to be supported by engineers who are not on site.

Use Cases

EcoStruxure Control Engineering - Monitoring meets the requirements of different profiles in various use cases:

• Operators:

◦ Assistance in determining potential causes for machine downtime

◦ Support in securing the system before a restart

• Maintenance teams:

◦ Diagnostics of hardware issues

◦ Diagnostics of software issues

◦ Identification of missing criteria

• Automation experts/developers:

◦ Familiarization with complex systems

◦ Reduction of the time required to develop the monitoring system by removing the need to create diagnostic synoptics (EcoStruxure Control

Engineering - Monitoring can substitute corresponding panels).

◦ Reduction of the time required for code instrumentation since EcoStruxure

Control Engineering - Monitoring does not require any.

For each of these profiles, EcoStruxure Control Engineering - Monitoring is also useful for training people.

12 EIO0000004427.02

Registration, Licenses and Sessions

Registration

Overview

EcoStruxure Control Engineering - Monitoring is accessible using a dedicated server for your organization.

The URL of the dedicated server is available from your system administrator.

Browser Compatibility

The following web browsers are supported:

• Mozilla Firefox from version 11

• Google Chrome from version 16

• Microsoft Edge from version 12

• Microsoft Internet Explorer from version 10

• Apple Safari from version 7

Registration

Registration procedure:

Step

Action

In your browser, go to the URL of the dedicated server.

Click Sign up .

Fill in the form with your first and last names, your phone number, your e-mail address

(which is used as your identifier) and select a password. Password requirements:

• At least one uppercase character

• At least one lowercase character

• At least one numerical character

• At least one special character (such as ”{”, ”/”, “$” )

• Password length between 8 and 32 characters

Read the Terms and Conditions and, if you agree, select I agree to the Terms and

Conditions .

Click Sign Up .

Result: Your account is created and activated.

Contact your system administrator for further details on the registration procedure.

EIO0000004427.02

Registration, Licenses and Sessions

Licenses

Overview

Schneider Electric offers various license plans for EcoStruxure Control

Engineering tools.

Paid License Plans

Contact your local Schneider Electric representative for details on the available license plans for EcoStruxure Control Engineering tools. A selection of licenses is also directly available from Schneider Electric Exchange at https://exchange.se.

com/shop .

14 EIO0000004427.02

Registration, Licenses and Sessions

Sessions

Automatic Log-Out (Session Time-Out)

After 10 minutes of inactivity in an EcoStruxure Control Engineering session, you are automatically logged out. If you work with multiple browser tabs, the most recent activity in any of the tabs applies. For example, if you work in tab 1, but not in tab 2, tab 2 does not disconnect you because there is activity in tab 1.

Multiple Sessions

If your credentials are used in multiple sessions, you receive a notification. For example, if you are logged in and another session is established with the same credentials, you receive the following message:

EIO0000004427.02

The information on the connection date and time, the IP address, the operating system and browser help you to determine whether or not a sessions is legitimate.

You can select and close a session with Close Session(s) .

Creating Projects and Programs

Introduction to Projects and Programs

Overview

EcoStruxure Control Engineering provides projects and programs for you to organize your work.

A project is a type of container that can hold programs. A project is not specific to an EcoStruxure Control Engineering tool.

When you register with EcoStruxure Control Engineering, the platform provides one default project for you.

A program is assigned to a project. A program is created in conjunction with one of the tools provided by EcoStruxure Control Engineering. A program typically comprises metadata you entered during its creation, the uploaded source code of a controller application, and the results generated with the EcoStruxure Control

Engineering tools.

The EcoStruxure Control Engineering tools are launched from within a program.

Whether or not a specific EcoStruxure Control Engineering tool is available for a program depends on the source controller/development environment you select during the creation of the program ( PLC Brand or PLC source brand ).

Programs can be shared with other users.

Example

Assume you have been assigned the task of improving a machine ABC with two controllers X and Y. In a first step, you want to better understand the code of the two controller applications. You create a project “Machine ABC”. Then you add two programs to this project: “Controller X” and “Controller Y”.

In both of these programs, you run EcoStruxure Control Engineering -

Documentation to visualize the data flow and the control flow.

In a subsequent step, your task is extended to managing the creation of a new version of the controller applications. You start by running EcoStruxure Control

Engineering - Verification in your programs to verify the existing code. You share the two programs with the developers so they can access the results of the code verification for assistance in updating the code.

In subsequent steps, you can upload intermediate versions of the updated code into your program and re-run EcoStruxure Control Engineering - Documentation and EcoStruxure Control Engineering - Verification to document the progress and verify that your coding rules have been properly implemented.

16 EIO0000004427.02

Creating Projects and Programs

Creating Projects

Procedure for creating a project:

Step

Action

Select PROJECTS in the top menu to display the Projects page.

Select Actions > New project .

Provide a unique name for your project. Lowercase and uppercase are ignored which means that, for example, the name of a project to be created cannot be “Controller xyz” if you already have a project with the name “Controller XYZ”. Click Add to create it.

Click Add to create the project.

Result: The project is added to your list of projects on the Open projects tab.

Clicking a project in the list displays two tabs. The Overview tab provides general information on the project. The Programs tab contains the list of programs assigned to this project.

Creating Programs

There are three ways to start the creation of a program:

• From outside of a project select TOOLS on the main menu

• From the dashboard click New ...

• From inside a project on its Programs tab select Actions > New program

EIO0000004427.02

Creating Projects and Programs

Creating a program from outside of a project:

Step

Action

From the main menu, select TOOLS .

Select the tool you want to use for the program.

Result: EcoStruxure Control Engineering starts the program creation wizard.

Creating a program from the dashboard:

Step

Action

From the main menu, select DASHBOARD .

Click the New ...

button for the tool you want to use for the program.

Result: EcoStruxure Control Engineering starts the program creation wizard.

Creating a program from inside a project:

Step

Action

From the main menu, select PROJECTS .

Select the required project from the list.

Display the Programs tab of the project.

Select Actions > New program .

Result: EcoStruxure Control Engineering prompts you for the tool to be used for the program and starts the program creation wizard.

EIO0000004427.02

Creating Projects and Programs

Program Creation Wizard

Overview

A wizard can be used to guide you through the different steps required to create your program and launch the execution of the selected EcoStruxure Control

Engineering tool.

The project to which the new program is assigned depends on how the wizard is started. If the wizard is started from outside of a project or from the dashboard, the program is assigned to your default project. If the wizard started from inside a project, the program is assigned to this project. In both cases, the project assignment can be adjusted in step 1 of the wizard.

Refer to

Creating Programs, page 17

for details.

Step 1 - Start

The first step consists of providing setup information on the program.

Provide the following information:

• The fields Application name and Customer name are mandatory. The

“Application name” is used to identify the program in the different views of

EcoStruxure Control Engineering.

• Add additional information in the other fields so that you can identify this program in your project.

Continue with the next step by clicking Validate And Next Step .

Step 2 - Parameters

The second step consists of selecting the development environment that was used to develop the controller application.

EIO0000004427.02

Select the PLC brand and continue with the next step by clicking Validate And

Next Step .

Creating Projects and Programs

Step 3 - License

The third step consists of selecting the EcoStruxure Control Engineering license to be used with your new program.

Select the license to be used with this program from the dropdown listbox

Available license(s) and click Validate And Next Step to continue.

If no license is available, you can still continue creating the program by clicking

Validate And Next Step . In such a case, a license can be added to the program after you have created the program. Without a valid license, the EcoStruxure

Control Engineering tool selected for this program cannot be executed.

If you have a license, but the license has not yet been assigned to your user account, you can still use it by entering its identifier in the License #id field and clicking Validate And Next Step .

Step 4 - Source file

The fourth step consists of uploading the file with the source code of the controller application that you have exported from the development environment (refer to

Manufacturer-Specific File Export Procedures, page 43

for details). This source code is the input material for EcoStruxure Control Engineering. Depending on the

EcoStruxure Control Engineering tool used for the program, you may be prompted to upload additional files.

Drag and drop the files to the location indicated or click Select Files… to import the files. Then click Validate And Next Step to continue.

If the input files are not yet available when you create the program, you can skip the upload with Validate And Next Step and provide the files at a later point in time. Without the uploaded input files, the EcoStruxure Control Engineering tool selected for this program cannot be executed.

EIO0000004427.02

Creating Projects and Programs

Step 5 - Summary

The fifth step displays a summary of the information you have provided in creating your program.

Review the information. If you want to make modifications, click Previous Step to return to the step you want to modify.

If the information is correct, click Create to create the program or click Launch to create the program and to start the EcoStruxure Control Engineering tool selected for this program (this is possible if you have selected a valid license and if you have uploaded the required files).

EIO0000004427.02

Creating Projects and Programs

Accessing a Shared Program

If a program is shared with you, or if access to the program is not restricted (refer to

Sharing a Program, page 23

), you can add it to your list of programs by providing its unique 6-digit key. The unique 6-digit key can be found in the program overview under Application key .

Procedure for adding a program to your list of programs using its unique 6-digit key:

Step

Action

From the menu, select PROJECTS to access the Projects page.

2 Click Shared applications to display the corresponding tab.

3 Enter the unique 6-digit key of the program in the field below User personal accesses or in the field below One time access , depending on whether you want to add this program to your personal records for access at a later point in time, or whether you want to access it only once without adding it to your list of programs.

4 Click Add To My Applications or One Time Access .

22 EIO0000004427.02

Creating Projects and Programs

Sharing Programs with Other Users

Overview

You can share your programs with other users so that a team can work on the same project. As the owner, you can share your program. Selected users with whom you share your program cannot delegate their access rights, that is, they cannot share this shared program with further users.

There are two ways of sharing a program:

• Share with selected users: You choose who can access your program. By default, other users cannot share this program because you are the owner.

• Share with everyone: Everyone can access your program.

Sharing with a Specific User

Procedure for sharing a program with selected users:

Step

Action

Navigate to the Program page.

Select Admin management .

> Collaboration > Users access rights to display the User

Below Invited collaborators , select Actions > Add .

4 Enter the name and the e-mail address of the user to be invited. You can enter the email address the user specified for registration with EcoStruxure Control Engineering, or you can use any other e-mail address. You can also send an invitation notification to the user. On a dedicated server, the invitation notification function requires a mail server.

Users added to the list of invited users can perform the same actions as you, except for sharing the program and modifying its settings. If you do not want invited users to perform any further actions, deactivate the program with the Active application checkbox in Admin

Settings . This sets your program to read-only.

NOTE: If your program uses the EcoStruxure Control Engineering -

Verification tool, invited users may not be able to update the rules file and may not be able to work with the Justifications function. Refer to the EcoStruxure

Control Engineering - Verification user guide for details.

You can revoke sharing by selecting the user(s) you want to remove from your program and selecting Actions > Remove access .

Sharing with Everyone

Procedure for sharing a program with everyone:

EIO0000004427.02

Creating Projects and Programs

Step

Action

Navigate to the Program page.

Select Admin > Settings .

Enable the checkbox Private application .

Users accessing your program can perform the same actions as you, except for sharing the program and modifying its settings. If you do not want invited users to perform any further actions, deactivate the program with the Active application checkbox in Admin

> Settings . This sets your program to read-only.

NOTE: If your program uses the EcoStruxure Control Engineering -

Verification tool, invited users may not be able to update the rules file and may not be able to work with the Justifications function.

You can disable sharing with everybody by deactivating the checkbox Private application . With this setting, only users explicitly invited can access your program.

24 EIO0000004427.02

Monitoring an Controller Application

Pre-Deployment Considerations

Overview

EcoStruxure Control Engineering - Monitoring complements the controller commands for diagnostics.

EcoStruxure Control Engineering - Monitoring does not affect the commands of the controller application for your production process, but provides information on the status of such commands to support you in, for example, resolving issues that may cause machine downtime.

Pre-Requisites Regarding the Controller Application

The quality of the analysis of the source code of controller applications largely depends on the quality of such code. Using consistent coding rules and standards enables a better comprehension of what the source code does or is intended to do. Analyzing tools that respect a set of coding rules facilitates and improves the quality of diagnostics. For example, if the names of variables are explicit and have a clear comment, it is much easier to understand the role of the variables.

The architecture of a controller application also plays an important role in the analysis of the code. A controller application containing many pointers is more difficult to diagnose than a controller application without pointers.

If you are unsure about the quality or suitability of your controller application for use with EcoStruxure Control Engineering - Monitoring, verify the source code with EcoStruxure Control Engineering - Verification to identify optimization potential before using EcoStruxure Control Engineering - Monitoring.

EIO0000004427.02

Monitoring an Controller Application

Architecture

Overview

The following descriptions provide a generic overview of the architecture of an

EcoStruxure Control Engineering - Monitoring solution. The actual architecture and configuration depend on your specific hardware and software environment and the corresponding requirements.

Web Platform

The web platform manages the analysis of the controller application in order to generate the data flow information. It is also from the web platform that

EcoStruxure Control Engineering - Monitoring can be launched and the results can be visualized.

The web platform is available using a client workstation with a web browser.

Communication Server (COM Server)

The communication server is a Web Socket server allowing for communication of process data (that is, direct communication with the controller systems or with an

OPC server). This component can be installed on a virtual machine (VM) or on a separate server. The data is obtained from the controller system either with the

Modbus TCP protocol or with the OPC-DA protocol (using an OPC server). The possible configurations for the installation of these components are described below.

Your IT department needs to open certain ports and provide the appropriate permissions in your network to allow for communication with the controller systems or the OPC server.

Communication using OPC Server

The communication server is installed on the same virtual machine as the web platform and uses an OPC-DA connection to communicate with the OPC server.

26 EIO0000004427.02

Monitoring an Controller Application

In order to provide you with valid data, the communication server requires a valid configuration of the OPC-DA server, especially if the requests use names of variables instead of addresses.

Communication using OPC Server and Communication Server

To account for certain configuration constraints, the communication server can be installed on the same computer as the OPC server you use.

Direct Communication using Modbus TCP

The communication server uses the Modbus TCP protocol for direct communication with the controller system.

EIO0000004427.02

Monitoring an Controller Application

Installation and Configuration

Package

EcoStruxure Control Engineering - Monitoring is provided in a virtual machine

(VM) that contains the environment required for its operation. It includes the communication server in charge of the communication between EcoStruxure

Control Engineering - Monitoring and your controller application (if you enable

OPC communication from the virtual machine). The communication server can also be installed on your server (physical machine) that hosts the OPC server

(according to your cybersecurity policies).

Installation of the Virtual Machine

EcoStruxure Control Engineering - Monitoring is delivered in the form of a virtual machine that virtualizes a Linux Debian operating system.

This virtual machine can be delivered on different architectures and hypervisors:

• VMware that can be used on its OS ESX server, or on Windows

• Hyper-V (Microsoft)

• Oracle VM VirtualBox (Oracle)

Contact your Schneider Electric representative for other hypervisors and architectures.

Installation of the Communication Server

The communication server component is installed like a Windows service. The installation procedure is explained below for Microsoft Windows. The following operating systems are supported:

• Microsoft Windows 10

• Debian Linux 9 and 10

Configuration

The configuration is adapted in the file config.properties

which is located in the root of the folder containing the service wrapper:

Property dataProviderType dataProviderADDR dataProviderPort

Example

1 (for Modbus TCP)

127.0.0.1 when it is installed on the same computer as the communication server.

103 for OPC Server and 502 for Modbus TCP

Description

Defines the protocol to be used for the installation. OPC DA and Modbus TCP are supported.

Primarily used for OPC DA communication. This is the IP address of the computer on which the OPC server is installed.

The port used by the OPC

Server or by Modbus TCP.

EIO0000004427.02

Monitoring an Controller Application

Property dataProviderUser dataProviderPassword dataProviderDomain dataProviderProgId dataProviderClsId updateRate

Example

WORKGROUP

5000 ms (default value)

Description

Only for OPC DA. This is the name of the system user who has access to the computer on which the OPC server is installed.

Only for OPC DA. This is the password of the system user who has access to the computer on which the OPC server is installed.

Only for OPC DA. This is the domain name of the computer on which the OPC server is installed.

Only for OPC DA. This is the program ID of the OPC server.

Only for OPC DA. This is the

CLS ID of the OPC server.

The time interval to refresh the values of variable. With OPC

DA communication, the communication server refreshes the values of the variables every five seconds.

NOTE: Verify that your infrastructure supports the value specified.

NOTE: Restart the server service after each modification to the configuration

(for example, using the Windows services management console).

Installation of the EcoStruxure Control Engineering - Monitoring

Service of the Communication Server

The service wrapper can be installed by executing the script for the corresponding

Windows version:

• Windows 32 bit: windows-x86-32\installService.bat

• Windows 64 bit: windows-64/installService.bat

After the installation procedure, a command prompt with the installation status message is displayed (successful or not successful). The service is enabled following a successful installation.

EIO0000004427.02

It is possible to verify the status of the service by executing the file windows-x86-

32\ICSMonitoring.exe

. A window is displayed that allows you to stop or launch the service and to view the logs and service properties. It is advisable to keep automatic startup.

Monitoring an Controller Application

NOTE: The storage location of the installation package is used as the installation location, that is, the program is not installed in the Windows

\Program Files tree, but in the directory in which the installation package is contained.

Integration With a Supervision System

Supervision software capable of opening a web browser directly within the window or as an external software can integrate EcoStruxure Control Engineering -

Monitoring. You can integrate EcoStruxure Control Engineering - Monitoring into your supervision system either by automating the generation of the opening action from a variable or an alarm, or by adding an action button to launch it for the corresponding software (for example, in Visual Studio, the WebBrowser class defined in System.Windows.Forms

can be used to open a web browser window).

Integration With a Version Control System

WARNING

INCORRECT OR INCOMPLETE SOURCE CODE ANALYSIS

• In your risk assessment, consider all potential effects of inappropriate, incorrect, or incomplete input files used with EcoStruxure Control

Engineering.

• Do not rely on the data provided by EcoStruxure Control Engineering -

Monitoring as the sole source of information in monitoring, verifying, validating or otherwise assessing the operation of your machine/process.

Failure to follow these instructions can result in death, serious injury, or equipment damage.

Integrating EcoStruxure Control Engineering - Monitoring and a version control system facilitates keeping the controller application used for EcoStruxure Control

Engineering - Monitoring and the controller application used to run your system synchronized. After each modification to your controller application and the deployment of this controller application in your system, the following steps are required:

Step

Action

Exporting the code of the controller application in the corresponding format with the help of the EcoStruxure Control Engineering - Import/Export tool.

Launching the EcoStruxure Control Engineering - Monitoring program on the newly uploaded version of the code of the controller application.

These two steps can be executed automatically without user intervention. This is managed by script mechanisms (such as hooks) that are available in version control tools.

30 EIO0000004427.02

Monitoring an Controller Application

NOTE: Verify that EcoStruxure Control Engineering - Monitoring has access to both the archived controller applications and the data from the production systems.

EIO0000004427.02

Monitoring an Controller Application

Creating a Representation of an Controller Application

Procedure

No code analysis tool can provide analysis procedures for all potential types of code and methods of creating code. For example, a code block in your source code may be semantically invalid, but syntactically correct. A code analysis tool may not be able to detect such a condition.

Software development environments may provide code protection features intended to, for example, block access to intellectual property. Unlock such protected code blocks in your software development environment before creating export files to be used with EcoStruxure Control Engineering.

WARNING

INCORRECT OR INCOMPLETE SOURCE CODE ANALYSIS

• In your risk assessment, consider all potential effects of inappropriate, incorrect, or incomplete input files used with EcoStruxure Control

Engineering.

• Verify that the source code exported from your software development environment and to be used by EcoStruxure Control Engineering is complete and up to date.

• After modifications of any type whatsoever to the source code of your application resulting from your use of EcoStruxure Control Engineering, verify the correctness of the modified source code.

Failure to follow these instructions can result in death, serious injury, or equipment damage.

Step

Action

Select Documentation | Monitoring > Launch Monitoring on the Program page.

Upload the source files of the controller application exported from your software development environment as described in

Program Creation Wizard, page 19

Specify the files to be analyzed. If you do not want to generate the representation for each file, you can remove unwanted files by unselecting them in the list.

Start the representation process by clicking Launch .

NOTE: The time required to generate your representation depends on the size and complexity of the source code of the controller application. Progress information is displayed on the Program page.

32 EIO0000004427.02

Monitoring an Controller Application

The Data Flow View

General

The Data Flow view displays the relationships between variables of a controller application from input to output, or vice versa.

This view displays how the values of the variables of the controller application are read or written.

Displaying the Data Flow View

To display the Data Flow view, select Monitoring > Data flow .

NOTE: If you have downloaded a copy of the online results and want to work with the downloaded copy, open the file index.html

and click the button

Display Data Flow . Refer to

Downloading an Offline Version of the

Representation, page 42

Overview of the Data Flow View

The Data Flow view consists of four parts:

EIO0000004427.02

Monitoring an Controller Application

• List of variables to explore and settings for variables (top left, green frame)

• Dependency tree (bottom left, purple frame)

• Language settings (top right, blue frame)

• Cross references snippets (bottom right, yellow frame)

List of Variables

The list of variables to explore lets you select a variable whose dependencies you want to display. Click List Of Variables to select a variable.

Functions for finding a variable:

• You can scroll through the list using the page buttons at the bottom of the view. You can specify the number of variables to be displayed on a single page using the dropdown list at the top left part of the table.

• You can filter the variables using the search field at the top right part of the list. You can search by full or partial name, address and comment of a variable.

Click the name of a variable to display it in the dependency tree and in the cross references snippets parts of the page.

The Data flow direction let you specify the way the dependencies are listed and displayed.

Write displays only the dependencies that write the value of the variable.

Read displays only the variables that are written using the selected variable.

Read and write displays both. This selection also affects the way the

Dependency tree is displayed.

Dependency Tree

The Dependency tree is a graphical representation of the dependencies between the variables. If a variable is used to compute or to determine another value, this variable is displayed with a link to that other variable.

34 EIO0000004427.02

Monitoring an Controller Application

In the example above, the following is true of the selected (blue) variable ( Data flow direction is set to Read and write ):

• The variable needs the values of the two linked variables displayed to its left in order to calculate its own value.

• The variable is used to calculate the values of the linked variables displayed to its right.

You can explore the relationships between variables by clicking their names.

This view is helpful to locate the variables affected if code is modified in the controller application, or to determine an unwanted value of a variable in the running controller application.

Language Settings

The language settings let you select Ladder or Literal as the language for the cross reference snippets.

Depending on the different types of variables, a representation of the code in

Ladder may not be available. In such a case, the cross references are displayed in

Literal.

Creating a flow chart from an controller application is a complex operation.

Depending on the complexity of the code and the different types of objects,

EcoStruxure Control Engineering - Monitoring may not be able to generate a precise flow if a variable is indexed and/or if its address is accessed indirectly using a variable in the controller application.

Cross References Snippets

The cross references snippets part of the page displays how the variables are used in the calculations of one another.

It consists of a code extract, displayed in Ladder or Literal language, that highlights the relations. The code extract is not displayed in the same way it is written in the original code in order to provide a synthetic view. Its logic still remains the same as in the original code. The logic can be retrieved using the location displayed behind each snippet.

For instance, if you access a variable inside several nested conditional instructions, the snippet compresses these instructions into a single one.

EIO0000004427.02

Monitoring an Controller Application

The cross references snippets view is updated each time you select a variable either in the list of variables or in the dependency tree.

Live Visualization

EcoStruxure Control Engineering - Monitoring provides a live visualization of the values of the variables of the running controller application. The transmission latency between the running controller application and the visualization in

EcoStruxure Control Engineering - Monitoring depends on, among other things, the communication infrastructure, the server settings (refer to updateRate in

Configuration ), and the controller application itself.

To start the live visualization, click Start under Monitoring .

NOTE: The button Test Connection allows you to test the connection, for example, in order to test whether the view is frozen or the communication server is running.

The states of a variable are displayed depending on the type and the value:

• Boolean value: If the value is TRUE, the node is green. If the value is FALSE, the node is red.

• Non-boolean value: The value is displayed in a label associated with the node.

• Indeterminable: The “?” symbol is displayed next to the node if the value cannot be retrieved because it does not have an address or is not accessible.

In the following example, the boolean values are highlighted with an orange frame.

The non-boolean values are highlighted with a blue frame:

In the following example, the value of the variable A_ferm_vv depends on the variables Niv_sas , Niv_aval , Mode_manu and Mode_auto . The value of the variable A_ferm_vv determines the values of the variables Dde_ouv_vv and Dde_ ferm_v .

EIO0000004427.02

Monitoring an Controller Application

Representation in the dependency view:

Representation in Ladder language:

Representation in Literal language:

EIO0000004427.02

Monitoring an Controller Application

The Control Flow View

General

The Control Flow view displays the order in which the function or procedure calls are executed or evaluated.

This view displays the way the logic of the controller application is called.

Displaying the Control Flow View

Select Monitoring > Control flow .

NOTE: If you have downloaded a copy of the online results and want to work with the downloaded copy, open the file index.html

and click the button

Display Control Flow . Refer to

Downloading an Offline Version of the

Representation, page 42

38 EIO0000004427.02

Monitoring an Controller Application

Overview of the Control Flow View

The Control flow view consists of four parts:

• List of procedures to explore (top left, green frame)

• Dependency tree (bottom left, purple frame)

• Language settings (top right, blue frame)

• Cross references snippets (bottom right, yellow frame)

List of Procedures

The list of procedures lets you select a procedure whose call tree you want to display. Click List Of Procedures to select a function, function block or task

(which are generally referred to as called “procedure” in the EcoStruxure Control

Engineering tools).

EIO0000004427.02

Monitoring an Controller Application

Functions for finding a procedure:

• You can scroll through the list using the page buttons at the bottom of the view. You can specify the number of procedures to be displayed on a single page using the dropdown list at the top left part of the table.

• You can filter the procedures using the search field at the top right part of the list. You can search by full or partial name of the procedure.

Click the name of a procedure to display it in the dependency tree and in the cross references snippets parts of the page.

Dependency Tree

The Dependency tree is a graphical representation of the dependencies between the procedures.

The selected procedure is highlighted in blue. Each linked procedure displayed to its left is a procedure that calls it. Each linked procedure displayed to its right is a procedure that is called by it.

You can explore the relationships between procedures by clicking their names.

This view is helpful to determine how the procedures call each other.

Language Settings

The language settings let you select Ladder or Literal as the language for the cross reference snippets.

Depending on the different types of procedures, a representation of the code in

Ladder may not be available. In such a case, the cross references are displayed in

Literal.

Cross References Snippets

The cross references snippets part of the page displays how the different procedures call each other.

For instance, if you call a procedure inside several nested conditional instructions, the snippet compresses these instructions into a single one.

40 EIO0000004427.02

Monitoring an Controller Application

The cross references snippets view is updated each time you select a procedure either in the list of procedures or in the dependency tree.

EIO0000004427.02

Monitoring an Controller Application

Downloading an Offline Version of the Representation

You can download a copy of the EcoStruxure Control Engineering - Monitoring online results from the server to your local PC.

Download procedure:

Step

Action

Navigate to the Program page.

Select Monitoring > Download (zip) .

A ZIP file with the representation in HTML format is downloaded to your PC.

Extract the contents of the downloaded ZIP file and open the file index.html

if you want to work with the downloaded representation.

NOTE: Security policies in your organization may keep your browser from displaying certain or all HTML content stored on your PC. In such cases, contact your administrator to resolve this condition.

42 EIO0000004427.02

Manufacturer-Specific File Export Procedures

EcoStruxure Control Engineering tools use the source code files of controller applications as input files. These files are exported from the corresponding software development environments. The following sections provide information on generating these export files in various software development environments.

EcoStruxure Control Expert (.XEF / .ZEF File Export)

Export the EcoStruxure Control Expert (formerly Unity Pro) controller application to an XEF or a ZEF export file in order to be processed with EcoStruxure Control

Engineering tools.

To export the file, you can use the EcoStruxure Control Engineering Import/Export tool. Select SUPPORT > DOWNLOADS .

It is also possible to export the files using the EcoStruxure Control Expert menu:

Step

Action

From the menu, select File > Export application… .

In the Export application… dialog box, provide a name for the XEF or ZEF file.

If required, modify the storage location for the XEF or ZEF file.

Click Save .

EIO0000004427.02

Manufacturer-Specific File Export Procedures

EcoStruxure Machine Expert (.EXPORT File Export)

Export the EcoStruxure Machine Expert controller application to an XML export file (with the extension .export

) in order to be processed with EcoStruxure Control

Engineering tools.

Procedure:

Step

Action

From the menu, select Project > Export… .

2 You can export particular objects or a full tree. From the tabs in the Export dialog, select the objects to be included in the export file.

EIO0000004427.02

Manufacturer-Specific File Export Procedures

Step Action

NOTE: The checkbox One file per subtree allows you to generate separate export files for the selected subtrees. You can export the file with a specific

EcoStruxure Machine Expert version that you select from the dropdown list

Storage version . To re-import the file, this EcoStruxure Machine Expert version is used.

Click OK and provide a file name and a folder name as prompted.

Click Save .

EIO0000004427.02

Manufacturer-Specific File Export Procedures

PL7 Pro (.FEF File Export)

Export the PL7 Pro controller application to an FEF export file in order to be processed with EcoStruxure Control Engineering tools.

Procedure:

Step

Action

From the menu, select File > Export application… .

In the Export application… dialog box, provide a name for the FEF file.

If required, modify the storage location for the FEF file.

Click Save .

46 EIO0000004427.02

Manufacturer-Specific File Export Procedures

3S CODESYS V3 (.EXPORT File Export)

Export the CODESYS V3 controller application to an XML export file (with the extension .export

) in order to be processed with EcoStruxure Control Engineering tools.

Procedure:

Step

Action

From the menu, select Project > Export… .

2 You can export particular objects or a full tree. From the tabs in the Export dialog, select the objects to be included in the export file.

EIO0000004427.02

NOTE: The checkbox One file per subtree allows you to generate separate export files for the selected subtrees. You can export the file with a specific

CODESYS version that you select from the dropdown list Storage version . This version is then used to re-import the file in CODESYS. If you work on CODESYS

V3 code, select a version from the version 3 family ( CODESYS V3 … ).

Manufacturer-Specific File Export Procedures

Step

Action

Click OK .

Provide a file name and a folder name as prompted and click Save .

48 EIO0000004427.02

Manufacturer-Specific File Export Procedures

3S CODESYS V2 (.EXP File Export)

Export the CODESYS V2 controller application to an EXP export file in order to be processed with EcoStruxure Control Engineering tools.

Step

Action

From the menu, select Project

Export… .

2 In the Export Project dialog box, select the objects to be included in the export file

(with the default settings, a selected item has a blue background), then click OK .

EIO0000004427.02

Step Action

Manufacturer-Specific File Export Procedures

Click OK and provide a file name and a folder name as prompted.

Click Save .

EIO0000004427.02

Manufacturer-Specific File Export Procedures

BECKHOFF TwinCAT V3 (.XML File Export)

Export the Beckhoff TwinCAT controller application to an XML export file

(PLCopen) in order to be processed with EcoStruxure Control Engineering tools.

Step

Action

In the Solution Explorer window, select the project.

2 Right-click the project and select Export PLCopenXML… .

3 Click Save .

EIO0000004427.02

Manufacturer-Specific File Export Procedures

PHOENIX CONTACT Multiprog v5.5 (.XML File Export)

Export the MULTIPROG controller application to an XML export file in order to be processed with EcoStruxure Control Engineering tools.

Step

Action

From the menu, select File

Export… .

2 Select Export PLCopen xml file .

Provide a name for the export file.

Click Save .

As MULTIPROG can export the controller application in different versions of

PLCopen, there may be differences in the way your EcoStruxure Control

Engineering tool processes the export file, depending on the PLCopen version.

EIO0000004427.02

Manufacturer-Specific File Export Procedures

Rockwell Automation

®

RSLogix 5000

®

or Studio 5000 (.

L5K File Export)

Export the Rockwell Automation ® RSLogix 5000 ® controller application to a L5K export file in order to be processed with EcoStruxure Control Engineering tools.

Step

Action

From the menu, select File > Save as… .

In the Save as… dialog box, provide a name for the L5K file.

If required, modify the storage location.

Select the file type: RSLogix 5000 Import/Export File (*.L5K) .

Click Save .

EIO0000004427.02

Manufacturer-Specific File Export Procedures

Siemens SIMATIC STEP 7 (.ASC, .AWL, .GR7 and .SCL File

Export)

Overview

The following steps are required to process a Siemens SIMATIC STEP 7 controller application with EcoStruxure Control Engineering tools:

• Set your SIMATIC STEP 7 workshop to German abbreviations (mnemonics).

• Create and export the symbols of the controller application to an .ASC

file.

• Create and export the contact code (CONT) to an .AWL

file.

• Create and export the graph blocks (GRAPH) to a .GR7

files.

• Compile the CFC code (if any) to create the corresponding SCL sources.

• Export structural codes (SCL) to .SCL

files.

Setting German Mnemonics

Before creating the export files, set your SIMATIC STEP 7 workshop to German abbreviations (mnemonics):

54 EIO0000004427.02

Manufacturer-Specific File Export Procedures

Step

Action

From the menu, select Options > Customize… .

2 Display the Language tab.

EIO0000004427.02

Select German mnemonics.

Click OK .

Manufacturer-Specific File Export Procedures

Creating an ASC File

Step

Action

Right-click the symbols table in your program folder and select Open object .

2 From the menu of the symbols editor, select Symbol Table > Export… .

3 Select ASCII Format (*.ASC) .

Provide a name and select a directory for the .ASC

export file.

Click Save .

Creating an AWL File

To create an .AWL

file, first generate the LIST source for the code blocks developed in the languages CONT, LIST and LOG.

56 EIO0000004427.02

Manufacturer-Specific File Export Procedures

Step

Action

Right-click a CONT, LIST or LOG source and select Open Object to open the CONT/

LIST/LOG code editor.

2 From the menu, select File > Close to close all open objects.

3 From the menu, select File > Generate source… to generate the program source.

EIO0000004427.02

Step

Action

Provide an object name and click OK .

Manufacturer-Specific File Export Procedures

5 Click All to select all program blocks and select the options Sort according to program structure and Symbolic addresses.

6 Click OK to confirm.

If your controller application contains safety-related blocks, export those blocks in a separate AWL file. Refer to

Safety-Related Applications, page 61

for details.

Creating a GR7 File

The .GR7

sources have to be created for each GRAPH blocks separately. Repeat the following procedure for each GRAPH block to be exported.

58 EIO0000004427.02

Manufacturer-Specific File Export Procedures

Step

Action

Right-click a GRAPH object and select Open Object .

2 From the menu, select File > Generate Source File .

3 Provide a name for the GRAPH object.

EIO0000004427.02

Click OK to confirm.

Repeat the procedure for each GRAPH object to be exported.

Manufacturer-Specific File Export Procedures

Creating a CFG File

The CFG file is required for analyzing the communication and the hardware configuration of the station.

Step

Action

Double-click your CPU's links in the main window to open NetPro.

In the NetPro window, double-click the CPU of the station to be exported open the HW

Config utility.

From the Station menu, select Export… to export your station configuration (leave the default settings in the dialog).

If the controller application contains CFC code, compile the code to generate the corresponding SCL source files which are the files processed with EcoStruxure Control

Engineering tools. To do so, open the CFC code editor by clicking its icon in the toolbar of the main window .

60 EIO0000004427.02

Manufacturer-Specific File Export Procedures

Step

Action

Compile the code with the options Entire program and Generate SCL sources and click OK .

6 The generated SCL source file can then be exported like other source files (refer to

Exporting Files, page 65 ).

Safety-Related Applications

A safety-related controller application contains two code parts:

• The non-safety-related code part

• The safety-related code part

Procedure for exporting controller applications that contain safety-related code:

Step

Action

Export the .ASC

file that contains the database for the safety-related code and for the non-safety-related code (refer to

Creating an ASC File, page 56

Generate the sources for the non-safety-related code parts (refer to

Creating an AWL

File, page 56

and

Creating a GR7 File, page 58

EIO0000004427.02

Manufacturer-Specific File Export Procedures

Step

Action

Click All to select all program blocks and select the options Sort according to program structure and Symbolic addresses.

Click OK to confirm.

Follow the procedure for

Creating an AWL File, page 56

until the dialog Generate source Safety is displayed.

EIO0000004427.02

Manufacturer-Specific File Export Procedures

Step

Action

Select the option User-created F-FBs, F-FCs and F-DBs and click OK to confirm.

7 Create a .dif

file (refer to

Creating a dif File, page 63 ). The

.dif

file is used to determine whether code is safety-related.

Creating a dif File

A .dif

file is created in the SIMATIC Manager of SIMATIC STEP 7 in the following way:

EIO0000004427.02

Manufacturer-Specific File Export Procedures

Step

Action

From the menu, select Options > Reference Data > Display .

2 In the Display S7 reference data dialog, select the option regenerated?

and click Yes .

3 In the Customize dialog, select the option Program Structure and click OK to display the program structure.

EIO0000004427.02

Manufacturer-Specific File Export Procedures

Step

Action

From the menu, select View > Export to open the Save dialog box.

5 Provide a name for the .dif

and click Save .

Exporting Files

After you have created the files, export them from SIMATIC STEP 7:

Step

Action

Select the LIST, GRAPH (or .AWL

and .GR7

files) and SCL sources that you have generated.

Right-click the sources and select Export source… .

EIO0000004427.02

3 Select a file name and a storage location and click Save .

Manufacturer-Specific File Export Procedures

Siemens TIA Portal SIMATIC STEP 7 (.ZIP File Export)

Export the Siemens TIA Portal SIMATIC STEP 7 controller application to a ZIP export file in order to be processed with EcoStruxure Control Engineering tools.

The export can be performed automatically with the EcoStruxure Control

Engineering - Import/Export tool. Select SUPPORT > DOWNLOADS .

Refer to the EcoStruxure Control Engineering - Import/Export user guide for details on the export procedure.

66 EIO0000004427.02

Schneider Electric

35 rue Joseph Monier

92500 Rueil Malmaison

France

+ 33 (0) 1 41 29 70 00 www.se.com

As standards, specifications, and design change from time to time, please ask for confirmation of the information given in this publication.

EIO0000004427.02

Key features

Provides live views of running controller applications.
Reduces downtime by supporting diagnostics.
Offers data flow dependence tree with cross-references.
Displays values of variables in the running controller application.
SaaS tool accessible with a web browser.
Supports determining potential causes for machine downtime.
Aids in securing the system before a restart.
Supports diagnostics of hardware and software issues.
Helps identify missing criteria.

Frequently asked questions

It is a diagnostics solution that provides live views of your running controller application, reducing downtime by helping operators and maintenance teams diagnose issues.

It provides a representation of the structure of your controller application in the form of a data flow dependence tree with corresponding cross references showing the equations related to a selected variable. It displays the values of the variables of the running controller application.

Operators, maintenance teams, and automation experts/developers can all benefit from using EcoStruxure Control Engineering - Monitoring.

EcoStruxure

™

Control Engineering

Monitoring

User Guide

Legal Information

Table of Contents

Safety Information

Important Information

DANGER

WARNING

CAUTION

NOTICE

Please Note

Before You Begin

Start-up and Test

Operation and Adjustments

About the Book

Document Scope

Validity Note

Related Documents

Product Related Information

Terminology Derived from Standards

Introduction to EcoStruxure Control Engineering -

Monitoring

Overview

Use Cases

Registration, Licenses and Sessions

Registration

Overview

Browser Compatibility

Registration

Licenses

Overview

Paid License Plans

Sessions

Automatic Log-Out (Session Time-Out)

Multiple Sessions

Creating Projects and Programs

Introduction to Projects and Programs

Overview

Example

Creating Projects and Programs

Creating Projects

Creating Programs

Program Creation Wizard

Overview

Step 1 - Start

Step 2 - Parameters

Step 3 - License

Step 4 - Source file

Step 5 - Summary

Accessing a Shared Program

Sharing Programs with Other Users

Overview

Sharing with a Specific User

Sharing with Everyone

Monitoring an Controller Application

Pre-Deployment Considerations

Overview

Pre-Requisites Regarding the Controller Application

Architecture

Overview

Web Platform

Communication Server (COM Server)

Communication using OPC Server

Communication using OPC Server and Communication Server

Direct Communication using Modbus TCP

Installation and Configuration

Package

Installation of the Virtual Machine

Installation of the Communication Server

Configuration

Installation of the EcoStruxure Control Engineering - Monitoring

Service of the Communication Server

Integration With a Supervision System

Integration With a Version Control System

Creating a Representation of an Controller Application

Procedure

The Data Flow View

Schneider Electric 如何处理Machine 项目ユーザーガイド

Schneider Electric 如何仿真ユーザーガイド

Schneider Electric 如何实现用户文档ユーザーガイド