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.
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.
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.
On the edge side, things are working fine.
Currently my server is running on 8.0.16, and to match things up, i have upgraded to 8.1.7 as well.
I have downloaded 4.0.8 distributor and engine module.
I observed that when i tried to restart the engine modules / updating engine settings, it takes minutes to refresh. And i am having Error_Config issues for my UDT instances. Hence im doubting the engine module.
IF one of the edge transmission is not working properly, for that particular edge, can i try with v8.1.7 + transmission module 4.0.11? (together with remaining systems in point 1 & 2).
IF point 3 happens, should i just go ahead with upgrading all edge and server MQTT modules to 4.0.11 instead? So that it will be more…standardized? meaning edge/ignition v8.1.8 + MQTT engine/distributor/transmission module 4.0.11
Sorry for the long post and many thanks in advance!!
Since you’ve upgraded all of your Ignition GWs to 8.1.7, I recommend that you run the latest official MQTT module release - 4.0.11. 4.0.11 is supported on 8.0.16 to 8.0.17 and 8.1.0 to 8.1.17.
When we release a new version of our MQTT modules we typically only upload to the latest Ignition version, but the new module likely runs without issue on older Ignition versions as well. To see which version of our modules are supported on which versions of the Ignition platform, see our compatibility matrix here. I hope this helps. Let us know if continue to run into UDT issues after upgrade. Thanks.