Replication and Deployment Utility (RAD)

[Mads]

Thanks for that Burt.

A couple of other details/wishes;

1. The application saves its settings in its own folder. Now this works fine if it happens to be installed in a folder where someone has managed to add write access...but that's not normally the case for Program Files on Windows 7 / Vista. It works fine in this case because the installer is set to put it into a LabVIEW project folder, but if you do not have LabVIEW installed already that might not work (I have verified this yet though) - and it would also look a bit strange for people who install this without LabVIEW (the RAD-tool is in our case mostly used by non-developers and customers to get their controllers updated). With the source code available we can always edit it so that it will only use the included file as a baseline to create a writable copy in the user's app data folder for example, and edit the installer to install it under Program Folder\RAD for example...But it would be great if we did not need to 🙂

2. The window run-time position is set to be unchanged, but the window is then centered in code. This produces a flicker whenever you start it. It would be neater to just set the run-time position to be centered.

[Mads]

And by default the tool filters out Fieldpoint devices for example, so the user's have to edit that the first time they use it. It would be better if the default was to show all types of devices, and then let the users limit that afterwards:-)

[Burt_S]

Thanks for the great feedback.  I struggled for a while to decide on the best place to install the utility.  I ended up defaulting to save it where it had always been saved in the past.  I have tested installing the tool on a fresh machine and it worked fine.  I also thought the shortcut is what most non-LabVIEW users would interact with anyway.  All of that said, this is definitely something I will reconsider in the future. 

As for the other feedback, I completely agree and it should be very easy to fix for a future build.

[MartinMeyer]

I installed the current version of the installer, rad_3001_installer.zip.  I have an executable on one cRIO and was able to retrieve an image without any issues.  When I tried to deploy to the other target, the target was booted into install mode. The Deploy Application Images window was going through a process of Enumerating directories.  It hung on /tmp/MAX/logs.  I am using LV2012 on my host and the cRIO. Any hints on what I should look into would be helpful.  This is the first time I am using the RAD tool.  Thanks.

[Burt_S]

How long have you waited for the application to continue?  The application can occasionally appear to hang on a file only to recover 20 or so seconds later.  Also, does it always fail at this exact step? Just out of curiousity, which controller are you using?

Installing the newest version of the System Configuration driver may fix this if you don't have it installed already.  It would be good to get to the root of the issue, but if you are looking for a workaround you may be able to make a working image by formatting the original controller, reinstalling the drivers and EXE from MAX and the project, and then retrieving the image again.

[MartinMeyer]

It has happened twice at the same spot.  I have waited nearly 10 mins.  I am using a cRIO-9074.  The cRIO and desktop just had LV2012 installed with the f1patch.  I was not aware of a system configuration update required.  Thanks.

[Burt_S]

Interesting.  I have deployed to a 9074 many times without running into this.  I would definitely check that you have System Configuration 5.3.2 installed.  I don't believe this version was shipped with LabVIEW 2012.  If it isn't installed, you can find it here. 

If that doesn't help, and you need an urgent fix, I would still recommend trying to reformat the cRIO, reinstall all software, retrieve a new image, and try again.  I would also recommend contacting NI Support to send them your image (assuming you can share it) so they can try to reproduce the issue.

[MartinMeyer]

I had version 5.3 with LV2012, so I installed the update.  I tried running using the source install so that I could recompile for 2012 and that didn't seem to change anything.  Mass compiling reveals a couple of VIs that aren't runnable, but apparently aren't used. 

When doing the deploy it is very repeatable and It hangs in the same spot each time.

I can retrieve an image from a cRIO and try to deploy right back to it and it hangs.

I am going to send an image to support.  Good chance with this, I am doing something stupid, but there sure aren't many clues. 

Thanks for responding.

[Mads]

Burt,

Any chance the source code (and installer) file on this web could be updated with one that has all the necessary files included in the build script? Every now and then I find myself in a situation where the easiest way to get hold of a copy is to visit ni.com, but then I have to redo the necessary fixes...and that's just me. I guess everyone else downloading it will havew to discover these things for themselves too as long as the files stay as they are. Perhaps the other things that have been pointed out earlier (like default device filtering e.g.) could be added at the same time?

The installer should also include the System Configuration Run-Time. You also have the issue with converted images not working without some manual modification (CAR 366310) - could that not be automated by the RAD-tool itself?

[JoshuaP]

Note we are currently working on NI System Configuration 5.3.3 to address (CAR 366310).  It should go live by the end of the month.