External clock LabView crash with Measurment Computing board.

[dontknow]

Hi,

I'm using a Measurment Computing PCI-DAS6402-16 board with Labview (using Universal librarys VIs) in a 4-stroke engine DAQ application and amognst the signals obtain Internaly clocked, there is In-Cylinders Pressure signal which is timed with a Crank-angle deocoder sending analog pulse signal.
Although there seems to be no problem while the motor is running, it appears that when to external clocked signal  is not getting any pulses (while the motor is not running) then Labview stops to respond and awaits for the external clock to start, and that doesnt happen within 10s then it crashes.

I dont know whether it is Software problem (because external and internal clocked signals are both in the same WHILE LOOP) or if it is a Hardware problem (because With a NI card there seem to be no problems).

THNX in Advance

[Broken_Arrow]

I think you'll need to post code before getting help on that. There's a million things that could cause your issue. From reading your post, the first thing that strikes me is the 10 seconds, which sounds like the default timeout on some VISA functions. Your data, not being there, could cause a timeout, and without propper error handling, a crash.

[Matthew_Kelton]

By crashing, do you mean that LabVIEW or your EXE crashes and you have to restart the program, or do you mean that your program stops working, generates an error, or something else, but continues to be responsive to user input, etc.?

[dontknow]

Well it couldnt be a more typcal windows crash:
If a channel is externally timed with an analog pusle signal, If the VI starts running but the external clock isn't then:
-Labview stops to respond to any clicks (there is no .exe at this point) but it keeps working though (That i know cause if i start the ext. clock at this point it "un-stucks' and starts working)

-But, if for some secs no ext. pulse signal is generated then labnview app stops respondin and i get the typical 'send error report' window.

Could it be that the Universal library for Measurment Computing boards haw a bug? Cause the same thing happens with the "Analog input External Clock.vi" example given with the Library..so it can't be my mistake..or can it?!

[Matthew_Kelton]

It wouldn't surprise me that their driver would have a bug.  You may want to contact Measurement Computing directly and try to determine this.  What you may want to try is a very basic example to demonstrate the behavior, that has as little of your code as possible.