开云体育

I ahve a set of them. They are high quality PL259 plug to SMA with good quality SMA OSL. The OSL tested on Agilent 8357C PNA were good past 3ghz but not to 6. The PL adapted loads of course start to

Hi Keen Thank you I did update the H4 and used is for a couple of hours. It look good. Only in rare cases there is small straylines, e.g. just one yellow one, and it disappear very quickly. So to

Herb, Well, my calibration? tryal was @ 1010 points ( 10 segs) , frequency range 1MHz to 50 MHz, CH0 only, on a Windows 10 PC. Regards, Jos Op 20-2-2020 om 18:51 schreef hwalker:

OK, progress... sort of. but not yet quite working. The new OTG cable installed. Result is it shows a connection available but the web app then displays ERROR: Failed to claim interface

Referring to the OP reference, they look a lot like N male to to SMA female adapters with a male SMA O/S/L screwed onto them. So you can as well buy one N male to SMA female adapter for 3$ on eBay --

#107': On the Missing Terms in NanoVNA firmware - ERRATUM Dear Erik, Thank you very much indeed for your valuable comment, since you forced us to recheck the related code. No, we can not explain that,

A direct link https://www.sdr-kits.net/Female-12%20GHz-Kit

Does this flash cure the problem of momentary markers loading behind programmed ones..and does this cure the nasty problem of the CH Z disappearing and needing to be reawakened to get a display of "Z"

Thank you Stefano!? I will try that tonight. 73 Glen K4KV

Hi Glen, IMHO it is only a problem of resetting charts. As you have a frequency range problem: 1) Point the mouse cursor on the chart that show the wrong behaviuor. 2) right click to show the chart

Another good source for Precision with full specification are Rosenberger (German) sold by www.sdr-kits.net

Ken, I upgraded to version 1.3 and have been running various tests for about an hour without noticing any persistent stray display artifacts. Thanks for the release and I'll let you know if I

I also flashed the new firmware version 1.3 into my NanoVNA-H4 and performed a 404 pts, 50k - 1 GHz calibration using NanoVNA-Saver to see if I could duplicate Jos' report. My calibration using the

Can you explain why they are needed given the current content of eterm_calc_er? -- NanoVNA Wiki: /g/nanovna-users/wiki/home NanoVNA Files: /g/nanovna-users/files

Hello? Ken and Rune, I flashed the new firmware version 1.3? of today into my NanoVNA-H4 and tried to calibrate the device in NanoVNA-Saver; Sorry I have to say that 4 times in a row NanoVNA-Saver

My timing was impeccable - I ordered via PayPal/email just before the start of Chinese New Year. As soon as that ended, the Corona virus threw everything in a state of confusion. I exchanged a few

I was working only on the PC.? I saw in the pdf document where they seemed to change the sweep range to a sub-set of the main calibration range, and the graphic areas also changed to the new sweep

#107 : On the Missing Terms in NanoVNA firmware Hello, Allow us, please, to propose the following modifications remarked by "//" :

Did you change the sweep on the nano or using NanoVNA-saver. I think you need to do the latter.

Kurt and Herb, I fixed the stray display artifacts left by moving markers. Please give a try and let me know if there is still any issue. https://github.com/AA6KL/NanoVNA-H4/releases/tag/v1.3 Ken