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

No Discovery Url included in FindServersResponse. #24

Open
huebl opened this issue May 5, 2019 · 2 comments
Open

No Discovery Url included in FindServersResponse. #24

huebl opened this issue May 5, 2019 · 2 comments
Assignees

Comments

@huebl
Copy link
Contributor

huebl commented May 5, 2019

Describe the bug
A FindServers request is sent to the OPC UA stack. The answer does not include a discovery URL.

Expected behavior
The Find Servers Response must return all discovery URLs of the OPC UA server.

@huebl huebl self-assigned this May 5, 2019
@huebl
Copy link
Contributor Author

huebl commented May 8, 2019

The OpcUaStack itself is not responsible for processing the find server request. He forwards the request to an opc ua application. If an application does not have an implementation for the find server service, the request will be answered with an error message.

In our case, the demo server answers the find server request. But the demo server does not set all parameters in the response. For example, the UAExpert client does not find the opc ua server. He can not connet.

@huebl
Copy link
Contributor Author

huebl commented May 8, 2019

The behavior should be changed as follows..

  • The opc ua demo application reads the endpoints from the configuration file and returns those endpoints to the caller of the service.

@huebl huebl transferred this issue from ASNeG/OpcUaStack May 8, 2019
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

Successfully merging a pull request may close this issue.

1 participant