Best way to publish non-SparkplugB MQTT data?

Ignition
1

Hi all,
I'm looking for the best approach to put an entire tag provider (or a certain folders) to publish plain MQTT (non-SpB) on change. I currently have an on-change tag event working (script below) but I'd like to design something more scalable instead of putting scripts on each tag. I"m thinking a gateway event could do this?

Basically I'd like all the functionality of the MQTT transmitter but not have it in SparkplugB format.

Script -----
tagvalue = tag.value
system.cirruslink.transmission.publish("Chariot SCADA", tagPath, str(tagvalue.value).encode(), 0, 0)

2

Hi all,
Referencing this post on IA forum, and here on Cirrus Link forum, looks like if I use a custom namespace, it may be a work-around for SpB

3

what did you end up doing here?

4

Probably worth mentioning the new[ish] UNS Transmitter in MQTT Transmission, as this wasn't available at the time of this original post.

5

Ended up not using MQTT, MES vendor bypassed Ignition to go direct to the equipment controller with their native edge connectors. Ugh....

6

Thanks for the reply!

7

Hi @Kevin.Collins I got it working and thanks for the links.

I do have another question, I noticed in the broker when i send a temperature for example, there are two topics, Temperature.props = {} and temperature = {value:mysuff}.

Any idea what the temperature.props = {} is used for and if I need it or can remove it?

Thanks again!