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

Send extension fields as part of datasetmessage and enable free form configuration of extension fields (move to Variant value) #1940

Closed
marcschier opened this issue Jan 17, 2023 · 1 comment
Assignees
Labels
feature request New feature or request
Milestone

Comments

@marcschier
Copy link
Collaborator

          I moved the filling of extra extension fields into the encoder.  Need to still support extension fields in PubSub messages and configuration from control plane, will put on backlog.

Originally posted by @marcschier in #1928 (comment)

@marcschier marcschier self-assigned this Jan 17, 2023
@marcschier marcschier added feature request New feature or request OPC Publisher labels Jan 17, 2023
@marcschier marcschier added this to the 2.9.0 Preview 1 milestone Jan 17, 2023
@marcschier
Copy link
Collaborator Author

Customers want the ability to add machine or engineering unit context to messages. Extension Fields in OPC UA Pub Sub support this. The plan is to add full support to OPC Publisher. Customers will be able to add extension fields to pn.json per endpoint/per datasettag. These will become fields of the dataset as if they originate from the OPC UA server and thus allow a consumer to understand the context of the message.

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

No branches or pull requests

1 participant