Trace sometimes starts with bad data #2
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
See in this plot how the S11 trace doesn't start until ~180MHz.

Note that frequency is the inner-most loop in this code.
Encountered with
vna_dev.py
in339dbe255e
.Since all of these are relative measurements, that means that the
a
measurement (incident signal) has at least one time sample exactly equal to zero.This output occasionally happens but only after a fresh "start". That doesn't mean power on reset but does mean a freshly initialized sdr. IDK if there's really anything I can do to make this not happen since I think it's happening in the Pluto but I can at least detect it and throw out data until it is good.
It appears that once I get good data it stays good indefinitely.
Details