MVME5500-0161工控模塊備件
由于這些值與測量值相同，因此不進(jìn)行縮放。導出為測量值的數據記錄器與顯示的數據記錄器之間的唯一區別是，前一種情況下的值是未縮放的，但后一種情況中的值是縮放的。趨勢6-124 DriveWindow 2另請參閱：導出趨勢圖子菜單數據記錄器顯示器監視器顯示上下文菜單將趨勢復制到剪貼板處理導出文件如何導出參數DriveWindow 2 7-1第7章-OPC服務(wù)器內容1.什么是OPC OPC服務(wù)器7-2 DriveWindow 2 1.什么是一個(gè)OPC服務(wù)器OPC服務(wù)器是一個(gè)軟件模塊，它實(shí)現了OPC基金會(huì )（www.opcfoundation.org）制定的OPC數據訪(fǎng)問(wèn)規范。OPC代表“OLE for Process Control”。原則上，DriveWindow可以作為任何OPC服務(wù)器的用戶(hù)界面。但是，DriveWindow包含許多與驅動(dòng)器相關(guān)的功能，這些功能要求OPC服務(wù)器為DriveOPC。DriveOPC包含在DriveWindow的安裝中。安裝DriveWindow時(shí)，也會(huì )安裝DriveOPC。DriveOPC也可以通過(guò)DCOM遠程使用。DriveWindow也可以連接到遠程O(píng)PC服務(wù)器。在內部，DriveWindow（自2.10版起）使用另一個(gè)OPC服務(wù)器OfflineOPC。它用于保存離線(xiàn)圖形和工作空間，以及恢復圖形或模擬驅動(dòng)器。OPC服務(wù)器可以有兩種版本：?進(jìn)程內服務(wù)器，即DLL。它只能在本地使用。?本地服務(wù)器，這是一個(gè)EXE文件。它在遠端使用，但也可以在本地使用。通常，DriveWindow在本地使用進(jìn)程內服務(wù)器。OfflineOPC只有一個(gè)進(jìn)程中版本。OPC服務(wù)器未靜態(tài)連接。用戶(hù)必須請求連接。用戶(hù)還必須選擇要連接的服務(wù)器和PC。但是，用戶(hù)不應直接連接到OfflineOPC。用戶(hù)通常也會(huì )請求斷開(kāi)連接。請注意，即使本地沒(méi)有安裝DDCS硬件，也可以將DriveWindow用作遠程客戶(hù)端。另請參閱：DriveOPC OfflineOPC Offline Mode Offline Connection 2.連接到OPC服務(wù)器在DriveWindow中完成的大多數操作都需要連接到OPC Server。雖然原則上，DriveWindow可以作為任何OPC服務(wù)器的用戶(hù)界面，但OPC服務(wù)器必須是DriveOPC。OPC服務(wù)器驅動(dòng)窗口2 7-3注意，您可以打開(kāi)參數文件并使用它，而無(wú)需連接到OPC服務(wù)器。還要注意，當您保存和恢復工作區時(shí)，連接也會(huì )恢復。如果需要，當前連接的OPC服務(wù)器已斷開(kāi)。
Because the values are as measured, they are unscaled. The only difference between a datalogger exported as measured and as shown is that the values in the previous case are unscaled, but in the latter they are scaled. Trends 6-124 DriveWindow 2 See Also: Exporting Trends Graph Submenu Context Menu of Monitor Display Context Menu of Datalogger Display Copying Trends to the Clipboard Handling of Exported Files How to Export Parameters DriveWindow 2 7-1 Chapter 7 - OPC Server Contents 1. What is OPC OPC Server 7-2 DriveWindow 2 1. What is OPC Server 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”. In principle, DriveWindow is able to act as a user interface for any OPC Server. However, DriveWindow contains many drive dependent features, which require that the OPC Server is DriveOPC. DriveOPC is included in the installation of DriveWindow. When you install DriveWindow, you get also DriveOPC installed. DriveOPC can be used also remotely through DCOM. DriveWindow has the ability to connect to a remote OPC Server, too. Internally, DriveWindow (since version 2.10) uses another OPC Server, OfflineOPC. It is used for saving graphs and workspaces for off-line as well as restoring graphs or simulating drives. There can be two versions of an OPC Server: ? In-process server, which is a DLL. It can be used only locally. ? Local server, which is an EXE. It is used at the remote end, but can also be used locally. Normally, DriveWindow uses locally the in-process server. There is only an in-process version of OfflineOPC. The OPC Server is not statically connected. The connection must be requested by the user. The user must also select the Server and the PC, which to connect. However, a user should never connect directly to OfflineOPC. Disconnecting is usually also requested by the user. Note that you can use DriveWindow as a remote client even if you do not have DDCS hardware installed locally. See Also: DriveOPC OfflineOPC Off-line Mode Off-line Connection 2. Connecting to OPC Server Most operations done in DriveWindow require that you have connected to an OPC Server. Although, in principle, DriveWindow is able to act as a user interface for any OPC Server, it is required that the OPC Server is DriveOPC. OPC Server DriveWindow 2 7-3 Note that you are able to open a parameter file and work with it without a connection to an OPC Server. Note also that when you are saving and restoring a workspace, connection is restored, too. Currently connected OPC Server is disconnected, if needed.
