...
The configuration options for each of the six tabs - General, Servers, Sets, Transmitters, UNS Transmitters, Records and Files - are detailed below.
...
- Filtered Properties
- Rebirth Debounce Delay
- The amount of time, in milliseconds, to delay before processing Rebirth NCMD requests after one has been processed. Default of 5000 milliseconds.
- Include Sparkplug DataTypes
- Whether or not to include Sparkplug DataTypes for Metrics in Sparkplug DATA payloads
- Enabled by default
Anchor |
---|
| unstransmitter |
---|
| unstransmitter |
---|
|
UNS TransmittersThe UNS Transmitter can be configured to read tags from the UNS structure created by MQTT Engine and publish tag changes over MQTT to any Enterprise consuming clients. Each transmitter is configured with a server Set and will attempt to maintain an MQTT client connection with one server in that Set at all times.
The UNS Transmitter will use the namespace unsAv1.0 and will prefix this to all publishes from MQTT Transmission
Tip |
---|
The UNS namespace may be disabled via script using the "UseTopicPrefixToken" parameter |
Note |
---|
The UNS Transmitter MQTT Client has no subscriptions and so will not receive commands from Enterprise consuming clients |
Image Added
The configuration sections available are Tag Settings, Publish Settings, History Settings and Advanced Settings.
Anchor |
---|
| unstagsettings |
---|
| unstagsettings |
---|
|
UNS Transmitters - Tag Settings
Image Added
- Name
- Unique name for the UNS Transmitter
- Enabled
- Checkbox to enable/disable the UNS Transmitter. Selected by default.
- Tag Provider
- The name of the tag provider that Transmission will monitor.
- Tag Path
- Optional path to the root folder where the tag tree starts.
- Transmitters also support a multi-tag path configuration. Reference the Transmitters with Multi-Tag Paths tutorial for configuration assistance.
- Set
- The Set that the UNS Transmitter client will connect to.
- Discovery Delay
- An optional startup delay, in milliseconds, to wait before scanning for Tags to monitor. This is useful when Tags are dynamically created on initial startup, as is the case when using the MQTT Engine module.
Anchor |
---|
| unspublishsettings |
---|
| unspublishsettings |
---|
|
UNS Transmitters - Publish Settings
Image Added
- Properties QoS
- The MQTT Quality of Service to use for 'properties' messages
- Properties Retain
- Whether or not to set the MQTT retain flag to true for 'properties' messages
- Data QoS
- The MQTT Quality of Service to use for 'data' messages
- Data Retain
- Whether or not to set the MQTT retain flag to true for 'data' messages
Anchor |
---|
| unshistorysettings |
---|
| unshistorysettings |
---|
|
UNS Transmitters - History Settings
Image Added
- History Store
- The MQTT Transmission History Store to use with the UNS Transmitter.
- Enable History Storage by Default
- Checkbox to enable/disable store and forward for all tags. Selected by default.
- Store and forward controls whether or not a tag is stored in the configured History Store when Transmission is offline. To override the global setting, individual tags will require a custom tag property 'StoreAndForward' (type: boolean) to be created and set to the reverse state of the global setting.
Anchor |
---|
| unsadvancedsettings |
---|
| unsadvancedsettings |
---|
|
UNS Transmitters - Advanced Settings
Image Added
- Send All Properties
- Send all properties, including default properties, in .props messages
- Filtered Properties
Records
Within MQTT Transmission, a record is a collection of tags under an Ignition folder which are treated as a single entity and published on demand. They are usually used for, but not restricted to, sending flow computer records such as events, alarms and history data.
...