开云体育

Bob, One other thing to try before you start looking at the hardware. The first NanoVNA I bought came pre-calibrated and was ready to go out of the box. A second cheaper NanoVNA that I bought came

Any time you push new F/W to the device it is good practice to re-cal the touchscreen. Now, with that said, I just updated one of my units and found the touch surface was still calibrated. So - if you

Hmm. Can newly installed firmware detect that it has never been touch screen calibrated and automatically start in TOUCH CAL the first time?

Good day, When I began this process of working with the NanoVNA, I was not certain how the cal standards were being treated. Since the completed cal showed a perfect open, short and termination, I was

Larry, thanks for the encouraging information.? Where do I get the schematics?? What could be wrong with the bridge?? Where do I find it?? Pictures would help. I don't have much to lose at this

Bob, It sounds like the bridge circuit on CH0 is bad and the nano is not seeing any reflected energy to measure.Don't throw it away, just do a little troubleshooting - the schematics are

Rune, forgive me if you aren't the guy to whom I should ask this. I purchased a nanoVNA recently and it isn't working as I think it should.? Regardless of terminations I always get a dot at the right

Hi Mike- Exactly, IMO "calibration" should reflect actual measurement configuration More specifically, SHORT was by clamping alligators together and OPEN was by unclamping them. I want nanoVNA "CAL"

On Mon, 29 Jul 2019 at 16:59, alan victor <avictor73@...> So at this point, create the best short, open and 50 ohm load... the Perhaps there is a transaction issue, but the source code I

RuneSorry for the alert? Win10 was trying to protect me from the download.I deleted? and then reloaded. This time it gave me a functional app.? Now all is well.I will test on thanks you so much for

26 : Correction of Maxima Version and "Unpacked" DERDEI Code - also @Jose Luu : /g/nanovna-users/message/3278 - Hello, Allow us, please, to inform you that, as we already promised at:

This was a little unclear to me, but interesting.? Are you saying that you used the 51 ohm resistor held by the jaws of the alligator clips for calibration?? Then the data you posted was for that

Hi Bryan, I'm aware of the issue. I don't know if it can be turned off via the serial console - thus far, my advice to users has been to not put the device in TDR mode when using it with

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