开云体育

Hi Hans No In /g/nanovna-users/wiki you will find /g/nanovna-users/files/Firmware/Windows%20guide%20on%20how%20to%20write%20firmware.pdf .. which describes how to

Hello all, I looked at github for new firmware 0.4.0 and i found at https://github.com/ttrftech/NanoVNA/releases only the firmware in hex or bin. Can i find anywhere the firmware from edy555 in .dfu

Re: DL9CAT version 0.4.0-2? I have encountered the following problem. CW FREQ once started can not be stopped,you have to shut down the device.

Well, the PC regognises the device as "STM32 Bootloader" , is that not OK? I have loaded several versions of version into my NanoVNA before, without any problem. Thanks anyhow Jos Op 10-11-2019 om

Ah, Zadig , not zdiag now I understand. Thanks Jos Op 10-11-2019 om 20:06 schreef Larry Rothman:

Jos, Did you install the STM drivers as described in the wiki at the end of the webpage?

Hi Rune, Yes, I used Zadig to install the USB drivers like WinUSB for use with SDR hardware? (Software Defined Radio). Besides, the PC recognises NanoVNA, you hear the sound when connecting and the

Look at Time's Meg. It's called Zadig, not zdiag.

Hi Andy, upgrading to a higher frequency range doesn't lose you any other features, and you don't *have* to use it ;-) But the newer firmwares DO contain bugfixes, and new features. QRP RX has been

No, I did read several user guids but not none that have info on the zdiag utility, can guide me to it ? I? can google for it as well. Referring to the WinUSB driver, Windows' Device Manager shows :

Ok, I stand corrected, Nooelec is the ttrftech authorized distributor. I hadn't look at edy555' GitHub page in a while.

I *think* I had to use something called Zadig to change the USB driver used: https://zadig.akeo.ie I certainly used it, at least, but quite *what* driver I had to change to I don't remember - and this

I don't know where you got your info from but ttrftech's edy555 was the original designer of the NanoVNA and hugen modified the charging circuit and designed the current PCB and was selling them on

Vaclav, it sounds like you have the background for it then, but maybe just not recent experience! The error you got concerning C99/C11 should be fairly self-explanatory, and probably just depends on

Please read up on the zdiag utility.? Check here...?/g/nanovna-users/message/4624 I had a similar issue at one point. You need to ensure you've got the win.usb driver installed.?

I purchased a NanoVNA from Nooelec (the authorized distributor from the edy555/ttrftech github page). I didn't realize at the time that all of the designs were actually based on hugen79's schematic

i did more, 1) Un-installed DFUseDemo 2) Cleaned the registry. 3) Restarted the PC. 4) Re-injstalled DFUsePackage 5) Looked in Windows Device manager : USB Devices ----> STM32 bootloadeer. 6) Result :

I am not sure I agree. It is MY understanding that (git) branch is sort-of "making a detour" in coding and eventually include such detour into the main flow. Assuming that I have the original code

Hello, I found your idea of adding Bluetooth interesting, but I am a little confused: Are you normally a C-programmer? Do you work with embedded software? The firmware is written in C, and I probably

Hi Guyla Yes, I read that. But it does not say *why* the grounds for the N connectors are kept separate. Any ideas? 73 Nick G3VNC