开云体育

you initially waved around a complaint which might as well be a
surrealist's dream: your HT will be un-burnt when you fill your bathtub
with brightly colored screwdrivers. and now you make rude demands? consider
yourself lucky the group may respond kindly to you.

back to the matters at hand: a technique for measuring output impedance of
an audio amp may not at all be used with the Ailunce HT for the simple fact
the audio amplifier will happily operate open circuit, while the HT may be
very unhappy indeed and release all the magic smoke from its power
amplifier.

except for the aforementioned magic smoke release warning, the simple and
direct method of measuring output impedance (or "source impedance") is to
compare the open circuit operating voltage with operating voltage under
load.

the load value will be equal to the source value when the operating
voltage under load is one-half of the open circuit operating voltage.

- 1001001 (base 2) -

Hi Rune,

I have downloaded your release 0.0.5 and am checking it out. Some
comments:

1. At first I thought the Mouse Cursor was broken -- I was clicking in
the S11 Smith Chart plot and I wasn't seeing its marker. Then I discovered
accidentally that its marker would appear if I instead clicked in the S11
Return Loss plot. Any chance to get this marker to appear no matter which
plot we first click our mouse in?

2. Also, in the version I downloaded this morning from the master (not
release) folder (a version without the verbose Mouse cursor and dots for
Markers in lieu of triangles), I could move the mouse cursor in the S11
Smith Chart plot. I cannot do this now -- I have to go to the S11 Return
Loss plot to move it.

3. Reference Plot color -- works fine, but I notice that the color
displayed in the "color button" is a very grayed-out version of the color I
select. Not sure why it's grayed-out, as the color of the actual reference
plot is fine.

4. The only way I seem to be able to get Markers 1 and 2 to appear on the
screen is if I first type a frequency into their boxes, and then the
markers appear (which might be your intention). But I know that the
frequency I type isn't the actual frequency that the marker is pointing to
(which I can read by ovelaying the mouse cursor on top of either Marker 1
or 2). For example, for Marker 2 I had typed in 500000000 (i.e. 500 MHz).
But the actual frequency of the sample is 506.936 MHz. Would be nice if
the displayed frequency were the actual frequency.

5. Being able to transfer the mouse cursor's frequency into either Marker
1 or Marker 2 would be a nice feature.

6. Would be nice to step the mouse cursor (and/or the markers) with the
keyboard arrow keys for "fine tuning".

7. Heartily agree with adding averaging.

8. A word of caution regarding adding C0 (and C1, C2, C3) for the open
calibration standard. As has been mentioned in other threads, there might
be a 50 femtofarad value already hard-coded into the NanoVNA software as
C0. Adding an external C0 parameter, without being able to zero out the
existing C0, will defeat the purpose of adding the new C0 value. (If this
is an issue, I would suggest contacting Hugen -- he might be able to
confirm the existance of this hard-coded value. If it an existing
compensation already exists, there might be some way to cancel out its
effect -- maybe by adding to it a negative (!!!) 50 femtofarad value?).

9. It would be nice if the release version appeared someplace in the app.

And finally...excellent job!

- Jeff, k6jca

I too have tried to execute the .exe file from the .zip window, I am
running Windows 10 64bit version and get a dialog box that I say to run
anyway, but only get a brief "flash" window on my screen and then it
disappears with no trace. I have not installed python etc. but I don't
think I need anything else to run the .exe file. Any idea what is
happening? Bob

A frequency extension up to 1500 MHz has been presented in the russion
forum:




I have installed it but did not yet check it.

A lot of very informative details can be found at the posts of XENOMORPH.

"rotating locking collar"?

Is that as opposed to a "rotating only" collar?

Den tors 5 sep. 2019 07:50Wayne <wb6bfn@...> skrev:

Some calibration standards do not have a rotating locking collar. In
that case there is no way to avoid rotating the center pin unless you
use those very short male-female SMA adapters sometimes called
"connector savers". The best way is to buy a set of calibration
standards that actually have rotating locking collars.

Wayne Maynard WB6BFN

On 9/4/2019 10:47 PM, Hans J Albertsson wrote:

Try as I might, I cannot keep the pin+back assembly still while

screwing

the short and/or load calibration piece down in the SMA socket!

Should I add some grip to their backs, with glue or solder? Should

I

file out a slit for a screwdriver?

Or just give up?

Some calibration standards do not have a rotating locking collar. In
that case there is no way to avoid rotating the center pin unless you
use those very short male-female SMA adapters sometimes called
"connector savers". The best way is to buy a set of calibration
standards that actually have rotating locking collars.

Wayne Maynard WB6BFN

On 9/4/2019 10:47 PM, Hans J Albertsson wrote:

Try as I might, I cannot keep the pin+back assembly still while screwing

the short and/or load calibration piece down in the SMA socket!

Should I add some grip to their backs, with glue or solder? Should I

file out a slit for a screwdriver?

Or just give up?

Try as I might, I cannot keep the pin+back assembly still while screwing the short and/or load calibration piece down in the SMA socket!

Should I add some grip to their backs, with glue or solder? Should I file out a slit for a screwdriver?

Or just give up?

I think many of us would really like having built-in TDR functionality for simple antenna & feedline testing. Considering how inexpensive the nanoVNA is I, for one, would not mind having one with the current VNA capability and one with SWR (or return loss) and TDR. Is that a coding possibility?

?Wayne Maynard <wb6bfn@...>