¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
Date

Re: NanoVNA USB C connector is stuck

 

Hi Anne,
Which end is stuck - the PC or the Nano?
Nanovna end:?
Just wiggle it side to side carefully while pulling on it - no special pliers needed - BUT - be aware the socket is a surface-mounted part and you can break the whole assembly off the board with any twisting or bending!
PC end:?
Pull with pliers straight out - there are two small tabs on the socket that may be caught in the plug.
I hope this helps.
,,,Larry

On Sunday, July 19, 2020, 12:08:39 p.m. EDT, Anne Ranch <anneranch2442@...> wrote:

Hello,
new user here.
After my new NanoVNA passed? "out of box" check I need to unplug the USB connector.
It won't budge.
Should I get a bigger hammer?
Anne


Re: NanoVNA USB C connector is stuck

 

Hi Anne,

Use some pliers, but be very careful...... Officially you have to use a special tool with controlled torque.

Jos


Op 19-7-2020 om 17:42 schreef Anne Ranch:

Hello,
new user here.
After my new NanoVNA passed "out of box" check I need to unplug the USB connector.
It won't budge.
Should I get a bigger hammer?
Anne


NanoVNA USB C connector is stuck

Anne Ranch
 

Hello,
new user here.
After my new NanoVNA passed "out of box" check I need to unplug the USB connector.
It won't budge.
Should I get a bigger hammer?
Anne


Re: NanoVNA firmware user interface mod #mods

 

Fixed scan_bin byte order, now proper little endian.


Re: NanoVNA Saver 0.3.3 or 0.3.4

 

ps .: copy the link in the message in its entirety so that you can download it. You cannot download it by clicking on it.
--
*** If you are not part of the solution, then you are the problem. ( ) ***


Re: NanoVNA Saver 0.3.3 or 0.3.4

 

Hi Joe Joncas,

You can also use the latest (v0.3.6) version of nanoVNA-Saver on your Windows 32-bit machine if you run it under Python.
To do this, you need to install Python on Windows. Description here: /g/nanovna-users/attachment/10650/0/Installing Python on Windows7-32 for nanoVNA-Saver.pdf
In the group wiki (/g/nanovna-users/wiki) you will find the description under the heading NanoVNASaver, where you can download and read the necessary information by clicking on the blue text.
Once you have installed Python, you will download nanovna-saver 0.3.6 (). You unzip this to the C drive and see what modules need to be installed under Python in "requirements.txt" for nanoVNASaver to work well. The previously referenced Python installation is described in pdf. You will install these step by step and then the nanovna-saver will work on windows 32 bits as well.
It seems Holger can¡¯t or doesn¡¯t want to do this to make the latest nanovna saver work on windows 32-bit machines without Python.
If you want to use it on your MacBook, you can find a "Search" button in the forum where you're right now. Type "macBook" here and the information found there will help you with what you need to do.
I enclose some images, these are screenshots taken on a Windows 32-bit machine and under Python 3.7.4.
I hope I was able to help you get started.

73, Gyula HA3HZ
--
*** If you are not part of the solution, then you are the problem. ( ) ***


Re: hi all...VNA noob here, encountering a problem I haven't seen before

John Cunliffe W7ZQ (x-N2NEP)
 

Take a fine needle and gently bend the center connections on the SMA jack back together,


Re: NanoVNA firmware user interface mod #mods

 

Added a new serial command to fetch the scan data in raw binary format rather than inefficient text based stream .. helps speed up the serial transfer rate for PC software scan updates.

usage: scan_bin {start(Hz)} {stop(Hz)} [points] [outmask]

binary format returned (little endian) with n outmask of "7" (full data):

2-byte (16-bit) integer "mask" (LS-3 bits used to indicate the following data types)
2-byte (16-bit) integer "number of points" to follow
{
4-byte (32-bit) integer "frequency"
4-byte (32-bit) floating point "s11-real"
4-byte (32-bit) floating point "s11-imag"
4-byte (32-bit) floating point "s21-real"
4-byte (32-bit) floating point "s21-imag"
}

As usual typing "help" on the command line returns the full list of available serial commands.


Re: New H4 Case Problem Solution

 

Super Glue has great strength and one Weakness. I use a lot of Superglue when I turn bowls. I buy it by the pint. Superglue will not take a shear force well. I have released a temporary glue joint, with a sharp sideway rap with the palm of my hand. The joint stood up to spinning at 2000 RPM, but not the shear force.

Just a note, if you need to break the joint without damaging the PCB.


On Jul 19, 2020, at 8:05 AM, John <k9ka@...> wrote:

was to put a drop of Super-glue
73

de KEoZUW - John


New H4 Case Problem Solution

 

Hello Group;
I have been having random problems with the front case touching the display and causing odd results. Yesterday I found a good solution, which may be of intrerest to many. I noticed that the LCD display was lifted from the main PCB on the Right side, where the ribbon cable folds under. This end of the display was loose and could rise up and touch the case. My solution was to put a drop of Super-glue under each side of the display end and hold it down while the glue set. After that my problem is gone without any washers or shims. FYI
73, John, K9KA


