开云体育

Are you saying his latest software version, 0.4.5-4, compiled on January 18,
2020 will not run on version 3.3 hardware with 2.8" screen? If so what is the
latest Hugen firmware I can use on my version 3.3 hardware?

If you actually bothered to check the source, namely
then you would see that Hugen released separate firmware versions for -H4 (AKA 3.4) and -H (earlier) hardware

On Sun, Jan 19, 2020 at 07:45 PM, <erik@...> wrote:

For the CH0 and noise improvements you have to replace R9 with 200 ohm and
remove R29, R30 and R31.
Erik, PD0EK

And what about R13?

Latest should run. Just try. Even if the nanoVNA bricks you can always force it into dfu mode with the dfu jumper and restore a previous firmware

--
NanoVNA Wiki: /g/nanovna-users/wiki/home
NanoVNA Files: /g/nanovna-users/files
Erik, PD0EK

On Sun, Jan 19, 2020 at 08:00 AM, Oristo wrote:

Until NanoVNA-H4 (AKA HW version 3.4) all nanoVNA versions and clones can run
any nanoVNA firmware
(except Hugen's unique versions for HW version 3.4)

After HW version 3.3 of the 2.8" nanoVNA Hugen developed two products:
- 2.8" version 3.4 PCB
- 4" version with ?? PCB

Are you saying his latest software version, 0.4.5-4, compiled on January 18, 2020 will not run on version 3.3 hardware with 2.8" screen? If so what is the latest Hugen firmware I can use on my version 3.3 hardware?

Roger

Hi,

Thanks for adding me to the group.

So I received my NanoVNA-H on Friday. Today I managed to have a look at it. It comes with 'Firmware 0.4.5.1' and looks quite well built. I haven't opened up to check for screening at this time. It calibrated without an issue so I moved onto something straight forward. I checked some of my Hanheld's antennas for SWR/Freq. I used the toggle button and touch screen to evaluate both and they were as they should be. Next I connected to my ASUS ZenPad 3s 10 via the USB-C to USB-C cable provided with the kit.At this point I wasn't running the NanoVNA WebApp so unsure whether it would have seen it. It wasn't seen initially (that I'm aware of) on my Tablet so I run 'Easy OTG Checker' and there it was. I started the NanoVNA WebApp and all was good. It communicated with the NanoVNA and was great to use. I inputted 1500MHz for top and appeared to scan the higher frequency although I do not possess anything to verify the response.
The SWR measurements went well with the antenna from a Baofeng UV-82 surprising me. Not only did It over 144/430Mgs it also covered 220Mhz, also a 52Mhz antenna showed great promise for 144Mgs.

Something learned today and much to learn to learn going forward. I would like to thank all involved in this and say what a great job you are doing.

73
Ellis (M5AEI)

Congrats

Everything works fine again. Bad USB cable lost connection.
I used another USB cable and the DFU mode connected (jumper).
Updated and nano FW back to life.
73 !!

performance is now substantially better above 900MHz.
Much less noise and usable till 1.3GHz

Added to /g/nanovna-users/wiki/Mods-and-Design-Notes

Upgrading the firmware of the nanoVNA is something that is easily done but how about the HW?
Now I am the proud owner of an original V3.4 Hugen nanoVNA I dared to open my old Hugen nanoVNA and tried to modify it to the latest component values.
Looking at the schematic at github I saw I needed 91, 51 and 11 ohm for improving CH1, as I only had 51ohm I decided to leave CH1 as is for now
For the CH0 and noise improvements you have to replace R9 with 200 ohm and remove R29, R30 and R31. The latter three resistors are TINY (0402) and almost impossible to see and also very close to other tiny components.
Using 3 pairs of glasses and some solder wick and I was able to remove them without irreparable damage to the rest of the board (only one short circuit of a SA612 which did not destroy it). I lost one capacitor but had a somewhat bigger (0603) spare one.
After upgrading to the latest hugen firmware and calibration the performance is now substantially better above 900MHz. Much less noise and usable till 1.3GHz.
Having open HW and SW is so much fun!!!!
--
NanoVNA Wiki: /g/nanovna-users/wiki/home
NanoVNA Files: /g/nanovna-users/files
Erik, PD0EK

Can I indifferently load one or the other of those firmware, or just a specific one ?

Until NanoVNA-H4 (AKA HW version 3.4) all nanoVNA versions and clones can run any nanoVNA firmware
(except Hugen's unique versions for HW version 3.4)

I suppose that the version splash screen shows when there is no valid configuration in SAVE 0.

Anyone member can add a new Wiki page and/or edit existing ones,
so that is probably the easiest way to implement a document modifiable by others.
So far as I know, Groups.io has no specific FAQ mechanism.

I see that both eddy555 and hugen have recently released new versions of their respective firmware.
My nanovna is the -H model, 2.8", HW version 3.3
Can I indifferently load one or the other of those firmware, or just a specific one ? Currently I have the 0.5.4 by hugen, compiled on December 9,

Second question : before I played with it, my nanovna at power on did show a splash screen with some version info.
After some time, and a lot of recalibrations, at power on it goes directly to the graph screen, no splash screen anymore.
Is it caused by some mine wrong actions, or should I be worried ?

TNX

Alberto

On Sun, Jan 19, 2020 at 12:38 AM, Robert Rogers wrote:

$ python3.7 -m pip install .
FileNotFoundError: [Errno 2] No such file or directory: '/tmp/pip-build-x4up3i2u/PyQt5/setup.py'

Hello Robert,

Try: $ sudo python3.7 -m pip install .

73, Rudi DL5FA

Jim

see post #9737 for a workaround.

HTH

Error during the update caused problems:
- Screen completely white and without commands;
- Does not connect to the PC (COM port);
- Does not access DFU mode (jumper);
- It does not appear in the device manager list.
Any suggestions on how to access the nano?
Thanks!! 73 !!

Judging by a number of recent posts, a lot of folk are now having problems installing nanovna-saver on Debian based linux.

I've identified the problem, and have written some notes on how to fix it.

I'd like to share this with the group. Please could you gentlemen advise as to how best to do that. pdf in Files section, wiki, or even FAQ?

73
Nick

I tried just running the program as suggested in post #9840. Tried everything so far that been suggested. I do have it running in windows 7, but I just despise windows.
This is what I am seeing at this point.

jim@jim-NV53:~/nanovna-saver$ python3.7 nanovna-saver.py
Traceback (most recent call last):
File "nanovna-saver.py", line 17, in <module>
from NanoVNASaver.__main__ import main
File "/home/jim/nanovna-saver/NanoVNASaver/__main__.py", line 21, in <module>
from PyQt5 import QtWidgets, QtCore
ImportError: cannot import name 'QtWidgets' from 'PyQt5' (/usr/lib/python3/dist-packages/PyQt5/__init__.py)
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in apport_excepthook
from apport.fileutils import likely_packaged, get_recent_crashes
File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in <module>
from apport.report import Report
File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in <module>
import apport.fileutils
File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in <module>
from apport.packaging_impl import impl as packaging
File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in <module>
import apt
File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in <module>
import apt_pkg
ModuleNotFoundError: No module named 'apt_pkg'

Original exception was:
Traceback (most recent call last):
File "nanovna-saver.py", line 17, in <module>
from NanoVNASaver.__main__ import main
File "/home/jim/nanovna-saver/NanoVNASaver/__main__.py", line 21, in <module>
from PyQt5 import QtWidgets, QtCore
ImportError: cannot import name 'QtWidgets' from 'PyQt5' (/usr/lib/python3/dist-packages/PyQt5/__init__.py)

Hi-

I've spent three interesting days updating my EeePC notebook PC's Debian Linux OS so I could install the nanovna-saver software. Finally got there and all was good until I decided to load a calibration file and/or create a new one.

I've found that the calibration panel doesn't fit the screen. The bottom third or so is not visible, so I don't have access to the buttons for loading and saving calibration data. I hoped that I could drag the panel upward, but I cannot - I can move it down only, or stretch it horizontally, which is no help.

I did a few generic Debian/gnome searches on the issue and it seems to be not uncommon, but the solutions offered don't seem to help in my case.

Anyone got a suggestion for this? If there's no resolution, perhaps the author would consider changing the layout of the panel to accommodate screens with limited vertical space(?)

Thanks,

Nick, WA5BDU

Hi Dennis,

I think the solution is written here:
/g/nanovna-users/topic/51160730

if not, use and read the wiki description
it seems to me that for the first time the lack of a driver between the computer and nano is the source of the problem.

73, Gyula HA3HZ

Hi All, had my VNA-H for a short while and decided it was time to update it, mine is board V3.3, firmware 0.2.3.2, using DFUse, I put my unit into DFU mode and uploaded the latest upgrade. As i have the DFU option in my config, i assume i did not need to short the 2 pins together, that said, the software showed success at every stage, but my device is still stuck on its original firmware, help please.

Dennis G8IMN