Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- Nanovna-Users
- Messages
Search
Latest DiSlord's firmware where I find it
Hello
I have a nanoVNA SAA-2N HW V2_2 and I like to use the newest version of DiSlord firmware. On this occasion I want to thank him for the hard work he is doing. DiSlord's latest firmware version seems to be V1.3.12 but I can't find it. Can anyone help me with a link to it? Photos of my SAA-2N HW V2_2 for proper ID below. Thanks for any help. -- Eugen? - YO9WHI |
Re: RF Demo Kit for NanoVNA H4?
#nanovna-h4
On 01/02/2023 20:25, Donald S Brant Jr wrote:
Get. The. Proper. Tool.Do you have a URL for purchase, please? A quick search on Amazon and AliExpress was fruitless, and eBay gave: Harley Davidson tool box mount kit U FL EL VT 31-0578 which wasn't right. Otherwise ~US $36. 73, David GM8ARV -- SatSignal Software - Quality software for you Web: Email: david-taylor@... Twitter: @gm8arv |
Re: Start/stop points for HF SWR measurement
For your first question, regarding how wide is too wide for HF VSWR
toggle quoted message
Show quoted text
measurements: I have one saved calibration setup from 1MHz - 30MHz, which I use to see the basic characteristics of a multiband HF vertical antenna (i.e. do I see good dips on all the bands it is made for). Then I often set the range smaller to see more closely what the VSWR is at my desired part of just one or two bands. This works fine, no need to recalibrate for this general VSWR use. Note that the nanovna firmware interpolates quite well between calibration points, so reasonably accurate VSWR results are given. Note also that the frequency position of the VSWR 'dips' (minimums) is not dependent on calibration - finer calibration will only give a bit more accuracy of the value of the SWR at that frequency. So for this HF VSWR purpose, a single saved calibration works well across the HF bands. You can experiment with this, by doing a detailed calibration for just one band, say 13.5-14.5MHz, and comparing the VSWR value with what you get from the 1-30MHz calibration, and you won't see large differences. However, if you are doing other measurements, e.g. ones that require specific complex impedance values, you should always calibrate over the frequency range you are measuring. For your second question, regarding number of points: Note that with recent firmware, many nanovna hardware models support 401 points. It sounds like that is what you have, since you are getting 2.5kHz steps across a 1MHz range. The actual number of points used is settable via the menus. Which version of firmware do you have? and which model of nanovna? (can be seen on the startup screen, or on the config->version menu screen for more recent firmware). I hope that helps a bit. On Wed, Feb 1, 2023 at 5:35 PM Bill Klymus W5PB <bktx75@...> wrote:
I know that the nanoVNA has about 101 (measurement points between the |
Re: Start/stop points for HF SWR measurement
Actually, with 101 points there are 100 spaces, so divide the range by 100 to see the spacing.
I didn't write the code, but I suspect that the graphics engine interpolates between actual measurement points. If you set the range so that the spacing is too wide, you may miss something in between the points. |
Start/stop points for HF SWR measurement
I know that the nanoVNA has about 101 (measurement points between the start and stop frequencies. When using it for SWR measurements of an HF antenna, how wide is too wide? Should each band be framed separately? Or is it ok to combine bands to save memory slots? For example, instead of having separate memories for 20, 30, and 40 meters, would I still get a useable reading if I combined them into one memory (start at 7 MHz and stop at 14.35).
Which brings up another question: If I set the start frequency at, say 6.5 MHz and the stop frequency at 7.5, and there are 101 measurement points, that means each point should be 9.9KHz apart. However, the marker moves in 2.5 KHz increments. Is it just implying what the SWR should be at these points? |
Re: Group Co-ownership Change
You can always spot the programmers... If they need to say go to:
toggle quoted message
Show quoted text
They actually say: Goto: ... 73, and thanks, Dave (NK7Z) ARRL Volunteer Examiner ARRL Technical Specialist, RFI ARRL Asst. Director, NW Division, Technical Resources On 2/1/23 15:30, Tim Dawson wrote:
struct Daves |
Re: Group Co-ownership Change
They are probably of a "certain age".
toggle quoted message
Show quoted text
73, Gary - W6GVS At 07:19 PM 2/1/2023, you wrote:
Really???? |
Re: Group Co-ownership Change
Really????
toggle quoted message
Show quoted text
Dave E On Thu, Feb 2, 2023 at 12:10 AM Dave Daniel <kc0wjn@...> wrote:
We are all older than 25.-- *Dave - W?LEV* --
Dave - W?LEV |
Re: Group Co-ownership Change
We are all older than 25.
toggle quoted message
Show quoted text
DaveD On Feb 1, 2023, at 18:56, W0LEV <davearea51a@...> wrote: |
Re: Group Co-ownership Change
Yes, I've heard rumored that one could determine one's age by noting the
toggle quoted message
Show quoted text
first name. Yes, Dave D and Dave E are "about" the same age (we used to work together). How about Dave F? Dave E - W?LEV On Wed, Feb 1, 2023 at 11:06 PM Dave Daniel <kc0wjn@...> wrote:
Yeah, Dr. Seuss even wrote a story about ¡°too many Daves¡±.-- *Dave - W?LEV* --
Dave - W?LEV |
Re: Group Co-ownership Change
struct Daves
toggle quoted message
Show quoted text
{ char First_Name[50]; char Surname[50]; char purpose[100]; int dave_id; } daves; On February 1, 2023 5:16:00 PM CST, "Dave (NK7Z)" <dave@...> wrote:
Clearly you have not programmed enough... Should have ben --
Sent from my Android device with K-9 Mail. Please excuse my brevity. |
Re: Group Co-ownership Change
Clearly you have not programmed enough... Should have ben
toggle quoted message
Show quoted text
Dave0, Dave1, and Dave2... :)( 73, and thanks, Dave (NK7Z) ARRL Volunteer Examiner ARRL Technical Specialist, RFI ARRL Asst. Director, NW Division, Technical Resources On 2/1/23 15:06, Dave Daniel wrote:
Yeah, Dr. Seuss even wrote a story about ¡°too many Daves¡±. |
Re: Group Co-ownership Change
Dave? Daves not here, man . . . :-)
toggle quoted message
Show quoted text
On February 1, 2023 5:06:24 PM CST, Dave Daniel <kc0wjn@...> wrote:
Yeah, Dr. Seuss even wrote a story about ¡°too many Daves¡±. --
Sent from my Android device with K-9 Mail. Please excuse my brevity. |
Re: Group Co-ownership Change
Yeah, Dr. Seuss even wrote a story about ¡°too many Daves¡±.
toggle quoted message
Show quoted text
You¡¯ll notice that it is now DaveD, DaveE and DaveF. DaveD On Feb 1, 2023, at 18:01, Dave (NK7Z) <dave@...> wrote: |
Re: Group Co-ownership Change
Not another "Dave"...
toggle quoted message
Show quoted text
Welcome, Dave, (W0LEV) 73, and thanks, Dave (NK7Z) ARRL Volunteer Examiner ARRL Technical Specialist, RFI ARRL Asst. Director, NW Division, Technical Resources On 2/1/23 12:55, Dave Daniel wrote:
All, |
Re: RF Demo Kit for NanoVNA H4?
#nanovna-h4
On Wed, Feb 1, 2023 at 09:25 PM, Donald S Brant Jr wrote:
If you read /g/nanovna-users/wiki/16592 there is explaied how to handle the connector, e.g. see attached picture. 73, Rudi DL5FA |
to navigate to use esc to dismiss