- Posts: 69
- Thank you received: 0
Online Forums
Technical support is provided through Support Forums below. Anybody can view them; you need to Register/Login to our site (see links in upper right corner) in order to Post questions. You do not have to be a licensed user of our product.
Please read Rules for forum posts before reporting your issue or asking a question. OPC Labs team is actively monitoring the forums, and replies as soon as possible. Various technical information can also be found in our Knowledge Base. For your convenience, we have also assembled a Frequently Asked Questions page.
Do not use the Contact page for technical issues.
- Forum
- Discussions
- Feature Requests & Product Improvement Ideas
- Connecting Client -> Server without network connection
Connecting Client -> Server without network connection
- Captain_Dash
- Topic Author
- Offline
- Platinum Member
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
- Captain_Dash
- Topic Author
- Offline
- Platinum Member
- Posts: 69
- Thank you received: 0
When the network cable was connected, the server could be found with both methods.
When the network cable was disconnected DiscoverServers throws a Exception
OpcLabs.EasyOpc.UA.OperationModel.UAException: An OPC-UA operation failure with error code -2138963968 (0x80820000) occurred, originating from ''. The inner OPC-UA service exception with service result 'BadTcpInternalError' contains details about the problem.
The Inner exception is an UAServiceException
Error establishing a connection.
Please Log in or Create an account to join the conversation.
Are you saying that when you call DiscoverServers *without parameters* (resulting in a search on the local machine), it will discover the local OPC UA server properly when the network cable is connected, but not when it is disconnected? And what happens when the network cable is disconnected? Do you get an error (details please) - or no error, but an empty collection as a method result?
Thank you
Please Log in or Create an account to join the conversation.
- Captain_Dash
- Topic Author
- Offline
- Platinum Member
- Posts: 69
- Thank you received: 0
Please Log in or Create an account to join the conversation.
But there is something wrong if, as you wrote, "DiscoverServers [...] works only as long as the network is connected.". For a client and server on the same machine, that's not normal.
Please Log in or Create an account to join the conversation.
- Captain_Dash
- Topic Author
- Offline
- Platinum Member
- Posts: 69
- Thank you received: 0
Please Log in or Create an account to join the conversation.
1) OPC UA Local Discovery Server (LDS) is installed and running
2) The OPC UA server is running and successfully registering with the LDS.
Some servers (but they are typically embedded servers where LDS is not present and makes no sense - this is obviously not your case as you are on a PC) do not register themselves with a LDS.
In addition, every OPC UA server acts is its own "mini-LDS", being able to provide info about its own endpoints. This works even without 1) and 2) above, and this functionality can also be accessed by QuickOPC (in a more complicated way), but I would not call it "server discovery", because you actually need to know at least the protocol and server port upfront. It is meant for discovery of different endpoints of an already known server.
Regards
Please Log in or Create an account to join the conversation.
- Captain_Dash
- Topic Author
- Offline
- Platinum Member
- Posts: 69
- Thank you received: 0
we want to run the opc server on a pc together with a client application on the same pc. But this pc should not be connected with a network. Is it possible to discover the server by the client? I used DiscoverServers but this works only as long as the network is connected.
best regards
Please Log in or Create an account to join the conversation.
- Forum
- Discussions
- Feature Requests & Product Improvement Ideas
- Connecting Client -> Server without network connection