开云体育

Yes, you are missing the "back" button on the menu

??? I don't think so. My keyboard display on the H4 looks just like his
photo. The back-arrow or return key dismiss the keyboard if no entry is
made. This may have changed depending on the firmware version you are
using.
Stan

Hello,
Yes, you are missing the "back" button on the menu.
You did not say which "certain occasions" it happens on. You need to state that also.
But definitely there is a problem. I could not repeat your problem in any conditions I tried.
I would try reloading the FW to see if something went wrong with it.
Clyde KC7BJE

Stan, here's Rudy's answer to your question:

"Yes, I always reset before a new calibration and then check afterwards with Smith Chart OSL."

Brian

The "scale/div" menu item does not use those other range keys on the
keyboard, like some other items do (at least for the traces with dB values
and phase angles, I didn't try all trace types).

On 2/7/23 5:20 AM, Lawrance A. Schneider wrote:

On Mon, Feb 6, 2023 at 12:37 PM, Jim Lux wrote:

Elsie from Tonne Software

Is there a 64 bit version?
Thanks, larry

i don't think so, but it runs fine on my Win 10 64 bit machine.
It also runs in parallels on Mac OSX, Win 10 64 bit R85

On 2/7/23 3:40 AM, PDXer wrote:

Set it to LOGMAG.
Freq. range was 1 - 100 Mhz.

That's more like it, although it sure doesn't look like a *30 MHz* LPF. More like 10 MHz. You might zoom in on 1-21 MHz.

OTOH those ceramic filters are not necessarily 50 ohms in and out,

Try the BPF.

On 2/7/23 1:41 AM, PDXer wrote:

I can tell it was wrong setting. It is showing resistance?
I should have set it for LOGMAG?
Will try again later.

Definitely Log mag is what you want.

On 2/7/23 1:37 AM, PDXer wrote:

This is what I got.

Well, it sure looks like a low pass filter - the cutoff looks a bit high for a filter described as a 30 MHz Low Pass. I'd set the span to something like 0.1 to 100.1 (that makes the divisions on the screen an even 10 MHz), so you can see well below the cutoff.

What's the vertical scale set to? 10dB/div?

I'd take a look with the reference level (top line of display) set to 0 dB, and something like 2 dB/div 5 dB/div, so you can see the "top of the passband". Depending on the filter, there may be some ripples, or, alternately it will be the passband loss, and then gradually rolling ddown.

On Mon, Feb 6, 2023 at 12:37 PM, Jim Lux wrote:

Elsie from Tonne Software

Is there a 64 bit version?

Thanks, larry

Not an issue - you pressed the Scale button and you need to enter a new scale reference then click ENT
Press the <- key to return to the main display.

It's normal for the keyboard to cover part of the menu on the 2.8 inch unit - this has been discussed many times in the past 3 years of this forum.

Enjoy your nanoVNA

Set it to LOGMAG.
Freq. range was 1 - 100 Mhz.

I can tell it was wrong setting. It is showing resistance?
I should have set it for LOGMAG?
Will try again later.

This is what I got.

The menu display containing k M G is cut off.
It happens in certain occasions, not all the time.
Is this faulty? Or is it because something else?

Sorry to ask, but is he resetting the calibration each time before
calibrating? Missing that requirement was my problem last time I had a
similar issue.

I put less emphasis on the 25-ohm measurement after calibrating with 50 ohms because then the load accuracy matters. I think he used a pair of highly accurate HP loads, but who knows the exact values. Also disconnecting the cal load and connecting the test load invites SMA issues. That's why the original data I presented impressed me so. Cal with xxx, then read xxx without disconnecting anything. Results should be flat to within the data and algorithm resolution. I wonder if the divide by 16 you noted in your uncertainty analysis is coming into play.

Brian

On Mon, Feb 6, 2023 at 03:45 PM, Jim Lux wrote:

It would be interesting to see what he gets if he calibrates with 50 ohms and
measures 25. Is there the same frequency dependent variation?

Here it is. Same resistance offset (looks like same percentage, too). The reactance slope now extends throughout the frequency span.

Brian

On 2/6/23 2:45 PM, Brian Beezley wrote:

On Mon, Feb 6, 2023 at 02:38 PM, Jim Lux wrote:

Or are you calibrating with the load, and then remeasuring it and getting a
different answer?

Yes. N6LF calibrated with a 25-ohm load and then immediately measured it. That's why I don't understand the result. The resistance offset looks like a numerical bias issue. I don't know what to make of the LF reactance rise.
Brian

That is weird. The reflection coefficient (raw) is going to be (50-25)/(50+25) or 0.333 That's not getting anywhere near the noise floor.

It would be interesting to see what he gets if he calibrates with 50 ohms and measures 25. Is there the same frequency dependent variation?

On Mon, Feb 6, 2023 at 02:38 PM, Jim Lux wrote:

Or are you calibrating with the load, and then remeasuring it and getting a
different answer?

Yes. N6LF calibrated with a 25-ohm load and then immediately measured it. That's why I don't understand the result. The resistance offset looks like a numerical bias issue. I don't know what to make of the LF reactance rise.

Brian

On 2/6/23 2:15 PM, Brian Beezley wrote:

Thanks, Jim. I'll read the analysis.
I didn't realize the ADC was 16 bits. That's a lot. Now I feel even less forgiving about the observed performance.

The actual limitation is the SNR into the detectors. That's driven more by circuit noise within the 5 kHz measurement bandwidth.

In round numbers, each measurement is about 50-60 dB SNR. 60 dB SNR is 0.1% uncertainty.

But the calibration combines multiple measurements (O,S,L), so the uncertainty of the result is bigger. That is, if you combine two 0.1% measurements, the result is 0.2% uncertainty (or, alternately 0.14% if your RSS)

The cal actually combines more than that.

I don't understand why the possible imperfections in the load you postulate matter. Shouldn't calibration nullify them?

You were measuring something you expected to be perfectly flat. But is it flat to 0.02%?

Or are you calibrating with the load, and then remeasuring it and getting a different answer?