06-30-2009 05:30 PM
HI,
I have been converting a project from LabView 8.5 to 8.6.1 and have been replacing a self written class by another one. While working on this and updating a subVI LabView crashed. When I restarted LabView I could recover some of my work. Later I tried to open the main VI of the project and LabView crashed immediatly. The main VI was normally saved before LabView 8.6.1 crashed for the first time. So I wonder what could have happened? Is there any chance to recover the main VI and the work which I spent on the main VI?
The same happened to another VI which I never have opened in LabView 8.6.1 But when I copied the 8.5 Version of this VI again to the new project folder (using the Windows Explorer) I had no problems to open it. While working on my project in LV 8.6.1 I once used "Save all (this project)". Any explanation what could happened, how to avoid this and how to recover such VIs?
Regards,
Jörn
06-30-2009 06:40 PM
Jorn,
Yep- it can get pretty tricky to upgrade versions of LabVIEW. IMHO the BEST (safest) way is to follow this procedure;
1) Backup everything on a machine that still has the old LV version.
2) Install the LabVIEW version to move to.
3) Use tools>mass compile> all of your reuse code (pay attention to the warnings and address them individually)
4) Use tools>mass compile> all of your drivers (pay attention to the warnings and address them individually)
5) Use tools>mass compile> each your projects (pay attention to the warnings and address them individually)
a bit more time consuming than just opening and resaving---unless there are conversion issues that crash the enviornment.
07-01-2009 12:28 AM
Keeping a back-up is always good.
Meanwhile I updated all subVIs from the projekt without any problems (i.e. converting from 8.5 to 8.6.1 and introducing a newer version of a class which I wrote for the project). Now I took again the old version of my main VI, load it in 8.6.1, replaced the the old version of the class with the newer one (opening the old main VI introduced some conflicts), after 20 minutes work and replacing all old class VIs but one I saved the main VI, closed the project, opened the project again, tried to open my main VI and LabView crashed... Really bad!
Any ideas?
Jörn
07-01-2009 12:35 AM
Hi there
just in case LV provides some error messages including "FPHP"/"BDHP" (Front panel heap/block diagram heap) and an error number try this:
1) Close LabVIEW
2) Put the key "LVdebugkeys=True"in the LabVIEW.ini file
3) Open your VI
4) Press CTRL+SHFT+d, then press CTRL+SHFT+h This will turn on an object browser.
5) In the top left list box, select the element that contains the name of your VI and the letters FPHP or BDHP
6) In the top right listbox, find the line that begins with the error number
7) Click on the F button
😎 Delete this object and recreate it.
It may help to clear all NI related temp files. Close any NI application/service and delete all files in %TEMP%
07-01-2009 08:31 AM
Hi chris,
opening my main VI does not work because LV 8.6.1 crashes when I try to open it. So I copy the main VI from the old location (Version 8.5) to a new location on the harddisk and open it with LV 8.6.1. Most subVIs are loaded from the new location and have Version 8.6.1. One LVclass (the one I want to update) is not found and loaded from the old location on disk. Then I save the main VI. Next time I try to open the main VI LabVIEW crashes immediatly. The main VI and its subVIs are organized in a LVProject which causes no problems while opening.
I tried CTRL+SHFT+d, then press CTRL+SHFT+h but nothing happend. In which window do I have to do it?
Jörn
07-01-2009 08:33 AM
I once found an error in ProjektItem.cpp. But I can't reproduce it now.
Jörn
07-02-2009 10:03 AM
07-09-2009 02:02 PM
07-17-2009 02:28 AM
Installing the patch had no specific effect on broken VIs.
With regard to my previous posting in this thread LabView crashed with an error in line 14832 ProjectItem.cpp.
There must be a problem with LV 85 VIs in a LV86 Project (they can be "hidden" in the dependencies list).
Regards, Jörn