开云体育

I was also wandering why the SWR scale says 250m. FW version 1.2.14.

Help. Newly purchased Nano VNA H4 March 2, 2023. I've read several posts on the H4 model about firmware and each mention identifying the proper version and the URL that is listed. Mine does not have a

Regarding noisy plots, I have used NanoVNA-App on both Raspberry Pi and Windows laptop. The RPi gave noticeably more noise but it was reduced in both cases with a ferrite clamp on the USB cable close

This was a comparison of how well each one calibrated the same cable and measured a 1K DUT. A new calibration using the same cal loads was done at the end of the 3M cable for each test and then they

if you calibrate the cable out then all should show near similar results .. not?? measure without cable calibration can not work good so question is ... did you calibrate out that 3m cable?? if

Follow-up to last post. Here are some more measurements of a 1K SMD DUT. Using NanoVNA -H4 (1.2.19 fw) in standalone mode (no PC) and comparing it to NanoVNA Saver and OD NanoVNA app. Measurements

Thanks for the reply and information. I did recalibrate and saved them to SD. But the RECALL FROM SD menu item isn't there in 1.2.14. I rolled back to 1.2.0 for now. Regards

I agree that you should calibrate for the measured range and that interpolation must be used carefully. Here are two examples where I calibrate over 50k to 900 MHz and want to measure some 0805 SMD

Hi david I am not at home right now so not near my laptop but this might help?

I agree. A tiny bias above 1 along with noise. I plotted it just to compare with the earlier NanoVNA-App plot. Brian

@Brian - It may be relevant. Comparison of Open in calibrated NanoVNA-App and calibrated NanoVNA-Saver. In Saver it looks better, oscillating around 1 and in NanoVNA-App it is > 1 for all points.

It's not due to noise. The data is noisy, but the real part is > 1 for all points. I have seen this in other VNAs. I don't think it's pertinent to your calibration issue. Brian

It looks like it is conflicting with another port. Below is what I am seeing on my laptop: [image: image.png] [image: image.png] It appears that it is trying to conflict with Port 3. What is the best

@DiSlord - But that's exactly right. The measurement range is identical to the calibration range, the number of points is also the same, the calibration frequencies are equal to the measurement

This is how my (bought in 2023) H4_MS Model looks Note the _MS at the end of the HW Version And yes ... You can change the setting in the GUI too , if you have loaded the wrong one. Just remember to

Thank you all for the valuable information. The NanoVna works with the new firmware without any problems. 73 Zdenek

Remember state - allow save some device settings after power off like: Start/stop frequency Bandwidth Backlight Options Threshold - this option set frequency threshold after this device use harmonic

Hi there, I’m running Hugen’s 1.2.14 firmware, which I like because it lets you save more calibrations. It will also do more data points across the sweep. But I lost some of the defaults along the

Calibrate device in measured range. Interpolation not give good results for long cables (on big phase change for measured points)

Hello Roger, Just an observation, The green App curves have a distinct spike at the 5351 clock gen harmonic change points; ~300MHz, ~600MHz, 900Mhz. Cheers...Bob VK2ZRE