开云体育

On Wed, Oct 23, 2019 at 7:51 AM KV5R <kv5r@...> wrote:

I would still like to see a "big text" screen for use with CW stimulus
mode, for "traditional" antenna analyzer field use. Just Freq, SWR, and
R+jX with big digits. Re: /g/nanovna-users/message/4772
--kv5r </g/nanovna-users/message/4772--kv5r>

On Wed, 23 Oct 2019 at 16:30, Larry Rothman <nlroth@...> wrote:

QRP's scanraw command is an extension of Erik's original scan command so
you shouldn't have any difficulty adapting.
The big question is do you want to be backwards compatible to Erik's old
scan command or just declare all 'Saver versions going forward from 0.1.4
use the new syntax (the better way) and maybe add a quick check with a
popup window to get the user to acknowledge the change.

On Wednesday, October 23, 2019, 9:56:06 a.m. GMT-4, Rune Broberg <
mihtjel@...> wrote:

Thank you, Erik - I might make use of the scanraw functions in a future
version, we will have to see :-)

--
Rune / 5Q5R

On Wed, 23 Oct 2019 at 15:51, <erik@...> wrote:

Yes, in my next update I will have QRP's scanraw so all firmwares have

the

same scan command and some have identical scanraw
Will make Rune's life more easy......

On Wednesday, October 23, 2019, 9:56:06 a.m. GMT-4, Rune Broberg <mihtjel@...> wrote:

Thank you, Erik - I might make use of the scanraw functions in a future
version, we will have to see :-)

--
Rune / 5Q5R

On Wed, 23 Oct 2019 at 15:51, <erik@...> wrote:

Yes, in my next update I will have QRP's scanraw so all firmwares have the
same scan command and some have identical scanraw
Will make Rune's life more easy......

On Wednesday, October 23, 2019, 9:51:23 a.m. GMT-4, erik@... <erik@...> wrote:

Yes, in my next update I will have QRP's scanraw so all firmwares have the same scan command and some have identical scanraw
Will make Rune's life more easy......

On Wed, 23 Oct 2019 at 15:51, <erik@...> wrote:

Yes, in my next update I will have QRP's scanraw so all firmwares have the
same scan command and some have identical scanraw
Will make Rune's life more easy......

On Wednesday, October 23, 2019, 9:27:16 a.m. GMT-4, erik@... <erik@...> wrote:

If you want to use this command sequence for the edy555 and hugen firmwares:
pause
scan startfreq endfreq count
frequencies
data
resume
you can insert the "cal" and "edelay" command if needed and these apply as on screen
For maximum multi measurements speed you should not "resume" but keep the nanoVNA paused


There is (because of a bad decision by me) possibly confusion on what the "scan" command does.
Edy555 original implementation was scan being equal to sweep and wait till the data was available.
I changed that to have scan doing an on demand scan with unlimited amount of points and NO calibration/edelay being apply
As this lead? to two different "scan" command Rune had to sort out the mess.

I intend to change my "scan" command to "scanraw" that will be the same as what already has been implemented by another firmware developer (sorry, forgot your name....)
scanraw will pause the "on screen" measurements as these interfere with realizing maximum speed.

So "scan" will always be in all firmwares an on demand measurement of maximum 101 points with everything (e.g. calibration and edelay)? the same as on the screen

On Wednesday, October 23, 2019, 7:57:58 a.m. GMT-4, Oristo <ormpoa@...> wrote:

Among things which may confusingly scrog nanoVNA traces..

Using NanoVNA-H_AA_20191018.dfu,

Setting by menu ELECTRICAL DELAY 50p
.. then shell `edelay` reports 50.000000000

Setting by menu ELECTRICAL DELAY 50n
.. then shell `edelay` reports 50000.000000000

Setting by menu ELECTRICAL DELAY 50000p
.. then shell `edelay` reports 50000.000000000

So far as I know, there is no way to find current ELECTRICAL DELAY value
from touch screen.
So far as I know, setting edelay to other than the value used for calibration
is generally doomed..?? It certainly yields weird Smith charts.

menu? STIMULUS - PAUSE SWEEP stops data capture,
then e.g. selecting another FORMAT changes display, but
changing SCALE? or RECALL settings while PAUSE SWEEP
has no effect on display

I thought that there was a way to disable display refresh
for improving speed of e.g. data capture and return by USB?

If menu STIMULUS - PAUSE SWEEP or shell `pause` is set,
then e.g. shell `data 0` gets no different data is obtained by repeating.

If shell `scan` is set only once, then `data 0` returns identical values each time.
shell `sweep` without arguments still returns its previous settings, which are no longer in effect.
shell `recall n` will recover from `sweep` setting..
I don't want to think about what happens
if shell `save n` after some `scan` setting...

shell `offset` with no argument does not return current value

shell `trace 2` can be set for AA firmware but (so far as I know) has no effect

I would like to document interactions among touchscreen menu CAL CORRECTION
with shell `data` `scan` and `sweep`
but have not sorted a simple conclusive test scheme,
given noisy data.

On Wednesday, October 23, 2019, 2:44:04 a.m. GMT-4, Nan <vk2krn@...> wrote:

