当前位置:首页 >> 信息与通信 >>

OPC Server 用户配置手册


The opc Server installation manual For MS Windows XP SP2/SP3 and Windows Server 2003 SE SP2 1 2 3 Introduction .............................................................................................................................3 Security related settings ...........................................................................................................3 Installation ...............................................................................................................................3 3.1 Preliminary procedures .....................................................................................................4 3.2 Installation from SIC (recommended) ..............................................................................4 3.3 Installation without SIC ....................................................................................................4 3.4 Common metso CR Components .............................................................................4 3.4.1 metso CR Runtime ............................................................................................4 3.4.2 metso CR Type Collection................................................................................4 3.4.3 metso CR BsGUI ..............................................................................................4 3.4.4 metso CR Program Starter ................................................................................5 3.4.5 metso CR Version Info .....................................................................................5 3.5 Required off-side Components .........................................................................................5 3.6 Optional metso CR Components..............................................................................5 3.6.1 metso CR Diagnostics Server ...........................................................................5 3.6.2 metso CR SlotEditor .........................................................................................5 The opc Server configuration..........................................................................................5 4.1 Creating specific user account ..........................................................................................5 4.1.1 Creating 'opc Users' group ................................................................................5 4.1.2 Creating 'opc' user account ...............................................................................7 4.2 Licensing...........................................................................................................................9 4.3 Environment variables ......................................................................................................9 4.4 opc setup file ..........................................................................................................10 4.5 Slot configuration ...........................................................................................................11 4.6 Registration .....................................................................................................................11 4.7 DCOM settings ...............................................................................................................11 4.7.1 For the Server host ...................................................................................................12 4.7.2 For the metso CR opc Server .................................................................14 4.7.3 For the OpcEnum.exe software ...............................................................................15 Starting the metso CR opc Server ........................................................................16 5.1 Via metso CR Program Starter...............................................................................17 5.2 From Command Prompt .................................................................................................17 Connecting to the metso CR opc Server with OPC client ...................................17 Multiple instances..................................................................................................................18 Appendices ............................................................................................................................21 8.1 Starting the metso CR opc Server in simulation mode..................................21 8.1.1 Description ..............................................................................................................21 8.1.2 Configuration ...........................................................................................................21 8.1.3 Startup......................................................................................................................23 8.2 Detailed configuration information.................................................................................23 8.2.1 The metso CR opc Server setup file.......................................................23 8.2.2 Command line parameters .......................................................................................28 8.2.3 Registration / Unregistration ...................................................................................28 8.2.4 Static namespace file ...............................................................................................28 8.2.5 Multiple server instances and names .......................................................................29 8.2.6 Simulation items ......................................................................................................29 1

4

5 6 7 8

8.3 Examples.........................................................................................................................29 8.3.1 Command line parameters examples .......................................................................29 8.3.2 Setup file examples..................................................................................................30 8.3.3 Static namespace file example.................................................................................31 8.4 Runtime diagnostics........................................................................................................32 8.4.1 Metso interface diagnostics ............................................................................32 8.4.2 OPC interface diagnostics .......................................................................................32

2

1 Introduction
This document describes how to install and run the metso CR opc Server on a host based on Windows XP Professional (English) with SP2 / SP3. This document includes also some configuration notes for running opc Server in Windows Server 2003 SE SP2. Please note! The examples presented in this document have to be modified to fit into the system in which opc Server is integrated into.

2 Security related settings
The opc Server can be used on a hardened environment without permanent modifications. There is no need to ease any security settings. But before server configuration it is necessary to start 'Server' service one time. Start Computer Management: menu Start and type compmgmt.msc.

Go to Services and Applications Services. Right click on the 'Server' in the list of services and select Start from pull-down menu.

3 Installation
Some basic knowledge the successful installation. of current Windows version is required for Knowledge of metso CR is required. The network software uses Ethernet multicast sending to communicate with the metso CR. Consult your system administrator to make sure that the multicasting is not filtered off.

3

3.1

Preliminary procedures
Log in as an administrator or make sure you have the administrator privileges. The disk space required by the installation is about 15 Mbytes. The opc Server requires a license to run properly. It can be installed without a license but cannot be run without one. Make sure you have a license file available.

3.2

Installation from SIC (recommended)

Start metso CR Software Installation Center and select role "OPC Server". In this way all required common metso components are installed automatically. The installation via SIC is the most appropriate. You worry about setting up all necessary components separately. SIC also installs some optional metso CR components which can help you to startup and control opc Server.

3.3

Installation without SIC

If the installation is done without using metso CR Software Installation Center, then the common components must be installed separately. The required common components are described in the following chapters.

3.4

Common metso CR Components

3.4.1 metso CR Runtime
The metso CR Runtime package contains files needed for metso communication: lib.dll libPV2.dll onStrExit.dll NCU2 Normally the full opc Server installation package is bundled with these components. If you use light version of opc Server installer you should get required files from installation package in the commonComponents\metso CR Runtime_<version> directory.

3.4.2 metso CR Type Collection
The Type Collection package contains the all_x.y_typ file. It is also included in the full opc Server installation package. If the file is not included into your installation package use the installation package in the commonComponents\metso CR Type Collection_<version> directory.

3.4.3 metso CR BsGUI
The metso CR BsGUI contains the BsTool and the graphical user interface for BsTool. The installation package is in the commonComponents\metso CR BsGUI_<version> directory. 4

3.4.4 metso CR Program Starter
The metso CR Program Starter is used to start and control the running of all the metso CR Application Servers including the opc Server. The installation package is in the commonComponents\metso CR Program Starter_<version> directory.

3.4.5 metso CR Version Info
The Version Info package contains software to collect version information for maintenance purposes. The installation package is in the commonComponents\metso CR Version Info_<version> directory.

3.5

Required off-side Components

Typically all required off-side components are shipped with the full opc Server installation package. If you are using light version of it you should also install the following components: Microsoft Visual C++ 2005 (SP1) Redistributable.

3.6

Optional metso CR Components
installed with the

There are also some optional components, which can be metso CR opc Server. They are described in the following chapters.

