开云体育

A number of forum members run their NanoVNA on Mac computers.?Please do some searching around the message topics and you will find a number of threads on this and the issues you might see.?
... Larry



On Tue, 19 Nov 2019 at 5:34 PM, vk6eh@...<vk6eh@...> wrote: hi all, forgive me if I missed any previous post on this subject.
Is it possible to run a nanoVNA on a MacBook, any problems, how to, s/ware etc ?

thanks
Wayne VK6EH

Hallo Karsten,

Ja, if I read you correct, I 100% agree.

Vy 73 de Andy

I was unable to locate a source that mentioned "hugen." Thank you from Mike, K0JTA

The 'H' on a NanoVNA-H supposedly means it is a Hugen device. Is there anything keeping the cloners from labeling their devices as -H ?

To the question "Trickle charge current is also mentioned on the spec sheet as being 100ma, not enough to kill a 400ma cell."

If you read the datasheet fully, you find this lines:

#Low Battery voltage VBAT When Battery voltage lower than VBAT ，the Boost will be shutdown 2.78 2.85 2.92 V
So in between 2.78 and 2.92V (tolerances) the device will stop operating)

#Trickle charge current ITRKL VIN=5V，BAT=2.7V 100 mA
#Trickle charge stop voltage VTRKL 3 V

In between 2.7V and 3V (i assume +/- tolerances) the device will Trickle Charge with lower current not to stress the battery at low charge.
So it is not charge keeping tricke charge, but stress reduction .
I assume (not written in datasheet) that below 2.7V of the battery no charging will start (under voltage shut off to prevent safety risk). There is the risk of a burning LiPo battery if a undervoltage battery is charged again. So leaving the device for a long time with 50?A discharge will destroy the battery.

#Target charge voltage VTRGT 4.2 V
#Recharge threshold VRCH 4.1 V
Charging is done up to 4.2V (switch off) and charging starts again with 4.1V (restart)

vy73 de Karsten, DD1KT

hi all, forgive me if I missed any previous post on this subject.
Is it possible to run a nanoVNA on a MacBook, any problems, how to, s/ware etc ?

thanks
Wayne VK6EH

LI-ON batteries, unlike NI-mH and Nicads do not respond well to trickle charging

Agreed.
But I was not saying that it should be the case, or was the case ;-)

I believe that Li-Ion prefer a typical 0.5C most of the time, so at the worst case lets assume a NanoVNA charge controller was
in error and allowed a full 1.2 amps to flow.

That would mean that if we used a typical 2400mah cell then the problem would go away.

As it just so happens, it happens to be the most unitary specification cell currently on the market.

So the paranoid users should just replace their own cell with a bog standard 2400mah cell and forget about it.

At worst case, it just takes a little longer to charge.

As for Ni-Mh, fast charging will kill them eventually, just like cigarettes and your lungs.

They contain water, and you know what happens to water when it gets hot <big-grin>

The negative electrode reaction occurring in a NiMH cell is

H2O + M + e? ? OH? + MH

On the positive electrode, nickel oxyhydroxide, NiO(OH), is formed:

Ni(OH)2 + OH? ? NiO(OH) + H2O + e?

I personally suspect that there are other reasons why users have experienced failed cells in NanoVNA's.

Undercharging and long periods of NO charging will produce swollen cells.

Those supplied cells might have been hanging around in a Peking warehouse for years and already faulty.

I left a crappy Android tablet in a drawer for 18 months, battery with no charge swelled and pushed the screen out ;-))

73 de Andy

On Tue, Nov 19, 2019 at 12:56 PM, Andy wrote:

Trickle charge current is also mentioned on the spec sheet as being 100ma, not enough to kill a 400ma cell.

Am I missing something ?
===============================================================================

Andy,
LI-ON batteries, unlike NI-mH and Nicads do not respond well to trickle charging. The LI-ON batteries used with the NanoVNA should have a small battery management board built in to limit the charging current and to cut-off when their voltage limit (~4.2V) is reached.

Most 3.7V cell phone batteries have the management pcb built in and so can be used without worry in the NanoVNA. Other 3.7V LI-ON batteries are "naked" (without a management board) and my guess is that those batteries over time will overheat, start to bulge and in other ways become defective.

- Herb

#79: Three Animated-GIF/AVIs in Slow Motion Demonstrate,
Step-by-Step, the Graphical Construction of Differential Error
Regions Arising in the Measurements with [AnyVNA]

Hello,

Allow us, please, to inform you that 11 years ago we uploaded 3
Animated-GIF/AVIs in slow motion demonstrating, Step-by-Step,
the graphical construction of the differential Error regions arising
in the Measurements with [AnyVNA], at:

1/3



2/3



3/3



Sincerely,

gin&pez@arg

:79#

Quote from spec sheet -

?Charger
?Adaptive charging current control,


Adaptive charging current control.

Quote from spec sheet -

IP5305 has integrated a voltage based fuel gauge algorithm, acquiring battery’s state of charge precisely.

Which in theory should regulate charging current.

The world and his dog knows full well that charging a Li-Ion cell needs real care under all circumstances, so I'm
puzzled by the claims that it would allow a full 1.2 amps to flow regardless. This does not make sense at all.

I guess the 1.2 amp spec is only based upon what the device can handle, since there is no heatsink etc.

Trickle charge current is also mentioned on the spec sheet as being 100ma, not enough to kill a 400ma cell.

Am I missing something ?

I wish I knew everything, but I accept that I don't ;)

73 de Andy

Hello,

This email message is a notification to let you know that the following files have been updated in the Files area of the [email protected] group.

• /NanoVNA-User-Guide-English-reformat-Nov-19-24.pdf

Uploaded By: Larry Rothman <nlroth@...>

Description:
This is a translated, reformatted and edited version of cho45's excellent (github-based) NanoVNA User Guide. I have made the URL links live as well as added additional content in order to clarify some sections. The document is 32 pages and is formatted for printing. updated Nov-19-2019 - Added sections on Scaling and menu map.

Cheers,
The Groups.io Team

Yes, you can upgrade and there is no issue of 'bricking' your unit.
Please refer to the Wiki and the User Guide (in the Files section) for info on how to upgrade and how to create a .dfu file if there is only a .hex file available.
...Larry

On Tue, Nov 19, 2019 at 10:19 AM, Rune Broberg wrote:

Generally, this means your firmware is so old, there is no way to read the
firmware version

Hi Rune,
Thanks! As a matter of fact by using NanoVNA v1.03 I got the following info (although I cant see FW version..):
Kernel: 4.0.0
Compiler: GCC4.9.3 ...
Architecture: ARMv6-M
Core variant: Contex-MD
Port info: Preemption through NMI
Platform: STM32F072xB entry level medium density devices
Board: NanoVNA
Build Time: Mar 27, 2019 16:28:15

Can I upgrade it to FW 0.5 using the DfuSe USB device firmware upgrade and following the advices I found on this group?

Thanks again,
Ciao
Alessandro i2sva

I wouldn't go as far as qbasic but I agree, whenever I see 'python' I
anticipate frustration and trouble. It's a mess. It's a great example of
why code re-use doesn't scale well. All too often it's hailed as the
platform for everything but the cracks are showing.

I was actually pleasantly surprised by how easily nanovna-saver ran for me
, so congrats to somebody for that.


On Tue, Nov 19, 2019 at 4:49 PM Andy via Groups.Io <punkbiscuit=
[email protected]> wrote:

It's Python that's a mess, as bad as java.

It promises app portability, and its anything but.

We need something like good old QBASIC, where we can load source into an
interpreter and run it.

Python and java are one big con.

Hi Alessandro,
Generally, this means your firmware is so old, there is no way to read the
firmware version.

--
Rune / 5Q5R

Hi all,
I noticed that moving to NanoVNASaver 0.2.0 > About, the NanoVNA Firmware version displayed is: NanoVNA Version ?
Has anyone noticed the same thing or I have something wrong? NanoVNAe works perfectly in conjunction with the NanoVNASaver; I was curious to understand which FW release is installed in my device and cannot see..!
Thanks for help,
73
Alessandro i2sva

Many have measured and tested it but found no noticeable difference between the variants. Probably the raw material comes from the same source, pcb is the same. So why would it differ unless the quality was properly controlled. They make sure that there is a slight difference between what they make and what they are compared to what is produced at the neighboring plant.

Looking again at your pic from Amazon, I notice it is sold by KKMoon. I brought two NanoVNAs from this same seller there. When they arrived one was a clone and the other appears to be a hugen original. You really can't tell what you're actually going to get from looking at the pictures in the adds.

I thought it was 1.2 amps max pass current, not actual current ?

English data sheet mentions intelligent charge levels.



Not sure if this helps, or the dsta sheet is misleading.

73 de Andy

What is pictured there is missing the "CH0" on the bezel. I think hugen would tag that as a clone That said, I have not seen where the clones have been shown to perform any worse. All NanoVNAs can be updated with a choice of new firmware with larger font, TDR, extended marker functions, etc.

The unit can operate as a stand-alone, unlike the many SDRs out there.
However, it can also operate with a PC, laptop, Android, and a number of
other platforms. With PC support, you get a MUCH larger screen, but PC is
not required for complete operation. You don't really need a PC if you can
read the small print on the color display.

The FW is continually being upgraded and additional functionality is being
augmented on a regular basis.

I'd suggest, as a newbie, you read some of the previously referenced
tutorials on the uses and capabilities of a VNA. It goes well beyond just
sweeping antennas for SWR. A VNA is an EXTREMELY capable instrument for
measurement of RF parameters of many flavors. I'd strongly recommend you
read the Agilent tutorials previously referenced on this group, I think
last week. Check the archives.

Dave - W?LEV

--

*Dave - W?LEV*
*Just Let Darwin Work*
*Just Think*