D2000 OPC Server configuration

This topic describes the configuration of the program D2000 OPCServer for both the server part and client part.

It is possible to manually install D2000 OPC Server within an existing D2000 installation or to install it using an external installer.

Manual installation

The D2000 OPC Server must first be registered in Windows as an OPC server. Registration is done from the command line. The D2000 OPC Server registers by default as Ipesoft.D2000.OPCSserver.opcserver.

This name can be modified (e.g. if it is necessary to register several D2000 OPC Servers in parallel on one communication server, each of which is connected to a different D2000 Server and can be of a different version). In this case, the opcserver.exe program must be copied under a different name (e.g. myprogram.exe) and such a renamed D2000 OPC Server will be registered under the name Ipesoft.D2000.OPCSserver.myprogram.

The procedure for manual installation is as follows:

1. Optional step (if the default name Ipesoft.D2000.OPCSserver.opcserver is not acceptable): copy opcserver.exe under a different name (e.g. myprogram.exe). The copied program should be located in the same subdirectory (bin or bin64) of the D2000 installation directory as the original opcserver.exe.
   
   
2. Starting the OPC server registration: starting the program with the parameter -RegServer e.g.
   opcserver.exe -RegServer
   or, if step 1 has been performed, running the copied program, e.g.
   myprogram.exe -RegServer
   
   
3. It is now possible to run the Windows utility dcomcnfg (Component Services) and verify that the Ipesoft D2000 OPC Server is registered (selected item in the image):
   
4. Then continue creating the D2000 user, which is described in the Configuration chapter.

Installation using an external installer

OPC server configuration
OPC client configuration

OPC server configuration

The name of the computer with running D2000 Server, to which the OPC server will connect, is the only configurable parameter of the OPC server. The computer name is being set during the OPC server installation (the parameter D2000 Server location) or it can be changed by running the OPC server from the command prompt with the parameter /S<name>. The setting will be saved.

For example, the command OPCServer.exe /Sws_main causes that the OPC server will connect to the D2000 Server, which runs on the computer ws_main.

For access of the OPC server to individual objects of the D2000 System, it is necessary to create a user in the D2000 System. The OPC server will log on to the system as the user with defined access rights. The user name must be in the form of OPC_User_<opc_server_name>. The user should have access rights to D2000 System objects that will be available to the OPC client.

OPC client configuration

A client connects to the OPC server by using the parameter ProgID defined during the OPC Server installation. Its form is Ipesoft.D2000.OPCServer.<server_name>. If the OPC client enables to set the OPC standard, select OPCDA 2.0 because OPCDA 1.0 is not supported by the D2000 OPC Server.
An OPC client can support the following types of OPC servers: InProc, Local, Remote. If the OPC client is running on the same computer as the server, set the type Local. If it is running on a remote computer, set Remote and enter the name of the computer with running OPC server into the parameter Host (it depends on OPC client).