wonderware ide 培训的手册文档第5章,共21章

合集下载

wonderware ide 培训的手册文档第一章

wonderware ide 培训的手册文档第一章

Lab 1 –Creating the GalaxyIntroductionIn this lab, you will create the Galaxy and connect to it using the ArchestrA IDE. This Galaxy will be used during the class to develop the sample application.ObjectivesUpon completion of this lab, you will be able to:Create a GalaxyConnect to a Galaxy using the ArchestrA IDECreate the GalaxyIn the following steps, you will create a Galaxy and connect to it.1.Open the ArchestrA IDE(Start | All Programs | Wonderware | ArchestrA IDE).The Connect To Galaxy dialog box appears with the local node name displayed in the GR node name drop-down list.In this image, TRAININGPC-ENG2is the local computer name.2.Click the New Galaxy button to create a new Galaxy.The New Galaxy dialog box appears.3.In the Galaxy name field, enter TrainingGalaxy.4.In the Galaxy type field, confirm Base_Application_Server.cab is selected.5.Click Create.The Create Galaxy dialog box appears and shows the Galaxy creation progress. This will take a few moments. Check to make sure that no error messages are displayed.6.When the Create Galaxy progress displays 100% completed, click Close.The newly created TrainingGalaxy now appears in the Galaxy name drop-down list.7.Click Connect.The Connect To Galaxy dialog box closes and, after a few seconds, the ArchestrA IDE opens.You will use the ArchestrA IDE to develop the Galaxy throughout the remainder of this class.-This page intentionally left blank -。

最新wonderware培训资料

最新wonderware培训资料

最新wonderware培训资料最新 Wonderware 培训资料Wonderware 作为一款在工业自动化领域广泛应用的软件,其功能强大、应用广泛。

为了帮助大家更好地掌握和运用 Wonderware,我们精心准备了这份最新的培训资料。

Wonderware 软件涵盖了多个方面的功能,包括但不限于数据采集与监控、过程控制、人机界面设计等。

对于初学者来说,可能会感到有些复杂和无从下手。

但别担心,我们会逐步为您揭开它的神秘面纱。

首先,让我们来了解一下 Wonderware 的历史和背景。

Wonderware成立于_____年,多年来一直致力于为工业领域提供先进的自动化解决方案。

它在全球范围内得到了广泛的应用,涵盖了制造业、能源、水处理等多个行业。

Wonderware 软件的安装和配置是使用它的第一步。

在安装过程中,需要注意系统的兼容性以及相关的驱动程序的安装。

配置方面,包括网络设置、数据库连接等,这些都需要根据实际的应用场景进行仔细的调整和设置。

接下来是数据采集与监控功能。

Wonderware 能够实时采集各种设备和传感器的数据,并将其以直观的方式展示给用户。

通过配置数据点、建立通信协议等操作,可以实现对生产过程中的各种参数的实时监测。

比如温度、压力、流量等关键参数,一旦出现异常,系统能够及时发出警报,以便操作人员采取相应的措施。

在过程控制方面,Wonderware 提供了丰富的控制策略和算法。

用户可以根据实际的工艺流程,编写控制逻辑,实现对生产过程的精确控制。

这不仅提高了生产效率,还保证了产品的质量和稳定性。

人机界面设计是 Wonderware 的一大特色。

一个好的人机界面能够提高操作人员的工作效率和舒适度。

在设计人机界面时,要考虑到布局的合理性、颜色的搭配、操作的便捷性等因素。

可以使用图形、图表、动画等元素,让界面更加生动直观。

Wonderware 还支持与其他系统的集成,比如 ERP 系统、MES 系统等。

Wonderware InTouch 7.11 中文版 入门手册

Wonderware InTouch 7.11 中文版 入门手册

InTouch 7.11中文版安装1. 系统要求:硬件: 带 Pentium 100更高处理器的任何 IBM 兼容个人计算机。

至少100兆的可用硬盘空间。

至少32MB的随机存储器 (RAM)。

软件: Windows NT 4.0 SP6a 或Windows 2000 SP22. 安装过程:1. 把InTouch 7.11中文版光盘插入光驱,安装程序自动启动。

或者单击“开始”,“运行”,然后键入“Setup”,单击“确定”,启动安装程序。

出现以下对话框:12. 单击“Next”,接受授权协议,出现下一个对话框:3. 单击“Yes”,进入下一步,出现以下对话框:4. 输入用户名和公司名,单击“Next”,进入下一步,出现以下对话框:25. 检查输入的内容,如果正确无误,单击“Yes”,进入下一步,出现以下对话框:6. 单击“否”,出现以下对话框:37. 单击“InTouch”,启动InTouch安装。

8. 安装程序首先安装共用组件。

出现以下对话框:9. 如需要改变共用组件的安装路径,单击“Browse”,选择了安装路径后,单击“Next”,进入下一步,出现以下对话框:10. 在此输入你的计算机所在的域名(如不在域中,输入机器名),登录的用户名和密码。

单击“Next”,4进入下一步:11. 接着安装程序把共用组件安装到了计算机中,安装完成后,出现以下对话框:12. 单击“OK”,重新启动计算机(安装还没有完成,不要把InTouch 7.11的光盘从光驱中拿走),重新启动后,安装程序将自动继续运行。

13. 重新启动后, 安装程序自动运行, 经过一系列的自动安装过程后,弹出以下对话框:514. 在此对话框中,选择InTouch的安装目录,单击“下一步”继续安装,将出现以下对话框:15. 在此对话框中,选择你要安装到电脑中的InTouch部件,然后单击“下一步”,安装程序弹出以下对话框:16. 在此对话框中,选择InTouch配置,是完整的开发系统还是只有运行系统,或者安装FactoryFocus,选择好后,单击“下一步”继续,安装程序将弹出以下对话框:617. 此对话框中详细列出了将要安装到系统中的InTouch组件,如无误的话,单击“下一步”继续,否则按“上一步”重新选择。

wonderware-ide-培训的手册文档第一章

wonderware-ide-培训的手册文档第一章

实验 1 –创建银河介绍在本实验中,您将创建银河,并使用 ArchestrA IDE 连接到它。

此银河将在类期间用于开发示例应用程序。

