开云体育

Thanks for the info! Yes, I have calibrated in the App as well.

Thanks!! But I'm not sure what you mean by generator threshold. Is that the stop point in the calibration?

Only had this for a few days. I don't know how to do any of what you suggested. Connectors are tight. I didn't use cables with this calibration. I followed the guy in the video. I agree this does not

Here my generator: As can see my device allow work up to ? 306M, but i leave default 300M Your device can be near 290M (some device 280M)

Generator threshold value must be less then default 300M, need more detail see work in range 270 - 300M (reset calibration and see in this range) From there threshold start problem. After write it to

You have no trace information or markers displayed. See the orange box below to see what I mean. If you did a software update you might need to do a Clear Config to flush out the old settings. It is

I have a hunch it might be the harmonic mode that is having problems. Try calibrating from 50 kHz. to 200 MHz and see if it improves. Roger

try to do your sweeps with some averaging (means more points/values per measure point are takern and interpolated) ... that make the curves more even you even can do the calib with high avg .. and

HA!! Didn't know I could do that!! Here at the pics. The green lines are moving. Thanks!!

why not use w10?? ... most if not all software for w7 should also work on w10 dg9bfc sigi Am 30.08.2022 um 19:39 schrieb Leif M:

You can take screenshots using nanoVNA app by just connecting to your nanoVNA and clicking the camera button. Roger

I still use W7 because most of my software is there. Nano VNA software for W7 would be nice too.

Here are some screenshots of short, open and load after calibration. Post yours for comparison Roger

Right, the frequency range is a little wider than the range/points I want to check. Range is 460Mhz to 470Mhz and I want to check 462.550Mhz and 467.550Mhz. Thanks

Thanks!! I watched the video and did the calibration along with the guy. My menus are a little different than his. I don't have the choice of 'CORRECTION'. I think the equivalent on mine is 'Apply".

My first guess is that the frequency range used for calibration is different than the frequency range used for the measurement.

I suggest you use the nanoVNA in stand-alone mode (without a PC) in order to test it out. Do a calibration over a wide range like 50 kHz. to 900 MHz. and then check it using the cal loads and the

I know about several problems in 450-480MHz range. Try calibrate in 300-600MHz, but measure in 460-470MHz PS on screenshot i see you use NanoVNA-App calibration mode (so you calibrate in it?)

Actually I started with Slackware 1.0 but moved to RH 2.0. Been a long time ago, my memory may be off on the date.

Yes, I re-did the calibration on nanovna itself as well as in the App.