Difference between revisions of "Using communication packages"
Jump to navigation
Jump to search
| Line 12: | Line 12: | ||
=== EasyUASubscriber object === | === EasyUASubscriber object === | ||
| − | Usually, you will use the same communication package across your solution, but there is nothing that prevents you to use a different one with each connection. | + | Usually, you will use the same communication package across your solution, but there is nothing that prevents you to use a different one with each PubSub connection, e.g. for compatibility reasons with different MQTT brokers. |
=== OpcCmd tool === | === OpcCmd tool === | ||
Revision as of 10:17, 13 December 2019
Contents
Specifying the communication package
In order to select this communication package in OPC UA PubSub tools, you need to set a custom property on a PubSub connection as follows:
- Property namespace: http://opclabs.com/OpcUA/PubSub
- Property name: MessageChannel!
- Property datatype: String
- Property value: The type name of the message channel object. See the communication package documentation (example: OpcLabs.Mqtt.MqttClientMessageChannel,OpcLabs.Mqtt).
How this is done depends on the concrete software you are using.
EasyUASubscriber object
Usually, you will use the same communication package across your solution, but there is nothing that prevents you to use a different one with each PubSub connection, e.g. for compatibility reasons with different MQTT brokers.
