Run Communication Drivers from the command line using DDE

DDE communication between Communication Driver and DDE clients can work only if both driver and client are running in the same user session. It means that the Communication Driver must not be automatically activated. It must run as an application started by the same interactive user that is running the DDE client.

For non DASWRAPPER-based Communication Driver

To run the Communication Drivers listed below, navigate to the corresponding installation folder, and double-click the .exe file.

• OI.ABCIP

• OI.ABTCP

• OI.Gateway

• OI.GESRTP

• OI.ITME

• OI.MBTCP

• OI.MQTT

• OI.SIDirect

• OI.WebSvc

The .exe file is usually located in the below file path:

C:\Program Files (x86)\Wonderware\OI-Server\<OI-Server Name>\bin\OIServer.exe

For example:

To run ABCIP Communication Driver directly from the command line, navigate to C:\Program Files (x86)\Wonderware\OI-Server\OI-ABCIP\bin and double-click ABCIP.exe

To run MBTCP Communication Driver directly from the command line, navigate to C:\Program Files (x86)\Wonderware\OI-Server\OI-MBTCP\bin and double-click MBTCP.exe

For DASWRAPPER-based Communication Drivers

To run the OI Servers not listed, follow the steps below:

1. Retrieve the ClassID and ProgID of the Communication Driver

   1. Ensure that the Communication Driver is configured to run in either Auto-Start or Manual-Start mode (desktop mode).

      Right-click the Communication Driver and select Desktop mode (Must start from command line). If already active , deactivate and activate in desktop mode.

   2. Navigate to the services applet Communication Driver.

      Or, Open the Command prompt, and type: services.msc.

   3. In the Name column, locate the desired Communication Driver.

   4. Right-click the Communication Driver, and select Properties.

      The OI Server Properties dialog appears.

   5. In the General tab, the Path to executable displays the file path of the .exe file. Select to highlight and copy the path.

   Note: The value of path to executable is usually very long, and only a part of the string is shown. Ensure to copy the entire string into the copy clipboard or Notepad.

   A general executable path is given below:

   C:\Program Files (x86)\ArchestrA\OIServerRuntimeComponents\Bin\DASWRAPPER.exe -service /CLSID={<Value of Cass ID>} /ProgID=<Value of Prog ID>

   The value of the ClassID and ProgID are shown right after the parameter /CLSID= and /ProgID= respectively.

   For example: The general executable path of MELSEC Communication Driver is:

   C:\Program Files (x86)\ArchestrA\OIServerRuntimeComponents\Bin\DASWRAPPER.exe -service /CLSID={9EE7EE06-36F9-43D7-989B-4B96117F1A75} /ProgID=OI.MELSEC.1

   

2. Execute the command line to start the Communication Driver manually.

   1. Open the command prompt.

   2. Run the command. Replace the ClassID and ProgID with the values obtained from the above steps.

      "C:\Program Files (x86)\ArchestrA\OIServerRuntimeComponents\Bin\DASWRAPPER.exe" /CLSID={<OIServer Specific CLSID>} /ProgID=OI.Server.x

   It is highly recommended to put the above line in a batch file, to re-run the Communication Driver more readily.