I am running into a problem that I have never experienced before - when I am adding case and sequence structures to a version of code I am writing, Labview 6i crashes (i.e CPU allocation jumps to 95% on the task manager and hangs there) requiring an "end task". I am writing the code within XP Pro running on a 1.7 Ghz Pentium 4 machine with 512 MB.
The code is used to control valves and temperature controllers on a Noble gas analysis line and is fairly simple. There are multiple nested sequence (30 steps long) and case structures within a while loop. The code itself is around 1.9 MB, so given the speed and on-board memory of my machine I doubt that I am reaching and physical limit in terms of the memory or proce ssing power required.
Has anyone ever seen something like this? Could the code have been corrupted by an email transfer? If so are there ways to recover? Any help would be greatly appreciated.
Les- Thanks for the reply. I guess I wasn't clear about the problem. This crash occurs when I am in edit mode. As soon as drag to resize the structure it crashes. In run mode the exisiting code executes just fine.
Yes. At least to 6.0.2. Also, you might be able to fix the problem by doing a mass recompile of the directory that the vi resides in, this fixed a similar problem I had about a year ago. Just start Labview, but don't open any of the VIs in that program, then select Tools->Advanced->Mass Compile. I am not sure why it worked for me, but it did, I think it cleans up the code a bit.
Thanks for your suggestion. Just a quick update on my situation. I reinstalled Labview 6.0...the disk claims that update 6.0.2 is included although the version appears to be "6.0.0.4005" from the information under executable's propeties.
As for the case structures I can now add them...I just can't drag/resize them around alot of controls and subVIs so that they are automatically included within the case or sequence. Now I am resizing --> moving structure to back --> dragging necessary code elements into the structure. It's cumbersome but it works.