MVME320B-1輸出卡件
DriveWindow作為遠(yuǎn)程OPC服務(wù)器的客戶端，安裝后即可使用。遠(yuǎn)程端需要在遠(yuǎn)程端PC中安裝DriveOPC或另一個(gè)DriveWindow（包括DriveOPC）。此外，需要配置遠(yuǎn)程端，以便客戶端可以訪問(wèn)遠(yuǎn)程PC、啟動(dòng)DriveOPC和訪問(wèn)DriveOPC。為遠(yuǎn)程使用配置DriveOPC超出了本文檔的范圍。另請(qǐng)參閱：DriveOPC什么是OPC服務(wù)器連接到OPC服務(wù)器遠(yuǎn)程連接高級(jí)信息10-6 DriveWindow 2 2.2幾個(gè)客戶端盡管不需要在本地運(yùn)行幾個(gè)DriveWindow實(shí)例，但可能有其他應(yīng)用程序，您希望能夠同時(shí)使用本地DriveOPC。由于DriveWindow將DriveOPC（SMP.DLL或SMP.EXE）的選擇委派給操作系統(tǒng)，因此將選擇進(jìn)程內(nèi)（DLL）版本。這意味著不可能從多個(gè)客戶端同時(shí)進(jìn)行通信。根據(jù)您的操作系統(tǒng)及其配置方式，可以“遠(yuǎn)程”使用本地服務(wù)器（EXE）版本。通常，遠(yuǎn)程連接到\\localhost或127.0.0.1實(shí)際上連接到同一臺(tái)PC中的本地服務(wù)器。當(dāng)然，所有客戶端都必須能夠進(jìn)行遠(yuǎn)程連接。另一種方法是對(duì)注冊(cè)表進(jìn)行更改，以便進(jìn)程內(nèi)（DLL）版本不再使用。然后，操作系統(tǒng)必須選擇本地服務(wù)器（EXE）版本，然后由使用DriveOPC的所有應(yīng)用程序在本地共享。甚至DriveWindow也將使用EXE版本。注意，本地服務(wù)器（EXE）版本固有地比進(jìn)程內(nèi)（DLL）版本慢。因此，除非絕對(duì)必要，我們不建議強(qiáng)制使用本地服務(wù)器（EXE）版本。如果可能，如果不再需要強(qiáng)制使用本地服務(wù)器（EXE）版本，進(jìn)程中（DLL）版本應(yīng)重新使用。這是通過(guò)恢復(fù)注冊(cè)表中的原始值來(lái)完成的。在對(duì)DriveOPC進(jìn)行任何注冊(cè)表更改之前，請(qǐng)停止使用它的所有程序。進(jìn)行注冊(cè)表更改有兩種方法：?使用注冊(cè)表編輯器編輯注冊(cè)表?使用服務(wù)器的自動(dòng)注冊(cè)和注銷功能如果DriveOPC版本為2.02（包括在DriveWindow 2.01中）或更高版本，則可以使用后一種方法。高級(jí)信息驅(qū)動(dòng)窗口2 10-7 2.2.1編輯注冊(cè)表啟動(dòng)您喜愛(ài)的注冊(cè)表編輯器（例如RegEdit.exe）。UAC可能會(huì)請(qǐng)求您的許可繼續(xù)。高級(jí)信息10-8 DriveWindow 2搜索SMP.DLL（在數(shù)據(jù)中）。如有必要，重復(fù)，直到鍵InprocServer32的默認(rèn)值中包含SMP.DLL（前面有路徑）。將InprocServer32密鑰重命名為，例如，InprocServer32.bak。高級(jí)信息DriveWindow 2 10-9在此更改后，所有在本地使用DriveOPC的應(yīng)用程序?qū)⑹褂帽镜胤?wù)器（EXE），而不是進(jìn)程內(nèi)服務(wù)器（DLL）。2.2.2使用自動(dòng)注冊(cè)功能如果DriveOPC版本為2.02（包括在DriveWindow 2.01中）或更高版本，則這是首選方法。
DriveWindow acting as a client for a remote OPC Server is ready for use after installation. The remote end requires that DriveOPC or another DriveWindow (includes DriveOPC) is installed in the remote end PC. In addition, the remote end needs to be configured, so that clients can access the remote PC, can launch DriveOPC, and can access DriveOPC. Configuring DriveOPC for remote use is out of scope of this document. See Also: DriveOPC What is OPC Server Connecting to OPC Server Remote Connection Advanced Information 10-6 DriveWindow 2 2.2 Several Clients Although there is no need to run several instances of DriveWindow locally, there may be other applications, which you want to be able to use the local DriveOPC simultaneously. Because DriveWindow delegates the selection of DriveOPC (SMP.DLL or SMP.EXE) to the operating system, the in-process (DLL) version will be selected. It means that simultaneous communication from several clients is not possible. Depending on your operating system and how it is configured, it may be possible to use the local server (EXE) version “remotely”. Typically, connecting remotely to \\localhost or 127.0.0.1, actually connects to the local server in the same PC. Of course, all clients must then be able to do remote connection. Another way is to make changes to the registry, so that the in-process (DLL) version is taken out of use. Then the operating system has to select the local server (EXE) version, which is then shared by all applications using DriveOPC locally. Even DriveWindow will use the EXE version then. Note that the local server (EXE) version is inherently slower than the in-process (DLL) version. So, we do not recommend forcing the use of the local server (EXE) version unless absolutely necessary. If possible, the in-process (DLL) version should be taken back in use, if the forcing the use of the local server (EXE) version is not needed any more. It is done by restoring back the original values in the registry. Before making any registry changes concerning DriveOPC, stop all programs using it. There are two methods of making registry changes: ? Editing the registry with a registry editor ? Using self-registering and unregistering features of the servers The latter method can be used if DriveOPC version is 2.02 (included in DriveWindow 2.01) or newer. Advanced Information DriveWindow 2 10-7 2.2.1 Editing Registry Start your favourite registry editor (RegEdit.exe, for example). UAC may ask your permission to continue. Advanced Information 10-8 DriveWindow 2 Search for SMP.DLL (in data). If necessary, repeat, until the key InprocServer32 having SMP.DLL (preceded by path) in its default value. Rename the InprocServer32 key to, for example, InprocServer32.bak. Advanced Information DriveWindow 2 10-9 After this change all applications, which use DriveOPC locally, will use the local server (EXE) instead of the in-process server (DLL). 2.2.2 Using Self-Registering Features This is the preferred method if DriveOPC version is 2.02 (included in DriveWindow 2.01) or newer.
