Multifunction DAQ

cancel
Showing results for 
Search instead for 
Did you mean: 

PCI-4065 agonizingly slow

Solved!
Go to solution

Straight out of DMM examples. The fastest acquistion rate I can get is about 1 reading per second. From PCI?! This is not acceptable. I can get faster acquisitons from a serial device. Anyone know how I can speed things up?

 

DMM.png

 

 

PaulG.

LabVIEW versions 5.0 - 2020

“All programmers are optimists”
― Frederick P. Brooks Jr.
0 Kudos
Message 1 of 8
(3,660 Views)

I'm just shooting in the dark here.  I haven't had any problems like this with my PXI-4072.

 

AC measurements usually are slower than DC.  What happens when you change it to a DC measurement type?

Reading the specs, I don't see a 3.5 digit specification.  It only goes down to 4.5.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 2 of 8
(3,653 Views)

Hi Paul, the DMM will have a minimum aperture time that depends on the combination of the # of Digits you set as well as the Minimum Frequency in the AC bandwidth. 

 

The DMM Measurement Defaults lists the following for Aperture Time

  • AC 6½ digits — 1 sec
  • AC 5½ digits — Max (100 msec or (10/(minFreq)))
  • AC 4½ digits — Max (10 msec or (5/(minFreq)))

Try adding the niDMM Configure AC Bandwidth VI and setting the Min Frequency.

 

 

Steve B

0 Kudos
Message 3 of 8
(3,646 Views)

DC without a wait goes faster than I can see so it's fast enough. I changed to 4 1/2 digits but no effect. I changed to an initiate>fetch multipoint configuration and it had no improvement either.

PaulG.

LabVIEW versions 5.0 - 2020

“All programmers are optimists”
― Frederick P. Brooks Jr.
0 Kudos
Message 4 of 8
(3,645 Views)

Changing my digits did not help or change anything. Playing around with niDMM Configure AC did not help.

PaulG.

LabVIEW versions 5.0 - 2020

“All programmers are optimists”
― Frederick P. Brooks Jr.
0 Kudos
Message 5 of 8
(3,641 Views)
Solution
Accepted by PaulG.

I overlooked it before but the default settling time for the ACV mode is 1.5 seconds and the DMM Measurmeent Cycle will wait for the settling time and then the aperture time. The path is AC coupled and could take quite a bit of time to settle if the DC component changes. 

 

You can try reducing the Configuration:Advanced:Settle Time Property to something more reasonable for your input signal.

 

Steve B

0 Kudos
Message 6 of 8
(3,632 Views)

@Steve_B wrote:

I overlooked it before but the default settling time for the ACV mode is 1.5 seconds and the DMM Measurmeent Cycle will wait for the settling time and then the aperture time. The path is AC coupled and could take quite a bit of time to settle if the DC component changes. 

 

You can try reducing the Configuration:Advanced:Settle Time Property to something more reasonable for your input signal.

 


This appears to work. Troubles me that I have to go so far under the hood. It's a simple AC measurement. And now I have to run more tests to make sure I'm getting accuracy. Troubling.

PaulG.

LabVIEW versions 5.0 - 2020

“All programmers are optimists”
― Frederick P. Brooks Jr.
0 Kudos
Message 7 of 8
(3,614 Views)

Hi Paul, you are configuring almost everything in the measurement cycle. The switch time is configured when your system involves handshaking, etc with an external switch. You can see the entire cycle outlined here. The 4065 defaults are listed on another page here

 

When you are running in the single point mode the settling time occurs for every measurement. If you work with the Acquire and Graph Multi Samples example and set your Minimum AC Bandwidth the very first measurement will have the 1.5s settling time to be sure that the DC component settles out but subsequent measurements in the same set will not have the settling time. For example if you measure 1000 points at 4.5 digits, the first point should take 1.5s and subsequent points should take 10ms each (assuming a high enough minimum frequency).  

Steve B

0 Kudos
Message 8 of 8
(3,601 Views)