Industrial Automation Knowledge Base

Issue Integration of OPC UA Server in rack with Ecostruxure Process Expert Resolution This document will guide you in the integration of the OPC UA Server Module in Rack BMENUA0100 with Ecostruxure Process Expert for AVEVA System Platform. Disclaimer The views and opinions expressed in this article are those of the author(s) and do not necessarily reflect the official policy or position of Schneider Electric.  

This technical document will guide you to develop a project based on EcoStruxure Process Expert for AVEVA System Platform. The document will help you to create a project from scratch and also shows the benefits of using this engineering platform.

Issue By default you can only acknowledge one Alarm at a time using the three exclamation marks !!!   Resolution The following knowledge base article details the steps required to Acknowledge either All Alarms or All Visible Alarms. Acknowledgement of Visible Alarms is particularly useful for Alarm banners.   Step 1 – Identify the Alarm Control Name Open the Canvas that contains the Alarm Control and select the Alarm Control. In the following example the name is alarmGrid1, record for later.     Step 2 – Acknowledgment Buttons   Place two buttons on the Canvas, one for Ack All Alarms and the other for Ack Visible Alarms. In this example the button names are AckAllAlarms and AckVisableAlarms.      Step 3 – Acknowledge All Alarms Button Code Select the Ack All Alarms Button and in the properties window, click the lightning symbol (events).     Double-click in the column right of the Click event and the Code Window will open with the function event name automatically created (AckAckAlarmsClick).     Start to type in the Alarm Control Name, e.g. alarmGrid1 and the IntelliSense will offer suggestions; select the Alarm Control Name or select Enter.   Once the Alarm Control has been created enter a Full Stop and a second IntelliSense box will appear, select AckAllAlarms     Finish with ():  so the following is displayed:   Return to the canvas by clicking the following icon:   Step 4 – Acknowledge All Visible Alarms Button Code Repeat Step 3 for the AckVisableAlarms button and create the following code:   Step 5 – HMI Test Start the HMI and test that the buttons work.   Disclaimer   The views and opinions expressed in this article are those of the author(s) and do not necessarily reflect the official policy or position of Schneider Electric.  

Issue When using EcoStruxure Automation Expert V22.1 and AVEVA System Platform the Galaxy project needs to contain all the templates associated with EcoStruxure Automation Expert AppCommonProcess Library, by default the Galaxy backup supplied by EcoStruxure Automation Expert V22.1 is for AVEVA System Platform 2020 R2 SP1. To use a newer version of AVEVA System Platform requires migration. Resolution The following knowledge base article details how to migrate the Galaxy backup supplied by EcoStruxure Automation Expert V22.1 to AVEVA System Platform 2023. The first time EcoStruxure Automation Expert is used to create a AVEVA System Platform Galaxy, it will copy the Galaxy project supplied as part of the installation (called CFLBlankGalaxy) from the ASP Library folder to the AVEVA System Platform BackupGalaxies folder.   Once the Galaxy backup has been copied, it will then create all other projects based upon this backup. The aim is to replace this backup file with a fully migrated version.     Step 1 – Create a temporary EcoStruxure Automation Expert Solution Create a temporary solution and right click on the solution and select Configuration>AVEVA SP Configuration      Give the new Galaxy project any name and click Create   After some time you will notice a message in the Output window saying ‘Galaxy needs to be migrated manually’.   Cancel the System Platform Configuration form.   Step 2 – Migrate the Galaxy project  Open System Platform IDE and select On Server and double click on the project created by EcoStruxure Automation Expert.   A message will be displayed asking if you want to migrate, select Yes   The migration will start and will take some time (around 45 minutes), once the migration is complete click the Close button.   Once the Close button has been clicked you will be asked to log in. The default username and password is Administrator and password left blank.   When the AVEVA System Platform IDE opens, close without making any changes.   Step 3 – Create a Galaxy Backup from the Migrate project  Open the Operations Control Management Console   Navigate to the newly created Galaxy project and right click and select Backup.   Confirm that you want to create a Backup by clicking Yes   Save the backup to a known folder, e.g., Downloads and name it CFLBlankGalaxy     Step 4 – Copy the new CFLBlankGalaxy over the old Copy and Replace the newly-created Backup to the BackupGalaxies Folder     From this point on Automation Expert will create any new Galaxy projects using the migrated CFLBlankGalaxy backup. . Disclaimer The views and opinions expressed in this article are those of the author(s) and do not necessarily reflect the official policy or position of Schneider Electric.  

How do I create custom templates within EcoStruxure Automation Expert which will allow me to synchronize to AVEVA System Platform?

Issue EcoStruxure Control Expert - Asset Link uses Patterns to crate, update and delete Assets and Attributes within AVEVA System Platform.  EcoStruxure Control Expert - Asset Link can also be configured to create Patterns. Resolution The aim of this document is to provide a step by step guide for creating a Pattern for EcoStruxure Control Expert - Asset Link. It provides the user with an EcoStruxure Control Expert Project and a corresponding Template for AVEVA System Platform. Disclaimer The views and opinions expressed in this article are those of the author(s) and do not necessarily reflect the official policy or position of Schneider Electric.  

Issue At System Platform Management Console (SMC) is where all the communication drivers from AVEVA System Platform are installed. Natively, we can have OPC DA clients, OPC UA clients, we can use Modicon Communication Server, as an OPC UA Server to communicate with Modicon PLC’s. We can also use SMC as an OPC DA Server, to make all the variables from AVEVA System Platform available to other OPC DA clients, such as Inbatch. Disclaimer The views and opinions expressed in this article are those of the author(s) and do not necessarily reflect the official policy or position of Schneider Electric.  

Issue For the public not familiarized with Aveva System Platform 2020 and how to configure a setup of one GR node and one EAE client so that the EAE can connect to the Galaxy Repository.  Resolution Explain all the required AVEVA System Platform Components in both machines together with the DCOM settings Disclaimer The views and opinions expressed in this article are those of the author(s) and do not necessarily reflect the official policy or position of Schneider Electric.  

Issue This document will help you in the integration and configuration of the IO.MBTCP driver for AVEVA System Platform as well as in the integration of the AVEVA Insight cloud historization solution.   Resolution For this proof of concept, we have created a small application in M580 with a localized variable. This variable will be read through IO.MBTCP Driver and then will be published in AVEVA Insight. Disclaimer The views and opinions expressed in this article are those of the author(s) and do not necessarily reflect the official policy or position of Schneider Electric.