开云体育

From: in3elx@...

The DMR-CLEAR_MEMORY_DFU.dfu file was corrupt... I have redone the download.
It would be better if there was a checksum txt-file ...
=====================================

Agreed.

MD5 (or better) should be available for all files. There are Windows program to generate and check MD5 signatures:

(command-line)
(GUI)

Cheers,
David
--
SatSignal Software - Quality software for you
Web:
Email: david-taylor@...
Twitter: @gm8arv

I have another question:
How do you try the edy555 firmware since it is not a .DFU?
Thanks

NOTE: the 900_aa version does not have the stop-boot problem after touchscreen calibration (with my white Gecko).
I look forward to the new 800_aa version with interest.

How do you try the edy555 firmware since it is not a .DFU?

DfuSe_Demo_V3.0.6_Setup.exe also installs DfuFileMgr.exe,
which can convert to dfu.

Read.? The.? User.? Guide.?
On Sat, 5 Oct 2019 at 9:28 am, in3elx@...<in3elx@...> wrote: I have another question:
How do you try the edy555 firmware since it is not a .DFU?
Thanks

NOTE: the 900_aa version does not have the stop-boot problem after touchscreen calibration (with my white Gecko).
I look forward to the new 800_aa version with interest.

On Sat, Oct 5, 2019 at 02:34 PM, Oristo wrote:

How do you try the edy555 firmware since it is not a .DFU?

DfuSe_Demo_V3.0.6_Setup.exe also installs DfuFileMgr.exe,
which can convert to dfu.

I tried but something is wrong.
I would like to try a tool for the original ady555 binary.

On Sat, 5 Oct 2019 at 16:08, <in3elx@...> wrote:

How do you try the edy555 firmware since it is not a .DFU?

DfuSe_Demo_V3.0.6_Setup.exe also installs DfuFileMgr.exe,
which can convert to dfu.

I tried but something is wrong.
I would like to try a tool for the original ady555 binary.

I just did this on Windows 10.
First, get the edy555 0.2.2 file:
from there, click the 'releases' icon near the top
the latest release is 0.2.2
click 'nanovna-firmware-0.2.2.zip' to download it to a place you
will remember. I put mine in c:\addons
Next, unzip it in a place you will remember :-)
I put mine in C:\addons\nanovna-firmware-0.2.2
Next, convert the .bin to .dfu
Start > STMicroelectronics > Dfu file manager
There are two choices. We want to GENERATE a DFU file from a BIN
file. Click OK.
On the right side, half way down there is a button for S19 or Hex. Click that.
Navigate to the place you unzipped 0.2.2, and go down into the build
directory. On my machine that is
C:\addons\nanovna-firmware-0.2.2\build
Click on ch.hex, and then Open.
Click Generate
You will be asked to save the file. I called mine nano_0.2.2.dfu,
and saved it in the same directory.
You get a message 'Success for Image for alternate setting...'
Click OK.

Now I have C:\addons\nanovna-firmware-0.2.2\build\nano_0.2.2.dfu

I used this dfu file to flash the NanoVNA with the DfuSe Demo 3.0.6 program.
I hope that helps!

Ciao!
--buck

AA version font requires a larger flash, resulting in saving the settings of
the flash address overlaps with the program flash and I will modify the aa
version later.

It eventually hung at power-on for me WITHOUT doing touchscreen calibration,
fortunately after capturing mostly legible menu screens.

Took this opportunity to exercise starbuck5250's DFU-from-Hex message:
/g/nanovna-users/message/4159

...hacked into

edy255's 0.2.2 ch.hex sadly has tiny font..

edy255's 0.2.2 ch.hex sadly has tiny font..

Also, touch screen seems much less responsive than Gen Hu releases,
and hung repeatedly (requiring power off/on) when trying to set START stimulus..

... back to NanoVNA-H__900_ch_20191003.dfu

I had the .dfu file generated and uploaded.
The edy555 firmware didn't convince me ... then I discovered that I have a problem with all types of firmware (NanoVNA-edy555, NanoVNA-H):
If you execute and save more than two calibrations, the others saved make me show always SWR 1:1, even with the SMA connector open (CH0)!

Usually memories (calibrated) that I saved are this:
0) 1Mhz-900Mhz; track 1: SWR CH0; track 2: Smith CH0
1) 1Mhz-30Mhz; track 1: SWR CH0; track 2: Smith CH0
2) 30Mhz-100Mhz; track 1: SWR CH0; track 2: Smith CH0
3) 80Mhz-500Mhz; track 1: SWR CH0; track 2: Smith CH0
4) 1Mhz-900Mhz; track 1: LOG CH0; track 2: LOG CH1 (for filter)

Note: before any upgrade I used the file for cleaning "DMR-CLEAR_MEMORY_DFU.dfu " (131 kB; Sep 30).

