开云体育

Roger,
Have a look at Erik's post from earlier today. Those are the changes that are documented in the latest schematics for hugen's design v3.4
I hope you have a microscope and a steady hand in order to change those parts.?

RegardsLarry

On Fri, 17 Jan 2020 at 1:41 PM, Roger Need via Groups.Io<sailtamarack@...> wrote: On Fri, Jan 17, 2020 at 09:05 AM, Larry Rothman wrote:

A number of forum members have 2 or even 3 of the Nano's and I for one have
already modified mine to reduce noise and increase the freq range specs.
my $0.02

Larry,

Would you consider making a separate post detailing what you did to increase the freq range and reduce noise?

Roger

"Please note: Starting with NanoVNA-H rev3.4 D2 uses IN4148, if your NanoVNA
D2 is a Schottky diode, use the "vbat_offset 150" command to calibrate the
battery voltage."

So it made me wonder if the rest of the software worked with earlier H
versions

The D2 story is: few nanoVNA were shipped with any D2 installed.
1N4148 was installed by some, Schottky by others.
Just as most nanoVNA (except gecko) have type C USB connectors
while few have the resistors necessary for type C connection.
The only significance of D2 is for accuracy of the battery gauge,
which can be corrected using that "vbat" USB shell command
in any firmware which supports the battery gauge icon.

Hi Robert -

The answer will come

This comment in your first message is a concern:

I've tried creating the tmp folder and manually moving setup.py . It really didn't make much difference.

Ubuntu 18.04.3 LTS surely has a tmp folder for updates...

Linux distros generally have packaging schemes which typically do not use pip.
To the extent possible, a distro user should use the same package manager
to install python packages that was used to install python itself.

If python were manually installed from e.g. a tarball,
then the distro's package manager would not be implicated, and pip would be appropriate.

Using pip can be compared to crossing wires:


"In most cases, you should use pip within a virtual environment only."

On Sun, Jan 19, 2020 at 11:43 AM, Oristo wrote:

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

I did check and saw this comment by Hugen...

"Please note: Starting with NanoVNA-H rev3.4 D2 uses IN4148, if your NanoVNA D2 is a Schottky diode, use the "vbat_offset 150" command to calibrate the battery voltage."

So it made me wonder if the rest of the software worked with earlier H versions

But thanks anyway for your kind response....

Roger

Rudi:

I'll look into PyQt5 not installing issue. Rather be working on this than blowing snow in my driveway......

I've been running Ubuntu for years, and still I'm a novice. Thanks for taking time for the suggestion. The answer will come..

Best 73
Bob

On Sun, Jan 19, 2020 at 09:21 PM, Robert Rogers wrote:

Tried that as well. Results below

Hello Robert,

Too bad.
It helped me, therefore I told you.

What is strange for me, PyQt5 was downloaded OK, but was not installed.

73, Rudi DL5FA

I was thinking ahead and picked up an USB extender. Didn't work.

This summer I'm hoping to put up a modified .64 wavelength antenna (formerly on 11m).
Measuring the Z of the antenna then designing the feed matching network.

To keep any external influences out of the measurements, I thought it would be a good idea to take measurements from the ground.

Suggestions? An Amazon $7 solution didn't cut it.

73
Bob

Rudy:

Tried that as well. Results below

------------------------------------------------------------------------------------------

-OMEN-by-HP-Laptop:~/nanovna-saver$ sudo python3.7 -m pip install .
[sudo] password for mm:
The directory '/home/mm/.cache/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
The directory '/home/mm/.cache/pip' or its parent directory is not owned by the current user and caching wheels has been disabled. check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
Processing /home/mm/nanovna-saver
Collecting PyQt5 (from NanoVNASaver==0.2.2)
Downloading (3.2MB)
100% |████████████████████████████████| 3.2MB 232kB/s
Complete output from command python setup.py egg_info:
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/usr/lib/python3.7/tokenize.py", line 447, in open
buffer = _builtin_open(filename, 'rb')
FileNotFoundError: [Errno 2] No such file or directory: '/tmp/pip-build-a8hpixj_/PyQt5/setup.py'

----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-a8hpixj_/PyQt5/
mm@bob-OMEN-by-HP-Laptop:~/nanovna-saver$ python3.7 -m pip install .
Processing /home/mm/nanovna-saver
Collecting PyQt5 (from NanoVNASaver==0.2.2)
Using cached
Complete output from command python setup.py egg_info:
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/usr/lib/python3.7/tokenize.py", line 447, in open
buffer = _builtin_open(filename, 'rb')
FileNotFoundError: [Errno 2] No such file or directory: '/tmp/pip-build-7clot2r6/PyQt5/setup.py'

----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-7clot2r6/PyQt5/
-----------------------------------------------------------------------------------------------------------------------------------------------------
Before I forget tnx all for the help everyone

73

On Sun, Jan 19, 2020 at 04:06 AM, Rune Broberg wrote:

python3.7 nanovna-saver.py

tried that (btw tnx) results below
OMEN-by-HP-Laptop:~/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/mm/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)

You have to schort R13 and change? R22 upto included R24 also :

R22 and R23= 51 Ohms , R24 91 Ohms, R25 = 11 Ohms.

After this you have updated version 3.3 to version 3.4 as far as possible (without the power supply)

Jos.


Op 19-1-2020 om 19:45 schref Andy UA3RAW:

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.