LabVIEW Real-Time Application Deployment

[JoshuaP]

You are most likely running out of disk space on your cRIO.  As a general rule of thumb you can't create or deploy an image to a target with more than half its disk full, because you need enough space to store an image of your entire disk next to the contents of your disk.  The image is compressed, so it isn't exactly half.    From the image it looks like your disk is around 70% full.

[EcthelionV]

---

@JoshuaP  ha escrito:

You are most likely running out of disk space on your cRIO.  As a general rule of thumb you can't create or deploy an image to a target with more than half its disk full, because you need enough space to store an image of your entire disk next to the contents of your disk.  The image is compressed, so it isn't exactly half.    From the image it looks like your disk is around 70% full.

---

What if I need those files? I'm even missing my LabVIEW application (I have some configuration files like openvpn, python with some modules and a script for some communication with a protocol not developed in labview). What options could I use in order to replicate the same image to many crios?

[Greil]

Hello,

first, I didn't know RAD is not a product from NI.

NI hotline Reference #3274879 told me, it's an Open Source Software.

So I post an issue here. Steps to reproduce:

1. Develop a new LabVIEW Real-Time Project on a PXI Target.

2. Make first backup with RAD 16.0 - downloaded from here: http://www.ni.com/example/30986/en/

3. Deploy first backup to second identical PXI hardware.

4. Now the 2nd system ist ready to use.

5. But when you do a RAD backup from second hardware, then the backup is twice the size.

You can compare the two backups when rename the file extension to *.zip

1st backup is on left and 2nd backup is on right side.

So I can see: The deployment process copy the whole backup file to the target (wasted disk space)

Another improvement:
The deployment process should have an option to SKIP old logfiles.

[GatorChomp]

Hi Greil,

If you go into the source, RAD is using the Create System Image VI to perform the actual image creation. You can blacklist files with that VI and RAD should have a dialog option for blacklisting files as well. I'd recommend adding the image copy and the logs you don't want copied to that list. 

[cgibson]

RAD has a GitHub repo where bugs and issues can be posted. You can find it here:

https://github.com/ni/rad

When I find a bug I post about it in both places, but the developer is usually quicker to respond on the GitHub repo.