3.6.1 metso CR Diagnostics Server
The metso Diagnostics Server (DIA) is used to read and edit data from metso CR nodes. The installation package is commonComponents\metso CR Diagnostics Server_<version> directory. application in the

3.6.2 metso CR SlotEditor
The metso CR SlotEditor is used to create and edit metso CR Program Starter's configuration files. The installation package is in the commonComponents\metso CR SlotEditor_<version> directory.

4 The opc Server configuration
The metso CR opc Server can be launched in two separate modes, the simulation and the standard mode. This Part describes how to configure and run the server in standard mode. For more detailed information about the simulation mode see the appendices.

4.1

Creating specific user account

Log in as an administrator or make sure you have required privileges to perform actions below. In a hardened environment you have to start the Server -Windows system service.

4.1.1 Creating 'opc Users' group
Start Computer Management: menu Start Go to System Tools Local Users and Groups and type compmgmt.msc. Groups. 5

Right click on Groups item and select New Group

from pull down menu.

Fill in into the opening dialog all the values shown below. Field name Value Group name opc Users Group for the opc Server users Description Members <empty>

Click Create and then Close buttons. The 'opc Users' group is now created.

6

4.1.2 Creating 'opc' user account
Start Computer Management: menu Start Go to System Tools Local Users and Groups and type compmgmt.msc. Users.

Right click on Users item and select

from pull down menu.

Fill in into the opening dialog the values shown below. Field name Value User name opc opc user account Full name Description Default opc Server user Password <current valid password> <current valid password> Confirm password User must change password at next logon Unchecked Unchecked User cannot change password Password never expires Checked Account is disabled Unchecked

Click Create and then Close buttons. Double click on just created 'opc' user account to open opc Properties dialog. 7

Go to Member Of tab.

Remove all existing items. Click button.

In the opening Select Groups dialog enter 'Power Users' and 'opc Users' separated by a semicolon and click OK.

'opc Users' and 'Power Users' should appear as seen in the dialog below. For Windows . Click OK.

8

The 'opc' user is created and joined into the required user groups.

4.2

Licensing
a license. (by The licenses are default _law.cfg configured which is

The metso CR opc Server requires in a centralized license file stored in the <D:\>\Shared\Law\cfg\ directory).

The following table illustrates the different license types: License Description OPCClientConn The maximum number of connected OPC clients. TagCount The maximum amount of non-profile tags a given OPC client can connect to. This number is multiplied by 100. PrTagCount The maximum amount of profile tags a given OPC client can connect to. This number is multiplied by 100.

4.3

Environment variables

When running the opc Server from Program Starter the environmental variables can be skipped. When running from Program Starter the same settings are declared in its configuration file (SYS-file). When running without Program Starter (from command line) use Start Settings Control Panel System (Advanced tab) to set the following environment variables: Variable name Variable value Description XD_HW_ADDR xxxx The hardware address is a hex number which eg. e521 or denotes the upper part of the process id reserved 0181 for this PCSor 0ae1. The WIN. This must be unique for each Windows and VME application server. The hardware addresses are second last defined digit must be even and in the _sys file (eg. :s:AB01:AB01_x.y_sys, on the last digit must EAS //CA/bu/AB01_x.y_sys). To ensure that be 1. online- the metso CR bus token address. It must be XD_HW_TOKEN 1-50 This is unique for each Windows in the same virtual bus, ie. the TOKEN+MCAST pair must be unique. The selected value must be documented (e.g. to AB01_x.y_sys) so that the same value is not used in another metso machine. CR XD_HW_MCAST e.g. 239.0.171.1 The network provides a multicast

9

e.g. D:\\Shared\ NCU2\ncu2s_8.7. exe). XD_IP_ADDR e.g. 192.168.0.11 XD_DEBUG 1 XD_STDIO CONSOLE XD_HW_BUS 0 XD_HW_SWITCH 0 XD_NCU_PROG

address in a router. The multicast address is defined in the router cpufile, eg. AX01_x.y_cpu: iplink 3 1 mcast 239.0.171.1 Full path to the NCU2 executable file.

XD_HW_BOND

default

XD_MCLOCK

XD

IP address of the node. Shows basic debug information. Shows console window. SubNetwork id, 0=-2002 compatible. ACN SwitchGroup, 0=undefined. If node is in metsoACN cabinet, value is the lowest HW address of the nodes connected to switch in that cabinet, e.g. 161. Process Bus Ethernet interface names. "default" equals to "_PB1,_PB2". Check Start->Settings>Network metso Connections. XD=Use and Dial-upCR clock, otherwise use the Windows local clock

4.4

opc setup file

Each opc Server instance must have its own configuration file. Typically it is named like ACxx_cpu (ACxx the Server identifier). By default the opc Server runs on slot 5, but it is possible to configure the Server into another slot number. Create the configuration file called AC05_cpu into the opc Server installation directory (D:\\XA\opcServer\) The template for the file can be found in the installation directory ) file and edit the key values as required: [General] ; use corresponding server id Server identifier = AC05 ; full path to the metso types file Types = d:\\shared\types\@_types ; the name of backup to initialize license server if not using licenses locally Disk = :s:AB01 ; full path to the correct metso local license file or the name of the license file on the license server Unlock file = d:\\shared\law\cfg\_law.cfg ; usually <server_id>.nvi NVI file name = AC05.nvi ; usually <server_id>_ Trace file name = AC05_ [Defaults] ; the update rate of the values from metso to opc Server. Rate = 1000 ; to have both readable and writeable access to the items Item access = full This is an example of a basic configuration to start the metso CR opc Server. For full list of the settings in setup file see the appendices. 10

4.5

Slot configuration
about metso CR

s more detailed information Program Starter's configuration file (SYS file), its name and location.

Open Program Starter's configuration file and configure the opc Server into slot 5: Slot 5 PRIORITY=REALTIME STARTDELAY=5 AUTOSTART=NO TITLE=AC05 // Set correct path to the opc Server executable file. PROGRAM=D://XA/opcServer/<OPCSERVER> USERNAME=opc // Type the correct encrypted password. PASSWORD=******* // Specify the full name (with path) of the opc Server setup file. PARAMETERS=-ini D://XA/opcServer/AC05_cpu // Set working directory (typically, installation). WORKDIR=D://XA/opcServer BACKUPDIRS=D://XA/opcServer Note! It is also possible to configure the opc Server into any other slot.

