StruxureWare PowerSCADA Expert v7.30 Delta Technical Training

Schneider Electric 1- Power Solutions

StruxureWare PowerSCADA Expert v7.30

Delta Technical Training


Course Description

● The PowerSCADA Expert v7.30 delta technical training course provides students with a comprehensive overview of the new features of StruxureWare PowerSCADA Expert v7.30 and the practical skills to use this tools.


StruxureWare PowerSCADA Expert v7.30Agenda

● Installation and StruxureWare rebranding● VijeoCitect Core Changes ● PLS_Include Changes● Profile Editor ● One Line configuration● Historical Reports● Support contacts and Documentation● Key Points to Remember



● Installation and StruxureWare rebranding● Rebranding● Software Requirements● Hardware Requirements● Installation Procedure● Optional Components (add-ons)

● VijeoCitect Core Changes ● PLS_Include Changes● Profile Editor ● One Line configuration● Historical Reports● Support contacts and Documentation● Key Points to Remember


Re-branding

● Full re-branding from PowerLogic SCADA to PowerSCADA Expert


Re-branding (cont.)

Updated software interface look and feel, identifies as a StruxureWare Product. ● Installation process dialogs

● Software startup screen

● Project template Pls_Style_1

● Runtime splash screen

● Profile Editor shortcut

● Profile Wizard Screens

● Documentation

● Etc…


Hardware Requirements

● Updated hardware requirements:

Further info: Vijeo Citect 7.30 Installation Guide


Software Requirements

● Updated software requirements:


Installation

● The StruxureWare PowerSCADA V7.30 Installation procedure is similar to previous versions with some additional features

> See the “PowerSCADA Expert v7.30 Installation Instructions” for more information


Installation (Cont.)

● IIS is required for the historical reports tool.● Needs to be installed and configured in Windows XP and Server 2003● Preinstalled in Windows 7 and 2008




● New installed Components:● Schneider Electric License Manager




● New Add-on● PowerSCADA Expert Reporting



Upgrades from v7.20 to v7.30

For a smooth upgrade from version 7.20 to version 7.30, please follow these best practices:

• Backup the Data directory when importing from another Profile Editor instance.

• Do not make changes to PLS_Include, if possible.

• Use the Migration Utility to migrate projects from previous versions


Upgrades from v7.20 to v7.30 (cont.)

The migration utility allows you to migrate previous versions of PowerSCADA Expert to the current version. You only need to run this utility one time.

Schneider Electric 15- Power SolutionsSchneider Electric 15- Power Solutions

Install StruxureWare PowerSCADA Expert v7.30

Procedure● Connect to the provided virtual machine:

●Username: Administrator●Password: 1()NE25pm

● Follow the Installation instructions to install PowerSCADA v7.30 Expert all core components.

● Run the PLS_Example and leave it running.

Results Expected● StruxureWare PowerSCADA v7.30 successfully installed● Become familiar with the new re-branding and project runtime look and

feel.



● Installation and StruxureWare rebranding● VijeoCitect Core Changes

● Alarming● OPC DA● Library_Controls Project● Equipment● Scheduler

● PLS_Include Changes● Profile Editor ● One Line configuration● Historical Reports● Support contacts and Documentation● Key Points to Remember


Vijeo Citect Core Changes - AlarmingArchitectural Overview

Alarm Properties

IO Server

Cle

arS

CA

DA

serv

er

Alarm Server proc

Display Client

AlarmConnector

DBServerCore

SQL server OPC A&E

server

CS DB

Alarm view

Arbitration

TCP server

Alarm conf.

(RDB)

Alarm Engine

Redundant alarm server

CS DBClient

Intermediate layer• DB inside alarm server process

• Client-server comm’s direct to DB

• Synchronisation handled by DB

• Alarm properties unchanged


Vijeo Citect Core Changes - AlarmingRedundancy

● Synchronization occurs periodically between partner servers

● Whilst both servers are running, only one is ‘Main’

● Writes to the DB will only occur on the ‘Main’ server

● If network lost between servers, both will operate as ‘Main’

● When connection re-established, an attempt is made to reconcile data

● SOE (Sequence of Events) should show events from both servers

● Configuration changes made during the network disconnect may be lost


Vijeo Citect Core Changes - AlarmingAlarm Engine

● In previous versions, all alarms evaluated every [Alarm]ScanTime● All IO tag values read from client cache every 500ms by default

● Now, alarm only evaluated when input (tag or cicode) changes state● No I/O Tag scanning = Less CPU usage● [Alarm]ScanTime only used to know what rate to subscribe IO tag at● ...except advanced alarms, where cicode expression still evaluated every

ScanTime.● Removed limit of 64k alarms of each type


