开云体育

Hi Bruce and hwalker Please visit www.reeve.com and read the next report where I tuned in and contributed. The linked article are the first step to better methods ? Kind regards Kurt

Hi, I have tested a lot of firmware version, and never one of them has allowed a frequency step below 100Hz. Are you sure of your previous test ? To have a firmware allowing a more precise frequency

Hi qrp.ddc The way you wrote "by connecting Ch0 with Ch1" it was obvious the you missed the end of cable calibration ? Always remember a test cable is part of the instrument as you are forced to

Thanks all for the replies with detailed information, and also the links, which provide a treasure of information. It looks like the nanoVNA will be extremely helpful in looking at the snap-on ferrite

Hello Reg, I brought up this question of uncertainty in measurements several posts ago. Although the calculation is not complicated, obtaining the parameters to find the uncertainty boundaries is a

On Mon, Sep 23, 2019 at 12:07 PM, Rune Broberg wrote: > > Maurizio, > thank you very much! I see the use for separate segments, certainly, but > with the current architecture of the code, it's not

Maurizio, thank you very much! I see the use for separate segments, certainly, but with the current architecture of the code, it's not easily achievable. Many, many parts of the code assume uniform

Hi Tom, [image: image.png] Coming in the next release. Pushed to GitHub in a few minutes as development code. -- Rune

nice trick, but it will works until power off...

Bruce, You could calibrate the device, make the measurement of interest, go to "Stimulus", press "Pause Sweep", and the data is saved in the nanovna. The device under test can be removed and the data

there is no memory on the board to store results.

Just tested, with previous firmware version (nanoVNA_900_ch_20190802.dfu) it works ok with 5 kHz span. I tried even 10 Hz span and it works ok. But the new firmware version

I am finally understanding the concept of calibrations and saving the settings/range in the nanoVNA. But I am wondering if there is any way to save results from out in the field and then

How does one calculate the uncertainties of an out of calibration VNA and calibration kit bought on ebay? In an ideal world everyone would do as you ask. But the nanoVNA has made it possible for

I've seen at least one firmware version where the minimum attainable step size was 100Hz. I don't exactly know why, but your findings fit my observations as well. -- Rune

I catch some strange bug in the latest firmware. I tried to get better resolution around 26.996500 MHz to see crystal resonance. Span 10 kHz works ok. But when I trying to setup span=9 kHz or 5 kHz or

I tried the S21 method. Connected the 2 center pins (CH0 and CH1) to the choke ends (coax shield on both ends). -20dB at the frequency of interest is a decent common mode attenuation. -30dB is good.

Yes, that's all you need. I ran a similar case with a single strand of #22 AWG with and without the addition of the lossy core material. Although very nice particularly for looking at common mode

Yes, I am familiar with the "other" PN systems. Thanks for the clarification. I assumed this was test set limited, however, just to be sure. Regards, Alan

A poor mans test jig for checking if these cheap chinese chokes do anything. Two SMA female chassis connectors with the ground pins soldered together and a short wire connecting the center pins. The