labview problems, file corruptions, hang ups, etc..

labview problems, file corruptions, hang ups, etc..

Post by JimmyinCT » Thu, 07 Feb 2008 11:40:05


 
we are having endless and constant problems with labview.
The problems are all reproducable on 3 different machines.
Im going to list the 3 most troubling.
 
The biggest problem right now is that our vi files keep getting corrupted approximatly every hour of work. The files cannot be reopened.   Upon repopening the file, the processor utilizes 100% of the cpu.  The three comptuers are all checked out to be okay, hard disks, ram, etc, and one is ever brand new with 8gb or ram..  I suspect the problem has to do with the matlab script environment.  On one of the comptuers, after installing labview, i cant even get matlab to start up, it gets stuck utilizing 100%   of the processor. This is the latest and greatest edition of matlab and labview 8.2 but was 8.0 a week ago.  The reason we upgraded is to fix this. This is a huge disapointment and has costed many weeks of work.  We are now going to try to remake all teh sub vi and matlab script, again.  I feel the problem is the programming langugae at this point.
 
Another problem is that labview keeps *** up when we are double click some of the graphical charts. It happens sometimes but not others but generally a few times a day..  Again, the problem is reproducable on all three computers. I think the problem has to do with the graphical objects being created by being copied rather then recreated each time from the front end but i dont  see why this would matter as they should not be inheriting any properties.
 
Each time we create a new graph or object on the back panel, it goes to some artibrray position on the front panel which seems to be a huge distance from the rest of the objects.  Moving these objects takes a great deal of time, around a minute each time,  there has to be a better way then recreating the object and duplicating its properties each time on the front panel.   No matter where we align the grid, the new objects go to some arbitrary position.
 
 
 
 
Just wondering if anyone has seen problems like this before....
I doubt is just us.
 
 Message Edited by JimmyinCT2 on 02-05-2008 08:37 PMMessage Edited by JimmyinCT2 on 02-05-2008 08:37 PM
 
 
 

labview problems, file corruptions, hang ups, etc..

Post by jimmyinC » Fri, 08 Feb 2008 09:10:04

i assume your just kidding about the dells.
actually the three computers are all dells
 
the one thing i really care about is getting the file corruption to stop, we lost 2 entire sets of working files two days in a row.
This was before we even figured out what was going on, the total amount of corrupted files is around 100.
 
As an example, last wednesday, we make backups along the way, each hour,  yet, and at teh end of teh day, we cant repoen them, even on otehr pcs.
Most of the time, the processors get stuck at 100%
We remade all teh sub vis with no luck getting this to stop.
 
 
 
Ill post some of the files such as the last version that is not corrupted and one version which is "corrupted" but might not really be.
<a href=" http://www.yqcomputer.com/ ~jmacione/temp/" target="_blank"> http://www.yqcomputer.com/ ~jmacione/temp/</a>
 
It woudl be great if you could find a way to open them.
The file will load to a point where the file says it is compliing or initializing and then just hangs
 
 
As for the others issues, well, lets just do one at a time for now.
I do have other issues, but they dont matter if i cant even save a file anyway  :)
One of the biggest issues is that labview just wont make the computations fast enough, this with a built project file and no graphics, but thats a problem for later.Message Edited by jimmyinCT on 02-06-2008 05:49 PM

 
 
 

labview problems, file corruptions, hang ups, etc..

Post by jimmyinC » Sun, 10 Feb 2008 05:10:11

thanks for the over whelming support.  :smileyindifferent:
 
so after trying to replace all the code, and having no sucess, i did the opposite.
I copied all graphical code to a new blank vi and pasted it in.
This seemed to do the trick, it is now wokring without a problem.