目标完成本实验后,您将能够:创建银河使用 ArchestrA IDE连接到加尔斧西创建银河在以下步骤中,您将创建一个银河并连接到它。

1.打开ArchestrA IDE(开始 |所有计划 |奇迹软件 |阿尔切斯特拉 IDE)"连接到银河"对话框显示,本地节点名称显示在GR 节点名称下拉列表中。

在此映像中,训练PC-ENG2是本地计算机名称。

2.单击"新建银河"按钮创建新的银河。

将出现"新建银河"对话框。

3.在"银河"名称字段中,输入训练银河。

4.在"银河类型"字段中,确认已选择"基础_应用程序_服务器.cab"。

5.单击"创建"。

将显示"创建银河"对话框并显示"银河"创建进度。

这将需要一些时间。

检查以确保未显示任何错误消息。

6.当创建银河进度显示100% 已完成时,单击"关闭"。

新创建的训练银河现在显示在Galaxy 名称下拉列表中。

7.单击"连接"。

"连接到银河"对话框将关闭,几秒钟后,ArchestrA IDE 将打开。

您将使用ArchestrA IDE 在本课程的其余部分中开发银河。

- 此页有意留空 -。

wonderware ide 培训的手册文档第16章,共21章

wonderware ide 培训的手册文档第16章,共21章

Lab 16 –Configuring HistoryIntroductionIn this lab, you will configure the Galaxy for historization to the local Historian Server. Specifically, you will configure the $gAppEngine object to store historical data.Additionally, you will configure the object attributes to be historized.ObjectivesUpon completion of this lab, you will be able to:Configure a $gAppEngine object to store historical data to a Historian ServerConfigure objects to enable history including a History extensionConfigure Objects for HistoryIn the following steps, you will configure multiple objects in the Galaxy to begin historizing data.1.In the Deployment view, double-click AOSPlatform1to open the configuration editor.2.On the General tab, in the History store forward directory field, enter C:\S&F.3.Save and close the configuration editor.4.In the Check In dialog box, Comment field, enter Store and Forward configuration and click OK.5.Double-click AppEngine1to open the configuration editor.6.On the General tab, check the Enable storage to historian check box.7.In the Historian field, enter [your instructor will confirm the computer name]. In this image,TrainingPC-ENG2will be used.8.Save and close the configuration editor.9.In the Check In dialog box,Comment field, enter Historian configuration and click OK.10.In the Template Toolbox,Working toolset, double-click $Mixer to open the configuration editor.11.In the Inherited field attributes list, select LT.PV and check the Enable history check box.12.In the Trend high field, enter 100.0and lock the history group.13.Save and close the configuration editor.14.In the Check In dialog box,Comment field, enter LT historization and click OK.15.When the Check In progress shows Object 1 of 1 completed, click Close.16.In the Template Toolbox,Working toolset, double-click Inlet1to open the configuration editor.17.Check the Historize PV check box and lock the PV group.18.Save and close the configuration editor.19.In the Check In dialog box,Comment field, enter PV historization and click OK.20.When the Check In progress shows Object 1 of 1 completed, click Close.21.In the Template Toolbox,Working toolset, double-click Agitator to open the configuration editor.22.On the Extensions tab, Extendable Attributes list, select Speed.23.Configure the Speed attribute as follows:History extension checked and lockedEngineering units:RPMTrend high:50Description:Agitator Speed24.Save and close the configuration editor.25.In the Check In dialog box,Comment field, enter Speed historization and click OK.26.When the Check In progress shows Object 1 of 1 completed, click Close.The Deployment view now displays several objects that need to be redeployed.27.Deploy AOSPlatform1and keep the default options.28.When the Deploy progress displays 100% completed, click Close.View the Historical Data with Historian ClientNow, you will use Wonderware Historian Client Trend to view a trend of the historical data.29.Start Wonderware Historian Client Trend (Start | All Programs | Wonderware | Historian Client |Trend).The Server List Configuration dialog box appears.30.In the Server field, enter [check with your instructor]. In this image, TrainingPC-ENG2will be used.31.Check the Use Integrated security check box and click Add.After a few moments, the computer name appears in the Server list.32.Click Close.The Wonderware Historian Client Trend window opens and in the Tag Picker pane, all of the tags configured for historization are displayed.33.Double-click the Agitator_001.Speed tag to add it to the trend chart.The Agitator_001.Speed historical data now displays in the trend chart.You can also drag and drop tags to the trend chart to add them.34.Drag and drop Inlet1_001.PV and M1XX.LT.PV onto the trend chart.Your trend chart will now display all three tags at the same time.35.On the toolbar, click the Enable or disable live or replay mode button.The trend chart now updates automatically.36.Close the Trend application.The Wonderware Historian Client dialog box appears.37.Click No .。

wonderware ide 培训的手册文档第20章,共21章

wonderware ide 培训的手册文档第20章,共21章

