¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
Date

Re: NanoVNASaver QT Platform problem (won't load)

jim
 

on the other end of the "scale" ..someone gifted me a HP Stream (2018 model) ...running Linux Mint 19.1 ..has more than 10 g freespace left on solid-state fixed drive
(if you don't want to mess with your current device) ...approx $200 on amazon

Jim

On Wednesday, November 6, 2019, 7:25:55 PM UTC, Jim Allyn - N7JA <jim@...> wrote:

On 11/6/19 9:38 AM, DougVL wrote:
My PC runs Windows Vista with all available updates made.? I suspect this may be the problem, but no newer operating system is available for this computer.

???? Yes, there is a newer operating system available for your
computer:? Linux.? Windows Vista is out of support and no longer
updated, so, if you continue to use it, at a minimum you should keep it
off the internet.? I have updated many older computers running Vista, XP
(and even earlier versions) to Linux.? A common comment from the owners
of those computers is, "Wow, this is faster than it ever was, even when
it was new!"? Linux is a great way to breathe new life into older
computers.? Something to think about, anyway.? If you want more
information on using Linux on our old computer, you can email me off-list.

????????????????????????????????????????????? Jim, N7JA


Re: Chasing ghosts??? #internals #calibration

 

Setting power to 1 removed most of the noise and also the jump when switching to harmonics mode disappeared but it also resulted in yet another different oscillation pattern above 600MHz.
For measurements till about 400MHz power level 1 is for sure the best as the cable attenuation for both cables is very lineair, even for the RG58
Above 400MHz there is still a ghost hiding somewhere
The oscillation seems to be faster then the rotation speed from the cable length so there could be some capacitive factor involved.
For the cable model I use only a first order rotation with frequency. Should I add somewhere a cable specific capacity that accelerates and amplifies the rotation impact at higher frequencies?
--
Erik, PD0EK


Re: NanoVNASaver QT Platform problem (won't load)

 

On 11/6/19 9:38 AM, DougVL wrote:
My PC runs Windows Vista with all available updates made. I suspect this may be the problem, but no newer operating system is available for this computer.

???? Yes, there is a newer operating system available for your computer:? Linux.? Windows Vista is out of support and no longer updated, so, if you continue to use it, at a minimum you should keep it off the internet.? I have updated many older computers running Vista, XP (and even earlier versions) to Linux.? A common comment from the owners of those computers is, "Wow, this is faster than it ever was, even when it was new!"? Linux is a great way to breathe new life into older computers.? Something to think about, anyway.? If you want more information on using Linux on our old computer, you can email me off-list.

????????????????????????????????????????????? Jim, N7JA


Re: NanoVNA-Saver 0.1.5

 

On Wed, Nov 6, 2019 at 01:16 AM, Rune Broberg wrote:


Have you set the NanoVNA to normal (non-TDR) mode before making the
readings?
If you would be willing to send me a Touchstone file of the data, that would be helpful for testing! :-)

Rune,

Yes, I did set the nanoVNA to non-TDR mode before making the readings. This is essential to getting good data in nanoVNA-Saver from the nanoVNA. I recalled cal0 which was created with my best SMA calibrators (from another VNA) on short male-female connector savers attached directly to the nanoVNA.

Attached is an S1P file from the ~0.5m long RG316. I also have attached an S1P file from the ~1 m long 75 ohm cable that you can use for testing with nanoVNA-Saver 0.1.5. Using the velocity factor for RG316 as 0.695 give a length of 0.56 m for that cable. Setting the velocity factor for the 75 ohm cable to 0.66 yields a cable length of 1.086 m. The cables are showing a little longer than the measured length because of some 50 ohm adapters that are about a total of 2" long on the nanoVNA end of the cables. These are the same cables I used in the nanoVNA screen shots shown above.

Both cable measurements were made using my best nanoVNA calibration and the best tuned nanoVNA-Saver calibration.

I hope these help your efforts with the TDR software to show the impedance vs time.

--
Bryan, WA5VAH


Re: Looking for firmware with battery indicator, 1500 and big font

 



4 traces, big font, big info screen, 1500 Mhz, battery indicator
Has anyone tried it lately?
YT9TP - Pedja could not calibrate over 310MHz on Oct 22
/g/nanovna-users/message/5510


Re: NanoVNA software developers wanted #hacking

 

That is a lot of data to buffer.
Given custom NodeMcu/nRF5 firmware, nanoVNA need pass only 101x2x4 bytes of float per scan,
which could then be converted to ASCII by BTLE micro for USB COM compatibility.


Re: Looking for firmware with battery indicator, 1500 and big font

 

Hi,

Maybe this in interesting for you:

4 traces, big font, big info screen, 1500 Mhz, battery indicator

2 traces (AA version), big font, 1500 Mhz, battery indicator

Battery indicator requires an additional diode.


Re: Chasing ghosts??? #internals #calibration

 

Dana,

Indeed, and for that reason I measured the same cables with the same calibration kit on thee different VNA's. (one the nanoVNA)
The results from the 3GHz VNA convinced me the fluctuations seen at the nanoVNA where not originating from the cable as such.
If this is a a wrong assumption I'd welcome an explanation to avoid I'm chasing ghosts
--
Erik, PD0EK


Re: errors of "error" models

 

Hi Erik;

I was raised to believe that there is no such thing as a stupid question, but after several decades of not being exposed to the light, I discovered that there are actually many... All of them are the ones that never get asked. :-)

From my perspective at least, the question you asked was a brilliant one, as evidenced by the response it solicited. It is a struggle for me to capture much of the understanding I'm attempting to achieve through the many segmented and translated responses. Its only fair to assume that the reverse holds true for them as well. Their published documents on this are much better written English translations, but they don't stand on their own for all readers, and for those of us who have had limited if any exposure, are left with many unanswered questions.

We ask questions to get smarter. Very often it is helpful to hear "You don't understand." If we fail to ask questions that solicit such a response, we might well go through our lives with the truly stupid notion that "We must be pretty smart."; while in fact we have no understanding at all. :-)

