开云体育

If you're not a noob to Linux, then why are you using Mint 17.x which is out of support? ???? I run nanovna-saver on Linux Mint 19.1 and it works quite well.? Installing Python 3.7 was no

Revert back to original( ttrftech ) board.c and change callback in UI, problems( not to jump address ) gone

The included cables are not Rosenbergers but are there any good and low cost sets? Or are they more than the VNA itself? John I ain't designing a ecm GHz device, just sweeping antennas

Hello Dick, There are several firmware versions available: /g/nanovna-users/message/7477 has a snapshot of firmware in the wiki.

Small post giving some background on the building and tuning of the 2GHz cavity filter. I was able to use my nanoVNA to check the tuning of this filter as described in another post

Actually, his Android app still calls home to mama Google for statistics.?? If you have your Android device's WiFi enabled and connected, the NanoVNA app starts right up. However, I run a firewall

Hi? Rune and QRP RX Yes indeed, running a calibration on my NanoVNA-H itself first, solved my prtoblem. The calibration with 60 segments and 10/5 Averaging over 10K to 900M is still running :-D:-D Oh

Using cho45's NanoVNA apk avoids Internet dependency: https://play.google.com/store/apps/details?id=net.lowreal.nanovnawebapp .. and Amazon Fire tablet is currently < US$30

Thanks Rune and QRP for responding that quickly, I did nothing more? than the flashing and trying to calibrate in NanoVNA-Saver, I wil run a calibration on NanoVNA itself and see if it solved it !

Another way to do this would be to package it up with an Android tablet and use NanoVNA WebApp as the user interface (remove or hide the built-in LCD). I'd like to try this but the android app won't

even if you cleaned your connector with alcohol, you're needs to perform calibration after that

any change, firmware or hardware requires a new calibration.

Hi Jos, I haven't done anything in particular relating to the NanoVNA-Q firmware, so any changes, assuming you are using the same version of NanoVNA-Saver, is in the firmware. :-) The individual

if firmware detects incompatible calibration it reset calibration and settings. You're needs to perform calibration after firmware update.

Hi Rune After Flashing NanoVNA-Q-0.4.4 I found that the calibration in Nan0VNA-Saver has changed. I am used to set the sweep settings in the NanoVNA-Saver to a high number of segments and averaging

it can enter into DFU with no issue, this is your compiler issue.

Tested: original(191124), Q(191119), H(191125) - Compiled with ARM-GCC/2019-Q4 - Each firmware flashed before FF overwrite & clearconfig & uncalibrated( cal reset & cal off ) nothing connected - trace

I tried to get it running on Linux Mint 18.3 (32bit) The big fault was to deinstall Python 3.5. This crashed my system completely. I installed a clean Mint 18.3 Cinnamon, installed Python 3.7, I

/g/nanovna-users/files/Hardware%20Mods/NanoVNA%20new%203.2%20LCD%20display%20Herman%20ON1BES.pdf -- NanoVNA Wiki: /g/nanovna-users/wiki/home NanoVNA Files:

from what i can tell a 3.2" will fit,would one of these do the job?,ones resistive and one capacitive on the touchscreen