Lab 20 –Configuring RedundancyIntroductionIn this lab, you will configure a second network connection in Windows for use as the Redundancy Message Channel. Then, you will configure the Galaxy platforms and engines for redundancy. Finally, you will create the hosting relationship, deploy the changes, and force a failover to confirm the functionality.ObjectivesUpon completion of this lab, you will be able to:Configure a secondary network connection in Windows as the Redundancy Message Channel Configure WinPlatform and AppEngine objects for redundancyCreate a deployment model for redundant enginesForce a failover on a redundant systemConfigure Windows for RedundancyIn the following steps, you will configure a second network connection in Windows as the Redundancy Message Channel (RMC). This will need to be done on both computers, where the first is the computer where GRPlatform is deployed and the second is the computer where AOSPlatform1is deployed.1.Connect to the machine where the GRPlatform is installed [for the remote computer, this will be themachine where the AOSPlatform1in installed].2.Open Network Connections(Start | Control Panel | Network and Sharing Center).3.Click Change adapter settings.The Network Connections window appears.4.Right-click Local Area Connection and select Rename.5.Rename the connection ArchestrA.6.Right-click Local Area Connection 2and select Rename.7.Rename the connection RMC.8.Press Alt+N to unhide the Menu bar.9.On the Advanced menu, select Advanced Settings.The Advanced Settings dialog box appears.10.In the Connections area, select ArchestrA and click the Up Arrow button.The ArchestrA connection is now listed first.11.Click OK.12.In the Network Connections window, right-click RMC and select Properties.The RMC Properties dialog box appears.13.In the This connection uses the following items area, select Internet Protocol Version 4(TCP/IPv4).14.Click the Properties button.The Internet Protocol Version 4 (TCP/IPv4) Properties dialog box appears.15.Click the Use the following IP address option.16.In the IP address field, enter 192.168.1.1. [For the remote computer, this will be 192.168.1.2]17.Click in the Subnet mask field to automatically assign the subnet mask.18.In the bottom-right of the window, click the Advanced button.The Advanced TCP/IP Settings dialog box appears.19.On the DNS tab, uncheck the Register this connection’s addresses in DNS check box.20.Click OK.21.In the Internet Protocol Version 4 (TCP/IPv4) Properties dialog box, click OK.22.In the RMC Properties dialog box, click Close.23.Repeat Steps 1to 22on the remote computer where AOSPlatform1is deployed. The IP address thatwill be used on the remote computer will be 192.168.1.2.Configure the Platforms for RedundancyYou will now return to the ArchestrA IDE and configure the platforms for redundancy.24.In the Deployment view, open the GRPlatform configuration editor.25.In the Redundancy area, Redundancy message channel IP address field, enter 192.168.1.1.26.Save and close the configuration editor.27.In the Check In dialog box,Comment field, enter Redundancy configuration and click OK.28.Open the AOSPlatform1configuration editor.29.In the Redundancy group, Redundancy message channel IP address field, enter 192.168.1.2.30.Save and close the configuration editor.31.In the Check In dialog box,Comment field, enter Redundancy configuration and click OK.The Deployment view now displays that both platforms have pending changes.You will redeploy the platforms later in this lab.Configure AppEngine1 for RedundancyYou will now configure AppEngine1for redundancy. Since AppEngine1is currently deployed, you must first undeploy it.32.Right-click AppEngine1and select Undeploy.33.In the Undeploy dialog box, keep the default options and click OK.34.When the Undeploy progress is complete, click Close.35.Open the AppEngine1 configuration editor.36.On the Redundancy tab, check the Enable Redundancy check box.The Redundancy configuration settings auto populate with the default values.37.Keep the defaults and click Save and close.38.In the Check In dialog box,Comment field, enter Redundancy configuration and click OK.The Deployment view now displays the AppEngine1icon with the primary redundant engine icon.39.Expand the Unassigned Host folder to reveal the new backup application engine instance.This was automatically created when redundancy was enabled in AppEngine1.You will now have GRPlatform host the new AppEngine1 (Backup) object.40.Drag and drop AppEngine1 (Backup)onto GRPlatform.Now, you will redeploy the platforms.41.Select both the AOSPlatform1and the GRPlatform.42.Right-click either platform and select Deploy.43.Keep the default options and click OK.44.When the Deploy progress is complete, click Close.45.Return to Object Viewer.Because the platforms redeployed, you will get the following error in Object Viewer.46.Click OK.Object Viewer closes.You will now deploy the application engines using the Include Redundant Partner option.47.In the Deployment view, right-click AppEngine1and select Deploy.48.In the Deploy dialog box, check the Include Redundant Partner check box.49.Click OK.50.When the Deploy progress is complete, click Close.The Deployment view now displays that all objects have been deployed.View the Redundancy Functionality and Data in RuntimeYou will now use Object Viewer and observe selected AppEngine1attributes in the runtime environment. You will then force a failover and observe the changes.51.In the Deployment view, right-click AppEngine1and select View in Object Viewer.52.On the File menu, select Load Watch List.53.Navigate to C:\Training and select MyWatchWindow.54.Click Open.55.Add the following attributes to the watch window:HostRedundancy.IdentityRedundancy.StatusRedundancy.PartnerPlatformRedundancy.PartnerStatusRedundancy.FailoverOccurredRedundancy.ForceFailoverCmdThe watch window displays that AOSPlatform1is currently hosting AppEngine1and the redundancy status is active. Additionally, the GRPlatform is the partner platform and is currently in a Standby mode.56.Save the watch window.You will now force a failover to trigger redundancy and observe the changes.57.In the watch window, double-click AppEngine1.Redundancy.ForceFailoverCmd.The Modify Boolean Value dialog box appears.58.Click the True option and click OK.After a few seconds, the watch window displays GRPlatform as the host platform andAOSPlatform1as the partner platform.You will now refresh Object Viewer to view the changes.59.In the console tree pane, collapse and expand AOSPlatform1and GRPlatform.The pane now displays that AOSPlatform1is no longer hosting any objects and GRPlatform is now hosting all of the objects.60.Click the Mixer1tab.The watch window displays that all attributes are still running and producing good quality data.Lab 20–Configuring Application Redundancy 9-33Application Server 201261.On the Mixer2watch window, observe the same behavior.You will now force another failover to return to the primary redundancy configuration.62.In the Redundancy watch window, double-click AppEngine1.Redundancy.ForceFailoverCmd .63.In the Modify Boolean Value dialog box, click the True option and click OK .After a few seconds, the watch window displays AOSPlatform1as the host platform andGRPlatform as the partner platform.You can also observe what happens when the connection to the remote computer loses connectivity.64.Disable the RMC network connection.After a few seconds, the watch window now displays that the Standby Status isActive –Standbynot Available.9-34Module 9–RedundancyInvensys Learning Services 65.Reenable the RMC connection.After a few seconds, the watch window displays the Standby Statusis back to Active .。

InSQL_Wonderware培训

InSQL_Wonderware培训
Cyclic, Delta, Swinging, Forced
存储算法: Storage

