UDT Definitions not propagating to enigine

Hi Guys

I created u UDT on the transmitter/Edge and created an instance of it. I see that on the engine side I receive the udt as folders with tags in them and thus not as a UDT.
-I did disable “Converts UDT members to normal Tags before publishing”
-I disabled “Optimizes UDT payload sizes in NDATA and DDATA payloads” (tried enabled as well)
-I have deleted the tag instances on the engine side and then refreshed under transmission control.
I keep on receiving the udt as folders containing tags and no UDT definition pops up on the engine UDT Definition side.

Am I missing something?
I am running:
-Ignition 8.1.7 (b2021060314)
-Eng/Dist/Trans 4.0.7 (b2021041216)

This issue is due to a change in Ignition 8.1.7 that causes our UDT definition lookup logic to return the wrong value. We have a fix for this issue in our latest Nightly modules for Ignition 8. You can download the MQTT Engine fix via the link below.


Let us know if you run into any other issues or have any follow up questions. Thanks.

Hi Nathan

Thank you for the solution. But that brings me to my next question. I am doing all of this in a dev environment. Once I commission I will be updating the client’s ignition gateway server to 8.1.7 but that client has an existing Ignition edge 8.1.5 running with MQTT Transmission 4.0.6. So I assume I will run into the same issue there? Which means I have to update the Ignition edge MQTT Transmission module and the Ignition Edge version itself as well?

The easiest would probably be to standardize on an Ignition version for that client but a lot of features that the client wants (e.g. map component in Ignition) is getting constant updates with new Ignition releases.

Or can I assume that since the Ignition edge version and its transmission version are stable, it won’t be affected by updating the Main Cloud Ignition GW to 8.1.7?

Basically tying in to what Wes said in a different post

That is correct, the Central and Edge GWs (and our MQTT modules) do not need matching versions to work properly since both sides implement Sparkplug B. The only caveat to that is if you’re running into a bug cross module (e.g., a bug that exists in both Engine and Transmission) you may need to pick up the fix and that may require installing matching versions of our modules containing the fix.

In this case, the bug you’re hitting is specific to MQTT Engine on Ignition 8.1.7 and so you will only need to upgrade MQTT Engine to pick up the fix.

Thanks Nathan, that saves me a lot of work!

Had same issue. Ended up upgrading the modules. It seems to be working now. Ref Ignition Version 8.11.16 MQTT module versions 4.0.10 (b2022020721).