Re: nanoVNASaver clone - anybody
On Mon, Dec 12, 2022 at 10:25 AM, Anne Ranch wrote:
I am planning to ask directly in github....
Good plan; now execute it and you should be all set!
|
Re: Erratic results on nanoVNASaver ?
I am not really sure what kind of problem you are running into....( did not bother to read) But if it looks like a software issue, smells like a software issue and quacks like a software issue, but the user refuses to update. Then the problem might very well be sitting in front of the screen. -John Op zo 11 dec. 2022 om 15:41 schreef Anne Ranch <anneranch2442@...>:
I am not really sure which version nanoVNASaver software I am running....
( did not bother to look )
To verify it actually functions - I hooked to my old 440MHz ground
plane.
I am NOT looking for ANY accuracy , just
"proof of concept".
When I sweep from 400 to 500 MHz I get pretty much expected SWR display
pretty much scattered BELLOW 2... good enough for government work
When I "narrow it down" to
440 to 450 MHz
it is WELL bellow 1.2 - not expected when compared to previous measure
When I change back to
400 to 500 MHz
there is absolutely no change in ANYTHING on the software displays
and I get "I/O error " and I have to rerun the software.
What gives ?
and if the answer is
upgrade to the latest version
DO NOT BOTHER TO SAY SO
|
5v power should *always* be available on a USB port, so slow charging can
happen even on a dead device. What is negotiated are faster charge rates,
so, as you noted, a dead device will need to slow charge to the point that
it can power up before it can take a fast(er) rate of charge.
(FWIW, I have never charged my NanoVNA H4 on anything *but* my laptop USB
port (no external hub - just plugged it in. Seems to work fine.)
- Tim
toggle quoted message
Show quoted text
On Mon, December 12, 2022 9:13 am, Anne Ranch wrote: I was going to quit this thread, but...
I left the nanoVNA running overnight , connected to my PC and I did
"shutdown" and turned the PC power source off.
Turned off the D_link power source too.
In the morning I got no LCD and no LED's.
Turned all AC power on (PC , D-Link) and run "lsusb".
Still no LCD and LED's and no nanoVNA USB device.
Unplugged nanoVNA from USB port.
Unplugged "wallwart " from AC !!!
Plugged nanoVNA to dead wallwart and - LCD came on, so did both LEDs -
BUT briefly
Plugged wallwart to AC and have normally operating nanoVNA
LCD on, charging LED on , sweep LED flashing,,,
My conclusion / opinion
in my interpretation of USB "standard operation"
...when a USB device is first plugged into its controller
it runs kind of "here I am " sequence and the controller should
acknowledge that and respond ...
How does supposedly dead nanoVNA manages to do this when plugged in DEAD
power source ?
--
Tim Dawson (tadawson@...) Owner/Engineer
TPC Services Bellnet: (972)-221-7385
Lewisville, Texas 75067
"The world is complex. Sendmail.cf reflects this...."
|
nanoVNASaver clone - anybody
Up front - few years back I got involved with nanoVNASaver and soon
realized this is not a right group to ask about nanoVNASaver software.
BUT - if there is a remote possibility that has changed
Does anybody (here) has an interest in hacking the nanoVNASaver software?
I have managed to clone it as QT project , but since I do not do "python" I am pretty much stuck...
PS
I am planning to ask directly in github....
|
I was going to quit this thread, but...
I left the nanoVNA running overnight , connected to my PC and I did "shutdown" and turned the PC power source off.
Turned off the D_link power source too.
In the morning I got no LCD and no LED's.
Turned all AC power on (PC , D-Link) and run "lsusb".
Still no LCD and LED's and no nanoVNA USB device.
Unplugged nanoVNA from USB port.
Unplugged "wallwart " from AC !!!
Plugged nanoVNA to dead wallwart and - LCD came on, so did both LEDs - BUT briefly
Plugged wallwart to AC and have normally operating nanoVNA
LCD on, charging LED on , sweep LED flashing,,,
My conclusion / opinion
in my interpretation of USB "standard operation"
...when a USB device is first plugged into its controller
it runs kind of "here I am " sequence and the controller should acknowledge that and respond ...
How does supposedly dead nanoVNA manages to do this when plugged in DEAD power source ?
|
On 12/11/22 8:07 PM, Anne Ranch wrote: My PC is "open architecture " ASUS motherboard in old desktop case. nanoVNA USB port is via powered D_Link " USB hub.
It has not been powered for about 6 months ,,,, I am going to let it fully discharge overnight.
It looks as setting to "continuous sweep" drains the battery pretty fast - perhaps the flashing
"sweep LED" is "too much load "?
The OS still controls (or at least manages) the hub's power as part of the whole USB tree, even if the hub itself receives external power. That is, the hub can decide if it wants to turn power on to a downstream device or not, and the OS (in theory) can find out. The OS can also force a downstream hub to turn off a device. Considering that (almost) all USB hubs are 4 port devices at the "building block" level, the interlocking state diagrams up and down the chain can be really complex to figure out exactly what is going on. (Note that this four-ness, is why you see 7 port hubs. It's actually a cascade of two 4 ports, with one hanging off one of the 4 ports of the other). There's an equally complex negotiation and state machine for data rate through a USB hub.
|
Re: Erratic results on nanoVNASaver ?
Interesting question.
I mostly use my Nano VNA on HF bands.
It has never failed in any aspect - one port antenna, 2 port filter tests, over all of the HF bands anyway.
But when I did the 440 band calibration, I did it over a 20x sample, so the number of data points on the 1-port calibration was about 2000 data. You want to be sure the CAL file does what you need.
Plug your 50 ohm standard into the port (in place of your 440 antenna) and test the VSWR from 430 to 450 MHz and see if you get what you expect: 1 to 1.
I suspect that the coax you use to connect this Nano VNA socket to your 440 antenna matters a bunch.
First, I would try a very simple 440 MHz ground plan using just a few feet of coax, just to verify everything is working.
Do you have an SMA to UHF coax socket adapter?
I usually plot the Reflection Coefficient (0 to 1) and the RETURN LOSS (dB) as well as the VSWR, the Resistance and Reactance, the PHASE, and finally a Smith Chart on ALL of my HF antenna checks.
They should all agree.
Where is the resonant frequency/frequencies (where the reactance is zero)?
Where is the VSWR minimum?
Where does the phase change from net to pos?
My Nano VNA is three years old and my SAVE software is something like V0.5
I¡¯ve never used it with the internal battery, nor the internal 101 data points.
I always use it connect to usb port, power with usb port, and to a Windows 10 desktop.
The DRIVERS are fine.
It is one amazing device with superb (free) software.
I can share some of my 70 cm antenna plots if that would help.
I would bet problems you have are due to bad connectors and/or faulty coax when you get up to 440 MHz band.
So try your 50 ohm dummy load and be sure it is behaving.
So explain in detail your calibration procedures.
Hope you solve your question,
K3eui barry
|
My PC is "open architecture " ASUS motherboard in old desktop case. nanoVNA USB port is via powered D_Link " USB hub.
It has not been powered for about 6 months ,,,, I am going to let it fully discharge overnight.
It looks as setting to "continuous sweep" drains the battery pretty fast - perhaps the flashing
"sweep LED" is "too much load "?
|
I charge my NanoVNA from my PC's usb port every time I use it, work fine. Are you using a laptop, or a tablet maybe?
N0NC
|
On 12/11/22 9:47 AM, Anne Ranch wrote: ...to be continued
there is more
when the "charge LED" is off and I plug the USP cable to wallwart - it starts flashing...
hence it is charging
after coupe of minutes
when I unplug the wallwart - the LED goes steady - charged (?) / not charging
if I plug the cable into PC USB port (powered DLink) the LED
stays on for a minute or so then LED goes blank
My OPINION / conclusion
my battery is weak and PC USB port has not enough "umpf" to actually charge
such dead battery ..
Or it's not responding to the request for more current.
|
ask and yea shall receive
the original post answer in in the manual under Specification
and that is why it won't work - in theory
Supply current 500 mA NO CHARGING
Battery current charging 1.2A
NORMAL , not setup for "charging " USB port is LIMITED to 500mA
if the batter charging current is 1.2 A
DEAD battery cannot be safely charged using NORMAL USB port.
Besides - rule of thumb - battery charging current is limited by
capacity (in Ah) of the battery and USUALLY about 10% of such
capacity is considered safe charge current.
I am not going to go into nanaoVNA battery technology - in is NOT Lead Acid -
however , improperly charged LiPo batteries have been source of few fife causing "accidents"
CASE CLOSED
PS
How is dx?
|
This make no sense
you pause the sweep, or after a single-sweep, the LED is steady on.
hence there is no flash ?
DO I understand this correctly ?
Calibrated and maybe even not calibrated (?) nanoVNA should sweep automatically - by design
( it can be calibrated for single or continuous sweep ??)
When I use nanoVNASaver I can control the sweep
so if set for "single seep" the "sweep LED" should come on - no flash-
and then stay on?
or
if set for "continuous sweep" should it keep flashing ?
|
...to be continued
there is more
when the "charge LED" is off and I plug the USP cable to wallwart - it starts flashing...
hence it is charging
after coupe of minutes
when I unplug the wallwart - the LED goes steady - charged (?) / not charging
if I plug the cable into PC USB port (powered DLink) the LED
stays on for a minute or so then LED goes blank
My OPINION / conclusion
my battery is weak and PC USB port has not enough "umpf" to actually charge
such dead battery ..
|
Re: Erratic results on nanoVNASaver ?
I had it calibrated for different band ....No I did not change "sweep points " but I may have lost the connection -
my battery does not seems to last very long - but that may be different issue.
Actual values of SWR do not matter - for now.
and on top of it - I have no clue how "wide banded" is my old ground plane antenna ....;..
As soon as I get it fully changed I'll try to calibrate it for the 440 MHz band plus the extra hardware I am using.
On startup I get the display to show the original band calibration and it did include the coax...
|
"Please keep the discussion impersonal and civil."... Please leave! You
wonderful example of a person whom wishes to improve them selves by
sponging upon people who have put in the hours and own a tee shirt with
RTFM on it. They then place this rude demanding post up. A sweet farewell
to you.
toggle quoted message
Show quoted text
On Sun, 11 Dec 2022 at 14:25, Anne Ranch <anneranch2442@...> wrote: Please keep the discussion impersonal and civil.
That is hilarious reply to my original post....
I got ONE LED function solved - not thanks to this group...
Now you can redeem yourself - if so desired ....
What is the function of the (green) LED next to the "wheel " switch?
No opinions , please , - a reference / clip (cut and paste ) from
any manuals would be appreciated.
|
The green LED next to the wheel switch (actually the one on my nanovna-H4
is blue): the firmware 'flashes' this LED when the device is sweeping. If
you pause the sweep, or after a single-sweep, the LED is steady on.
toggle quoted message
Show quoted text
On Sun, Dec 11, 2022 at 6:25 AM Anne Ranch <anneranch2442@...> wrote: Please keep the discussion impersonal and civil.
That is hilarious reply to my original post....
I got ONE LED function solved - not thanks to this group...
Now you can redeem yourself - if so desired ....
What is the function of the (green) LED next to the "wheel " switch?
No opinions , please , - a reference / clip (cut and paste ) from
any manuals would be appreciated.
|
Re: Erratic results on nanoVNASaver ?
On 12/11/22 6:41 AM, Anne Ranch wrote: I am not really sure which version nanoVNASaver software I am running....
( did not bother to look )
To verify it actually functions - I hooked to my old 440MHz ground plane.
I am NOT looking for ANY accuracy , just
"proof of concept".
When I sweep from 400 to 500 MHz I get pretty much expected SWR display
pretty much scattered BELLOW 2... good enough for government work
When I "narrow it down" to
440 to 450 MHz
it is WELL bellow 1.2 - not expected when compared to previous measure
When I change back to
400 to 500 MHz
there is absolutely no change in ANYTHING on the software displays
and I get "I/O error " and I have to rerun the software.
What gives ?
and if the answer is
upgrade to the latest version
DO NOT BOTHER TO SAY SO
How did you calibrate? (was it a 101 point cal covering 400-500 or something like that? or a "multisweep" cal with more points?)
|
Re: Erratic results on nanoVNASaver ?
Ok I won¡¯t bother
fox out
|
Erratic results on nanoVNASaver ?
I am not really sure which version nanoVNASaver software I am running....
( did not bother to look )
To verify it actually functions - I hooked to my old 440MHz ground plane.
I am NOT looking for ANY accuracy , just
"proof of concept".
When I sweep from 400 to 500 MHz I get pretty much expected SWR display
pretty much scattered BELLOW 2... good enough for government work
When I "narrow it down" to
440 to 450 MHz
it is WELL bellow 1.2 - not expected when compared to previous measure
When I change back to
400 to 500 MHz
there is absolutely no change in ANYTHING on the software displays
and I get "I/O error " and I have to rerun the software.
What gives ?
and if the answer is
upgrade to the latest version
DO NOT BOTHER TO SAY SO
|
Please keep the discussion impersonal and civil.
That is hilarious reply to my original post....
I got ONE LED function solved - not thanks to this group...
Now you can redeem yourself - if so desired ....
What is the function of the (green) LED next to the "wheel " switch?
No opinions , please , - a reference / clip (cut and paste ) from
any manuals would be appreciated.
|
Muggs KC3UDZ
Barry K3EUI