节省大量的存储空间
SwingDoor – 存储策略
9 10 11 12 13 14 8 7 6 17 1 2 3 4 5 18 19 15
16
Value Deadband Swinging Door
Swinging Door
• 动态配置
• 配置导入/导出 • 高可用性功能 • 企业版
IndustrialSQL Server„ 更多 特定功能
• 更加方便地满足政府或行业法规
• 支持Windows 2003
• 客户端应用 - 工厂智能
动态配置
• 当 InSQL运行 时更改标记和对象的配置
– 无需停机或重起 – 对客户端没有影响No interruptions for clients – 没有数据间隔*
数据查询?采用结构化查询语言sql来查询insql数据而不采用专用的查询系统或方式?sql是一个行业的超级标准被行业内广泛采用允许任意的查询能很好地与其它的工厂信息系统集成有上百的现有sql查询工具sql数据读取扩展?数据读取模式?bestfit?counter?cyclic?delta?full?integral?interpolation?maximun?minimum?slope?timeinstate?timeweightedaveragewonderwaresql时序扩展?时间序列的分辨率控制对于时序数据采用基于时基采样的查询避免采用传统行计数的办法?循环增量检索wwretrievalmodecyclicewwretrievalmodedelta?分辨率控制wwresolution1000?基于行的检索wwrowcount100?基于边缘的检索wwedgedetectionleadinganaloghistory日期时间值标记名质量sql数据读取扩展cyclicmodeselectdatetimetagnamevaluequalitydetailfromvanaloghistorywheretagnameinreactlevelandwwretrievalmodecyclicandwwrowcount1000日期时间值标记名质量查询分辨率1秒但它能达到3毫秒

Wonderware 培训资料

Wonderware 培训资料
Support Section 6: Application Planning
Lab 2 – Identifying the Mixer
Course Description and Objectives
Course Description
The System Platform – Part 1 training course is a 4-day instructor-led course designed to give the knowledge necessary to develop and support applications with Wonderware Application Server.
System Platform
Clients
Microsoft Technologies & Industry Standards
Wonderware System Platform
InTouch
(Visualization)
Wonderware Clients
ActiveFactory
(Analysis Client)
?Leverage the .NET Framework for the Automation World
?Object-based application
?One global networked namespace
?Centralized configuration and security
?Multi-user development environment ?Component-based plant application model ?Self documenting

wonderware ide 培训的手册文档第19章,共21章

wonderware ide 培训的手册文档第19章,共21章

Lab 19 –Configuring Instances Through a .CSV FileIntroductionIn this lab, you will use the Galaxy Dump and Galaxy Load features of the ArchestrA IDE to change the configuration of one of the mixer instances, including its contained objects. Then, you will use the feature again to create new instances of the container.ObjectivesUpon completion of this lab, you will be able to:Use Galaxy Dump and Galaxy Load features of the ArchestrA IDEUse the Galaxy Dump FeatureIn the following steps, you will dump a configuration of the object and its contained objects into a .csv file.1.In the Model view, expand Production | Line1 | M1XX and select M1XX and all of its containedobjects.2.On the Galaxy menu, select Export|Galaxy Dump.3.Navigate to C:\Training and in the File name field, enter Mixer.csv.4.Click Save.5.When the Galaxy Dump progress is complete, click Close.Change the File Using ExcelYou will now use Microsoft Excel to view and change the .csv file.6.Start Microsoft Excel.7.On the File menu, click Open.The Open dialog box appears.8.Navigate to the C:\Training folder.The drop-down list currently displays All Excel files.9.Click the down arrow, and then in the drop-down list, select All Files(*.*).10.Select the Mixer.csv file.11.Click Open.The Text Import Wizard dialog box appears.12.Keep the default options and click Next.Step 2 of 3of the wizard displays.13.Uncheck the Tab check box and check the Comma check box.14.Click Finish.The file contents open in Excel.15.Expand column A to fully display the cell contents.You will now delete the Inlet1rows so that no changes are made to the configuration of Inlet1.16.Select rows 12 through14.17.Right-click any of the selected rows and select Delete.18.For the M1XX instance, ShortDesc name (cell F6), enter Mixing Tank.19.Change the remainder of the ShortDesc values as follows:The cells now display the new short description names.20.In the File menu, click Save As.21.In the File name field, enter Mixer1.csv.22.In the Save as type drop-down list, select CSV (Comma delimited)(*.csv).23.Click Save.The Microsoft Excel dialog box appears asking if you are sure of the format.24.Click Yes.25.Close the Microsoft Excel application.The Microsoft Excel dialog box appears if you would like to save the changes, even though you have not made any further changes.26.Click Don’t Save.27.In the ArchestrA IDE, on the Galaxy menu, select Import | Galaxy Load.28.Select the Mixer1.csv file and click Open .29.The Galaxy Load Conflict Resolution dialog box appears.30.Select the Only update changed attributes option.31.Click OK .32.When the Galaxy Load displays 100% processed , click Close .The Model view now displays that the objects that were imported have pending changes and need to be redeployed, except for Inlet1_001, which had no changes. You will redeploy these later in this lab.33.Open the configuration editors for M1XX,Agitator_001,Inlet2_001,and Outlet_001and then on theObject Information tab, verify the Description has changed.34.Close the configuration editors.35.Open the Inlet1_001configuration editor and on the Object Information tab, verify the Descriptionhas remained the same.36.Close the configuration editor.37.Select all five objects.38.Right-click on any of the selected objects and click Deploy.39.Keep the default options and click OK.40.When the Deploy progress is complete, click Close.Create Another Mixer Container InstanceYou will now create another mixer container instance by exporting and importing the objects.41.In the Model view, right-click on any of the selected objects and select Export | Galaxy Dump.42.In the File name field, enter Mixer2.csv.43.Click Save.44.When the Galaxy Dump progress completes, click Close.45.Start Microsoft Excel.46.On the File menu, click Open.47.In the Open dialog box, in the drop-down list to the right of the File name field, select All Files.48.Navigate to C:\Training and select Mixer2.csv.49.Click Open.50.In the Text Import Wizard dialog box, Step 2of 3, uncheck the Tab check box and check theComma check box.51.Click Finish.52.Rename the $Mixer template tagname M3XX, where XX is your student number.53.Rename the other four objects as follows:Agitator_003Inlet1_003Inlet2_003Outlet_00354.For the same four objects, enter M3XX as their Container name.55.On the File menu, click Save As.56.In the File name field, enter Mixer3.csv.57.In the Save as type drop-down list, select CSV (Comma delimited)(*.csv).58.Click Save.59.In the Microsoft Excel dialog box, click Yes.60.Close the Microsoft Excel application.61.In the Microsoft Excel dialog box, click Don’t Save.62.In the ArchestrA IDE, on the Galaxy menu, select Import | Galaxy Load.63.Select Mixer3.csv.64.Click Open.The Galaxy Load Conflict Resolution dialog box appears.65.Keep the default options and click OK.66.When the Galaxy Load progress completes, click Close.In the Model view, the new M3XX instance appears in the same area as M1XX.67.Expand M3XX to view the new contained objects.68.Deploy the M3XX container object.69.In the Deploy dialog box, keep the default options and click OK.70.When the Deploy progress is complete, click Close.。

