Re: NanoVNA Not Recognized by Laptop over USB After dfu Upgrade
Distro is very limited. Doesn't have -w either. I give up on Linux. I can't get the CD drive to load anything else or even to reload the Grml-small I had on there to begin with.
I received my USB-A Male to Male cable. I connected it, with an A-C adapter between the original W10 laptop and the NanoVNA. It gave the same result as the other two cables.
When I said the device was working properly in the analyzer mode I had only looked at boot behavior. I don't remember actually checking it on an antenna. When I connected it to my tuned antenna its readings are different from the SWR meter on my transceiver.
It has also started flashing the white screen momentarily when turning on in the analyzer mode. I don't recall noticing that before.
I think either the device is failing or possibly the hardware was not compatible with the firmware I loaded.
I am officially giving up on trying to figure out what happened. I guess I'll have to take the risk that it won't happen with whatever replacement unit I get.
Going back to vendor tomorrow.
K5TAN
ZZZZ
Out
toggle quoted message
Show quoted text
-----Original Message----- From: [email protected] < [email protected]> On Behalf Of Tim Dawson Sent: Friday, January 27, 2023 7:40 PM To: [email protected]Subject: Re: [nanovna-users] NanoVNA Not Recognized by Laptop over USB After dfu Upgrade You can still see what is going on without the "-H" option, the output is just a little less clear. Basically, run "dmesg -w", and then plug the USB device in, and you should see the system react to it. (You can also see the same in syslog . . .) On January 27, 2023 6:33:23 PM CST, Al Waschka <awaschka@...> wrote: Thanks, I was wondering if that was the cause. I just picked up my ipad to check the syntax but saw your message first.
Greml small was suggested so that is what I loaded. I am running on an old xp box with 1G ram and 1.7 ghz celeron.
I’ll try to find another to load.
On Jan 27, 2023, at 7:27 PM, Tim Dawson <tadawson@...> wrote:
?Looks like a distro with crippled dmesg . . . . the man page clearly states "-H: Human readable output" and "-w: wait" so the options *should* be valid.
On January 27, 2023 6:17:49 PM CST, Al Waschka <awaschka@...> wrote:
Actual response is Invalid parameter, I think
On Jan 27, 2023, at 6:00 PM, Al Waschka <awaschka@...> wrote: ?Hope this isn’t considered off topic. It is about troubleshooting a NanoVNA.
Finally got the greml distro working. When I enter the string you suggested it says -H is unrecognized.
On Jan 27, 2023, at 6:07 AM, Ho-Ro <linuxaudio@...> wrote:
?On Fri, Jan 27, 2023 at 01:59 AM, Al Waschka wrote:
I am trying to get my hands on a Liinux device to see how it
responds in both modes to Linux commands
On Thu, Jan 26, 2023 at 08:50 PM, Al Waschka wrote:
HP Pavilion ZE 4220 Laptop
Old.
Celeron processor over 1 GHz
960MB Ram (1G?)
CD Drive
Ethernet and USB
Al,
You could download a "live" image, no installation required.
For your HW this small "rescue-linux" should be ok:
- Select the "grml-small" "32-bit PC" version, currently this one:
- Burn as ISO to a CD and boot the laptop from this CD.
- Then just type "dmesg -Hw" and connect your NanoVNA.
Look at the responses when switching on / off in various modes (jog pressed / not pressed, BOOT0-VDD shorted / open, etc.).
Martin
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-- Sent from my Android device with K-9 Mail. Please excuse my brevity.
|
Re: NanoVNA Not Recognized by Laptop over USB After dfu Upgrade
You can still see what is going on without the "-H" option, the output is just a little less clear. Basically, run "dmesg -w", and then plug the USB device in, and you should see the system react to it. (You can also see the same in syslog . . .)
toggle quoted message
Show quoted text
On January 27, 2023 6:33:23 PM CST, Al Waschka <awaschka@...> wrote: Thanks, I was wondering if that was the cause. I just picked up my ipad to check the syntax but saw your message first.
Greml small was suggested so that is what I loaded. I am running on an old xp box with 1G ram and 1.7 ghz celeron.
I’ll try to find another to load.
On Jan 27, 2023, at 7:27 PM, Tim Dawson <tadawson@...> wrote:
?Looks like a distro with crippled dmesg . . . . the man page clearly states "-H: Human readable output" and "-w: wait" so the options *should* be valid.
On January 27, 2023 6:17:49 PM CST, Al Waschka <awaschka@...> wrote:
Actual response is Invalid parameter, I think
On Jan 27, 2023, at 6:00 PM, Al Waschka <awaschka@...> wrote: ?Hope this isn’t considered off topic. It is about troubleshooting a NanoVNA.
Finally got the greml distro working. When I enter the string you suggested it says -H is unrecognized.
On Jan 27, 2023, at 6:07 AM, Ho-Ro <linuxaudio@...> wrote:
?On Fri, Jan 27, 2023 at 01:59 AM, Al Waschka wrote:
I am trying to get my hands on a Liinux device to see how it responds in both
modes to Linux commands
On Thu, Jan 26, 2023 at 08:50 PM, Al Waschka wrote:
HP Pavilion ZE 4220 Laptop
Old.
Celeron processor over 1 GHz
960MB Ram (1G?)
CD Drive
Ethernet and USB
Al,
You could download a "live" image, no installation required.
For your HW this small "rescue-linux" should be ok:
- Select the "grml-small" "32-bit PC" version, currently this one:
- Burn as ISO to a CD and boot the laptop from this CD.
- Then just type "dmesg -Hw" and connect your NanoVNA.
Look at the responses when switching on / off in various modes (jog pressed / not pressed, BOOT0-VDD shorted / open, etc.).
Martin
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
|
Re: NanoVNA Not Recognized by Laptop over USB After dfu Upgrade
Thanks, I was wondering if that was the cause. I just picked up my ipad to check the syntax but saw your message first.
Greml small was suggested so that is what I loaded. I am running on an old xp box with 1G ram and 1.7 ghz celeron.
I’ll try to find another to load.
toggle quoted message
Show quoted text
On Jan 27, 2023, at 7:27 PM, Tim Dawson <tadawson@...> wrote:
?Looks like a distro with crippled dmesg . . . . the man page clearly states "-H: Human readable output" and "-w: wait" so the options *should* be valid.
On January 27, 2023 6:17:49 PM CST, Al Waschka <awaschka@...> wrote:
Actual response is Invalid parameter, I think
On Jan 27, 2023, at 6:00 PM, Al Waschka <awaschka@...> wrote: ?Hope this isn’t considered off topic. It is about troubleshooting a NanoVNA.
Finally got the greml distro working. When I enter the string you suggested it says -H is unrecognized.
On Jan 27, 2023, at 6:07 AM, Ho-Ro <linuxaudio@...> wrote:
?On Fri, Jan 27, 2023 at 01:59 AM, Al Waschka wrote:
I am trying to get my hands on a Liinux device to see how it responds in both
modes to Linux commands
On Thu, Jan 26, 2023 at 08:50 PM, Al Waschka wrote:
HP Pavilion ZE 4220 Laptop
Old.
Celeron processor over 1 GHz
960MB Ram (1G?)
CD Drive
Ethernet and USB
Al,
You could download a "live" image, no installation required.
For your HW this small "rescue-linux" should be ok:
- Select the "grml-small" "32-bit PC" version, currently this one:
- Burn as ISO to a CD and boot the laptop from this CD.
- Then just type "dmesg -Hw" and connect your NanoVNA.
Look at the responses when switching on / off in various modes (jog pressed / not pressed, BOOT0-VDD shorted / open, etc.).
Martin
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
|
Re: NanoVNA Not Recognized by Laptop over USB After dfu Upgrade
Looks like a distro with crippled dmesg . . . . the man page clearly states "-H: Human readable output" and "-w: wait" so the options *should* be valid.
toggle quoted message
Show quoted text
On January 27, 2023 6:17:49 PM CST, Al Waschka <awaschka@...> wrote: Actual response is Invalid parameter, I think
On Jan 27, 2023, at 6:00 PM, Al Waschka <awaschka@...> wrote:
?Hope this isn’t considered off topic. It is about troubleshooting a NanoVNA.
Finally got the greml distro working. When I enter the string you suggested it says -H is unrecognized.
On Jan 27, 2023, at 6:07 AM, Ho-Ro <linuxaudio@...> wrote:
?On Fri, Jan 27, 2023 at 01:59 AM, Al Waschka wrote:
I am trying to get my hands on a Liinux device to see how it responds in both
modes to Linux commands
On Thu, Jan 26, 2023 at 08:50 PM, Al Waschka wrote:
HP Pavilion ZE 4220 Laptop
Old.
Celeron processor over 1 GHz
960MB Ram (1G?)
CD Drive
Ethernet and USB
Al,
You could download a "live" image, no installation required.
For your HW this small "rescue-linux" should be ok:
- Select the "grml-small" "32-bit PC" version, currently this one:
- Burn as ISO to a CD and boot the laptop from this CD.
- Then just type "dmesg -Hw" and connect your NanoVNA.
Look at the responses when switching on / off in various modes (jog pressed / not pressed, BOOT0-VDD shorted / open, etc.).
Martin
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
|
Re: NanoVNA Not Recognized by Laptop over USB After dfu Upgrade
Actual response is Invalid parameter, I think
toggle quoted message
Show quoted text
On Jan 27, 2023, at 6:00 PM, Al Waschka <awaschka@...> wrote:
?Hope this isn’t considered off topic. It is about troubleshooting a NanoVNA.
Finally got the greml distro working. When I enter the string you suggested it says -H is unrecognized.
On Jan 27, 2023, at 6:07 AM, Ho-Ro <linuxaudio@...> wrote:
?On Fri, Jan 27, 2023 at 01:59 AM, Al Waschka wrote:
I am trying to get my hands on a Liinux device to see how it responds in both
modes to Linux commands
On Thu, Jan 26, 2023 at 08:50 PM, Al Waschka wrote:
HP Pavilion ZE 4220 Laptop
Old.
Celeron processor over 1 GHz
960MB Ram (1G?)
CD Drive
Ethernet and USB
Al,
You could download a "live" image, no installation required.
For your HW this small "rescue-linux" should be ok:
- Select the "grml-small" "32-bit PC" version, currently this one:
- Burn as ISO to a CD and boot the laptop from this CD.
- Then just type "dmesg -Hw" and connect your NanoVNA.
Look at the responses when switching on / off in various modes (jog pressed / not pressed, BOOT0-VDD shorted / open, etc.).
Martin
|
Re: NanoVNA Not Recognized by Laptop over USB After dfu Upgrade
Hope this isn’t considered off topic. It is about troubleshooting a NanoVNA.
Finally got the greml distro working. When I enter the string you suggested it says -H is unrecognized.
toggle quoted message
Show quoted text
On Jan 27, 2023, at 6:07 AM, Ho-Ro <linuxaudio@...> wrote:
?On Fri, Jan 27, 2023 at 01:59 AM, Al Waschka wrote:
I am trying to get my hands on a Liinux device to see how it responds in both
modes to Linux commands
On Thu, Jan 26, 2023 at 08:50 PM, Al Waschka wrote:
HP Pavilion ZE 4220 Laptop
Old.
Celeron processor over 1 GHz
960MB Ram (1G?)
CD Drive
Ethernet and USB
Al,
You could download a "live" image, no installation required.
For your HW this small "rescue-linux" should be ok:
- Select the "grml-small" "32-bit PC" version, currently this one:
- Burn as ISO to a CD and boot the laptop from this CD.
- Then just type "dmesg -Hw" and connect your NanoVNA.
Look at the responses when switching on / off in various modes (jog pressed / not pressed, BOOT0-VDD shorted / open, etc.).
Martin
|
Re: NanoVNA H4 calibration anomaly
You nailed it. I was looking at S11 phase and not S21 phase. Thank you!
John W1FV
|
Re: Updating the firmware on a nanoVNA-H4 with a Mac
On Thu, Jan 26, 2023 at 02:46 PM, Lawrance A. Schneider wrote:
I there a similar usage of the dfu_util command for the nanoVNA - H4?
Lawrence, The dfu_util command works exactly the same for NanoVNA-H and -H4 as for tinaSA and tinySA Ultra. Both families use exactly the same STM32 processor (the small STM32-F072, the larger STM32-F303). Martin
|
Re: NanoVNA Not Recognized by Laptop over USB After dfu Upgrade
On Fri, Jan 27, 2023 at 01:59 AM, Al Waschka wrote:
I am trying to get my hands on a Liinux device to see how it responds in both
modes to Linux commands
On Thu, Jan 26, 2023 at 08:50 PM, Al Waschka wrote:
HP Pavilion ZE 4220 Laptop
Old.
Celeron processor over 1 GHz
960MB Ram (1G?)
CD Drive
Ethernet and USB
Al, You could download a "live" image, no installation required. For your HW this small "rescue-linux" should be ok: - Select the "grml-small" "32-bit PC" version, currently this one: - Burn as ISO to a CD and boot the laptop from this CD. - Then just type "dmesg -Hw" and connect your NanoVNA. Look at the responses when switching on / off in various modes (jog pressed / not pressed, BOOT0-VDD shorted / open, etc.). Martin
|
Re: Very compressed SWR scale #nanovna-h - Murphy
#nanovna-h
Murphy is a ham also…. However he gets on the air and into my set very sporadically. Usually similar to the trouble shooting suggestions in the latest Ham Radio Workbench podcast. Remember to check the obvious. Don’t assume anything. Even PL 259s and Anderson power connectors need exercising every so often to clean off the oxide and other stuff that electrons seem to attract. So opening up a 50 ohm standard on your Nano doesn’t surprise me at all. 62 years in this hobby and still finding Murphy in my shack. All the ham radio license tests should have a Murphy question.
When I had teenagers in the shack I could expect anything but they have been gone for almost 30 years. My XYL of 51 years is afraid to enter the shack, even to clean, for fear she will be infected and waste more time in there since she knows how addicted I am to being there. I tell her my mistress lives in there….. then I duck and cover.
Dave K8WPE since 1960
David J. Wilcox’s iPad
toggle quoted message
Show quoted text
On Jan 26, 2023, at 5:47 PM, Marc VK3OHM <vk3ohm@...> wrote:
?Thank you Owen Duffy for an off list suggestion. Turns out the 50 ohm load had failed open circuit, so it was not calibrated. Replaced the load and now working perfectly. Who'd have thought one of those could fail?
|
Hi Marc,
Just a heads up. It is possible that static on your antenna crisped your NanoVNA.
It is really good practice to short your antenna cable before connecting it to your Nano VNA.
Also be very aware of nearby transmitters, even VHF/UHF ones that could induce high input signals on your HF antenna to the NanoVNA.
A DC block and/or 6/10dB fixed attenuator are also good safety insurance.
73...Bob VK2ZRE
toggle quoted message
Show quoted text
On 27/01/2023 8:15 am, Marc VK3OHM wrote: Thanks for all your assistance - I'm pretty sure my NanoVNA has a serious fault. A new one is on order. I checked the antenna with a SARK 110, and got exactly the result I expected, so that eliminates the antenna and feed as the problem. My NanoVNA is actually not the H model, but the vanilla one. Have upgraded it to what I believe is the latest firmware - v0.8.0. Development of this branch seems to have ceased in 2020, so time for an upgrade anyway. Have bought the latest 4" H model.
|
Re: NanoVNA H4 calibration anomaly
John,
Are you sure that your phase trace is looking at S21 phase and not S11 phase?
--John Gord
toggle quoted message
Show quoted text
On Thu, Jan 26, 2023 at 08:47 PM, John Kaufmann wrote:
I'm running into an issue trying to calibrate my NanoVNA H4 so that I can run
S21 scans. I've done the calibration two ways: (1) using the NanoVNA-saver
software and (2) using the on-screen menu on the VNA itself. The first method
works fine but the second one does not. I don't know why there is this
discrepancy.
Using the on-screen method, I run through the calibration menu procedure:
open, short, load (50 ohms), isolation, and through (using a short SMA jumper
cable between the CH0 and CH1 ports). I happen to be doing this over a
frequency range of 100 kHz to 5 MHz. When I'm done I save the result and
apply the calibration. Next I check the calibration by running an S21 scan,
leaving the jumper cable in place between the CH0 and CH1 ports, If the
calibration has been done correctly, I should see an S21 magnitude of 0 dB and
S21 phase of 0 degrees across the frequency range. I do see 0 dB but the
phase is wildly inaccurate, and varies between 177 degrees at 100 kHz to 141
degrees at 5 MHz.
When I do the same calibration using the NanoVNA-saver software and following
the calibration steps in the software, I get the correct S21 results with the
jumper cable connecting the CH0 and CH1 ports. It shows 0 dB and 0 degrees
phase from 100 kHz to 5 MHz.
If I run an S21 scan of a two-port device like a filter, both the on-screen
and NanoVNA-saver scans produce the same S21 magnitude but not phase. The
phase that's displayed in the on-screen method varies all over the place and
is clearly erroneous.
What am I doing wrong that I cannot get a correct calibration and S21 phase
measurement with the on-screen method?
John W1FV
|
NanoVNA H4 calibration anomaly
I'm running into an issue trying to calibrate my NanoVNA H4 so that I can run S21 scans. I've done the calibration two ways: (1) using the NanoVNA-saver software and (2) using the on-screen menu on the VNA itself. The first method works fine but the second one does not. I don't know why there is this discrepancy.
Using the on-screen method, I run through the calibration menu procedure: open, short, load (50 ohms), isolation, and through (using a short SMA jumper cable between the CH0 and CH1 ports). I happen to be doing this over a frequency range of 100 kHz to 5 MHz. When I'm done I save the result and apply the calibration. Next I check the calibration by running an S21 scan, leaving the jumper cable in place between the CH0 and CH1 ports, If the calibration has been done correctly, I should see an S21 magnitude of 0 dB and S21 phase of 0 degrees across the frequency range. I do see 0 dB but the phase is wildly inaccurate, and varies between 177 degrees at 100 kHz to 141 degrees at 5 MHz.
When I do the same calibration using the NanoVNA-saver software and following the calibration steps in the software, I get the correct S21 results with the jumper cable connecting the CH0 and CH1 ports. It shows 0 dB and 0 degrees phase from 100 kHz to 5 MHz.
If I run an S21 scan of a two-port device like a filter, both the on-screen and NanoVNA-saver scans produce the same S21 magnitude but not phase. The phase that's displayed in the on-screen method varies all over the place and is clearly erroneous.
What am I doing wrong that I cannot get a correct calibration and S21 phase measurement with the on-screen method?
John W1FV
|
The standards by their nature are delicate, as the manufacturer attempts to minimize parasitic capacitance/inductance. This often results in mechanically less-than-robust construction.
This mechanical weakness is exacerbated by the fact that many inexpensive standards do not have a place to hold the standard from rotating when mating/demating the connectors; the resulting rotation of the standard can unscrew a threaded center pin, or worse, extend it out so that it damages another connector. Metrology grade calibration kits include gages to ensure that the connector pins are properly positioned and connectors are gaged before beginning a calibration.
"Turn the nut, do not turn the connector body" is the mantra.
A useful habit to develop before calibration is to watch the screen as you connect each standard in turn, to ensure that the expected, or at least different, response is obtained. This will help to pick up gross problems with the cal standards. Another is to closely examine the mating surfaces of the standards for bent, distorted or missing pins or damaged outer conductors. I have even found a male pin which someone left in a female standard.
73, Don N2VGU
|
Re: NanoVNA Not Recognized by Laptop over USB After dfu Upgrade
Thanks,
The question is which statement in the manufacturer's brochure is incorrect. But the "other cable" is the one that came with the NanoVNA and it worked a few minutes prior to the point at which it didn't work.
I have a ISB-A to USB-C adapter I bought yesterday, and a USB-A Male to Male cable coming tomorrow. That setup will implement a USB-A to USB-C cable that whould work. If it does then we will know the problem was the cable. I suspect it will not.
|
Re: NanoVNA Not Recognized by Laptop over USB After dfu Upgrade
Hi,
In point 8 you say that the new cable is identified as a "charging cable" and this type of cable is only for charging but not for data transfer. After that you say that in the description they say that you can transfer data while charging, so this is not what a "charging cable does", this description applies to a "normal" cable.? I would check both cables with a phone for transferring files or images between the phone and a PC. It they work the cables are OK.
Regards,
Ignacio
toggle quoted message
Show quoted text
El 27/01/2023 a las 1:59, Al Waschka escribió: Chronology of the Problem
1. Unpacked NanoVNA ordered from eBay vendor as a non-H unit, powered up and operated, including calibration, configuration, and testing an existing antenna system until the display started to dim. VERSION identified the dfu as NanoVNA-H Version 1;1 Build Time Dec 21 2021
2. Plugged the unit into a powered USB hub to charge the battery. The laptop powered up but not active.
3. After charging, played with it some more, including trying to install and operate VNA Saver on a laptop, with no success. The device would be detected by the laptop as an “Unidentified Device” and would not allow me to update the driver to the STM USB CommPort driver in the 32102(?) zip file. As a result, I decided to change the firmware load. I picked a load identified as nanoVNA_800_ch_20190920.dfu and after calibrating and configuring it realized it was substantially less capable than the original load. I decided to replace the dfu with another.
4. I went through the documented process for installing DfuSe demo on my laptop. When I tried to complete the verify drivers step, I found that the laptop was reporting “STM Bootloader” as the device, instead of the correct “STM Device in DFU Mode”. After several iterations I found that it might be necessary to manually install the proper driver. When I did that the proper designation appeared and I installed nanoVNA_800_ch：50K-900MHz dfu.
5. Immediately on started the new firmware I noticed the lack of features. There was no CONFIG menu. The list of parameters available for display in the FORMATS menu significantly less than in the original version and lacked the R and X values that I am particularly interested in. I decided to change back to the original version and immediately noticed there was no DFU option in the menus. After some research I discovered that pressing the jogwheel down while powering the device up might put in in DFU mode. When I did that, I got a white screen which is allegedly indicative of being in DFU mode.
6. When I connected the device to the laptop used to load the new firmware onto the device the computer did not react at all. When I went into device manager, I expected to see the “STM Device in DFU Mode” identified but it wasn’t there. Neither was the “STM Bootloader”.
7. When I posted these facts on Groups.io several members responded with suggestions including that the cable might be bad, or something changed in the computer.
8. I purchased and tried a new cable without success. The new cable came from the phone section and was identified as a charging cable, but the description said you could transfer data while charging. I tried the device on another computer with both cables with no success. Even on the new computer which did not have the DFU mode driver there was no indication of the “STM Bootloader”.
9. At various points during this process while testing DFU mode I would try powering on with the Vcc to Boot0 jumper in place, which also produced the white screen response but didn’t change the way the device enumerated on the laptop, i.e it didn’t show up in device manager.
10. Also at various points in the process I tried to update the driver with the device on normal operating mode, but was never able to successfully install the Com Port driver.
11. I am pursuing two paths to identify the guilty party, i.e. the device or the computer. I am trying to get my hands on a Liinux device to see how it responds in both modes to Linux commands and trying to locate an Android device capable of loading the NanaVNA app.
12. More as it happens……
--
Este correo electrónico ha sido analizado en busca de virus por el software antivirus de Avast.
www.avast.com
|
hah, and I just sent a suggestion - yeah, it happens. And to someone with your callsign, how ironic.
I've had more than one 50 ohm load turn into an open - or what's worse, 50 ohms at high frequencies, but open at low - a break, with sufficient capacitance that at some GHz, the capacitive impedance was negligible - so it was a fine S band load.
If you have a spare 3-10 dB pad around, that's a handy thing to use as a cross check, too.
|
If you clear the calibration (reset), so it's totally uncalibrated, what does it show? It should show S11 fairly low with a load, and close to zero with either open or short. If it does, then check your calibration standards. It's not unheard of for shorts or loads to change - I have a load that decided to become an open one day, close to 50 ohms, then it wasn't the next day. Who knows what happened (probably some sort of tiny crack that developed and finally went open).
Also check your frequency range. Set it to something "moderate" like 1-100 MHz
|
Re: NanoVNA Not Recognized by Laptop over USB After dfu Upgrade
Chronology of the Problem
1. Unpacked NanoVNA ordered from eBay vendor as a non-H unit, powered up and operated, including calibration, configuration, and testing an existing antenna system until the display started to dim. VERSION identified the dfu as NanoVNA-H Version 1;1 Build Time Dec 21 2021
2. Plugged the unit into a powered USB hub to charge the battery. The laptop powered up but not active.
3. After charging, played with it some more, including trying to install and operate VNA Saver on a laptop, with no success. The device would be detected by the laptop as an “Unidentified Device” and would not allow me to update the driver to the STM USB CommPort driver in the 32102(?) zip file. As a result, I decided to change the firmware load. I picked a load identified as nanoVNA_800_ch_20190920.dfu and after calibrating and configuring it realized it was substantially less capable than the original load. I decided to replace the dfu with another.
4. I went through the documented process for installing DfuSe demo on my laptop. When I tried to complete the verify drivers step, I found that the laptop was reporting “STM Bootloader” as the device, instead of the correct “STM Device in DFU Mode”. After several iterations I found that it might be necessary to manually install the proper driver. When I did that the proper designation appeared and I installed nanoVNA_800_ch：50K-900MHz dfu.
5. Immediately on started the new firmware I noticed the lack of features. There was no CONFIG menu. The list of parameters available for display in the FORMATS menu significantly less than in the original version and lacked the R and X values that I am particularly interested in. I decided to change back to the original version and immediately noticed there was no DFU option in the menus. After some research I discovered that pressing the jogwheel down while powering the device up might put in in DFU mode. When I did that, I got a white screen which is allegedly indicative of being in DFU mode.
6. When I connected the device to the laptop used to load the new firmware onto the device the computer did not react at all. When I went into device manager, I expected to see the “STM Device in DFU Mode” identified but it wasn’t there. Neither was the “STM Bootloader”.
7. When I posted these facts on Groups.io several members responded with suggestions including that the cable might be bad, or something changed in the computer.
8. I purchased and tried a new cable without success. The new cable came from the phone section and was identified as a charging cable, but the description said you could transfer data while charging. I tried the device on another computer with both cables with no success. Even on the new computer which did not have the DFU mode driver there was no indication of the “STM Bootloader”.
9. At various points during this process while testing DFU mode I would try powering on with the Vcc to Boot0 jumper in place, which also produced the white screen response but didn’t change the way the device enumerated on the laptop, i.e it didn’t show up in device manager.
10. Also at various points in the process I tried to update the driver with the device on normal operating mode, but was never able to successfully install the Com Port driver.
11. I am pursuing two paths to identify the guilty party, i.e. the device or the computer. I am trying to get my hands on a Liinux device to see how it responds in both modes to Linux commands and trying to locate an Android device capable of loading the NanaVNA app.
12. More as it happens……
|
I would think that someone with a call like yours would have checked the load first! (Just kidding!)
toggle quoted message
Show quoted text
On Jan 26, 2023, at 2:47 PM, Marc VK3OHM <vk3ohm@...> wrote:
?Thank you Owen Duffy for an off list suggestion. Turns out the 50 ohm load had failed open circuit, so it was not calibrated. Replaced the load and now working perfectly. Who'd have thought one of those could fail?
|
Ho-Ro
David Wilcox K8WPE
Donald S Brant Jr