Vijeo Citect Core Changes - AlarmingConfiguration

● Largely unchanged

● Alarm server config form

● New DB port (default 5482)

● This port must be accessible to clients (firewall mods?)

● Must be defined if more than one server on one address


Vijeo Citect Core Changes - AlarmingConfiguration (cont.)

● Alarm definitions

● Equipment / tag item fields added

● Historize field added

● No 64k limit

● Category must exist


Vijeo Citect Core Changes - AlarmingArchiving

• Event Journal can be archived and restored• Configuring archiving ([Alarm] section of citect.ini):

• ArchiveAfter (weeks, default is 4)• KeepOnlineFor (weeks, default is 6)

No control over archiving time


Vijeo Citect Core Changes - AlarmingArchiving (cont.)

● Manual: Cicode function SOEArchive()● Archives data eligible for archiving into ArchivePath location. It

will create a folder with a prefix specified in ArchivePrefix (if any) and will add current date to the folder name.

● The media needs to be labelled.● Automatic: configured on AlarmServer


Vijeo Citect Core Changes - AlarmingArchiving (cont.)

Using Scheduler to archive:

• Create an equipment, mark it as scheduled• Create a new state for it – archive• Put archiving cicode as an entry command:

•Login(“Engineer”, “citect”);•SOEArchive();

• On a scheduler page in runtime create a schedule entry to archive (single entry or recurring).


Redundant Configuration

● Archiving will only happens on server where main database is running at the time of archiving

● To ensure the archiving operation can only be executed, need to configure both Primary and Standby servers for archiving ([Alarm.Cluster.Server])


What happened if you don’t archive?

Citect.ini[Alarm]

KeepOnlineFor = 10

After 10 weeks the data will be deleted from the database!

The default value for KeepOnlineFor parameter is 6 weeks.


Restoring

● SOEMount(path)● Restores data from the path specified, displays the restored data in

sequence of event page● Does not bring data back to the database, just allow you to browse the

data!● SOEDismount


Vijeo Citect Core Changes - AlarmingProject Upgrade

● Migration of Historical Data● One-off import of data from <project name>_<cluster>_ALMSAVE.DAT● Only happens when DB is created for the first time● Simply leave [Alarm]SavePrimary and [Alarm]SaveSecondary as they are

● DB lives in [Data]● i.e. Data directory will get larger than

previous versions

● Higher memory requirements● DB is always loaded in memory● Require more RAM to run same project

● Some user/role names are now reserved● Users: Driver, Logic, Schedule, System● Roles: Default


Vijeo Citect Core Changes - AlarmingOPC A&E Interface

● Computer setup wizard

● OPC Alarms and Events registration


Vijeo Citect Core Changes - AlarmingOPC A&E Interface (Cont.)


Register PSE v7.30 OPC A&E Server.

Procedure● Open the Project Editor and run the computer setup wizard in custom

mode for the PLS_Example project. ● Register the OPC A&E server● Run the project.● Connect to the OPC A&E Server using an OPC Client (Provided in the

VM)● Subscribe to alarms.

Results Expected● See the OPC A&E server using OPC Explorer● Read some alarms using OPC Explorer


Vijeo Citect Core Changes – OPC DAOverview

• Brand new implementation “SchneiderElectric.SCADA.OpcDaServer.1”

• Full implementation of OPC DA v2.05 and v3.0 specification

• Self-certified using OPC Foundation’s test tools (CTT)


Vijeo Citect Core Changes – OPC DAOverview (Cont.)

• Runs as SCADA process of OpcDaServer type (one per machine)• Managed by Runtime Manager process• Designed using the same pattern used for all other SCADA processes

(SCADA kernel + .NET SCADA Platform using PSI)


Vijeo Citect Core Changes – OPC DABasic Configuration

• Configured as any other SCADA server process

• No need to specify cluster as OPC DA Server connects to all cluster• Can be configured to provide “Flat” tag structure and “Hierarchy”

where clusters and equipment branches are visible.


Vijeo Citect Core Changes – OPC DAAdvanced Configuration

● Enables vendor specific Item properties allowing OPC Clients to read some Tag Extension field related to the tag


Vijeo Citect Core Changes – OPC DARuntime

● Always runs as separate SCADA process (even when SCADA is configured as single process)

● If it is not configured by SCADA project OPC DA Clients won’t be able to connect, browse any tags or read or write any data.

● SCADA tags subscribed through OPC DA Server are contributing to client point count.


Vijeo Citect Core Changes – OPC DADiagnostics

● Same model as for all other SCADA processes

● syslog file syslog.OpcDaServer.<server name>.log

● tracelog file tracelog.OpcDaServer.<server name>.log

● crash dump user.OpcDaServer.<server name>.dmp

