开云体育

Chinese fonts take up more room. BTW - hugen has released the TWO TRACE 'AA' version of the latest firmware, located on the Google Drive below. There are both 800MHZ and 900MHz versions. Regards,

On the Google drive here - https://drive.google.com/drive/folders/1IRz6E1wlkRyV0u7sbqj0lhWST-GV1szY The firmware is now in folders (I do not think this was the case last week when I got the 900

Hi Rune, thanks for the hint! I tried it out right away and it works very well! I have attached the plot of a 200MHz BP-Filter. The calibration is done with full span and 8 segments. Now I can figure

28 : DERDEI : Use of Standalone [gnuplot] Instead of [maxima] Hello, Allow us, please, to confirm the interested Common User, who already observed that is indeed redundant in this case, since the use

I agree; with decent screen calibration and an old Samsung Galaxy Note stylus, I find device menus faster and easier than any VNA software UI, so use software mostly for data capture or TDR.

Probably not long. I am sure there are much more robust connection options available but <$30 for a set of possible uses doesn't exactly seem that expensive (you could make your own of course) but I

Hi Jim - I will try! Yes. Exactly, but I am not about to build a pcb with BNC connectors for each component to measure, and it is IMO not necessary for use below 150 MHz. Not really, but did not

Thanks for the segment suggestion Rune and those off line too, I don't think it was the segment issue. It seems the callibration data had somehow been borked and nothing was correct, once did the 'cal

Hi Norbert, For calibration within NanoVNA-Saver, setup the sweep first to be the span you want calibrated - for example, 50k to 1500M. Then in the box labeled "segments", enter how many segments (of

Hi Rune, thank you very much for your quick answer! Please tell me the trick where I can change the number of points prior to calibration. I didn't find that yet. I think the following measurements

Hi Norbert, the application can run calibrations at far more than 401 points - I have certainly done 5050 points at one point. ;-) But it does this in the application, and not on the device, due to

Hi Rune, thank you for fixing this issue! I have a question for you in respect to the required number of data points to measure a band pass filter. With 101 points it is most likely not possible to

Thanks Rune, I'll try both options. BTW this is running Linux & Python 3.74 version at home, work is much earlier so will have to wait I guess until later. I get the same output with the previous

Glad you got yours. Obviously I'm not worthy. I have got one now from elsewhere on eBay. And when my sma to n adapters come I may even use it!

Nice idea. I wonder how long those little u.fl connectors will last though.

27 : Reproduction of (REGION , DEREDEI) Results and Graphics @Jose Luu : /g/nanovna-users/message/3812 Hello Jose, Thank you very much for your proved interest on our work. Your

You tried sweep 50kHz span with 101*10 sweep. I don't think NanoVNA capable below 50Hz RBW... How about give more span with default 101 sweep?

Oh, a different issue: You set the segment count far, far too high (1000). Try a value of 1 first, and see if that helps :-) -- Rune / 5Q5R [email protected]> wrote:

Hi Dom, The application is receiving some weird data from you device - a value of about 2 billion, which is supposed to be in the range -1 to +1. ? Try doing a full calibration on the nanovna,

Of course Larry, you've been a great help thus far! :-) I'll be doing alpha testing for each new version from here on. -- Rune / 5Q5R