View Issue Details

IDProjectCategoryView StatusLast Update
0010160Part 81: UAFX Connecting Devices and Information ModelSpecpublic2025-02-28 14:07
ReporterSuad Morgan Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status newResolutionopen 
Summary0010160: Clarification on the Behavior of the EstablishConnections Method Callback timeouts
Description

Need clarification on the behavior of the establish connection method callback in OPC UA FX when a device takes an extended time to become ready for data exchange to go to operational. Specifically, what is the recommended duration for waiting for the device or controller to create endpoint and return from the callback? could this be added to the capabilities?
The callback may take longer if the connection manager is unaware of the device's readiness time, which can impact performance. While a retry mechanism may not always be the best approach. Also, various issues can lead to delays, including communication failures, device malfunctions, or inherent latency in the device itself.

TagsNo tags attached.

Activities

Paul Hunkar

2025-02-28 14:07

manager   ~0022424

after discussion , we think this could apply to slow controllers, not just to devices
we should also consider how the client provided timeout hint applies to the call service.

we should examine solution that already exist in other services like history (continuation point) or the write service (completes async)
we could add a special errorcode and then a new method that would just effectively have the return parameters - so a new call timeout period can be started

we could also add recommendation or some other discussion on sending single command - to allow more time for the overall action

Issue History

Date Modified Username Field Change
2025-02-21 22:08 Suad Morgan New Issue
2025-02-28 14:07 Paul Hunkar Note Added: 0022424