QuickOPC-UA Timeout Settings: Difference between revisions
From OPC Labs Knowledge Base
No edit summary |
|||
| Line 48: | Line 48: | ||
= CloseTimeout = | = CloseTimeout = | ||
A timeout for closing the session (in milliseconds). | |||
This parameter is not interpreted by the component; it is simply passed down to the OPC UA Stack for processing. | |||
If the session cannot be closed in a timely manner, it is consider closed anyway, and the component will not use | |||
the same session again. The timeout prevents the component from waiting too long or indefinitely for the | |||
confirmation. This means that any new requests to the same endpoint will open a new session, as with the properly | |||
closed sessions. | |||
= EndpointSelectionTimeout = | = EndpointSelectionTimeout = | ||
Revision as of 12:17, 29 July 2021
Overview
| Parameter[1] | Default value[1] | Description |
|---|---|---|
| in UAClientSessionParameters | ||
| CloseTimeout | 10 000 | A timeout for closing the session (in milliseconds). |
| EndpointSelectionTimeout | 30 000 | A timeout for endpoint selection (in milliseconds). |
| OperationTimeout[2] | 120 000 | Timeout used when sending requests (in milliseconds). |
| SessionConnectTimeout | 60 000 | A session connect timeout (in milliseconds). |
| SessionTimeout | 60 000 | A session timeout (in milliseconds). |
| SessionTimeoutDebug | 600 000 | A session timeout used when a debugger is attached (in milliseconds). |
| in UADiscoveryParameters | ||
| DiscoveryTimeout | 15 000 | A maximum time a server discovery can take (in milliseconds). |
| in SDK configuration | ||
| (none)[2] | ||
Documentation on how to modify the parameters that are set in the SDK configuration: User's Guide: OPC UA Application Configuration
See also: https://www.opclabs.com/forum/ua-connections/891-timeouts-reconnections
CloseTimeout
A timeout for closing the session (in milliseconds).
This parameter is not interpreted by the component; it is simply passed down to the OPC UA Stack for processing.
If the session cannot be closed in a timely manner, it is consider closed anyway, and the component will not use the same session again. The timeout prevents the component from waiting too long or indefinitely for the confirmation. This means that any new requests to the same endpoint will open a new session, as with the properly closed sessions.
