MVME328S-1工控模块系统备件
OPC通过定义一个通用的高性能接口消除了这一要求，该接口允许这项工作只完成一次，然后可以被HMI、SCADA、控制和定制应用程序轻松重用。原则上，只要DriveWindow实现了数据访问标准1.0A的强制性自定义界面和IOPCBrowseServerAddressSpace，它就可以作为任何OPC服务器的用户界面。但是，DriveWindow包含许多与驱动器相关的功能，这些功能要求OPC服务器为DriveOPC。DriveOPC包含在DriveWindow的安装中。安装DriveWindow时，也会安装DriveOPC。OPC服务器有两个版本：•进程内服务器（SMP.DLL）。它只能在本地使用。•本地服务器（SMP.EXE）。它在远端使用，但也可以在本地使用。如果客户端程序在本地使用OPC服务器，则可以在连接到OPC服务器时选择要使用的版本。然而，DriveWindow与许多其他客户端程序一样，将选择委托给操作系统，操作系统选择进程内服务器（如果可用）。如果没有，则选择本地服务器。如果需要，可以通过寄存器更改使进程内服务器停止使用。但是，根据您的操作系统及其配置方式，也可以“远程”使用本地服务器（EXE）版本。通常，远程连接到\\localhost或127.0.0.1实际上连接到同一台PC中的本地服务器。当使用DriveOPC进程内服务器（DLL）时，在同一台电脑中同时运行的每个客户端程序都会获得自己的服务器实例。DriveOPC中有一个内部锁，只允许一个实例使用通信库。例如，如果多个DriveWindow同时运行并连接到本地进程内服务器，则只有第一个可以看到驱动器，其他人什么都看不到。自DriveOPC 2.02版（包含在DriveWindow 2.01中）以来，如果库的另一个实例已在运行，则通信库会显示一个消息框。但是，请注意，如果DriveOPC配置为远程使用，则不会显示该消息。注意，本地服务器（EXE）也使用通信库。因此，它也是库中使用内部锁的“客户”之一。高级信息驱动窗口2 10-5在本地或远程（如果配置正确）使用本地服务器（EXE）时，多个客户端可以同时连接和使用服务器。但是，DriveWindow始终检查其他DriveWindow实例是否试图使用同一服务器。如果是这种情况，DriveWindow拒绝连接，并通知用户同时使用，首先是一条详细的错误消息，然后是一个更容易理解的解释：另请参阅：什么是OPC服务器离线OPC服务器2.1远程使用信息由于DCOM涉及安全风险，我们不建议远程使用DriveOPC。DriveOPC没有用户界面，基于COM技术，因此也可以通过DCOM远程使用。DriveWindow也可以连接到远程OPC服务器。但是，需要在本地安装相同的OPC服务器，因为DriveWindow在本地获取可用服务器的列表。
OPC eliminates this requirement by defining a common, high performance interface that permits this work to be done once, and then easily reused by HMI, SCADA, Control and custom applications. In principle, DriveWindow is able to act as a user interface for any OPC Server as long as it implements the obligatory custom interfaces and IOPCBrowseServerAddressSpace of the Data Access Standard 1.0A. 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. There are two versions of an OPC Server: • In-process server (SMP.DLL). It can be used only locally. • Local server (SMP.EXE). It is used at the remote end, but can also be used locally. If a client program uses the OPC Server locally, it can select, which version to use, when connecting to the OPC Server. DriveWindow, however, like many other client programs, delegate the selection to the operating system, which selects the in-process server, if it is available. If not, local server is selected. The in-process server can be taken out of use by a register change, if needed. However, depending on your operating system and how it is configured, it may also 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. When using DriveOPC in-process server (DLL), each client program running simultaneously in the same PC gets its own instance of the server. There is an internal lock within DriveOPC, which allows only one instance to use the communication library. If, for example, more than one DriveWindow are running simultaneously and connect to the local in-process server, only the first one is able to see the drives, others see nothing. Since DriveOPC version 2.02 (included in DriveWindow 2.01), the communication library shows a message box, if another instance of the library is already running. Note, however, that the message is not shown in case DriveOPC is configured to be used remotely. Note that also the local server (EXE) uses also the communication library. So it is also one of the “clients” competing about the use of the internal lock in the library.Advanced Information DriveWindow 2 10-5 When using the local server (EXE) either locally or remotely (if properly configured), several clients can connect and use the server simultaneously. DriveWindow, however, always checks, if other DriveWindow instances are trying to use the same server. If that is the case, DriveWindow refuses to connect, and informs the user about the simultaneous use, first with a detailed error message and immediately after that with a more understandable explanation: See Also: What is OPC Server OfflineOPC Information about OPC Server 2.1 Remote Use Because of security risks involved in DCOM, we do not recommend using DriveOPC remotely. DriveOPC does not have a user interface and is based on COM technology, so it can be used also remotely through DCOM. DriveWindow has the ability to connect to a remote OPC Server, too. It is required, however, that the same OPC Server is also installed locally, because DriveWindow gets the list of available servers locally.
