Re: nanovna-H black screen
A reset and everything is back to normal.
I remove the battery, wait for a few minutes and plug the battery back in.
The nanonovna-H wakes up from its sleep.
73.
|
Re: New Problem (Bricked?) Re: Trouble Setting Up DFuSE Driver
I apparently misstated where I got the recommendation for fw from, and now I can't find the reference, but the fw I uploaded was nanoVNA_800_ch_20190920.dfu.
|
Hi, Gyula.
I tried that with no change.
Chris VK5SA
|
New Problem (Bricked?) Re: Trouble Setting Up DFuSE Driver
Apparently you can brick one of these, even with a recommended firmware upload.
As previously noted, I was able to get DFuSe to recognize the unit and uploaded the 800MHz firmware, which the NanoVNA.com site recommended as being more stable. The firmware operates, but is missing the CONFIG option. I found several things I didn't like in the version and set about trying to upload a different version. I tried the jogwheel press while powering on and got a white screen which is supposed to indicate that the unit is in DFU mode. When I plugged it in, the computer didn't recognize it. I thought maybe I needed to do the hardware boot option so I shorted the Vcc and Boot terminals as recommenced and when I powered up I got the same white screen, but still no recognition when I plugged the unit in to the computer. I reinstalled the driver which had worked before, but still no recognition that the unit is being plugged in.
Help. Please!
|
Re: Trouble Setting Up DFuSE Driver
Well, I followed the directions, but when my indications didn't agree I quit reading. I finally realized (from the "you can¡¯t brick it" note that the designation of STM Bootloader was correct. I had to go to the DFuSe folder and manually install the correct driver. I now have it working in DFU mode.
On to trying to get the normal mode to work properly......
toggle quoted message
Show quoted text
-----Original Message----- From: [email protected] < [email protected]> On Behalf Of Al Waschka Sent: Monday, January 23, 2023 1:35 PM To: [email protected]Subject: Re: [nanovna-users] Trouble Setting Up DFuSE Driver Thanks for trying to help, but I think I followed the directions in the link explicitly. Comments below marked <<<<<xxxxx>>>>>> -----Original Message----- From: [email protected] < [email protected]> On Behalf Of HA3HZ Sent: Monday, January 23, 2023 1:00 PM To: [email protected]Subject: Re: [nanovna-users] 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. <<<<<<The first thing I did was to install the virtual comm port driver, as suggested in the link you sent me.>>>>>> 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. <<<<<<When I installed DFuSe, no driver was installed for the device. >>>>>>> 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. <<<<<<<I have repeatedly uninstalled the devices (operate mode and DFU mode) in Device manager to no avail.>>>>>> <<<<<<<In DFU mode it is identifying as an STM Bootloader and will not allow driver update. Does the firmware provide a device identity to Windows which then specifies the appropriate driver? Where is the STM Bootloader ID coming from?>>>>>>> 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 driver should be here if you installed to the default directory:
C:\Program Files (x86)\STMicroelectronics\Software\DfuSe v3.0.6\Bin\Driver
|
Re: Trouble Setting Up DFuSE Driver
Thanks for trying to help, but I think I followed the directions in the link explicitly. Comments below marked <<<<<xxxxx>>>>>>
toggle quoted message
Show quoted text
-----Original Message----- From: [email protected] < [email protected]> On Behalf Of HA3HZ Sent: Monday, January 23, 2023 1:00 PM To: [email protected]Subject: Re: [nanovna-users] 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. <<<<<<The first thing I did was to install the virtual comm port driver, as suggested in the link you sent me.>>>>>> 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. <<<<<<When I installed DFuSe, no driver was installed for the device. >>>>>>> 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. <<<<<<<I have repeatedly uninstalled the devices (operate mode and DFU mode) in Device manager to no avail.>>>>>> <<<<<<<In DFU mode it is identifying as an STM Bootloader and will not allow driver update. Does the firmware provide a device identity to Windows which then specifies the appropriate driver? Where is the STM Bootloader ID coming from?>>>>>>> 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
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.
|
Igor - PY3IG
HA3HZ
Martin Glazer