Re: Trouble Setting Up DFuSE Driver
Greetings, I have successfully used a program called Zadig to manually overide windows insistance it already had the best driver issue. The Zadig program itself, as well as how to use it can be found on the web. I hope this may help you.
toggle quoted message
Show quoted text
On Jan 23, 2023, at 12:59, HA3HZ <gyula@...> wrote:
?The description of the steps means to me that you are not aware that in 'normal' operation, when the device communicates with the PC, you need a driver called VCP.
When you are in so-called DFU (device firmware upgrade) mode, you need another driver, which is automatically installed by the program when DfuSe is installed for the first time. Now we just need the dfu driver.
If for some reason this does not happen, or you have installed something and the PC accepts it - but you still cannot connect. Then you need the help of USBDeview. (search google: www.nirsoft.net)
This small program without installation shows you which USB device you have connected since the installation of your operating system. Shows the drivers. You can delete what may cause the collision with the right mouse button pointing to the row.
If several USB devices are connected, they are marked with a green line. Choose which one could be at fault. Be careful not to delete the necessary device from the queue.
After deleting, remove the device (which is in DFU mode) and you will find the win10 driver in the driver folder at the DefuSE installation location. Install this driver. Plug in the device that is still in DFU mode. USBDeview shows it in green. After that, the DefUSE demo will already see the device in dfu mode.
If you accidentally uploaded an incorrect or incorrect dfu file, the device will remain in dfu mode. If you can't login in normal mode, then don't panic either, just find the working dfu file and repeat the installation. After the installation, the device will log in normally by restarting (off - on).
I was long, if something is not clear, please ask or read on my website.
--
Gyula HA3HZ ( )
|
Re: Trouble Setting Up DFuSE Driver
The description of the steps means to me that you are not aware that in 'normal' operation, when the device communicates with the PC, you need a driver called VCP.
When you are in so-called DFU (device firmware upgrade) mode, you need another driver, which is automatically installed by the program when DfuSe is installed for the first time. Now we just need the dfu driver.
If for some reason this does not happen, or you have installed something and the PC accepts it - but you still cannot connect. Then you need the help of USBDeview. (search google: www.nirsoft.net)
This small program without installation shows you which USB device you have connected since the installation of your operating system. Shows the drivers. You can delete what may cause the collision with the right mouse button pointing to the row.
If several USB devices are connected, they are marked with a green line. Choose which one could be at fault. Be careful not to delete the necessary device from the queue.
After deleting, remove the device (which is in DFU mode) and you will find the win10 driver in the driver folder at the DefuSE installation location. Install this driver. Plug in the device that is still in DFU mode. USBDeview shows it in green. After that, the DefUSE demo will already see the device in dfu mode.
If you accidentally uploaded an incorrect or incorrect dfu file, the device will remain in dfu mode. If you can't login in normal mode, then don't panic either, just find the working dfu file and repeat the installation. After the installation, the device will log in normally by restarting (off - on).
I was long, if something is not clear, please ask or read on my website.
--
Gyula HA3HZ ( )
|
Re: Trouble Setting Up DFuSE Driver
When I right click on STM Bootloader in Device Manager and click on Driver
Details, W10 responds that no driver has been loaded for this device. It is
apparently recognizing the NAnoVNA in native form as the STM Bootloader.
IDK how to fix this......
toggle quoted message
Show quoted text
-----Original Message----- From: [email protected] < [email protected]> On Behalf Of ae1th@... Sent: Monday, January 23, 2023 12:28 PM To: [email protected]Subject: Re: [nanovna-users] Trouble Setting Up DFuSE Driver try this, when in device manager and you see - dfu in bootloader -right click on it, it should change to stm in dfu mode. then good to go , from memory,
|
Re: Trouble Setting Up DFuSE Driver
try this, when in device manager and you see - dfu in bootloader -right click on it, it should change to stm in dfu mode. then good to go , from memory,
|
Thanks I will check it out Thanks for your help, Thanks Dave On Mon, 23 Jan 2023, 17:20 Neil Preston W0NRP via groups.io, <w0nrp= [email protected]> wrote: This is a very good introduction to interpreting the Smith chart on your
Nano, along with links for more info.
|
thanks On Mon, Jan 23, 2023 at 9:20 AM Neil Preston W0NRP via groups.io <w0nrp= [email protected]> wrote: This is a very good introduction to interpreting the Smith chart on your
Nano, along with links for more info.
|
This is a very good introduction to interpreting the Smith chart on your Nano, along with links for more info.
|
Re: Trouble Setting Up DFuSE Driver
OK, I read the reference. I remembered that I had plugged the NanoVNA in to my laptop to charge the battery and, back in the day, that would have installed a driver that can only be removed by uninstalling the device and restarting the computer. Here is what I did:
1. NanoVNA in operate mode and plugged in
2. Found the "Unknown Device" in Device Manager and uninstalled it.
3. Unplugged NanoVNA
4. Set NanoVNA to DFU mode
5. Plugged it in.
6. Found STM Bootloader device and uninstalled it
7. Unplugged NanoVNA
8. Restarted computer
9. Uninstalled STM USB comport Driver
10. Reinstalled STM USB Comport Driver
11. Turned NanoVNA on in operate mode
12. Plugged NanoVNA in to USB port on computer
13. W10 responds with Unknown Device - try plugging in again or contact device manufacturer.
14. Went into Device manager and tried to update driver
15. W10 responds with "Best driver already installed for device.
I think I followed the instructions exactly as written in the link, except for trying to make sure the computer was clean w.r.t. NAnoVNA drivers, but still no joy.
Help?
Al K5TAN
toggle quoted message
Show quoted text
|
Re: recall saved images NanoVNA-h4
I suppose you could call it the "source" of the trace. As I understand it (if I really do!?), the s1p file is the measured values that were used to generate the trace. I'm not an s1p file user, but have been reading the nanovna groups messages for a long time. From what I've learned from the group, the s1p file is data that is processed and used by other software, and is not itself displayable on the nanovna.
The only (free) program that I've found and tried for displaying s1p files is AntScope2. There are others, but their descriptions made them seem unsuitable for my 'wants'. And, in the end, Antscope2 didn't really show me what I wanted to see, either (a reproduction of the trace or sweep).
Actually, I'm hoping to get on of the newest nanovna versions that can export and store traces to an SD card (or screenshots? Just now, I forget.)
Some of the PC software for the nanovna can print (or save) screenshots. (When connected to the nanovna.)
--
Doug, K8RFT
|
Re: Nanovna Saver stopped working
|
|
|
Re: Trouble Setting Up DFuSE Driver
|
Re: Trouble Setting Up DFuSE Driver
What are you doing wrong?
Believing Whinders when it tells you the best driver is already installed . . . . it isn't!
Dump what is there and install the driver that came with DFuSE!
toggle quoted message
Show quoted text
On January 23, 2023 12:12:22 AM CST, Al Waschka <awaschka@...> wrote: I am unable complete the step to validate the driver for DfuSe while trying to install and run DfuSe Demo.
My NanoVNA is apparently a clone. The Version Page says it is a NanoVNA-H Version 1;1 Build Time Dec 21 2021 13:46:37
When the unit is in normal mode, it shows up as an unidentified USB device. When set to DFU mode the device identifies as STM Bootloader.
I tried the Update Driver steps from the Absolute Beginners Guide. In both cases, update driver reports the best driver for my device is already installed.
i have done the above with and without the DFuSe Demo SW installed and running, with no difference.
What might I be doing wrong?
Thanks,
Al
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
|
Trouble Setting Up DFuSE Driver
I am unable complete the step to validate the driver for DfuSe while trying to install and run DfuSe Demo.
My NanoVNA is apparently a clone. The Version Page says it is a NanoVNA-H Version 1;1 Build Time Dec 21 2021 13:46:37
When the unit is in normal mode, it shows up as an unidentified USB device. When set to DFU mode the device identifies as STM Bootloader.
I tried the Update Driver steps from the Absolute Beginners Guide. In both cases, update driver reports the best driver for my device is already installed.
i have done the above with and without the DFuSe Demo SW installed and running, with no difference.
What might I be doing wrong?
Thanks,
Al
|
So I have SAA-2n that was working have maybe turned it on a few times at most... Went to test my new ant and cable today and the screen would touch to have menu come on but that was it... the test was lines up and down and very frustrating.
I took it apart just to see what I could see.. and well it wasn't working so can't get any worse. split it in half disconnected the ribbon on the screen and didn't see anything obvious wrong. apart didn't seen to work. Well I just threw it all together and it worked for 5 min..
hopefully it work work awhile and maybe I can learn to use it vs learn to hate this device.
Anyone know how hard it is to get parts? and or where to get some? thx
--
W7GEL
|
On Sat, Dec 24, 2022 at 04:27 AM, <gleamy2@...> wrote: "it is possible to export and save the s2p file of the latest file" could you explain how you are able to "export and save" ??? are you doing this on NanoVNA-f ? dan
|
Re: recall saved images NanoVNA-h4
hi Doug,
isn't the data in the S1P file the source of trace that is viewed on the NanoVNA ?
or are you saying that the S1P file can not be recalled into the NanoVNA ?
thanks for your reply, dan
|
toggle quoted message
Show quoted text
On Sunday, January 22, 2023 at 05:14:16 PM EST, Gene Fish <gerufish@...> wrote:
I purchased my H4 from R&L.? I only have version 1.1.01.? It saves files perfectly to a SanDisk 32 GB Ultra Plus card. I know I need to upgrde the software,? Don't know how, but I'm sure I'll figure it out.
|
Both VNAs have worked fine before, but now both have the same problem.
No change in settings that I can see.
A local ham came around on the weekend with the same problem.
Frustrating!
Chris VK5SA
|
Re: Nanovna Saver stopped working
Run it from the cli so you can see what errors it gives.
toggle quoted message
Show quoted text
On January 22, 2023 9:30:37 AM CST, Fkawee <frankw259@...> wrote: Hello Group.
I had the NanoVna Saver executable file loaded and working on my Ubuntu laptop.
The Ubuntu version was 18, Then I let it upgrade to version 20.
Since then when trying to run the Nanaovna Saver executable, there is no response. double click .... nothing...
I tried loading the latest version of the nanovana Saver Executable which is giving the same results.
I have searched for a possible remedy without finding any results.
Can anyone give any insight on what may of happened?
Thanks all
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
|
HA3HZ
Martin Glazer