Herb,
After thinking having solved the previous problem with NanoVNA-H4 calibration I went on playing. :-D I did a 2port calibration 1MHz- 30MHz in NanoVNA-Saver with the '"S11 Phase"? chart shown and experienced the same problem as with the " S21 gain"? calibration , before calibration a decent display, after calibration no correction on it but all garbadge on the screen, see the picture before calibration attached. I did the measurement on the 50 Ohms standard I had used. Not that I was interested in the phase, but it shoiuld work correctly.
I think Oristo is right, about the communication from NanoVNA-Saver and the device.
Jos
Op 26-1-2020 om 01:24 schreef hwalker:
toggle quoted message
Show quoted text
On Sat, Jan 25, 2020 at 03:58 PM, Jos Stevens wrote:
I did what you suggested , removed the portsavers re-calibrated the standalone VNA,the result was better then before 0.00 db, +0.12 and -0.25 at 50k, 750M and 1500M. Then I calibrated in Nanovna-Saver using 4 segs like you, Before was better, and After was an ideal straight line at 0 dB!
==============================================================================
Good job Jos. I initially had problems with Rune's calibration module but after he posted that you needed to start the module from a good calibration on the NanoVNA saved to "SAVE 0" it has always worked well for me. I still use the ideal models because I hate entering numbers that I don't fully understand.
Rune's NanoVNA-saver application has been working great with the NanoVNA-H4 thus far. The screen saver doesn't work because different code is required for the 4" display, and NanoVNA-saver reports the unit as a NanoVNA-H which may mean the hugen will need to change the -H4 identifier in firmware to help developers differentiate it.
- Herb
