开云体育

In my view scanraw should return raw readings (as it does) and BOTH S11 and S21 instead of currently EITHER S11 or S21 and yes, if you do not want to do your own calibration you can use the internal

"You might be having a problem with RF currents on the coaxial cable shield and therefore the VNA. You could try putting a ferrite beads on the cable but you would need to remove and reattach one

erik@...> wrote: ----------------------------------------------------------------------------------- Erick, Does that mean that the data returned by "scanraw" can be corrected by applying

My first "working" script gets screen colors wrong: https://oristopo.github.io/nVhelp/html/screenV.py $ python screenV.py screenV.py: PNG filename (without .png) expected $ python screenV.py foo $

AA has larger text, but is limited to displaying two traces at a time

Spelling the name of the file wrong doesn't suggest a problem with numpy, no ;-) I don't know exactly what Linux version you are using, but the instructions given normally work, and will install any

"I have different problems with every version tried. For using nanoVNA standalone, I install Hugen's most recent AA dfu version from here: https://github.com/hugen79/NanoVNA-H/releases" When I fist

You might be having a problem with RF currents on the coaxial cable shield and therefore the VNA. You could try putting a ferrite beads on the cable but you would need to remove and reattach one

data 0 returns S11 (all in complex format) data 1 returns S21 data 2-6 returns the 4 internal calibration tables dac was used by edy555 to calibrate the SI5351 frequency by setting a vxco, hugen did

Hi Herb - Thanks for reviewing Some further comments I think their point was that some nanoVNA >>may<< wire in a Real Time Clock. IMO, firmware anticipating hardware is doomed, but perhaps RTC was

Hi QRP - Sorry, key part of message was: "broken for my python scripts, since not ASCII" - problem is in >>MY<< Python code, NOT firmware - I need to add some Python that correctly handles

An absolutely EXCELLENT idea.? Thanks!! On Sat, 26 Oct 2019 at 6:38 AM, DL9CAT<groups.io@...> wrote: Hi, maybe this is interesting for you:I added a big info screen for CH0 on top

He dropped the last r on the filename... On Sat, 26 Oct 2019 at 5:57 AM, Rune Broberg<mihtjel@...> wrote: Hi, the file name is "nanovna-saver.py". So the error you got seems to

Hi, maybe this is interesting for you:I added a big info screen for CH0 on top of the normal screen: https://github.com/reald/NanoVNA/raw/master/doc/nanovna_infoscreen.jpg Select Config -> "Info

I would also suggest you are too close to the antenna you are trying to test. With a 20cm cable your body is very close. If you are also testing indoors it can also scew your results. Paul G0VKT

A couple of questions. How can I tell which version of firmware I have? My NanoVna works fine as far as I can see. Also works ok with the latest version of nanonva-saver. I am mainly interested in HF.

Thanks for confirming that. Both edy555 and Hugen79 0.2.3 are fine with Mod3.

Hi, the file name is "nanovna-saver.py". So the error you got seems to have been because you tried to run a file that did not exist? If the application works, then I don't think anything important

Hi John Here are 3 menu maps for different firmware versions: /g/nanovna-users/wiki/User-Guides That SAVE is nominally for touch screen calibration. Unless you identify problems

This version has a larger screen. What do folks who have one think of it. Does it need any firmware upgrade ? Thanks, Dick, W1KSZ ======================================= Dick, Yes, I have one of