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

How initial metadata and how metadata is published if configuration version changes? #2728

Open
1 of 7 tasks
merlingeorge555 opened this issue May 13, 2019 · 2 comments
Open
1 of 7 tasks
Labels
Component: PubSub Priority: Low Issue with low priority Type: Question General question or code understanding

Comments

@merlingeorge555
Copy link

Description

I have four questions against the specification. If I'm not wrong the subscribers use the DataSetMetaData for decoding the values of a DataSetMessage to a
DataSet.

  1. As of now ie. current implementation of OPCUA Pub/Sub how the initial metadata is published?
  2. How exchange the DataSetMetaData between Publisher and Subscriber if the configuration changes?
  3. Does mirror variable implementation required datasetmetadata from publisher to subscriber?
  4. What is mirror variable?

Checklist

Please provide the following information:

  • open62541 Version (release number or git tag):
  • Other OPC UA SDKs used (client or server):
  • Operating system:
  • Logs (with UA_LOGLEVEL set as low as necessary) attached
  • Wireshark network dump attached
  • Self-contained code example attached
  • Critical issue
@cpipero
Copy link

cpipero commented May 14, 2019

I also had some questions on this topic, because I am not sure that this configuration aspect of pub-sub is implemented yet.
I was testing with some of the examples and looked at the test fixtures and while the examples work correctly (even with my own custom nodes), the configuration info (like DataSetMetaData) is NULL on the serve (publisher side).
For example, if I use the OPC Foundation .NET example I cannot configure a subscribed because it looks for that info to map the dataset fields.
I will subscribe to this issue to see the replies in case I'm missing something that exists.

@theresa95
Copy link

I have also problems understanding this concept as well.
I am publishing the values of multiple sensor data (2 temperature, 1 pressure and so on) and I have already managed to subscribe to all of them. But I do not know neither the order of the published values, nor the fieldnames. Thus I cannot distinguish between those values. Therefore, I will have to read out the dataset definition initially to have the metadata and the order of fields. But I do not know how to accomplish that.

I have already opened an issue (#2726 ) about that yesterday. If someone could let me know how this can be accomplished, I would be very grateful! :)

@NoelGraf NoelGraf added Component: PubSub Priority: Low Issue with low priority Type: Question General question or code understanding labels Apr 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: PubSub Priority: Low Issue with low priority Type: Question General question or code understanding
Projects
None yet
Development

No branches or pull requests

4 participants