开云体育

Rune, Running firmware NanoVNA-H__900_ch_20190924.dfu from hugen with nanovna-saver.v0.1.0 This firmware has TDR mode built-in to the device. If the TDR Transform is enabled in the device, data sent

Hi Larry, you're right - the application still thinks at that point that the NanoVNA is connected - despite having just received an error that it was disconnected. It should probably just disconnect

I saw this https://www.ebay.com/itm/RF-Demo-Kit-NanoVNA-Tester-Board-Filter-Attenuator-for-NanoVNA-F-Vector-Network/174045219309 Thought might be of interest to some. 72 Dom M1KTA

LCR meter, OSL calibration and measurement for alligator clips, using axial lead 51 Ohm resistor LOAD 23 Ohms 7 uH @ 0.1 MHz 5.5 Ohms 6.6uH @ 1 MHz 40 Ohms 400mH @ 10-100MHz 57 Ohms 900pH @500-900MHz

Hi Rune,There is a small bug in the serial connect routine.If I disconnect the Nano while scanning, I get the pop-up error and that's OK.If I then click on the Rescan button, the selected serial port

On the AIM-4170D PC SW, the y=0 axis is also used for resistance and reactance on the same graph as SWR so here is what it usually looks like:

Hi Nick, this looks ... interesting. The Gtk error isn't something I have any control over - it seems to be your Window Manager (at a guess?) or local Qt implementation that's using Gtk for its

Here's the console output when when I hit the load cal button... nick@LM19-2:~$ python3.7 ./nanovna-saver/nanovna-saver.py NanoVNASaver 0.1.0 Copyright (C) 2019 Rune B. Broberg This program comes with

Hi Bryan, thanks for the feedback! The code used is the same for S11 and S21 charts of the same type, such as the return loss/gain charts - so the errors end up being the same ;-) Thanks for checking

Hello Brian, thanks for trying out the software! :-) I do not read from or save to the NanoVNA calibration locations. Currently, my recommendation is that users calibrate the NanoVNA across the full

That's actually a good point.? However, the AD4350 only goes down to 137 MHz.? So unless they have done something creative to extend that range down lower, you will need BOTH V1 and V2 if you want

Rune, Thanks for the new release. Keep up the great work. I see the same issue with S11 return loss in dB. I do not see it in the phase plots. -- Bryan, WA5VAH

Hi Norbert, thanks for the bug report! I can tell you that the data points are drawn where they should be, but the reference lines are 10 pixels offset. Whoops! I've fixed it on GitHub, and the fix

Hi Bill, The .exe file should work just fine on Windows 10. First startup can take a little while, maybe 10-20 seconds, but after that it should run fine. What happens when you try to start it? --

These are nice little instruments !!Thanks for the update.

Larry Not very much actually. It was calibrated at the 100 MHz span and then I reduced the span to 50 MHz without recalibration in order to get better resolution. At these levels I am not concerned

Hi Rune, Thanks for your development efforts! I have a quick question about saving calibration data; can you read from / save to memory locations on the NanoVNA? 73, Brian WB8AM

Is there a trick to get the 0.1. version .exe to work.? I am on a win 10. machine. Is thisa linux .exe?? the other two version unload and install and work well w10 no.I tried to unload the zip file

Hi Kurt, Thank you, I look forward to your report. With regards, Bob

Hi Rune, thanks for the software update and for the additional features! One issue I recognized: S21 is with the previous version after calibration right on the 0 dB line and on the current version