To compare the ADC I assume you will need to divide by the used range, also only compare the same number of PLCs, the distribution graphs would then be in ppm. (not nV)
Meaning ppm from range?
Representation is easy to modify.
0.01 NPLC 0.1 NPLC 1 NPLC 10 NPLC 50 NPLC 100 NPLC 1000 NPLC
0.01 NPLC 0.1 NPLC 1 NPLC 10 NPLC 50 NPLC 100 NPLC 1000 NPLC
TiN,
I have been busy this past week but I believe I have the 3458A working with all 35 data sets in an automatic acquisition. I hope to modify it with little changes on the newer SCPI meters. I can create all 35 files with one run.
I just need clarification on the data set sizes. I have the script written to acquire based on NPLC size. Would you break down a list of samples / NPLC? Dr Frank mentioned up to 10K samples on the .01NPLC setting and decreasing from there. I just have to plug in the numbers and run the test.
I do have one odd issue that is nagging me. Occasionally, the meter will output a perfect 0.0000000 reading. It is annoying and I don't think it is a good sample. I will add code to ignore it unless you believe there is reason to keep it. I have attached the file. I will try this on another 3458A to see if this may be part of the controller or software.
function parserk(d) {
d.vmeas = +((d.vk15 / 2) * 1e6)-0.395;
d.v2002 = +((d.vk2002 / 2) * 1e6)+1.42;
d.vk13 = +((d.vk13 / 2) * 1e6)+0.74;
d.vk12 = +((d.vk12 / 2) * 1e6)+0.32;
return d;
}
Why I want combine multiple data sets on same graph? Well, this will allow to have multiple ranges and/or multiple NPLC settings shown by one graph on same meter. I don't think comparing 32 graphs for one meter with 32 graphs for another meter would be great idea..
Any suggestions?
Why I want combine multiple data sets on same graph? Well, this will allow to have multiple ranges and/or multiple NPLC settings shown by one graph on same meter. I don't think comparing 32 graphs for one meter with 32 graphs for another meter would be great idea..
Any suggestions?
Sequence[0] := '32'; Sequence[1] := '22'; Sequence[2] := '31'; Sequence[3] := '30'; Sequence[4] := '--'; Sequence[5] := '--'; Sequence[6] := '--';
Sequence[7] := '--'; Sequence[8] := '--'; Sequence[9] := '--'; Sequence[10] := '--'; Sequence[11] := '33'; Sequence[12] := '34'; Sequence[13] := '20';
Sequence[14] := '21'; Sequence[15] := '23'; Sequence[16] := '24'; Sequence[17] := '--'; Sequence[18] := '--'; Sequence[19] := '--'; Sequence[20] := '--';
Sequence[21] := '--'; Sequence[22] := '--'; Sequence[23] := '--'; Sequence[24] := '--'; Sequence[25] := '10'; Sequence[26] := '11'; Sequence[27] := '12';
Sequence[28] := '13'; Sequence[29] := '14'; Sequence[30] := '00'; Sequence[31] := '01'; Sequence[32] := '02'; Sequence[33] := '03'; Sequence[34] := '04';
I have attached a script that works with the Keithley 2001 and EZGPIB. It will acquire all 20 different Range/NPLC combinations and has been tested with both the Prologix USB and Ethernet adapters.
The original script I posted was rewritten and and is based on the 3458A script. The output was formatted similar to TiN's sample data.
I will post the 3458A script tomorrow when I finish the first run and verify the results.
Dr. Frank
Graphing script does not calculate RMS noise, as well as SD, mean, min, max values and sample window math, but that would be not hard to add after we get all display data format and representation finalized.
macboy
I used READ? as well before. And simply changing READ to FETCH or DATA does not work well, with DATA it does not actually trigger measurement, but just takes reading, while FETCH gives bunch of errors when trying to run on two meters, blocking both.
P.S. Also funny note, running EZGPIB makes my one of my 2001's emit high-pitched buzz. I hear electrons moving in meter's brain, as buzz is different when sampling at different NPLCs Did not had it before with LabView.