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.
Oristo