Cannot install RTI DDS on cRIO 20.7

[FireflyAutomatix]

Not sure if this is the correct place for this question or not.  After installing Linux RT on a cRIO as a Base System Image, it is no longer possible to install the RTI DDS toolkit using the software installer in MAX.

We need to use this version of Linux RT as it is the only one that supports System Link.

[elcalverado]

From what I can see, it looks like RTI's DDS installer is still CDF-based. CDF installers can't be used with Base System Images. In order for packages to show up as available after installing the Linux RT Base System Image, the software has to be packaged as an IPK installer and then must be added to a feed which is registered on the target. 

Hopefully an RTI engineer can comment here on whether they have considered rebuilding the DDS installer for Linux RT as an IPK package.

[FireflyAutomatix]

Thank you.  I just reached out to RTI to see what they say about this.  Very frustrating for the price we have to pay for this package.

[wegunterjrFireFly]

So, does this mean anyone using VIPM will not be able to use SystemLink?

[elcalverado]

Most package installed with VIPM just add new drivers/APIs to the functions palette and don't require any additional software to be installed on RT targets. So in those cases, you can definitely still develop and deploy LabVIEW applications using SystemLink, even if they use functionality from VIPM packages.

The RTI DDS case is different because DDS does require files to be installed on the RT target before being able to run code on the target. If there was an IPK installer for the DDS toolkit, it could registered with a feed on SystemLink and installed on targets from their instead of from NI MAX.

You also may want to check out this previous post on this forum where someone was able to manually copy over the RTI DDS dependencies onto an RT target and unzip them in the correct directories. This allowed them to run their DDS code even without installing anything through MAX. This definitely isn't a tested/supported workflow I'm guessing, but it seemed to work for them.

-Jordan

[FireflyAutomatix · Accepted solution]

Jordan,

Thank you for the feed back and information.  We have also been in contact with RTI on this issue.  From our stand point we are going to consider this issue closed and use the manual workarounds until RTI sees fit to use the IPK packages.

-Alan