4.6

Registration

To perform further opc Server configuration it has to be registered first. Log in as an administrator or make sure you have required privileges to perform registration. Run Command Prompt (Start Accessories Command Prompt) and go to the opc Server installation directory. Type the following command: OPCServer.exe regserver slot 5 ini AC05_cpu

This command registers the opc Server using setup file AC05_cpu into slot 5. The slot number here (SYS-file).

4.7

DCOM settings

Log in as an administrator or make sure you have required privileges to perform actions below. The DCOM-settings are to be configured for the 1) server host, 2) opc Server and 3) OPCEnum.exe by giving command via Start menu -> Run -> dcomcnfg which opens a window seen in the picture below. 11

4.7.1 For the Server host
Go to Console Root Component Services Computers My Computer.

Right click on My Computer item and select Properties from pull-down menu. It opens My Computer Properties dialog. Go to Default Properties tab and set properties as shown in picture below:

Click Apply and select the Default Protocols tab (The picture below). Remove all other protocols but Connection-oriented TCP/IP. Be sure that they are not needed by any other software. Set the port range for TCP/IP as shown below (5100-5134).

12

Click Apply button and select the COM Security tab. Add the opc Users group into the dialogs opened by pressing each of the four buttons shown in the picture below. In each of these dialogs for opc Users group set both the local and remote permissions as . Set the SYSTEM group local for the Access Permissions. via Edit Default button

Finally click Apply and OK to close My Computer Properties dialog.

13

4.7.2 For the metso CR opc Server
Start Component Services (menu Start Run to start the Server -Windows Service hardened environment. Go to Console Root Component Services Config. and type dcomcnfg). Remember first in a Computers My Computer DCOM

Right click on MetsoAutomation OPC Server item and select Properties from pull-down menu. It opens MetsoAutomation OPC Server Properties dialog. There can be multiple MetsoAutomation OPC Server items. The slot number of the opc Server can be checked from the Local Path value on General tab. See picture below.

Set Authentication Level (General tab) to Connect. Click Apply button. panel select Customize and Select Security tab, press Edit-permissions from opc Users group. Do not deny any permission. All the other permissions are still allowed. Click Apply button.

14

Select Identity tab. Check This user radio button and fill in the values: Field name Value opc User Password <current valid password> Confirm password <current valid password>

Click Apply and OK button to close the dialog.

4.7.3 For the OpcEnum.exe software
Start Component Services (menu Start Go to Console Root Component Services Config. and type dcomcnfg). Computers My Computer DCOM

15

Right click on OpcEnum item and select Properties from pull-down menu. In the OpcEnum Properties dialog set Authentication Level (General tab) to Connect.

Click Apply and OK button.

5 Starting the metso CR opc Server
The opc Server is meant to be run only under the control of the Program Starter. For the testing purposes the startup from the Command Prompt may be used. In this case the Windows Environmental Variables have to be set first as presented earlier in this document. No matter how the opc Server is started the DCOM settings have to be configured on the OPC Client host before the client can connect to the server. See the details in the chapter 6.

16

5.1

Via metso CR Program Starter

After configuring the Program Starter to use certain SYS-file launch Slot Controller software: menu Start Programs metso CR Architecture Program Starter Slot Controller. Start first NCU2 program (typically, slot 16) and then AC05 program (slot 5, as was configured earlier in this document). Notice that the Server can also be configured into another slot number. The NCU2 and opc Server (e.g. AC05) are normally set to startup automatically.

5.2

From Command Prompt

Running the opc Server from the Command Prompt in meant to be used only in testing purposes. Run Command Prompt (Start Programs Accessories Command Prompt) under 'opc' user account (right click on link and choose from pull-down menu). Go to the opc installation directory. Type the following command to run opc Server: OPCServer.exe slot 5 ini AC05_cpu

6 Connecting to the metso CR opc Server with OPC client
Create 'opc' user account which is a member of 'Power Users' group on the Client host. User must have the same password as on the server host. Configure the DCOM settings for the OPC client host. The settings are the same as the settings configured for the opc Server host in section 4.7.1 above. But instead of the opc Users group use opc user. DO NOT forget to set the permissions for the SYSTEM group!!

17

-

Run OPC client under 'opc' user account: o Right click on requisite item (file, link, etc.) and choose down menu. from pull-

o In the Run As dialog select The following user and enter the user name and password: Field name Value User name opc <current valid password> Password

o Click OK button. The opc Server can be connected to (when configured and registered into slot 5) by using its ProgID MetsoAutomation.OPC.Slot05. For more information about ProgIDs see appendices. Remember: o DCOM settings should be configured. o All RPC-services should be running on client host. o TCP port 135 should be opened on client host. Be sure that no firewall blocks it. If the client is run under another identity that opc In some cases the OPC Client is run under another identity than opc e.g custOPC- user. Then both the users (Identity for running opc Server and identity for running OPC client) must be declared both in the opc Server and Client hosts and added into appropriate groups. On the opc Server host this is enough. On the OPC client host both the users must have all least the same permissions as instructed for the DCOM settings of the OPC client host.

-

7 Multiple instances
This chapter describes how to configure two metso CR opc Server instances in one host. It is also possible to configure and run up to 15 instances in the same way.

18

It is recommended to configure each server instructions from chapter 4: 1. Create specific user account.

instance

independently using

1.1. Create 'opc Users' group. This is done only once on the host. 1.2. Create user account(s) that are used running the opc Server and OPC client SW. 1.3. Add the user(s) as member of the required user groups. 2. Order the licenses Each instance should have a license placed in common license file (typically, d:\\shared\law\cfg\_law.cfg). 3. Setup the environment variables into the sys-file. All environment variables are common for each instance of opc Server. 4. Create setup files 4.1. Each instance must have: own configuration file with unique name; unique server identifier; unique names for trace files and NVI-file.