Wonderware 培训资料PPT

Wonderware 培训资料PPT

▪ Multi-user development environment ▪ Component-based plant application model ▪ Self documenting
• Be able to troubleshoot applications in a standalone and networked environment.
Wonderware System Platform
Project Specific Work
Industry Packs Function Specific Modules
Course Objectives
• Understand the ArchestrA® technology and how it is applicable to the plant floor environment.
• Become familiar with developing objects and instances configuring applications using the Integrated Developing Environment.
ArchestrA
It provides a unified environment for visualization, plant history, device communications and automation application integration.
Application Server’s application, configuration information and project database.
System Platform

Wonderware_培训资料

Wonderware_培训资料

Wonderware_培训资料Wonderware 培训资料在当今的工业自动化领域,Wonderware 系统凭借其强大的功能和卓越的性能,成为了众多企业的首选。

为了让大家更好地了解和掌握Wonderware 系统,本文将为您提供一份详细的培训资料。

一、Wonderware 系统概述Wonderware 是一套功能强大的工业自动化软件套件,它涵盖了从数据采集、监控到过程控制和管理的各个环节。

其主要特点包括:1、强大的可视化功能:能够以直观、清晰的方式呈现生产过程中的各种数据和状态。

2、高度的可扩展性:可以轻松适应不同规模和复杂程度的工业系统。

3、丰富的通信协议支持:能够与各种现场设备和控制系统进行无缝连接。

二、Wonderware 系统的安装与配置1、系统要求在安装 Wonderware 之前,您需要确保您的计算机满足以下最低要求:(1)操作系统:Windows 7 及以上版本。

(2)处理器:Intel Core i5 或更高。

(3)内存:8GB 及以上。

(4)硬盘空间:至少 50GB 的可用空间。

2、安装步骤(1)下载安装文件:从官方网站或授权渠道获取 Wonderware 的安装文件。

(2)运行安装程序:双击安装文件,按照向导的提示进行操作。

(3)选择安装组件:根据您的需求选择要安装的组件,如InTouch、Historian 等。

(4)配置安装选项:设置安装路径、数据库连接等选项。

(5)等待安装完成:安装过程可能需要一些时间,请耐心等待。

3、配置系统安装完成后,您需要进行一些基本的配置,如设置用户权限、连接数据库等。

三、Wonderware 软件组件介绍1、 InTouchInTouch 是 Wonderware 的人机界面(HMI)软件,它允许用户创建直观、交互式的操作界面,以监控和控制工业过程。

(1)图形设计:使用丰富的图形库和绘图工具创建精美的界面。

(2)数据连接:轻松连接到各种数据源,实时获取数据。

wonderware培训

wonderware培训

Wonderware培训Wonderware公司推出旗舰级InTouch软件,这是第一个基于微软Windows&reg操作系统的人机界面(HMI)。

Wonderware只能在windows环境下运行,支持32位及64位操作系统,但wonderware 公司建议使用32位操作系统因为64位操作系统部是很稳定,系统容易崩溃带来不必要的损失。

Wonderware软件架构:Intouch等可视部分客户端 Active factory分析部分Information Server CAL等第3方认可软件即符合(微软技术标准,工业标准)App Server发布数据三个服务器 Historian历史数据Information Server实时数据DAServer/I/OserverPLC等第三方软件Daserver/ioserver :收到采集命令,采集数据,发广播包,工作完成后,各机从DAseerver 堆栈中提取数据。

概念:1.Archestry 只是一个名字2.Application server:应用程序服务器。

类似于I/Osever 客户端(阀门,泵,开关等运行配置,控制配置,run_time部分)3.Galaxy:数据库4.Galaxy Repostistory:配置的指令存储在此可以用这台机器进行开发。

5.GR是装Galaxy数据库的机器一个(工程)网络只能有一个Galaxy。

安装前准备:APPLICATION SERVER 的同时还可以安装I/OserverGR SQLSERVER可单独也可与APPLICATION 一起装。

Historation > 安装SQL server2005数据库需要建立防火墙,需专门一台机器。

Information server >安装SQL server2005数据库需要建立防火墙,需专门一台机器。

步骤1:1.每台机器装BOOTSTAP(需要主动对GR访问取数据的必须安装不是主动对GR访问被动的接收数据的不用安装)。

Wonderware FactorySuite InTouch 参考指南

Wonderware FactorySuite InTouch 参考指南

第 1 章 – 系统标记名 .............................................. 1-1
$AccessLevel.............................................................................................. 1-2 $AlarmLogging............................................................................................ 1-3 $AlarmPrinterError ...................................................................................... 1-3 $AlarmPrinterNoPaper................................................................................ 1-4 $AlarmPrinterOffline.................................................................................... 1-4 $AlarmPrinterOverflow................................................................................ 1-5 $ApplicationChanged.................................................................................. 1-5 $ApplicationVersion .................................................................................... 1-6 $ChangePassword ..................................................................................... 1-6 $ConfigureUsers ......................................................................................... 1-7 $Date........................................................................................................... 1-7 $DateString ................................................................................................. 1-8 $DateTime .................................................................................................. 1-8 $Day............................................................................................................1-8 $HistoricalLogging ......................................................................................1-9 $Hour .......................................................................................................... 1-9 $InactivityTimeout .....................................................................................1-10 $InactivityWarning.....................................................................................1-11 $LogicRunning ..........................................................................................1-11 $Minute .....................................................................................................1-12 $Month ......................................................................................................1-12 $Msec .......................................................................................................1-13 $NewAlarm ...............................................................................................1-13 $ObjHor.....................................................................................................1-13 $ObjVer .....................................................................................................1-14 $Operator..................................................................................................1-14 $OperatorEntered .....................................................................................1-14 $PasswordEntered ...................................................................................1-15 $Second....................................................................................................1-15 $StartDdeConversations...........................................................................1-15 $System ....................................................................................................1-16 $Time ........................................................................................................1-16 $TimeString...............................................................................................1-16 $Year.........................................................................................................1-17

