开云体育

Using the SMA-M/SMA-F adapters as connector savers like I think you show, Stan, is a very good idea. Even very high quality SMA connectors (>$50 each) degrade in match very quickly. Cheap ones with

Dr. Kirkby is right, as I can confirm from my own experience. Last year I wanted to do a RL measurement o find the losses of several lengths (up to 25 m) of leftover coaxial cables on all amateur

Sounds like a perfect excuse to buy a 3D printer! 73 Ed N5KZW

Thanks for all the suggestions!

No it look like hardware problem (or measure frequency problem) It possible fix by software need redefine To current XTAL frequency and rebuild Or replace XTAL

DiSlord suggested the error could be due to the firmware. What version are you running? Roger

Interesting way to measure balun loss with a single balun and a VNA. Thank you for posting this information. Roger

Hi, Is it posible for add the big CH0 screen info in version 0.7.1-20200321 by edy555 ? Tnx Andy - ON7BA

I just joined the nanoVNA group a couple of days ago and followed your thread on the balun measurement. If possible, why don’t you measure the scattering params, save the data, build a 3x3

Always perform a reset before setup and SOL. I have a piece of that DX400max 50ft long I do not see that oddity. That cable would have to be really poor to get that result. Several possible things,

As the TCXO frequency is out of tolerances, it's certainly a defect component. As i wrote, i ordered the Nanovna-H at "Wish". I've read, but too late, that this was not the best solution... The

DR Kirkby, That would be a corner case and a very very long cable. Typical cables used ran maybe as long as 100M, so we haven't reached a radar mile yet. Usually we have no reason to make sudden

Try update firmware to my last version and check /g/nanovna-users/files/Dislord%27s%20Nanovna%20-H%20Firmware As i remember old Hugen (and edy555 < 0.6) firmware not fully correct

The NanoVNA-H we produced should not have such a large deviation. Can we provide PCB pictures and test pictures? If it is the version we made, we can provide a new one for free.

With a loop, i was able to measure the TCXO frequency and found 25.997748 MHz instead of 26MHz ! This error correspond to ~ -86ppm, not too far of the output error of -85.5 ppm at 100MHz CW ! As i'm

Thanks for sharing will look into it !

Please read the forum WIKI and notes in the forum FILES sections. You need to install the latest version of firmware for the model of Nano you purchased.

I just got my Nanovna-Hv3.4 from amazon seesii. I was ready to return it because the back states frequency:50k-300MHz. I am looking for the 10KHz starting frequency. Now I see your expert review.

Just by curiosity, i entered a CW value of 100.0086 Mhz and i measured 100.00002 MHz. It should be a solution with Si5351 programmation but, after reading a lot of related information, i don't find a

REF: /g/nanovna-users/message/13681 Hello, again. Well, after the Special Interest shown here, we would like to inform you that, in direct contrast with what Gary O'Neil, N3GO