Multifunction DAQ

cancel
Showing results for 
Search instead for 
Did you mean: 

NI4060, MSVC++ and over range detection. How?

I am using the NIDMM api in a MSVC++ application. Other than clumsily
comparing the aquired floating point measurement to the current range, how
can I detect if an overrange condition occurred? I've tried to call
Ivi_Dmm_IsOverRange(), but this function does not appear to be bound to
nidmm_32.lib.

Thanks,
Chris Lincoln
ULTRAX, Inc.
0 Kudos
Message 1 of 2
(1,905 Views)
On Mon, 7 Feb 2000 11:32:25 -0600, "Chris Lincoln"
wrote:

>I am using the NIDMM api in a MSVC++ application. Other than clumsily
>comparing the aquired floating point measurement to the current range, how
>can I detect if an overrange condition occurred? I've tried to call
>Ivi_Dmm_IsOverRange(), but this function does not appear to be bound to
>nidmm_32.lib.
>
>Thanks,
>Chris Lincoln
>ULTRAX, Inc.
>

Chris,
This is a known problem with niDMM 1.1 and is being addressed
in the next release of niDMM. For the moment, comparing to the
current range is the only option. There is one gotcha with this
approach, though. Some measurement modes have the ability to take a
measurement beyond the set range. Some ranges don't. For the ranges
that don't
, the value returned is the range. For the ranges that do,
the value returned is whatever the maximum is. For example: on the
250V DC range, up to 300V DC can be returned. On the 2000 Ohm range,
the max ever returned will be 2000 Ohms. The new behavior will be NaN
returned when over range and niDMM_IsOverRange will exist and return
the appropriate value. The next release will be sometime after NI-DAQ
6.7 is released.
0 Kudos
Message 2 of 2
(1,905 Views)