LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Is there a way to make LV24 save for previous when VIs are under an FPGA target?

Solved!
Go to solution

LV24Q3, using .lvversion file to make it autosave everything to an older version. This works if a VI is under the "My Computer" target or a real-time target in the project. If I put it under an FPGA target, it will will get upgraded to 24.0, even if it is a completely empty VI. If I put something in it which explicitly cannot be saved to an earlier version, it correctly flags it and saves to the editor version. With the empty VI, it correctly indicates that there are no issues back saving but then still only saves it to the editor version.

0 Kudos
Message 1 of 3
(303 Views)

I don't know anything about the FPGA target; but maybe this will help:

  1. Copy the attached file to the folder:  "... \National Instruments\LabVIEW 20xx\project\".
  2. Mass compile it.
  3. Restart LabVIEW.

Now, under menu -> Tools, you'll see menu item "Retain LV Version - Save...".

It allows you to save the current VI to previous versions; defaulting to the version it had when loaded.

0 Kudos
Message 2 of 3
(268 Views)
Solution
Accepted by topic author blackburnitearmy

The new Save for Previous feature does not support FPGA.

 

https://www.ni.com/docs/en-US/bundle/labview/page/saving-for-a-previous-version.html?srsltid=AfmBOoq...

 

Files that Cannot Save for a Previous Version

  • LabVIEW-built applications, shared libraries, and PPLs can save for the current editor version only. For source distributions, in order for the defined save version of the project to apply, you need to configure the source distributions to save VIs as source-only. To do this, go to Source Distribution Properties » Additional Exclusions and select the Separate compiled code from source file checkbox.
  • LabVIEW Real Time targets must match your current editor version for deployment.
  • VIs on FPGA targets or VIs using FPGA nodes can save for the current editor version only, regardless of the defined save version of the project.
Message 3 of 3
(261 Views)