Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

MQTT Transmission will publish all any non-filtered tag properties which are different from the default Ignition tag property setting in a BIRTH message.

...

Note

Cirrus Link modules often optimize Sparkplug payloads by excluding Good tag qualities from a payload. If you see a Sparkplug payload that is missing the tag quality, it should be assumed to be Good.


Filtering or blocking the publish of tag properties

MQTT Transmission can be configured to flitterfilter/block tag properties from being published. The filtered properties list is configured here and by default contains:

 accessRightsaccessRights;clampMode;deadband;deadbandMode;formatString;historicalDeadband;historicalDeadbandMode;historicalDeadbandStyle;historyEnabled;historyMaxAge;historyMaxAgeUnits;historyProvider;historySampleRate;historySampleRateUnits;historyTagGroup;historyTimeDeadband;historyTimeDeadbandUnits;opcItemPath;opcServer;permissionModel;rawHigh;rawLow;sampleMode;scaleFactor;scaleMode;scaledHigh;scaledLow;tagGroup;valueSource;expression;expressionType;ConfiguredTagPath;eventScripts;readPermissions;writePermissions;eventScripts


Discrepancy with tag properties at MQTT Engine

If you make tag property changes at MQTT Engine, you will see that these changes are overwritten when the next BIRTH message is received for example on a Transmission refresh or disconnect/reconnect. 

This is because the Edge is considered the 'source of truth' for the tag data and it is recommended that tag properties are made at the Edge and propagated to MQTT Engine.


Excerpt Include
CLD80:FAQ: Ignition Modules
CLD80:FAQ: Ignition Modules
nopaneltrue

...