Type of OPC server architecture used:

• Single-threaded apartments (STA) - all OPC calls must be made from a single thread (task) of the client process.

• Multithreaded apartments (MTA) - OPC calls can be made from multiple tasks of the client process.

OPC servers can support STA, MTA, or both architectures. In some cases, this is even a licensing restriction, e.g. in the case of the Rockwell RSLinx OPC server:

• RSLinx Single Node, RSLinx OEM, RSLinx Professional - supports only STA and local connections of one OPC client

• RSLinx Gateway - supports MTA and local/remote connections of multiple OPC clients

Note: Currently, the default and recommended MTA architecture is MTA, in the past the D2000 KOM operated in STA mode.
Note: After changing this parameter, it is necessary to restart the D2000 KOM process.

-

MTA

OPC HDA server name (ProgID), if it is available. Leave empty if OPC HDA functions are not to be used.

-

Sets the NumItems parameter for the synchronous reading of historical "raw" values. The implicit value 0 (zero) means all values in the given interval.

-

0

Authentication level used when establishing a connection to the OPC server. The OPC standard defines the following levels:

• RPC_C_AUTHN_LEVEL_DEFAULT (0)

• RPC_C_AUTHN_LEVEL_NONE (1)

• RPC_C_AUTHN_LEVEL_CONNECT (2)

• RPC_C_AUTHN_LEVEL_CALL (3)

• RPC_C_AUTHN_LEVEL_PKT (4)

• RPC_C_AUTHN_LEVEL_PKT_INTEGRITY (5)

• RPC_C_AUTHN_LEVEL_PKT_PRIVACY (6)

Note: The default value RPC_C_AUTHN_LEVEL_CONNECT (2) may no longer be sufficient. Microsoft has implemented security hardening to address the security issues described in CVE-2021-26414. See "KB5004442—Manage changes for Windows DCOM Server Security Feature Bypass (CVE-2021-26414)" for more details.
Recommended values when using DCOM (communication with a remote OPC server) are RPC_C_AUTHN_LEVEL_PKT_INTEGRITY (5) and RPC_C_AUTHN_LEVEL_PKT_PRIVACY (6).

-

2

Starts the sequencing of calling the function Refresh2 of interfaces Async I/O 2.0 and Async I/O 3.0. The calling executes after the first calling has been finished (after it gets the values).

YES/NO

NO

Failed OPC group activations will be attempted again after a delay specified by the parameter "Group reactivation delay".

YES/NO

YES

A delay after which a failed OPC group activation is repeated if repetition is enabled by the parameter "Repeat failed group activation".

sec

30

When an OPC group activation fails, KOM disconnects from the OPC server and reestablishes a connection. The parameter is relevant in a configuration of redundant OPC servers (after a disconnect from an OPC server, a reconnect to an alternate OPC server follows, where group activation may be successful).

YES/NO

NO

Period of executing the call of GetGroupState of the interface IOPCGroupStateMgt. This synchronous call is repeated periodically to detect the problems that could occur in communication with the OPC Server.

sec

10

All the errors returned by calling the "GetGroupState" function of interface IOPCGroupStateMgt are considered to be fatal (they will result in a disconnect from the OPC server and in a reconnect, or in a restart of the KOM process).

An example of an error message returned by "GetGroupState":
WARNING: Siemens.TXP.OPC caused COM/OPC error 80010108H on IOPCGroupStateMgt::GetState(), Error string: The object invoked has disconnected from its clients.

YES/NO

NO

Allows stopping the KOM process when a fatal error occurs in communication. See the Note.

YES/NO

NO

Only the active KOM process (i.e., the active instance connected to the HOT server) communicates with the OPC server. The KOM process, which becomes passive (by changing the active instance or switching the redundancy), closes the connection to the OPC server.
Note: This parameter allows the reduction of the OPC server load in redundant D2000 systems, as well as solving problems with the license limitation on the number of OPC clients.

YES/NO

NO

When terminating the KOM process, a correct disconnection from the OPC server is performed. Setting the parameter to NO can help speed up the termination of the KOM process in configurations with a large number of OPC I/O tags

YES/NO

YES

The parameter causes the first value of each I/O tag received after connecting to the OPC server to be ignored if it is invalid (it has a 'BAD' status). This parameter was implemented to suppress undesirable behavior of the OPC.SimaticNET server.

