¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. Nanovna-Users
  2. Messages
Expanded Topics Messages
Date
Emails

 

Hi,

Can I receive emails like a digest just once a week please?

I am snowed under by the emails I am getting.

Thanks

Ken Walker
Re: NanoVNA firmvare, compiled by DiSlord #firmware with MiniSD support #firmware

 

yes, AND in Makefile uncomment the line with UDEFS..

#Enable if install external 32.768kHz clock quartz on PC14 and PC15 pins on STM32 CPU
#UDEFS+= -DVNA_USE_LSE
Re: NanoVNA firmvare, compiled by DiSlord #firmware with MiniSD support #firmware

 

Sorry for the dumb question, but if I want to build the latest firmware for the H4 with RTC & SD Card, I need to uncomment the #defines on lines 25 & 27 of nanovna.h and then run make?

Thanks,
Brian
Re: Identifying ferrite materials with S11 measurements

 

Graeme, I've had the identical experience, even using the HP 8753C VNA
calibrated properly. I don't get it, either.

Dave - W?LEV

On Tue, Jul 14, 2020 at 4:12 AM Graeme Jury <gvjury@...> wrote:

Hello Group,

Yes I know that this has been pretty fully dealt with before and I have
read all the posts but I still can't get a consistently good result.

The method that I used was to tightly wrap a single turn of 24 swg wire
around the core (or 1 turn looped through the balun core) and soldered with
minimum lead length to an sma female connector and run an S11 R/w & X/w. I
tested on a range of type 43 cores and the FT50-43 and BN43-202 matched
well plus the X = R crossover came out where I expected but the others came
out widely different and seemed to give results more like I would expect
from type 61 material.

I also experimented with an FT240-43 core and could not get the X and R
lines to crossover with 1 turn at all so I tried 2 turns and got a
crossover at around 80 MHz and 3 turns at about 25 MHz (going from memory
here as I didn't screenshot this) so I am missing something entirely I
think. I will look into Jeff Anderson's work

and see if there is a better approach that I can make but it means that I
will need to come to grips with matlab which I have not done up til now so
there will be a time delay until I get some results.

Naturally I am hoping that someone will come up with "Hey Graeme, you
didn't do this" as I am feeling that there is more that I have not done
like maybe a low inductance copper tape around the core or something.

73, Graeme ZL2APV



--
*Dave - W?LEV*
*Just Let Darwin Work*
Re: NanoVNA Saver 0.3.3 or 0.3.4

 

ps.: /g/nanovna-users/attachment/10650/0/Installing%20Python%20on%20Windows7-32%20for%20nanoVNA-Saver.pdf

--
*** If you are not part of the solution, then you are the problem. ( ) ***
Re: NanoVNA Saver 0.3.3 or 0.3.4

 

I confirm that 0.36 works under Python 3.7.4 installed on windows 32 bit. You need to install Python and the required modules in advance. See the required modules in the NanoVNA Saver .zip / requirement.txt

I note that versions 0.3.0 ... 0.3.4 do not work this way.
73, Gyula HA3HZ
--
*** If you are not part of the solution, then you are the problem. ( ) ***

NanoVNA_Saver_0.3.6-pre.png

To Dave Daniel #rant

vaclav_sal
 

What a cop-out!
How about instead of "taking you ball and going home " DO SOMETHING constructive , even NON TECHNICAL for amateur radio?

Amateur radio operators are known for rag chewing - also know as " chewing the fat " by normal folks.

Would it destroy the technical integrity of this group to just let them "blow off the steam" once a while ?
( You do not have to read it or participate and memory is cheap )

Cheers

This message will self destruct when I get a "round tuit"
Re: NanoVNA Saver 0.3.3 or 0.3.4

 

On 14.07.20 09:43, pgc1682@... wrote:
Hi,

I have same problem, my ultra portable laptop 32 bit only w10.

Lajos
You can stll try to install from source.

First you need python from the microsoft-store.
Then clone the git (or download as zip).

In the source directory running following in the commands in
the console.

python -m pip install --upgrade pip setuptools
pip install -r requirements.txt
then
python nanovna-saver.py

should start the program.

But some Windows guys can surly give more hints.

73
Holger, DG5DBH
Re: noise on screen

 

Hi,
Like the others have written, its the measured phase of the S21
measurement, and as nothing is connected between ch0 and ch1 you only see
the noise in the ch1 receiver.
It also looks like you don't have a good calibration. If there is nothing
connected to ch0 in the picture, you need to redo it.
Remember to always press reset before you start the calibration...

Br,
Askild

On Tue, Jul 14, 2020 at 10:23 AM "Reske, Jim NB3P" <jgreske@...>
wrote:

Hi, i just purchased a nano vna and can't seem to get it working
properly. When i ruen the unit on i get only what i can describe as noise
on the screen. When i calibrate the unit, the screen does not go blank but
continues to display the noise. Ive tried resetting the unit but that did
not help. Am i doing something wrongbor di I have a defective unit ? See
the attachment for a photo. JIM NB3P
Locked Re: The Uncertain Future of Ham Radio - IEEE Spectrum

 

All,

I am locking this thread. No further posting will be allowed.

Despite my earlier admonition to keep this technical, there continue to be posts which are entirely non-technical.

DaveD

On 7/10/2020 11:32 PM, Larry Rothman wrote:
Interesting article:

--
This email has been checked for viruses by Avast antivirus software.
Locked Re: The Uncertain Future of Ham Radio - IEEE Spectrum

 

I was holding myself, but finally decided to write my own opinion: I'm
extremely disappointed by some attempts to extinguish enthusiasm, hobby
interests and inquisitive approach of younger generation, by many seasoned
hams, trying to reduce amateur radio to 'what it was': only activity
reserved to some bands and operator skills...Nowadays communicating around
the world and using radio is nothing reserved for exclusive clubs. We all
communicate using Internet and our radio activity, nolens-volens is mostly
on other radio bands. It's convenient. At the same time, great wee thing
like NanoVNA is very much a gift for all hams: affordable device, for
achieving a lot with simple means. I'm myself radio amateur, can use CW and
microphone but choose NOT to spend my time fisting one key and chatting
through noise of dead bands. I have much fun with other technology. Why not
take inexpensive modem, and enjoy hobby with everything from 2G to NBIoT,
with GPS, audio codecs and everything else. Legally using other bands, not
limited to what my callsign buys, but add 5 pounds credit on the SIM card
and buy the rights for my toaster talking around the world, legally on
mobile bands? 73 de Mi6HQA.

On Tue, 14 Jul 2020 at 13:44, Lawrance A. Schneider <llaassllaaass@...>
wrote:

What I wrote was NEVER meant to disparage anyone in particular. Nor was
it meant to start some sort of meaningless word war amongst this or any
group. I guess I was just letting off steam. I apologize!

I will sign this in a way I've never used until today: larry KC1FDF
Re: NanoVNA firmvare, compiled by DiSlord #firmware

 

On Tue, Jul 14, 2020 at 01:07 PM, DiSlord wrote:


for battery voltage need add correction by command
vbat_offset xxxx
Ok thanks!

On display should add window
<-BRIGHTNESS->
Move leveler left or right for ajust it
Ok, I did with stylus.. grrh..
Locked Re: The Uncertain Future of Ham Radio - IEEE Spectrum

 

What I wrote was NEVER meant to disparage anyone in particular. Nor was it meant to start some sort of meaningless word war amongst this or any group. I guess I was just letting off steam. I apologize!

I will sign this in a way I've never used until today: larry KC1FDF
Re: NanoVNA firmvare, compiled by DiSlord #firmware

 

Definitely looking nicer ;)

