Date   

Re: New, disappointed member intro

John
 

Thanks for all the replies. I've connected the NanoVNA to my PC (Windows 7)
and it's working OK. I've even had a quick scan through the manual...

I don't have a can of compressed air. I could flush the switch out with a
jet of isopropanol and see what happens. I could replace the switch if I
had one, I have access to a reasonable rework station and a good
stereomicroscope, but I haven't found a source of that particular switch.
Actually I don't like the switch, not because it doesn't work but because
it sticks out and looks fragile. I'd rather have a row of three tiny push
buttons just accessible from the edge of the board. I'll have a look at the
circuit diagram. It should be easy enough.

If the supplier offers to ship another immediately and trust me to send the
faulty one back then I'll wait. If not I might just hang on to this one on
the basis that a VNA in the hand is worth two in the post.

I've tried the touch screen and it works OK.

John

On Sun, 15 Sep 2019 at 13:52, Larry Rothman <ac293@rogers.com> wrote:

Hi John,
Please remember that you can use this device via the touchscreen. However,
make sure to calibrate and save the touchscreen parameters. I created a
wiki entry on how to do that if your device has the default firmware.
73
Larry




Re: NanoVNA bricked

David J Taylor
 

From: Bruce KX4AZ

I am trying to jumper the boot to Vdd with a wire with alligator clip on each end. So it's still booting normally with regular screen, so wondering if there are any special tricks to getting the jumper connection, or a better too like the connectors used for logic probing?
=========================

Bruce,

I just bent 24 swg tinned copper wire into a "U" shape, tweaked the space so that it held itself into position to get the white-screen boot.

Cheers,
David GM8ARV
--
SatSignal Software - Quality software for you
Web: http://www.satsignal.eu
Email: david-taylor@blueyonder.co.uk
Twitter: @gm8arv


Re: List of NanoVNA Console Commands

Oristo
 

How does one enter console commands in a Windows 10 environment...use a terminal program to connect via a USB COMx connection?
PuTTY https://putty.org/
https://store.chipkin.com/articles/using-putty-for-serial-com-connections-hyperterminal-replacement/


Re: NanoVNA bricked

Bruce KX4AZ
 

I am trying to jumper the boot to Vdd with a wire with alligator clip on each end. So it's still booting normally with regular screen, so wondering if there are any special tricks to getting the jumper connection, or a better too like the connectors used for logic probing?


Re: List of NanoVNA Console Commands

Bruce KX4AZ
 

As a newcomer to much of this I have a simple question that gives away my inexperience...

How does one enter console commands in a Windows 10 environment...use a terminal program to connect via a USB COMx connection? I am assuming a command prompt window would not work. Or is entering console commands just a Linux only thing? Thanks in advance for "dumbing it down" for me.


Re: Using Linux CLI dfu-util question.

Andy 'FTD <punkbiscuit@...>
 

Thank you Rudi.
I've archived your post for future reference.
Many thanks.

73 de Andy


Re: List of NanoVNA Console Commands

 

Hello,

From the calibration and measurement results of full one-port measurements
of the reflection coefficient of a constructed experimental one-port black box,
we concluded by trial-and-error that, as it seems, the 1st line from below in p.1
of "NanoVNA Console Commands 8-6-19.pdf", that is this one:

"NOTE: need to determine what the output parameters above represent."

which is referenced to the Console Command "data", is redundant, at least in
this case, because, the values in the two 2 columns are - from left to right -
the Real part and the Imaginary part, respectively, of the reflection coefficient.

Sincerely,

yin&pez@arg


Re: New, disappointed member intro

Larry Rothman
 

Hi John,
Please remember that you can use this device via the touchscreen. However, make sure to calibrate and save the touchscreen parameters. I created a wiki entry on how to do that if your device has the default firmware.
73
Larry


Re: New, disappointed member intro

John Herleman
 

If you have access to a can of compressed air, it may be worthwhile to try blowing the switch out a bit and then carefully examine the rear portion where it contacts the silver metal backing. I found on mine that the metal had some sharp edges that impeded free movement. While I wouldn't generally recommend it, I have also put a tiny bit of lubricant on the back of the wheel and then used the compressed air to remove excess and to force some tiny bit of it into the mechanism. The switch is replaceable if you are comfortable with precision soldering but I suspect that you may be able to salvage it. I found only a single "spring" operated mine and, accordingly, it seems unlikely that it can be broken in one direction only. While well thought out, the open source nature of this unit often means that quality control is VERY compromised. Don't give up without a proper fight.


Re: NanoVNA bricked

Adrian Waiblinger
 

Hi

I tried what you said and it did not work. I get an error "Target 00 /error code: Bad state machine infirmware."

I have ordered an STL-Link 2 from your advice.

Thanks for your help

Regards
Adrian


Re: New, disappointed member intro

John
 

Hello Bruce,

Thank you for the reply. I can manually return the switch to the centre
position but the spring return no longer works except from the left
position. The movement of the switch feels "gritty".

I've had an answer from the seller who seems to think that a part was
missing, so I've replied to explain again that the switch is faulty. Yes, I
could use the NanoVNA with the PC software (although I haven't tried) but I
want to use it with a very compact Go Kit when I don't have use of a
computer. I'm expecting (hoping) for a replacement but I could learn to use
it in the meantime.

73,

John G4EDX

On Sun, 15 Sep 2019 at 11:56, Bruce KX4AZ <bruce@tustinfarm.com> wrote:

When you say it does not return by itself, does that mean you can still
manually "persuade" it to return by pulling it back from the stuck
position? If it is permanently stuck, have you tried using any PC software
to control the analyzer? That might at least let you collect data etc
while working on getting a replacement.




Re: New, disappointed member intro

Bruce KX4AZ
 

When you say it does not return by itself, does that mean you can still manually "persuade" it to return by pulling it back from the stuck position? If it is permanently stuck, have you tried using any PC software to control the analyzer? That might at least let you collect data etc while working on getting a replacement.


New, disappointed member intro

John
 

Hi All,

My NanoVNA arrived two days ago and appeared to work OK. After only a few minutes the up/down/select switch failed. Now it won't return by itself from the "in" or "right" positions. Anyone else had this problem? I've contacted the UK seller and hope to have it replaced. I'm keen to start using it.

I also have an original RFS MiniVNA which I've converted to Bluetooth so I can use it with an app on my phone. I carry it in my FT-817 Go Kit for checking aerials in the field.

Glad to be a member of this group. Expect questions!

73,

John G4EDX


Re: NanoVNA firmware extended to 1500MHz with added scan command

Rudi
 

i'm on windows, so have different tools (DfuFileMgr.exe), for you "dfu-tool set-product somefirmware.dfu df11" should work

Hello tinhead,
Thank you for the hint.

I found the following web page:
https://github.com/myriadrf/LMS8001-Companion/tree/master/drivers/STM32_DFU/tools/DfuSe%20v3.0.5/Bin
I could download "DFUFileMgr.exe" and the accompanied DLL files.
Also needed are "MFC120-dll" and "MSVCR120.dll" which I found in the internet.

Running "DFUFileMgr.exe" under windows 10 I could read in the DFU file from erik "NanoVNA_with_scan-and_1500MHz_erik.dfu"
and export as a binary file. Then I read in the binary file, added the USB product ID "DF11" and saved as a .dfu file.
Unfortunately the header in the exported file was changed, so the CRC at the file end does not match your file "NanoVNA_with_scan_and_1500MHz_tinhead.dfu"

How did you manage to change the USB product ID only and update the CRC without changing the file header?

73, Rudi DL5FA


Re: 1500 MHz

QRP RX
 

I tried to use 1500 MHz version, but it seems that it has worse S21 measurement, I'm not sure, may be this is just a bad calibration, but original firmware works better. So I flashed original one.

I tested also S11 and it seems that it is a little usable up to 1200 MHz (with S11 smaller than 15 dB). Above 1200 MHz it has terrible distortions and almost unusable. Actually I don't need 900-1200 MHz range, so I rollback to original firmware. :)


Re: Yet another NanoVNA PC app

Erik Kaashoek
 

For the SA612/SI5351/dead bug bridge version:
The dynamic range of port 2 is limited by the leakage of the SI5351, just like the nanoVNA.
The biggest difference is above 300MHz where the directivity of the bridge becomes dependent on the quality of the layout, but below 300MHz directivity is equal to NanoVNA
For the ADF4351/IAM81008/ebay bridge version:
Dynamic range of port 2 around 2.5GHz is about 40-50dB and decreases somewhat till 30-40dB at 4.4GHz, but there no shielding at all so this can still be improved.
Directivity is ok till 2.6GHz but the ebay bridge quickly looses performance and basically stops working at 3GHz.
A SI5351/IAM81008/ebay bridge version easily has directivity till 1.2GHz, did not try higher.


Re: NanoVNA bricked

QRP RX
 
Edited

Just buy ST-LINK2 on aliexpress: https://www.aliexpress.com/item/32839270086.html

it allows to flash STM32 even if it is bricked. You will need to connect GND=GND, VDD=3.3V, SWDIO=SWDIO, SWCLK=SWCLK. These signals are placed near boot jumper on the right side of nanoVNA.

In order to flash you will need ST-LINK Utility: https://www.st.com/en/development-tools/stsw-link004.html

Connect ST-LINK to NanoVNA (there is no need to solder, you can keep wires with finger during flashing), start ST-LINK Utility, and set the following values in the window:
Address: 0x08000000
Size: 0x20000
Data width: 8 bits

After that select menu: Target => Connect, it should connect to STM32 and show it's memory content.

Use File => Open file menu to open HEX file with NanoVNA firmware.
And then flash it into NanoVNA with menu Target => Program and verify

That's it :)
See HEX file with NanoVNA firmware in attachment.


Also, you can try to reflash it with DFU. Just connect USB cable, power off NanoVNA, short the boot jumper and power on NanoVNA, after that remove boot jumper and try to flash it with DFU again.

But DFU is not reliable way to flash it. So, if it won't work just buy ST-LINK and use instruction above. ST-LINK is native way to flash STM32. While DFU is just a way to flash it for those, who don't have ST-LINK. But flashing through DFU is buggy and not reliable way to flash it. It's better to use ST-LINK. But note, ST-LINK uses HEX or BIN format, it cannot understand DFU file.


Re: Latest version of NanoVNA-Saver locking up for some reason

Rune Broberg
 

Hi Ron,
I pushed a fix to the first bug you mentioned. I think the locking up
problem is due to your NanoVNA not responding to requests by the program to
set a sweep span (or possibly because you are trying to run a 0 span sweep).

Which firmware are you using?

--
Rune / 5Q5R

On Sun, 15 Sep 2019, 02:30 Ron Webb, <bigron@gmail.com> wrote:

I have had the same exact issues in Ubuntu Linux. One little oddity I've
noticed and don't know how to fix while in Ubuntu is that I have to run
NanoVNA-Saver with elevated privileges to actually connect to device ("sudo
python3 nanovna-saver.py") to start. When it locked up, as it did in
Windows 10, this time I saw a some type of message which I did not see in
Windows:


Traceback (most recent call last):
File "/home/ubuntu/Git/nanovna-saver/NanoVNASaver/NanoVNASaver.py", line
702, in dataUpdated
if self.dataLock.acquire(blocking=True):
KeyboardInterrupt
The X11 connection broke: I/O error (code 1)
XIO: fatal IO error 0 (Success) on X server ":0"
after 984 requests (731 known processed) with 0 events remaining.


I had to force it to quit, so maybe that is all this is about, but it
brought something up about "dataLock" I thought MIGHT have something to do
with the lock up, I'm not sure though.




Re: Yet another NanoVNA PC app

croma641 <croma641@...>
 

Hi, Eric, what is the dynamic range of Your "dead-bug" setup ? Thanks in advance

- Andrea IW2FDH -


NanoVNA bricked

Adrian Waiblinger
 

Hi all.

I used Dfuse Demo to do an upgrade on the original NanoVNA.
Did as instructed boot to Vdd, switched on and presented with white screen
Fired up DfuSe Demo upgrade to nanoVNA_900_AA, got error message and now I have a white screen after the jumper is removed.
I assume the firmware is gone. any tips on how dot to get this error.

Regards Adrian.

19441 - 19460 of 21884