You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
Originally posted by @marcschier in #1928 (comment)
The text was updated successfully, but these errors were encountered: