开云体育

I'm in the weeds reading this but what I do to verify a "working"
battery is: charge it up and then put a calculated load across it while
monitoring the battery health. i.e. choose a fixed load like 100ma and
see what happens, yeah, you do the math.

Mike C. Sand Mtn GA

Yes, if yours it is a 2.8" NanoVNA-H, i have replace the LCD screen with a 3.2" version. This is described eirlier in the Files section. It was the only version that has fit on the 40p? flatcable.

VCC is 4.9 volts, but VDD starts out at about 2 volts when I turn it on and
then drops below 1.7. Is U11 the likely culprit? I guess I could order one
and find out how good my surface mount soldering skills are.

Jim

On Fri, Oct 25, 2024 at 11:07?AM Stan Dye via groups.io <standye=
[email protected]> wrote:

It sounds like you may have a component failing on the board, probably in
the power supply circuits. I would say to check the electrolytic
capacitors, since a failing cap could cause this behavior, but looking at
the schematic, it doesn't seem to have any. There are a few 10uF caps that
may be worth checking. Other than that, may need to probe with an
oscilloscope or meter and see what is happening when it fails.
Since more commonly, failures are mechanical, I would also clean and
re-seat all connectors, and see if any of them made a difference.
Schematic:


And BTW, your original post, and your repeat of it here has an error: you
say you reflashed with later firmware, but you gave the same old date code
for the new firmware, so we have no idea what firmware you loaded. And
most on this list know firmware by its version number rather than build
date code. But that is probably not relevant, if the unit is suddenly
powering down in DFU mode. The DFU mode bootloader is in ROM on the STM32
microprocessor, you can't brick it with a firmware download - so if it is
spontaneously powering off in DFU mode, it must be something in the
hardware.

Good luck, Stan

Thanks all for your advices and valuable guidance , very informative .

Please did NANO-VNA H4 V4.3 has an STM32F407 microcontroler inside or STM32F10X ??

Did NANO-VNA H4 V4.3 has a reliable touchscreen function as it should or it's vary bugy ??

indeed i Have a NAno-VNA F , it run OK except very bugy touchscreen function especially when working over the menu, very desappointed and i would like to try this time an other Nano-VNA H4 V4.3 wich has approximatly the same features but no idea about it's touchscreen function reliability ?

if any known commun bugs still not resolved with Nano-VNA H4 V4.3 ??

Thanks
73's Nizar

First, which NanoVNA are you asking about?
There are several different designs of the NanoVNA. Each may differ in hardware designs, that may require a specific display driver components as well as voltages.

One person did add a 3 inch screen to their NanoVNA H directly. However they did not mention any changes to the case or battery. Also the screen was compatible with the screen drivers used in the H. You will have to surch past posts for his info.

The screen in the H is soldered directly to the pcb. The H4 screen is connected to the pcb by a connector.
I am not sure how the screens on other NanoVNA's like the F or S2 or other designs are assembled.

There are other considerations like the case and battery required for a larger display.

I use my Samsung S24 Ultra phone or Samsung 10 inch Tablet if I need a larger screen than my H4, or to update the FW.
Yes there are Android apps to use for the NanoVNA's, for operation or FW updates.

The other way is to buy a NanoVNA with a larger screen to begin with.

Good luck with your endeavors.
73's
Clyde KC7BJE

Good Morning.

I find that tethering the nanovna to a computer or notebook works quite
well when used with either nanovna-saver or the RigExpert app called
"AntScope2" which is available free (Windows, Linux and MacOS) on the
RigExpert website.

Best Regards,

On Fri, Oct 25, 2024 at 8:29?AM W8NSI James via groups.io <w8nsi=
[email protected]> wrote:

Has anyone opened a nanovna to see if it has header plug-in pins to the
screen?
Can a larger screen be swapped on to one with a tiny screen?
Otherwise I must use a magnifier to read it.
I did a search using various terms and did not find this type of query.

--
73 de W8NSI Jim
New NanoVNA User, please be patient.
75 YO and eyesight not what used to be.
I build my own antennas and need this.

--
Michael L Robinson, KC0TA

FREEDOM is NEVER given; It Is WON!

“In the beginning of a change the Patriot is a scarce man, and brave, and
hated and scorned. When his cause succeeds, the timid join him, for then it
costs nothing to be a Patriot.” ― Mark Twain

When Tyranny becomes Law, Revolution becomes Duty!

On Fri, Oct 25, 2024 at 06:29 AM, W8NSI James wrote:

Has anyone opened a nanovna to see if it has header plug-in pins to the
screen?
Can a larger screen be swapped on to one with a tiny screen?

You can't just swap in a larger screen because it will not be pin compatible. If you own a 2.8" you could buy a 4" model which is much easier to read.

Or you can connect it to your PC using NanoVNA Saver, NanoVNA App or one of the older PC programs. That way you have a large monitor and you can do very nice graphs and easily save your work.

Roger

It sounds like you may have a component failing on the board, probably in the power supply circuits. I would say to check the electrolytic capacitors, since a failing cap could cause this behavior, but looking at the schematic, it doesn't seem to have any. There are a few 10uF caps that may be worth checking. Other than that, may need to probe with an oscilloscope or meter and see what is happening when it fails.
Since more commonly, failures are mechanical, I would also clean and re-seat all connectors, and see if any of them made a difference.
Schematic:

And BTW, your original post, and your repeat of it here has an error: you say you reflashed with later firmware, but you gave the same old date code for the new firmware, so we have no idea what firmware you loaded. And most on this list know firmware by its version number rather than build date code. But that is probably not relevant, if the unit is suddenly powering down in DFU mode. The DFU mode bootloader is in ROM on the STM32 microprocessor, you can't brick it with a firmware download - so if it is spontaneously powering off in DFU mode, it must be something in the hardware.

Good luck, Stan

Has anyone opened a nanovna to see if it has header plug-in pins to the screen?
Can a larger screen be swapped on to one with a tiny screen?
Otherwise I must use a magnifier to read it.
I did a search using various terms and did not find this type of query.

--
73 de W8NSI Jim
New NanoVNA User, please be patient.
75 YO and eyesight not what used to be.
I build my own antennas and need this.

On Fri, Oct 25, 2024 at 2:16 AM Roger Need via groups.io <sailtamarack=
[email protected]> wrote:

Take the battery out and run it on USB power.

I’ve already done that. It makes no difference. I doubt the battery is the
problem because it behaves exactly the same way with or without the battery
connected.

I'm looking for suggestions of other things to try. Thanks.

Here’s my original message, which describes what it’s doing and what I’ve
tried:

I've used my NanoVNA-H4 periodically for several years. Yesterday I charged
it, then upgraded the firmware from NanoVNA-H4-SI_20211230 to
NanoVNA-H4-SI_20211230. I re-calibrated and started doing some testing with
it apparently working fine. I got distracted for a few minutes, and when I
checked the screen was black. I powered it off, then back on, but the
display only appeared for a second, then went black.


Since then when I turn it on I see a normal display for approximately one
second, then it apparently shuts off.


Things I've tried, none of which have made any difference:
* Charging it, including overnight.
* Powering it on while plugged into a charger or USB port.
* Disconnecting the battery for a while, then reconnecting it.
* Powering it from USB with the battery disconnected.


I wanted to try re-flashing old firmware, but it appears to do the same
thing in DFU mode. When I power it on while holding the multifunction
switch, I see the following in dmesg on Linux, and dfu-util doesn't see it:


[385834.014786] usb 1-3.4: new full-speed USB device number 39 using
xhci_hcd
[385834.104077] usb 1-3.4: New USB device found, idVendor=0483,
idProduct=df11, bcdDevice=22.00
[385834.104090] usb 1-3.4: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[385834.104096] usb 1-3.4: Product: STM32 BOOTLOADER
[385834.104101] usb 1-3.4: Manufacturer: STMicroelectronics
[385834.104105] usb 1-3.4: SerialNumber: 205E33642031
[385835.056995] usb 1-3.4: USB disconnect, device number 39


