LabVIEW "save for previous version" get stuck and crashes

[DavideBrusamolino02]

Hi everyone,

i'm trying to save a project made with LabVIEW 2020 to LabVIEW 2016 (because i need to use it on a PC that has only LV 2016), but during the conversion it get stuch while converting this vi and if i try to stop or do enything else on LabVIEW it starts not responding and i have to close it by force.

Do you have any idea why this happens? I will attach a screenshot of the vi where it get stuck.

Thank you.

[paul_cardinale]

Usually when I try to save a project for a previous version, it's grayed out and I can't even start.

[altenbach · Accepted solution]

I can't troubleshoot well from a simple error message, but it should of course NOT convert anything that's in the LabVIEW system folder. Did you explicitly add system stuff to the project that should just be in dependencies? Do you use any toolkits?

If project items and dependencies are scattered all over the computer, "save for previous" will create very deep hierarchies that could exceed the capabilities of the file system.

Is this a simple PC project or does it also contain .e.g RT and FPGA, etc.

[DavideBrusamolino02]

Is not a project i have made, i just have to convert it to LV 2016 and test if it works.

I have checked and the VI that causes the crash seems not to be called anywhere, that's very strange.

Yes the project uses some toolkits: VISA, IMAQ and GOOP, but the problematic VI is not part of any of these.

[instrumento]

This is marked solved but I don't understand what the solution is.

I'm trying to save for 2018 a single VI (references a large number of VIs underneath) that is currently a 2022Q3 VI.

The Save for Previous Version shows me a few tool kits, but the selected versions are all ancient. For NI Analysis Library it chooses LV2012, and there isn't anything newer; for NI Analysis Library - Pro, it chooses LV2010, nothing newer; for Picture control toolkit in LV7.0 it choose Picture Control V2.

On one machine it wants to load <vilib>:\addons\_JKI Toolkits\Caraya\classes\Test\Define Test.vi, on another it doesn't, maybe that tool kit is not installed there. I need to Ignore Item for that, then for a few other Caraya VIs.

On both machines it gets stuck Saving c:\Program Files\National Instruments\LabVIEW 2022\vi.ib\regexp\sfp\Match Regular Expression SaveForPrev2010T2009.vi and that's it, it hangs, and the only way out is to kill LabVIEW.

I've used Save For Previous before, lots of times, never had this problem.

[instrumento]

And the answer is, the 2022Q3 code in questions uses Set (from Collections) which is not available in 2018.

Wish the Save For Previous could somehow tell me that was the case, I wouldn't have wasted a couple of hours going down the hierarchy and check which one the  process was stuck on.