One of the VI stops

[Joseph_Loo]

The VI is is in a Sub-panel. It is running on its own loop. If I recall correctly, it never happen before.

[JamesR]

Hi Joseph,

Paring down the code to be as simple as possible while still reproducing the problem would be a good way to troubleshoot this.  Or trying the architecture JoeLabView suggested might take care of the problem as well.  What is supposed to cause the condition that stops the subpanel VI?

[Joseph_Loo]

I believe that has to do with one of the running VI within the sub-panel.

The only way the VI  stop is to terminate all the programs at the same time.

The reproducing the problem is difficult at best. It askes 2 or 3 weeks of continuous running before it happens. I was hoping there is a way to log the situation or look for some kind of files to tell me what has happen.

[JamesR]

Hi Joseph,

Since the problem has only occurred once, it may be difficult to narrow down what's going on.  My best suggestion would be to handle your errors in that subVI (an error message won't automatically pop up if the VI is run in a subpanel), and if it stops running again, the error might reveal more clues as to what happened.

[Joseph_Loo]

That is part of the problem. The VI contact is through some global variables. All it does is basically display the data and keep a logging data. It is not clear at this time the VI is erroring out. It could be a schedule problem with Labview where it starved the VI to death.

That is the reason I am for any suggestions to help probe for these kind of problems.

[JamesR]

Hi Joseph,

My best suggestions are to handle and log any errors that occur.  Also, you could monitor the execution state (a property of VIs) of the VI.  You could also possibly get the front panel image of the VI when it stops.  One other thing to try is profiling the VI to make sure it's not eating up memory.

[Joseph_Loo]

The problem, there is not much to log. There are vitually no place where errors are generated. the only place where it is not running by itself is when it prints a file but the VI that error out has the printing turned off

I am checking the memory used in the computer using the task manager. The machine that does not have the problem actually consumes memory faster  than the machine that has the VI stopping. In both cases, the memory used is below the total amount of physical memory.

[JamesR]

One thing you might do to monitor how the VI stops is record any True values sent to the while loop conditional terminal.  If the conditional terminal receives a true, you could get the time, iteration count of the loop, and any other pertinent information you can think of and write the information to a file or pass it to another VI.  This would at least give you more information with which to work.

[Joseph_Loo]

I will try what you mentioned by displaying the values and the iteration count of the main loop.