LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

lv 6.1 crashing

Hi everyone,

I'm experiencing a rather annoying (and increasingly frequent) problem....

I have a program using several different modules for instrument communication (Spectrometer, filter wheel, monochromator etc) which has been running fine for a year or so.

Recently, I have problems with LV bombing out in the middle of a measurement.  No error messages from LV, a system-level crash.  I'm not used to this kind of thing.

Following pictures are details of ONE type of crash (it has two or three different "forms").
The dialogs appear in this order:






Details on my system:
  • I'm using a dell (I've seen reports of problems regarding this before....), but the crashes happened on an old no-name beige box before also.
  • The VIs are saved with diagram on a network drive (Both PCs using WinXP Pro with up-to-date patches).
  • I am calling a DLL for a spectrometer interface, but testing this code on its own for several hours cannot generate a crash.
  • All other functions are built-in G.
  • It seems kind of fond of crashing in the middle os a gauss-fitting routine I've written (Heavily modified Levenberg routine).  This code has also worked without any problems since over a year.
  • I am using 3 RS-232 ports (Filter wheel, Spectrometer, Linear stage) and 2 USB ports (Spectrometer via DLL, Relay via Command-line parameters).
  • The crashes seem random with no single module causing the problems (except for the affinity mentioned above).  Sometimes I can even finish a complete measurement series (oooh) whereas sometimes I only get through 10 or 30 or 50%.
I'm at a loss currently.  I've looked at as much of the code as I can, and I can't see anything wrong.  I've even tried copying the code to new VIs, but this hasn't stopped the crashes.

Please help....

Shane.

Message Edited by shoneill on 10-10-2006 11:11 AM Added pictures

Message Edited by shoneill on 10-10-2006 11:11 AM   Linked to pictures

Message Edited by shoneill on 10-10-2006 11:12 AM

Using LV 6.1 and 8.2.1 on W2k (SP4) and WXP (SP2)
Download All
0 Kudos
Message 1 of 5
(3,117 Views)
Nobody?

Not even a NI engineer who could point me in the very approximate direction as to where the problem is coming from?

I would appreciate even the most vague of hints as to what could be causing this.

The reason is that I'm not able to find where the problem is, or even where the problem is perhaps coming from.

Any input is appreciated.

Thanks

Shane.
Using LV 6.1 and 8.2.1 on W2k (SP4) and WXP (SP2)
0 Kudos
Message 2 of 5
(3,081 Views)
Hello Shane,

It is very hard to find something about your error.
Can you try to break down your error to a minimum of code!
Maybe you can try your code in a higher LV Version (6.1 is offically not supported anymore)

You can get a trial version of LV 8.20 here:

https://sine.ni.com/apps/utf8/nigb.guestbook?code=GB_LVEVAL&lang=D&gb_prof_id=1000&scode=&pr=1000&shadow_flag=N

Best regards

Stefan

0 Kudos
Message 3 of 5
(3,069 Views)
I know 6.1 isn't supported any more, but It's been rock solid until now.....

Either way, it looks like we'll be upgrading to 8.2 soon, so I suppose I'll just hope that the errors will go away then.......

I was hoping that the error message could give SOME insight as to whether the LV core, Windows or a device driver was the problem.

I suppose I'll never know......

Shane.

PS: Can someone at least tell me what "Runtime Error 217" is?

Message Edited by shoneill on 10-11-2006 04:35 PM

Using LV 6.1 and 8.2.1 on W2k (SP4) and WXP (SP2)
0 Kudos
Message 4 of 5
(3,061 Views)
Hi Shane,

Our Database has not much information about this errors.
The error 217 might somehow come from external called dlls.
But I can not get enough information about this error.

Sorry that we can not provider a better solution.

Stefan
0 Kudos
Message 5 of 5
(3,042 Views)