¿ªÔÆÌåÓý

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

Broken S-A-A v2 ?


 

Hello. Got my hand on this nanovna v2 plus(?)
Frist time turned it on got ALOT of traces and no idea what to do. After some tutorials I realased that it might be broken / bricked.
As you can see from the pictures the traces go all over the place and resistances etc change all the time.
I've calibrated the thing many many times, changed frequency range and calibrated again, calibrated more, tested antennas.... nothing
Seems like there is no connection between board and sma connector.
I can connect to nanovna-qt and saver. all show same kind of traces. Done calibration through software and through the screen.
I have updated the firmware to the lastest one. Also tried the experimental. Still same.
Any ideas?


 

Did you do a reset before each cal?

Dave - W?LEV

On Tue, Sep 14, 2021 at 10:16 PM <jorksx@...> wrote:

Hello. Got my hand on this nanovna v2 plus(?)
Frist time turned it on got ALOT of traces and no idea what to do. After
some tutorials I realased that it might be broken / bricked.
As you can see from the pictures the traces go all over the place and
resistances etc change all the time.
I've calibrated the thing many many times, changed frequency range and
calibrated again, calibrated more, tested antennas.... nothing
Seems like there is no connection between board and sma connector.
I can connect to nanovna-qt and saver. all show same kind of traces. Done
calibration through software and through the screen.
I have updated the firmware to the lastest one. Also tried the
experimental. Still same.
Any ideas?





--
*Dave - W?LEV*
*Just Let Darwin Work*


 

Yea. Reseted all before ecah cal. Did cal reset and tried reset all and started all over...


 

Not sure what frequency you are measuring but first do a reset all. In menu buttons.

Set the stimulus 1 MHz to 10 MHz? just for some low hf range.

On the s-a-a-2 my SAA2 port zero is the bottom connection not the top left.

Do a reset then
Do a SOL calibration.

If you get the same results all over the place.

Go to the transform turn it on and off. Observe the display on the Smith chart.

See if you can see something other than garbage. It not then probably the sma connection is broken of the PC board.

De K8HTB Joe


 

Also check what version of firmware you have. Current version is 1.0.69

De K8HTB Joe


 

I would also agree on checking connections. when i ever have not a tight connection to whatever I am testing I get that birds nest mess of lines also.

Joe WB9SBD

On 9/14/2021 6:13 PM, K8HTB wrote:
Not sure what frequency you are measuring but first do a reset all. In menu buttons.

Set the stimulus 1 MHz to 10 MHz? just for some low hf range.

On the s-a-a-2 my SAA2 port zero is the bottom connection not the top left.

Do a reset then
Do a SOL calibration.

If you get the same results all over the place.

Go to the transform turn it on and off. Observe the display on the Smith chart.

See if you can see something other than garbage. It not then probably the sma connection is broken of the PC board.

De K8HTB Joe



 

It looks like the calibration parts and or a cable or 2 might be defective.?
This has tripped-up users in the past with the same display output.?
Check all your call components.?


On Tue., 14 Sep. 2021 at 6:16 p.m., jorksx@...<jorksx@...> wrote: Hello. Got my hand on this nanovna v2 plus(?)
Frist time turned it on got ALOT of traces and no idea what to do. After some tutorials I realased that it might be broken / bricked.
As you can see from the pictures the traces go all over the place and resistances etc change all the time.
I've calibrated the thing many many times, changed frequency range and calibrated again, calibrated more, tested antennas.... nothing
Seems like there is no connection between board and sma connector.
I can connect to nanovna-qt and saver. all show same kind of traces. Done calibration through software and through the screen.
I have updated the firmware to the lastest one. Also tried the experimental. Still same.
Any ideas?


 

There is a similar effect when you upload the plus version firmware to the non plus hardware.


 

I tried with those sma calibration things and I also calibred with 50ohm resistor
I also tried open so without any connection
short, I shorted sma center to threads
and load was 50ohm resistor

Firmware is downloaded from here
20201013 stable for v2 plus


 

Are you sure you have a plus version? The firmware for regular V2 and V2Plus is different (but work, not good work).


 

Config - Version says NanoVNA v2 Plus.
I just tested ALL the firmwares listed on that site I linked.
2 of them did not work at all, 2 were super slow and rest were working but still with my problem.
frequency range is 100mhz-150mhz.
Tried many different of them.
What should the scale/ and div etc... values be? Seems when I play with them I get better looking traces but the resistance values for example still changed all the time.
SOmetimes -6ohm to 20ohm. sometimes its 48ohm - 51ohm


 

Config-version only displays the version of FW you installed into the device.
If you installed plus FW into a non-plus device, you will see 'plus' on the version screen.
So - you need to install the non-plus FW into your device and calibrate to see if the problem goes away - if it does, you have a non-plus device.

On Wednesday, September 15, 2021, 06:25:05 a.m. EDT, <jorksx@...> wrote:

Config - Version says NanoVNA v2 Plus.
I just tested ALL the firmwares listed on that site I linked.
2 of them did not work at all, 2 were super slow and rest were working but still with my problem.
frequency range is 100mhz-150mhz.
Tried many different of them.
What should the scale/ and div etc... values be? Seems when I play with them I get better looking traces but the resistance values for example still changed all the time.
SOmetimes -6ohm to 20ohm. sometimes its 48ohm - 51ohm


 

not sure how quoting works here but @Larry Rothman
From the link above. I installed the v2.2 firmware. The one that is not sold anymore. Problem is still the same
Then I installed one above it (v2 plus v2.3) Tried both experimental and stable. problem is still the same
Tried the V2 plus4 and the firmware does not work and have to force dfu and reflash something else...
Also tried all the "unoffical hardware variants"


 

Your device work in < 140MHz?

Check work in < 140MHz on V2 and V2Plus firmware

If work, problem in ADF generators or switches


 

nope. does not matter if the frequency is 3mhz - 6mhz or 140mhz - 455 mhz or full scale etc...
Always the traces are all around the place.


 

you need check output switch u551, see v2 scheme


 

witch pin do I check and what should it read?
Wayy too small traces for my multimeter so I have to go lend some smaller stuff tomorrow.


 

I had the same problem, which appears when making the calibration and SHORT probe does no electric contact is made with the CH0 connector.
Solving was by tightening the warm wire in the CH0 connector.


 

What is a "warm" wire in the CH0 connector??

On 9/19/2021 11:32 AM, eugen.trifu@... wrote:
I had the same problem, which appears when making the calibration and SHORT probe does no electric contact is made with the CH0 connector.
Solving was by tightening the warm wire in the CH0 connector.




William Smith
 

I'd imagine 'not the shield', aka the ('hot'?) center conductor.

73, Willie N1JBJ

On Sep 19, 2021, at 1:44 PM, Mike C. <mg@...> wrote:

What is a "warm" wire in the CH0 connector??


On 9/19/2021 11:32 AM, eugen.trifu@... wrote:
I had the same problem, which appears when making the calibration and SHORT probe does no electric contact is made with the CH0 connector.
Solving was by tightening the warm wire in the CH0 connector.