Back

Topic

[KB47]How to identify the protocol .DLL files used in a project

14 years ago
By RM
Options
Print
Applies to:

PcVue all versions.
While the basic content of this article remains valid, details may have changed since it was written.


Summary:

This article explains how to identify from the project configuration files which communication protocol is loaded, which additional .DLL files are loaded by the protocol and the version number of the protocol.


Details:

You may need to identify the protocols used in a project without starting that project (e.g. because you do not have the appropriate version of PcVue). You can do so by checking the configuration and system files as follows:

  • Open the file …\Pcvue\USR\project\C\COMM.DAT in a text editor.

Example of contents of a COMM.DAT file:

VERSION,1,0

BOARD,0,1,5,0,0,53248,816,,,0,0,””

NETWORK,0,0,r1,220,FACTOR ACCESS

0,0,0,NO,0,0,0,5,0,1,0,0,,,0#0#0#0#0,,,0,0,””,0,0,3

EQT,0,0,0,e1,1,DAU_MODBUS,16,0,0,0,0,5,0,1,0,,0,1,0#0#0#0#0,0,,,0,0,””

FRAME,0,0,0,0,t,2,250,125,R,0,Mot E :,65,0,0,1,0,0,0,0,1,1,,,0,0,””

  • The name and version number of the protocol appear in the Network line such as:

NETWORK,0,0,r1,220,FACTOR ACCESS

  • In the example, the protocol number is ‘220’. Close the file COMM.DAT.
  • Open the file …\Pcvue\Bin\PROTOC.DAT in a text editor.
    Caution: Since PcVue version 16, protoc.dat has been removed. It is now possible to find protocols by searching into CimWayProtocols.xml in Bin folder of the PcVue software.

Example of the contents of a PROTOC.DAT file:

# Usage PROTOC.DAT

#

#     Field   Size in Bytes      Description

#                max

#

#       1          8             Key word “PROTOCOL”

#       2          3             <Protocol number>

#       3          2             10 = BLANK environment

#                                20 = New Generation environment

#       4         127          DLL Name in \Bin

#       5         127          Manufacturer’s DLL in the SV\Bin directory

#

# The BLANKNG protocol is allowed to use 13 and any value in the range

# 10000 to 20000 as protocol number

#

PROTOCOL,010,10,CWSIMU.DLL

PROTOCOL,013,20,CWSMNG.DLL

PROTOCOL,015,20,CWELINET.DLL

PROTOCOL,019,10,CWMITSU.DLL

PROTOCOL,021,10,CWSYSWAY.DLL

PROTOCOL,026,10,CWMBP.DLL

PROTOCOL,206,20,CWLN3.DLL

PROTOCOL,209,10,CWESP.DLL

PROTOCOL,211,10,CWAPPL.DLL,APPLICOM.DLL

PROTOCOL,213,10,CWSUCC.DLL

PROTOCOL,220,10,CWTRSMMS.DLL,TRMMSI.DLL

PROTOCOL,222,10,CWETH.DLL,EPCWIN32.DLL

PROTOCOL,223,10,CWFIP.DLL,FPCWIN32.DLL

PROTOCOL,100,10,CWUTE.DLL,UPCWIN32.DLL

PROTOCOL,226,10,CWSBUS.DLL,SCOM32L1.DLL

Warn

Do not modify the file PROTOC.DAT.

  • Check the .DLL files linked to the protocol number. (In the example, the file name for protocol ‘220’ is ‘CWTRMMS.DLL’; but this protocol needs another .DLL file to be loaded: ‘TRMMSI.DLL’, provided by manufacturer.)
Note In the file COMM.DAT, the files named ‘CWxxx’ are PcVue’s .DLL files. The others are manufacturers’ DLL files.
Note

The COMM.DAT file is created when you first configure a protocol.

More about the PROTOC.DAT file

In the 3rd field of the PROTOC.DAT file, you will see these values:

identify_protocol

The C++ API interface is easier to use and new protocols are developed with it.

If you need to know which version of protocol DLL is provided with your installed version of PcVue:

  1. In Windows Explorer, open the Supervisor’s ‘…\Pcvue\Bin\’ folder.
  2. Right-click on the .DLL file for the protocol (e.g. CWTRSMMS.DLL) to open its Properties dialog, then open the Version tab.
  3. In the list of element names, click on ‘ProtocolVersion’ to display the version number of the .DLL in the right-hand pane.

protocol_version_example_dialog

To check for compatibility, you can also display the version of the CIMWAY software under which this DLL was compiled:

  1. In the list of element names, click on ‘Product Version’ to display the version number of CIMWAY in the right-hand pane.
  2. Click on Cancel to close the dialog.

Created on: 08 Oct 2010 Last update: 04 Sep 2024