wonderware conference. schneider electric...

Wonderware Conference. Schneider Electric confidential.

TSS-07: Simulating I/O & Introduction to Wonderware Operations Integration Servers

Presented by: Gary Alldredge and Dan Scott


Wonderware IO Simulation


Why Simulation is Valuable

●Project testing ●Verify scripted or dynamic IO references ●Graphics, scripting, alarm, and historization testing

●Demo applications ●Bring realism to the demo ●Allow the customer to interact with the system

●Problem replication ● IO is often needed to diagnose problems ●Closer replication of the customer’s environment


Methods to Simulate IO Values

●Modbus Simulators ●Mod_RSSim

●Wonderware DAS or OI Simulator

●OI.SIM ●DASSIM

●Simulation with App Server

●Scripting


Modbus Simulators

●Modbus Simulators (Mod_RSSim) ●Can simulate 65535 Coils, Digital Inputs, Analog Inputs, and Holding

registers ●Can be configured for multiple Server connections ●Port number can be configured (Default is 502) ●Can simulate device IDs 1 through 255


Modbus Simulators

●Useful for testing with the MBTCP Server. ●Setup when using Mod_RSSim

●Set the Maximum outstanding message in MBTCP server to 1. ●Change the # server connections in Mod_RSSim if MBTCP is configured for

more than 10 PLC or bridge objects. ● If Mod_RSSim and MBTCP are on the same node, start Mod_RSSim first.

Also make sure that unsolicited messages is not enabled in MBTCP.


Wonderware SIM Server

●Wonderware Simulation Server (DASSIM / OI.SIM) ●Can simulate any Device item name ●Can be configured to simulate Boolean, Integer, Float, String values ●Can Simulate Process Values and Setpoints



●Default item data types ●The first character of the item name determines the data type.

First Character Data Type Example i or I 32 bit integer iPumpRunHours b or B Boolean bPumpStart f or F 32 bit float fPumpSpeed d or D 64 bit float dPumpAmps s or S String sPumpName



●You can override the default syntax and/or define your specific item syntax by specifying the appropriate expression in the syntax definition file named TagSyntax.txt

●The TagSyntax.txt file also contains examples of the various definitions.


Wonderware SIM Server ●TagSyntax.txt file.

^[fF].* , VT_R4

Character Description ^ Look at the beginning of the string

[fF] Look for f or F .* Followed by any character(s)

Matches any string that starts with f or F. Assigns a 32 bit float data type Example: fTag1


^MB[0-9]+\.S7STRING.* , VT_BSTR

Character Description ^ Look at the beginning of the string

MB Look for MB

[0-9] Any number between 0 and 9

+ Preceding occurs one or more times

\ Escape

.S7STRING Look for .S7STRING

.* Followed by any character(s)

Matches string that begins with MB followed by numbers then .S7STRING followed by character(s). Assigns a string data type. Example: MB24.S7STRING48



Simulating Modbus Wonderware SIM Server


Simulating a PLC-5 Wonderware SIM Server


Wonderware SIM Server ●Process Simulation Item Syntax

● Each simulated process value is specified with a specific suffix. For each simulated process value there are 3 other suffixes which can be set dynamically in runtime: Suffix Description Default Example

/sim.pv Process value for the corresponding tag.

70.0 Tag1 /sim.pv

/sim.sp Setpoint for the associated process value

60.0 Tag1 /sim.sp

/sim.dev Maximum deviation the setpoint and process value can have.

6.0 Tag1 /sim.dev

/sim.noise Maximum amount of fluctuation the process value can have.

3.0 Tag1 /sim.noise



●Alternate Process Simulation Item Syntax Suffix Description Default Example

.pv Process value for the corresponding tag.

70.0 Tag1.pv

.sp Setpoint for the associated process value

60.0 Tag1.sp

.dev Maximum deviation the setpoint and process value can have.

6.0 Tag1.dev

.noise Maximum amount of fluctuation the process value can have.

3.0 Tag1.noise



DEMO


Simulation using App Server ●Creating Simulation Objects in App Server

●Use scripting to simulate values ●Process Values ●PID Loops with tuning parameters ●Discrete simulation using the sequencer object


Simulation using App Server


Simulation using App Server

DEMO


Wonderware Operations Integration (OI) Servers


Introduction to Wonderware OI Servers

●Wonderware Operations Integration Servers ●Next Generation of DAServer technology ●New Features

● Installation ●Operations Integration Server Manager ●Multi-Instance Support ●Multi-Version Support ● Licensing ●Documentation ●Product Download


OI Server Installation

● Installation is now broken into two parts: ●OI Core

●Supersedes DAS Runtime Components ●Installs all common OI Server components ●Installs OI Simulation Server (previously DASSIM) ●Prerequisite for OI Servers

●OI Servers ●Small file sizes ●Very fast install


Operations Integration Server Manager


Multi-Instance Support


Multi-Instance Support Benefits

●Leverage the enhanced computing power of computers ●Enhance maintainability, scalability and robustness

