开云体育

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

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

Hi Robert - This comment in your first message is a concern: 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

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

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

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

Rudy: Tried that as well. Results below ------------------------------------------------------------------------------------------ -OMEN-by-HP-Laptop:~/nanovna-saver$ sudo python3.7 -m pip install .

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

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

If you actually bothered to check the source, namely https://github.com/hugen79/NanoVNA-H/releases then you would see that Hugen released separate firmware versions for -H4 (AKA 3.4) and -H (earlier)

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:

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

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

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 !!

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

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