I like the circle indicators.
Use above 900Mhz

Peter G8VXY
 

OK, I may have Bo-Bo-ed I that I thought the NanoVNA went up to 1.5Ghz plus, but only after it arrived did I spot that it supposedly only worked up to 900Mhz, yet I had already tried it out at a setting above 900Mhz, (800-1200Mhz) testing a filter for 1090Mhz. now I have never used a VNA before and it did seem to at least partially work in that frequency response was what I was expecting but the resistance SWR seemed very flat.

The Version details say's NanoVNA-H Version 0.2.2-1

Can the firmware be upgraded? or does the board need hardware upgrading? and what programmer would I need?
Re: NanoVNA firmvare, compiled by DiSlord #firmware

 

for battery voltage need add correction by command
vbat_offset xxxx
It come from H version value can be different from diode drop voltage

First set vbat_offset 0 (see current value on display or run command vbat, result is for example 3.768V so 3768)
vbat_offset 0
vbat
Measure correct voltage on battery (for example 4.200V so value is 4200)
And add correction 4200-3768=432
vbat_offset 432
Save settings
saveconfig
Also it crashes when messing with Brightness..
On display should add window
<-BRIGHTNESS->
Move leveler left or right for ajust it
Push leveler button for confirm
Save if need (Config->Save)
Re: NanoVNA firmvare, compiled by DiSlord #firmware

 

@DiSlord - I've built your latest H4 branch with your new ui - nice! (w/ no SDcard and no xtal/RTC).
The battery voltage (on the Version screen) shows here 4.512V, is that correct? (should be <4.2V afaik).
Also it crashes when messing with Brightness..
Re: NanoVNA firmvare, compiled by DiSlord #firmware

 

Looks very good, waiting for the binaries
Re: Identifying ferrite materials with S11 measurements

 

Hi Graeme,
Please read this message where the link leads to the solution: /g/nanovna-users/message/15131
I can see that manufacturers measure over a larger range, why didn¡¯t you measure the way ferrite manufacturers give the curves.
Then the curve of the curve is more visible.

73, Gyula HA3HZ
--
*** If you are not part of the solution, then you are the problem. ( ) ***
Re: Identifying ferrite materials with S11 measurements

 

FYI -

24721 - 24740 of 39697