YES/NO

NO

Allows verifying the value after the recording by synchronous reading.

YES/NO

NO

Allows writing data into the OPC Server only by the synchronous interface IOPCSyncIO2.

YES/NO

NO

Using the Async I/O 3 option allows writing data by the WriteVQT function of the IOPCASyncIO3 interface (i.e., the write that transfers the quality and the timestamp together with the value).

YES/NO

NO

Activates the debug list. It increases the amount of information about the communication operation. It is recommended to use it only for the detection of problems and debugging.

YES/NO

NO

Special mode for communication with OPC Servers made by the Merz company. The conversion to/from MS DOS Date Time Format (2 x WORD) is used for values of TiA and ToA type.

YES/NO

NO

A delay artificially inserted between the AddItems calls to slow down the initialization phase.

ss:mss

0

An integer value of the "ERROR" state for conversion into Qi - quaternary input.

0,1,2,3

3

An integer value of "OFF" state for conversion into Qi - quaternary input.

0,1,2,3

2

An integer value of "ON" state for conversion into Qi - quaternary input.

0,1,2,3

1

An integer value of "TRANS" state for conversion into Qi - quaternary input.

0,1,2,3

0

If the quality of the OPC item changes to "BAD", the value of the I/O tag will be valid with a Weak flag.

YES/NO

NO

Blocks repeated calls of AddItems, should adding a specific I/O tag address fail.

YES/NO

NO

Activates all the items of a group by a single call. It can speed up the OPC communication start.

YES/NO

NO

All calls of the Write and Refresh2 functions are registered as separate transactions. If they do not finish (successfully or unsuccessfully) within this timeout, the error message will occur in the trace file of communication.

sec

120

Timeout, which delays repetitions of failed operations:

• creation of AddGroup,

• creation of AddItems (see the SA protocol parameter),

• repeated connection to the OPC Server after it has been stopped, failed, or disconnected,

• creation of groups and items after repeated connection to the OPC Server.

sec

5

Enables synchronous reading of the item value before the writing if the KOM process does not know the item data type (i.e., if there is a default value of data type "Empty/Default (VT_EMPTY)" and if the value must be written).

YES/NO

YES

Address of OPC Item (OPC Item ID), which contains the OPC server or OPC group error status (e.g., depending on the state of communication). An I/O tag with this address must also be configured.
If the status reports an error, it will affect the values of all I/O tags on the station (they will have the Weak flag set). The Status Item Inverted Operation parameter specifies what value corresponds to the error status.

-

-

Interpretation of the OPC Item Status Item Name with an error status of the OPC server or the OPC group.
The NO value means that the False or 0 values mean the correct state, and True or non-zero values mean an error.
The YES value means that the False or 0 values mean the error state, and True or non-zero values mean the correct state.

YES/NO

NO

Mapping the "Non Specific " OPC DA quality flag into the attributes of the I/O tag value.

None, FA, FB, FC, FD, FE, FF, FG, FH, FI, FJ, FK, FL, FM, FN, FO, FP

None

Mapping the "LocalOverride" OPC DA quality flag into the attributes of the I/O tag value.

Mapping the "Config Error" OPC DA quality flag into the attributes of the I/O tag value.

Mapping the "Not Connected" OPC DA quality flag into the attributes of the I/O tag value.

Mapping the "Device Failure" OPC DA quality flag into the attributes of the I/O tag value.

Mapping the "Sensor Failure" OPC DA quality flag into the attributes of the I/O tag value.

Mapping the "Last Known" OPC DA quality flag into the attributes of the I/O tag value.

Mapping the "Comm Failure" OPC DA quality flag into the attributes of the I/O tag value./td>

Mapping the "Out Of Service" OPC DA quality flag into the attributes of I/O tag value.

Mapping the "Waiting For Initial Data" OPC DA quality flag into the attributes of I/O tag value.

Mapping the "Last Usable" OPC DA quality flag into the attributes of the I/O tag value.

Mapping the "Sensor Cal" OPC DA quality flag into the attributes of the I/O tag value.

Mapping the "EGU Exceeded" OPC DA quality flag into the attributes of the I/O tag value.

Mapping the "Sub Normal" OPC DA quality flag into the attributes of the I/O tag value.