开云体育

Please perform a touchscreen calibration, save, touchtest and cycle the power.?Does it lock-up?



On Fri, 4 Oct 2019 at 9:28 PM, Oristo<ormpoa@...> wrote: > Do not use hugen's Oct 2 'AA' firmware versions.

?They cause the nano to lock-up after touchscreen calibration.

Doh!!? I just installed NanoVNA-H__900_aa_20191003.dfu for hacking a new menu tree

Do not use hugen's Oct 2 'AA' firmware versions.
?They cause the nano to lock-up after touchscreen calibration.

Doh!! I just installed NanoVNA-H__900_aa_20191003.dfu for hacking a new menu tree

If you calibrate the touchscreen, it will lock-up at boot.?Please confirm.?



On Fri, 4 Oct 2019 at 7:59 PM, in3elx@...<in3elx@...> wrote: I installed the NanoVNA__800_aa_20191003 firmware. I think this is fine, it has improved to 300Mhz ...

I installed the NanoVNA__800_aa_20191003 firmware. I think this is fine, it has improved to 300Mhz ...

On Fri, 4 Oct 2019 at 19:58, Rune Broberg <mihtjel@...> wrote:

Hi David,
your suggestion of interfacing with the HP 8753 is certainly interesting! I
am going to have the code reworked at some point to accept more VNA types,
so an 8753 option isn't completely impossible.

Since I want to use my NanoVNA/P, I doubt that I will use your software for
now. But it had crossed my mind that perhaps look at modifying it later -
once your rapid development had slowed. ????

As of now, though, I have no

way I would be able to test it, and that's likely to block any progress
towards it for the foreseeable future. I wouldn't want to be releasing
software that I no way to verify was actually running.

Since you intend supporting others VNAs, if the code was commented well,
and structured in such a way to give others the chance to add code for
other VNAs, others could add support for an 8753.

If you ignored setting up an 8753 (start frequency, source power,
calibration, etc) but only read the data, it would probably be easy to test
with remote access via ssh to a linux machine with an 8753 on the GPIB bus.

I have remote access at night to a 67 GHz Agilent PNA-X, with tons of
options. That is nice to play with! I only wish I owned the hardware, which
I expect is a similar cost to my house - perhaps even more so.

I don’t know what information you get from the NanoVNA,

There might be someone local who has one, but barring that, I don't think
I'll work on it for now :-)

I think you have enough with the NanoVNA for now. I expect I get a
NanoVNA-F, as I want a larger screen. But I will wait for prices to fall,
as I am not in any hurry.

--
Rune / 5Q5R

On Fri, 4 Oct 2019 at 15:10, Dr. David Kirkby from Kirkby Microwave Ltd <
drkirkby@...> wrote:

On Fri, 4 Oct 2019 at 13:55, Rune Broberg <mihtjel@...> wrote:

If there are any miscalculations in my software, I do what I can to

correct

them. I have not recently been made aware of any problems, and at no

point

by Owen. I hope that any of you would immediately contact me, should

you

find errors in NanoVNA-Saver! :-)

I have not read the article by Owen, but I would agree on this single

point

about return loss. But I never commented to you, as it is a subject of

much

debate. If there was a very clear majorty for one convention or the

other,

I would stay you should go with it, but there's not a clear majority, so
use whatever you want.

If I was to use your software, which I might well do, but m interest is

in

portable use, without external software, I would probably recompile and
change the sign. My HP LCR meter allows one to display this R+jX think in
multiple formats. I could give them to you if you wanted, but again, you
know what space you have.

While I am sending you a message, there's something else I thought of

that

could be of use to many people, but you might not want to get involved

in,

so I did not bother. Your software could be useful to those of us with

the

very popular HP 8753 series VNA. It would be good if you could support
reading from them too. The Python code to open a GPIB code and read from

it

is about 5 lines long. Much of the other commands you use to set up a
NonVNA would have an equivalent in 8753.

--

Rune / 5Q5R

--
Dr David Kirkby Ph.D C.Eng MIET
Kirkby Microwave Ltd
Registered office: Stokes Hall Lodge, Burnham Rd, Althorne, CHELMSFORD,
Essex, CM3 6DT, United Kingdom.
Registered in England and Wales as company number 08914892

Tel 01621-680100 / +44 1621-680100

--

Dr. David Kirkby,
Kirkby Microwave Ltd,
drkirkby@...

Telephone 01621-680100./ +44 1621 680100

