Products > Test Equipment
Rigol DS1000Z series buglist continued (latest: 00.04.04.04.03, 2019-05-30)
ebastler:
--- Quote from: video on May 01, 2017, 07:10:20 pm ---The second bouton "Output" could be named "WFCal" for "Write File Calibration" and of course the first hidden button (what is named "LFCal") seem to be "Load File Calibration".
But i didn't try to "Load" (if it's really a loading function..)..to much afraid..
--- End quote ---
That's quite plausible! We already know that "Output" writes a calibration file to USB; and as the two buttons are grouped together, "LFCal" could indeed be its counterpart. I was too much stuck on interpreting it as "low frequency calibration", so this would not have occured to me.
I can't figure out, however, what this would be used for. Why would one want to store and recall a calibration, rather that redo a fresh calibration (after some time has passed, or after a firmware upgrade, or...)? Well, I guess those to buttons are only meant for debugging or service purposes anyway. I don't think I will try an "LFCal" any time soon...
video:
Yes, as is a hidden button, it's probably for development/debugging, but if it exists, there is a reason :) even if it seems not logic to load a such file; but loading is quicker (fresh calibration can take an half hour), may be it's usable after some kind of reset or firmware update..i don't know
Sredni:
I wonder what the calibration data is...
For example:
{//CH1
500 ,ATT_X1 ,G_X2 ,1 ,13 ,4233 ,
1000 ,ATT_X1 ,G_X2 ,1 ,13 ,2116 ,
2000 ,ATT_X1 ,G_X2 ,1 ,13 ,1058 ,
5000 ,ATT_X1 ,G_X2 ,1 ,10 ,1058 ,
10000 ,ATT_X1 ,G_X2 ,1 ,7 ,1058 ,
20000 ,ATT_X1 ,G_X2 ,1 ,5 ,1058 ,
50000 ,ATT_X1 ,G_X2 ,1 ,2 ,1058 ,
100000 ,ATT_X1 ,G_X0625 ,1 ,3 ,1364 ,
200000 ,ATT_X1 ,G_X0625 ,1 ,1 ,1364 ,
500000 ,ATT_X50 ,G_X2 ,1 ,7 ,1080 ,
1000000 ,ATT_X50 ,G_X2 ,1 ,5 ,1080 ,
2000000 ,ATT_X50 ,G_X2 ,1 ,3 ,1080 ,
5000000 ,ATT_X50 ,G_X0625 ,1 ,3 ,1392 ,
10000000 ,ATT_X50 ,G_X0625 ,1 ,1 ,1392 ,
}
...
or
------------100M-----------
{
{,32732,32699,32634,32640,32649,32670,32753,34786,36988,32664,32696,32771,34929,37221},
{,32721,32688,32622,32624,32628,32639,32668,34702,36814,32639,32659,32697,34817,37029},
{,32673,32640,32575,32578,32584,32593,32647,34635,36700,32596,32621,32673,34774,36992},
{,32744,32712,32646,32653,32660,32676,32741,34825,37032,32671,32699,32760,34904,37250},
},
...
bitseeker:
--- Quote from: ebastler on May 01, 2017, 07:36:59 pm ---I can't figure out, however, what this would be used for. Why would one want to store and recall a calibration, rather that redo a fresh calibration (after some time has passed, or after a firmware upgrade, or...)?
--- End quote ---
Perhaps to recreate a known state of the machine to reproduce particular results. It could also be useful if running a new self-cal didn't work properly for some reason.
garnix:
That sounds neat - I always see some small offset after calibration. Perhaps with some editing and reloading that file we could tune it to get rid of that offset...
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version