this topic is not exactly the same like a previous one posted by me. It is slightly different, that is why I decided to post a different one. The use case is different.
The use case:
In our application, the user browse first any OPC server.
Then he goes to a mapping page where he can map OPC items for some other purpose, not relevant here.
After browsing the server the whole OPC tree is saved for the mapping functionality.
The OPC server is NOT used anymore directly.
I calculated manually about 4/5 seconds timeout, after that the OPC server will be automatically disconnected.
OPC items that come into the tree some second after the connection, asynchronously, are NOT available after the first browse.
When the user recognizes that some item is still missing, he browses again but it is too late, the OPC server will be connected again and the same items shall be found, the "fastest" coming into the tree.
The "slowest" shall never be available!
To clarify exaclty what I'm asking:
I can implement several workarounds to solve this issue, it is not difficult, for example keep internally browsing some node with 1 second frequency just to keep the server alive.
I'd rather prefer a good tehoretical way, whenever it is already available in the OpcLabs library.
Is there any possibility to increase the connect timeout, which might be too short for our purposes?
I haven't found it in the Concept Document.