LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

Possible bug in NI-DAQ/CVI 6.0

I have written an application that uses the GPCTR functions to measure pulse time period, and also acquires data using interval scanning.

I have noticed that if I start pulse time period measurement, then terminate it using GPCTR_Control (,,ND_DISARM), the next call to SCAN_Op() or SCAN_Start() has problems with the DMA transfer and after one or two calls to SCAN_Op() or SCAN_Start() the PC crashes with the blue screen or causes CVI to terminate (usually the former on my machine).

Looking at the binary data acquired before the machine crashes shows the acquisition to be incomplete, as if the pointers have become corrupted.

However, I have also discovered that terminating the time period measurement with GPCTR_Control(,,ND_RESET) preve
nts the problem from occuring.

Should ND_RESET always be used over ND_DISARM?

Is this a known bug?

Jamie Fraser
0 Kudos
Message 1 of 2
(2,988 Views)
Jamie;

ND_RESET disarms and resets the counter parameters back to their default state.
In case you have the need to run the code multiple times, without reseting the device, it's better to use the ND_RESET parameter as oppose to the ND_DISARM parameter.

Regards
Filipe A.
Applications Engineer
National Instruments
0 Kudos
Message 2 of 2
(2,988 Views)