¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Latest edy555 firmware release with dfu file


 

Hot off the presses, folks:

Version 0.2.3

edy555 released this 1 hour ago

-change toggle behavior of trace menu and marker menu
-add transform command to change mode of TDR
- add threadshold command
-remove cal glitch between different harmonic modes
-NanoVNA-saver in multisegment mode shall work well

** Needs touch calibration and save it after flashing firmware.



Regards,
Larry


 

Seems to work well.

One small request - Could the velocity factor that has been used please be added to the TDR marker text, or displayed in some other way, so that it's more obvious if you have used the wrong value for the type of cable being measured.

Regards,

Martin - G8JNJ


 

Hello Larry,
I tried to flash your provided file edy-0.2.3-oct-7-19.dfu
under MacOS with the program dfu-util (Ver. 0.9), which I have used before.

I have learned from the manual, that the USB product ID should be "df11".
Unfortunately in your provided file the USB Product ID was 0,
so it coud not be programmed. See error:
dfu-util: Error: File ID 0483:0000 does not match device (0483:df11 or 0483:df11)

Next I have taken the .hex file under Windows 10 and program DfuFileMgr.exe
to add the Provider ID "df11".
Then I could flash in the Terminal:
$ dfu-util -v -d 0483:df11 --alt 0 -D nanoVNA_0.2.3-ch.dfu

I have appended to file nanoVNA_0.2.3-ch.dfu

73, Rudi


 

OK, thank you for adding the updated file.
Unfortunately, the Windoze DefuSe app doesn't care about the USB IDs and I forgot to check when I converted.

On Monday, October 7, 2019, 2:07:41 p.m. GMT-4, reuterr@... <reuterr@...> wrote:

Hello Larry,
I tried to flash your provided file edy-0.2.3-oct-7-19.dfu
under MacOS with the program dfu-util (Ver. 0.9), which I have used before.

I have learned from the manual, that the USB product ID should be "df11".
Unfortunately in your provided file the USB Product ID was 0,
so it coud not be programmed. See error:
dfu-util: Error: File ID 0483:0000 does not match device (0483:df11 or 0483:df11)

Next I have taken the .hex file under Windows 10 and program DfuFileMgr.exe
to add the Provider ID "df11".
Then I could flash in the Terminal:
$ dfu-util -v -d 0483:df11 --alt 0 -D nanoVNA_0.2.3-ch.dfu

I have appended to file nanoVNA_0.2.3-ch.dfu

73, Rudi


 

Rudi,

You could also omit the "-d 0483:df11" parameter from the dfu-util command line.

Ralph


 
Edited

Hello Ralph,

You could also omit the "-d 0483:df11" parameter from the dfu-util command line.
Ralph

Thank you for the hint, but see the man page:
-d, --device [Run-Time VENDOR]:[Run-Time PRODUCT][,[DFU Mode VENDOR]:[DFU Mode
PRODUCT]]
Specify run-time and/or DFU mode vendor and/or product IDs of the DFU
device to work with. VENDOR and PRODUCT are hexadecimal numbers (no pre-
fix needed), "*" (match any), or "-" (match nothing). By default, any
DFU capable device in either run-time or DFU mode will be considered.

If you only have one standards-compliant DFU device attached to your
computer, this parameter is optional. However, as soon as you have mul-
tiple DFU devices connected, dfu-util will detect this and abort, asking
you to specify which device to use.

If you have more than one DFU device on the USB bus it will be a problem,
so I think it is saver to add this option.

73, Rudi DL5FA