Hi Harry,
it certainly needs both error handling, and documentation! ;-) It was
getting late and I wanted it released.
The calibration buttons require you to run a sweep of the standard in
question first - not just connect it - before clicking it. I'm not sure if
you did this? Otherwise, this would certainly lead to the division by zero
error, as each standard would be seen as the same.
The sweeps for the 3 standards need to be the same length, and across the
same frequency span. Full span of the NanoVNA is probably most useful, and
10+ sweep count (to get 1000+ data points) is probably good. For detailed
work you can of course recalibrate at the span you intend to use the device
for a specific measurement.
The two-port measurements - through and isolation - are not available yet,
as I'm not entirely certain on the calculations needed. If someone's really
into this, and knows how to do 1.5 port calibration in a way that can be
explained to a numpty like me - please let me know! :D
I hope these quick notes lead you to more success with the calibration
function.
--
Rune / 5Q5R
toggle quoted message
Show quoted text
On Wed, 4 Sep 2019 at 05:21, Harry McGavran Jr <w5pny@...> wrote:
Hi Rune --
Well, I ran pdb to look at a few things in Calibration.py --
gm1, gm2, and gm3 all come up with the same values, hence denominator is 0.
I didn't have time to see why s11short, s11open and s11load led to that
though.
I only looked at the first interation through that loop.
Maybe this will help give you a head start on the problem...
73 --
Harry
