| Name | Description | Unit | Default value |
|---|
OPC HDA: Server if Available | OPC HDA server name (ProgID), if it is available. OPC HDA functions are not to be activated, use empty text. | - |
|
OPC HDA: Max. Number of Values | 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 |
Repeat Failed Group Activation | 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 activations is repeated if repetition is enabled by the parameter "Repeat failed group activation". | sec | 30 |
Reconnect After Failed Group Activation | 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 follows a reconnect to an alternate OPC server where group activation may be successful). | YES/NO | NO |
| Period of executing the call of GetGroupState of interface IOPCGroupStateMgt. This synchronous call is repeated periodically and detects the problems which could occur in communication with OPC Server. | sec | 10 |
Accept All GetGroupState Errors | All the errors returned by calling of "GetGroupState" 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 |
Stop KOM When OPC Server Fails | 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 license limitation of the number of OPC clients. | YES/NO | NO |
| 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 (has a 'BAD' status). This parameter was implemented to suppress undesirable behavior of the OPC.SimaticNET server. | YES/NO | NO |