LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Trouble with niDMM Overrange

Solved!
Go to solution

Dear NI Community, 

 

I am trying to measure some capacitance in parallel that should give me 6uF in theory. My PXIe4082 always returns an error with over range (code : 1073356901), even if I am trying with every range possible. Do you have maybe some idea about with parameters I can use to solve this issue ? I am 100% sure of the MUX channel I am using and 100% sure that all the capacitance are good.

 

I am attaching a screenshot of a VI where I tried every range. However at the end, it will be in a TestStand sequence. 

 

Capture.PNG

 

 

 

 

Thanks a lot in advance for you answer, 

 

Best regards

 

0 Kudos
Message 1 of 4
(313 Views)
Solution
Accepted by al0909

For sanity check, try connecting that capacitor directly to DMM terminals, use the DMM Soft Panel and perform measurement. If you aren't able to measure, then, something is wrong with hardware. If successful, gradually add complexity until you reach the end goal, this way, you will be able to narrow down the problem.

Santhosh
Soliton Technologies

New to the forum? Please read community guidelines and how to ask smart questions

Only two ways to appreciate someone who spent their free time to reply/answer your question - give them Kudos or mark their reply as the answer/solution
Message 2 of 4
(285 Views)

 

You do realise you have the ERROR chain looping back to the start of your loop? Meaning, once an error occurs, it gets propagated to all range measurements.

Try changing the Shift register to an indexing tunnel.

---------------------------------------------
Former Certified LabVIEW Developer (CLD)
Message 3 of 4
(266 Views)

@Frozen wrote:

 

You do realise you have the ERROR chain looping back to the start of your loop? Meaning, once an error occurs, it gets propagated to all range measurements.

Try changing the Shift register to an indexing tunnel.


I think that it is good practice to have the error wire in a shift register when using a FOR loop to guard against the FOR loop iterating zero times and losing the incoming error in the process. Maybe a better way is to clear the error. An even better way would be to understand the error and handle it.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
Message 4 of 4
(231 Views)