开云体育

Hi erik,

edy555 and hugen have sources for 256 point FFT Firmware ?

Where is it ? I can not find...

Not sure but maybe you have to select for the trace "real"

Both edy555 and hugen

Any source, if any, of github repository ??

Hi Veen

Hope the image comes through

Alex

Mine came with a 602040 (20x40x6mm) 450mA pouch cell.

Hi Veen

From what I have seen from some of the adverts with the battery

it is a 1S 400 to 450mah lipo in the flat almost rectangular style.

The advert also identified where you would solder the leads,

so it would pay you to check out some of the advertising on the auction

site for the pictures.

I am awaiting delivery of mine that supposedly has the battery - we will see.

regards Alex VK2ABE

Yesterday evening received my first nano vna and does not contain internal
battery due to shipment restrictions.

Request for specifications of li-ion battery specifications

73
de vu2pgb
Veen

Hello again YZA;

I have not yet attempted to install the relevant software and math engine required to compile and run your Fortran code, and it would take some effort on my part (or any evaluator not programatically versed or equipped) to work through that process. Before investing the effort to do so, I am attempting to understand the goals and objectives of your work, and if or how it might benefit users of the NanoVNA, and the VNA community overall.

The principal utility and benefit of the NanoVNA is it's size and portability. To that end, it is limited in its available reserve of stand alone computational resources. Additionally; most users on this forum are not motivated to invest in high quality (accurately characterized) calibration standards that cost many times the price of the device itself. System requirements of the evaluator(s) need to be clearly defined.

The software you describe would, by necessity, require PC connectivity, and operates on data files collected by the NanoVNA and ported to your software for statistical analysis in order to derive the error bounded plots shown in your documentation. There are sophisticated VNA users in this group that might find great interest in your work if the goals, objectives, system requirements, output results, and the utility and benefit of those results were clearly presented such that they could be easily and clearly understood in the context of how they might enhance the quality of the NanoVNA measurements. Those users are likely a minority. There may be an even smaller subset of this group that may simply have an academic interest in your work.

I think your documentation may be sufficient for those motivated to dig into the details of your algorithms; given that there is a clear benefit for investing in that effort. What type of support are you requesting from this group? What dictates the need to distribute Fortran code? Can it not be compiled and distributed as a stand alone executable, and a readme.txt file outlining the detailed feedback content you desire?

73

Gary, N3GO



--
73

Gary, N3GO

hi
I have tried : menu transform on
entered the velocity of coax 0.66

the lenght is about 16feet
and tested the other menu: low pas impulse etc

but I don't see the lenght of the coaxial cable

I am able with nanovna saver to see the coaxial cable lenght but not with only the nanovna
any help?
thank you
Gilles

Users of Micro$oft systems, no more money need be spent nor upgrades

done to run Rune's application; Mr. Bill has milked you for long enough.

Simply install a Linux version on your machine which, now, won't run

Rune's superb application.

Ubuntu and Mint are suggested for those recent users of a Micro$oft

system. A five year radio engineer friend, a Window$ user, has just this
week installed Mint Cinnamon on an "old" 64 bit laptop. He is already in
love with it so maybe Mint Cinnamon is the way to go at the moment for
Window$ users. Anyway, take a bit of time and read up on those two
distributions and understand them.

The installation programs are automatic. The automatic installation

programs spend a good long time going back and forth all through the
destination machine and end up understanding it fully before actually
doing the installation. The installation is then turn key. Please, read
up on those two Linux distributions before giving away yet more money to
Mr. Bill; a 21 car garage is big enough for anybody.

The Linux system can be installed "beside" the Micro$oft system for

those who are perverse and wish to persist with Window$. The Linux 64
bit "Ubuntu 18.04" system here works beautifully with Rune's
application. Detailed instructions for installing Rune's application on
a Linux system are set out on the web. They were followed here...they work.

Consider an operating system engineered properly, from the ground

up. The Linux operating system is not a porous, "rush it out the door",
rattle trap replete with buffer overruns, virus vulnerabilities and
other inexcusable Q.C. oversights.

The everyday applications for use on Linux systems are not

threadbare and low rent.

John

at radio station VE7AOV.

+++++


On 2019-09-25 2:04 p.m., George wrote:

Rune,

You are doing fine work. Keep it up.

But I hope you can understand the frustration of not being able to run the software on the many laptops and other computers that have not been upgraded to Win10. We do not want to install a bloated Framework 4.0 when it already has Framework 3.5 --- just to run one program.

If you ever get it to run on WinXP that would be a big big plus!

I'm sure a software developers life is full of headaches. Hope you hang in there. Your work is appreciated by many here.

By the way, how did this thread get hi-jacked away from dealing with Win7 issues?

On Wed, Sep 25, 2019 at 01:12 PM, Rune Broberg wrote:
...

On Thu, Sep 26, 2019 at 07:12 AM, Steve London wrote:

A little confused on the firmware versions.

Is the source code available for the nanoVNA_900_AA ? Or is that already in
the hugen-modified 0.1.1 ?

What I really want is the best of all worlds for using the nanoVNA while
hanging from my tower at 110 feet. Being able to measure Z at the feedpoint
with large font and display of R + jX. I'm perfectly willing to tweak the code
to do that, but I need the large font version as the starting point.

Thanks,
Steve, N2IC

