RAD not fully/properly copying drivers

[jefferyanderson]

Based on guidance from the NI software support team, we have started using RAD for deployment of our code on RT Linux cDAQs (9134). It appeared to work at first but now that we are moving to a larger number of units we are finding that the utility doesn't seem to be doing what it claims to do.

It appears that RAD for the most part copies things over, but certain drivers (in our case OPC-UA drivers) aren't properly copied. They appear to be on the unit when explored in MAX, but our Vis using OPC-UA have errors until we manually re-install the OPC-UA drivers. This is not a good solution considering our deployment scenario, we can't have LV developers touching every unit that goes out the door.

When I look at the feedback on the RAD page I see similar complaints from another user that claims they need to manually reinstall drivers as well.

So a couple of questions:

1. Does anyone know how if there are steps that can be taken (i.e. workarounds) to ensure that the drivers are fully and properly copied?

2. Does NI have any plans to update RAD so it works properly?

Regards,
Jeff

[Sam_Sharp · Accepted solution]

As far as I know, the RAD tool is just an implementation of the System Configuration VIs that are on the LabVIEW palettes. Have you tried using those VIs?

You could try a few things with the VIs - you could check the installed components, you could reinstall the ones that didn't install properly, you could create an image that tests the OPC functionality etc. before loading your application code. The VIs can even reboot the target etc.

I believe NI provides the source for the RAD tool as well, so you should be able to modify it yourself. I suspect it was a project for an NI employee rather than an officially supported tool.