Difference between revisions of "OPC UA PubSub JSON mapping component"
Jump to navigation
Jump to search
Line 19: | Line 19: | ||
!Property | !Property | ||
!Type | !Type | ||
+ | !Default | ||
!Description | !Description | ||
|- | |- | ||
|MessageFormattingParameters | |MessageFormattingParameters | ||
|OpcLabs.UAPubSubJson.Sdk.PubSub.JsonMessageFormattingParameters | |OpcLabs.UAPubSubJson.Sdk.PubSub.JsonMessageFormattingParameters | ||
+ | | | ||
| | | | ||
|- | |- | ||
|MessageFormattingParameters.IndentChars | |MessageFormattingParameters.IndentChars | ||
|System.String | |System.String | ||
+ | | | ||
|The character string to use when indenting. | |The character string to use when indenting. | ||
|- | |- | ||
|MessageFormattingParameters.PrettificationLevel | |MessageFormattingParameters.PrettificationLevel | ||
|OpcLabs.UAPubSubJson.Sdk.PubSub.JsonMessagePrettificationLevel | |OpcLabs.UAPubSubJson.Sdk.PubSub.JsonMessagePrettificationLevel | ||
+ | | | ||
|A value indicating how to prettify the output. | |A value indicating how to prettify the output. | ||
|} | |} | ||
Line 60: | Line 64: | ||
|The message is prettified to the dataset message data level. | |The message is prettified to the dataset message data level. | ||
|} | |} | ||
+ | |||
+ | == Receive message mapping == | ||
+ | The table below lists the available properties, their types, and descriptions. | ||
+ | {| class="wikitable" | ||
+ | !Property | ||
+ | !Type | ||
+ | !Default | ||
+ | !Description | ||
+ | |- | ||
+ | |MessageParsingParameters | ||
+ | |OpcLabs.UAPubSubJson.Sdk.PubSub.JsonMessageParsingParameters | ||
+ | | | ||
+ | | | ||
+ | |- | ||
+ | |MessageParsingParameters.AutoRecognizeMessageFormat | ||
+ | |System.Boolean | ||
+ | | | ||
+ | |Determines whether the message format will be automatically recognized when possible. | ||
+ | |- | ||
+ | |MessageParsingParameters.RecognizedNonReversibleBuiltInTypesMask | ||
+ | |System.Int32 | ||
+ | | | ||
+ | |The built-in types that be recognized when parsing the non-reversible JSON encoding. | ||
+ | |- | ||
+ | |MessageParsingParameters.RequireDataSetMetadata | ||
+ | |System.Boolean | ||
+ | | | ||
+ | |Determines whether data set metadata will always be required for parsing. | ||
+ | |} | ||
+ | |||
+ | |||
+ | == Envelope mapping == |
Revision as of 10:30, 30 January 2020
(tbd!!!)
Contents
Installation
Configuration
EasyUASubscriber object
OpcCmd tool
UADemoPublisher tool
Parameters
Send message mapping
The table below lists the available properties, their types, and descriptions.
Property | Type | Default | Description |
---|---|---|---|
MessageFormattingParameters | OpcLabs.UAPubSubJson.Sdk.PubSub.JsonMessageFormattingParameters | ||
MessageFormattingParameters.IndentChars | System.String | The character string to use when indenting. | |
MessageFormattingParameters.PrettificationLevel | OpcLabs.UAPubSubJson.Sdk.PubSub.JsonMessagePrettificationLevel | A value indicating how to prettify the output. |
!!!
Name | Value | Description |
---|---|---|
None | 0 | The JSON message is not prettified. |
NetworkMessage | 1 | The message is prettified to the network message level. |
NetworkMessageData | 2 | The message is prettified to the network message data level. |
DataSetMessage | 3 | The message is prettified to the dataset message level. |
DataSetMessageData | 4 | The message is prettified to the dataset message data level. |
Receive message mapping
The table below lists the available properties, their types, and descriptions.
Property | Type | Default | Description |
---|---|---|---|
MessageParsingParameters | OpcLabs.UAPubSubJson.Sdk.PubSub.JsonMessageParsingParameters | ||
MessageParsingParameters.AutoRecognizeMessageFormat | System.Boolean | Determines whether the message format will be automatically recognized when possible. | |
MessageParsingParameters.RecognizedNonReversibleBuiltInTypesMask | System.Int32 | The built-in types that be recognized when parsing the non-reversible JSON encoding. | |
MessageParsingParameters.RequireDataSetMetadata | System.Boolean | Determines whether data set metadata will always be required for parsing. |