● Kernel page

● Third party diagnostics

● OPC Analyzer application


Vijeo Citect Core Changes – OPC DADiagnostics (Cont.)



OPC Analyzer

● Provided by OPC Foundation. Latest version 1.03.1014 is available at http://opcfoundation.org/DownloadFile.aspx?CM=3&RI=902&CU=4 or on local network at \\syd-file01\VOLATILE\APPS\OPC Foundation

● Allows tracing of COM traffic to/from OPC DA Server

● Traces can be saved and loaded into OPC Analyzer for off-line analysis of OPC DA traffic.

● OPC Analyzer connects between OPC DA Client and OPC DA Server as proxy.

● It can be used for both, debugging OPC DA Client traffic and OPC DA Server traffic in various COM/DCOM configurations.

http://opcfoundation.org/DownloadFile.aspx?CM=3&RI=902&CU=4



OPC Analyzer


Configure a PSE v7.30 OPC DA Server

Procedure● Open the Project Editor and configure an OPC DA Server for the

PLS_Example project. Use Hierarchy for the Browse Hierarchy option.● Compile and run the Computer Setup Wizard● Run the project.● Connect to the OPC Server using an OPC Client (Provided in the VM)

Results Expected● See the OPC DA Server running as a separate project in PSE● Connect to the OPC DA Server and read tags using the hierarchy with the

Matrikon OPC explorer


Vijeo Citect Core ChangesLibrary_Controls Project

The Library Control Include project is a series of genies for common UI controls such as an equipment tree view, data table, and vertical and horizontal scrollbars.


Vijeo Citect Core ChangesLibrary_Controls Project (cont.)

● Another Built-in Include project for common UI controls● Automatically included if project is created based on Tab_Style_1 template● The following UI Controls are found in genie library, lib_controls:

● Tree● EquipTree● Table● AlarmTable● TagTable● BrowseTable● SqlTable● TableRow● Scrollbar_Horz● Scrollbar_Vert● Slider


Vijeo Citect Core ChangesLibrary_Controls Project (Cont.)

● Paste genie on page, and enter parameter in Genie substitution form.● Most genies are not to be manually resized in Graphics Builder. Set its

width, height or length, etc. in the genie form.● Mandatory Fields:

● Name - must be unique within a page● Width, Height, …- dimension in pixels (to be resized to) at runtime● Refresh Rate - min. interval (in millisecond) for the control to update● Scan Delay - no. of page scan to wait before control initializes

● Scrollbar Fields● Horiz. / Vert. - assign name of scrollbar genies to work with this ctrl.

● User (Callback) Functions:● Initialize, Mouse, … - set function call with keyword subs. & literals as

args.


Vijeo Citect Core ChangesLibrary_Controls Project (Cont.)

● Two types of Cicode files found in project:● Normally named for public use, e.g. Table.ci, Tree.ci, Slider.ci, etc.● Underscored for internal use, e.g. _Internal_Table.ci, _Internal_Tree.ci,

etc.● Common functions to get / set properties of genie control:

● …GetProperty(), GetPropertyInt()● …SetProperty(), …SetPropertyInt()

● Common callback hooks:● Initialize - called when genie is initialized, Func(“#Name”)● Reload - called when genie is “redrawn”, Func(“#Name”, …)● LClick - called when left button clicked, Func(“#Name”, …)● RClick - called when right button clicked, Func(“#Name”, …)● #<keyword> is substituted with the metadata of the genie when the

function is called. Please see public Cicode files for the available subs. keywords for different control genies.


Vijeo Citect Core Changes – EquipmentOverview

● The term "Equipment" provides a conceptual way of providing logical groupings of SCADA objects in your system, such as trends, alarms, accumulators etc. The grouping can be created down to the level of one or more items by the use of a textual representation of an equipment hierarchy

● The textual representation of a hierarchy is achieved by the use of a dot, or period (".") to separate the items and their level in the hierarchy. Ex. Factory1.Line1.Assy2.Convey2


Vijeo Citect Core Changes – EquipmentRules

● Definition● Dots are used to define its place in the hierarchy i.e. Site1.Building1.Panel1● Fully qualified equipment name must be less than 254 characters● Each level of the hierarchy must be 63 characters of less.● The hierarchy must be no more than 14 levels deep.

● Syntax● Follows rules for tag naming, including the ‘.’ character.● Can start with a number if [General] TagStartDigit = 1

● Clustering● Equipment names are unique across clusters.● Compile error if two clusters exist and cluster names for equipment are

blank.


Vijeo Citect Core Changes – EquipmentEquipment and Scheduler


Vijeo Citect Core Changes – EquipmentEquipment in PSE v7.30


View Equipment Hierarchy in PSE v7.30

Procedure● Open the Graphics Builder and add a new page in the PLS_Example

project● Paste the genie: lib_controls.equiptree in the new page● Save the page and add the page to the Menu Configuration Parameters● Run the project.● Go to the new Page in the runtime and expand the items of the tree

hierarchy, compare the tree to the equipment database in the Project Editor

Results Expected● New page with a tree view of the equipment hierarchy.● Be familiar with the concept of equipment.


Vijeo Citect Core Changes - SchedulerOverview

The Scheduler is a component of the report server featuring an ActiveX control that links your SCADA system to a calendar. Using the control you can schedule equipment operations around peak and non-peak work hours within a business. You can create recurring schedules, and configure and view schedule entries on a daily, weekly and monthly basis.


Vijeo Citect Core Changes - SchedulerScheduler Engine

• Scheduler has been designed to be a core component of the report server.

• This provides tight integration with the SCADA.

• It also supports the online change functionality available with PowerSCADA Expert using the report server reload.

• Backup schedule entries made at runtime copy the file (located in the Data directory): [ClusterName].[ReportServerName].scheduling.xml to a secondary location.

• Only shows equipment that belongs to areas were the user has access to.

• Redundancy is provided. See the product help for more details.

• Troubleshoot with Kernel and the Tracelog.


Vijeo Citect Core Changes - SchedulerConfiguration

• Scheduler configuration is related to the configuration of Equipment and States

• In Scheduler, equipment is any item or items in your control system that can be scheduled to operate, such as a set of lights ,a single light in a room, heating or even a motor.

• Equipment States belong to equipment and determine the action that the item or group of equipment will take at a scheduled time.


Vijeo Citect Core Changes - SchedulerConfiguring Equipment

Equipment is defined in PSE using the Equipment form, which is accessible from the Equipment menu in the Project Editor.

The following fields are used specifically when setting schedules for this item of equipment:

• Scheduled• Default State


Vijeo Citect Core Changes - SchedulerConfiguring Equipment States

As equipment can have multiple states, identify the states that exist for the equipment before defining them


Vijeo Citect Core Changes - SchedulerConfiguring Equipment States (Cont.)

• The entry action is a Cicode expression to execute when the equipment transitions to the state. For example, the expression can be used to write a value to a variable tag.

• A delay is a period where the entry action does not occur until the period of the delay has elapsed. Delay enables you to turn on equipment sequentially thus avoiding a power spike.

• When configuring states you can define a repeat action. This action can be set to repeat for the specified repeat period



Entry Action:



Delay:



Repeat Action and Period:



Demand response (DR) refers to the mechanisms used for the management of electricity consumption in response to supply conditions

In Scheduler, states can be defined multiple times, each for a specific DR mode



• The default DR mode value is '0'. When the DR mode field is empty, the default value is used.

• Set the DR mode on equipment using the EquipSetProperty Cicode function

For example : EquipSetProperty (Equipment, "DRMODE", "1", cluster)


Add States to an Existing Piece ofEquipment

Procedure● Open the Project Editor and add an On and Off State to the following

devices:●S33K_A_INC●S33K_B_INC

● Hint: On state, TagPrefix\XCBR1\Pos = 2 ● Off State: TagPrefix\XCBR1\Pos = 1

Results Expected● 4 new entries to the Equipment States DB.


Vijeo Citect Core Changes - SchedulerUsing the ActiveX Control

Being an ActiveX control, you can insert the Scheduler as an object on a PowerSCADA Expert graphics page.

To do this, do one of the following:• Go to Edit | Insert ActiveX Control. The Insert ActiveX dialog box

appears.


Vijeo Citect Core Changes - SchedulerUsing the ActiveX Control (Cont.)

• In Graphics Builder go to Objects | Scheduler or Ctrl-U



• In Graphics Builder, display the toolbar from the View|Show Toolbar menu and click the Scheduler tool.


Add the Scheduler to a Graphic Page in PSE v7.30

Procedure● Open the Graphics Builder and add a new page in the PLS_Example

project● Paste SE Energy Scheduler ActiveX Control to the new page● Save the page and add the page to the Menu Configuration Parameters● Compile the project.

Results Expected● New page with the Scheduler control ActiveX


Vijeo Citect Core Changes - SchedulerRuntime Interface

The interface is divided into the following areas:

Equipment Tree Calendar


Vijeo Citect Core Changes - SchedulerRuntime Interface

There are two views available in Scheduler. The views are selected using the tabs at the top of the calendar display.


Vijeo Citect Core Changes - SchedulerEquipment Tree

The equipment tree lists equipment that was defined as being part of the system's operations.

Only Equipment with the parameter Scheduled set to TRUE will display in the tree


Vijeo Citect Core Changes - SchedulerEquipment Tree (Cont.)

In the tree-view nodes can be expanded and collapsed to display their children.

Automatic mode Override

A piece of virtual equipment No Context Menu

Manual override Remove Override Set to State

Inherited override Override

Context Menu


Vijeo Citect Core Changes - SchedulerSchedule Entry

Schedules can be defined for any equipment that has valid states.


Add Entries to the Scheduler in Runtime

Procedure● Run the project● Go to the recently created page and create entries in the schedule to

change the state of the Generators (GEN1…GEN4) and to change the state of the Incomers (S33K_A_INC and S33K_B_INC)

● Play with different combinations and see the state change in the single line graphic page.

Results Expected● Circuit breakers opening and closing automatically in runtime based on the

schedule entries.


Vijeo Citect Core Changes - SchedulerSchedule Recurrent Entry

Use this dialog if the schedule entry needs to occur regularly at the same time, on a daily, weekly, monthly basis


Vijeo Citect Core Changes - SchedulerEditing and Deleting Entries

• To Modify an existing entry double click the entry in the calendar and change the values

• To delete an existing entry select the schedule entry and press delete on your keyboard, or select the delete icon on the entry.

• Schedule entries can overlap due to schedule inheritance, or when schedule entries are created and or modified causing an overlap with one that already exists.

Further info on overlapping and inheritance rules: PowerSCADA Expert 7.30 User Guide


Modify existing Entries to the Scheduler in Runtime

Procedure● Open the Scheduler page again and modify existing entries, make the

entries recurrent. Delete some entries.● Play with different combinations and see the state change in the single line

graphic page.

Results Expected● Circuit breakers opening and closing automatically in runtime based on the

schedule entries.


Vijeo Citect Core Changes - SchedulerOverride and Normal mode

Equipment can be in normal or override mode:

• Normal Mode: Every schedule entry for the equipment will run. If no schedule entry exists for the equipment, it will resolve to its default state.

• Override Mode: When enabled, schedule entries belonging to that equipment are ignored. You can then manually execute 'state' changes on that equipment.


Use the Override Mode

Procedure● Open the Scheduler page again and right click equipment in the tree to

change the mode from Normal to Override● Once in Override mode manually change the state.● Check the changes in the graphic page

Results Expected● Circuit breakers opening and closing manually by setting the state of the

equipment in Override mode



● Installation and StruxureWare rebranding● VijeoCitect Core Changes ● PLS_Include Changes

● Graphic Objects● Template● Starter Projects

● Profile Editor ● One Line configuration● Historical Reports● Support contacts and Documentation● Key Points to Remember


PLS_Include ChangesPages

Several graphic pages have been included


PLS_Include ChangesSymbols, Genies, Cicode

• New Tab_Base library of symbols• New Genies PLS_XXX_mot_1 and PLS_XXX_mot_2 (XXX=ANSI or IEC) for

TeSys T devices.• New ATS genie.• Additional Genies in different libraries, i.e. horizontal commands.• Cicode files to support new features.


PLS_Include ChangesPLS_Style_1 Changes

• New Look and Feel

Showlogo() Cicode Function to change the customer Logo (93x93 canvas)


Starter ProjectsOverview

Two starter projects make it easy for you to control background color on graphics pages. They are: default/white and high contrast/dark gray


Starter ProjectsConfiguration

When creating a new project the option to select a Starter project will display:

Starter projects are located in the folder: ….\ProgramData\Schneider Electric\PowerSCADA Expert 7.30\Starter (windows 7)


Starter ProjectsPredefined Components

The two starter projects include some predefined components:


Starter ProjectsPredefined Components (Cont.)

Cluster and Advance One line device preconfigured:


Starter ProjectsPredefined Components (Cont.)

Cluster and Advance One line (AOL) I/O device preconfigured with related Equipment (includes the AOL user):



● Installation and StruxureWare rebranding● VijeoCitect Core Changes ● PLS_Include Changes● Profile Editor

● New Device Types and Tags● One Line configuration● Historical Reports● Alarm/Events Page Enhancements● Support contacts and Documentation● Key Points to Remember


Profile EditorNew Device Types and Wages Topics

The following device types are now integrated into PowerSCADA Expert:

• PM1200• Micrologic E• TeSys T

New WAGES topics added to the existing tag library in the Profile Editor



● Installation and StruxureWare rebranding● VijeoCitect Core Changes ● PLS_Include Changes● Profile Editor ● One Line configuration

● One line animation● zOL Device● One line configuration utility● Genie Configuration● Colouring

● Historical Reports● Support contacts and Documentation● Key Points to Remember


Advanced One-line ConfigurationOverview

The color changing functionality in genies is no longer managed by Cicode functions but by a separated process called AdvOneLine.exe that connects to the running project using the citect API (CTAPI).


Advanced One-line ConfigurationFeatures

State machine driven Single Line Diagram● Source or voltage level colour animation scheme

● Trace the power from source to load● Or, represent voltage levels

● No glitch page changes● Back-feed calculation and representation● Display of potential issues

● Communication loss● Unknown power source


Advanced One-line ConfigurationConfiguration Files


Advanced One-line ConfigurationStart and Stop the One-Lines

The user must add the PLS_StartAdvOneLine method to the IO Server startup Cicode for One Line Animation

To start and stop the AdvOneLine.exe process, call one of these Cicode Functions:

• Stop: PLS_StopAdvOneLine(STRING sIOServer="",STRING sCluster="")

• Start: PLS_StartAdvOneLine(STRING sIOServer="",STRING sCluster="")


Advanced One-line ConfigurationOne-Line Device zOL

To use one-line graphics, you must create a memory device named zOL. One-linegraphics use the zOL device to drive animation. You must have at least one zOLdevice per project.


Advanced One-line ConfigurationOne-Line Device zOL (Cont.)

By default, this device will support 100 sources, 1000 buses, 1000 meters, and 1000 breakers. You can modify this via the Profile Editor:


Modify the Maximum Number ofBusbars and Breakers

Procedure● Open Profile Editor and go to the setup projects tab.● Click Add/Edit and Add the PLS_Example project, add a any profile to save

the project.● Add MaxBreakers and MaxBuses to the project parameters tab with a

value of 2000. Save and export the project.● Using the Profile Wizard update the zOL device. Update or Delete and

then add again.

Results Expected● zOL device updated to support 2000 busbars and 2000 circuit breakers


Advanced One-line ConfigurationConfiguring Genies

In PowerSCADA Expert 7.30, colouring is based on the source and meter line activestates. Sources dictate the colours for each genie. Basic Genie Parameters must be configured when pasting a Genie on a Graphic page:

• Equipment Information

• Source Information

• Busbar Connections

• Display Information

• Etc.


Advanced One-line ConfigurationConfiguring Genies (Cont.)

The configuration of the Top Source and Bottom Source parameters of the transformer Genie control the type of coloring to be used in the One-lines:

Pass-through colouring: If you leave these fields blank

Voltage-level colouring: When you enter top and bottom source numbers


Advanced One-line ConfigurationCreating Custom Genies

There are two ways to create a new custom one-line genie:

• Copy a genie: copy an existing genie and change attributes. This new genie must

be added to the SupportedGenies.xml

• Create a unique genie: Use your own symbols or genies to create a new genie. Call the PLS_GetBusColorIndex(INT nColorIndex) function from the Fill (array) property of the symbol. The new genie must be added to the SupportedGenies.xml and GenieDefinitions.xml files.


Advanced One-line Configuration Configuration Utility

Use the Configuration Utility to review genie configurations before you compile a project. Then you can view errors and warnings, and repair and upgrade genies.


Advanced One-line Configuration Repairing One-lines

The configuration utility can perform repairs to your project one lines

• Repair option: Attempts to fix errors and warnings in a project (PSE v7.30)

• Repair option with Upgrade Project checked: Is used to upgrade projects from previous versions of the product. This option renumbers all genies in the project. (DO NOT use in PSE v7.30 project)


Advanced One-line Configuration Repairing One-lines

Use the one-line configuration utility to review genie configurations before you compile your project.

• You must correct errors; otherwise, you may not be able to compile and the animation will not work.

• You might not need to correct warnings, but you should review them to ensure that their settings are correct.


Advanced One-line Configuration Repairing One-lines (Cont.)

● Clicking the repair option will show a message that describes the

degree of repair that is about to take place.● The repair will not applied to the project graphic pages until you press

save.● A summary window will be displayed at the end of the process (this

summary can be saved to a CSV file).● It is possible that some errors and warnings will not be repaired, for

example, missing busbar numbers or missing equipment. Click

individual errors or warnings to view them


Advanced One-line Configuration Typical Errors in Genies

● Breaker numbers must be a number greater than 0 and unique.● Source busbar numbers must be a number greater than 0.● Destination busbar number must be a number greater than 0.● Source and Destination busbars must not be equal.● Equipment must be present.● Meter number must be a number greater than 0 and unique.● Either the Source or Destination Busbar number must exist (busbar

may link to a Busbar, transformer, meter, source, or another breaker)


Advanced One-line Configuration Typical Warnings in Genies

● Line Active should be present.● Busbars across all meters should be unique


Advanced One-line Configuration One-Line Colours

● In PowerSCADA Expert 7.30, colouring is

based on the source and meter line active

states.

● Sources dictate the colours for each genie.

● Meters can only determine if a bus is

active.

● When the bus is live, the meter then

colours based on the source that is

connected to the bus.

● If there is no source, the default colour is

used.


Advanced One-line Configuration One-Line Colours (Cont.)

● Unknown source Color

● Off Color

● Error Color

● Sources


Change the Colours in the One-line

Procedure● Open One-line Configuration Utility and go to the color configuration tab.● Change the colors of the sources, unknown source, off and error colors.● Save the changes and close the Utility

Results Expected● Different colors in the one-lines during runtime



● Installation and StruxureWare rebranding● VijeoCitect Core Changes ● PLS_Include Changes● Profile Editor ● One Line configuration● Historical Reports

● Reports Overview● Default Reports● Report Configuration

● Alarm/Events Page Enhancements● Support contacts and Documentation● Key Points to Remember


Historical ReportsOverview

The reporting feature is an IIS web application that provides 4 basic out of the box historical reports

● Historical information coming from Trend files

● Reports can be viewed in the runtime client or in a web browser


Historical Reports – Default ReportsSingle Device Usage Report

Use single device usage reports to display historical energy data from a single device and multiple topics. A single device report includes only usage and consumption topics.


Historical Reports – Default ReportsMulti Device Usage Report

Use multi device usage reports to display historical energy data for multiple devices and one topic. A multi device usage report includes only usage and consumption topics.


Historical Reports – Default ReportsTabular Report

Use tabular reports to display a system's historical data in a table format. Tabular reports can include one or more devices and one or more topics. A tabular report can include all available topics.


Historical Reports – Default ReportsTrend Report

Use trend reports to display a system's historical data in a trend (line) and table formats. Trend reports can include one or more devices and one or more topics. A trend report can include all available topics.


Historical Reports - ConfigurationReport Pages in the Runtime Client

● The PLS_Inlude project defines a PLS_ReportPage.

● PLS_ReportPage contains a Microsoft Web Browser ActiveX control in which the reporting web pages are displayed.

● New menu tabs must be configured in the project to use the function:

PLS_ReportDsp(STRING sIPAddress, STRING sName, STRING sOptions = "", STRING sTitle="")

Example: PLS_ReportDsp(“10.10.10.10", "SingleDeviceReport”, "", “Single Device Usage Report”);


Modify the Menu Configuration to Add new Pages for each Report

Procedure● Open the Menu Configuration form in the Project Editor and add the new

pages for each type of report using the function: PLS_ReportDsp(STRING sIPAddress, STRING sName, STRING sOptions = "", STRING sTitle="")

● Compile the project ● Run the project and se the new pages in runtime.

Results Expected● Report Pages created in the project.


Historical Reports - ConfigurationINI and CtAPI Parameters

● [Trend]MaxRequestLength : Max. number of samples per trend.

● [CtAPI]Remote = 1 Remote connections to the CtAPI

● [Reporting]PrivLevel - Default = 0

● [Reporting]Area - Default = 0

● Change the Modules.Platform.Citect.dll.config file:● IPAddress: Of the server hosting reporting ● UserName: To connect to CtAPI● Password: To Connect to CtAPI● Is Encrypted: Set to 1 if you change the password


Historical Reports - ConfigurationReports in a Web browser

You can create reports and save report configurations using a web browser (e.g., Internet Explorer).

You can generate reports in two ways:

● Run a new report by entering parameters

● Run a report from a saved configuration


Historical Reports - ConfigurationReports in a Web browser (Cont.)

There are two options (URL’s) to run a new report:

● Browse directly to the required report:

http://<ServerName>/Reporting/Report/<ReportName>

● Browse To the default reporting URL, and click the report you want to view:

http://<ServerName>/Reporting/


Generate a Trend Report in a Web Browser

Procedure● With your project running open a web browser (IE) and type the following

URL in the address bar:http://localhost/Reporting/Reporting/Report/TrendReport

● Login to the application using the credentials: demo/demo● Set the report input parameters and generate the report.

Results Expected● Report created in a web browser



You can run a report and save its configuration:

● Visit the “Build Configuration” URL:

http://<ServerName>/Reporting/Report/<ReportName>/BuildConfiguration

● Generate the report normally, when the report displays at the bottom of the page there will be a text box with XML code.

● Copy this code and save it to a file with the following format:

<ReportName>_<ConfigurationName>.cfg

● Save the file in the following location:

…Program Files\Schneider Electric\PowerSCADA Expert\PowerSCADAExpert Reporting\Reporting\ReportConfigurations\


Generate a Trend Report and Save the Configuration

Procedure● With your project running open a web browser (IE) and type the following URL

in the address bar:http://localhost/Reporting/Reporting/Report/TrendReport/BuildConfiguration

● Login to the application using the credentials: demo/demo● Set the report input parameters and generate the report.● Copy the XML format at the bottom of the report.● Save it as TrendReport_Configuration1.cfg under :

Program Files (x86)\Schneider Electric\PowerSCADA Expert\PowerSCADA Expert\Reporting\Reporting\ReportConfigurations\

Results Expected● Report Configuration saved



● To view a report with a saved configuration, browse to the URL of the report and specify the configuration. :

http://<ServerName>/Reporting/Report/<ReportName>/<ReportConfiguration>

● To view and modify a saved configuration use the Show configuration URL:

http://<ServerName>/Reporting/Report/<ReportName>/<ReportConfiguration>/ShowConfiguration

● After the report runs, a text box displays at the bottom of the finished report. It contains the new XML of your saved configuration.


Generate a Trend Report with a Saved Configuration

Procedure● With your project running open a web browser (IE) and type the following

URL in the address bar:http://localhost/Reporting/Reporting/Report/TrendReport/BuildConfiguration1

Results Expected● Report generated with a saved Configuration


Historical Reports - ConfigurationConfigure Email settings to send Reports

● In order to send reports to one or multiple email addresses some configuration needs to be done in the web.config file:

…Program Files\Schneider Electric\PowerSCADA Expert\PowerSCADA Expert Reporting\Reporting

● Locate the following text and replace the SMTP and the FROM email address:

<system.net> <mailSettings> <smtp deliveryMethod="Network" from="FROM_EMAIL_ADDRESS"> <network host="INSERT_SMTP_SERVER" port="25" defaultCredentials="true" /> </smtp> </mailSettings></system.net>


Historical Reports - ConfigurationConfigure Email settings to send Reports (Cont.)

● Email list: with your preferred text editor; enter one or more email addresses (one per line, no commas). Save it as:

Email_<EmailListName>.cfg

● Save the file in the …Reporting\ReportConfigurations\ directory.

● The email body that you send is contained in a resource (.resx) file intheReporting\bin\Resources\Reporting.en-US.resx\ directory,


Historical Reports - ConfigurationSend Reports Via Email

● There are three ways to send PowerSCADA Expert reports via email:

• The report Viewer email Button

• Visit a Specific URL

• Use Cicode via ReportMailer


Historical Reports - ConfigurationSend Reports Via Email (Cont.)

The Report Viewer Email Button: Use this method to send a customized one-time email to an individual or group of email addresses.



● Visit a specific URL: Each visit to a URL causes the email to be sent.

● Set the Timeout Value in the web.config file.

● To send a report to an existing email list, visit the following URL:

http://<ServerName>/Reporting/Report/<ReportName>/<ReportConfiguration>/Email/<EmailList>

● You must use a saved configuration.



● You can use a utility called ReportMailer to email reports. ● This command line utility is located in the PLS_Include project. It can be

called by Cicode.

● You can create a button on the graphics page and have it call the Cicode function or use a scheduled process to trigger an email. Example:

FUNCTION PLS_EmailReport() ErrSet(1); STRING FilePath = ParameterGet("CtEdit","User","") + "\PLS_ Include\ReportMailer.exe " + "MultiDeviceReport SampleConfiguration SampleList " + "^"C:\ProgramData\Schneider Electric\PowerSCADA Expert 7.30\User\PLS_Example^"";Exec(FilePath);END



● Installation and StruxureWare rebranding● VijeoCitect Core Changes ● PLS_Include Changes● Profile Editor ● One Line configuration● Historical Reports● Alarm/Events Page Enhancements● Support contacts and Documentation● Key Points to Remember


Technical Support

● If support or additional information about any concepts or products in the course is required, students should ask the Instructor who will either address the question or obtain additional technical assistance as required.

● Schneider Electric Technical Support can be reached from the website: http://www.schneider-electric.com

● Navigate to http://www.schneider-electric.com ● Select your country when prompted ● Select an option from the Support tab at the top of the page

Available contact information will be provided, based on the country selected.

http://www.schneider-electric.com/


Documentation

● Several important documents are provided with PSE v7.30 installation files:


Documentation

● Help files are also included with specific information for different tools:



● Installation and StruxureWare rebranding● VijeoCitect Core Changes ● PLS_Include Changes● Profile Editor ● One Line configuration● Historical Reports● Alarm/Events Page Enhancements● Support contacts and Documentation● Key Points to Remember


Key Points to Remember

… intentionally left blank

StruxureWare PowerSCADA Expert v7.30 Delta Technical Training

Documents

Transcript of StruxureWare PowerSCADA Expert v7.30 Delta Technical Training