The following two examples describe basic setup files for the opc Servers (AC03 and AC04). These files are to be placed into the opc installation directory. 4.2. Setup file AC03_cpu for the server identified as AC03. [General] ; use corresponding server id Server identifier = AC03 ; full path to the metso types file Types = d:\\shared\types\@_types ; the name of backup to initialize license server if not using licenses locally Disk = :s:AB01 ; full path to the correct metso local license file or the name of the license file on the license server Unlock file = d:\\shared\law\cfg\_law.cfg ; usually <server_id>.nvi NVI file name = AC03.nvi ; usually <server_id>_ Trace file name = AC03_ [Defaults] ; the update rate of the values from metso to opc Server. Rate=1000 ; to have both readable and writeable access to the items Item access = full 19

4.3. Setup file AC04_cpu for the server AC04. [General] ; use corresponding server id Server identifier = AC04 ; full path to the metso types file Types = d:\\shared\types\@_types ; the name of backup to initialize license server if not using licenses locally Disk = :s:AB01 ; full path to the correct metso local license file or the name of the license file on the license server Unlock file = d:\\shared\law\cfg\_law.cfg ; usually <server_id>.nvi NVI file name = AC04.nvi ; usually <server_id>_ Trace file name = AC04_ [Defaults] ; the update rate of the values from metso to opc Server. Rate = 1000 ; to have both readable and writeable access to the items Item access = full 5. Slot configuration Each instance must be configured and run on separate slot number. 5.1. Slot 3 is configured for the server AC03. Slot 3 PRIORITY=REALTIME STARTDELAY=5 AUTOSTART=NO TITLE=AC03 // Set correct path to the opc Server executable file PROGRAM=D://XA/opcServer/<OPCSERVER> USERNAME=opc // Type the correct encrypted password. PASSWORD=******* // Specify the full name (with path) of the opc Server setup file. PARAMETERS=-ini D://XA/opcServer/AC03_cpu // Set working directory (typically, installation). WORKDIR=D://XA/opcServer BACKUPDIRS=D://XA/opcServer 5.2. Slot 4 is configured for the server AC04. Slot 4 PRIORITY=REALTIME STARTDELAY=5 AUTOSTART=NO TITLE=AC04 // Set correct path to the opc Servre executable file 20

PROGRAM=D://XA/opcServer/<OPCSERVER> USERNAME=opc // Type the correct encrypted password. PASSWORD=******* // Specify the full name (with path) of the opc Server setup file. PARAMETERS=-ini D://XA/opcServer/AC04_cpu // Set working directory (typically, installation). WORKDIR=D://XA/opcServer BACKUPDIRS=D://XA/opcServer 6. Registration Each server instance should be commands in installation directory: 6.1. Registration of the server AC03. OPCServer.exe regserver slot 3 ini AC03_cpu registered separately using following

6.2. Registration of the server AC04. OPCServer.exe 7. regserver slot 4 ini AC04_cpu

DCOM settings for the opc server host 7.1. DCOM settings for the Server host are common and should be made once. 7.2. DCOM settings for each server instance should be made separately but they are equal. 7.3. DCOM settings for the OpcEnum.exe software are common and should be made once.

8.

The DCOM settings for each OPC Client host should be made once.

8 Appendices
8.1 Starting the metso CR opc Server in simulation mode
8.1.1 Description
No external metso servers, e.g. NCU, Only local metso communication is available. are required in simulation mode.

The following sections describe how to configure and run the metso CR opc Server in simulation mode step by step.

8.1.2 Configuration

8.1.2.1 Creating specific user account
Create 'opc Users' group.

- Create 'opc' user account and add as a member of 'opc Users' and 'Power Users' groups. 21

8.1.2.2 Licensing
The metso CR opc Server doesn't require any licenses in simulation mode.

8.1.2.3 Environment variables
Set environment variables to see the opc Server console window and some debugging information (Start Settings Control Panel System (Advanced tab)): Variable name Variable value XD_DEBUG 1 XD_STDIO CONSOLE

8.1.2.4 Setup file
Create in the opc Server installation directory (D:\\XA\opcServer\) AC00_cpu file and fill it with the following content (change key values to the correct if necessary): [General] ; Use this parameter to run the server in simulation mode if it is not directly defined in ; command line. Simulation mode = 1 ; use corresponding server id Server identifier = AC00 ; Mandatory! The metso type packet file. Types = d:\\shared\types\@_type This is a basic configuration to start the metso CR opc Server with server id AC00 in simulation mode.

8.1.2.5 Registration
Usually, the simulation opc Server registers itself during installation process. Anyway you are recommended to make registration manually. Log in as an administrator or make sure you have required privileges to perform registration. Run Command Prompt (Start Accessories Command Prompt) and go to the opc Server installation directory. Type the following command: OPCServer.exe regserver sim ini AC00_cpu

