Reading the number from a certain column in an running .CSV file

[RTSLVU · Accepted solution]

Here's an example of how to properly use this device. This program was an Accelerated Lifecycle Test that used TWO FULLY LOADED 34790A's to monitor temperatures, and output voltages for must have been 30 individual units under test.

34970A #1

1. Initialize 34970A 
2. Configure DC voltage measurements
3. Configure AC voltage measurements
4. Configure K type thermocouples
5. Configure Scan list
6. Configure Scan

23970A #2

1. Initialize 34970A
2. Configure 60 K type thermocouples
3. Configure Scan List
4. Configure Scan

Now this one looks complicated, but it's not really. This is where I take measurements Sort, display, and save them to a file. SO most of the mess is sorting things for display. Follow the Error Cluster for the important parts that I will touch on.

1. Take a measurement (Scan 34970A's) 
   1. I wrote my own "Agilent Scan.vi" years ago to make it more user friendly. My vi outputs data in three forms. Numeric Array, String Array, and a "CSV string". Long ago I found that helpful, but honestly I onlt ever use the Numeric Array output anymore.
   2. I will attach this VI for you.
2. Write data to file (1D Array to XLS)
   1. Now this vi of mine is very handy. It takes an array of numerics add a time stamp, and writes them to a text file that can be opened by Excel.
   2. I will attach this vi too 
3. The rest of this diagram is sorting measurements for display and writing to four other files

[eevisi.chen]

Hi, RTSLVU:

Do appreciate you attached so useful sample, to a rookie like me who just jumped into LV for one month.

The 60 K-type thermoCoupling vi is already very close to my demand, to improve my daily work becoming more efficiently.

My great honor to be guided by a senior like you.

eevisi

[eevisi.chen]

Hi RTSLVU:

Followed your comment, I tried to setup the 34970A by the device in LabVIEW.

But something was not correct & I have no idea what's going wrong....

Please see another thread in forum by the link:

https://forums.ni.com/t5/LabVIEW/Channel-missing-amp-amp-write-the-data-in-csv-file/m-p/3943518

Have you met similar issue when you program it?

B/R

eevisi 

[Shannara]

Can I get this VI, it really helps me.

Thanks

[Shannara]

Dear Labview users,

I am using Agilent 34972a data logger with three 34901 multiplexer cards, with 60 channels set up by using the LabVIEW program for the DC voltage measurements. 34901 multiplexer cards can read 60 channels per second.

Here, my query is when I run the LabVIEW program with 0.4 aperture value it is reading the 60 channels with less amount of time like 2 seconds (which I need), but the accuracy of the values not right and which is giving the wrong measurement data (which I don’t want). When I use NPLC (number of power line cycles) ad 1, the accuracy of the measurement data which is very precise (which I need) but it is taking around 12 seconds to read the 60 channels (which I don’t want). I want to complete the whole loop in just 4 or 5 seconds at least.

Is there any way to speed up the program by measuring the accurate measurements?

[GerdW]

Hi shannara,

this sounds like a typical tradeoff between accuracy, number of channels, and time needed for measurement!

Does the manual of your device provide any "best practices" for your kind of problem?

[Shannara]

No, I did not find the best practices in the manual.

Do you know anyway that I can make it faster?

[RTSLVU]

@Shannara wrote:

 34901 multiplexer cards can read 60 channels per second.

I am pretty sure the specification is UP TO 60 channels per second. 

Measurement speed is of the 34971A or 34972A determined by a few things here's some tips

1. Ranging
   1. Autorange takes longer
   2. Set the range for every channel when you initialize the instrument
2. Switching modes between channels takes more time
   1. Group like measurement channels and ranges together to reduce the number of times the instrument has to switch measuring mode or range
3.  Accuracy
   1. Less digits of accuracy are faster more digits of accuracy is the slower
4. Aperture, lower is faster
5. NLPC, (Number of Power Line Cycles to wait) lower is faster

BTW: There is a section in the manual that discusses this in detail.

Also PLEASE tell me you are NOT using any of the "EZ" vi's that come with the 3497xA LabVIEW drivers.

[Shannara]

Thank you so much for the reply and with the brief answer.

1. I have used Auto range all the time because with the auto range I was getting the right answers and without auto-range, the measured values are not accurate.

2. I always used the high precision measurements so, I will change it to less digits of precision.

3. When I use the Aperature the measured values are shifting a little.

4. When I use the NPLC method, I find these are accurate measured values.

one thing I want to tell you that, When I use EZ.vi those are also taking time for measuring as same as the NPLC method. (because the EZ.vi LabVIEW code syntax is simple, it doesn't include any Aperature and NPLC) it includes only range and precision. 

When I used Voltage config.vi, I find it better but the problem is the accuracy. 

I request that, could you please sent me the link for the Manual which is for the coding, and as you said they explained about it.

[RTSLVU]

Here's a link to the manual https://literature.cdn.keysight.com/litweb/pdf/34972-90001.pdf?id=1837993

Honestly I cant' find the section I was looking for, a lot has changed since these instrument were made by HP.

But read General Measurement Configuration through Custom A/D integration time and the full Voltage Measurement Configuration sections in the Features and Functions chapter and you might pick up a couple things.