最新wonderware培训资料

合集下载

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培训教学提纲

w o n d e r w a r e培训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-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 在本课程的其余部分中开发银河。

- 此页有意留空 -。

InSQL_Wonderware培训

• 支持 ‘迟到的’ 数据(旧的数据,人工数据,非实时
数据)
• 把最初是从外部收集的数据导入到 InSQL – LIMs, RTU, .CSV 数据文件 (快速加载!) – 旧的 InTouch 历史 • SQL 将数据值插入/更新到History – 原始数据 – 传感器故障时输入修正值 – 检索原始的 / 最新的修正
Wonderware Historian
Wonderware 系统组件
强大的数据分析工具
实时的工厂历史数据库
强大的工厂模型架构 =
易于配置和变更管理
信息门户传送合适的信息
工厂数据源
主要内容
• IndustrialSQL Server - 实时/历史数据库 • Industrial Application Server – Wonderware 统一的系统平台 • 基于ArchestrA的系统解决方案 • 小结
• 在大多数场合下非常高效 • InSQL适应更多的应用
– 无损压缩 – 有损压缩
存储效率
168 Raw Values 9 Values (Swinging Door = 3.0)
33 Values (Deadband = 4.0) 9 Values (Deadband = 13.0)
数据访问 - 实时的 SQL
Delta
Cyclic New “Best Fit”
No gap indicated
Adds detail with more subintervals or smaller time periods
事件和概要数据
• 强大的事件检测功能
– 模拟，离散，定时的，ActiveX 事件, 通用 SQL
• 可配置的事件响应系统

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 培训的手册文档第11章

Lab 11 –Adding Auto Reconnect to DDESuiteLinkClientIntroductionIn this lab, you will configure the $gDDESuiteLinkClient to automatically reconnect to the data source when the connection is lost. You will do so by extending the objects with UDAs with scripts.Using a UDA/script combination, you will also add additional diagnostic information that will indicate the number of disconnects the object has experienced since it last went on scan.ObjectivesUpon completion of this lab, you will be able to:Create scripts in an objectCreate scripts with multiple execution typesAdd reconnect functionality to the $gDDESuiteLinkClient objectAdd the Auto Reconnect FunctionalityIn the following steps, you will create a script that will automatically reconnect to the data source when the connection is lost.1.In the Template Toolbox,Global toolset, double-click $gDDESuiteLinkClient to open theconfiguration editor.2.On the Scripts tab, click the Add Script button. the new script Reconnect and press Enter.4.Configure the Reconnect script as follows:Aliases:lockedDeclarations:lockedScripts: Execution type:Execute(default) and lockedBasics lockedExpression: Me.Connectionstatus<>2Trigger Period:00:00:05.0000000Script body Me.Reconnect=true;This script will attempt to reconnect every 5 seconds when not connected to the data source.Now, you will validate the script syntax by using the Validate feature. If the script has a syntax error, it will appear in the yellow bar just above the script body area.5.To the right of the Execution type drop-down list, click the Validate button.6.In the UDAs tab, click the Add button.7.Rename the new UDA t and press Enter.8.Configure the t UDA as follows:Data type:IntegerCategory:Calculated9.In the Scripts tab, click the Add button. the new script Disconnect.Monitor and press Enter.11.Configure the Disconnect.Monitor script as follows:Aliases:lockedDeclarations:lockedScripts: Execution type:Execute(default) and lockedBasics lockedExpression: Me.Connectionstatus<>2Trigger type:OnTrueScript body t=t+1;This script will increase a counter by one every time the condition is true.12.Click the Validate button.You will now add code within the same script under a different execution type that will run when the object goes on scan.13.While still in the Disconnect.Monitor script, change the Execution type to OnScan.14.In the script body, type t=0;.This script will reset the counter to zero every time the object goes on scan.15.Save and close the configuration editor.16.In the Comment field of the Check In dialog box, type Reconnect script and click OK.17.When the Check In progress displays Object 1 or 1 completed, click Close.18.Redeploy PLCSim, leaving the default options.19.When the Deploy progress displays 100% completed, click Close.View the Scripts in RuntimeNext, you will use Object Viewer to view the runtime data of the scripts.20.In the Deployment view, right-click PLCSim and select View in Object Viewer.21.Click on the PLCSim tab.Add the following attributes to the watch window:tDisconnect.Monitor.ExecutionCntReconnect.ExecutionCnt22.Save the watch window.Note:Your instructor will now disconnect your connection to the Device Integration server, and then reconnect the connection so that you can observe the behavior.Your Watch List now displays that there was a disconnect, but the connection has been restored.。

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 .。

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

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/Oserver
PLC等第三方软件
Daserver/ioserver :收到采集命令，采集数据，发广播包，工作完成后，各机从DAseerver 堆栈中提取数据。

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

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

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

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

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

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

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

安装一个bootstrap意味着一个授权。

2..安装Intouch。

