LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Blank VIs Continually Pop-up Upon Launch

Hoping to get some insight on an issue we're having w/ LabVIEW 2010 SP1 installed on a Dell Latitude running Windows XP SP2.

 

We're controlling an external instrument with a VI that seems to work correctly.  We have consistently been able to run the VI, collect .txt files comprising accurate data, etc. while testing indoors.  This past weekend, during our first field test, our VI was terminated after ~32 hrs of continuous data collection.  The computer was off when we discovered it today.

 

Now, I am unable to open the VI in LabVIEW without sending the program into an error loop that requires CTL+ALT+DEL to escape from.  The specified VI seems to open correctly at first.  Immediately after it opens, it is replaced by "Untitled 1 Front Panel" and "Utitled 1 Back Panel," which flash briefly on the screen.  The same thing happens w/ files being renamed untitled 2, 3, etc.  This continues ad infinitum until I force close LabVIEW.  At that point, we are not even able to run our desired VI.

 

I've searched to see if this issue has been described before.  I surmise it's a LabVIEW install error or PC hardware issue.  Since the VI worked fine (when it ran) and the computer has been restarted during the troubleshooting process (to rule out a COM-related error), those are the main options...right?

 

Thanks in advance for your help.

 

Message 1 of 6
(2,728 Views)

LV may have gotten corrupted.   Have you tried it on another system?  What is the behavior of another program that you've written?  You can try doing a repair of LV in Control Panel>>Add/Remove Programs, but first I would verify that your development system has an issue.

 

-----------------------------------------------------------------------------------------
Reese, (former CLAD, future CLD)

Some people call me the Space Cowboy!
Some call me the gangster of love.
Some people call me MoReese!
...I'm right here baby, right here, right here, right here at home
0 Kudos
Message 2 of 6
(2,712 Views)

I agree with MoReese here.  You may be better off just running an install and reinstall because it sounds evident of corruption.  Please keep me updated on whether this solves the issue or if I can help with the issue any further.  

 

Regards, 

 

Benjamin N 

Applications Engineering

National Instruments

Regards,

Ben N.
Applications Engineering
ni.com/support
0 Kudos
Message 3 of 6
(2,683 Views)

@Benjamin38 wrote:

I agree with MoReese here.  

 


That's too bad.  I was hoping to have an AFC-NFC rivalry going here (Any chance you like the Oakland Raiders?).Smiley Mad

-----------------------------------------------------------------------------------------
Reese, (former CLAD, future CLD)

Some people call me the Space Cowboy!
Some call me the gangster of love.
Some people call me MoReese!
...I'm right here baby, right here, right here, right here at home
0 Kudos
Message 4 of 6
(2,675 Views)

Thanks MoReese - we were able to snap a screen print of the dialogue box that kept fleeting by as we force closed the program.  It referenced a specific corrupt file.  We did a repair and the VI (and LabVIEW) appears to be working correctly again.

 

Hopefully it will stay that way.  We reformatted the PC especially for this use and didn't get any LabVIEW install errors when we first loaded it...so fingers crossed this is a permanent fix.

0 Kudos
Message 5 of 6
(2,670 Views)

Glad to hear it.  I hope things work out.

-----------------------------------------------------------------------------------------
Reese, (former CLAD, future CLD)

Some people call me the Space Cowboy!
Some call me the gangster of love.
Some people call me MoReese!
...I'm right here baby, right here, right here, right here at home
0 Kudos
Message 6 of 6
(2,664 Views)