Hi Bryan,
I know it's the easy way out to claim that it's the other guy's fault, but
I really don't treat 0.3.0 any differently than I did 0.2.3. The fact that
it's at a specific frequency might point towards it being related to your
calibration at that particular frequency. I assume, though, that you have
tried re-calibrating your device, and that it remained in place at the same
frequency? Do you get any errors in the console log? Have you tried
running it with '-d' command line option to see the debugging output, and
whether that gives you something? (though it probably won't.)
If you save a Touchstone S1P or S2P file, you can cut out the frequencies
around where the fault occurs, and maybe put those in this thread - it
would be interesting to see the numerical values of the fault, at least for
me. :-)
--
Rune / 5Q5R
On Mon, 21 Oct 2019 at 20:19, bryburns via Groups.Io <bryburns=
[email protected]> wrote:
On Sun, Oct 20, 2019 at 11:03 PM, <bryburns@...> wrote:
I am seeing a lot more data errors with this version of firmware than I
saw
with 0.2.3 from edy555
Rune,
I have a little more information on the data error issues when
nanoVNA-Saver 0.1.3 interfaces to the edy555 - 0.3.0 firmware.
I get a consistent error when running 3 scans from 50 kHz to 900 MHz. The
device connected to the nanoVNA was the "through" I used for calibration of
both the nanoVNA and nanoVNA-Saver 0.1.3. The first sample of the 3rd scan
is often, but not always, in error in the S11 data. The frequency in the
s2p file is 602003132 Hz. It seems to happen 2 or 3 times in 5 scans. I
setup nanoVNA-Saver to run continuously and put a marker on that frequency
and can see the errors are exactly the same frequency. Sometimes 2
consecutive scans will have errors. Often, the S11 data will show a 5-10
dB error. When the S11 data is in error at this frequency, S21 in (dB and
degrees) will also show a relatively small error compared to adjacent
samples. With these settings, I don't see any other obvious errors in the
S11 data or the S21 data. So, this particular issues seems tightly
correlated to scanning in nanoVNA-Saver and the 0.3.0 firmware. Again,
this doesn't happen with 0.2.3 firmware.
I hope this helps with figuring out the cause of some of the data errors.
--
Bryan, WA5VAH