Registered in England & Wales, company number 08914892.
Registered office:
Stokes Hall Lodge, Burnham Rd, Althorne, Chelmsford, Essex, CM3 6DT, United
Kingdom

@in3elx
The latest build code is 10KHz-1.5GHz

If you're interested in learning the Python programming language so you can play with some of the open-source software development that is being done by various forum members, a free 660+ page reference book has been made available online in PDF format.


.

Enjoy!

Larry

Do not use hugen's Oct 2 'AA' firmware versions.?They cause the nano to lock-up after touchscreen calibration.?I have the 'CH' version installed and it is working so far
Remember to do full calibration after installing new firmware.?



On Fri, 4 Oct 2019 at 5:30 PM, in3elx@...<in3elx@...> wrote: Thanks for all these info, compliments.

This interests me:
"DMR_M_10KHz_sept-13-19.dfu
Such as these were for enhancements, in this case 10KHz instead of 50KHz minimum.
I >>guess<< many enhancements are in Gen Hu Oct 2 firmware"
- Should this be installed before or after the firmware?

- Which firmware can be used to set an impedance different than 50 Ohm?

Mike,Look at the schematic at the end of the July user guide.?The 5v output from the inverter powers the 612 mixers and also feeds an LDO 3v regulator that powers everything else.?



On Fri, 4 Oct 2019 at 4:30 PM, mike miniver<wa7ark@...> wrote: The internal LiOn battery (if connected) is like 3.7 to 4.2V. It is normally charged from externally-supplied USB 5V. This suggests to me that the innards run on something less than 3.7V (most likely 3.3V), meaning that there is an on-board voltage regulator to drop 5V to whatever the internals run on.

My question has to do with what is the maximum voltage that the internal voltage regulator can handle. If doing this, there would be no internal LiOn battery.

Reinier,
Gabriel only pops in now and then to let the group know how things are progressing. She posted that Maxscend rf switches will be used because, "the maxscend switches do not have the shunt diode problem (most RF switch ICs have parasitic diodes from RF input to ground which will start to conduct at lower frequencies), so it has no theoretical lower frequency limit and can be applied at the IF frequency".

My guesses are the Maxscend MXD8661 or MXD8680.

Herb

33 : the mathematical expressions

hello,

Allow us, please, to emphasize that the mathematical
expressions we used for:

30 : our final report 1 - 4 Oct 2019
/g/nanovna-users/message/3989

are just those mentioned at:
16 : 27 September 2019
/g/nanovna-users/message/3161

that is the ones shown at:


sincerely,

gin&pez@arg

33

Yes, "Return Loss" s o m e t i m e s is a misnomer: If used in context with simply two different impedances meeting at a connection.
This can be understood as a complex generator's inner (serial) impedance Z2 being terminated with a (serial) complex load Z1 (parallel to
be recalculated to serial equivalent).

This can be built from lumped components.

Everybody will agree, that there is absolutely no "returning" of a "wave", and no "reflection", in what is just a complex voltage divider.
Physically it is a different (no wave) phenomenon. In such cases, all the following are "misnomers" I n t h e s t r i c t s e n s e of the wording:

Standing "Wave" Ratio,
"Reflection" Factor,
"Return" Loss.


Reflections will, however, appear on Lines: there is a forward wave and a reflected wave.
There is a (wave typical) 180° phase shift by reflection involved, that makes valid

Gamma = (Z1 - Z2) / (Z1 + Z2) (a)

But where there are no waves, there are also no reflections and thus no 180° phase shift. This is why we get a different formula.
Please note, that Z2 above is the line's w a v e impedance - that does not exist in lumped circuits.

There we need to use a different Gamma:

Gamma = (Z1 - Z2*) / (Z1 + Z2) (b) with the asterisk meaning conjugate complex.

Z2 here now means generator's inner impedance (Some call it Thévenin Impedance.)

Unfortunately so many well established papers and publications do not care for that difference between (a) and (b) , just very few do.

And the many careless publications are being quoted and repeated ever so often. That is the problem. (Just the same as with fake news ...)


So - for complex voltage dividers - that is where there are simply no waves involved -
but also if one had previously calculated equivalent impedances on places with waves, like at line ends -
thus whenever we are using a load impedance Z1 and an (equivalent) generator impedance Z2, the above (b) is the correct formula.

The problem with the Smith Chart is, that the Z (or Y) Plane is mapped to the Gamma plane only by formula (a).

It would be extremely bad to "reinvent" the Smith Chart.

So we must live with (a) - like it or not. I see no choice.

