Lab 3 - Creating the Plant and Deployment Models 3-23 ‘The Deploy cialog box appears and displays the progress of the deployment. This may take a few moments. 27. When complete, the progress displays 100% comploted. 28. Click Close. You will now deploy the second platform. 29, Right-click AOSPlatformt and select Deploy. saBeniovment pales “Applicaton Server 20143-24 Application Infrastructure ‘The Deploy dialog box appears. Notice that itis sel to Cascade Deploy by default and that there are nine objects in totat that wil be deployed. This is because ADSPlatform1 hosts other objects, C epeyomayes Sale ot errant comes tated apache ‘ete pas ——— resis te F test ardince fall ta cote Sey ea 6 ats | rer epaed 30. Keep the default options and click OK. 31, When the progress shows 100% completed, click Close. edly conc [er ts a rea ate were. [rn advan sc) sarge ter edb om AOS [owl tsar) arg ns ASPs ety Guey.0 wen Cayce sen Trwensys Leeming SorcesSection 3—The Runtime Environment 3-25, Section 3 - The Runtime Environment ‘This section providas an explanation of the Runtime environment and the use of the Object ‘Viewer and Platform Manager to monitor it. Additionally, it explains attribute referencing and how 10 upload changas from the Runtime environment to the configuration database. Runtime Environment ‘The previous workilow task defined the deployment model that specifies where objects are deployed. In other words, the deployment model defines which nodes wil host the various ‘AulorationObjects. ‘The objects deployed on particular platforms and engines define the objects' system resources on. the platform. The load is based on the number of I/O points, the number of user-defined attributes (UDAs), and so on, The more complex the object, the higher the load required to run it. Attributes and Attribute References Every plece of configuration and data available within an objects called an attribute. Interaction vith objects, in configuration or runtime, is done through the attributes of the specific object. Attribute references refer to data within an object's attributes; it consists of an object's reference string plus an altrbute's reference string, separated by a dot (’."): ObjectName.AttributeName ‘An object referance cannot exceed 32 characters (including the $ character used in template names) and must contain at least one non-numeric character. You should avoid assigning objects and attributes the same names because this may result in an attribute reference can refer to two different things. For example, if you have two objects, At and B2, where At is the container of B2, and object A1 has an atiribule named 82, the reference string ‘A1.B2 could either refer to the B2 attribute within A1, or the B2 object contained in At. ‘opicaion Server 20143-26 Application Infrastructure Object Viewer ‘The Object Viewer is a diagnostic tool that monitors the stalus of the objects’ attributes and can be used to modify an attribute value for testing purposes. It is a common component and is available ‘rom any workstation that has a deployed platform. You do not need to install the utility on each workstation. Use Object Viewer to view the data type, dala quality, data vaiuo, time stamp, and the communication status of any application object attribute, In Application Server, the Object Viewer is used to monitor the Runlime environment. For example, ‘anode may be executing more objects than itcan easily handle, and it will be necessary to deploy ‘one or more objects to another computer. Object Viewer is used to view the activity in runtime. It displays the current value of object attributes. As object and object attribute values change (for example created, value change, configuration change), the changes are reflected in Runtime and monitored via the Object Viewer. a =e 8b Reccen [mw = Cae: see wp ae ae Ee Bold fea Somes] ef ee Eloeomaveonee] Sz 2 em P peiaancie) Sez 3 een ae 7 r ieee Tacha [anos anoee ps frexcy FE inetate re ‘To monitor values that are constanly updated as much as every second, he attribute can be added to a wach list, To add an attribute to the Object Viewer Watch list, right-click the attribute from the Delails pane and select Add to Watch. To modify an attribute, you can double-click it and the modify dialog box appears. This dialog will appear diferently depending on which type of attribute you are trying to modify, To facilitate the search of attributes, you can click on any of the ‘colurnn headings in the details pane to sort the data shown in either ascending or descending order. Thwensye Loaming SoracesSection 3—The Runtime Environment 3-27 Every readable attribute is assigned a quality property that matches one of four categories: [Description |[Datais good and ean be used ~ Dalai questonabo, but can bo used but wil be soon ‘The status of an Application Object's attribute describes whether a particular Read or Write succeeded or failed. Possible status conditions include: [Desevition ~~ Operation compstedaucsosstly : : Roquosl is ecevod, bus ol yt complete (a ranslony sais) Operon completed succassfuly, but win some wamvng conaion {eoples ony to Write ection) “ “Gamnmurication Ear Request aed duo to an err convmuricaing wih he target applzaton obect | Configuration Enor Reques faled due o an erorin configuration — ‘Operational Error | Request failed due to an op Sofware Eror Requested dv | Secunty ror Roque fed duo to neuen socurly access rahi | Other Enor TAother eros ‘You can save a list of items being monitored. Once you have a list of attributes in the Watch Window, you can save them to an XML file by right-clicking on the Watch window and selecting Save. A previously saved Watch window can also be loaded to monitor previously saved attributes. You can also add a second Watch window that shows as a separate tab in the bottom of the Viewer. To delete and item from the watch list, you can select the attribute and press Delate or ‘right-click the attribute and select Remove from Watch, ‘Adsitionally, you can search for an object by using the Find Object feature. To use this feature, on the Edit manu, select Find Object. “Aentcaton Server 20143-28 _ Application Infrastructure Platform Manager You can also start Object Viewer using the System Management Console (Start |All Programs. [Wonderware | System Management Console). In the console tree pane, expand the Platform Manager to show thelist of Galaxies, and then expand a Galaxy to show a list of platforms. Righl- ‘lk a platform, and select Launch Object Viewer. ac] Tivensys Learning SonvcesSection 3-The Runtime Environment also highiight a platform or engine and the Object Viewer icon becomes available. this icon makes the Object Viewer window appear. Uploading Runtime Configuration ‘You can upload runtime configuration changes to the Galaxy database. This lets you Keop any attribute values that changed during runtime. ‘The values of certain attributes can be set in the configuration environment, but they can also be changed by the user at runtime, As a result, the values of these attributes can differ between the runtime and configuration environments. For example, you create an object with an attribute named mylnteger. in the Object Editor, you ‘specify an intial value of 30. ‘Then you depley the object. At runtime, you writa a new value to mylnteger of 31. If you redeploy this object, the original value of 30 overwrites any value assigned during runtime. Ifyou want to upload runtime changes to the Galaxy, make sure the selacted objects are: ‘+ Notedited and checked in since last deployment or upload Not in Pending Update state © Checked in Objects whose configuration is successfully uploaded have a new version number and a change log entry for the upload operation. The runtime object's version number also has a new version ‘number. That version number matches the version in the configuration database. ‘Apolialion Server 20143-30 Application Infrastructure Ifyou select an abject that is currently checked out fo you, a waming appears during runtime upload. if you continue, you lose all configuration changes you made to the checked out object. ‘The Galaxy performs an Undo Check Out operation on it before the runtime attributes are copied to the Galaxy database. Note: You cannot upload runtime changes for objects checked out to other users. To upload runtime changes to the Galaxy: 4, Select one or more objects in the Model view or Deployment view. For example, you could select an entire hierarchy from AppEngine down, 2. Inthe Object menu, click Upload Runtime Changes. The runtime atributes of the selected objects are copied over those in the Galaxy database. ‘hist [Window Heb 9, neko seve etek ‘Upload Run CharaLab 4. Ising Object Viewer 3-31 Lab 4 — Using Object Viewer Introduction In this lab, you wil use the Object Viewer as a diagnostic too! to test your application objects and modify their atsibute values. You will then create, rename, and save walch lists and add atirbutes to the watch lists. Objectives Upon completion of this ab, you will be able to: ‘Open Object Viewer fram the ArchestrA IDE and the System Management Console (SMC) ‘Add attributes to a watchlist Create and rename a watch list Save a watch list ‘Aopication Server 20143-32 _ Application Infrastructure Open and Add Jn the following steps, runtime data. Items to Object Viewer you will open Object Viewer which is a diagnostic tool used to monitor 4. Inthe Deployment view, right-click AOSPlatformt and select View in Object Viewer. Note: Ifyou are performing this Iab using a single-node network configuration, you will use the GRPlatform for ths step. Tene eT 2 cuss |B tobe aS 8 ‘Notice thatthe con Trvenays Leaming Serices ed bore, woos seas Aaaaanesaprenaenemenmpag| i i 1sole tree is in top-left pane, the attributes of the selacted object in the top- Fight details pane, and the watch window in the bottom pane. To see updated runtime values, you wil now add attributes to the watch window.Lab 4 - Using Object Viewer ‘Note: Click the column heading to sort thelist based on the selected column. For instance, select Attribute Name to son the list based on the attribute names. Inthe console tree pane, ensure that AOSPlatformt Is selected, and then in the detalls pane, right-click on PlatformInfo and select Add to Watch. au} Topas Poster Aone ‘The attribute is added to the watch window. [ae ere oa [sate HSA CaeTHDTE.. isi TTEI,. Catal Ok ‘Appicaton Server 2014 3-333-34 Application Infrastructure Aliernatively, you can drag and drop atributes to add them to the waich window. 3. Inthe console tree pane, click GRPlatform and in the details pane, drag Platformlnfo to the watch window. 8 srucomss0s 35 Getaonteveen ig) oreo. Visine sR. Insp eae(m)i25.. isons sale. {roi inf 0 PU 3-9 vara Vea Sev van Sew Pak TTD 25) ar 2am Ug 3a, eel ta Seve 40 vere 5.1 See Pak 1 7.) ‘The Platforminfo attribute displays the processor and operating system information of the ‘computer where the platform is deployed to. 5. Add GR.TimeOfLastDeploy to the watch window, Gg 3, awh WiaSow AD some Scan GU 3 3a ona ata Sow 40 sean 33S Pack 1 0) Fuss hiatal ear ‘This attribute shows the date and time of the most recent object deployment in the Galaxy. “rversys Learning SorcosLab 4~Using Object Viewer 3-35 Rename the Watch List Inthe following steps, you wil rename the watch list ab to give a better description of the attributes, that were added. 6. Right-click in the empty space in the watch window and select Rename Tab. ‘The Rename Tab dialog box appears. 7. Inthe Tab Name field, enter Platforms. 8 Click OK. ‘The waich list tab now displays the new name. Teta) Gre(ng 7 oo Guo 3-9, rsh a Sve 20 wwe Teaver P| OD ish) comp amo GU 9 Asai tasot aa Seve 0 ven Asan Pac! Bu 7200) “Aopicaton Sarver 20143-36 Application Infrastructure Save the Watch Window ‘Saving your watch window will allow you to access the information at any time. 9. On the File menu, select Save Watch List As. a toa Wate ‘ve Wath it ‘Tho Save As dialog box appears. 40, Navigate to the C:\Training folder, and then in the: ‘My Watch Window.xml. le name field, enter Note: Adding the xm file extension is optional. This allows you to edit the fle with an XML_ editor. The Object Viewer does not require a fle extension. 7 Taig 3] -ace [iuba3-sopmghaActonCaniestt 13Va0252.. TertOoament (Sb cantgtng Sted ao et TextOoamant tap 5-craang an Avge eet TextOoaret lb s-HeeErepbowmeSupLit 12/9 835. TertDoanent Dincieetetcy SRY 205. Heh Bea 11. Click Save, 12, Close the Object Viewer. Trwersye Learing ServesLab 4-Using Object Viewer 3-37 Use the SMC Platform Manager to Open Object Viewer In the following steps, you will start the System Management Console (SMC) and use the Platform Manager feature (o open Object Viewer. 43, Start the SMC (Start | All Programs | Wonderware | System Management Console). 14, In the left pane, click Platform Manager. ‘The Gataxy is displayed in the right pane. 415, In the left pane, expand Platform Manager and select Galaxy_XX. Both platforms in the Galaxy are now displayed in the right pane. “Application Server 20143-38 _Application Infrastructure 416. In the right pane, right-click AOSPlatform’ and select Launch Object Viewer. Note: You can ako select AOSPlatformt in the right pane, and then on the toolbar, select Launch Object Viewer. The Object Viewer window reappears and displays the AOSPlatformt attributes and the areas it hosts. ora atgpas ma anspor Tionays Unarning SonscesLab 4-Using Object Viewer 3-39 Load the Saved Watch List In the following steps, you will load the Object Viewer watch list you saved earlier and observe Platform attributes. 117, Click in the blank area of the Walch List to change focus. 48. On the File menu, select Load Watch List. |e Eat Yew Options See seve Wotistaa. 19, Navigate to C:\Training, select My Watch Window.xml and click Open. Eons (ub Coniperg Amram ot HIRAPOO HPA TertOoamet 15 Davnoats [bn SobigPokcenCansht — IRIE Tectoanent Lub2t-confasrasoped Aiemett — YD1S3470 _ TectDoanes oe “Liubas-ceatrgan avenge chpc.at —14RIPOL34I0"TestOoasent “Thomann Liusba-tndrgzemteenasogite TRUE _TestDoanes| Ped ear RPO EASP Bi voe % corp Ca ramer NR a aE > Flename [aytincnvindowart | (Fie ca ‘The Platform attributes you added earlier are now visible again. Facsrestrns Aectcinke Wiel) Gore 7 2508 GRU 1-E, Meal Waa Sever A vere 6d Sev Pa 1 Dud TD. [Seiten aternih_aiedearen rast crv. @ ana, areata eve 42 vera Ses Ped 70) ‘Apotcation Server 20143-40 Application Infrastructure Add a New Watch List Multiple watch windows allow you to view attributes in organized groups. Each time you add s new watch lst, it creates a new tab af the bottom of the watch window. These tabs creale a simple way to switch between watch windows. 20. In the Object Viewer, right-click in any part of the empty space in the watch window and select ‘Add Watch Window. FE Cag Wa We Ber etter Trvensys Learning SoricesLab 4—Using Object Viewer 21. In the console tree pane, click AppEnginet, and then in the details pane, add the following attributes to the watch window and adjust the column sizes to view your data. © ScanState * ScanStateCmd © Scheduler.ScanPeriod 2B Sentence ab Ly apna Tas Tee oa Tee plage sors Tis TRG coed Ok ene sas Visalia Chitod ok emetic sorvect SO Visiwivivinvanat Choad Ok STATED pas Ameen [FRE Cian Wath Vd al ‘The ScanState attribute shows ifthe AppEnginet is on scan. The ScanStateCmd attribute allows y AppEnginet on or off scan. The Schaduler.ScanPeriod attribute is the period of time, in miliseconds, in which AppEnginet will run all of ts hosted objects. 22. Right-click the watch window and select Rename Tab. 23. In the Tab Name field, type AppEngine and cick OK. a [Een]! cess) ‘The watch list tab now displays the new name, FRE Cray ta Vine [Soe 24. On the File menu, click Save Watch List. 25. Minimize the Object Viewer and close the SMC window. “Appicaton Server 2078 3413-42 _Application Infrastructure Tivensys Learning SoricasSection 4~- Device Integration Products 3-43 Section 4 — Device Integration Products ‘This section provides an introduction to Device Integration Servers. It also provides an explanation of Device Integration Objacts, their communication protocols, and /]O addressing. ‘Adiscussion of the use of Advanced Communication Management Is also provided. Introduction ‘The server application provides the data and accepts requests from eny other application interested in is data. Requesting applications are called clients. Some applications such as InTouch and Microsoft Excel can simultaneously be both a client and a server. Dynamic Data Exchange (DDE) Dynamic Data Exchange (DDE) is a communication protocol developed by Microsoft to allow applicalons in the Windows environment to sendireceive data and instructions tolrom each other iLimplemants 2 cfent-server relationship between two concurrently running applications. Note: NelODE, an older protocol previously used for communication over the network 1o| ‘Wonderware and non-Wondenvare sources, Is strongly discouraged and has been phased out by Microsof. SuiteLink is the recommended communication protocol for use with Wonderware sources. Wonderware SuiteLink ‘Wonderware SuiteLink uses a TCP/P-based protocol. SuiteLink is designed specifically to meet industrial needs, such as data integrity, high-throughput, and easier diagnostics. This protocol standard is supported for Windows 2000, Windows 2003 Server, and Windows XP. SuiteLink is Not a Replacement for DDE. Wonderware recommends that DDE be used for intemal client communication, and SuiteLink for communication over the network. Each connection between a client and a server depends on your network situation. “Application Server 20143-44 _ Application Infrs ucture SuileLink provides the following benefits: Consistent high daa volumes can be maintained between applications, regardless of whether the applications are on a single node or distributed over @ large node count. ‘Value Time Quality (VT) places a lime stamp and quality indicator on all data values delivered to VIQ-aware clients. Extensive diagnostics of the data throughput, server loading, computer resource ‘consumption, and network transport are made accessible through the Microsoft Windows NT@ operating system performance monitor. This feature is critical for the scheme and maintenance of distributed industrial networks. The network transport protocol s 1GPiIP using Microsofts standard Winsock interface. To Use the SuiteLink Communication Protocol, the following conditions must be satisfied: ‘© You must have Microsoft TCP/IP configured and working property. ‘+ You must use computer names (Node Names) of no more than 15 characters. For ‘more information on instaling and configuring Microsoft TCP/IP, see your Microsoft Windows operating system's documentation. ‘+ Wonderware SuiteLink must be running as a service. Iffor some reason SuiteLink has been stopped, you will need to start it again. (SuiteLink is automaticaly installed as a Common Component when you install InTouch. Itis configured to startup automatically as a Windows Service). DDE and SuiteLink I/O Addressing DDE and SuiteLnk identifies an element of data in an /O data source program by using a three- part naming convention that includes the application name, topic name and item name. To obtain data from another application, the client program opens a communication channel to the server program by specifying these three items. Additionally if tho communication channel is between applications running in different computers, a node name must be specified too. Node: Name of the computer the I/O data source program or service is running on. Application: Name of the source program or service that provides V/O dala to the client application. This is the name of the executable file without the extension. ‘Topic: I's an application-specific sub-group of data elements. tam: Name of the actual individual data point o be access once the communication channel is opened. For example, in the case of Excel as a server program, the application name is “Excel the topic ame is the name ofthe specific spreadsheet that contains the data and the item name is the Identification of the cell on the spreadsheet toffram which the data is to be readiwriten. “rensys Learning ServicesSection 4 — Device Integration Products oPc ‘OPCs open connectivity in industrial automation and the enterprise systems that support industry. Interoperability fs assured through the creation and maintenance of open standards specifications. “The first standard (originally called simply the OPC Specification and now called the Dala Access Specification) resulted from the collaboration of a number of leading worldwide automation suppliers working in cooperation wih MicrosoR. Originally based on Microsoft's OLE COM (component object model) and DCOM (distributed component object model) technologies, the specification defined a standard set of objects, interfaces and methods for use in process control ‘and manufacturing automation applications (o facilate interoperability. The COM/DCOM technologies provided the framework for software products to be developed. There are now hundreds of OPC Data Access servers and clients, ‘A typical analogy for needing the original Data Access Specification is printer drivers in DOS and then in Windows. Under 00S the developer of each application had to also write a printer diver for every printer. So AuloCAD wrote the AuloCAD application end the printer drivers. And WordPerfect wrote the WordPerfect application and the printer drivers. They had to write a separate printer driver for every printer they wanted to support: one for an Epson FX-80 and one. for the H-P LaserJet, and on and on. in the industrial automation world, one industrial device manufacturer wrote their Human Machine Interface (HM!) software and a proprietary driver to each Industral devies (including every PLC brand). Another industrial device manufacturer wrote their HMI and a propritary driver to each industrial device (including every PLC brand, not just their own). Windows solved the printer driver problem by incorporating printer support into the operating ‘system. Now one printer driver served all the applications! And these were printer drivers thatthe printer manufacturer wrote (not the application developer). Windows provided the infrastructure to allow the industrial device driver's solution as well. Adding the OPC specification to Microsoft's ‘OLE technology in Windows allowed standardization. Now the industrial devices' manufacturers, could write the OPC DA Servers and the software (ike HMIs) could become OPC Clients, ‘The resuling solsh benefit tothe software suppliers was the ably to reduce their expenditures for connectivity and focus them on the core features ofthe software. For the users, tha benelit was flexibly. They could now choose software suppliers based on features instead of ‘Do they have the driver to my unique device?" They don't have to create a custom interface that they musl bear the full cost of creating and upgrading through operating system or device vendor changes. Users were also assured of better quality connectivity as the OPC DA Specification coifed the Connection mechanism and compliance testing. OPC interface products are bul once and reused many times; hence, they undergo conlinuous qualily contol and improvement. The users project cycle is shorter using standardized software components, And their cost is, lower. These benefits are real and tangible. Because the OPC standards are based in tum upon computer industry standards, technical reliability is assured. ‘The original specification standardized the acquisiio of process data. I was quicky realized that communicating other types of data could benef from standardization. Standards for Alarms & Events, Historical Data, and Batch data were launched. “Applicaton Server 2014 3-453-46 Application Infrastructure Below is the comparison of the protocols, where VTQ stands for Value, Time, Qualiy, yy Node Name of the computer wherethe server applicationis running. 4 | Application Name ofthe server application executable. Topic Name of the topic in the server application from which to receive data. Name of the computer where the OPC Serveris running. pe Node ig§ Server Name ofthe OPC Server. Scan Group Name ofthe scan groupin the OPC Server from whichto receive data, eee af a eee Message Exchange Message Exchange (MX) is a proprietary protacol used by Apalicalion Server for object fo objct communications. I includes Local Message Exchange (LMX) for communication between objects {nd Network Message Exchange (NM) for communication between Galaxy nodes. NMK runs when WinPltiorms ee deployed Invensys Leaming SonicosSection 4 - Device Integration Products Device Integration Objects A Davice Integration object (DIObjects) is an Automation Object that represents communication with extemal devices. DlObjects run on an AppEngine, and include DiNetwork Objects and DiDevice Objects. A DiDevice Object is a representation of an actual external device (for example, ‘a PLC or RTU) that is associated with a DiNetwork Object. A DiNetwork Objects a representation ‘fa physical connection to a DiDevice Object via the Data Access Server, Device Field Device Driver Legacy InTouch Node DDESuiteLinkClient ‘The DDESulteLinkClient object is @ key member of the core set of AulomationObjects within the ArchestrA system infrastructure, The DDESuiteLinkClient object is a Devicelntegration object that ‘allows access to a running 10 Server. A DDE or SuileLink V/O Server can provide data points to Galaxy application objects through the DDESulteLinkClient object. Note: The DDESuiteLinkClient object is compatible with all Wonderware VO Servers and ‘components. ‘There is a one-to-one relationship between an instance of the DDESuileLinkClient object and a running /O Server. If you want fo reference data points in more than one l/O Server, you must ‘configure and deplay more than one DDESuileLinkCiient object. For example, you would need to configure one DDESuiteLinkClient object fo communicate to an TCP UO Server and another one to talk to the GEHCS N10 Server. When you configure the DDESuiteLinkCtient object, you can specify one or more I/O Server topics to which access is required. At runtime, all tems that the Galaxy application requires for 2 ‘specified topic are updated with the latest values ftom the UO Server. The rate at which the valves ‘are updated depends on how the topics were configured within the target VO Server. Ifyou want to connect to @ DDE M10 Server, specify login information that the DDESuiteL inkClient object uses to connect to the 10 Server. ‘Aopication Server 20143-48 Application Infrastructure From other objects and from scripts, you can reference the topics you configured for the ‘DDESuiteLinkClient object. For example, you might configure the input source for a FieldRoference object to reference an item for one of the topics. Thus, the FieldReference object Input source is receiving data from an lO Server through the DDESuiteLinkClient object. ‘To aid in rapid application development, you can create a list of topic items that appear in the Arciesité Attibule Browser. To do this, specify the item address and associate it with a user- defined attribute name (alias). Creating the item list is not required in order to reference data from the 110 Server. The reference syntax for a DDESuilteLinkClient object data point is: .. oR ‘.. ‘The is the name that you choose fo give to the DDESuiteLinkCtient object. Each WO topic for a DDESuiteL inkClient object is also known as a “scan group.” Runtime object ‘attributes allow you to monitor errors related to the data quality for item values in a scan group. InTouchProxy ‘The InTouchProxy Object is @ gateway between Galaxy application objects and data that is avalable through a stand-alone InTouch application. The InTouchProxy object allows you to browse a selected InTouch application tagname dictionary, add selectec tags as attributes in the Galaxy application, then read these attributes from the inTouch application at runtime. The InTeuchProxy object is a Devicelntegration object thal represents a running InTouch node. The InTeuch node effectively serves as the data provider (supporting the SueLink communication protocol) by providing data points to Gelexy application objects through the InTouchProxy object. Nota: Before using the tagname browser to browse for tags, make sure that InTouch ‘WindowMakor is not running on the InTouch node. WindowViewer, however, can be running. Also, bo sure that you have given share permission of Read to the InTouch foder that contains the Tagname.X file. ‘The InTouchProxy object is a key member of the core set of AutomationObjects within the ArchestrA system infrastructure. Note: This objectis compatible with InTouch v7.11 and later applications. ‘There Is @ one-to-one relationship between an instance of the InTouchProxy object and a running InTouch node. An InTouch “node” is a unique combination of the computer name and InTouch apptcation. If you want to reference data poins in more than one InTouch node, you must ‘configure and dopioy mare than one InTouchProxy object. For examplo, you would need to configure one InTouchProxy object to get data from an InTouch application running on Computer {nd anether one to get dala from an InTouch application running on Computer2. ‘When you configure the InTouchProxy object, you might want to specify one or more existing InTouch tagnames (items) to use as object attributes. At runtime, ifthese attributes are added in the client (for example, the Object Viewer watch window), they are updated with the latest values from the InTouch items. InTouch sends a new data value for an item to the InTouchProxy object ‘each time the value changes. Any items that you configure for an InTouchProxy object, automatically becomes available within the ArchestrA Attribute Browser. Tver Learning SenicosSection 4— Device Integration Products 3-49 From other objects and from scripts, you can reference the attributes you created for InTouch items. For example, you might configure the input source for a FisldReference object to reference ‘one of these InTouchProxy object attributes. Thus, the FialdReference object’ input source would bbe receiving data from a lag in an InTouch node through the InTouchProxy object. The reference ‘syntax for an InTouchProxy object data point is: . ‘The is the name that you choose to give to the InTouchProxy object. ‘The group of specified InTouch items for an InTouchProxy object is also known as the "scan ‘group,” Only one scan group exists in the InTouchProxy object. Runtime object attributes within the scan group allow you to monitor errors related to the dala quality for InTouch item values in a ‘scan group. OPCClient ‘The OPCClient object is a key member of the core set of AutomationObjects within the ArchesirA, system infrastructure, The OPCClient object is a Devicelntegration (D1) object that allows access to a running OPC Data Access (DA) Server. A third-party OPC DA Server can provide data points {0 Galaxy application objects through the OPCCiient object. Note: The OPCClient object is compalible with all OPC Servers that are compliant with OPC Data Access v2.05 or later standards. ‘There is a one-lo-one relationship between an instance of the OPCClient object and a running OPC DA Server. If you want to reference data points in more than one OPC DA Server, you must ‘configure and deplay more than one OPCClient object. For example, you would need to configure ‘one OPCCtient object to communicate to an TCP OPC Server and another one to talk to the CIP OPG Server. ‘An OPCClient abject supports the following operations on VO points for the OPC DA Server: '¢ Subscriptions, which are implemented via scan groups. ‘© Read transactions, which are implemented via block reads. '* Write transactions, which are implemented via block writes. Note: Ifyou are using this object to communicate with an OPC DA Server, you must properly configure the OPC DA Server before deploying this object. Time and Quality Propagation ‘When a dynamic attribute is poked, the time stamp is updated to the timestamp passed in with the valve ff available, or he current time provided by the hosting AppEngine is used. If the data provider passes in a Value, Time, Quality (VTQ) triplet of dala in the callback, the time stamp is associated with the value and quality used to update the altribute. ‘Application Server 2014Scan Mode ‘The scanning mode forthe scan group, either ActiveOnDemanc, Active, or ActveAll. For the ‘AcliveOnDemand mode, altibutes thal are not actively being referenced by any client or object {are not scanned. For the Active mode, an atibute is always in he active scanning state. When the last reference tothe abut is unregistered (unadvised), the altibute is deleted. For ActveAN, an altibule is aways inthe active scanning sate, but when the last reference to the allibute is Unregistered (unadvised, the atribute isnot deleted. To enable Advanced Communication Management, you mu + Select Advanced Communication Management for your Galaxy. Set the scan mode for each scan group that belongs to your device integration objects within the Galaxy. Advanced Communications Management ‘Advanced Communications Management minimizes network trafic and CPU usage of aD! Object ‘and DAServer when a particular DI attribute is currently subscribed to, butts value is not currently ‘shown. For example, scanning for updated values from a DI attrbute representing pump RPM is suspended when an operator minimizes the application window containing a pump graphic, containing attribute references that subscribe to the DI Object’s pump RPM altnbutes. Note: This dependence on the attribute being referenced by a running application is only the case ‘when the attribute subscription is not already active due to configuration for history, alarming, or scripting. For example, if an altbute is configured for history, the subscription to the field device will always be active regardless of what window is active in InTouch, and regardless of whether InTouch is running at all. Mirage pogictenaineeg —_ Infoxh Weebwiover Rung Ghanieelenten Sve tee Wovdaslen clare Peacatin Pedcnevomat | ‘aay Poms deke ea oy! otc basa) = Cuect j | | | WerteSection 4 — Device Integration Products WO Server Different #0 data sources have different requirements. Twa main groups are identified ‘© Legacy WO Server applications (SuiteLink, DDE, and OPC Servers) do not require @ platform on the node on which they run. They can reside on either a standalone or workstation node. However, the D Objects used fo communicate with those data sources such as the DDESuiteLinkClient object, OPCCiient object, and inTouchProxy objects must bbe deployed to an AppEngine on a Platform. Although itis not required that these DI ‘Objects be installed on the same node as the data server(s) they communicate with, itis highly recommended in order to optimize communication throughput. ‘* For Device Integration objects like CIP and TCP DINetwork objects, both the DAServer ‘and the corresponding DI Objects must reside on the same computer hosting an AppEngine. VO Servers can run on Workstations, provided the requirements for visualization processing, data processing, and VO read-writes can be easily handled by the computer. Run the /O Server and the corresponding DI Object on the same node where most or al ofthe object instances (that ‘obtain data from that Ol Object) ere deployed. ‘This implementation expedites the dala transfer between the two components (the I/O Server and the object instance), since they both reside on the same node. This implementation also minimizes ‘network trafic and increases reliability. However, itis good practice to evaluate the overhead necessary to run each Data Access Server (DA Server) DAServers, are designed to provide simultaneous connectivity between plant floor devices and modem DDE, SuiteLink and/or OPC based client applications. DAServers support the OPC Data ‘Access 2.08 specification and offer additional features beyond the standard, including powerful diagnostics and remote configuration capabilites. They offer enhanced communication diagnostics and performance. Each DAServer is designed to provide simultaneous connectivity between cient applications based on Wonderware SulleLink, OPC and DDE protocols that run on Microsoft's Windows® ‘operating systems and the data devices supported by the speciic protocol being translated. Several standard features are available with each DA Server, including: © Compliance with OPC version 2.05 Stand-alone operation mode ‘© Support for hot configuration, device additions and device- and server-specific parameter modifications © Awide range of DA ‘Servers support connectivity to numerous protocols and products. Wonderware's current DA ‘Servers offering also includes support for: ‘© Allen-Bradley’s CIP protocol for ControlLogix Allen-Bradley’s TCP protocol ‘Allen Bradley's OH Plus protocol ‘Siemens’ Simatic Net S7 ‘Modbus® Serial protocol “Applicaton Sorvr 2014 3-51‘The DAServer's lke a driver: itcan receive data from different controllers simultaneously. For ‘example, a DAServer might use OPC to access data remotely in one machine, and use InTouch to ‘communicate with another machine. When a DAServer transfers data, It also transfers a timestamp and quality codes. ‘The DAServeris flexible enough to be used in a variety of topologies, but some topologies are more efficient than others. For example, the DAServer can connect to the OPC Server directly across the network, or FactorySuite Gateway can be placed on the same machine as the OPC DAServer and SuiteLink ‘can be used fo link the server to devices. Of the two topologies, using FactorySuite Gateway is. ‘more efficient than connecting the DAServer cireclly to the OPC Server. OPC DAServer technology also has drawbacks; for instance, data may be lost briefly without the user realizing the loss has occurred. Tvensys Learring SoresLab § — Connecting tothe Id 3-53 Lab 5 — Connecting to the Field Introduction In this Iab, you will configure an instance of the SaDDESuitaL inkCtient template to connect to a data source using the SuiteLink protocol. You will hen use Object Viewer to monitor the ‘connection status ofthe instance in runtime. Objectives Upon completion of this lab, you will be able to: ‘© Configure a device integration object 5 ‘+ Monitor the connection status of a device integration object ‘Applicaton Server 2014ae © 3-54 Application Infrastructure fe] Create a Connection to a Field Device 1 Instance of the $gDDESuiteL inkClient template and lator. In the foliowing steps, you wil cre ‘configure it to connect to the PLC 1. Inthe ArchestrA IDE, Template Toolbox, Training\Global toolset, rightclick ‘$9DDESuiteLinkClient and select New | Instance. eoo000o00o0c¢ O° »© OO Coacooo00000n0 oo0000°0 IO00C “rvensys Leaning Sonces Oooo0000 oLab 5—Connecting tothe Field 3-55 3. Double-click PLCSim to open its configuration editor. 4, On the General tab, configure the instance as follows: Instructor wil provide RTEngine = ‘Communication Protocol: | SuileLink (default) TD Acan é |e |e oman | sue | xr | es] S sere ed c ‘sever oe: ee oct serene este cc e cewresapteat: faa 5. Atthe top of the PLESim configuration editor, click the Topic tab. ° @ aca ‘ coe 155 Jin atin sot |e [era] ts] 6. Inthe Available topics section, click the ScanGroupList [1 button to add a topic. 7. Inthe Tople feld, enter Tagname and press Enter. ace ares rot te [cts] tere 8. Inthe Associated attributes for Tagname section, click the Import (Tagnamé button. : -@aae | patioes & Smrneme’ DASHTEE ‘Appicaion Server 20143-56 Application Infrastructure ‘The Open dialog box appears. 9. Navigate to the C:\Training folder, select the PLC tems List.csv file, ‘tune [itiemizey =] [eeprom =] 10. Click Open. “nvenays Leaning Soncos Open cnai_|Lab 5 - Connecting to the Field Aller a few seconds, the Associated attributes for Tagname section is populated with al of the items in the fle. ‘The Attribute column displays the aliases assigned to each of the corresponding Item Reference data points. 11, Glick the Save and Close button to close the editor, ‘The Check In dialog box appears. 12. Inthe Comment field, enter Basic Configuration. tee Cataaiat bm woneta Gnckinaneers ee, ta ————— cn ane tans rent bad ram eration 13. Click OK. “Applction Server 2014 3.57Application Infrastructure 14. In the Model view, assign the PLESim instance to the ControlSystem area AppEnginet. 16. Right-click on PLESim and select Deploy. TTR wpsad anne eas son. seein ces foot Ob ont ecb! ase Trwensye Laorring Sores17, Keep the default options and click OK. 18. Fete When the Deploy progress displays 100% completed, click Close. ‘esc aeraindaion lati cet vou. lcci eter ces bey deere ftnere oe ede: (rn nt Vakning ea aaron can ested am AOS lca Oumar cht) stra ren cases by scan). ett ete oncom aa al an heed Seta Connecting to the Field ‘Application Server 2074 3-593-60 _ Application Infrastructure View the Attributes in Runtime ‘You will now return to Object Viewer to view the attribute valves in runtime, 19. In the Deployment view, right-click PLESim and select View in Object Viewer. The Object Viewer window appears and refreshes. 20. Right-click on an empty area of the watch window and select Add Watch Window. 21. Right-click on the watch window and select Rename Tab. 22, Rename the tab PLCSim and click OK. eben:Lab 5 - Connecting to the Field 23, From the Attribute Name list, add the following attributes to the watch window: © ConnectionStatus Reconnect ‘ScanState ‘ScanStateCmd spose aoe Iiishors oasis ore isis innova Yusposs asano14e FOC Waray Wath Wencal USasbeladtne ‘The ConnectionStatus attribute displays the communication status between the topics Configured in the device integration object and the topics in the Device integration Server. ‘The Reconnect attribute, when set to tru, wil ttempt to reconnect tothe Device Integration Server, ‘Acocaion Server 2014 3-613-62 Application Infrastructure 24, Add the SeanGroupList attribute to the watch window. ‘The Array for PLSIm.ATTRIBUTE(ScanGroupList) dialog box appears. This appears because ScanGroupList is an array and requires an index to be entered. ‘You will now configure the array to display the entire array dimension. 2, In the Enter an array index field, enter +. 28. Click OK. The ScanGroupList is now displayed in the watch window. ‘YIM TSSOP CEcced OF Uigeuisessorm cieed oe iishowicssemm Coceed Ge e Wishaw inssssosse Coded Mispouinassaoser Coded 27. Right-click on the watch window and select Save. Testy Tiwensys Learing SericosIODODEOGCHDHOAAODONGDODGNNDD >909009000000000000990000 invensss Learning Services Module 4 — Application Objects Section 1 - The $UserDefined Object 43 Lab 6 - Modeling the Mixer aT Section 2 - Change Control and Propagation 4.27 Lab 7 - Configuring Change Control and Propagation 431 Section 3 - The $DiscreteDevice Object 4.39 Lab 8 ~ Modeling a Valve and a Motor 445 Section 4 - Containment 4-53 Lab 9 - Creating the Mixer 4-574-2 _Application Objects Module Objectives ‘© Explain and configure discrete Field Attributes in a $UserDefined object, © Describe propagation of changed templates to derived objects Explain and configure a SDiscreteDevice object, '* Explain and configure a containment relationship between objects Trwenays Learing SormoesSection 1—The $UserDefined Object 4-3, Section 1 - The $UserDefined Object ‘This section explains the $UserDefined object and Field Attributes. $UserDefined Object ‘The UserDefined object provides the basic functionally you need to develop an ArchestrA supervisory application. The UserDefined object provices this functionality as Field Attributes (FAs), scripts, User Defined Attributes (UDAS), and attribute extensions. In the following image there is a eld device. In this example, you can acquire either Boolean or Analog values from the field device: ‘* For the Boolean values, there are a couple of attributes where we save the input source ‘and the input value. The input source will save the WO address of thal data point and the input value will save the actual value. The object saves the data to a discrete field attribute. '* For Analog values, we also have a couple of atibutes related; one that saves the /O ‘address, which is the input source and one that saves the value, which is the input value. Since these are analog values, they can be scaled and saved in an analog field attrbute. Scaling needs to be configured with the Engineering Units Maximum and Minimum and the Raw Values Maximum and Minimum. | AnalogFA.Rawrtin [AnalogFa.Rawntax ‘AnalogFA | -__DiscreteFA. Input. Value Invert Lipase) alo. Note: The InpulOut direction in Application Server is opposite ofthat in the PLC. In Application Server, plant data comes “in” and settings go ‘out to the PLC. “Application Server 201444 Application Objects ‘You can configure Field Attributes as an Analog or Discrete type with one of the following access modes: ‘© Input: The Field Attribute only accepts input. The Field Attribute is updated based on the value that is read from the configured input address. InputOutput: The Field Attribute accepls input and sends ouiput. The output destination can optionally differ from the input source address. The InpulOutput mode supports the User writeable and Object writeable attribute categories. '* Output: The Field Attibute only sends output. The Field Attribute writes to the specified 9g ‘output destination. The Output mode supports the following catagories: © Calculated ‘© Calculated retentive v © User writeable © Object writeable Note: We recommend you do not extend the Field Atirbute value with an Input, InputOutput, or ‘Oulput extension. Ifthe value is extended, unstable behavior with the Field Attrbute value will occur ‘The Analog Field Attribute supports the following dala types: © = Integer © Float © Double ‘The Analog Field Attribute provides the enabling and configuration forthe following functionality: © Scaling of Input and Output values ~ History O HIHi Hi, Lo and LoLo Limit Alarms Rate of Change Alarms ‘Target Deviation Alarms Bad Value Alarm + Slatistics ‘The Discrete Field Attribute provides the enabling and configuration fr the following 2 functionality: State Labels History Slate Alarm : Bad Value Alarm Siatistcs “The UserDefined object isan object that you can use to create custor the UserDefined object as a template, or as @ container. ized objects. You can use Tenaya Learning Sorces|Soction 1 - The $UserDefined Object Asa template Use the UserDefined object as a template containing Field Attnbutes associated to multiple variables in a system. In this case, the object provides a simple and manageable stucture as all the variables are coalained in the seme object. For example, you might create a UserDefined object called “Tank” and configure Feld Attibules that represent variables associated to the tank system: 7100 - Analog Field Attribute - Input from a level transmitter configured with options such 2: Scaling, Limit alarms and Statistics (Min/MawAvg). ‘TT100 - Analog Field Attribute - Input from a temperature transmitter configured with options such as Rate of Change alarm and Statistics (Min/Max/Avg). 'SW100a - Discrete Field Attribute - Input from a limit switch configured with options such as State Labels and Slate alarm. 'SW100b - Discrete Field Attribute - Input from a limit switch configured with options such 2a Stale Labels and State alarm. XV100a- Discrete Field Attribute - InputOutput to a solenoid valve configured with options such as State Labels, Stale alarm, and Statistics (Open/Close time), XV100b - Discrete Field Attribute - InputOutput toa solenoid valve configured with options such as Stale Labels, State alarm, Statistics (Open/Close time). Asa “container” Use the UserDefined object as a "container" for other objects. An object relationship in which one object is comprised of other objects is called containment. Containment allows you to group various objects together to make complex objects. For more details, refer lo Module 4, Section 4 fon the subject of Containment. “Aoplcation Server 2014 454.6 Application Objects Trwensys Learing SenizesLab 6-Modeling the Mixer 4-7 Lab 6 — Modeling the Mixer Introduction {In this lab, you will configure analog and discrote field attributes in a $UserDefined object to model ‘a mixer device. You will also use the Galaxy Browser to find attributes and bulld references. You ‘wil use the PLCSim object created in the previous Iab to provide the connection to the ive values ‘within the mixer. Objectives Upon completion of this iab, you willbe able to: ‘© Configure analog and discrete field attributes in a $UserDefined object, ‘© Select and assign attribute references using the Galaxy Browser ‘Aoplication Server 201448 Application Objects Create the Tank Template {nthe following steps, you will create the tank template. 4. Inthe ArchestrA IDE Template Toolbox, expand the Application toolset. (Wreplate woobae rae =p sent BBspooesen keno © Espira 120 steegoene [£0 soot 50 OuceDeee 129 sone 5g eieteence $40 wren 10 sheer Tnvensys Leeming Senicoe oocoot oooo00e oo0o00g O CODDDOCOCTOVGOCOCVDNVONDOO OOOO> > Lab 6—Modeling the Mixer 4.9 3, Rename the derived template $Tank. ‘@Wrenplate toolbox ar 29 soiscetdevie eg speable 159 sPeleReterece sox ° 1 Hseneleed 4. Drag the $Tank tomplate to the Training\Project toolset. (Wrenplate ootbax +e Tg geaslepDever 5g s200kn 159 doiseetevee #9 sone 0 shetkefwence £9 sort 0 scene 40 sseaueser | [89 ssuone | Eto esting b f0 ssxnd beg aurea Ep rateg 2 Gicibt 3 elPoe “ao 5. Double-click the $Tank template to open its configuration editor. 6. On the Field Attributes tab, click the Add Analog [4] button to add a new analog field altibute. Inthe Name field, rename the field attribute LT.PV and press Enter. © Fant ties [tes Wan] Soo | ie | ewes | a 2 - eo =e oaate: [rom ela scssoaie: Tresor =I a cog [ine wetnaie evtees G orton | “Application Server 2014410 _Application Objects 5 7. Click on the Add Analog press Enter. button again and rename the new field attribute TL.PV and Oo @ $tank~ Ft tates [cope tomate | Se | ois | er | aces | ano ‘Tho Field attributes list displays both attributes. 8. Click the LT.PV field attribute and configure the attributes as follows: (Leave all other attributes as defaut,) Input Float Engineering units: Gallons Enable UO scaling checked Raw value: Maximum 4095.0 EU range value: Minimum — -5.0 EU range value: Maximum 105.0 Frank o Feiss [oo verti | sos | as | ent | te (avs| +15] ne | Rte a ttn seessom [ie =] tare: Fa) Tnvensys Learning Senicos9. Click the TT.PV field attribute and configure the attributes as folk Lab 6 — Modeling the Mixer (Leave al other attributes as default.) ‘Access mode: Input Data type: Float Engineering units: Deg F Enable 1/0 scaling checked Raw value: Maximum 4095.0 EU value: Maximum 250.0 EU range value: Minimum — -5.0 EU range value: Maximum 255.0 3 Stank Fidos Jo rain) St us | ans | ti | -—_ z cence cesnnctron oT po Boe es Toads oer ee — 83 Penieomry ered te ste essa [ele] re Renee oe feme e vate: foe ee aeewe Fs. mes comeansois [Re 1g Pempenttoniume 9 ¢ 10. Click Save and Close. 41. Inthe Check In dialog box, Comment field, enter LT and TT Configuration. 12. Click OK. 13. When the Check In progress displays Object 4 of 1 completed, click Close. “Application Server 2014 444412 Application Objects Create the Mixer Template Next, you will create the mixer template, 14, In the Template Toolbox, Tralning\Project toolset, right-cick the $Tank template and select New | Derived Template. 16. Rename the new template $Mixer. 49 inca 18 Becranene 189 aa AQ sFeldRaterence 4 bso ston 189 Etre ) eso 39 ine | ea 1 sUreDefined Peta Bree ot =38 16. Double-click the $Mixer template to open its configuration editor, Notice the inherited field attrbutes from the parent object, $Tank. a er sites [ea nema] So | nie |r] mes | [ati —] fed reste) Trea SCO oe Fem a Fo re° Lab 6 -Modeling the Mixer 4-13 17. Click the Add Discrete [4] button, 18. Configure the field attribute as follows: € Name TP1.Cmd G Access mode: Output C Category: User writeable (dofaut) oO Enable state labels checked oO Label for ‘False’ state ‘Stop Label for ‘True! stato: Start > © Stizer® c sets | cos emi | ose] ose | Eee | ates} O° i > | = | rssxenmseaten e | = viene sot ar nels ——— os wire ee 7 vies Ledietiaae Ree ! “Appiation Server 20144-14 _Application Objects 19. Click the Add Discrete [4] button again and configure the attributes as follows: Name: TPLPV ‘Access mode: Input Enable state labels checked Label for False’ state: Stopped Label for True’ state: Running eer reisstas Jn ttn | So | [ man |i fxg cenirtar ae Be Biotin ele, eee “iworeye Looming SorizosLab 6 — Modeling the Mixer 20. Click the Add Discrete button again and configure the attributes as follows: Name: TP2,0md Access mode: Output Category: User writeable (default) Enable state labels checked Label for ‘False’ state: Stop Label for ‘True’ stato: Start o Bier = at atts Jones fmt | Ss] uC | Exes | ts | (Be) BG me Stat ft] ed tae cet noins [Ouse 3) ge ee Fates == oom FC Tl Peme oe ee _ weene: Fi x Foe LP were onsite dare Was = rene | sss Fone cranterdinr ober ce o sas etl na soba ata Sate a vbetarenes: FR Ea reais tastorios ane PRED “Anpiation Server 2014 4154-16 Application Objects 21. Click the Add Discrete button again and configure the attributes as follows: Name: Te2PV Access mode: Input Enable state labels checked Label for ‘False’ state: Stopped Label for ‘True! state: Running ote Feld ante oop fom | Sots Jus |r| cratis| (2) nee ER titotp ease 2) fccessoode: fret) [cae =) [opewantes ed 8 P ewe aia 2 ted dae Saas LS ar ab Fa tte ea evita abt oe: Al four new field attributes are displayed in the Field attributes lst. 22, Click Save and Close. 23. In the Check In dialog box, Comment fiekd, enter Pumps Attribute Configuration and click 0K. 24, When the Check In progress displays Object 1 of 1 completed, click Close. Thvensys Learning Sarcas0 Lab 6—Modeling the Mixer 4-17 € Create the Mixer Instance Next, you will create an instance of the mixer template. 25. In the Template Toolbox, Training\Project toolset, right-click the $Mixer template and select New | Instance. ‘The new instance eppears in the Unassigned Host toolset in the Deployment view. Notice the exclamation point to the left of the Mixer_001 instance. This is because the object ‘has configuration wamings. - 26. Keep the default name Mixer_001. aD sadeplovment Gson.0 Si ee ost Festal = cocsyen © fs Surettusery = B unwe(tee2) > = padaseo Spetcton ~ Brees = 8 Bone a Geeta ° 27. In the Model view, assign the Mixer_001 instance to the Linet area. 2g Model =e = weve 01 PES uneeanesiee “pplication Server 20144-18 _Application Objects ‘Now, you will check the warning messages. 28, Right-click the Mixer_001 instance and select Properties. pie sae arene Sitanedtons ope one vow obj Vina Sirovanip ews Cana [pies eae ‘The Mixer_004 Properties window appears. 29, Click the ErrorsiWarnings tab to view the configuration issues that need attention. Notice that the window is displaying the tems that need the proper I/O addressing, because == Is a place holder for an attribute reference. The waming messages indicate that the listed attributes do not have valid attibute references. Sines a eS eee eS) 30. Click Close. Invensys Leeming Services|Lab 6 - Modeling the Mixer Now. you will configure the attribute references forthe field attributes. 431. In the Mode! view, double-click on the Mixxer_001 instance to open its configuration editor. 82, Inthe Inherited field attributes list, select TP4.Cmd. 83, To the right of the Output destination field, click the ellipsis button. 3 her tnt oop tama | | 0% | eer | Gch AD we: ‘ld attate [Ase Tare ne) cel fae Peet 12 wecnat om) ariel reves) tien ‘The Galaxy Browser appears. ‘Aoolication Server 2014 4-194-20 Application Objects Now, you will create a filler in the Galaxy Browser. This wil show only object attributes that correspond to the fiter criteria, Csrevatabttes Thvonays Leaming SonicosLab 6 ~ Modeling the Mixer 35. Click the Add Filter CE] button to add a new filter. 36. Name the Filler MIXX where XX is your student number. 38. Click OK. ‘Applicaton Server 2014 4-214-22 _Application Objects the Instances pane, click PLCSim to view the attributes of the 39, In the Galaxy Browser, device integration object. 40. Verify hat the applied fiter is M1XX. 41, Expand the Attribute column so you can read the entire attribute name. 42, M1XX_TP1_CmdStart where XXis your student number and click OK. anLab 6~ Modeling the Mixer 4-23 ‘The Output destination now displays the correct value. @ Miser_oor eteties [tet aman | Ses | As | Ese | Cat | 3) we EET certceee FTE) el rit seusmte Ea) [le Se) Qttgom rem sd Pneens heed idee Ty ricaieei Pun (eel Ty race) i rar temet Burrriswst Brecon ‘Application Sarvr 20144-24 _ Application Objects 43, In the Inherited field attributes list, select TP2.Cmd. 1 sexe By rps 6) re tant ES reeves) 44, In the 1/0 area, click the ellipsis button to the right of the Output destination field. 485, Verify the filters sil selected for M1XX. 46. This time, select the attribute Tagname.M1XX_TP2_CmdStart and click OK. 47. Configure the rest ofthe attributes with the following Input sources 1 (aioe pa oars UIpipv [Tagname,M1x0_TP1_FlowSwitch TP2PV_ | Tagname Mixx. 1P2_FlowSwitch | [rev TTagname M130. UT_PV Crev Fagname. MIXX_TT_PV | All ofthe inherited field attributes are now configured. Thweneye Looming Sorscoe