Now I am forced to save only 2 memories:
0) 1Mhz-900Mhz; track 1: SWR CH0; track 2: Smith CH0
1) "empty"
2) "empty"
3) "empty"
4) 1Mhz-900Mhz; track 1: LOG CH0; track 2: LOG CH1 (for filter)

Why?

Thanks

On Sun, Oct 6, 2019 at 9:30 PM <in3elx@...> wrote:

I have a problem with all types of firmware (NanoVNA-edy555, NanoVNA-H):
If you execute and save more than two calibrations,
the others ... show always SWR 1:1, even with the SMA connector open (CH0)!

Usually memories (calibrated) that I saved are this:
0) 1Mhz-900Mhz; track 1: SWR CH1; track 2: Smith CH1
1) 1Mhz-30Mhz; track 1: SWR CH1; track 2: Smith CH1
2) 30Mhz-100Mhz; track 1: SWR CH1; track 2: Smith CH1
3) 80Mhz-500Mhz; track 1: SWR CH1; track 2: Smith CH1
4) 1Mhz-900Mhz; track 1: LOG CH1; track 2: LOG CH2

Note: before any upgrade I used the file for cleaning "DMR-CLEAR_MEMORY_DFU.dfu " (131 kB; Sep 30).

FWIW, I don't think DMR-CLEAR_MEMORY_DFU.dfu helps
unless some desired firmware otherwise fails to load.

Now I am forced to save only 2 memories:
0) 1Mhz-900Mhz; track 1: SWR CH1; track 2: Smith CH1
1) "empty"
2) "empty"
3) "empty"
4) 1Mhz-900Mhz; track 1: LOG CH1; track 2: LOG CH2

Why?

My >> guess<< is that
this may be another consequence
from overlap of code and data flash segments.

Developers traditionally like to add new features but dislike testing.
Ideally, code functions and issue resolutions should require
automated unit regression tests, which can be hard for GUI.

I guess this currently happens especially with recent edy555 releases,
which may be more focused on PC software programmer requests:


..than on-device usability.

NanoVNA-H lists fewer issues:


Your issue could be added, if repeatable...

FWIW, I see no issues recalling 4 different calibrations
saved with NanoVNA-H__900_ch_20191003.dfu
from

On Sun, 6 Oct 2019 at 21:30, <in3elx@...> wrote:

Now I am forced to save only 2 memories:
0) 1Mhz-900Mhz; track 1: SWR CH1; track 2: Smith CH1
1) "empty"
2) "empty"
3) "empty"
4) 1Mhz-900Mhz; track 1: LOG CH1; track 2: LOG CH2

Why?

Ciao Roberto,
I wish I had the time to look at the code but my 'real' job keeps me
very busy. :-(

The developer of the firmware you are using might be reading this
group... or might not.
It's good to ask here first, because someone else might have already
seen the bug, or maybe has a way to work around it.

If no one here has any thoughts to share, then the best idea is to
report the bug to the developer on Github.
For edy555, you can go to and
click on the 'Issues' link near the top.

Thanks for helping to make the NanoVNA project better!
73 de Buck, KC2HIZ
--buck

I can't communicate with the developers.

Please stop repeating yourself in the forum - it is very poor etiquette.
You also appear to be the only one with this issue.
Please verify you are following all the various guides that are available here.
Read, then read some more, then google for nanovna on other websites where users have created pages about the device.

On Mon, Oct 7, 2019 at 07:24 PM, Larry Rothman wrote:

Please stop repeating yourself in the forum - it is very poor etiquette.
You also appear to be the only one with this issue.
Please verify you are following all the various guides that are available
here.
Read, then read some more, then google for nanovna on other websites where
users have created pages about the device.

On Monday, October 7, 2019, 2:16:39 p.m. GMT-4, <in3elx@...> wrote:


[Edited Message Follows]

I can't communicate with the developers.

I don't repeating anything.
What problem I do you create? Is this your etiquette/ham spirit?
This is a forum, those who want to help help me maybe they will, those who don't want to help me can read other things.
Good night. Thanks again.

Hi Larry and in3elx.

Larry he is not repeating himself he is editing his post. But he is
doing it with the web interface of the group.

You on the other side are using the email fonction of the group and
every time in3elx edit his post you receive a new email of his edited
post.

That is why you see [Edited Message Follows] into his messages.

hope this helps.

So that's what's going on. From the email readers point of view it's a mess!

Roy
WA0YMH

Does anyone know a way to cleaner the 5 calibration memories?
The DMR-CLEAR_MEMORY_DFU.dfu file does not seem to do this (only firmware cleaner?).
Thanks

Hi Rob,
simply you have to tap "CAL MENU" and then "RESET".
The "RESET" button will highlight and stay highlighted.
Invoking the RESET function will destroy all the previously saved calibration data, at that point you have to tap "SAVE" button.

Have a fun!

N.V.