The good thing is: The same (Smith chart type) mapping formula can stay, if both (serial) reactances are combined together at the load side.
Then the (thus new) generator impedance is real without reactance and the (thus new) load includes the sum of the two (serial) reactances.
Then the conformal mapping formula (a) can be applied again as usual in the Smith Chart.


We need the voltage divider type formula (b) when dealing with power transfer.


But when will that become common knowledge?

Debating fake physics (calculating with wave formulas where there are no waves and thus no no phase shift) is like fighting against windmills ...


73, Hans
DJ7BA




-----Ursprüngliche Nachricht-----
Von: [email protected] <[email protected]> Im Auftrag von Oristo
Gesendet: Freitag, 4. Oktober 2019 17:32
An: [email protected]
Betreff: Re: [nanovna-users] Return Loss

its become the consensus that return loss is a negative number

IMO, "return loss" is a poor term.
Arguably, >>any<< return is loss, when sending power is the goal. In which case, "return loss" might be power sent (since lost from return)..




--
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.

DMR_M_10KHz_sept-13-19.dfu
Such as these were for enhancements, in this case 10KHz instead of 50KHz
minimum.
I >>guess<< many enhancements are in Gen Hu Oct 2 firmware"

- Should this be installed before or after the firmware?

Any .dfu installed becomes the only firmware, replacing previously installed firmware.

- Which firmware can be used to set an impedance different than 50 Ohm?

I know of none. No real benefit, since reflection bridge components are fixed for 50 Ohms.
Firmware based on different calibration impedance would improve neither sensitivity nor accuracy.

Steven Maas if I recall in one of his little texts, mentions, I dis like the term return loss.

Its one of those EE crazy terms!

That said, I never discuss return loss with any thought whatsoever. All return loss numbers that ever roll off my lips are positive. Per the IEEE definition. I feel fine with this for the simple reason as follows:

A filter... its passive... generates no power, lousy filter, 2 dB return loss, ugh. Good filter, great match in the pass band, 20 dB return loss. I'll take it.

I just finished a power amplifier design. Output power 500 W and oh by the way, the return loss is 15 dB. Wow.... Is that 15 dB or -15 dB sir? Hey all my power amplifiers are UNCONDITIONALLY stable. I don't build oscillators here, sir!

Alan

32 : a REGION executable
-
also @Gary O'Neil :
27 September 2019 - /g/nanovna-users/message/3259
26 September 2019 - /g/nanovna-users/message/3091
26 September 2019 - /g/nanovna-users/message/3070

Hello,

Allow us, please, to inform you that we just uploaded the version 101 of
REGION executable:



- 131,584 bytes -

Sincerely,

gin&pez@arg

32

Correct.

The measurement conducted is a SPOT NOISE FIGURE measurement. The VNA or a SA may be set into the CW or fixed frequency receive mode. If you desire a swept NF measurement, than perhaps steps may be a small concern but still, that would be easy to average. Yes, conducting NF measure at BAD or bright frequencies is not easy. Try conducting a NF in the middle of the FM radio band. You need to be in a screen room. However, for the most part most of the spectrum is pretty quiet.

The LNA in front of the SA is critical. You need to have a low noise figure to eliminate the SA from contributing to the noise figure value, so called 2nd stage contribution affect and you must have sufficient gain to over come the intrinsic noise power of the SA. You must see a definitive noise power shift on the SA between firing (HOT source) and going COLD (noise source OFF) to determine the Y factor value.

Bandwidth is not an issue as long as there is sufficient noise power visible on the SA. Recall, noise power is directly linked to BW as a 10 log BW value. Our assumption here is that the BW of the DUT is larger than the BW of the measurement system. Measurement of NF of narrow band devices is difficult simply because there is insufficient noise power!

Alan

Thanks for all these info, compliments.

This interests me:
"DMR_M_10KHz_sept-13-19.dfu
Such as these were for enhancements, in this case 10KHz instead of 50KHz minimum.
I >>guess<< many enhancements are in Gen Hu Oct 2 firmware"
- Should this be installed before or after the firmware?

- Which firmware can be used to set an impedance different than 50 Ohm?

Need to place the file with the electrical circuit separately.

added to Wiki Main Menu:
/g/nanovna-users/wiki

Fit a RCA/0.1" pins/BNC/SO239/SMA (depends what freq range and what is to
hand) to either side of a pcb and the DUT (Device Under Test) in between.

I looked for BNC with 0.1" spacing, but so far found only this:

Need to place the file with the electrical circuit separately. Some do not suspect that it is in the instruction manual.
Many questions will disappear.