UDT's in a Reference Provider or MQTT Engine

Ignition
1

Hello,

I was wondering what the pros and cons of having UDT's in a reference provider with tags referencing the MQTT engine tags as opposed to having the UDT's in the MQTT Engine it self.

We have created all our UDT's in the MQTT engine and all our tag bindings are directly with these UDT's in MQTT Engine. We did this because someone told us that this would be the correct way to enable history in special regards to store and forward. Is this the case?

or should we port all our UDT's to a reference provider with reference tags? Would this inpact the our database logging in a negative way?

1 Like
2

I also am interested in knowing the answers to those questions.

I use MQTT edge devices that aren't Ignition Edge so they don't send UDTs. On the Ignition Edge devices I do use, I don't send the UDTs because the other other scies don't.

So I'm curious of what's the benefits of using Ignition Edge with Transmission and send UDTs vs not doing that and just using reference tags in a tag provider referencing tags in the MQTT engine provider. Can anyone comment on this?

I thought I can try this out and seeing what happens using a trial of Ignition with the Transmission module.

1 Like