MVME328S-2控制卡件
數(shù)據(jù)記錄器數(shù)據(jù)記錄器的限制由其在驅(qū)動(dòng)器中的實(shí)現(xiàn)來設(shè)置。DriveWindow也有一些限制。驅(qū)動(dòng)器中數(shù)據(jù)記錄器的最大數(shù)量：DriveWindow 2.30本身沒有限制，但DriveOPC 2.09限制為10。舊版本：2。記錄變量的最大數(shù)目：6。y軸最小值和最大值的最大絕對值：3.40282356779733642751e+038。x軸的最大長度：32700*間隔。雜項(xiàng)DriveWindow 2 9-33 4.1.6最大項(xiàng)目集數(shù)DriveWindow限制項(xiàng)目集窗格中可以顯示的項(xiàng)目集數(shù)，如下所示：?項(xiàng)目集的最大總數(shù)為9。?瀏覽的項(xiàng)目類型只有一個(gè)項(xiàng)目集。?所有故障類型的項(xiàng)目集的最大數(shù)量為1。?所有事件類型的項(xiàng)目集的最大數(shù)量為1。4.1.7對ACS880系列驅(qū)動(dòng)器的支持DriveWindow 2.40（及更新版本）在安裝了DriveDA OPC服務(wù)器（不包括在DriveWindow中）的情況下，對ACS880驅(qū)動(dòng)器系列的支持有限。限制如下：?無系統(tǒng)軟件備份、還原或加載。?應(yīng)避免參數(shù)下載。?僅支持默認(rèn)語言（英語）。?驅(qū)動(dòng)器名稱只能包含拉丁字母。?無動(dòng)態(tài)參數(shù)支持。?數(shù)據(jù)記錄器無法配置，只能控制。?只能顯示數(shù)據(jù)記錄器的六個(gè)通道。?只能監(jiān)控六個(gè)通道（如果可能，使用ACS880監(jiān)控記錄器）。另請參閱：監(jiān)視器和數(shù)據(jù)記錄器使用項(xiàng)目集DriveWindow 2 10-1第10章-高級(jí)信息內(nèi)容1.本地使用時(shí)，DriveWindow的體系結(jié)構(gòu)大致如下：遠(yuǎn)程使用時(shí)，高級(jí)信息DriveWindow 2 10-3 DriveWindow的架構(gòu)大致如下：離線使用時(shí)，大致如下：2.DriveOPC DriveOPC是基于OPC數(shù)據(jù)訪問標(biāo)準(zhǔn)1.0A的OPC服務(wù)器。它實(shí)現(xiàn)了必需的自定義接口和IOPCBrowseServerAddressSpace。通常，OPC服務(wù)器是一個(gè)軟件模塊，它實(shí)現(xiàn)OPC基金會(huì)（www.opcfoundation.org）制定的OPC數(shù)據(jù)訪問規(guī)范。OPC代表“OLE for Process Control”。根據(jù)OPC基金會(huì)：高級(jí)信息10-4 DriveWindow 2，OPC規(guī)范是一種非專有技術(shù)規(guī)范，它定義了一套基于Microsoft OLE/COM技術(shù)的標(biāo)準(zhǔn)接口。OPC標(biāo)準(zhǔn)接口的應(yīng)用使得自動(dòng)化/控制應(yīng)用程序、現(xiàn)場系統(tǒng)/設(shè)備和業(yè)務(wù)/辦公應(yīng)用程序之間的互操作性成為可能。傳統(tǒng)上，每個(gè)軟件或應(yīng)用程序開發(fā)人員都需要編寫自定義接口或服務(wù)器/驅(qū)動(dòng)程序，以與硬件現(xiàn)場設(shè)備交換數(shù)據(jù)。
Dataloggers Limits of dataloggers are set by their implementation in the drives. There are some limits in DriveWindow, too. Maximum number of dataloggers in a drive: No limit in DriveWindow 2.30 itself, but DriveOPC 2.09 limit is 10. Older versions: 2. Maximum number of logged variables: 6. Maximum absolute value of yaxis minimum and maximum: 3.40282356779733642751e+038. Maximum length of the x-axis: 32700 * interval. Miscellaneous DriveWindow 2 9-33 4.1.6 Maximum Number of Item Sets DriveWindow limits the number of item sets that can be present in the item sets pane as follows: ? Maximum total number of item sets is 9. ? There is exactly one item set of type browsed items. ? Maximum number of item sets of type all faults is one. ? Maximum number of item sets of type all events is one. 4.1.7 Support for ACS880 Family of Drives DriveWindow 2.40 (and newer) has limited support for ACS880 family of drives in case using the DriveDA OPC sever (not included in DriveWIndow) is installed. The limitations are as follows: ? No system software backup, restore, or load. ? Parameter download should be avoided. ? Only default language (English) is supported. ? Drive names must contain Latin alphabet only. ? No dynamic parameter support. ? Dataloggers cannot be configured, just controlled. ? Only six channels of a datalogger can be shown. ? Only six channels can be monitored (ACS880 monitorlogger is used if possible). See Also: Monitor and Dataloggers Working with Item Sets DriveWindow 2 10-1 Chapter 10 - Advanced Information Contents 1. Architecture Architecture of DriveWindow, when used locally, is approximately as follows: Advanced Information DriveWindow 2 10-3 Architecture of DriveWindow, when used remotely, is approximately as follows: Architecture of DriveWindow, when used off-line, is approximately as follows: 2. DriveOPC DriveOPC is an OPC Server based on OPC Data Access Standard 1.0A. It implements the obligatory custom interfaces and IOPCBrowseServerAddressSpace. In general, an OPC Server is a software module, which implements OPC data access specification made by OPC Foundation (www.opcfoundation.org). OPC stands for “OLE for Process Control”. According to OPC Foundation: Advanced Information 10-4 DriveWindow 2 The OPC Specification is a non-proprietary technical specification that defines a set of standard interfaces based upon Microsoft’s OLE/COM technology. The application of the OPC standard interface makes possible interoperability between automation/control applications, field systems/devices and business/office applications. Traditionally, each software or application developer was required to write a custom interface, or server/driver, to exchange data with hardware field devices.
