Advanced configuration
- Last UpdatedJun 10, 2025
- 2 minute read
Advanced configuration settings are defined in the following table:
|
Setting |
Definition |
|---|---|
|
Incoming Timestamps [ Source ] |
Specifies whether the incoming timestamps are taken from the source, from the OPC UA server, or from the connector. |
|
PI Store Mode [ Update ] |
Specifies whether the connector INSERTs or UPDATEs values. If a PI point already has a value at a timestamp, the UPDATE mode modifies it. If not, the INSERT option creates a new value. |
|
Preferred Locale [ English - United States ] |
Specifies the text localization to be used. |
|
Max Browse References to Return [ 100 ] |
Specifies the maximum number of returned references per node in a Browse() call. |
|
Browse Block Size [ 1 ] |
Specifies the maximum number of nodes in a Browse() call. |
|
Read Block Size [ 1000 ] |
Specifies the maximum number of nodes in a Read() call. |
|
[ ] Allow Insecure Credentials |
Marking this means that passwords can be sent over insecure connections. |
|
[x] Take DNS Name and Port from Discovery URL |
Marking this causes the connector to use the DNS name and port from the discovery URL to connect to an OPC UA server. |
|
[ ] Enable Property Subscription |
Marking this means that the connector will create subscriptions to those OPC UA objects (their properties) that are mapped to static PI AF attributes. |
|
[ ] Enable OPC UA Model Changes |
Marking this means that the connector receives notifications when any new OPC UA object is added to the address space, as well as when an object is updated.Consequently, and depending upon the DCM settings for the 'Future changes to the data source structure' option, the connector replicates them to PI and/or PI AF. Note: Your OPC UA server must implement the GeneralModelChangeEventType so that the connector can react onto these notifications. |
|
[ ] Override the Reconnection Logic |
When the communication link to an OPC UA server is disconnected, the default reconnection logic (implemented in the third party component the connector uses) is activated. In certain scenarios, however, this logic might not deliver the desired results. Marking this causes the connector to initiate its own reconnection logic. Note: Consult with OSISoft technical support about your use scenario before activating this option. |