02-01-2008 12:37 PM
02-01-2008 01:21 PM
02-01-2008 03:12 PM
02-01-2008 03:59 PM
I am not sure of the old version. I think it may have been 1.51 from memory. The installation of the new version blew away all traces of the old.
The pertitent steps in the code are the following
sprintf(resourceName,"DAQ::%i",resource);
// Open the NI-SCOPE instrument handle
handleErr (niScope_init (resourceName, NISCOPE_VAL_FALSE,
NISCOPE_VAL_FALSE, &vi));
if(vi == VI_NULL) GetDataEditCntl->MessageStr = "DAQ Not Available";
niScope_reset(vi);
error = VI_SUCCESS; // Initialize
// Call auto setup, finds a signal and configures all necessary parameters
error = niScope_AutoSetup (vi);
if(error < 0 ) {
GetDataEditCntl->MessageStr = "Autosetup Fail";
return -1; }
if(error > 0){
niScope_error_message(vi,error,errormessage);
GetDataEditCntl->MessageStr = errormessage; }
The message that is returned from AutoSetup is a warning that it could not find any signals. Previously, this message was only returned if both channels did not have signals. They both do have a wideband noise signal applied for the testing. For applications like mine, (Radio Astronomy) wideband noise is a valid signal.
02-01-2008 05:45 PM
I looked into how our autosetup algorithm has changed over time. The original algorithm was purely based on the min and max voltage on a channel. This algorithm worked well for configuring the vertical settings of the device; however, the algorithm didn't perform well for other types of signals. Autosetup was then changed to use a FFT based algorithm which works very well for many signals. Unfortunately, the FFT algorithm doesn't work well for your wide band signal. I'm making modifications to the algorithm to include both the FFT and min/max power as a selection criteria. The changes will probably be available in NIScope 3.5 or 3.6 which will be released later this year.
In the mean time you could modify your code to take a dummy acquisition on each channel. Niscope has measurement functions for min and max voltage. Using those values you could set the vertical range of the digitizer appropriately.
Sorry for the trouble, but thanks for the feedback.
02-01-2008 06:07 PM