How to Measure Voltage Using NI 6001 and Calibrate Using LabVIEW

[TanmayBoii]

Hello GerdW,

Can you send a sample code for that tare problem for reference.

[GerdW]

Hi Tanmay,

see message #7…

[TanmayBoii]

Hello GerdW,

I tried Making the tare/zeroing code but I'm stuck. Please help me I'm new to LabVIEW.

I'm attaching the code in 2018 version

[GerdW]

Hi Tanmay,

• replace BundleByName with a plain Bundle function
• replace the graph with a chart
• set the datatype of that "5" constant to DBL to avoid the coercion dot
• connect the "Numeric" indicator to the output of the FromDDT ExpressVI

(As has been shown in message #7! Why didn't you use the supplied snippet?)

[TanmayBoii]

Hello GerdW,

I made the code and I'm getting a Good output with a difference of 0.02 to 0.05.

Is there any way to remove those differences too ?

also I'm attaching the code for reference.

[GerdW]

Hi Tanmai,

---

@TanmayBoii wrote:

I made the code and I'm getting a Good output with a difference of 0.02 to 0.05.

Is there any way to remove those differences too ?

---

Question: what is the measurement range and what is the expected noise level?

(When the offset always is positive then there is a systematical error, which can be corrected. When the offset fluctuates around zero then it's a random error (aka "just noise")…)

You may apply more averaging and you may do better taring (aka tare as often as you want to), but I don't think that will help without introducing other problems!

[TanmayBoii]

Hey GerdW,

can you guide to how to add write to measurement and take reding for every 15 minutes without disrupting Tare/zeroing button.

I've added one but, for after clicking tare button it tares after 15mins.

[GerdW]

Hi Tanmay,

---

@TanmayBoii wrote:

can you guide to how to add write to measurement and take reding for every 15 minutes without disrupting Tare/zeroing button.

I've added one but, for after clicking tare button it tares after 15mins.

---

I don't see anything in your latest VI related to "15 minutes"…

What I see:

• There still is an additional wait function next to the DAQAssistent: Let DAQmx do the loop timing on its own!
• The DAQAssistent is set to read 100 samples at 1kS/s: this will take about 100ms. Why do you wait for 500ms?
• The DAQAssitent is set to "N Samples" mode: why not use "Continuous mode" when you read samples continuously?
• Why use DAQAssistent at all, when all example VIs coming with LabVIEW explain the usage of "normal" DAQmx functions? (Read this!)
• Why not save measurement data once each 15mins*60s/mins*10iterations/s? Then you will get your data and will not "disrupt" the taring…

[TanmayBoii]

Hello GerdW,

sorry for Inconvenience, actually I added a flat sequence for write for measurement but it failed.

so, you're recommending me to use DAQmx instead of DAQ assistant.

I need to understand how to measure values for 15mins in DAQmx without hampering the tare/zeroing button.

Also, Thankyou for your suggestion even I was thinking of using DAQmx

Please help me with an example or hints

[GerdW]

Hi Tanmay,

---

@TanmayBoii wrote:

I need to understand how to measure values for 15mins in DAQmx without hampering the tare/zeroing button.

---

Think about it: measuring once for 15mins is the same as measuring 9000 times for 100ms!

(You already have a loop to measure for 100ms: you just need to iterate 9000 times…)