开云体育

Hi George, thanks for the credit! I made several known "Miss-matches" like from 0.1:1 till 10:1. If you use 0805 smd components they work fine up to several GHz. Yes, maybe the Chinese friends jump on

the id in Erik's firmware is 0483:0000, so you can convert it, or try to pgm with -d 0483:0000, or take the attached version

FWIW there is no reason to truncate the time domain transform except for lack of memory. A routine means of resampling data is to transform to frequency, pad the high frequencies with zeros and

Hello erik, Thank you for the firmware extension. I have tried to flash your firmware under MacOS: $ dfu-util -v -d 0483:df11 --alt 0 -D NanoVNA_with_scan-and_1500MHz.dfu But I got the

Nice work Norbert, Wouldn't it be great if someone made up a bunch of these objects and offered for them sale, possibly on ebay. They could be offered with various resistor values from 5 ohm to 500

Well, I had intended to post something, but on using a better 50-ohm load, and revisiting the calibration procedure a number of times, I now have short-open-load displaying at their expected positions

I'm beginning to think that my expectations are incorrect! I'll start a new thread about that, but in the meantime here are three screenshots showing the transmitted power through my 1-3000 MHz

just in case someone wish to play with it, when you set first "Center" frequency to 1 (and click on x1) and then "stop" to e.g. 100k, you will get 1Hz to 100kHz range displayed.

Hi all, thank you for all support on this Wiki and group. The documents made it easy for me getting started with calibration and basic use of the great little NanoVNA. 73, regards Lars SM0TGU

From: qrp.ddc@... here is my bridge with fix. ===================================== Oh, thanks for that. Mine was a boxed unit, and I made some DC resistance measurements: Resistances, all

Hi Dave, I've certainly seen the problem in cases where the screen did not turn white, and the device worked fine moments later. So I'm not entirely convinced it's the same issue? In any case,

David, Your nanovna not changing frequency is much more likely to be the stability issue I've described here:/g/nanovna-users/message/2379 You could see if you can reproduce the

here is my bridge with fix.

Yes, I've heard someone else mention that. I can't quite think what causes it, *assuming* the firmware didn't change the format of the commands used. I currently just have the one NanoVNA, and as I

Hi David, I have seen situations where the NanoVNA had not changed frequency after being asked to do so in the about 500ms I've arbitrarily decided to give it. In this case, it would repeat the data

SO-239 connectors have terrible SWR about 1.2. If you don't use more than 100W power, it's better to use SMA. For more power it's better to use N connectors

Yes, I've heard someone else mention that. I can't quite think what causes it, *assuming* the firmware didn't change the format of the commands used. I currently just have the one NanoVNA, and as I

From: Rune Broberg It's Friday, and that apparently means NanoVNA-Saver 0.0.9: https://github.com/mihtjel/nanovna-saver/releases/tag/v0.0.9 ======================= Rune, Trying with the new

Hi David, I have seen situations where the NanoVNA had not changed frequency after being asked to do so in the about 500ms I've arbitrarily decided to give it. In this case, it would repeat the data

From: DMR RFpro, Firmware 10KHz-1500MHz. By default, when turned on, 50KHz-900MHz. Expand the boundaries in the frequency setting menu. Added dfu menu item, now it is not necessary to close the