Any suggestions of other things to try?

Roger

Take the battery out and run it on USB power.

Roger

It could measure 4.1V but have high internal resistance. That would cause it to fail under load. I take it that the SA runs OK on USB power?

On Thu, 24 Oct 2024 22:43:17 -0400
"Jim Ancona N1ADJ via groups.io" <jim@...> wrote:

Currently mine runs for one second after I turn it on. Given that the
battery measures 4.1 volts, do you still think it's a battery issue?

Jim

On Thu, Oct 24, 2024 at 10:34?PM Jim Shorney via groups.io <jimNU0C=
[email protected]> wrote:

Start from a fresh charge and see how long it takes to run the battery
down and turn off. "Runtime test" is easier to type. :)

Recharge it immediately when done.

On Thu, 24 Oct 2024 22:27:17 -0400
"Jim Ancona N1ADJ via groups.io" <jim@...> wrote:

What do you mean by a runtime test? I tried searching but didn't come up
with anything.

--

73

-Jim
NU0C

--

73

-Jim
NU0C

Currently mine runs for one second after I turn it on. Given that the
battery measures 4.1 volts, do you still think it's a battery issue?

Jim

On Thu, Oct 24, 2024 at 10:34?PM Jim Shorney via groups.io <jimNU0C=
[email protected]> wrote:

Start from a fresh charge and see how long it takes to run the battery
down and turn off. "Runtime test" is easier to type. :)

Recharge it immediately when done.

On Thu, 24 Oct 2024 22:27:17 -0400
"Jim Ancona N1ADJ via groups.io" <jim@...> wrote:

What do you mean by a runtime test? I tried searching but didn't come up
with anything.

--

73

-Jim
NU0C

Start from a fresh charge and see how long it takes to run the battery down and turn off. "Runtime test" is easier to type. :)

Recharge it immediately when done.

On Thu, 24 Oct 2024 22:27:17 -0400
"Jim Ancona N1ADJ via groups.io" <jim@...> wrote:

What do you mean by a runtime test? I tried searching but didn't come up
with anything.

--

73

-Jim
NU0C

On Thu, Oct 24, 2024 at 10:05?PM Jim Shorney via groups.io <jimNU0C=
[email protected]> wrote:

I would say do a runtime test on it. That will tell you one way or the
other. But do remember to maintenance charge it if you don't use it for a
long period of time.

What do you mean by a runtime test? I tried searching but didn't come up
with anything.

Thanks,

Jim

It could also be crud in the power switch. My TinySA was a victim of that.
It was highly intermittent. I opened it tonight and after unplugging the
battery I vigorously exercised the switch a couple of dozen times. That
helped. If the problem comes back I will hit it with some CRC cleaner and
maybe DeOxit Gold.


On Thu, 24 Oct 2024 21:39:07 -0400
"Jim Ancona N1ADJ via groups.io" <jim@...> wrote:

I like the battery theory, but I measure 4.1 volts across the battery
terminals with the unit turned on (battery is marked 3.7v) and the device
behaves exactly the same way when plugged into the charger with the

battery

disconnected. Neither of those seems consistent with the battery being

the

problem.

--

73

-Jim
NU0C

I would say do a runtime test on it. That will tell you one way or the other. But do remember to maintenance charge it if you don't use it for a long period of time.

It could also be crud in the power switch. My TinySA was a victim of that. It was highly intermittent. I opened it tonight and after unplugging the battery I vigorously exercised the switch a couple of dozen times. That helped. If the problem comes back I will hit it with some CRC cleaner and maybe DeOxit Gold.


On Thu, 24 Oct 2024 21:39:07 -0400
"Jim Ancona N1ADJ via groups.io" <jim@...> wrote:

I like the battery theory, but I measure 4.1 volts across the battery
terminals with the unit turned on (battery is marked 3.7v) and the device
behaves exactly the same way when plugged into the charger with the battery
disconnected. Neither of those seems consistent with the battery being the
problem.

--

73

-Jim
NU0C

I like the battery theory, but I measure 4.1 volts across the battery
terminals with the unit turned on (battery is marked 3.7v) and the device
behaves exactly the same way when plugged into the charger with the battery
disconnected. Neither of those seems consistent with the battery being the
problem.

Jim

On Thu, Oct 24, 2024 at 9:26?PM Jim Shorney via groups.io <jimNU0C=
[email protected]> wrote:

You battery is likely bad. Lithium based batteries do not like to be deep
discharged. It will kill them. The VNAs have a very small but finite
current drain when powered off and need to be occasionally maintenance
charged if not used for long periods.

On Thu, 24 Oct 2024 07:21:02 -0700
"Jim Ancona N1ADJ via groups.io" <jim@...> wrote:

I've used my NanoVNA-H4 periodically for several years. Yesterday I

charged it, then upgraded the firmware from NanoVNA-H4-SI_20211230 to
NanoVNA-H4-SI_20211230. I re-calibrated and started doing some testing with
it apparently working fine. I got distracted for a few minutes, and when I
checked the screen was black. I powered it off, then back on, but the
display only appeared for a second, then went black.


--

73

-Jim
NU0C

You battery is likely bad. Lithium based batteries do not like to be deep discharged. It will kill them. The VNAs have a very small but finite current drain when powered off and need to be occasionally maintenance charged if not used for long periods.

On Thu, 24 Oct 2024 07:21:02 -0700
"Jim Ancona N1ADJ via groups.io" <jim@...> wrote:

I've used my NanoVNA-H4 periodically for several years. Yesterday I charged it, then upgraded the firmware from NanoVNA-H4-SI_20211230 to NanoVNA-H4-SI_20211230. I re-calibrated and started doing some testing with it apparently working fine. I got distracted for a few minutes, and when I checked the screen was black. I powered it off, then back on, but the display only appeared for a second, then went black.

--

73

-Jim
NU0C

That acts exactly the way I would expect a failed battery to behave, esp. since DFU mode does not eun anything that you flashed . . . Somewhat odd that it won't stay on if plugged in, but the charge circuitry may not provide enough to overcome a failed cell.

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

I've used my NanoVNA-H4 periodically for several years. Yesterday I charged it, then upgraded the firmware from NanoVNA-H4-SI_20211230 to NanoVNA-H4-SI_20211230. I re-calibrated and started doing some testing with it apparently working fine. I got distracted for a few minutes, and when I checked the screen was black. I powered it off, then back on, but the display only appeared for a second, then went black.

Since then when I turn it on I see a normal display for approximately one second, then it apparently shuts off.

Things I've tried, none of which have made any difference:
* Charging it, including overnight.
* Powering it on while plugged into a charger or USB port.
* Disconnecting the battery for a while, then reconnecting it.
* Powering it from USB with the battery disconnected.

I wanted to try re-flashing old firmware, but it appears to do the same thing in DFU mode. When I power it on while holding the multifunction switch, I see the following in dmesg on Linux, and dfu-util doesn't see it:

[385834.014786] usb 1-3.4: new full-speed USB device number 39 using xhci_hcd
[385834.104077] usb 1-3.4: New USB device found, idVendor=0483, idProduct=df11, bcdDevice=22.00
[385834.104090] usb 1-3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[385834.104096] usb 1-3.4: Product: STM32 BOOTLOADER
[385834.104101] usb 1-3.4: Manufacturer: STMicroelectronics
[385834.104105] usb 1-3.4: SerialNumber: 205E33642031
[385835.056995] usb 1-3.4: USB disconnect, device number 39

Any suggestions of other things to try?

Thanks,

Jim