LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Labview: Null Window ... stopped at unknown on the block diagram

Solved!
Go to solution

Hi,

 

I have a fairly large program that was written in Labview 6.0. Recently we upgraded to Labview 9.0 and this program was exported to an executable with the new version.

 

When running the executable I sometimes get the following error as seemingly random places. I have not been able to make it crash when not using the executable. Labview: Null Window. The top-level VI ".vi" stopped at unknown on the block diagram of ".vi"

LV9error.JPG 

 

I apologise for having to blank out the vi names but i cannot give vi names, say what the software is used for or give over code. I can say that it uses NI USB 6212 IO cards, interfaces with Rhode and Swartz instruments and uses alot of file IO.

 

I was hoping that someone could give me a hint on how to debug such an error. I have noticed that When this error occurs, the memory use almost doubles.

 

Thankyou

 

James 

0 Kudos
Message 1 of 11
(7,903 Views)

Hi James,

did you try it with the debug functionallity of applications? Do you call vi's dynamically?

 

Mike

0 Kudos
Message 2 of 11
(7,898 Views)

I think you open the front panel of a VI that has it's front panel removed during the build. Try to adjust the built settings of that specific VI to include the front panel.

 

Ton

Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas

LabVIEW, programming like it should be!
Message 3 of 11
(7,892 Views)

Thanks for the replies!

 

I have gone through and unticked all the boxes to remove the front panels. I thought we were on a winner but it is still giving this error.

 

It appears to happen at the same place. This program has a few different operations run from buttons on a front panel. Occasionally it crashes running one of these buttons. It is the first VI called that has a front panel enabled. Most of the time is runs fine.

 

Any more thoughts?

 

Thanks

James 

Message 5 of 11
(7,851 Views)

Ok, I have been looking at this code all day now. I have narrowed down what is happening.

 

As i said before there are two buttons. The first collects data and saves it to files. The second loads from these files and  displays the data. Read and Write Spreadsheet file is used for the file IO. Both buttons address the same VI. This VI either saves or loads depending on the input.

 

If data is collected (button 1) and then read (button 2), it will crash at the first VI with a front panel enabled giving the error stated above.

 

If data is collected (button 1) then the application is exited and restarted. Then the data is read (button 2), it will work without an error.

 

As stated earlier, when it crashes the memory in use doubles.

 

Thanks for any input. 

 

Regards

 

James 

0 Kudos
Message 6 of 11
(7,837 Views)

Hi James,

 

Do you get an option to "investigate error" when you reopen LabVIEW? You can go through those steps so that the error log is sent to National Instruments and we can take a closer look at the reasons for LabVIEW crashing. Hope this helps!

 

Ipshita C.

National Instruments
Applications Engineer
0 Kudos
Message 7 of 11
(7,825 Views)

Hi,

 

No there is no option to investigate error.

 

More experimentation has shown that it never crashes when run from the VI.

 

It is only crashing from the executable.

 

I believe I have made sure all front panels etc are included but now that i have narrowed it down to an executable problem, i will experiment with a few different options.

 

Cheers

James 

0 Kudos
Message 8 of 11
(7,812 Views)

Is there something I am missing here? 

 

exprop.JPG

0 Kudos
Message 9 of 11
(7,809 Views)

Hi,

 

More fidling.

 

If i enable Reentrant Execution on the VI that comes up with the error, the error moves on to the next VI with a Front Panel enabled.

 

So it looks like a partial solution, if i enable this on every VI with a front panel.

 

Is there something i am missing here? This shouldn't be required? 

 


0 Kudos
Message 10 of 11
(7,787 Views)