I created the AA version to better display Chinese. Since the TDR function does not have enough ROM to store Chinese fonts, I need to separate the AA version from the Chinese version and merge it with NanoVNA-H. If all goes well I will update on github.

hugen

CAL/CORRECTION:

This is the prompt to turn correction ON or OFF...

I believe that is what you are referring and that is all it does.

CORRECTION when doing a CAL... No not part of or an influence on CAL.

Regards,

The battery indicator requires you to add a surface mount diode (D2 on the schematic) or it shows an empty rectangle.
The correction button enables or disables the stored calibration factors.
Please search the forum posts on both items and you will find the information.

Regards
Larry

A little confused on the firmware versions.

Is the source code available for the nanoVNA_900_AA ? Or is that already in the hugen-modified 0.1.1 ?

What I really want is the best of all worlds for using the nanoVNA while hanging from my tower at 110 feet. Being able to measure Z at the feedpoint with large font and display of R + jX. I'm perfectly willing to tweak the code to do that, but I need the large font version as the starting point.

Thanks,
Steve, N2IC

Happy if somebody could answer the following:

I have FW Sept 19 2019:10.37.16. What is CAL/CORRECTION? Is it application of the selected RECALL?

Is it necessary to have CORRECTION highlighted when calibrating?

By the way: My battery-icon shows just the outline and nothing inside, is this correct for my current FW?

Thanks for any reply,

Torbjorn

No, It is just ttrftech/NanoVNA head build. XENOMORPH is not an author.

Hi Erik
One note
If you are using the NanoVNA-saver and has entered the calibration kit data as a female kit (adding the delay of the Thru adaptor (2 x 62ps) for the short and open, then you only need to subtract the delay of the Thru adaptor for the s21/s12 measurements to have the right phase (0 degree) at both the two SMA male adaptors.
Kind regards
Kurt

-----Oprindelig meddelelse-----
Fra: [email protected] <[email protected]> P? vegne af erik@...
Sendt: 25. september 2019 16:54
Til: [email protected]
Emne: [nanovna-users] Trying to understand the T-Check outcome of the nanoVNA

Using a not too good BNC Tee I performed a T-Check Attached the measurement (.s2p) and the excel file (.xlsx) in which the T-Check is calculated.
Next to the T-Check calculation the excel also calculates the abs(Zin-Zout)/Z0 (the percentage absolute distance of the two impedances as another estimate of error) The frequency is denoted in MHz Do ignore anything above say 500MHz

The T-Check suggests the error quickly increases to substantial levels but the abs(Zin-Zout)/Z0 suggests there is a very systematic error in my measurement where the absolute distance of the two rotating impedances grows very linear with frequency.

I did calibrate using the Tee without (OSL) and with (T) the outgoing cable connected but maybe that did result into the error.

What am I doing wrong?

Hi Rune
Have a look on my answer to Erik about his T-Check experiment. There sis some issues about subtracting the delay of the thru adaptor which is missing in you calibration setup (I think ?)

Kind regards

Kurt



-----Oprindelig meddelelse-----
Fra: [email protected] <[email protected]> P? vegne af Rune Broberg
Sendt: 25. september 2019 22:52
Til: [email protected]
Emne: Re: [nanovna-users] NanoVNA Saver



Hi Bryan,

The signs on those phase plots have *really* been bothering me. It's one of the places where it really shows how much of a newbie I am at RF

measurements: I have no idea what way the phase is *supposed* to go, so I might well end up flipping it ;-)



I think I got it all pointing the same way in the coming version, which is in a development branch on GitHub. Maybe I'll post a screenshot and have you (or others) sanity check it before I release!



Thanks for taking the time to report it! Reports like these really help make the software better.



--

Rune / 5Q5R

Hi Erik
Three problems.
First of all you have not subtracted the delay of the Thru adaptor (2 x 62ps) when calibration s11/s22 as you remove the thru adaptor after s11 calibration and thus the calibration plane are 124ps out in the blue air.
Second when measuring s21/s22 you must subtract the delay of the thru adaptor (1x62ps) from the calibration as then you have same phase at the two male SMA adaptor for the two test cables. That is why the T check is only some + - 20% and as seen for my image for 500MHz span as I throw away all points above 500MHz.
Third the range above 900MHz is "stupid" to use as useless
When above is done the T-Adaptor is sitting between two calibration planes where s11/s22 and s21/s12 are correct placed at the two calibration planes being identical to the measurement plane
Good luck with the next steps
Kind regards
Kurt

-----Oprindelig meddelelse-----
Fra: [email protected] <[email protected]> P? vegne af erik@...
Sendt: 25. september 2019 16:54
Til: [email protected]
Emne: [nanovna-users] Trying to understand the T-Check outcome of the nanoVNA

Using a not too good BNC Tee I performed a T-Check Attached the measurement (.s2p) and the excel file (.xlsx) in which the T-Check is calculated.
Next to the T-Check calculation the excel also calculates the abs(Zin-Zout)/Z0 (the percentage absolute distance of the two impedances as another estimate of error) The frequency is denoted in MHz Do ignore anything above say 500MHz

The T-Check suggests the error quickly increases to substantial levels but the abs(Zin-Zout)/Z0 suggests there is a very systematic error in my measurement where the absolute distance of the two rotating impedances grows very linear with frequency.

I did calibrate using the Tee without (OSL) and with (T) the outgoing cable connected but maybe that did result into the error.

What am I doing wrong?