Watir学习手册

Watir学习手册

TIB自动化测试工作室/testware/简介 (2)Watir vs. SilkTest (3)watir vs. Selenium (4)Watir vs. Selenium vs. Sahi (5)Goodbye Selenium,Hello Watir (6)Watir and Selenium - Bret Pettichord (6)安装 (8)ruby1.9.1+watir1.6.5 (8)ruby1.8.6+watir1.6.5 (12)ruby1.8.6+watir1.5.2(成功!) (13)Fxri – Interactive Ruby Help & Console (14)帮助文档 (14)录制器 (15)WatirRecorder++ (15)testwise(iTest2) (15)Watir WebRecorder (16)GlobalWatch Script Recorder (16)中文问题 (16)基础使用 (17)HelloWorld (17)google测试例子 (18)link (18)检查点 (18)contains_text (18)assert (19)Rspec (21)命令行运行 (22)IE窗口处理 (23)JavaScript窗口处理 (23)整合AutoIt处理JavaScript弹出窗口 (24)获取IE浏览器版本和操作系统版本 (25)Watir可读取和与之交互的HTML页面元素 (27)高级使用 (28)用Watir测试Mercury Tours (28)Excel (33)Object Map(对象映射) (34)How do I create an application/object map? (35)创建Map类 (35)JavaScript (36)调用JavaScript脚本 (36)How do I trigger JavaScript events? (37)How do I interact with a JavaScript tree view? (37)Watir+XPath (38)Watir框架、扩展、工具 (38)数据驱动 (39)关键字驱动 (39)Rspec (39)WatirCraft (39)WET (40)360WebTester (41)简介Watir is a testing tool for automating browser-based tests of web applications. It is a Ruby library that works with Internet Explorer and Firefox./projects/wtr/目前最新版本是:watir1.6.5 November 10, 2009下载地址:/frs/?group_id=104&release_id=41300Watir简介"Watir" (发音与 water相近) 全写是 "Web Application Testing in Ruby"。

Wonderware 培训资料学习资料

Wonderware 培训资料学习资料

ArchestrA
It provides a unified environment for visualization, plant history, device communications and automation application integration.
Application Server’s application, configuration information and project database.
System Platform
Clients
Microsoft Technologies & Industry Standards
Wonderware System Platform
Project Specific Work
Industry Packs Function Specific Modules
Application Server Galaxy
Galaxy Repository
Single computer and software where the Galaxy database is located.
Wonderware Application Server
+++ Scan-based system. Highlights
Support Section 6: Application Planning
Lab 2 – Identifying the Mixer
Course Description and Objectives
Course Description
The System Platform – Part 1 training course is a 4-day instructor-led course designed to give the knowledge necessary to develop and support applications with Wonderware Application Server.

wonderware ide 培训的手册文档第6章

wonderware ide 培训的手册文档第6章

Lab 6 –Modeling the MixerIntroductionIn this lab, you will configure the analog and discrete field attributes in the $UserDefined object to model a mixer device. You will also use the Galaxy Browser to find and build attribute references using the PLCSim object created in the previous lab to provide the connection to the live values within the mixer. ObjectivesUpon completion of this lab, you will be able to:Configure analog and discrete field attributes in a $UserDefined objectBuild attribute references using the Galaxy BrowserCreate the Tank TemplateIn the following steps, you will create the tank template.1.In the Template Toolbox,expand the Application toolset.2.Right-click the $UserDefined template and select New|Derived Template.3.Rename the derived template $Tank.4.Move the $Tank template to the Working toolset.5.Double-click $Tank to open its configuration editor.6.On the Field Attributes tab,click the Add Analog button to add a new analog field attribute.7.In the Name field, rename the field attribute LT.PV and press Enter.8.Click on the Add Analog button again and rename the new field attribute TT.PV and press Enter.Your Field attributes list displays both attributes.9.Click the LT.PV field attribute and configure the attributes as follows:Access mode:InputData type:FloatEngineering units:GallonsEnable I/O scaling checkedRaw value: Maximum4095.0EU range value: Minimum-5.0EU range value: Maximum105.010.Click the TT.PV field attribute and configure the attributes as follows:Access mode:InputData type:FloatEngineering units:Deg FEnable I/O scaling checkedRaw value: Maximum4095.0EU value: Maximum250.0EU range value: Minimum-5.0EU range value: Maximum255.011.Click Save and close.12.In the Check In dialog box,Comment field, enter LT and TT configuration.13.Click OK.14.When the Check In progress displays Object 1 of 1 completed, click Close.Create the Mixer TemplateNext, you will create the mixer template.15.Right-click the $Tank template and select New | Derived Template.16.Rename the new template $Mixer.17.Double-click the $Mixer template to open its configuration editor.Notice the inherited attributes from the parent object,$Tank.18.Click the Add Discrete button.19.Configure the field attribute as follows:Name:TP1.CmdAccess mode:OutputCategory:User writeable (default) Enable state labels checkedLabel for ‘False’ state:StopLabel for ‘True’ state:Start20.Click the Add Discrete button again and configure the attributes as follows:Name:TP1.PVAccess mode:InputEnable state labels checkedLabel for ‘False’ state:StoppedLabel for ‘True’ state:Running21.Click the Add Discrete button again and configure the attributes as follows:Name:TP2.CmdAccess mode:OutputCategory User writeable (default)Enable state labels checkedLabel for ‘False’ state:StopLabel for ‘True’ state:Start22.Click the Add Discrete button again and configure the attributes as follows:Name:TP2.PVAccess mode:InputEnable state labels checkedLabel for ‘False’ state:StoppedLabel for ‘True’ state:RunningAll four new field attributes are displayed in the Field Attributes list.23.Click Save and close.24.In the Check In dialog box,Comment field, enter Pump attribute configuration and click OK.25.When the Check In progress displays Object 1 of 1 completed, click Close.Create the Mixer InstanceNext, you will create an instance of the mixer template.26.In the Template Toolbox,Working toolset, right-click the $Mixer template and select New |Instance.27.Keep the default name Mixer_001.28.In the Model view, assign the Mixer_001instance to the Line1area.Notice the exclamation point to the left of the Mixer_001instance. This is because the object has configuration warnings.Now, you will check the warning messages.29.Right-click the Mixer_001instance and select Properties.The Mixer_001Properties window appears.30.Click the Errors/Warnings tab to view the configuration issues that need attention.Notice that the window is displaying the items that need the proper I/O addressing, because ---.---is a place holder for an attribute reference. The warning messages indicate that the listed attributes do not have valid attribute references.31.Click Close.Now, you will configure the attribute references for the field attributes.32.In the Model view, double-click on the Mixer_001instance to open its configuration editor.33.In the Inherited field attributes list, select TP1.Cmd.34.To the right of the Output destination field, click the ellipsis button.The Galaxy Browser -TrainingGalaxy window appears.35.In the Instances pane, click PLCSim to view the attributes of the device integration object.36.Select Tagname.M1XX_TP1_CmdStart where XX is your student number and click OK.In thisimage,the student number is00.The Output destination now displays the correct value.37.Repeat steps32through35to configure the Output source for attribute TP2.Cmd using theTagname.M1XX_TP2_CmdStart attribute.38.Configure the rest of the attributes with the following Input sources:All of the inherited field attributes are now configured.39.Click Save and close, and then in the Check In dialog box,Comment field, enter I/O referencesconfiguration and click OK.Notice that the exclamation point is no longer displayed.40.In the Deployment view, right-click the Mixer_001instance and select Deploy.41.Keep the default options and click OK.42.When the Deploy progress displays 100% completed, click Close.View the Mixer in Object ViewerNext, you will observe the attribute values for the object created in the previous steps.43.Right-click on the Mixer_001instance and select View in Object Viewer.44.If you closed Object Viewer, on the File menu, select Load Watch List to open the watch list file yousaved earlier.45.Add a new watch window and rename the tab Mixer.46.Add the following attributes to the newly created Mixer watch window:LT.PVTT.PVTP1.CmdTP1.PV.MsgTP2.CmdTP2.PV.Msg47.Save the watch window.。

培训手册WonderwareApplicationServer

培训手册WonderwareApplicationServer

培训手册Wonderware ApplicationServer 3.1目录一、简介 (5)1.1 Wonderware系统平台 (5)Lab 1 创立 Galaxy (6)1.2 ArchestrA IDE (9)1.3 系统对象 (17)1.4 建模及规划 (18)Galaxy 项目开发流程 (18)Lab 2 搅拌器建模分辨 (19)二、平台应用构造 (22)2.1 模板 (22)Lab 3 创立一个模板 (22)2.2 开发模板 (27)Lab 4 创立部署模板 (27)2.3 运转环境 (35)Lab 5 怎样使用对象查察器 (35)2.4 连结现场数据 (41)Lab 6 连结现场数据 (41)三、平台应用对象 (49)3.1 模板与实例 (49)3.2 用户定义对象 (51)Lab 7 创立热互换器模板 (51)3.3 改变控制及衍生 (61)Lab 8 怎样改变控制及衍生 (61)3.4 模拟型设施对象 (64)Lab 9 创立仪表模板 (64)3.5 失散型设施对象 (66)Lab 10 创立阀、泵、电机模板 (66)3.6模板容器 (74)Lab11 创立 Mixer (74)四、扩展对象 (91)4.1 UDAs (91)4.2扩展属性 (91)Lab12配置电机速度属性 (91)4.3脚本简介 (96)Lab13用脚本增添自动连结至 DDE Suitelink Client (96)Lab14用脚本配置自动说明 (99)五、报警和历史 (105)5.1报警 (105)Lab15报警配置 (105)5.2历史 (117)Lab16历史配置 (117)六、安全 (122)6.1安全回首 (122)Lab17安全配置 (122)七、 Galaxy 保护 (142)7.1导出导入对象 (142)7.2经过 .csv 文件配置实例 (143)7.3系统管理控制( SMC) (144)7.4网络账户功能 (145)八、数据收集产品 (145)8.1IO Server (146)8.2DA Server (147)8.3DI Object (147)九、多节点开发 (148)9.1应用系统冗余 (148)Lab 18 配置应用冗余148 9.2 数据收集冗余 (150)Lab 19 配置 DI 对象冗余150 9.3 多节点应用 (153)Lab 20 变换到网络开发环境153一、简介1.1 Wonderware系统平台系统架构节点描绘安装组件Galaxy Repository GR 节点,一个 Galaxy 就有一个 GR 节点。

Wonderware培训

Wonderware培训

wonderware一、 wonderware是做什么的?wonderware主要提供工业中的MES (Manufacturing Execution System)制造(生产)执行系统的解决方案(solution)。

针对的行业包括钢铁、烟草、化工、能源、食品、水处理等。

二、:wonderware的产品体系架构。

1、wonderware主要包括那些软件?主要包括:intouch(数据采集和画面监视控制用),DI(device integration),InSQL(工业数据库软件),IAS(Industrial Application Server工业应用平台),incontrol(软PLC),I/Oserver(数据通讯软件),DT(停机分析软件),QI(质量分析软件),InBatch(批处理软件),intrack(跟踪软件),SCADAlarm(事件报警软件),ActiveFactoty(InSQL终端服务软件)等。

2、wonderware的架构特点?wonderware目前所有产品都是基于ArchestrA技术。

ArchestrA 是一种面向对象(工厂),基于.NET的软件技术架构。

三、wonderware的产品亮点。

简易的(容易安装和使用),高可靠性(通过冗余和备份确保数据安全),先进性(同microsoft合作的技术领先),高开放性(方便的数据访问,支持众多PLC),高扩展性,有效性,集成性(方便的数据交换和通讯,上千种的I/Oserver,有Tookit供用户开发IOserver,RPM快速协议开发工具)。

wonderware和microsoft是金牌合作伙伴,致力于将微软技术带入工业现场,被成为工业界的微软。

智能工厂,实时决策(powering intelligent plant decisions in real time).协助用户快速集成,掌握和运用实时信息,进行智能决策,提高企业效益。

wonderware ide 培训的手册文档第7章,共21章

wonderware ide 培训的手册文档第7章,共21章