●Reduce application cost by increasing single node scalability ●Eliminate single point of failure ●Reduce downtime due to configuration changes ● Improve performance by leveraging parallel independent processing


Multi-Instance Support Details

●Configure device connectivity across multiple instances of an OI Server ●OI Server allows 1 to 100 instances of the server to run; each a

separate process ●Each instance has a unique ProgID (for OPC), and Application name

(for SuiteLink) ●OI Server Manager provides the utility to create and manage multiple

instances ●Management of OI Server instances can be done only locally ●Remote SMC continues to show all OI Servers in a flat hierarchy

●Licensing restrictions apply


Creating Multiple OI Server Instances

●Option #1: Right-click on OI Server -> Create Server Instance


Creating Multiple OI Server Instances

●Option 2: Right-click on OI Server instance -> Clone Instance


Multi-Instance Configuration Files

●New OI Server configuration files location per instance: ● C:\ProgramData\Wonderware\OI-Server\$Operations Integration Supervisory Servers$\<Driver Name>\<Instance

Name>\<Driver Name>.AAcfg


Moving Configuration Files

● Instance(s) with same name must first be created on new node, then copy the configuration files ● Limitation of ProgID creation and

other required registry keys and file folders


OI Servers with SuiteLink/DDE

●MBTCP OI Server (base instance): OI.MBTCP.1 ●DDE/SuiteLink client uses: MBTCP (this is a change from DAS naming) ●DDE is supported by the base instance only ●Unsolicited messaging is supported by the base instance only

●MBTCP OI Server instance : OI.MBTCP_P1.1 ●SuiteLink client uses: MBTCP_P1 ●MBTCP_P1 is the application name and must be <16 characters due to

SuiteLink limitation


OI Servers with OPC

●Each instance of OI Server follows this naming convention (ProgID) in the SMC: ●OI.<Instance name>.<version #>

●Examples: ●MBTCP OI Server (base instance): OI.MBTCP.1

●OPC client uses: OI.MBTCP or OI.MBTCP.1 ●Unsolicited messaging is supported by the base instance only

●MBTCP OI Server instance : OI.MBTCP_P1.1 ●OPC client uses: OI.MBTCP_P1 or OI.MBTCP_P1.1


Multi-Version Support

●DAServer and OI Server can co-exist and run at the same time ●DAServer is considered an instance of the same connectivity of the OI

Server and thus subject to licensing restriction of multi-instance ●DAServer shares

OI Core Components which are backwards compatible


Multi-Instance Processes

● Instance in Task Manager contains ProgID in Command Line column


Multi-Instance Logging

●SMC Log Flags per instance


OI Server License Types

●Standard License Features: ●Only 1 instance or version can run, similar to existing DAServer behavior ● License file feature name can be either DAServer or OI_Server v11.1+ ●Existing DAServer feature line is supported by OI Servers as a Standard

license for backwards compatibility and upgrades ●Professional License Features:

●Multi-Instance ●Multi-Version ● License file feature name is OI_Server ●Only available with v11.1+ licensing


OI Server Professional Licensing

●Vendor_String value differentiates the tiers of licensing for OI Servers: ●VENDOR_STRING=count:1 means Standard Licensing ●VENDOR_STRING=count:2 means Professional Licensing

●Duplicate Licenses are read from top to bottom, so Pro license must be

on the top ●When upgrading from Standard License to Professional License, both

SMC and the OI Server need to be restarted before the new license will take effect


Licensing Errors

●Configuration: License Error when Professional license is not available:

●Runtime: License Error when the OI Server instance is not starting:


OI Server Documentation Changes

●Changed User’s Guide title in SMC


OI Server Documentation Changes

● Installed OI Server documentation will focus on 3 main areas: ●Configuration ● Item Syntax ●Troubleshooting


Product Download/Living Documentation

●OI Core and OI Servers are distributed through the GCS software download site only

●The site will provide : ●Hyperlink to the downloadable msi file. You may have to “unblock” the msi

file after the download before you can run it. ●Readme file ●Supported firmware and hardware ●OS Compatibility

●The site will be updated to reflect the latest firmware, hardware, and Operating System support


What About DIObjects?

●OI Servers are only available as standalone servers at this time ●DIObjects will no longer be developed under their current design

●Dev is working on replacement deployable technology ● If you want to use OI Servers, you must use DDESuitelink or OPCClient

object for now


OI Servers Currently available Wonderware OI Servers (vG-1)

●ABCIP 6.0 (includes ControlLogix Firmware 26 support) ●MBTCP 4.0 ●GESRTP 3.0 ●Simulation OI Server 1.0 (automatically installed with OI Server Core) ●Melsec 10.4 ●CodeSys 2.6 ●OptoMMP 1.0 ●BACLite 3.6 ●TwinCat 1.16 ●Koyo 1.18

Wonderware Conference. Schneider Electric confidential. ©2015 Schneider Electric. All Rights Reserved. All trademarks are owned by Schneider Electric Industries SAS or its affiliated companies or their respective owners.

Thank you!

wonderware conference. schneider electric...

Documents