开云体育

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

On Tue, Nov 26, 2019 at 11:29 PM, Dom Baines M1KTA wrote: " Is that gecko image on the cover linked to them in some way as I had problems with a basic NanoVNA with that logo."

Is that gecko image on the cover linked to them in some way as I had problems with a basic NanoVNA with that logo. Yes I know a logo isn't going to matter but maybe the 'dumb cloners' try to badge

Exactly.

The nanovna-saver source code is there so on the Mint 17.3 host could you not do an altinstall of python 3.7 without tramping all over the 2.7 install and then use a python environment and switch

Connections with LCD incompatible, firmware has insufficient free space See wiki /files for a possible retrofit -- NanoVNA Wiki: /g/nanovna-users/wiki/home NanoVNA Files:

is it possible to retrofit a 4.3 inch screen to a nanovna that has a 2.3 inch one,has anyone tried this?.

Anyone contemplating purchasing a NanoVNA-F in the near future should be aware a rash of clones have hit the marketplace. According to BH5HNU , "Recently we found a bad clone of the -F machine on

Sam, If I am doing an S21 measurement and I need to normalize for an added attenuator or preamp, I just do a quick through calibration with the attenuator or preamp in-line and that normalizes my

Has anyone thought about having a normalize mode? You could put it on the channel screen selection and indicate with a N added to the C#DRSTX with maybe a space between the X and the N to indicate to

linked under Firmware in /g/nanovna-users/wiki

Updated link in /g/nanovna-users/wiki/RF-Calibration%2C-considerations%2C-notes

No problem, I was skimming through the messages quickly and missed it.? Have a talk to Neb and see if he will share a copy of the reversed source to hugen's Sharp application for you to try and port

ajparent1/kb1gmx wrote: Then rather than update it, just install multiple versions and call the one you need. configure --prefix= (something like /usr/lib64/python3.7 or whatever your system uses),

add new Q-0.4.4 and special firmware in pdf. 73, Gyula

Just a clarification: NanoVNA-Saver is not "cross-developed Windows code with dependencies", but rather a pure Python program developed using a (reasonably) modern version of the language. :-) -- Rune