Re: Loading Wrong FW version for Nano

 

Gary,
You cannot brick your Nanovna even if you load the wrong FW as the bootloader is in a normally non-writable area, not flash.?

I've intentionally corrupted the FW in my unit to verify this.?
All Nanovna units that are NOT an H4 or F can take any FW that is NOT labelled as H4 or F. (exception is a few of DiSlord's versions that support external 32khz xtals - you need the xtal installed for that FW)
... Larry


On Sat, 18 Jul 2020 at 8:27 PM, gary.sewell@...<gary.sewell@...> wrote: Before I screw up my Nano, I was wanting to know if you load the wrong version of FW into say H4 that was written for the H, first can you, and if so can you reverse it back to the correct FW?

Gary


Re: Loading Wrong FW version for Nano

 

If you have H version, open nanoVNA, search
Vdd and Boot0 pads
Connect in together and power on nanoVNA, after possible upload new firmware as before
Remove this connection after finish

On H4, possible push leveler button and power on, after upload new firmware


Re: NanoVNA Saver 0.3.3 or 0.3.4

 

Hi Enrique,

NanoVNA-Saver 3.6 runs well on Windows 10 64 bit, at least for me, you
can download it here :


Jos
======================================

Do anyone happen to know whether 0.3.6 incorporates updated for the NanoVNA-F 3 GHz update? I recall you need the version: nanovna-saver-0.3.4-bh5hnu.exe for this firmware update.....

Thanks,
David
--
SatSignal Software - Quality software for you
Web:
Email: david-taylor@...
Twitter: @gm8arv


Re: hi all...VNA noob here, encountering a problem I haven't seen before

 

An easy to prove possible cause:

It could well be a contact (or less probably a PCB jack solder) problem.

Try to rescrew the plugs or gently rock them a bit.

The SMA cal Load received together with my NanoVNA caused that behavior, too. Purchasing another one fixed it.
If the cal Load is bad not at the contact, but inside, you may measure something different to 50 Ohms with a DC Ohm meter.
The cal Open cannot be the reason, as it is open anyway, but the cal Short might also have a contact problem.

73, Hans
DJ7BA

-----Urspr¨¹ngliche Nachricht-----
Von: [email protected] <[email protected]> Im Auftrag von Chuck
Gesendet: Sonntag, 19. Juli 2020 06:59
An: [email protected]
Betreff: Re: [nanovna-users] hi all...VNA noob here, encountering a problem I haven't seen before

On Sat, Jul 18, 2020 at 6:47 PM Tim Reimers KA4LFP <treimers95@...> wrote:

I have a nano VNA that is now refusing to read correctly after calibration it seems.
After running a one port calibration using the calibration assistant,
using the supplied open, short, and load calibration elements
... My normal technique is to do a scan of the Load element at the
frequencies I have selected (before the calibration)... expecting to see a dot n the middle of the Smith chart and a straight 1:1 line on the SWR chart, as I believe the load element should be 50 ¦¸ of pure resistance.
But as of yesterday that is not now how the device responds.
The Smith chart is covered in zigzags instead of even trying to be circles, and the SWR chart looks like a seismograph measuring a 5 on the Richter scale!
Well, several things come to mind. First, did anything of note happen "yesterday" ? It is pretty easy to burn out the port if you accidentally transmit into it, or connect an "active" antenna which feeds back power into the VNA. Simpler question is are you using the correct port? The Nano VNA is not a two port device, it transmits only on one port (I don't really expect this to be the case but in the interest of completeness ...) Do you have a different load? If not do you have a 50 ohm resistor you can solder across a cable and plug that in and see what you see?

Things that might be helpful when using your VNA, a 6 dB pad to mitigate the effects of high SWR, and/or a DC blocker.

If you do the through port calibration does that work as expected?

--Chuck
AI6ZR




--
Diese E-Mail wurde von Avast Antivirus-Software auf Viren gepr¨¹ft.


Re: hi all...VNA noob here, encountering a problem I haven't seen before

 

On Sat, Jul 18, 2020 at 6:47 PM Tim Reimers KA4LFP <treimers95@...> wrote:

I have a nano VNA that is now refusing to read correctly after calibration it seems.
After running a one port calibration using the calibration assistant,
using the supplied open, short, and load calibration elements
... My normal technique is to do a scan of the Load element at the frequencies I have selected (before the calibration)... expecting to see a
dot n the middle of the Smith chart and a straight 1:1 line on the SWR chart, as I believe the load element should be 50 ¦¸ of pure resistance.
But as of yesterday that is not now how the device responds.
The Smith chart is covered in zigzags instead of even trying to be circles, and the SWR chart looks like a seismograph measuring a 5 on the Richter scale!
Well, several things come to mind. First, did anything of note happen "yesterday" ? It is pretty easy to burn out the port if you accidentally transmit into it, or connect an "active" antenna which feeds back power into the VNA. Simpler question is are you using the correct port? The Nano VNA is not a two port device, it transmits only on one port (I don't really expect this to be the case but in the interest of completeness ...) Do you have a different load? If not do you have a 50 ohm resistor you can solder across a cable and plug that in and see what you see?

Things that might be helpful when using your VNA, a 6 dB pad to mitigate the effects of high SWR, and/or a DC blocker.

If you do the through port calibration does that work as expected?

--Chuck
AI6ZR


Re: hi all...VNA noob here, encountering a problem I haven't seen before

 

Checking before calibration is not reliable.

Put it in the freezer for a few minutes and see if it works again until it warms up.

Gary AG7TH

On 7/18/20 18:47, Tim Reimers KA4LFP wrote:
Hello everyone,

I have a nano VNA that is now refusing to read correctly after calibration it seems.
After running a one port calibration using the calibration assistant,
using the supplied open, short, and load calibration elements

... My normal technique is to do a scan of the Load element at the frequencies I have selected (before the calibration)... expecting to see a dot n the middle of the Smith chart and a straight 1:1 line on the SWR chart, as I believe the load element should be 50 ¦¸ of pure resistance.

But as of yesterday that is not now how the device responds.
The Smith chart is covered in zigzags instead of even trying to be circles, and the SWR chart looks like a seismograph measuring a 5 on the Richter scale!

I've read on the topics here, and as a result, I have connected to the device on its COMport and done a "clear config 1234", followed by a power cycle and careful recalibration and retest against the Load, that got me nowhere. Same results on NanoVNASaver, and best I can tell on the tiny LCD, same thing....

what next, o guru's of the NanoVNA?

thanks and 73, Tim KA4LFP


hi all...VNA noob here, encountering a problem I haven't seen before

 

Hello everyone,

I have a nano VNA that is now refusing to read correctly after calibration it seems.
After running a one port calibration using the calibration assistant,
using the supplied open, short, and load calibration elements

... My normal technique is to do a scan of the Load element at the frequencies I have selected (before the calibration)... expecting to see a dot n the middle of the Smith chart and a straight 1:1 line on the SWR chart, as I believe the load element should be 50 ¦¸ of pure resistance.

But as of yesterday that is not now how the device responds.
The Smith chart is covered in zigzags instead of even trying to be circles, and the SWR chart looks like a seismograph measuring a 5 on the Richter scale!

I've read on the topics here, and as a result, I have connected to the device on its COMport and done a "clear config 1234", followed by a power cycle and careful recalibration and retest against the Load, that got me nowhere. Same results on NanoVNASaver, and best I can tell on the tiny LCD, same thing....

what next, o guru's of the NanoVNA?

thanks and 73, Tim KA4LFP


Loading Wrong FW version for Nano

 

Before I screw up my Nano, I was wanting to know if you load the wrong version of FW into say H4 that was written for the H, first can you, and if so can you reverse it back to the correct FW?

Gary


Re: User settable number of sample points

 

Reg,
All of DiSlord's firmware for the H4 supports 50, 101 and 201 points.
He uploaded his last release a few days ago - search his name and you'll find it.
It also has a nicer menu now.?
... Larry



On Sat, 18 Jul 2020 at 5:00 PM, Reginald Beardsley via groups.io<pulaskite@...> wrote: I've got a black 2.8" clone and a recent Hugen H-4 from R&L Electronics.? I suspect that the STM32F103 version can't do more than 101 points except via a PC, but it seems to me the STM32F303 version should be able to do more.? I've not seen any option for setting the number of points in the menus.

Is there FW that supports user setting of the number of sampling points?

Have Fun!
Reg


Re: NanoVNA Saver 0.3.3 or 0.3.4

 

Hi Enrique,

NanoVNA-Saver 3.6 runs well on Windows 10 64 bit, at least for me, you can download it here :

Jos

Op 15-7-2020 om 01:52 schreef Enrique A. Wembagher LU8EFF:

Hi Larry,

My programming and compilation knowledge is not the best ones to do it but I totally agree with you.

Holger and Gyula told me how to do it with the Python and I was able to run it (yours help is very best) , ¡­.
but it would be nice if someone compiled the latest versions for win 10 / 32-64....

Vy 73
Enrique LU8EFF



-----Mensaje original-----
De: [email protected] [mailto:[email protected]] En nombre de Larry Rothman
Enviado el: martes, 14 de julio de 2020 20:14
Para: [email protected]
Asunto: Re: [nanovna-users] NanoVNA Saver 0.3.3 or 0.3.4

Holger,

One of the newsletters I receive had an article on malware written in Python.
Part of the discussion revolved around how to get the size of the windows package down and there were 3 different Python to EXE utilities presented that are used for non-malware Python to Windows uses.

One of these is: Nuitka -

Right now, the NanoVNA-Saver EXE application is very large and takes time to execute.
What Nuitka does is to convert Python code to C and then compile.
The resultant application size is a fraction of what you get with py2exe or pyinstaller and runs much faster.

Could you try Nuitka on NanovnaSaver to see if it speeds up the application?
I did not look over the entire website but if Nuitka compiles C, it might be able to generate both 32 and 64 bit binaries.

Thanks,
Larry




--
El software de antivirus Avast ha analizado este correo electr¨®nico en busca de virus.