8.1.2.6 DCOM settings
DCOM settings for the Server running in simulation mode mostly the same as for standard mode (4.7): DCOM settings for the Server host are common (applied for the host machine) and should be made once. DCOM settings for the opc Server should be done for slot 0. DCOM settings for the OpcEnum.exe the host machine) and should be made once. software are common (applied for

22

-

Remember to configure also the DCOM settings for the OPC Client host.

8.1.3 Startup
Move to the installation directory and run the opc Server (OPCServer.exe) under the 'opc' user account (right click on file and choose from pull-down menu). executable file

OPC Client can be connected to the server with ProgID MetsoAutomation.OPC.Simulation.

8.2

Detailed configuration information

8.2.1 The metso CR opc Server setup file
Setup file follows the structure: [section] key = value

8.2.1.1 [General] section
Key Simulation mode Server identifier Types Disk Module package 1 (2, 3, ...) Unlock file _law.cfg 0 Default value Description Execution mode of the opc Server. A value of zero specifies the use of standard mode, whereas a nonzero value specifies the use of simulation mode. The metso Server LID of the opc Server. The string is limited to a maximum length of four characters. The metso type packet file used by the opc Server. The value of this string parameter is used in initializing the license server. Specifies the module packages the opc Server will load at startup from the metso The name of the file containing the licensing information that the opc Server will use.

OPC1 @_types :s:<BU> (the <BU> is a literal string)

NVI file name

Log server

Update rate limit

<server identifier>.nvi (<server The nonvolatile connection storage file identifier> is the used by the opc Server. parameter specified above) The name of the metso log used for AB01 messages concerning the loading of configuration The lower limit for update rate, in milliseconds, that the opc Server will 100 request from XDCOM. This parameter also specifies the fastest 23

OPC trace

XDCOM trace

Trace file name

Trace file limit Authenticati on level

Impersonatio n level Callback authenticati on level Callback impersonatio n level Static namespace file name

the OPC Group Update Rate. The opc Server doesn't use values lower than 10 for the update rate. The OPC trace output level of the opc errors Server. The alternatives are 'none' (OPC trace off), 'errors' (errors), 'function' (OPC function level The XDCOM trace output level of the opc errors Server. The alternatives are 'none' (XDCOM trace off), 'errors' (errors), 'function' (XDCOM function level trace) and 'item' (XDCOM item level trace). <server The initial part of the name of the trace output ring identifier>_ buffer file pair. The name of first file of the pair (<server will be the initial section suffixed with 'A.log', and identifier> is the the name of the second file of the pair will be the parameter specified initial section suffixed with 'B.log' above) The maximum size of each trace output 1048576 files in bytes. Authentication level required by the opc connect Server from connecting OPC Clients. The alternatives is 'none', 'call', 'packet', 'packet integrity', 'packet level and 'connect'. Impersonation privacy' required by the opc impersonate Server from connecting OPC Clients. The alternatives are 'anonymous', 'identify', 'impersonate' and 'delegate'. Authentication level used by the opc Server in it's notifications to connected OPC Clients. The connect alternatives is 'none', 'call', 'packet', 'packet integrity', 'packet privacy' and 'connect'. Impersonation level used by the opc Server in it's notifications to connected OPC Clients. The impersonate alternatives are 'anonymous', 'identify', 'impersonate' and 'delegate'. Name of the static namespace specification file. A nonempty string as the value disables the Directory Data configuration module based address.dat namespace mechanisms. The namespace instead is read from the specified text file.

8.2.1.2 [Defaults] section
This section defines default values for detailed metso communication parameters. Default Key Description value The default update rate, in milliseconds, requested by the opc Server from XDCOM. A value of zero (Rate = 0) Rate 5000 specifies that the OPC group's update rate will be used as the update rate passed to XDCOM. This parameter has a low limit of <Update rate limit from the [General] section> and a high limit of 25500 ms. 24

Continuous Writes

0

Singleshot Datascan Reads

1

Read Connection timeout fixed Read Connection timeout temporary Write connection timeout fixed Write connection timeout temporary Close connections

3600

120

3600

120

1

Store connections

1

Connection groups Short group reconstruction

0 0

The default write connection mode used by the opc Server when writing to metso. A value of zero specifies the use of single shot write connections, whereas a nonzero value use of Specifies whether the specifiesServerthe opc will use blocking single shot read operations to get valid data from metso if the standard continuous read has not succeeded. With 'Singleshot Datascan Reads' enabled, a blocking single shot read operation will be issued for a metso item if either 1) the item is encountered during the background data scan and the continuous read operation from XDCOM returns a status other than OK or 2) the item is requested through the OPC Interface, the continuous read operation from XDCOM returns a status other than OK and 'Enable blocking reads' is on. A value of zero disables Concerns read connections that are either stored into the NVI dataset or made with test items. Specifies the idle time criteria, in seconds, for closing a continuous read connection (and, in case the connection is in the NVI read connections the connection fromstored Concerns dataset, removing that are neither the NVI into the NVI dataset nor made with test items. Specifies the idle time criteria, in seconds, for closing a continuous read connections Concerns write connection. that are either stored into the NVI dataset or made with test items. Specifies the idle time criteria, in seconds, for closing a continuous write connection (and, in case the connection is in the NVIwrite connections that are neither stored the NVI Concerns dataset, removing the connection from into the NVI dataset nor made with test items. Specifies the idle time criteria, in seconds, for closing a continuous write removal Specifies whetherconnection. of an OPC Item by an OPC Client will cause the closing of the corresponding metso Communication connection. A value of zero disables the closing of connections based on Specifies whether continuous metso read connections made from the opc Server will be stored into the NVI dataset. With the NVI dataset enabled, the opc Server at startup asynchronously activates stored connections. A value of zero disables the storing of continuous read connections, whereas a nonzero value enables it. The metso communication group autosplit parameter passed to XDCOM. A zero value lets XDCOM to use its The minimum time, in ms, that XDCOM waits after a group modification before actually forwarding the 25

Long group reconstruction

Min Resolving delay Max Resolving delay Connection solver priority Number of connection solvers Solver s delay

Solver g delay

Zerobased Tableindex

Mask FB to OPCGood

Enable blocking reads

Item access

metso communication. A zero value lets XDCOM to use its internal default. The maximum time, in ms, that XDCOM waits after a group modification before actually forwarding 0 the change to metso communication. A zero value lets XDCOM to use its internal default. The minimum delay, in ms, that XDCOM waits after name resolving for a given name has failed the first time before 0 making a new resolve attempt. A zero value lets XDCOM to use its internal default. The maximum delay, in ms, that XDCOM waits 0 between name resolving attempts for a given name. A zero value lets The priority level at which the XDCOM background solver 0 helpers run. A zero value lets XDCOM to use its internal default. The number of background helper threads used by XDCOM for name and type queries. A zero value lets 0 XDCOM to use internal default. An itsadditional delay, in ms, used by XDCOM 0 in type queries (to reduce load on application server nodes). A zero An additional delay, in ms, used by XDCOM in name and 0 type queries (to reduce load on application server nodes). A zero value lets XDCOM to use its internal default. The indexing used by the opc Server on its OPC interface in case of metso Fixed Frame Tables being converted to/from SAFEARRAYs. A nonzero value specifies that the opc Server will use 0 zero as the starting index on each dimension of SAFEARRAYs, regardless of the base index of the corresponding dimension in the counterpart Fixed Frame Table, and will do the required index mapping. A value of zero specifies that the opc Server will use identical indexing both on This numeric parameter specifies a filtering to apply against each metso fault bit set before converting the set to an OPC Status. If the value of the parameter is 0, no filtering is 0 applied. If the value of the parameter is other than 0, the fault bit set is ANDed bitwise with the bitwise complement of the mask. Specifies whether the opc Server is allowed to use 0 blocking read operations in metso communication. A value of zero disables blocking reads, whereas a nonzero value enables them. data access level granted The default metso Tag to readonly OPC clients whose user identity cannot be determined. The alternatives is 'none' (no access granted), 'readonly' (only read access granted) and 'full' (full access

26

8.2.1.3 [Client <name>] sections
Contains values specific to a named OPC Client, having name <name>, for a subset of the detailed metso communication parameters. It is possible to define multiple [Client <name>] sections, each with a unique <name>. OPC client is able to write the name into a special data item, internal to the opc Server and unique for each client connection. The name of the item on the OPC interface is client:name. Key Description Zerobased See the Zerobased Tableindex parameter in [Defaults] Tableindex section (8.2.1.2). Mask FB to See the Mask FB to OPCGood parameter in [Defaults] section OPCGood (8.2.1.2).

8.2.1.4 [Identity <id>] sections
Contains metso tag data access rights specific to a user identity <id>. It is possible to define multiple [Identity <id>] sections, each with a unique <id>. It is also possible to define defaults for name specific metso tag data access rights in a special [Identity <Default>] section (where '<Default>' is a literal string). Key Description The default item access rights (see the Item access Default parameter in Zerobased See the Zerobased Tableindex parameter in Tableindex [Defaults] Mask FB to See the Mask FB to OPCGood parameter in [Defaults] section OPCGood (8.2.1.2). Name<N> Item name matching pattern **. <N> - is the numeric suffix *. Item access rights (see the Item access parameter in [Defaults] Access<N> section (8.2.1.2)). <N> - is the numeric suffix. * When determining the access level for a name, the access specified by the first matching group is applied, with groups processed in order of increasing numerical suffix. If no matching group is found, the access specified by the 'Default' key is applied. ** The name matching has two separate modes, a literal substring mode and a regular expression mode. Only one mode is applied against a given matching pattern. The mode is determined by the first character of the matching pattern. A tilde ('~') indicates that the following string is a regular expression. A pattern beginning with any other character is used as a literal substring pattern. Examples can be found in section 8.3.2.3.

8.2.1.5 [Modules] section
Contains item specific values for a restricted set of the detailed metso communication parameters. This section is organized into groups of 'key = value' pairs. Each group consists of a name matching pattern (see notes in 8.2.1.4) and settings to be applied for items with names matching the pattern. Each group shall be identified by a numeric suffix. The suffix shall be present in each of the group's key strings. Key Description Name<N> Item name matching pattern. <N> - is the numeric suffix.

27

Rate<N> Continuous Writes<N>

See the Rate parameter in [Defaults] section (8.2.1.2). <N> - is the numeric suffix. See the Continuous Writes parameter in [Defaults] section

8.2.2 Command line parameters
The opc Server supports the command line parameters and switches listed below: Parameter / Switch Effect -ini <filename> use <filename> as setup file; -sim run the opc Server in simulation mode; -regserver force the registration, exit after registration; -unregserver unregister the opc Server and exit; -slot <slot number> assign the opc Server to specified slot number. It is possible to use few command line parameters simultaneously. Examples can be found in section 8.3.1.

8.2.3 Registration / Unregistration
Registration / Unregistration can be done only under Windows user account with write access to registry. The opc Server must be registered into Windows its services. before the OPC client can utilize

During the setup the installation software registers simulation opc Server with ProgID MetsoAutomation.OPC.Simulation (information about ProgID can be found in 8.2.5). On each startup the opc Server examines the local registry to determine whether the registration of the server is already done for the corresponding ProgID/ClassID. If the required entries do not exist the server tries to perform the registration automatically. It is also possible to force the opc Server registration on corresponding slot specifying regserver and slot command line parameters. The default slot number is set to 5 when not defined in the command line. When the OPC client starts the opc Server the same setup file that has been defined at the registering process (-ini parameter) will be used. The default setup file is opc.ini which is located at the installation directory. Unregistration process is done using unregserver and slot command line parameters. Examples can be found in section 8.3.1.1.

8.2.4 Static namespace file
A static namespace specification file contains 0 ... n tag names, one name per line. Tag name should be without whitespaces; otherwise it will be truncated after the first whitespace. Example can be found in section 8.3.3.

28

8.2.5 Multiple server instances and names
It is possible to run multiple instances of the opc Server on a given machine. Each instance appears as a separate metso server on a metso network, except an instance running in simulation mode as such an instance is not a part of a metso network. Each server instance is logically tied to a metso slot number, even if the instance is running in simulation mode or is not started by the metso program starter. The slot is identified by a slot number within the range 0...15. It is not possible for two executing server instances to have the same slot id. An instance of the opc Server tied to slot number 0 runs in simulation mode only. An instance tied to a slot number within the range 1...15 runs either in standard or in simulation mode. As each possible server instance available on a given machine needs to be identifiable by an OPC client, each instance has its own ProgID and ClassID. There are 16 separate {ProgID , ClassID} pairs, each corresponding to a specific slot number. The ProgIDs for slot numbers 1...15 are of format MetsoAutomation.OPC.Slot<ss>, where <ss> is one of 01, 02,...15, according to the slot number of the server. The ProgID for slot number 0 is MetsoAutomation.OPC.Simulation.

8.2.6 Simulation items
The opc Server provides simulated data items for all metso data types: char; char16; uns8; uns16; uns32; uns64; int8; int16; int64; float; double; bool8; bool16; fails; time; ana; intl; bin; anaev; intsev; intlev; binev; txt16; txt1024; cha_37; ana_4; ana_34; ins_4; ins_34; inl_4; inl_34; bin_34; ise_4; ise_34; ile_4; ile_34; bne_4; bne_34. int32; ints; cha_7; bin_4;

For each data type there are both a read only item and a read/write item. The content of the read only items is changed (increment with wraparound) with a cycle of 1 second; however it is not updated when no OPC client could detect the change. The OPC test item name of each item is formed by combining a fixed prefix, a middle part indicating the writability of the item and as a suffix the name of the item's metso type. The prefix is opcsimulation:<lid>:, <lid> is the metso server identifier of the opc Server. The writability component of the name is ro: for read only items and rw: for read/write items. As an example, the OPC item name of a read-only test item of metso type ints on a server with identifier AC01 will be opcsimulation:AC01:ro:ints. Simulation items are always visible in the opc Server namespace for any connected OPC client.

8.3

Examples

8.3.1 Command line parameters examples

8.3.1.1 Registration / Unregistration
Command line parameters regserver Effect Registers the opc Server with ProgID

29

regserver

slot 3

regserver slot 9 d:\AC09_cpu unregserver unregserver unregserver slot 2 sim

ini

MetsoAutomation.OPC.Slot05. (Slot number is 5. When the server will be run by OPC client, the setup file name will be <full path to installation directory>\opc.ini). Registers the opc Server with ProgID MetsoAutomation.OPC.Slot03. (Slot number is 3. When the server will be run by OPC client, the setup file name will be<full path to installation directory>\opc.ini). Registers the opc Server with ProgID MetsoAutomation.OPC.Slot09. (Slot number is 9. When the server will be run by OPC client, the setup file name will be d:\AC09_cpu). Unregisters the opc Server with ProgID MetsoAutomation.OPC.Slot05. Unregisters the opc Server with ProgID MetsoAutomation.OPC.Slot02. Unregisters the opc Server with ProgID MetsoAutomation.OPC.Simulation.

8.3.1.2 Examples with other command line switches
Command line parameters sim Effect Starts the opc Server with ProgID MetsoAutomation.OPC.Simulation in simulation mode. (Slot number is 0, setup file name is <full path to installation directory>\opc.ini). Starts the opc Server with ProgID MetsoAutomation.OPC.Slot04 in simulation mode. (Slot number is 4, setup file name is <full path to installation directory>\opc.ini). Starts the opc Server with ProgID MetsoAutomation.OPC.Slot11 in standard mode. (Slot number is 11, setup file name is d:\\test.conf).

slot 4

sim

slot 11 ini d:\\test.conf

8.3.2 Setup file examples

8.3.2.1 Basic setup file for standard mode
[General] ; Mandatory! The metso type packet file. Types = d:\\shared\types\@_type ; Mandatory! The name of the license file. Unlock file = d:\\shared\law\cfg\_law.cfg

8.3.2.2 Basic setup file for simulation mode
[General] ; Use this parameter to run the server in simulation mode if it is not directly defined in command ; line. Simulation mode = 1 ; Mandatory! The metso type packet file. Types = d:\\shared\types\@_type 30

8.3.2.3 Custom setup file for standard mode
[General] ; The metso server LID of the opc Server will be AC02. Server identifier = AC02 ; Mandatory! The metso type packet file. Types = d:\\shared\types\@_type ; During startup the opc server will try to load Directory Data configuration module 'DIR1' ; and generate namespace according to its contents. Module package 1 = DIR1 ; Mandatory! The name of the license file. Unlock file = d:\\shared\law\cfg\_law.cfg ; The metso Backup Server LID from which will be loaded package 'DIR1'. Log server = PB01 ; The OPC trace output level will be off. OPC trace = none ; All possible XDCOM trace information will be output. XDCOM trace = item ; Load to namespace additional tag names from file <full path to the server installation directory>\tagnames.dat. Static namespace file name = tagnames.dat [Defaults] ; No access granted to the metso tags by default. Item access = none ; Custom tag access policy for OPC client running under user identity ' TESTPC\User1'. [Identity TESTPC\User1] ; The default access rights to all metso tags for this client will be readonly. Default = readonly ; This client have no access to tag pr:TEST.F:tagN. Name1 = pr:TEST.F:tagN Access1 = none ; This client can read and write tags starting with pr:TEST.F (except pr:TEST.F:tagN). Name2 = ~pr:TEST.F Access2 = full ; This pattern will not be applied and access to tag pr:TEST.F:tagM will be full. Name3 = pr:TEST.F:tagM Access3 = none

8.3.3 Static namespace file example
pr:ALLSUPOPCTYP.F:bool8_val pr:ALLSUPOPCTYP.F:ints_val:s pr:ALLSUPOPCTYP.F:ints_val:f pr:OTHERFUNCBLOCK.F:intlev_val:intlstat:l pr:OTHERFUNCBLOCK.F:intlev_val:intlstat:f pr:OTHERFUNCBLOCK.F:intlev_val:intltime pr:TABLE_EXAMPLES:ana_7_table:elem:a pr:TABLE_EXAMPLES:ana_7_table:elem:f pr:TABLE_EXAMPLES:cha_37_table

31

8.4

Runtime diagnostics

The OPC Server publishes diagnostic information accessible through the metso communication. The OPC Server includes a trace mechanism for tracing OPC interface communication and XDCOM interface communication. The trace mechanism has the following granularity options, switchable without restarting the server and controlled by the relevant setup file parameters and the corresponding diagnostic items: OPC trace off / Errors / OPC function level trace / OPC item level trace XDCOM trace off / Errors / XDCOM function level trace / XDCOM item level trace

The OPC and XDCOM trace levels are independent of each other. Error level tracing includes timestamp, possible related interface function name plus possible client identity information. The error level trace includes errors occurred at the interface in question, as well as internal errors. Having either trace at a level other than 'none' enables the tracing of these internal errors. Function level trace additionally includes timestamp, interface function name plus possible client identity information for successful interface function calls. Item level trace additionally includes item names and values. The trace output is shown in the user interface if the trace monitoring window is activated and/or into ring buffer file pair with adjustable maximum size if requested in the setup file (opc.ini). If the OPC Server is running in standard mode, the trace will additionally be output.

8.4.1 Metso interface diagnostics
The XDCOM Library publishes and maintains the diagnostic tags pertaining to the metso Server aspect of the OPC Server.

8.4.2 OPC interface diagnostics
In standard mode the OPC Server publishes diagnostic data pertaining to the OPC interface. All read only OPC interface diagnostic names are prefixed with di:<lid>:opc: where <lid> is the server identifier acquired from the [General] section of the setup file. All read/write OPC interface diagnostic names are prefixed with sn:<lid>:opc:. Besides the actual value, the OPC Server also maintains the timestamp on those diagnostic items whose type include a timestamp field (intlev, anaev).

8.4.2.1 OPC interface general diagnostic items
txt512 versioninfo (read only) Version info of the OPC Server file and 3rd party libraries. intl trace:opc (read/write) intl trace: (read/write) The trace levels of the OPC server. The effective trace levels are controlled by the most recent changes either to these items or to the corresponding parameters in the setup file. In these items, a value of 0 corresponds to 'none' in the setup file, 1 to 'errors', 2 to 'function' and 3 to

32

8.4.2.2 OPC interface summary diagnostic items
intlev client:slookup (read only) intlev client:flookup (read only) intl client:sread (read only) intl client:fread (read only) intl client:swrite (read only) intl client:fwrite (read only) Total number of successful/failed lookups, reads and writes on client connections since the startup of the OPC Server. Every time an OPC item is validated, added it is considered as a lookup. Reading/refreshing an item is considered as a read. Writing an item is a write. Counters

intl client:bytesread (read only) / NOT IMPLEMENTED YET intl client:byteswritten (read only) / NOT IMPLEMENTED YET Total amount of data read/written through client connections since the startup of the OPC

intlev client:nclients (read only) Number of active client connections. A single client may have multiple active connections. intlev client:agroups (read only) intlev client:dgroups (read only) Total number of active/deactive OPC groups in active client connections. intlev client:aitems (read only) intlev client:ditems (read only) Total number of active/deactive OPC items in active client connections.

8.4.2.3 OPC interface client connection specific diagnostic items
In the item names of this subsection the notation <N> represents a number logically bound to the active OPC client connection in question. The number shall be unique among the client connections active at a given moment. The range of the number shall be 1 ... 999. A number bound to an active client connection is released for reuse at the termination of the client connection. At release time the number is timestamped. A released number is not reused until all numbers in the range have been used once. When reusing a released number, the number with the oldest timestamp shall be selected the notation <G> represents a string logically bound to an OPC group, unique among the groups on a given client connection, and based on the name of the group (max 31 characters). Longer name will be truncated to 31 characters. If necessary, the last characters shall be modified to keep the string unique txt128 client:<N>:userid (read only) The user id, if available, of the client; otherwise 'unknown'. 33

txt128 client:<N>:appname (read only) The name, if available, written by the client to the client:name OPC item otherwise 'unknown'. txt128 client:<N>:stme (read only) The name, if available, set by the client using IOPCCommon::SetClientName otherwise 'unknown'. intlev client:<N>:slookup (read only) intlev client:<N>:flookup (read only) intlev client:<N>:aitems (read only) intlev client:<N>:ditems (read only) Perclientconnection counts, see corresponding server level items. intlev client:<N>:g:<G>:refresh (read only) Number of refresh requests received by the group. intlev client:<N>:g:<G>:slookup (read only) intlev client:<N>:g:<G>:flookup (read only) intlev client:<N>:g:<G>:aitems (read only) intlev client:<N>:g:<G>:ditems (read only) Pergroup counts, see corresponding client or server level items. intlev client:<N>:g:<G>:active (read only) 1 if the group is active, 0 otherwise. intlev client:<N>:g:<G>:rate (read only) Requested update rate of the group. intlev client:<N>:g:<G>:timebias (read only) Timebias of the group. anaev client:<N>:g:<G>:deadband (read only) Specified deadband of the group. intlev client:<N>:g:<G>:lcid (read only) Locale id of the group.

34


相关文章:
OPC配置说明
OPC配置说明_计算机硬件及网络_IT/计算机_专业资料。OPC 配置说明书步骤 1 2 ...的OPC Client的机器名 4 在OPC Client上创建一个mngr帐户,密码与OPC Server的...
远程OPC服务器连接配置手册
4、在 OPC 服务器上,还要回到“组件服务”界面,打开 DCOM 配置,找到注册的 OPC 服务 器的名称选项,打开它的属性。 -> 启用交互式用户(确保由客户机主动启动 ...
OPC通讯DCOM配置手册
OPC DCOM 配置 用户操作说明书 1 第一节 进入 DCOM 配置程序 1、运行 dcom...OpcEnum.exe 安装位置+空格+//regserver 回车确定 3、配置 opc server 1)、...
opc通讯配置手册
opc通讯配置手册_IT/计算机_专业资料。OPCClient 远程连接 OPC 服务器配置手册一,操作系统用户 1、在 OPC 服务器上用 Administrator 用户建立一个拥有管理员权限的...
ABB AC800F OPC Server配置方法
ABB AC800F OPC Server配置方法_计算机软件及应用_IT/计算机_专业资料。ABB ...ABB OPC Server 5.15.01 暂无评价 6页 免费 OPC Server 用户配置手册... ...
OPC用户使用手册
OPC用户使用手册_IT/计算机_专业资料。MCGS OPC 设备使用说明 1. 组态环境的使用...服务器设置: OPC 服务器设置: 1.选择基本属性页中的OPC服务器选项,点击“ ”...
OPC服务器用户手册
OPC服务器用户手册_计算机硬件及网络_IT/计算机_专业资料。OPC 客户端开发工具包...OPC 客户端还可以配置数据的更新速率。在一个标签组中,用户可以定义一个或多 ...
现场OPC SERVER服务器与OPC 客户端远程连接设置方法
3.2 OPC SERVER 服务器上的防火墙做如下设置:声明:如果中控室工控机不需要防火墙的话,可以直接点击关闭。 如果现场企业用户不同意关闭防火墙再进行以下操作。 在 ...
OPCServer网络访问配置
OPCServer网络访问配置_IT/计算机_专业资料。OPC ...对于每个参与 OPC 通信的用户或组,均应赋予其本地...WinCC中文手册-OPC服务器... 80页 1下载券 基于...
OPC远程连接系统配置手册
OPCClient 远程连接 OPC 服务器操作系统配置手册 ---吕林波 2008-8-6 一,操作系统用户 1、在 OPC 服务器上用 Administrator 用户建立一个拥有管理员权限的用户...
更多相关标签: