¿ªÔÆÌåÓý

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

Re: LNA Design Using S Parameters

 

Several replies and spoken for. Perhaps the document can be scanned to share by the recipient. I do not have a scanner.
Thanks,


Re: Android NanoVNA app

 

Changed a few known working cables, but no luck.

Frustrating!

Chris VK5SA


Re: LNA Design Using S Parameters

 

Hi Frank. No, neither. Not an EB or an APP note. I will email you direct.


Re: "Bricked" after attempt to update FW #nanovna-v2 #firmware #crash #newbie #flashing

 

I feel your pain.. I had a similar occurrence with an alleged NanoVNA from an apparently Chinese vendor but shipped from stock in US. Although it was sold as a NanoVNA it was delivered with a NanoVNA-H firmware load that may have been modified. It could not be recognized in analyzer mode and registered as an unrecognized device. I was unable to get the driver updated.. So I figured I'd try a different fw load. IT was recognized in DFU mode and uploaded the fw but then I could not get the computer to recognize it in DFU mode. There was no DFU mode in the menu any more. I tried putting it in DFU mode by holding down the jogwheel when powering it up and also by using the jumper when powering it up. In both cases it gave the white screen indication of being in DFU mode but the computer would not even realize that it had been plugged in. To top it off the analyzer was messed up, showing SWR dips at the wrong frequency, as compared to the meter on my transceiver. I tried it on two computers with three different cables, all with the same result. Buyer beware - be sure you know what your hardware is before loading a new fw. I have also read that you need to run a command to clear the device prior to loading fw, but I don't know if that is necessary or even desirable.


Re: LNA Design Using S Parameters

Frank Sweeney
 

Hi AlanWas that is the RF Data Book? Do you have an AN number or EB number.? If neither, I would like a copy
Fxsweeney@...?
Tks and 73,Frank K9IC
On Sat, Jan 28, 2023 at 2:02 PM, alan victor<avictor73@...> wrote: A 100 + page text with examples and data. Not available on the net.
From a Motorola Design Course,? semiconductor division.

Interested, contact me off line.

73' Alan


Re: "Bricked" after attempt to update FW #nanovna-v2 #firmware #crash #newbie #flashing

 

is it an stm32 or a gd32???

dg9bfc sigi

Am 28.01.2023 um 17:18 schrieb Ray WW0AW via groups.io:

Good morning to all you good folks on this forum;

I bought it on Aliexpress and it's dubbed
"S-A-A V2 Pro 4 inch GS-400"
Worked fine for a number of years.
Foolishly attempted to update FW to try to get 401 points...
Bang crash !!! - White screen of death - "USB not recognized" (Device Manager)
Broke out my trusty STLINK V2 dongle, identified SWDIO, SWCLK etc on the device and tried to reflash a new bootloader
(using STM32 Cube Programmer , which does successfully identify the MCU - so it;s not "dead".)
All attempts have failed - tried every bootloader under the sun - "USB not recognized" every single time

STM32 Cube programmer can successfully flash the .bin files into the MCU but somehow the MCU doesn't respond appropiately.
Tried to blink PA6, PA7 LEDs ( there are some empty pads on the PCB) without success (Several Blue pill's PC13 on the other hand respond perfectly)
It's not the USB cable - tried several ones known to work fine on other devices.
I'm stumped. Any help ?




Re: LNA Design Using S Parameters

 

No problem. I found you on QRZ.com.


Re: "Bricked" after attempt to update FW #nanovna-v2 #firmware #crash #newbie #flashing

 

and some use gs32 intead the stm32 ... and some use a different screen (2.8 and 4 inch on the morket not counting in one unit that comes with? fat 7 inch display)

and you will find units with an open fw or units with a special bootloader and a heavy different fw

all need a "modded" fw to match the used hw

so at first you have to know what fw you need for your device ... may it be a clone, cousin, sister or brother or a genuine unit

(are they not all clones?!? no flamethrowings pease)

dg9bfc sigi

Am 28.01.2023 um 21:10 schrieb John Simons:

Be aware that there are Chinese clones of the STM32 that may have subtle
bugs in their implementations. It might just be trashed.

-John

Op za 28 jan. 2023 om 20:44 schreef Ray WW0AW via groups.io <hrpch=
[email protected]>:

Good morning to all you good folks on this forum;

I bought it on Aliexpress and it's dubbed
"S-A-A V2 Pro 4 inch GS-400"
Worked fine for a number of years.
Foolishly attempted to update FW to try to get 401 points...
Bang crash !!! - White screen of death - "USB not recognized" (Device
Manager)
Broke out my trusty STLINK V2 dongle, identified SWDIO, SWCLK etc on the
device and tried to reflash a new bootloader
(using STM32 Cube Programmer , which does successfully identify the MCU -
so it;s not "dead".)
All attempts have failed - tried every bootloader under the sun - "USB not
recognized" every single time

STM32 Cube programmer can successfully flash the .bin files into the MCU
but somehow the MCU doesn't respond appropiately.
Tried to blink PA6, PA7 LEDs ( there are some empty pads on the PCB)
without success (Several Blue pill's PC13 on the other hand respond
perfectly)
It's not the USB cable - tried several ones known to work fine on other
devices.
I'm stumped. Any help ?







Re: "Bricked" after attempt to update FW #nanovna-v2 #firmware #crash #newbie #flashing

 

Be aware that there are Chinese clones of the STM32 that may have subtle
bugs in their implementations. It might just be trashed.

-John

Op za 28 jan. 2023 om 20:44 schreef Ray WW0AW via groups.io <hrpch=
[email protected]>:

Good morning to all you good folks on this forum;

I bought it on Aliexpress and it's dubbed
"S-A-A V2 Pro 4 inch GS-400"
Worked fine for a number of years.
Foolishly attempted to update FW to try to get 401 points...
Bang crash !!! - White screen of death - "USB not recognized" (Device
Manager)
Broke out my trusty STLINK V2 dongle, identified SWDIO, SWCLK etc on the
device and tried to reflash a new bootloader
(using STM32 Cube Programmer , which does successfully identify the MCU -
so it;s not "dead".)
All attempts have failed - tried every bootloader under the sun - "USB not
recognized" every single time

STM32 Cube programmer can successfully flash the .bin files into the MCU
but somehow the MCU doesn't respond appropiately.
Tried to blink PA6, PA7 LEDs ( there are some empty pads on the PCB)
without success (Several Blue pill's PC13 on the other hand respond
perfectly)
It's not the USB cable - tried several ones known to work fine on other
devices.
I'm stumped. Any help ?






Re: LNA Design Using S Parameters

 

Hi Alan,

I am interested. I do not know how to contact you off line, therefore my answer here.

Kind regards

Matthias

www.dd1us.de


-----Urspr¨¹ngliche Nachricht-----
Von: [email protected] <[email protected]> Im Auftrag von alan victor via groups.io
Gesendet: Samstag, 28. Januar 2023 20:02
An: [email protected]
Betreff: [nanovna-users] LNA Design Using S Parameters

A 100 + page text with examples and data. Not available on the net.
From a Motorola Design Course, semiconductor division.

Interested, contact me off line.

73' Alan


Ray WW0AW
 

Good morning to all you good folks on this forum;

I bought it on Aliexpress and it's dubbed
"S-A-A V2 Pro 4 inch GS-400"
Worked fine for a number of years.
Foolishly attempted to update FW to try to get 401 points...
Bang crash !!! - White screen of death - "USB not recognized" (Device Manager)
Broke out my trusty STLINK V2 dongle, identified SWDIO, SWCLK etc on the device and tried to reflash a new bootloader
(using STM32 Cube Programmer , which does successfully identify the MCU - so it;s not "dead".)
All attempts have failed - tried every bootloader under the sun - "USB not recognized" every single time

STM32 Cube programmer can successfully flash the .bin files into the MCU but somehow the MCU doesn't respond appropiately.
Tried to blink PA6, PA7 LEDs ( there are some empty pads on the PCB) without success (Several Blue pill's PC13 on the other hand respond perfectly)
It's not the USB cable - tried several ones known to work fine on other devices.
I'm stumped. Any help ?


LNA Design Using S Parameters

 

A 100 + page text with examples and data. Not available on the net.
From a Motorola Design Course, semiconductor division.

Interested, contact me off line.

73' Alan


Re: NanoVNA Not Recognized by Laptop over USB After dfu Upgrade

 

Found one for $8 refurbished and guaranteed for 30 days.


Re: NanoVNA Not Recognized by Laptop over USB After dfu Upgrade

 

Thanks Jim,

IT is a combination DVD-CD drive. According to my Service Manual it is HP part number F4640-60937
319422-001.

Al


Re: NanoVNA Not Recognized by Laptop over USB After dfu Upgrade

 

I have a box full of NOS laptop DVD drives if you need one. Mostly SATA but a few PATA as well.

73

-Jim
NU0C

On Sat, 28 Jan 2023 09:31:02 -0800
"Al Waschka" <awaschka@...> wrote:

Good to know that it should have worked. I had several of these laptops. I think I cleaned the drives and tossed the others but if I can find one or a replacement CD drive, I will see what happens when I load the .iso.


Re: NanoVNA Not Recognized by Laptop over USB After dfu Upgrade

 

Thanks Martin, for the update, and your attempt to help this NanoVNA noob.

I did not watch the full boot sequence. When I tried to load Greml again after trying to load a Debian live distro that wouldn't load, it listed failures, but it stopped and never completed the startup.

When Greml first loads, there is a menu there. Which option did you load? Down arrow to select the few highlighted options did not worlk for me. Perhaps I should have taken that bit of information as indication of a load problem.

Good to know that it should have worked. I had several of these laptops. I think I cleaned the drives and tossed the others but if I can find one or a replacement CD drive, I will see what happens when I load the .iso.


Re: NanoVNA Not Recognized by Laptop over USB After dfu Upgrade

 

Sometimes I question my sanity - this thread is such an example. Before I recommended grml, I picked up my grml32-small CD and booted my laptop; typed "dmesg -Hw" and plugged in the NanoVNA-H, switched it on and off, with and without jog switch - great display, just as expected. But then this message

On Fri, Jan 27, 2023 at 11:59 PM, Al Waschka wrote:


When I enter the string you suggested it says -H is unrecognized.
and later:

Distro is very limited. Doesn't have -w either. I give up on Linux.
What have I done wrong? I always have this rescue CD with me and also use it when a PC in the family stops working (with the description: "I didn't do anything") - ok, the grml version is older, approx. 2020. Crap, did the makers " castrate" the programs to save space? So I downloaded the latest version grml32-small-2022.11, (just like Al); took an old lab laptop, booted it - typed in "dmesg -Hw" - perfect - detected all USB actions etc.

Even if it is no longer helpful for Al - maybe it will help someone else who really wants help.

In short - if you distrust your Windows, boot a Linux live system (only boot from CD, don't install anything) and explore the HW with the numerous tools - especially for NanoVNA and tinySA:
Watch system messages in real time: dmesg -Hw
What's going on at the USB: lsusb

Martin


Re: Very compressed SWR scale #nanovna-h

 

Not to be captain obvious, but on your nanovna calibration, did you reset cal first and click done when finished?
I easily forgot and made this mistake early on and got weird results.

Bryan , N0LUF


Re: NanoVNA Not Recognized by Laptop over USB After dfu Upgrade

 

I thought I might be able to see something in dmesg, as it worked before when I finally got grml-small loaded after several tries. Unfortunately I tried to load a better Linux distro but the CDROM drive was acting up. When I tried to reload greml-small again it wouldn't finish the install without errors.

The unit is packed and going to the PO tomorrow. I ordered a -H4 from R&L. Looking forward to using it.

Thanks to everyone who tried to help.

Al K5TAN

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Tim Dawson
Sent: Saturday, January 28, 2023 2:09 AM
To: [email protected]
Subject: Re: [nanovna-users] NanoVNA Not Recognized by Laptop over USB After dfu Upgrade

You can run "dmesg" alone and see what you see, then plug in and run it again, and if it saw the device, it will be at the end of the display, past what you saw the first time.

On January 28, 2023 12:26:07 AM CST, Al Waschka <awaschka@...> wrote:
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


-----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.










--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


Re: NanoVNA Not Recognized by Laptop over USB After dfu Upgrade

 

Also "lsusb" can give a hint if the device was recognized.