MVME51005E-0161输出卡件
•浏览树窗格中没有状态刷新。•数据记录器无状态刷新。•清除所有上载的数据记录器。所有未保存在驱动器中的设置均设置为默认值。•打开的参数文件已关闭。请注意，可能会显示保存未更改更改的请求。•浏览树窗格被清除。•将清除项目集。请注意，所有锁定的项目都已解锁，不会有任何项目在线。但是，不会删除用户项集中的模板。请注意，断开连接不会关闭打开的备份或加载包。OPC服务器7-12 DriveWindow 2注意，某些DriveWindow操作需要重新启动驱动器。重新启动DriveWindow启动的驱动器会导致OPC服务器的内部断开和重新连接。断开连接的副作用仍然有效，但重新连接会将驱动器带回浏览树窗格。然而，它们的顺序和可能的节点地址可能已经改变。此外，所有驱动器子分支都将折叠。OPC服务器DriveWindow 2 7-13 5.1.1自动断开OPC服务器当您：•打开图形文件，使DriveWindow脱机时，OPC服务器将自动断开。•恢复未连接到当前连接的OPC服务器的工作区。•关闭DriveWindow。•注销或关闭Windows操作系统。OPC服务器7-14 DriveWindow 2自DriveWindow版本2.11以来，您必须确认在前两种情况下自动断开连接，例如：另请参阅：什么是OPC服务器连接到OPC服务器6。使用DriveDA DriveDA是另一种设计用于处理ACS880系列驱动器的OPC服务器。不过，DriveWindow中不包含此功能。您需要安装包含DriveWare的产品（如Drivecomposer pro），然后才能将其与DriveWindow一起使用。除了能够本机连接到ACS880系列驱动器之外，DriveDA还可以连接到另一个OPC服务器。客户端程序将这种OPC服务器的所有设备视为DriveDA的设备。此功能允许您在DriveWindow中混合使用ACS800和ACS880系列驱动器。但是，DriveWindow仅对ACS880系列驱动器提供基本支持。有几个功能缺失或不工作。OPC服务器DriveWindow 2 7-15如果安装了DriveDA，则在选择要连接的OPC服务器时，您会在“选择OPC服务器”对话框中看到它。如果您想连接到DriveDA，请选择ABB。DriveDA而不是ABB.SMP。如果您只有ACS880系列驱动器，而您的电脑中没有DDCS通信硬件，则每次连接到DriveDA时，您可能会对有关它的消息感到厌倦。有两种方法可以消除此消息。如果您偶尔需要连接到ACS800系列驱动器，建议您在dwc_def文件中添加或编辑[OPC]部分。ini:[OPC]Remote=1文件位于：•Documents and Settings\All Users\Application Data\DriveWare（WinXP）或•Program Data\DriveWare
• No status refresh in the browse tree pane. • No status refresh of dataloggers. • All uploaded dataloggers are cleared. All those settings, which are not preserved in a drive, are set to their default values. • Open parameter file is closed. Note that a request for saving unchanged changes may be shown. • The browse tree pane is cleared. • The item sets are cleared. Note that all locked items are unlocked and there will be no item on-line. However, templates in user item sets are not deleted. Note that disconnecting does not close an open backup or loading package. OPC Server 7-12 DriveWindow 2 Note that some DriveWindow operations require restarting of a drive. Restarting a drive initiated by DriveWindow does an internal disconnecting and reconnecting of the OPC Server. The side effects of disconnecting are still valid, but re-connecting brings back the drives into the browse tree pane. Their order and possibly node addresses may have changed, however. Also, all drive sub-branches will be collapsed. OPC Server DriveWindow 2 7-13 5.1.1 Automatic disconnecting of the OPC Server The OPC Server is automatically disconnected when you: • Open a graph file, which puts DriveWindow off-line. • Restore a workspace, which was not connected to the currently connected OPC Server. • Close DriveWindow. • Log off or shut down Windows operating system. OPC Server 7-14 DriveWindow 2 Since DriveWindow version 2.11 you have to confirm the automatic disconnection in the two first cases, e.g.: See Also: What is OPC Server Connecting to OPC Server 6. Using DriveDA DriveDA is another OPC Server designed to handle ACS880 family of drives. It is not included in DriveWindow, however. You need to install a DriveWare product (such as Drive composer pro) that contains it before you can use it with DriveWindow. In addition to be able to connect natively to ACS880 family of drives, DriveDA can connect to another OPC Server. All devices of such an OPC Server are seen by the client program as devices of DriveDA. This feature allows you to operate with a mixture of ACS800 and ACS880 families of drives in DriveWindow. However, DriveWindow has only a basic support for ACS880 family of drives. There are several features missing or not working. OPC Server DriveWindow 2 7-15 If DriveDA is installed, you see it listed in the Select OPC Server dialog box when selecting the OPC Server to connect to. If you want to connect to DriveDA, select ABB.DriveDA instead of ABB.SMP. If you have ACS880 family of drives only and you have no DDCS communication hardware in your PC, you may get tired about the message complaining about it each time you connect to DriveDA. There are two ways to get rid of this message. If you occasionally need to connect to an ACS800 family of drive, we recommend that you add or edit [OPC] section in the file dwc_def.ini: [OPC] Remote=1 The file is located in: • Documents and Settings\All Users\Application Data\DriveWare (WinXP), or • Program Data\DriveWare