IDE.Galaxy.
3.部署platform相当于GR给各机器指令（GR本机也需要）
安装注意： 1.Historian安装好被动接受等于GR或I/O塞给的数据，不需要bootstrap.
只要对外广播被动获取的不需要bootstrap
2.安platform必须安装bootstrap
3.不要在域控制器上安装SQL每台机器必须安装微软补丁包KB958644否则机器
死机。

步骤2：
1.安装虚拟机Virtual pc 2007 sp1.exe。

2.解压缩“windows 2003 standard CHS.ZIP”用虚拟机进入该系统。

从“开始>程序>vpc>file>NEW virtual 选择使用已有的>选择 WIN 2003.ZIP文件即操作系统”pw：goodluck。

修改用户名全拼
“我的电脑>属性>计算机名”
3.连接到局域网，因为要组成工作组
步骤3：
1.Intouch(若先不安装Intouch后面安Application server有以下几点)
（1）注意画面出现的版本号
（2）域，组两台机器互相访问。

必须填写用户名和密码，必须和电脑中本地用户里的用户名，密码一致。

是不是一组只取决于安装此时用户名
和密码是否一样。

（3）创建本地用户不要勾选。

（4）选域，不不要再域控制器上安装SQLserver若不是域就找本机名。

USERNAME:用户名
PASSWORD:密码
配置密码：
我的电脑>管理MMC>本地用户和组>小网络内每台机器都要这样做。

注：先在MMC里创建，在填到上夜安装的信息。

2.SQL SERVER 2005或2008.
安装2008的ISO CD1和CD2>安装SQL之前会提示安装FRAMEWORK然后重启>安装过程中输入密码之前现找到计算机名的节点叫TERRY密码输进SQL的密码。

步骤4：
安装wonderware application server
（1）bootstrap
（2）IDE
（3）GR>要安SQL SERVER
（4）PDF DOCUMENTATION 帮助文件。

培训的90%内容都来自于此
步骤5：
安装完成后建议重启强烈建议
步骤6：
授权 .LIC文件
开始>wonderware>common>LicenseUtility>file>install license files>找到LICENSE或者自己拷贝到相应目录
安装好后的介绍：
1.books ：帮助文档，教学资料大都来自于此。

mon：（1）aaconfig sql:连接到SQL的配置。

默认用本机登录
（2）chang network account：登录到WINDOWS的用户可以是GUEST此处是网络中的。

网络中的用户名和密码不允许更，若是修改了，可以在此处改回来。

点确定后重启。

（3）license utility
（4）NetDDE Extension:几乎没有用。

针对WINDOWS98只是框架，不是DDE服务器。

3.Archestra IDE:装IDE的机器就是一个工程师站。

4.SMC：wonderware所有软件的管理，启动，备份的平台。

杀掉平台，停止引擎。

关于Log View:
Wonderware所有产品运行过程出现的问题，信息，记录80%的事故都可以在此找到原因。

出现错误>选好有用的行>右键SENT TO>NOTEPAT>另存为记事本
运行IDE
GR node:装IDE的机器名
Galaxy name
Type
About:vision 互相一致很重要，必须要完全一样。

低的一定要升级。

New Galaxy:
GR node name:可以远程GR那台机器
Galaxy type:Base_Application_server.cab(选此)
后面两个DEMO仅是示例
Base_Intouch.cab仅Intouch
注意：（1）机器名一定要改
（2）安装Intouch时必须是一组
（3）A能找到B C但是反之不行的解决方法如下
右键网络邻居>更改WINDOWS防火墙设置>启用（可能以启用，但是互相连接不上，刚安好WINDOWS，启用防火墙，不更改任何设置，ping不通）不能DEPLOY>例外>文件和打印机共享>编辑>4个全部选上
另：安装“硬件防火墙”和上面“软件防火墙‘同样，要打通上面4个端口（TCP,UDP）
只是文件传输，即拷贝文件端口，不是进程运行端口。

重启OK。

类等同于模板：虚的东西，只是模具。

不是实物。

对象------实例阀门
继电器
打印机
测温器
做实例之前要先做模板
IDE画面
Template:设备模板
Graphic：图形模板
Model：工厂逻辑，现场抢修人员观看的
Deploy：部署模式，工厂维护人员观看
Derivation：派生模式，工厂维护人员观看
Template中基本模板有3个
Application：应用模板，设备模板----- 1.AnalogDevice：压力。

温度等模拟类
2．DisscreteDevice：阀门，泵等开关类
erDegined:用户自定义
Device Integation :把现场物与计算机连接既利用此数据。

System:系统性。

不是物理，不是感应头那一类设备。

工厂 1.AppEngine 1.float:看作中间变量，做运算用。

仓库 2.area 2.switch:开关模板
车间 3.intouchviewapp 3.SQLDAta
4.viewengine 4.sequearcer:严格定义脚本模板的顺序
5.winplatform
虽然所有模板都能直接和设备通讯，但设备模板拿数据，面向实际对象，交给中间模板运算。