...
Following communication line parameters can be configured for protocol "OPC Data Access 2.05 & 3.0":
Tab. No. 1
| Name | Description | Unit | Default value | ||||||
|---|---|---|---|---|---|---|---|---|---|
| OPC HDA server name (ProgID), if it is available. OPC HDA functions are not to be activated, use empty text. | - | |||||||
| 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:
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. | - | 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 activations 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 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 | ||||||
| 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": | 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 to reduce the OPC server load in redundant D2000 systems as well as to solve problems with license limitation of the number of OPC clients. | YES/NO | NO |
...
The changed conditions come into effect by clicking the "Refresh" button.
Copying tags
A keyboard shortcut Ctrl+C copies the names of tags in a selected branch into the Windows clipboard. All tags will be copied unless a specific tag is selected.
A keyboard shortcut Ctrl+Shift+C copies the names of tags in all browsed branches into the Windows clipboard.
Note: In versions from 20th December 2018 and newer, recycling of browser dialog has been implemented. If the dialog is closed by the Close button or after selecting a tag, it is actually only hidden and it is available for browsing by another I/O tag within the same station so that the tree structure of the browsed objects is preserved. Clicking on the close icon at the top right corner will cause the dialog to be really closed.
...
- OPC FOUNDATION, Data Access Custom Interface Standard, Version 2.05A, June 28, 2002.
- OPC FOUNDATION, Data Access Custom Interface Standard, Version 3.00, March 4, 2003.
- OPC FOUNDATION, OPC Common Definitions and Interfaces, Version 1.0, October 27, 1998.
- OPC FOUNDATION, Using OPC via DCOM with Microsoft Windows XP Service Pack 2, (C) 2004 OPC Foundation Inc.
The othersOther sources:
- OPC DCOM White Paper, Richard C. Harrison, Intellution Inc. © Intellution Inc. 1998
...
- Ver. 1.0 – February 9th, 2000
- Ver. 1.1 - January 3rd, 2002
- Ver. 1.2 - January 23rd, 2004
- Ver. 1.3 - November 22nd, 2005
- Ver. 1.4 - October 10th, 2007
- Ver. 1.5 - December 3rd, 2007
- Ver. 1.6 - March 13th, 2009
- Ver. 1.7 - February 8th, 2010
- Ver. 1.8 - March 5th, 2013
- Ver. 1.í 9 - July 16th, 2021
- Ver. 1.10 - Feb 7th, 2021 - added parameter "Authentication Level"
| Info | ||
|---|---|---|
| ||
...