I changed D2 to a Schottky Diode. With a fully charged battery, the 3rd battery bar turns on and off. (unstable)
Since I have a Hugen's NanoVNA-H, PCB V3.2, I chose to stick on with firmware NanoVNA-H_20191018.dfu. (latest release)

Fully charged battery voltage reads 4.1V and after D2 (diode voltage drop) I read 3.91V. That's about 0.2V drop as expected.
Also I have not fully understood all hardware differences between Edy555's design and Hugen's design so not sure if Edy555's firmware shall work correctly on my board.

@ QRP RX - thanks for your offer to modify firmware, but that will not allow me to change/update firmware's as newer versions release. Is there any simpler way out?

BR - Nan

On Wednesday, October 23, 2019, 12:37:42 a.m. GMT-4, Daniel Marks <profdc9@...> wrote:

I made a fixture PCB for my VNA and I think it would be useful as well for the NanoVNA.? You can find it at:



It has the following features:

1.? Calibration standards for open, short, load, thru for SMA and BNC
2.? Four spots to solder on 0805 SMD components to create test loads for SMA, and an area left so that one can label the loads.
3.? ZIF socket for leaded component testing, both SMA and BNC
4.? A spot to place a spring clip into the board so that you can lay components flat against the board and clip them in to test them.

I do not think these calibration standards will necessarily work out to 900 MHz but should be useful for convenient testing at HF/VHF.

A picture of the test fixture is below.

Dan

Le 23/10/2019 à 11:23, Pierre-Fran?ois (f5bqp_pfm) a écrit?:

Hello Rune,

Where is the link to get this new beauty, I dont see it.

73's
Pierre-Fran?ois, F5BQP


Le 23/10/2019 à 09:56, Rune Broberg a écrit?:

Hello all,
I just released NanoVNA-Saver 0.1.4. Here are the release?notes:

This release adds a number of new features, some bug fixes, and some internal reorganisation:

Adding markers:
You can now add or remove markers, allowing you as many as you can fit on your screen. In fact, the software does not stop there: You can even add markers which you can't fit on your screen!

New charts:
A number of new chart types have been added, allowing you to plot |Z|, |S11| and |S21| in linear format, S11 and S21 logarithmic on the same chart at the same time, and the raw S11 and S21 real/imaginary S-parameter values.

Calibration updates:
The calibration assistant has become more talkative, and should be better at telling you what has gone wrong when it won't apply a calibration. When applying a new calibration, or applying after changing to a different calibration standard set, the previous sweep is immediately updated to show the effect of the new values. This should be useful for finding the right values for calibration standard sets.

Bugfixes:
Line thickness and point size should now load correctly and apply to charts after you restart the software.
SWR marker colours should similarly also load correctly.
The software should now be able to run and attempt to check for updates, and not crash when you don't have an internet connection.

I hope these features and updates are useful to the community!


I look forward to hearing the feedback from you all!

And a little announcement: I have been really quite busy with this software for the past two or so months. I'm now going to take a little break and relax, and I therefore don't expect to make any new releases next week (*gasp*), and I might even be slow in responding to your emails.

You have all been very kind in writing to me both showing your appreciation, as well as pointing out bugs, misunderstandings, potential improvements and new ideas. I appreciate this greatly, and I hope you will continue to do so, even as I take a week or so to relax ;-)

--
Rune / 5Q5R

--
Pierre-Fran?ois, F5BQP
Locator: JN18AN

On Wed, 23 Oct 2019, 08:56 Rune Broberg, <mihtjel@...> wrote:

Hello all,
I just released NanoVNA-Saver 0.1.4. Here are the release notes:

This release adds a number of new features, some bug fixes, and some
internal reorganisation:

Adding markers:
You can now add or remove markers, allowing you as many as you can fit on
your screen. In fact, the software does not stop there: You can even add
markers which you can't fit on your screen!

New charts:
A number of new chart types have been added, allowing you to plot |Z|,
|S11| and |S21| in linear format, S11 and S21 logarithmic on the same chart
at the same time, and the raw S11 and S21 real/imaginary S-parameter
values.

Calibration updates:
The calibration assistant has become more talkative, and should be better
at telling you what has gone wrong when it won't apply a calibration. When
applying a new calibration, or applying after changing to a different
calibration standard set, the previous sweep is immediately updated to show
the effect of the new values. This should be useful for finding the right
values for calibration standard sets.

Bugfixes:
Line thickness and point size should now load correctly and apply to charts
after you restart the software.
SWR marker colours should similarly also load correctly.
The software should now be able to run and attempt to check for updates,
and not crash when you don't have an internet connection.

I hope these features and updates are useful to the community!


I look forward to hearing the feedback from you all!

And a little announcement: I have been really quite busy with this software
for the past two or so months. I'm now going to take a little break and
relax, and I therefore don't expect to make any new releases next week
(*gasp*), and I might even be slow in responding to your emails.

You have all been very kind in writing to me both showing your
appreciation, as well as pointing out bugs, misunderstandings, potential
improvements and new ideas. I appreciate this greatly, and I hope you will
continue to do so, even as I take a week or so to relax ;-)

--
Rune / 5Q5R