开云体育

Hi Rune,

Would it be possible to use Saver as a mechanism to run the internal Nano calibration routine, and save these plus any other settings, without having to use the Nano interface. Then store the values to saver so that it's possible to use Saver as a repository for the Nano values, even though Saver doesn't use them itself ?

If it was then possible to download the values back into the Nano memories, this would save considerable time and allow additional configurations to be retained and quickly put back in to the Nano's limited memories when required.

Regards,

Martin - G8JNJ

Hi Martin,
that's a very interesting suggestion. I've put it on my backlog under
"Future / Cool ideas" ;-)

I *think* the firmware allows it. Probably. But I'm not entirely sure how
to do it.

Currently, I think I prefer to evolve the calibration methods I have put
into application itself, as this already allows saving to a files, and
loading whatever calibration is relevant for your measurement. It
still lacks a number of features, and those will take priority at first.

Thank you for making the suggestion, though!
--
Rune / 5Q5R

On Fri, 4 Oct 2019 at 15:28, Martin via Groups.Io <martin_ehrenfried=
[email protected]> wrote:

Hi Rune,

Would it be possible to use Saver as a mechanism to run the internal Nano
calibration routine, and save these plus any other settings, without having
to use the Nano interface. Then store the values to saver so that it's
possible to use Saver as a repository for the Nano values, even though
Saver doesn't use them itself ?

If it was then possible to download the values back into the Nano
memories, this would save considerable time and allow additional
configurations to be retained and quickly put back in to the Nano's limited
memories when required.

Regards,

Martin - G8JNJ

Martin,
You might also try using the console commands via a terminal to accomplish saving and loading configurations. If it can be done via a terminal, then you can provide that feedback to Rune and it will make it easier for him to incorporate that function into his application. Larry has just added an updated list of commands to the "Files" section.

Herb

The current firmware allows dumping the internal calibration table with the data command
data [0-6]
where
0: S11
1: S21
and
2 /* error term directivity */
3 /* error term source match */
4 /* error term refrection tracking */
5 /* error term transmission tracking */
6 /* error term isolation */
but it is currently NOT possible to upload calibration tables into the nanoVNA

Thanks for the clarification Erik,
With everything Rune has on his plate I'd hate for him to waste his programming efforts on something the firmware does not implement. Usually all save commands come with a reciprocal load command. In this case I guess the firmware developer(s) were being cautious about corrupting the device with erroneous data.

Herb

Thanks - add it to the console command doc.
...Larry

Pretty sure nanovnasharp does this.
Tried decompiling the thing but im no coder so all i found was this
private void save0Button_Click(object sender, EventArgs e)
{
this.controller.SendDataToCom("save 0\r\n");
this.saveGroupBox.Visible = false;
this.stateGroupBox.Visible = true;
this.responseGroupBox.Visible = true;
this.languageGroupBox.Visible = true;

with save 0 to 4
and then recall 0 to 4

Please have a look at the firmware.
The "save" command saves the internally measured calibration data to the internal save location [0-4], recall is the reciprocal command to load calibration data from the internal save location.
The "save" command does NOT upload calibration data from outside the nanoVNA into the nanoVNA
The "data" command downloads data from thenanoVNA to the PC, there is no reciprocal command to upload data from the PC to the nanoVNA

On Sun, Oct 6, 2019 at 10:49 AM, <erik@...> wrote:

no reciprocal command to upload data from the PC to the nanoVNA

It would seem sensible to add a reciprocal command if at all possible.

Anything to avoid having to physically manually enter long sequences is very desirable, especially as it's only possible to retain a small number of configurations internally.

The ability to reload (or clone) settings when new firmware is installed or the memories are wiped would also be handy.

Regards,

Martin - G8JNJ

It would seem sensible to add a reciprocal command if at all possible.

Particularly if NanoVNA-H V2 may have no touch screen
or is controlled via BlueTooth or USB from mobile devices
(as now by WebUSB app with recent Android versions)