There is a race condition in rad_Extract Full Image.vi. In the VI there is a copy function and a subVI called Util_AppCreateTempDirectory.vi. The order of execution of these two functions is not guaranteed. If the util runs first, it deletes and recreates a directory. The copy then copies the image file to this newly created directory. This is the correct order.

If the copy happens first, then the util deletes the directory along with the copied image file and leaves an empty directory.

Functions downstream fail in this case as they expect the image to be there and it isn't. The user level symptom of this is being told that the image file is incompatible with the version of RAD. This is because the image file version string is empty.

Best practices for LabVIEW Code in version control recommend separating compiled code from the source code for all VIs. The current version of the RAD project does not have this option enabled.

We need to add some SystemLink directories to the permanent blacklist list. The files that we are permanently blacklisting are ID files that would never need to be copied from one target to the next. I've included the items we need blacklisted below:

• /etc/salt/minion_id
• /etc/salt/pki (all files in that directory)

If you try to retrieve an image from a 9038 or 9049 when the / file system is 100% full, you will get a pop up with a unhelpful error message.

I think this happens if you deploy to a full cRIO as well.

Maybe if this error is detected a file system check can be done, and if full, a more informative error message provided.

This error happens in the Create System Image (Folder).vi that is called from rad_Retrieve Image Wrapper.vi.

In the installer build spec for RAD NI System Configuration is included, but NI CompactRIO Runtime is not. The later is required to allow systems to work with newer cRIOs over their USB connection.

When retrieving a new image, if you press "back" on the "Choose Image Directory" step and then press "OK" again, the application image path shows as incorrect. Every time you press back and OK, a new level is added to the image path.

1. Select a Deployment Target
2. Select Retrieve
3. Chose New Application Image
4. Type in a name of your choice and press OK
5. Take note of the generated application image path then press Back
6. Press OK and notice that a new level has been added to the file path
7. Repeat steps 5 and 6 and see that a new layer is added every time.

Workaround: Press Browse under the defined file path and then press OK. This will return the file path to its expected format.