Going from your picture, it looks like the calibration didn't "take". In
your picture of 50k-900M span, 50k-300M looks right, and the rest just
looks weird. So I would expect it to be that you need to do the full
calibration on the device itself again, including remembering to press
reset, and saving to slot 0. It *may* be an issue with the harmonic mode
used above 300MHz.
--
Rune / 5Q5R
toggle quoted message
Show quoted text
On Sun, 13 Oct 2019 at 13:49, KE8CPD <Josh.Mucinski@...> wrote:
Ok so the issue stemmed from trying to use it with Nano-saver, and got a
error (see below)(info: this is only two lines of what it spit out).
2019-10-13 08:38:17,772 - NanoVNASaver.SweepWorker - WARNING - Got a
non-float data value: 12.828430175 4.697909355 (12.828430175)
2019-10-13 08:38:17,972 - NanoVNASaver.SweepWorker - CRITICAL - Tried and
failed to read data 0 20 times. Giving up.
So after a quick google search i found that the correction needed to be
turned on. I turned it on and it did not help.
So the issue is that when the sweep is set to ago above 300 mhz the
readings do not make sense. On a 50 ohm load it should have one point on
the smith chart (red trace), and in the photo showing the span 50 khz to
900 mhz it clearly do not show the 50 ohm load as a dot on the smith chart
(red trace). But when I change the span to 50 khz to 300 mhz the smith
chart looks normal with a 50 ohm load.
This issue happened when i updated the firmware.
I flashed the hugen79 firmware (pull and built this morning) and still has
the same issue.
!*! Side note !*! : Does anyone know to revert to an old firmware.
Running Ubuntu, ive tried "git revert <hash>, then im not able to build.