Lab 15 –Logging AlarmsIntroductionIn this lab, you will configure and run the Alarm DB Logger Manager, which is used to store real-time alarms in a centralized database.ObjectivesUpon completion of this lab, you will be able to:Configure the Alarm DB Logger ManagerUse alarm queries to retrieve alarms and events from alarm providersConfigure and Start the Alarm DB Logger ManagerIn the following steps, you will configure the Alarm DB Logger and start sending alarms to the database.1.Start the Alarm DB Logger Manager(Start | All Programs | Wonderware | InTouch | Alarm DBLogger Manager.The Alarm DB Logger Manager dialog box appears.2.Click Settings.After a few moments, the Alarm DB Logger Manager –Configuration dialog box appears.The Server Name field should have the name of the node where your SQL database is located [the instructor will provide the server name]. In this image, the local node (default) will be used.The Database field should have the name of your SQL database [your instructor will provide the name of the database]. In this image, the default name of WWALMBD will be used.The User Info area should contain the SQL user name and password that is used to access the SQL server [your instructor will confirm the credentials that should be used]. In this image, sa will be used for the User Name.The Logging Mode area will be the default option of Detailed, so that every alarm and event will be recorded.3.Click Test Connection.The Error dialog box appears.This message is explaining that the connection was successful, but the database still needs to be created.4.Click OK.5.In the Alarm DB Logger Manager -Configuration dialog box, click Create.6.The Success dialog box appears.7.Click OK.8.In the Alarm DB Logger Manager -Configuration dialog box, click Next.The Alarm DB Logger Manager –Query Selection dialog box appears.9.Remove the contents of the existing default Alarm Query field.Configure the Alarm Query area as follows: [check with your instructor to verify your remote computer name]\\[your remote computer name]\Galaxy!ControlSystem\\[your remote computer name]\Galaxy!Packaging\\[your remote computer name]\Galaxy!Production\\[your remote computer name]\Galaxy!Receiving\\[your remote computer name]\Galaxy!ShippingIn this image, [your remote computer name] is displayed as TRAININGPC-REM2.10.Click Next.11.The Alarm DB Logger Manager –Advanced Setting dialog box is now displayed.12.Keep the default options and click Finish.This Alarm DB Logger Manager dialog box reappears.13.Click Start.The Smart Cache begins processing the alarms that have been queued up in the system and begins sending them to the database.The number decreases as the queued alarms are processed until the Smart Cache is Empty.14.Close the Alarm DB Logger Manager.The Alarm DB Logger Manager will continue to run in the background.View the Alarm History DataYou will now use the Microsoft SQL Server Management Studio to view the latest recorded alarms and events.15.Start Microsoft SQL Server Management Studio(Start | All Programs | Microsoft SQL Server2008 | SQL Server Management Studio).16.Keep the default settings and click Connect.17.In the Object Explorer pane, expand Databases | WWALMDB | Views.18.Right-click dbo.v_AlarmHistory and select Select Top 1000Rows.19.The data appears in the bottom-middle pane.20.In the Object Explorer pane, right click dbo.v_EventHistory and select Select Top 1000 Rows.The events logged from the previous lab are displayed here in the bottom-middle pane.21.Close the Microsoft SQL Server Management Studio.22.Close the Alarm DB Logger Manager window.。

  1. 1、下载文档前请自行甄别文档内容的完整性,平台不提供额外的编辑、内容补充、找答案等附加服务。
  2. 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
  3. 3、如文档侵犯您的权益,请联系客服反馈,我们会尽快为您处理(人工客服工作时间:9:00-18:30)。

Lab 5 –Connecting to the Field
Introduction
In this lab,you will configure an instance of the $DDESuiteLinkClient template to connect to a device integration server using the SuiteLink protocol. You will then use Object Viewer to monitor the connection status of the instance in runtime.
Objectives
Upon completion of this lab, you will be able to:
Configure a device integration object
Monitor the connection status of a device integration object
Create a Connection to a Field Device
In the following steps, you will create an instance of the $gDDESuiteLinkClient template and configure it to connect to the PLC simulator.
1.In the ArchestrA IDE,Template Toolbox,Global toolset, right-click $gDDESuiteLinkClient and
select New | Instance.
2.Rename the instance PLCSim.
3.Double-click PLCSim to open its configuration editor.
4.On the General tab, configure the instance as follows:
Server node:[check with your instructor] In this image, TrainingPC-IO2 is used.
Server name:RTEngine
Communication Protocol:SuiteLink(default)
5.At the top of the PLCSim pane, click the Topic tab.
6.In the Available topics section,click the Add button.
7.In the Topic field, enter Tagname and press Enter.
8.In the Associated attributes for Tagname section, click the Import button.
The Open dialog box appears.
9.Navigate to the C:\Training folder, select the PLC Items List.csv file.
Click Open.
After a few seconds, the Associated attributes for Tagname section is populated with all of the items in the file.
The Attribute column displays the aliases assigned to each of the corresponding Item Reference data points.
10.Click the Save and close button to close the editor.
The Check In dialog box appears.
11.In the Comment field, enter Basic Configuration.
12.Click OK.
13.In the Model view, assign the PLCSim instance to the ControlSystem area.
14.In the Deployment view, host the PLCSim instance in AppEngine1.
15.Right-click on PLCSim and select Deploy.
16.Keep the default options and click OK.
17.When the Deploy progress displays 100% completed, click Close.
View the Attributes in Runtime
You will now return to Object Viewer to view the attribute values in runtime.
18.In the Deployment view, right-click PLCSim and select View in Object Viewer.
The Object Viewer window appears and refreshes.
19.Right-click on the watch window and select Add Watch Window.
20.Right-click on the watch window and select Rename Tab.
21.Rename the tab PLCSim.
22.In the details pane, add the following attributes to the watch window:
ConnectionStatus
Reconnect
ScanState
ScanStateCmd
23.Add the ScanGroupList attribute to the watch window.
The Array for PLCSim.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.
24.In the Enter an array index field, enter-1.
25.Click OK.
Lab 5–Connecting to the Field 3-73
Application Server 2012
The ScanGroupList is now displayed in the watch window.
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 true, will attempt to reconnect to the Device Integration Server.26.
Right-click on the watch window and select Save .
3-74Module 3–Application Infrastructure
-This page intentionally left blank -Invensys Learning Services。

相关文档
最新文档