| Name | Description | Unit | Default value |
|---|
OPC HDA: Server if Available | OPC HDA server name (ProgID), if it is available. OPC HDA functions not to be activate use empty text. | - | |
OPC HDA: Max. Number of Values | Sets the parameter NumItems at synchronous reading of historical "raw" values. The implicit value 0 (zero) means all values in the given interval. | - | 0 |
| 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 parameter "Group reactivation delay". | YES/NO | YES |
| A delay after which a failed OPC group activations is repeated if repetition is enabled by parameter "Repeat failed group activation". | sec | 30 |
Reconnect After Failed Group Activation | When an OPC group activation fails, KOM disconnects from OPC server and reestablishes a connection. Parameter is relevant in a configuration of redundant OPC servers (after a disconnect from an OPC server follows a reconnect to 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 disconnect from the OPC server and reconnect or in restart of the KOM process). An example of 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 to stop KOM process when the 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 to reduce the OPC server load in redundant D2000 systems as well as to solve roblems with license limitation of the number of OPC clients. | YES/NO | NO |