Measurement error from NIDSA_get_olm_status() function

[promba]

(Before anyone asks, yes, we've read the function help page in NidsaC.hlp :))

We have a legacy product that uses an PCI-4552 DSA card.  We have a section of code that runs like this:

ViStatus dsaStatus;

ViStatus newMeasurement;

dsaStatus = NIDSA_check_new_measurement(dsaSession, &newMeasurement);

// Error checking removed for clarity 

if ((dsaStatus == 0) && (newMeasurement))

   {

   dsaStatus = NIDSA_get_olm_status(dsaSession,
                                    dsaChannelNumber,
                                    &elapsedSeconds,
                                    &linearAvgCompleted,
                                    &measurementError,
                                    &overload,
                                    &rt_error);

   }

if (dsaStatus == 0)

   {

   // log the status of any of the arguments to

   // NIDSA_get_olm_status() callthat did not return 0

   } 

The logs from this system report several cases where the measuremenError value is 1 *and* the overload value is 1. 

Does an overload condition always trigger a measurement error condition? 

If dsaStatus returned 0, what other things might be causing measurementError to be non-zero?

Thanks!

--Peter

[Mr.F]

Hi Promba,

Yes, an overload condition will always trigger a Measurement error condition becuase an overload in a type measurement error. You can check the manual, page 4-10 to see what will cause a measurement error.