Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LDS server doesn't receives unsolicited announcements from OPC UA server #77

Open
z-krejsa opened this issue Oct 26, 2022 · 4 comments
Open

Comments

@z-krejsa
Copy link

Our server sends unsolicited announce frames during initialization ...
image
The frames seems to be correct to me but they are not processed by the LDS server, the OPC UA server doesn't appear in the discovered servers list.
I've changed the logging of LDS service to "debug" mode to see all the events, but there doesn't appear anything during receiving of this frames.
Can you let me know why it doesn't work, what's the problem?

@erhardgrishaber
Copy link
Contributor

@z-krejsa See explanation from Issue #76

@z-krejsa
Copy link
Author

z-krejsa commented Nov 1, 2022

Even with hostnames and FQDN names, our server doesn't appear in the ServersOnNetwork list. The LDS service need to be restarted and then our OPC UA server appears in the list. Any idea of the cause of the problem ?

@erhardgrishaber
Copy link
Contributor

Can you check the configuration file: C:\ProgramData\OPC Foundation\UA\Discovery\ualds.ini for "EnableZeroconf" It should be "yes". Also it can help to look into the log files for more information (opcualds.log). By default it is set to "error", so please change it to "debug" in the configuration file (see LogLevel) and restart the service.

@z-krejsa
Copy link
Author

z-krejsa commented Nov 4, 2022

Zeroconf is enabled, I've checked it out. The log with debug traces is connected, but I cannot see something inside. The behavior is as I said, our device is properly recognized just after restarting the OPC UA Local Discovery Server service.
Strange thing is that sometimes it appears there immediately without restarting the service but I cannot find when, seems to me by chance.
When it works there appears following message in the log but as I said it's quite rare ...
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants