Re: Some required setting for NanoVNA-saver using female calibrations
Not sure. I often use port extensions when measuring a DUT with a different cable. Being able to quickly rotate the cable away during regular measurement is a very nice feature. Also it would help if nanoVNA-saver can calculate the extension to do the rotation (simplest way is to rotate S11 of the highest frequency response in the scan back to zero degrees phase shift) -- NanoVNA Wiki: /g/nanovna-users/wiki/homeNanoVNA Files: /g/nanovna-users/filesErik, PD0EK
|
Greetings to the Battery Group :)
I have some batteries for Samsung Galaxy S3, 2100mAH, that are a just a bit smaller than the nano and would fit inside with slightly longer standoffs.
But here the question: these phone batteries have 4 connections; I can measure positive voltage on one, negative on the 3 others. Does anyone know if these 4-terminal phone batteries have internal protection, and are they safe to use as a 2-wire battery? What do the other 2 connections do, in the normal phone purpose?
Thanks, --kv5r
|
Re: Some required setting for NanoVNA-saver using female calibrations
Hi Rune , in my opinion ,the right place of the port extension control , is on the calibration menu.
Best regards
Maurizio IZ1MDJ
|
Re: Some required setting for NanoVNA-saver using female calibrations
Hello Kurt,
a value of 1 should work. But I haven't had time to test it thoroughly :-)
I will look into making a value of 0 work as well, or give an error if it
is not possible.
"Port extension" delay setting is in the works, but I'm looking at where to
put the control in the interface.
--
Rune / 5Q5R
toggle quoted message
Show quoted text
On Wed, 20 Nov 2019 at 02:45, Kurt Poulsen <kurt@...> wrote: Hi Run
Aha, thank you for the info. That is a nasty one ?
Then a value of 1 might me OK ?
Kind regards
Kurt
-----Oprindelig meddelelse-----
Fra: [email protected] <[email protected]> P? vegne af Rune
Broberg
Sendt: 19. november 2019 17:40
Til: [email protected]
Emne: Re: [nanovna-users] Some required setting for NanoVNA-saver using
female calibrations
Hi Kurt,
Sorry for taking long to reply to your email.
The issue in your earlier tests seem to be with C0=0: the calibration
corrections divide by a value that is dependant on C0, and for that reason,
C0=0 is not a valid standard - and the custom settings for the "open" is
disabled, including delay.
--
Rune / 5Q5R
On Tue, 19 Nov 2019, 16:02 Kurt Poulsen, < <mailto:kurt@...>
kurt@...> wrote:
Hi All In the NanoVNA-saver the calibration settings, when doing a female calibration with the supplied NanoVNA calibration kit, where the male SOL parts are fitted to the FF adaptor, need some special settings until Rune gets fixing the following: The Open delay does not work and substituted by a C0 setting as shown in attached image of 1022.3 fF Do not use the open calibration standard just leave the FF adaptor open As Shunt C for the load not yet implemented an inductance og 205pH introduced as temporary fix The data are for the NanoVNA-H delivered after end October. The earlier delivered kits are for Short and Load identical but the delay of FF adaptor is a bit longer and 70.3ps Remember the NanVNA internal C0 calibration must be done prior to using the NanoVNA-saver with the same setup as when calibration with the NanoVNA-saver Kind regards Kurt
|
TL;DR: if unsure, ONLY use cells >= 2400mAh and <= 10000mAh with the Nano. The reason for the upper limit is a bit more subtle; it's due to the fact that the charge cut-off current is fixed (100mA), and on higher capacity cells by the time the current falls to 100mA it is already overcharged.
|
The IP5305 can not limit current to a "safe" value for the battery because it doesn't know what the battery's capacity is. It simply limits current to 1.2A or whatever the USB port can supply, whichever is lower. It's up to the design engineer to choose a battery that can handle 1.2A of charging current. Most 18650 cells are specified for at most 0.5C charge rate (some higher capacity laptop cells are even 0.25C). There are pouch cells specified up to 1C (for example in most smartphones). The cell's datasheet will state the maximum charge current. For ebay/aliexpress cells without a datasheet absolutely stay away from anything > 0.5C.
|
Re: running nanoVNA-saver under Linux Mint XFCE
On 11/19/19 8:22 AM, DougVL wrote: But I have already installed Linux and tried it a bit. Maybe fine for a trained I.T. person! ???? Interesting.? I am not a trained I.T.person, have been using Linux since 2002, and have had pretty much no problems with it at all.? I do, however, find Windows to be a royal PITA, on those rare occasions when I have the misfortune to have to use it. Also, I attend the computer club meetings at the local senior center, and I am constantly amazed at the problems those Windows users tolerate.? Different strokes for different folks, I guess. I had no? problems installing NanoVNA-saver on my Linux system.
|
Re: Is the NooElec nanoVNA any good?
On Tue, Nov 19, 2019 at 02:56 PM, W5DXP wrote:
"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 ?"
=================================================================
On eBay I already see cloner's misrepresenting their units as NanoVNA-F's when the photos are obviously 2,8" NanoVNA's. The same thing will happen with the Nanovna-H, and buyer's will have to be knowledgeable that the -H has a protective case and comes in a specially designed box with accessories.
Down the road the case designed and packaging will probably be cloned, but by that time hugen will hopefully stay ahead of the field with NanoVNA-F V2.
- Herb
|
Re: Some required setting for NanoVNA-saver using female calibrations
Hi Run Aha, thank you for the info. That is a nasty one ? Then a value of 1 might me OK ? Kind regards Kurt -----Oprindelig meddelelse----- Fra: [email protected] < [email protected]> P? vegne af Rune Broberg Sendt: 19. november 2019 17:40 Til: [email protected]Emne: Re: [nanovna-users] Some required setting for NanoVNA-saver using female calibrations Hi Kurt, Sorry for taking long to reply to your email. The issue in your earlier tests seem to be with C0=0: the calibration corrections divide by a value that is dependant on C0, and for that reason, C0=0 is not a valid standard - and the custom settings for the "open" is disabled, including delay. -- Rune / 5Q5R
On Tue, 19 Nov 2019, 16:02 Kurt Poulsen, < <mailto:kurt@...> kurt@...> wrote: Hi All In the NanoVNA-saver the calibration settings, when doing a female calibration with the supplied NanoVNA calibration kit, where the male SOL parts are fitted to the FF adaptor, need some special settings until Rune gets fixing the following: The Open delay does not work and substituted by a C0 setting as shown in attached image of 1022.3 fF Do not use the open calibration standard just leave the FF adaptor open As Shunt C for the load not yet implemented an inductance og 205pH introduced as temporary fix The data are for the NanoVNA-H delivered after end October. The earlier delivered kits are for Short and Load identical but the delay of FF adaptor is a bit longer and 70.3ps Remember the NanVNA internal C0 calibration must be done prior to using the NanoVNA-saver with the same setup as when calibration with the NanoVNA-saver Kind regards Kurt
|
Hi All,
I used the battery from a Boefeng 888 which was broken down to make an Allstar node. Labelled as 2.2Ah, and includes a protection board.
73
Barry
G4MKT
|
Re: Running NanoVNA on MacBook Pro
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
|
Re: Is the NooElec nanoVNA any good?
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
|
Running NanoVNA on MacBook Pro
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
|
Re: errors of "error" models
#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.
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
|
OwO
Jim Allyn - N7JA
Kurt Poulsen
gin&pez@arg