Author Topic: Anritsu AutoCalData  (Read 549 times)

0 Members and 1 Guest are viewing this topic.

Offline jjoonathanTopic starter

  • Frequent Contributor
  • **
  • Posts: 836
  • Country: us
Anritsu AutoCalData
« on: July 04, 2022, 05:29:40 pm »
Does anyone have Anritsu AutoCalData files they would be willing to share?

I have figured out the serial controls for my 36585K and I have written a python tool that uses it, in combination with its AutoCalDta file, to perform a calibration. I am in the process of putting this code into scikit-rf. However, I only have the one ACD file to test with, so I don't really know how well it generalizes. Besides, it would be nice to have a library of typical data in case anyone buys "as-is" and needs to diagnose their purchase. If anyone has ACD files for some of the related autocals (or, heck, even another 36585K) could you send me a copy?

36581NNF
36581KKF
36582KKF
36585K
36585V

PS If you have access to an Anritsu VNA, I think the file should live in
Code: [Select]
C:\Anritsu\VNA\AutoCal\V123456.ACD
Thanks!
 

Offline metrologist

  • Super Contributor
  • ***
  • Posts: 2239
  • Country: 00
Re: Anritsu AutoCalData
« Reply #1 on: July 15, 2022, 09:26:01 pm »
AutoCal has one Short, one Open, three Loads, and four Thrus. The Shorts, Opens, and Loads are measured on both ports giving three S11 measurements and three S22 measurements. The Thrus are measured between the ports giving four sets of S11, S12, S21 and S22, for a grand total of 26 Sxx measurements. Each Sxx measurement is a real-imaginary pair in CSV format.

The file is formatted as xml data and you should be able to edit the file you have to create as many characterization data sets as you want:
<Autocal.Characterization Date="mm/dd/yyyy" Time="hh:mm A/PM">
<Version>
</Version>
<Serial>
</Serial>
<Module.Type>
</Module.Type>
<Assurance.True>
</Assurance.True>
<Start>
</Start>
<Stop>
</Stop>
<Deltaf>
</Deltaf>
<NumberPts>
</NumberPts>
<FreqList>
</FreqList>
<Load1.L>
</Load1.L>
<Load1.R>
</Load1.R>
<Open.L>
</Open.L>
<Open.R>
</Open.R>
<Short.L>
</Short.L>
<Short.R>
</Short.R>
<Thru1.11>
</Thru1.11>
<Thru1.12>
</Thru1.12>
<Thru1.21>
</Thru1.21>
<Thru1.22>
</Thru1.22>
<Load2.L>
</Load2.L>
<Load2.R>
</Load2.R>
<Load3.L>
</Load3.L>
<Load3.R>
</Load3.R>
<Thru2.11>
</Thru2.11>
<Thru2.12>
</Thru2.12>
<Thru2.21>
</Thru2.21>
<Thru2.22>
</Thru2.22>
<Thru3.11>
</Thru3.11>
<Thru3.12>
</Thru3.12>
<Thru3.21>
</Thru3.21>
<Thru3.22>
</Thru3.22>
<Thru4.11>
</Thru4.11>
<Thru4.12>
</Thru4.12>
<Thru4.21>
</Thru4.21>
<Thru4.22>
</Thru4.22>
</Autocal.Characterization>
 

Offline jjoonathanTopic starter

  • Frequent Contributor
  • **
  • Posts: 836
  • Country: us
Re: Anritsu AutoCalData
« Reply #2 on: July 16, 2022, 12:18:38 am »
Yes, I did open up and read my ACD file. That's how I wrote the python library that reads ACD files. Yes, the tool probably works on many other ACD files out of the box. No, it does not work on all of the models out of the box. No, it is not obvious how to make it work with all models without actual examples, and further examples would still be useful even if it was. In particular,

  • How do the "L" and "R" suffixes generalize to four ports? I can imagine several plausible approaches.
  • Do the Lightning autocals have the same format as the TopShelf autocals?
  • What is a typical list of characterization frequencies for different models? Someone with an autocal but no ACD would have use for this.
  • What are typical S parameters for different models? Someone with an autocal but no ACD would have use for this.
  • Did I accidentally make my parser too specific?

It's easy to speculate on all of the above, but not interesting or useful. That's why I want samples  :)
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf