Labview 8.5.1 Newer not better?

[Jared_B]

Jim,

Are you receiving .cpp errors from the LabVIEW Crash?  You said you are able to narrow it down to a last sequence in your VIs.  Looking at your code, I would try to create a smaller piece of code that replicates the issue so you can track it down.  Have you ran your code with highlight execution on and been able to follow your code through to see if any other errors are happening?  Was this code migrated from a previous version of LabVIEW and if so, did it work fine in that version?

[JimSchwendeman]

Jared,

Thanks for the reply!

I am not sure about the .cpp errors, or even where to look for them.  I do know that infrequently, the code will "crash" and then Labview will close all windows and close completely.

I just mentioned the last sequence as where the crash typically occurs, because all the other sequences perform fine, (I have email notifications at the ends of each sequence).  I haven't narrowed it down to see exactly which component is causing this, but I can certainly try to see which object is causing this issue.

This code was migrated from a previous version of Labview, where it worked successfully.  I'm not sure, but I believe it was 8.2.

.jim

[Jared_B]

Jim,

If it were a .cpp error it would be LabVIEW itself crashing because it encountered an error.  You would receive a popup message about this.  If it is crashing otherwise, it could be Windows shutting down the application. 

It would be good to try and narrow down where the problem is occurring and focus on that.  It could be one of the custom sub VIs.  Again, I would try running the program with all sub VIs open and on highlight execution to see if you can determine where an error is encountered, and narrow it down that way.

[JSInc]

As promised, now I post my VI here.

My hardware: PXI-1031 chassis, PXI-8105 embedded controller, PXI-6123 in slot2, PXI-6221 in slot3.

Software: Windows XP, Labview 8.5.1, DAQmx 8.7.1

I had a program upgraded from Labview 8.2.1 to 8.5.1, I found it crashed my Windows (blue screen). Then I contacted NI support about a month ago, we can not figure it out what goes wrong.

Now I rewrite everything from a blank VI in Labview 8.5.1 and simplify my VI, it still crashes my windows. Please see my VI in the attachment. When I open the MainVI and hit RUN, it crashes my Windows immediately.

JSInc

[Jared_B]

JSInc,

Could you provide your simplified VI that is crashing your system?  I ran your VI without any problems.

What happens if you run with highlight execution mode?

[JSInc]

Hello Jared,

The VI in the previous post is the simplified VI that crashes my Windows, it has to be run on the physical hardware to cause crash. It seems fine if I run with highlight execution mode.

Regards,

JSInc

[Jared_B]

JSInc,

I am unfortunately not able to reproduce the behavior you are experiencing.  Are you able to narrow down what is causing this problem?  If you eliminate the second half of your program, does this still happen?

[JSInc]

Hello Jared,

I was able to produce two crashes after I saw your message (#27). I tried a few more times and it did not crash again after that.

However, I found another strange behavior: The program did not exit the while loop after it received a trigger, while it exited immediately when I ran it with simulated hardware.

Based on my previous observations, the program crashed Windows before it received a trigger. In my original program (not this posted simplified VI), I set a break point right before the DAQmx Read (Analog 1D Wfm NChan NSamp) vi (on the error data flow), I can still produce crashes.

Best regards,

JSInc

[Jared_B]

JSInc,

In the reduced program you posted, if you remove the while loop all together, with the event structure, do you still produce crashes?  Also, I'm assuming this loop has something to do with the full program, as I do not see any purpose to it with the program you posted.

P.S. - Sub VIs might be something you will want to look at for future programs.