Please keep the discussion impersonal and civil.
DaveD
toggle quoted message
Show quoted text
On Dec 11, 2022, at 07:06, Anne Ranch <anneranch2442@...> wrote:
?Respectfully disagree with this opinion
If you can¡¯t or don¡¯t want to actually answer a question, just delete the message.
coronary
If you cannot answer the question or do not get the question
DO NOT POST STUFF ABOUT YOUR pet
DO NOT POST YOUR (IRRELEVANT ) OPINIONS
KISS - "just the facts ma'am..."
|
Respectfully disagree with this opinion
If you can¡¯t or don¡¯t want to actually answer a question, just delete the message.
coronary
If you cannot answer the question or do not get the question
DO NOT POST STUFF ABOUT YOUR pet
DO NOT POST YOUR (IRRELEVANT ) OPINIONS
KISS - "just the facts ma'am..."
|
Gee folks, the manuals and other written tomes (more than I wanted) for my first nano and my most recent one were available from the seller and also a few web searches¡.. maybe I am just blessed but manuals and instructions for all my ham gear, new and old, is readily available on the web. And the company selling my most recent nano offered a nice and very complete book printed and Kindle right next to the nano on their site¡. Maybe I am just lucky.
Dave K8WPE
David J. Wilcox¡¯s iPad
toggle quoted message
Show quoted text
On Dec 10, 2022, at 10:50 PM, KK4ITX John via groups.io <jleahy00@...> wrote:
?This unit appears to be a very, very neat device, the flaw, IMHO, like so many of today¡¯s products come with zero to no documentation. One has to search hours on end and rely on the research of others to glean operating awareness before they otherwise destroy it.
What happens more often than not is few ¡°helpful¡± do not actually answer the original question but will rant on with verbiage and insult to no end. If I have the opportunity to help someone I point them to the details on PAGE # in the manual, which is far better than RTFM. Some folks may actually be on the road and away from the manual but in this case there isn¡¯t a particular manual that EVERYBODY has or have I missed it ?
If you can¡¯t or don¡¯t want to actually answer a question, just delete the message.
John
KK4ITX
Visit: www.zaarc.org. ?
On Dec 10, 2022, at 22:33, Larry McElhiney via groups.io <lmcelhiney@...> wrote:
Hi Vaclav,
Please cool your jets¡
Battery LED - constant light is an indication of a charged battery. It flashes when the battery is charging. During normal operation, flashing indicates low power - connect the charger to charge the battery.
(A very small amount of reading on your part could reduce the amount of time that others take to voluntarily help you.)
Larry
|
I have found over years of enjoyable ham radio building and operating that reading the manual 3 or even 4 times over before building the kit or receiving the radio (most manuals are on the web) is much preferred than trying to struggle with finding the answer with web searches and the WiKi¡.. it was written by the developer of the kit/radio and is specific. I liken it to my Bible¡.. when life isn¡¯t working out the ¡°manual¡± always seems to have answers appropriate to the situation. And even weeks or months after (lately on my Elecraft K1 the 20 year old manual had the answers I was looking for right in the index) starting to use the radio again the manual was even more helpful. Please don¡¯t disparage manuals. After the manual, looking in YouTube many times has the answer also if you look long enough for it. I would swear sometimes I have dyslexia because the answer will be right in front of me but I cannot see it. My nontechnical wife, if I ask her, can usually spot what I am not seeing in a manual just by her nontechnical way of problem solving. It just hurts my pride to ask even after 49 3/4 years¡¡
As my old German instructor used to repeatedly say to us young men, Hoch kompt vor dem fall¡..excuse the poor German spelling¡. It¡¯s been too many years¡¡
Also when asking here the more information one can supply the better the answer¡.
Dave K8WPE
David J. Wilcox¡¯s iPad
toggle quoted message
Show quoted text
On Dec 10, 2022, at 1:21 PM, Anne Ranch <anneranch2442@...> wrote:
?I have downloaded nanoVNA -saver, and I got it running on Ubuntu.
I have plugged in USB cable and identified the USB device - using lsusb command.
I have steady light next to the USB port - it indicates what ?
Next to it I have flashing light , I assume charging battery.?
Please just indicate / answer the ?
I did ask Mrs Google and she couldn't just simple state / answer.
I am NOT in favor RTFM , I just need the answers for above.
What is the correct sequence
of pushing buttons
to actually connect nanoVNA-saver to the USB port?
rescan -> select port from combo box
push -> Connect top device
I am getting bunch of what appears to be progress / error messages and so far no port ....
PS I got rid of "missing permission to access port ".
Here is a sample:
AttributeError: 'NoneType' object has no attribute 'lock'
Traceback (most recent call last):
File "/home/nov25-1/.local/lib/python3.10/site-packages/NanoVNASaver/Controls/SerialControl.py", line 74, in serialButtonClick
self.connect_device()
File "/home/nov25-1/.local/lib/python3.10/site-packages/NanoVNASaver/Controls/SerialControl.py", line 79, in connect_device
with self.interface.lock:
AttributeError: 'NoneType' object has no attribute 'lock'
Traceback (most recent call last):
File "/home/nov25-1/.local/lib/python3.10/site-packages/NanoVNASaver/Controls/SerialControl.py", line 74, in serialButtonClick
self.connect_device()
File "/home/nov25-1/.local/lib/python3.10/site-packages/NanoVNASaver/Controls/SerialControl.py", line 79, in connect_device
with self.interface.lock:
AttributeError: 'NoneType' object has no attribute 'lock'
PPS I am content with current version, whatever it is, no want / need to update - not yet - let me connect first...
|
This unit appears to be a very, very neat device, the flaw, IMHO, like so many of today¡¯s products come with zero to no documentation. One has to search hours on end and rely on the research of others to glean operating awareness before they otherwise destroy it.
What happens more often than not is few ¡°helpful¡± do not actually answer the original question but will rant on with verbiage and insult to no end. If I have the opportunity to help someone I point them to the details on PAGE # in the manual, which is far better than RTFM. Some folks may actually be on the road and away from the manual but in this case there isn¡¯t a particular manual that EVERYBODY has or have I missed it ?
If you can¡¯t or don¡¯t want to actually answer a question, just delete the message.
John
KK4ITX
Visit: www.zaarc.org. ?
toggle quoted message
Show quoted text
On Dec 10, 2022, at 22:33, Larry McElhiney via groups.io <lmcelhiney@...> wrote:
Hi Vaclav,
Please cool your jets¡
Battery LED - constant light is an indication of a charged battery. It flashes when the battery is charging. During normal operation, flashing indicates low power - connect the charger to charge the battery.
(A very small amount of reading on your part could reduce the amount of time that others take to voluntarily help you.)
Larry
|
Hi Vaclav,
Please cool your jets¡
Battery LED - constant light is an indication of a charged battery. It flashes when the battery is charging. During normal operation, flashing indicates low power - connect the charger to charge the battery.
(A very small amount of reading on your part could reduce the amount of time that others take to voluntarily help you.)
Larry
|
Thanks , but I did not ask for a presentation - I just need a simple answer.
With the slide switch in "next to USB plug " position
what does LED next to the USB plug flashing indicates ?
Here are multiple choices
Flashing LED next to USB plug is an indicator of
1. The LED is being powered on / off
2. The nanoVNA is receiving signal from aliens
3. TGIF
4. Nothing
5. The nanoVNA needs update to latest version
8/ All of the above
9. None of the above
10. nanoVNA is (being) powered via USB plug
|
Dear Anne, as Carey has already indicated, suggesting publicly that one can't/won't/shan't/find-it-against-my-religion to RTFM is very likely to put people off. Suggesting, on the other hand, that one has read the documentation, and is still having issues at least indicates that one has made the effort¡ The in-line notes below result from plugging a nanoVNA H-4 in to an 18.04? Ubuntu box, in the following sequence: 1) plug USB cable in to PC and nanoVNA 2) power on nanoVNA 3) Launch nanoVNA (in my case, from a menu item) 4) Look at serial port control (LHS of NanoVNA Saver window, towards the bottom). Probably, the device selected will be shown as ¡°/dev/ttyACM0 (NanoVNA)¡± 5) Click on the button marked ¡°Connect¡±, which, after a second or two, will change to ¡°Disconnect¡± 6) One may now start to see results by using the ¡°Sweep button¡± (LHS, towards the top) 7) Calibration &c. is for the user to explore Is that reasonably clear? The installation is important. Poke and hope¡ªmissing out the boring bits¡ªjust will not cut it, any more than it would with a Pi-tank valve (tube) PA. (see notes below). 73, Stay Safe, Robin, G8DQX ? It's due to be updated RSN! On 10/12/2022 18:21, Anne Ranch wrote: I have downloaded nanoVNA -saver, and I got it running on Ubuntu.
I have plugged in USB cable and identified the USB device - using lsusb command.
I have steady light next to the USB port - it indicates what ? It is the system LED, which blinks during a sweep. Next to it I have flashing light , I assume charging battery.? Correct. Please just indicate / answer the ?
I did ask Mrs Google and she couldn't just simple state / answer.
I am NOT in favor RTFM , I just need the answers for above. With any sort of gear, RTFM is always useful, and pretty much obligatory for complex equipment, whether based on valve (tube) or semiconductor (transistors & ICs) technology. ¡°I just need the answers for above¡± may be true, but those who are likely to have the knowledge to be able to answer the questions very probably had to start with RTFM, followed by a great deal of exploration. What is the correct sequence
of pushing buttons
to actually connect nanoVNA-saver to the USB port? Generally, the nanoVNA will already be recognised, and will appear on /dev/ttyACM0. Unless you have other ttyACM devices attached, such as a modem, there will only be one possibility. rescan -> select port from combo box
push -> Connect top device That should work, unless the top device is not /dev/ttyACM0. If, for example, one also had a tinySA attached, then there would be two possibilities. Simplest to disconnect any other ttyACM devices. I am getting bunch of what appears to be progress / error messages and so far no port .... How was NanoVNA-Saver installed? What version of Ubuntu is in use? Has a Python virtual environment (PVE) been established? In my hard-won experience, the PVE is pretty fundamental to success in this enterprise. Those error messages appear to be indicating something amiss, and an unhappy installation is likely to be the fundamental reason why things are not going well. PS I got rid of "missing permission to access port " <<stuff deleted>>
|
"I am NOT in favor RTFM , I just need the answers for above."
hahahahahahahaha
toggle quoted message
Show quoted text
On Sat, Dec 10, 2022 at 1:21 PM Anne Ranch <anneranch2442@...> wrote: I have downloaded nanoVNA -saver, and I got it running on Ubuntu.
I have plugged in USB cable and identified the USB device - using lsusb
command.
I have steady light next to the USB port - it indicates what ?
Next to it I have flashing light , I assume charging battery.?
Please just indicate / answer the ?
I did ask Mrs Google and she couldn't just simple state / answer.
I am NOT in favor RTFM , I just need the answers for above.
What is the correct sequence
of pushing buttons
to actually connect nanoVNA-saver to the USB port?
rescan -> select port from combo box
push -> Connect top device
I am getting bunch of what appears to be progress / error messages and so
far no port ....
PS I got rid of "missing permission to access port ".
Here is a sample:
AttributeError: 'NoneType' object has no attribute 'lock'
Traceback (most recent call last):
File
"/home/nov25-1/.local/lib/python3.10/site-packages/NanoVNASaver/Controls/SerialControl.py",
line 74, in serialButtonClick
self.connect_device()
File
"/home/nov25-1/.local/lib/python3.10/site-packages/NanoVNASaver/Controls/SerialControl.py",
line 79, in connect_device
with self.interface.lock:
AttributeError: 'NoneType' object has no attribute 'lock'
Traceback (most recent call last):
File
"/home/nov25-1/.local/lib/python3.10/site-packages/NanoVNASaver/Controls/SerialControl.py",
line 74, in serialButtonClick
self.connect_device()
File
"/home/nov25-1/.local/lib/python3.10/site-packages/NanoVNASaver/Controls/SerialControl.py",
line 79, in connect_device
with self.interface.lock:
AttributeError: 'NoneType' object has no attribute 'lock'
PPS I am content with current version, whatever it is, no want / need to
update - not yet - let me connect first...
--
Carey Fisher
careyfisher@...
|
I have downloaded nanoVNA -saver, and I got it running on Ubuntu.
I have plugged in USB cable and identified the USB device - using lsusb command.
I have steady light next to the USB port - it indicates what ?
Next to it I have flashing light , I assume charging battery.?
Please just indicate / answer the ?
I did ask Mrs Google and she couldn't just simple state / answer.
I am NOT in favor RTFM , I just need the answers for above.
What is the correct sequence
of pushing buttons
to actually connect nanoVNA-saver to the USB port?
rescan -> select port from combo box
push -> Connect top device
I am getting bunch of what appears to be progress / error messages and so far no port ....
PS I got rid of "missing permission to access port ".
Here is a sample:
AttributeError: 'NoneType' object has no attribute 'lock'
Traceback (most recent call last):
File "/home/nov25-1/.local/lib/python3.10/site-packages/NanoVNASaver/Controls/SerialControl.py", line 74, in serialButtonClick
self.connect_device()
File "/home/nov25-1/.local/lib/python3.10/site-packages/NanoVNASaver/Controls/SerialControl.py", line 79, in connect_device
with self.interface.lock:
AttributeError: 'NoneType' object has no attribute 'lock'
Traceback (most recent call last):
File "/home/nov25-1/.local/lib/python3.10/site-packages/NanoVNASaver/Controls/SerialControl.py", line 74, in serialButtonClick
self.connect_device()
File "/home/nov25-1/.local/lib/python3.10/site-packages/NanoVNASaver/Controls/SerialControl.py", line 79, in connect_device
with self.interface.lock:
AttributeError: 'NoneType' object has no attribute 'lock'
PPS I am content with current version, whatever it is, no want / need to update - not yet - let me connect first...
|
Re: Nano V2 on the blink.......
Tim, If you haven't used it in a while, you might want to bring it up to the latest version of firmware - use DiSlord's releases as he has made improvements and bug fixes. You can find new firmware in the Nanovna-beta group: /g/nanovna-beta-test/message/4024Also, did you remember to perform a calibration reset immediately prior to performing the cal so the existing cal memory is wiped? I don't own a V2, so that's all I can help you with at this point. Good luck. ...Larry VE3LRI
|
Re: Need help matching my DIY antenna using a NanoVNA
Hello Bill,
Great to see you are having fun with this. The NanoVNA is such a wonderful piece of kit.
As others have said here, you may not have to sweat this too much.
The 1/4 wave whip on most aircraft is usually 1/8" stainless steel rod and will not be as broadband as yours is now. As someone else noted, the radios are probably pretty tolerant anyway.
If you minimise the VSWR around the ATC and VFR frequencies you will actually transmit on, that will suffice. You will still receive stuff (like ATIS) at the extremities of the band OK.
Whilst the fan and bowtie suggestions for broadbanding the antenna are very valid, they do not seem to be a practical option for your vertical stabiliser looking at your photos.
As for the different lengths, that is quite feasible as other components in the aircraft, including the ply skin and the coax cable itself will affect the tuning.
You have the best tool available in the NanoVNA to do this tuning. Trust your VNA.
Most LAME electricians who install radios in aircraft would not know what a VNA was, let alone how to use it.
Just a word of warning, don't be tempted to connect the NanoVNA to the antenna cable at the airport or around other aircraft who might transmit near you.
Also, don't be tempted to use a hand held radio at home with the VNA connected.
You run the very real risk of frying the NanoVNA CH0 input if you do.
Good luck with your project. Hope you get many hours of enjoyment flying it. And many more hours of fun playing with the NanoVNA.
Cheers...Bob VK2ZRE
toggle quoted message
Show quoted text
On 9/12/2022 3:23 am, William tunna wrote: Thank you for the highly detailed response Bob, I have indeed got the shielding from the coaxial soldered to the strip on the top of the fuselage and the centre core soldered to the strip going up the fin of the aircraft. At the moment I have got 3 ferrite cylinders just off from where the coaxial connects to the antenna and I've run the whole coaxial to the cockpit the the final TNC connector, which is where I am measuring from.
Luckily my copper tape has conductive adhesive, so I reset my antenna by making both lengths the same. I have then taken 1cm off each end at a time and have found I had to take about 5cm off each end to get it within specs. I think the biggest problem with this antenna is the control rod for the tail runs all the way behind the fin. I have found though, that if the ground strip is 3cm longer than the other strip, it really improves the SWR in the lower ranges without affecting the higher frequencies. Not sure if this is a big deal or not, here is the improved SWR chart in the image
Tomorrow I'm going to try adding more copper tape either side of the existing tape to increase the width, see if this helps.
Thanks everyone else for the helpful responses
|
You can also look at ZPlots, by Dan Maguire, AC6LA, which I personally find more user-friendly, and perform the same analysis.
RigExpert¡¯s AntScope 1, when used in consistent fashion, will provide support fir the earlier RigExpert units.
Hard to believe, but there are still a bunch of internet self-appointed experts who would rather try to cut a half-wave of coax to bring the feedpoint impedance to the shack (or the analyzer) than believe the physics. I have seen their efforts to sadly include bogus Vf use, using coax specs, rather than testing it.
Oh well.
Ed McCann
AG6CX
|
Re: BASIC PPT on the Nano VNA de k3eui Barry
"Standards are /good things/...that's why there are so /many/ of them!" John at radio station VE7AOV +++++ On 2022-12-07 07:52, Jim Lux wrote: On 12/7/22 7:31 AM, Donald S Brant Jr wrote:
On Wed, Dec? 7, 2022 at 02:03 AM, Luc ON7DQ wrote:
that should of course be "at the Reflection socket" (or CH0)
I fail to understand why the designers of all of these VNAs labeled the ports CH0 and CH1, when every other VNA I have used over the past 45+ years has had Port 1 and Port 2.
This just adds to the confusion, especially when trying to explain S-parameters.? S21/S12 makes more sense when the ports are 1 and 2, much less so with 0 and 1.
73, Don N2VGU zero based indexing.? The first person to build one happened to choose CH0 and CH1, and then it stuck.
Matlab and Fortran (and BASIC) follow the mathematician convention of 1 based.
C started zero based because of the array/pointer duality and the desire to keep the compiler simple.
Component numbering usually starts at 1, but often has a hundreds or thousands to indicate which board or assembly (that is, C302 is the second capacitor labeled on board #3)
Yeah - it's kind of like emacs vs vi; or case sensitive file and directory names.? Someone picks something, and the rest follow, or not.
--
|
Hey Roger, Thank-you for your reply and the transformer info. I was aiming at what I can do with AntScope using the vna, either with nano-saver or on the device itself. 73Phil, WF3W
|
On 12/8/22 2:16 PM, Roger Need via groups.io wrote: On Thu, Dec 8, 2022 at 12:52 PM, Stan Dye wrote:
The normal way to do it on the nanovna is a bit different. You attach the
near end of the coax to the nanovna, then calibrate (using the
open/short/load calibration loads) at the far end of the cable. Then you
attach the antenna at the far end - all measurements then show the
performance of the antenna itself, having compensated for the coax
properties (primarily length and attenuation).
I agree with you that this "de-embedding" the cable method is the most accurate and only needs to be done once for the cable being used. Then the cal file can be saved for later recall. This is what I do, but I don't store it in the NanoVNA. I store it in a PC program (NanoVNA-Saver) as well as a .s2p file and then use scikit-rf to do the processing.
|
On Thu, Dec 8, 2022 at 12:52 PM, Stan Dye wrote:
The normal way to do it on the nanovna is a bit different. You attach the
near end of the coax to the nanovna, then calibrate (using the
open/short/load calibration loads) at the far end of the cable. Then you
attach the antenna at the far end - all measurements then show the
performance of the antenna itself, having compensated for the coax
properties (primarily length and attenuation).
I agree with you that this "de-embedding" the cable method is the most accurate and only needs to be done once for the cable being used. Then the cal file can be saved for later recall. You can alternately use the "edelay" setting on the nanovna to subtract the
length of the cable, if you look up its properties and enter the correct
value for your length of coax. This also is only approximate, and is
similar to what the RigExpert is doing.
The "edelay" method is the least accurate of all the methods because it only compensates for the propagation delay and not the attenuation. It just adjusts the angle of the "reflection coefficient" and not the magnitude which also needs adjustment. Roger
|
On Thu, Dec 8, 2022 at 06:49 AM, Phil, WF3W wrote:
Hello all XMAS-gift hopefuls,
Is there a way/method/technique for subtracting coax length from readings, as
can be done in Rig-Expert's ANTScope, sftwr?
Phil, If you like AntScope2 you can use it with your NanoVNA-H4. RigExpert added support for the -H and -H4 some time ago. Go to Settings and manually connect to the NanoVNA Com port. Some features like TDR and Calibrate are not available. You have to calibrate on the NanoVNA for the range of interest and then input the start/stop frequencies. The Cable Subtract/Add feature does work but I am not a fan of it for the reasons I posted earlier. Make sure you use metric settings as that is what is used cable length entry. Screenshot attached. Roger
|
Yet another method is to measure at the shack end of the feedline. Then, using SimSmith on your PC, propagate what you measure back to the feedpoint. You must know the parameters of your feedline: length, Vp, and type. For HF using anything but RG-174, the loss is pretty insignificant. Dave - W?LEV On Thu, Dec 8, 2022 at 8:02 PM Roger Need via groups.io <sailtamarack= [email protected]> wrote: On Thu, Dec 8, 2022 at 06:49 AM, Phil, WF3W wrote:
Is there a way/method/technique for subtracting coax length from
readings, as
can be done in Rig-Expert's ANTScope, sftwr?
The AntScope2 software by RigExpert allows the user to add or subtract
cable and then make a series of measurements. There is a database of cable
types (RG-58, LMRxxx etc.) to choose from. You select the cable type and
length and it calculates the approximate impedance at the antenna when
measuring at the far cable end (subtraction method). If the measurements
were made at the antenna and you want to know what happens if you add cable
(addition method) it will calculate the approximate impedance at the cable
end. The reason I say approximate is the attenuation and velocity of
propagation are not exactly known due to manufacturing tolerances and vary
with frequency.
The equations to do the impedance transformation are well known. Attached
is an excerpt from the ARRL Radio Amateur's Handbook describing how to do
it. The equation shown will work for the "addition method". To do the
"subtraction method" you need to rearrange the terms so that ZLoad is the
desired calculation. The length of the cable, velocity of propagation,
and attenuation for the frequency being used are inputs (some unit
conversion required).
Roger
-- *Dave - W?LEV* -- Dave - W?LEV
|
The normal way to do it on the nanovna is a bit different. You attach the
near end of the coax to the nanovna, then calibrate (using the
open/short/load calibration loads) at the far end of the cable. Then you
attach the antenna at the far end - all measurements then show the
performance of the antenna itself, having compensated for the coax
properties (primarily length and attenuation). This is more accurate than
the RigExpert's calculation, since as Roger noted, RigExpert uses a data
base of cable types - but any given actual cable will only be 'close' to
the data base values, whereas using the nanovna calibration measures the
actual values.
You can alternately use the "edelay" setting on the nanovna to subtract the
length of the cable, if you look up its properties and enter the correct
value for your length of coax. This also is only approximate, and is
similar to what the RigExpert is doing. You can also use the nanovna to
measure the cable's electrical length, and use that value to set the
edelay, but those are all manual steps, so calibration at the end of the
cable is usually just as easy.
Stan
toggle quoted message
Show quoted text
On Thu, Dec 8, 2022 at 6:49 AM Phil, WF3W <WF3W@...> wrote: Hello all XMAS-gift hopefuls,
Is there a way/method/technique for subtracting coax length from readings,
as can be done in Rig-Expert's ANTScope, sftwr?
73
Phil, WF3W
|
David Wilcox K8WPE
KK4ITX John
Larry McElhiney
Roger Need
