Re: NEgative resistance for S11 port antenna measurement
Have you tried reducing the sweep range? It might be informative to reduce the sweep to 25MHz starting at 300MHz, OSL calibrate at the measurement plane and run the sweep. Then move up 25MHz and run again. This will help focus down on where the issue is. Instinctively, I agree with Manfred, but there may be some oddity creeping in from the nano internals on such a wide sweep.
Steve
G0AIN
|
Re: NEgative resistance for S11 port antenna measurement
You might be receiving strong signals with that antenna, that interfere with the nanoVNA's measurements. If that's the case, at least some of the excursions to negative resistance should not repeat on every scan.
If that's not the problem, it might be just noise.
|
Re: NEgative resistance for S11 port antenna measurement
What am i doing wrong ? ** I think it would have been relevant, since you use nanaovna-saver, to post your .s1p files with your participation. -- F1AMM Fran?ois -----Message d'origine----- De la part de kellogs Envoyé : vendredi 28 mars 2025 21:30
|
NEgative resistance for S11 port antenna measurement
Hello,
v0.7.3 on Windows;
Already had my nanovna calibrated in two range: 30 MHz around 315 and another 30 MHz around 434; used an average of 10 sweeps with ~saver which has produced some partly negative values for resistance - measured two (almost) identical antennas, without any in- ~saver calibration. I can say for sure that nanoVNA did not report any negative resistances.
Having seen the failure, i have then set an interval from ~225MHz to 525MHz, some ~300 points, calibrated inside ~saver, remeasured the two antennas with generally different results, but still having ranges of frequency where the resistance was again negative. I have not properly checked what the naonoVNA was reporting on its screen for the frequency range.
What am i doing wrong ?
Thanks!
|
Re: New HW version 3.6.1 observations and questions
Use Zeetk (SMC5351A + custom mixer, but this option also work on SM_ST device) or MS5351
|
Re: New HW version 3.6.1 observations and questions
In the latest software version: 1.2.43/NanoVNA-H-ZK_20250220.dfu there is an additional generator setting.
Now we have three options in the MODE 1. MS5351 2. ZEETK 3. Si5351.
What to choose with the SMC5351A chip, NanoVNA 3.6.1 SM_ST?
|
Few people on the LibreVNA list did that, maybe ask there. IMHO it's not worth it. Sourcing some of the components is a problem and machining the enclosure is another one. On Fri, 28 Mar 2025 at 08:55, yura717 via groups.io <yura717= [email protected]> wrote: I wonder how much will cost to build LibreVNA / BOM + PCB price /.Thank you
|
I wonder how much will cost to build LibreVNA / BOM + PCB price /.Thank you
|
Re: red LED no longer lights
Clyde,
THANK YOU!!! I did not catch the difference earlier, used the H4 firmware and all is working well now!
Thank you.
Bill WB6YVK
|
Re: red LED no longer lights
If I read your post correctly,
"nanoVNA-H4 hardware build 4.3 using the NanoVNA-H.v1.2.40.bin "
Your problem is you used the WRONG firmware!!!
You can not use "H" firmware on a "H4"!!!!!
And expect it to work correctly.
They are two different NVA's
First, download and install the Firmware for the NanoVNA H4, then try it.
Clyde KC7BJE
|
Re: Running NanoVNA Saver (or other software) on Linux
Just did a quick search re nanovna-saver and mint and found a set of instructions for you to follow here: ________________________________ From: [email protected] < [email protected]> on behalf of M0CNL via groups.io <m1cxz.m0cnl@...> Sent: Monday, March 24, 2025 6:50:26 PM To: [email protected] < [email protected]> Subject: Re: [nanovna-users] Running NanoVNA Saver (or other software) on Linux Yes Sudo was what I meant to type but either I fat fingered it on my phone or it was auto corrected to Suso. So sorry about that. ________________________________ From: [email protected] < [email protected]> on behalf of Stephen Thornber via groups.io <stephen.g6sga@...> Sent: Sunday, March 23, 2025 8:09:50 PM To: [email protected] < [email protected]> Subject: Re: [nanovna-users] Running NanoVNA Saver (or other software) on Linux SUSO ………. sudo perhaps ? On Sun, 23 Mar 2025 at 20:05, k6whp via groups.io <k6whp= [email protected]> wrote: My apologies for being so dense but I cannot seem to unpack the advice
given here. I am running Linux Mint 21.0 something and have been able to
install other packages handily, but cannot get my head around what it takes
to install NanoVNA-saver per the instructions here.
Per your instructions..
<11:44|~> Suso apt-cache search nanovna
Suso: command not found
<11:44|~>sudo apt-cache search nanovna
[sudo] password for whp:
<11:45|~> {{{{nothing occurred after password negotiated}}}}
..howeverr, none of this worked out so, in looking for alternatives, I
found this, and was able to bring saver up.
panda@vika:~$ history
1 sudo apt update
2 sudo apt install python3-pip
3 pip3 install
4 echo 'export PATH=$PATH:/home/panda/.local/bin' >> ~/.bashrc
5 source ~/.bashrc
6 NanoVNASaver
Now my question is how does one connect to the NanoVNA like one would do
searching out the Com port on Windows?
--
William, k6whp
--------------------
"Cheer up, things could get worse. So I cheered up and things got worse."
|
Re: Running NanoVNA Saver (or other software) on Linux
Yes Sudo was what I meant to type but either I fat fingered it on my phone or it was auto corrected to Suso. So sorry about that. ________________________________ From: [email protected] < [email protected]> on behalf of Stephen Thornber via groups.io <stephen.g6sga@...> Sent: Sunday, March 23, 2025 8:09:50 PM To: [email protected] < [email protected]> Subject: Re: [nanovna-users] Running NanoVNA Saver (or other software) on Linux SUSO ………. sudo perhaps ? On Sun, 23 Mar 2025 at 20:05, k6whp via groups.io <k6whp= [email protected]> wrote: My apologies for being so dense but I cannot seem to unpack the advice
given here. I am running Linux Mint 21.0 something and have been able to
install other packages handily, but cannot get my head around what it takes
to install NanoVNA-saver per the instructions here.
Per your instructions..
<11:44|~> Suso apt-cache search nanovna
Suso: command not found
<11:44|~>sudo apt-cache search nanovna
[sudo] password for whp:
<11:45|~> {{{{nothing occurred after password negotiated}}}}
..howeverr, none of this worked out so, in looking for alternatives, I
found this, and was able to bring saver up.
panda@vika:~$ history
1 sudo apt update
2 sudo apt install python3-pip
3 pip3 install
4 echo 'export PATH=$PATH:/home/panda/.local/bin' >> ~/.bashrc
5 source ~/.bashrc
6 NanoVNASaver
Now my question is how does one connect to the NanoVNA like one would do
searching out the Com port on Windows?
--
William, k6whp
--------------------
"Cheer up, things could get worse. So I cheered up and things got worse."
|
Locked
Re: McAFee Virus Scanner Objects to nanoSaver download from GitHub
I am locking this topic as it has gone far afield of discussion related to NanoVNAs.
|
I have updated the firmware on my nanoVNA-H4 hardware build 4.3 using the NanoVNA-H.v1.2.40.bin file and STM32cube software, and notice that
the red battery LED no longer lights when charging or unit is turned on. Same effect after I upgraded my TinySA Ultra....no longer red LED function.
Is that normal?
|
Locked
Re: McAFee Virus Scanner Objects to nanoSaver download from GitHub
Quite right, however backdoors are not the usual attack vector for viruses and malware. The attack is tricking users into executing something they shouldn't. On Mon, 24 Mar 2025 03:23:56 -0400 "William McLaughlin via groups.io" <indispensibill@...> wrote: As I understand it, back doors were (and presumably, still are) created by
programmers as a convenience. They use them because it's quicker for
getting into a system than going through the login procedure and all the
other entries necessary for gaining access to the code when they want to
fix bugs, make modifications, etc. As I said, they're just a convenience
but they have to be kept secret so hackers can't use them to gain access
(as they undoubtedly have at times). -- 73 -Jim NU0C
|
Locked
Re: McAFee Virus Scanner Objects to nanoSaver download from GitHub
History is interesting, you can learn a lot from it. I heard that one of the first times the term ‘bug’ was used involved a moth that got into a relay, keeping it from operating.
This group is great at teaching us how to use and fix a VNA. Most of it is over my head but I am learning from it.
--
Sent from Canary ()
toggle quoted message
Show quoted text
On Monday, Mar 24, 2025 at 3:23 AM, William McLaughlin via groups.io <indispensibill@... (mailto:indispensibill@...)> wrote:
As I understand it, back doors were (and presumably, still are) created by
programmers as a convenience. They use them because it's quicker for
getting into a system than going through the login procedure and all the
other entries necessary for gaining access to the code when they want to
fix bugs, make modifications, etc. As I said, they're just a convenience
but they have to be kept secret so hackers can't use them to gain access
(as they undoubtedly have at times).
Back in the late 1980s I heard about a prankster who, when designing a
large company's software, added some code that at random times would freeze
all of the company's terminals and display the following message: *Hello.
Can I have a cookie?* Their entire system remained locked with this
message on all of their screens until, after what must've been a lot of
trial and error, someone discovered you could unlock the computers by
entering "*Here. Have a cookie*." After that, the system would return to
normal until the next time.
As the story goes, the code was so deeply embedded in their software that
it was cheaper to just instruct all of their employees on the proper
response than to dig through millions of lines of code to fix it. Might be
apocryphal but it's amusing.
73,
Mac
AB3RV
On Mon, Mar 24, 2025 at 1:50?AM Gary H Thompson via groups.io <garythomjw=
[email protected]> wrote:
If you read it again, you will see that I said what a back door is, I
didn’t say it was a virus, it was how a virus was put in computers. Didn’t
mean to start an argument.
--
Sent from Canary ()
On Sunday, Mar 23, 2025 at 11:18 PM, Jim Shorney via groups.io <jimNU0C= [email protected] (mailto:jimNU0C@...)> wrote:
A backdoor is not a virus. Viruses and malware are created by
programmers with malicious intent in order to spread mayhem or for
financial gain. A lot of it is offshore these days. It may be fun to poke
at the AV vendors but this stuff is real.
On Sun, 23 Mar 2025 22:19:45 -0400
"Gary H Thompson via groups.io" <garythomjw@...> wrote:
You are right! Most virus’s were created by computer repair/programing
techs. It started a long time ago, while working on a banks system, the
tech put in what they call a ‘back door’. It’s a hidden password so he
could access the system without anyone knowing. Putting a problem in that
would activate in three months, he had steady work without anyone knowing.
When he got called, he was a hero because he could fix it. It wasn’t
long before he had all the work he wanted.
It’s a sad time we live in!
--
Sent from Canary ()
On Sunday, Mar 23, 2025 at 10:02 PM, Michael Robinson via groups.io
<mlrobinson1953@... (mailto:mlrobinson1953=
[email protected])> wrote:
I'm gonna play Devil's Advocate here and suggest that all supposed
virii
are manufactured by the antivirii companies to induce the fear of a
viral
attack on your computer in order to sell you their ready-made
solution for
the virii in question.
--
73
-Jim
NU0C
|
Locked
Re: McAFee Virus Scanner Objects to nanoSaver download from GitHub
As I understand it, back doors were (and presumably, still are) created by programmers as a convenience. They use them because it's quicker for getting into a system than going through the login procedure and all the other entries necessary for gaining access to the code when they want to fix bugs, make modifications, etc. As I said, they're just a convenience but they have to be kept secret so hackers can't use them to gain access (as they undoubtedly have at times). Back in the late 1980s I heard about a prankster who, when designing a large company's software, added some code that at random times would freeze all of the company's terminals and display the following message: *Hello. Can I have a cookie?* Their entire system remained locked with this message on all of their screens until, after what must've been a lot of trial and error, someone discovered you could unlock the computers by entering "*Here. Have a cookie*." After that, the system would return to normal until the next time. As the story goes, the code was so deeply embedded in their software that it was cheaper to just instruct all of their employees on the proper response than to dig through millions of lines of code to fix it. Might be apocryphal but it's amusing. 73, Mac AB3RV On Mon, Mar 24, 2025 at 1:50?AM Gary H Thompson via groups.io <garythomjw= [email protected]> wrote: If you read it again, you will see that I said what a back door is, I
didn’t say it was a virus, it was how a virus was put in computers. Didn’t
mean to start an argument.
--
Sent from Canary ()
On Sunday, Mar 23, 2025 at 11:18 PM, Jim Shorney via groups.io <jimNU0C= [email protected] (mailto:jimNU0C@...)> wrote:
A backdoor is not a virus. Viruses and malware are created by
programmers with malicious intent in order to spread mayhem or for
financial gain. A lot of it is offshore these days. It may be fun to poke
at the AV vendors but this stuff is real.
On Sun, 23 Mar 2025 22:19:45 -0400
"Gary H Thompson via groups.io" <garythomjw@...> wrote:
You are right! Most virus’s were created by computer repair/programing
techs. It started a long time ago, while working on a banks system, the
tech put in what they call a ‘back door’. It’s a hidden password so he
could access the system without anyone knowing. Putting a problem in that
would activate in three months, he had steady work without anyone knowing.
When he got called, he was a hero because he could fix it. It wasn’t
long before he had all the work he wanted.
It’s a sad time we live in!
--
Sent from Canary ()
On Sunday, Mar 23, 2025 at 10:02 PM, Michael Robinson via groups.io
<mlrobinson1953@... (mailto:mlrobinson1953=
[email protected])> wrote:
I'm gonna play Devil's Advocate here and suggest that all supposed
virii
are manufactured by the antivirii companies to induce the fear of a
viral
attack on your computer in order to sell you their ready-made
solution for
the virii in question.
--
73
-Jim
NU0C
|
Locked
Re: McAFee Virus Scanner Objects to nanoSaver download from GitHub
If you read it again, you will see that I said what a back door is, I didn’t say it was a virus, it was how a virus was put in computers. Didn’t mean to start an argument.
--
Sent from Canary ()
toggle quoted message
Show quoted text
On Sunday, Mar 23, 2025 at 11:18 PM, Jim Shorney via groups.io <jimNU0C@... (mailto:jimNU0C@...)> wrote:
A backdoor is not a virus. Viruses and malware are created by programmers with malicious intent in order to spread mayhem or for financial gain. A lot of it is offshore these days. It may be fun to poke at the AV vendors but this stuff is real.
On Sun, 23 Mar 2025 22:19:45 -0400
"Gary H Thompson via groups.io" <garythomjw@...> wrote:
You are right! Most virus’s were created by computer repair/programing techs. It started a long time ago, while working on a banks system, the tech put in what they call a ‘back door’. It’s a hidden password so he could access the system without anyone knowing. Putting a problem in that would activate in three months, he had steady work without anyone knowing.
When he got called, he was a hero because he could fix it. It wasn’t long before he had all the work he wanted.
It’s a sad time we live in!
--
Sent from Canary ()
On Sunday, Mar 23, 2025 at 10:02 PM, Michael Robinson via groups.io <mlrobinson1953@... (mailto:mlrobinson1953@...)> wrote:
I'm gonna play Devil's Advocate here and suggest that all supposed virii
are manufactured by the antivirii companies to induce the fear of a viral
attack on your computer in order to sell you their ready-made solution for
the virii in question. --
73
-Jim
NU0C
|
Locked
Re: McAFee Virus Scanner Objects to nanoSaver download from GitHub
A backdoor is not a virus. Viruses and malware are created by programmers with malicious intent in order to spread mayhem or for financial gain. A lot of it is offshore these days. It may be fun to poke at the AV vendors but this stuff is real. On Sun, 23 Mar 2025 22:19:45 -0400 "Gary H Thompson via groups.io" <garythomjw@...> wrote: You are right! Most virus’s were created by computer repair/programing techs. It started a long time ago, while working on a banks system, the tech put in what they call a ‘back door’. It’s a hidden password so he could access the system without anyone knowing. Putting a problem in that would activate in three months, he had steady work without anyone knowing.
When he got called, he was a hero because he could fix it. It wasn’t long before he had all the work he wanted.
It’s a sad time we live in!
--
Sent from Canary ()
On Sunday, Mar 23, 2025 at 10:02 PM, Michael Robinson via groups.io <mlrobinson1953@... (mailto:mlrobinson1953@...)> wrote:
I'm gonna play Devil's Advocate here and suggest that all supposed virii
are manufactured by the antivirii companies to induce the fear of a viral
attack on your computer in order to sell you their ready-made solution for
the virii in question. -- 73 -Jim NU0C
|
Locked
Re: McAFee Virus Scanner Objects to nanoSaver download from GitHub
You are right! Most virus’s were created by computer repair/programing techs. It started a long time ago, while working on a banks system, the tech put in what they call a ‘back door’. It’s a hidden password so he could access the system without anyone knowing. Putting a problem in that would activate in three months, he had steady work without anyone knowing.
When he got called, he was a hero because he could fix it. It wasn’t long before he had all the work he wanted.
It’s a sad time we live in!
--
Sent from Canary ()
toggle quoted message
Show quoted text
On Sunday, Mar 23, 2025 at 10:02 PM, Michael Robinson via groups.io <mlrobinson1953@... (mailto:mlrobinson1953@...)> wrote:
I'm gonna play Devil's Advocate here and suggest that all supposed virii
are manufactured by the antivirii companies to induce the fear of a viral
attack on your computer in order to sell you their ready-made solution for
the virii in question. This includes Microsoft products, as well. Time to
use a little common sense here, folks. I am slowly making the transition
to Linux OS's. Currently using Linux Mint Cinnamon, Debian 12.9.0 with the
Mate Desktop and Kali Linux. No viruses detected by Clam AV.
Michael L Robinson, KC0TA
“In the beginning of a change the Patriot is a scarce man, and brave, and
hated and scorned. When his cause succeeds, the timid join him, for then it
costs nothing to be a Patriot.” ― Mark Twain
When Tyranny becomes Law, Revolution becomes Duty!
On Sun, Mar 23, 2025 at 8:48?PM Gary H Thompson via groups.io <garythomjw=
[email protected]> wrote:
That’s great! I do a lot of computer work too. Back in the day, my wife
would play the ‘ghost buster’ song and call me the virus buster.
Glad you got it fixed!
--
Sent from Canary ()
On Sunday, Mar 23, 2025 at 8:14 PM, William French - AA1BF via groups.io <bill.french.epsom@... (mailto:bill.french.epsom=
[email protected])> wrote:
My grandson cleared the "McAfee" pop-ups on my computer today.
He is a computer services professional.
He did what was stated above, clearing cookies and related stuff from the
Chrome browser and the problem went away. He said that he has to do this a
couple
of times a week for some of his clients.
On Sun, Mar 23, 2025 at 6:20?PM Chuck Cole via groups.io <cncole=
[email protected]> wrote:
Gary, you're probably right, but MacAfee is the only ID I could find in
many intrusions and I could not find anything to block. I examined and
searched extensively.
On Sun, Mar 23, 2025 at 6:03?PM Gary H Thompson via groups.io <garythomjw=
[email protected]> wrote:
It’s probably not McAfee, it’s a virus that try's to get you to go to
their site, thinking you are going to McAfee. The message is the
virus.
Clear your browser cookies and browser history and reboot. If that 诲辞别蝉苍’迟
work, use Google to find other things to try. If you clicked on the
popup
and went to their site, anything you entered is now compromised. Call your
bank and credit card and let them know what happened.
--
Chuck Cole K4TZO
|
Clyde Lambert
Jim Shorney