开云体育

Ok, Erik!
Thank you very much!
73!

I was afraid shorting R13 would overdrive CH1 as I did not have the resistors to change the CH1 input (R29-R31)
Current CH1 headroom is less than 10dB
--
NanoVNA Wiki: /g/nanovna-users/wiki/home
NanoVNA Files: /g/nanovna-users/files
Erik, PD0EK

On Mon, Jan 20, 2020 at 11:45 AM, RFy wrote:

How fast full sweep and how many sweep points on this variants?

Same as the original nanovna.

hugen

On Sun, Jan 19, 2020 at 11:01 PM, Jos Stevens wrote:

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

Jos.

I see it.
But Erik wrote only about R9, R29, R30, R31 for improving CH0.
Maybe he left R13 150 ohm? :-) That's why I asked him.

How fast full sweep and how many sweep points on this variants?

NanoVNA-H rev3.4 is fully compatible with previous versions of NanoVNA firmware.
The NanoVNA-H4 uses a Cortex-M4 MCU and a 4-inch LCD, so it is no longer compatible with previous firmware versions.

hugen

Hello all, I'm at a loss. I was able to update firmware by going into DFU mode on my nanoVNA, but now that is not working at all since firmware version 0.5.4. The DfuSe Demo (v3.0.6) is not recognizing the nanoVNA"c when I enter DFU mode either via "Config", "Reset and Enter DFU" or by putting the short across the pins to force DFU mode. My PC recognizes the difference between my virtual com port (normal mode) and Universal Serial Bus devices, STM32 BOOTLOADER mode (DFU) mode.

I'm not sure what has changed. Any troubleshooting tips would be greatly appreciated!

Thanks,
Brian

David,
Thank you.? I accidentally posted to the wrong list.? Sorry for the extra bandwidth.
Ray

--
They say a smart person learns from their mistakes. A
wise person learns from the mistakes of others.

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?