Sometimes I ask questions that I believe I know the answer to very well, to verify my understanding. I am a married man, so I have learned that just because I'm confident that I have all of the right answers; most of the time they are entirely incorrect. LOL!

--
73

Gary, N3GO


Re: NanoVNA software developers wanted #hacking

 

That is a lot of data to buffer
nRF52832-QFAA/QFN48 has 64KB RAM + 512KB flash

ESP8266 reportedly has > 40KB heap+data space available.

I guess HC-05/6 is unbuffered but also not BTLE,
so less interesting for e.g. Web Bluetooth API


NanoVNASaver QT Platform problem (won't load)

 

I've tried NanoVNASaver v0.1.3 and v0.1.4 but they will not start. I get a DOS window with the error message:
"Could not load the Qt platform plugin "Windows" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: minimal, offscreen, webg1, windows."

Reinstalling NanoVNASaver (either version) did not fix the problem.

My PC runs Windows Vista with all available updates made. I suspect this may be the problem, but no newer operating system is available for this computer.

Is there any known solution to not loading the Qt platform?

NanoVNA Sharp works well, though.

Thanks,
Doug, K8RFT


Re: NanoVNA software developers wanted #hacking

 

That is a lot of data to buffer.

On Wednesday, November 6, 2019, 12:14:38 p.m. GMT-5, Oristo <ormpoa@...> wrote:

> At the minimum you may
need to include some ferrite beads in the power and serial connections.
Firmware should sleep Bluetooth while sweeping and pause sweeps while Bluetooth is active.


Re: NanoVNA software developers wanted #hacking

 

At the minimum you may
need to include some ferrite beads in the power and serial connections.
Firmware should sleep Bluetooth while sweeping and pause sweeps while Bluetooth is active.


Re: NanoVNA software developers wanted #hacking

 

Before adding a radio transmitter and a second microcontroller such as a
HC-05 to the NanoVNA, you may want to examine how much RFI it might
introduce into the NanoVNA. My experience with my VNA, which I have
connected a HC-05 to, is that it introduces a lot. At the minimum you may
need to include some ferrite beads in the power and serial connections.

On Wed, Nov 6, 2019 at 11:27 AM William Heller <wheller34052@...>
wrote:

I am a retired embedded processor engineer an can recommend the ESP32
programmed as a serial to bluetooth/WIFI adapter it is a 32 bit processor
with the usual peripherals and both bluetooth and WiFi built in and do on
and do small pub only costs a few do?lars.

On Wed, Nov 6, 2019, 7:42 AM vaclav_sal via Groups.Io <vaclav_sal=
[email protected]> wrote:

Nice, but I am after adding the bluetooth externally.

Like to ask if it would make more sense to add processor internally
supporting wireless commodification.
I have not done any research if such processor exists.

Something in Raspberry Pi Zero style.






Re: Chasing ghosts??? #internals #calibration

 

RG-58 is just plain junk cable, and should never be used or (especially) trusted to
yield meaningful results in any measurement situation. The center conductor flops
around inside the shield at the slightest provocation (even quantum fluctuations),
leading to impedance variations from location to location as well as to phase variation
with bending. Further, RG-58 and similar single-shielded cables often have very poor
shielding integrity.

Also, with just about any cable, if it is poorly made it can exhibit so-called "structural
resonances" due to spatially-periodic variations in characteristic impedance arising
from the manufacturing process. Normally this is a problem only with cheap cables,
but in principle could occur with any. The result can be a surprisingly-sharp increase
in attenuation at and beyond the resonant frequencies, even though said frequencies
be far below the first "moding" frequency.

Dana K8YUM


Re: Chasing ghosts??? #internals #calibration

 

And here are the results.
The first picture is with power level 3 when above 300MHz, second picture is with powerlevel is 0 for all frequencies.
The noise is much higher with low power and that can be improved by running from a well regulated 5V supply.
The scale of the logmag S11 is different so do not compare the angle but only if the cable loss is a straight line (which has not improved.....)

So, although running at low power has a big impact as the uncalibrated jump at 300MHz is now almost gone, but this was mostly hidden by the calibration, There is maybe some impact above 600MHz. A bit less wild maybe.....

--
Erik, PD0EK


Re: NanoVNA software developers wanted #hacking

 

I am a retired embedded processor engineer an can recommend the ESP32
programmed as a serial to bluetooth/WIFI adapter it is a 32 bit processor
with the usual peripherals and both bluetooth and WiFi built in and do on
and do small pub only costs a few do?lars.

On Wed, Nov 6, 2019, 7:42 AM vaclav_sal via Groups.Io <vaclav_sal=
[email protected]> wrote:

Nice, but I am after adding the bluetooth externally.

Like to ask if it would make more sense to add processor internally
supporting wireless commodification.
I have not done any research if such processor exists.

Something in Raspberry Pi Zero style.




Re: T-Check for my nanoVNA - Results look excellent below 150 MHz and acceptable up to 300 MHz

 

Hi Rudi
Super you are on the way now. I just did a T-Check for some N cal kit work presently working on and it was below 1 % all the way. That is the magic of 12 term error correction (actually 10 term as isolation not done)
Regarding the listType= lin I loaded into a text editor a s2p file I had saved long ago from the VNWA to study the header of the Touchstone file and there it was. It is just a comment line so why it had any impact I do not know
I checked the Touchstone specification version 1.1 and it is not part of the specification at all.
Kind regards
Kurt


-----Oprindelig meddelelse-----
Fra: [email protected] <[email protected]> P? vegne af reuterr@...
Sendt: 6. november 2019 16:34
Til: [email protected]
Emne: Re: [nanovna-users] T-Check for my nanoVNA - Results look excellent below 150 MHz and acceptable up to 300 MHz

! ListType=Lin (This addition was probably not needed)
Hello Kurt,

This 'ListType=Lin' parameter was necessary :-)
Question: where did you found that parameter 'ListType=Lin'?
I looked in specification touchstone_ver2_0.pdf, and in VNWA_HELP_36.7.8.pdf and in How to perform a T-Check for a VNWA Calibration.pdf and did not found it.

Now it works, see attached screen shot VNWA_nanoVNA-Saver_T-Check.png

Thank you very much for this hint and you help.

73, Rudi DL5FA


Re: NanoVNA software developers wanted #hacking

 

if it would make more sense to add processor internally supporting wireless
commodification.
Link added in /g/nanovna-users/wiki/Mods-and-Design-Notes


Re: Looking for firmware with battery indicator, 1500 and big font

 

Sorry, I'm not following the group regularly.
Is there any firmware with battery indicator, 1500 MHz and big font ?