NanoVNA Custom Software

[nctnico]

To be honest there is a bit of an information overflow here. The github page isn't exactly layed out in a way that makes sense for releasing software so for me it is easier to just grab the exe and get the NI runtime.

But needs the program the 64 bit or 32 bit runtime? It would be extremely helpful to know (from the already extensive manual) to get the right NI runtime. I know that a lot of work went into documenting everything but missing this tiny bit of information just trips me up.

[joeqsmith]

To be honest there is a bit of an information overflow here. The github page isn't exactly layed out in a way that makes sense for releasing software so for me it is easier to just grab the exe and get the NI runtime.

But needs the program the 64 bit or 32 bit runtime? It would be extremely helpful to know (from the already extensive manual) to get the right NI runtime. I know that a lot of work went into documenting everything but missing this tiny bit of information just trips me up.

You may have felt at the time your way was easier.  Funny that you post that having it all packaged would have helped.   

You are certainly not alone in your struggles.  There's a reason I bundled everything up and included an installer.   But as the manual says, you can certainly do it your way. 

Git isn't really made to release EXEs.  It limits the file sizes which is the reason for the spanned ZIP.   

2011 is more than 10 years old and I would expect most people would have guessed its 32-bits just because of the age.  The fact the manual talks about running on XP (common) vs XP 64 which was rare and short lived should have been another clue.   

My guess is it will continue to be an uphill battle for you.  You may want to consider using one of the other open sourced programs.   These have several people working on them and I expect have much better support and documentation.   The software may also be a lot easier to learn.  Mine was really written for the EEs and it's far from user friendly. 

If you really want to use it, I suggest you start by following the instructions and use the installer. 

***
I'm guessing you will still have a question on which to use, 32 or 64.   Again, read the attached from Github, or not. 

The few people who follow my channel also may have seen the following where I talk about how to install it.
https://youtu.be/scZ3kZ4Q2sQ?t=1045

Having this level of detail and still having problems with the install is not uncommon.  There are people who just can't get past the install.  If you feel frustrated, your not alone.  Read the last issue posted on Github.  I never knew a VNA had anything to do with COVID 19 or who was president of the USA.   

[nctnico]

To be honest there is a bit of an information overflow here. The github page isn't exactly layed out in a way that makes sense for releasing software so for me it is easier to just grab the exe and get the NI runtime.

But needs the program the 64 bit or 32 bit runtime? It would be extremely helpful to know (from the already extensive manual) to get the right NI runtime. I know that a lot of work went into documenting everything but missing this tiny bit of information just trips me up.

You may have felt at the time your way was easier.  Funny that you post that having it all packaged would have helped.   

I certainly don't want to pick a fight here. I just want to explain my line of thinking in order to offer an insight in how & why I went wrong. We seem to have different views on what is easy. The Github page layout is also not helping me even though there is a releases item. Because the releases box only lists an old version I ignored it; it lead me to believe that the newer versions simply no longer come pre-packaged. Meanwhile I've downloaded & installed the 32 bit version of the 2011 Labview runtime and now the program starts.

And yes, I did try other software. I have a NanoVNA H4 (from nanovna.com ) and I already read that your software likely doesn't support it. No problems there, I just want to try and see how it goes. The other open source software I have tried doesn't seem to run at all without major Linux or Windows OS updates (to get the latest & greatest Python version). The (Windows only) software from nanovna.com does work though. Ultimately I'm researching whether it is worthwhile to get a full fledged VNA or stick with the NanoVNA and control it remotely.

[joeqsmith]

To be honest there is a bit of an information overflow here. The github page isn't exactly layed out in a way that makes sense for releasing software so for me it is easier to just grab the exe and get the NI runtime.

But needs the program the 64 bit or 32 bit runtime? It would be extremely helpful to know (from the already extensive manual) to get the right NI runtime. I know that a lot of work went into documenting everything but missing this tiny bit of information just trips me up.

You may have felt at the time your way was easier.  Funny that you post that having it all packaged would have helped.   

I certainly don't want to pick a fight here. I just want to explain my line of thinking in order to offer an insight in how & why I went wrong. We seem to have different views on what is easy. The Github page layout is also not helping me even though there is a releases item. Because the releases box only lists an old version I ignored it; it lead me to believe that the newer versions simply no longer come pre-packaged. Meanwhile I've downloaded & installed the 32 bit version of the 2011 Labview runtime and now the program starts.

And yes, I did try other software. I have a NanoVNA H4 (from nanovna.com ) and I already read that your software likely doesn't support it. No problems there, I just want to try and see how it goes. The other open source software I have tried doesn't seem to run at all without major Linux or Windows OS updates (to get the latest & greatest Python version). The (Windows only) software from nanovna.com does work though. Ultimately I'm researching whether it is worthwhile to get a full fledged VNA or stick with the NanoVNA and control it remotely.

From my previous post where I quoted the manuals troubleshooting section: 

Installing the EXEs and then randomly guess at which runtime is required. If they manage to find the correct one, they are unable to get the software to communicate with the device because they have not installed the correct VISA.

   Maybe you made it past that second part and actually have it communicating.

There's no fight.   Your original post:

Tried to get the software installed on Windows7 but the NI software won't install. Tried 4 different versions; I'm giving up. It would be so much easier if the NI software is included / bundled into the .exe file.

 
suggests there is a problem.   You were giving up and you never asked for help.  This can leave people with the wrong impression.  So, I provided quotes from the manual and from the on-line help and even a video clip explaining it.  All three were of no help to you.  Had you followed the instructions, or even bothered to read them, you would have seen it required the 32-bit runtime and VISA.  Even after linking the online help here, you were still asking if it was 32 or 64 bits.  I'm just pointing out the obvious.  Don't take offense to it.   Maybe consider what you are posting next time.     

Believe me, I will be the first to admit that this software is not an easy tool to use or learn.  There's a reason I made these videos and wrote that manual.   You read the manual, so I would have thought that the follow would have made that very clear:     

Additionally, there have been ongoing efforts to create other software for the NanoVNAs. I
have not been following their development but understand these programs have been largely
adopted by the radio community. My software was not written for this group. It was designed
as an engineering tool for the RF experimenter.

This manual assumes the reader is PC literate and has some basic understanding of how a VNA
works. It is not a learner’s guide on using a VNA and offers no assistance into solving basic
computer related problems.

This software can be viewed as an engineering tool at best. Its primary use was to extend the
author's understanding of NanoVNA V2 Plus. It was never intended to be used as a general tool
for radio hobbyists to tune their antennas. The software is buggy and not very robust. Even
under normal conditions, expect to run into several problems if attempting to use this software.
It is a very poor choice for the beginner.

As for supporting the H4 (or any other VNAs), it's hard to say really.  The manual talks about the H4 and so does this thread, even recently.  If the firmware is written such that it is backward compatible with the original NanoVNA and the firmware is stable then there is no reason my software would not support it.   I ran several tests with the H4 some time ago and it was not to the level I was expecting.  Still, others are using my software with it.  Of course, it does require you use the correct software which was covered in that video, manual and on-line help.  Or, you can just guess.   

Old firmware was so bad, I ended up writing my own test code to test their code.    Having a stable, automated test was the only way I could keep up with the firmware of the week.   I could try loading in Dislords latest firmware for the H4 and repeat the regression test.   The last time I played with it, we were working on using the VNA to measure a PDN.    Then again, if you are the typical radio hobbyist and just want to look at SWR, then you may be just fine.   It's free anyway so you're not out anything.     

[joeqsmith]

In Lite if remove DC block capacitor and ESD protection diode possible get better results on low frequency range < 10M (but this huge increase chance burn rf switch)

...

I prefer not do hardware mods (use for firmware tests only original hardware)

No problem.  Did you see this data published somewhere that you can provide a link to it?

[nctnico]

The last time I played with it, we were working on using the VNA to measure a PDN.    Then again, if you are the typical radio hobbyist and just want to look at SWR, then you may be just fine.   It's free anyway so you're not out anything.   

My use for a VNA is more likely doing PDN measurements and looking at component behaviour at high frequencies. I already have a network analyser but that only goes to 300MHz which is just not high enough. As a test I measured an elliptic microstripline 1GHz low pass filter I designed / build a about a decade ago with my NanoVNA h4. The measurement shows the filter does something but it is nowhere near accurate (compared to the simulation and measurements -using a swept RF generator + spectrum analyser- I did back then). The noise floor on the NanoVNA h4 is not stellar.  So yes, the NanoVNA h4 is good to see if the impedance / SWR isn't much off and get some very coarse measurements on filters.

[joeqsmith]

I don't recommend using the original NanoVNA or any derivatives above 300MHz.  The software/firmware can't overcome the limitations of the hardware.

To show the difference between the harmonic mode and the direct mode the V2Plus4 uses,  I had demonstrated a GHz interdigital filter and compared the data with my vintage Agilent PNA.   The same video also shows various hacked up circuits made from copper foil tape on FR4 to demonstrate the V2Plus4 working above 1GHz. 

Of course, these low cost VNAs are missing some key features.  I recently watched an YT video where a person was giving a training class on these low cost VNAs.   They talked about some of them having a sinewave drive which of course they don't.    They mentioned the possibility of problems when using a squarewave drive but provided no further details.  So I made a quick video showing one such potential problem.   

Of course there are many other missing features but for educational use, who cares.  They are very inexpensive.   With Dislord's efforts in developing the firmware for the LiteVNA, I would say that one in particular is the most flexible.  Once Dislord releases his latest firmware, I will most likely make a review for it. 
 
https://youtu.be/XaYBpPCo1qk?list=PLZSS2ajxhiQD2gftdurGQoyGpUM_HobNI&t=2732

[joeqsmith]

You can calculate it from IF / Periods count for one AVG / AVG like this:
IF = 60k (for > 400kHz measures, at current firmware)
Periods count for one AVG = 15 (at current firmware)
RBW = 60k / (15 * AVG)
For AVG = 1, RBW = 4k
For AVG = 10, RBW = 60k / (15 * 10) = 400Hz

0xE0 - for Si5351 (< 140MHz range)
0xE1 - for MAX (>140MHz)

Are both E0 and E1 defaults 15?

For RBW is the switch point 400kHz or 140MHz? 
Is E1 then used above 400kHz and E0 <= 400kHz?

Is the 60kHz fixed or can divider be set as well? 

[DiSlord]

E0 used for < 100MHz now (i move thie threshold to 100MHz, MAX2871 allow do this. This reduce generator mode change count in sweep)
E1 for >=100MHz

For < 400kHz used different IF (not 60k), used 12k
For < 20kHz used 6k IF

Default E0/E1 = 15

IF frequency depend from ADC samplerate, and used in DSP sin/cos table size and periods count in it.
IF can`t be any. MAX2871 generate F second MAX2871 generate F + IF, this must be very accurate. Generators not allow set any frequecncy, exist minimum step. This step additional depend from reference TCXO (24M at this moment).
Current step = 24M / 4000 = 6k

[joeqsmith]

When you calculate RBW (IFBW?)  is everything below 100MHz using E0? 

So, < 20kHz
RBW=6k/(E0 * AVG)

20k - 400k
RBW=12k/(E0 * AVG)

400k - 100M
RBW=60k/(E0 * AVG)

> 100M
RBW=60k/(E1 * AVG)

[DiSlord]

Yes, you can measure it as in
https://www.eevblog.com/forum/rf-microwave/nanovna-custom-software/msg4013407/#msg4013407

RBW - central lobe width in Hz

[joeqsmith]

I ask because you may find RBW is acronym mostly associated with spectrum analyzers.   For example:

https://coppermountaintech.com/optimizing-vna-measurement-speed/

I am trying to think about how you would tackle the filter from a user perspective.  I would expect for most VNAs, the user just sets the IFBW they want.  It's independent from frequency.  The software can set the sweep range which could cover all four bands you currently have defined.  It's not in control of E0,E1 & 40 real time during the sweep so it can't dynamically change them.   I also doubt the user will want to poke values into these registers after they calculate what filter they want.   The other problem I see is that you have not yet locked them down and I wonder when you release the firmware, if they would still be prone to changing.   This is why I asked about setting the divisor for the 6k-60kHz.  At least the software would have some control to keep it consistent.   

Maybe I'm not understanding it. 

[DiSlord]

Yes better name it as IFBW

register 0x40 (avg setting) present in all LiteVNA firmwares
registers E0/E1 also present in all, but better not use it, only if need very fast sweep (use only 0x40), i leave it for debug use in all fw
Power setting 0x41 and 0x42 registers also present in all firmwares (just fix apply in CW mode in last official fw)

0x44 - (S11 or S21 data select) added only in last beta, and i plan leave it for future use

PS It is quite difficult for me to operate with technological terms, English is not my native language

[joeqsmith]

Google translate has made it a smaller world.  Without it, you and I would not be working together and that would be a shame.   

VNAs I have used IFBW is constant across the entire sweep range.   With Lite,  presented with a selection of four bands (maybe more depending on what you settle on) .  The data for the IFBW pull-down is populated when changing E0 and/or E1. 

I can hear the screams of the poor users now.     Give it some thought. 

[DiSlord]

The low price of NanoVNA/V2/LiteVNA allowed many users to get it, and lowered the entry threshold. Many users with little skill have started to use the instrument and have many questions.

This little device has a lot of options available on professional devices, but there is no good description.

[joeqsmith]

I suspect most users are CB and amateur radio hobbyist who were sold on it being an antenna analyzer.  It seems to be the one area that they generally still enjoy constructing their own.    Most features would never be utilized by that group and I suspect just further confuses them.   Most are going from a simple SWR meter and now placing the VNA in-line with their PA and antenna.    

Using a PC can make it easier and more flexible.  It also provides a system with basically unlimited resources compared with the embedded system.  Still, there is only so much the software can do.  It's at the mercy of how the firmware is designed.

My experience based on feedback from users,  there is little benefit from investing in documentation.

[jspencerg]

Hello,  I have realized the source of my confusion about the graphs showing crystal filters in different vna's. My ignorance and not paying attention.  Need I say more?

I appreciate getting to watch your conversation as you work on firmware and software to eke or as much performance as possible from the hardware.  I've always admired the concept of continual improvement.
I went ahead and bought the nanovna-h and the v2plus. I did my best to get instrument that were not clones and which ran in Dislord's firmware.  I appreciate things will change, but my hope is that your collaboration will see continued functionality with Joe's software (Does the program have a proper name?)
Joe,  perhaps the day will come when you have to specify the specific hardware and firmware which will be compatable with your program?  Maintaining and testing compatability with the variations is a job which you have not signed up for!
I know I'm ignorant, but I am learning.  I've decided to use program SimSmith and videos from WOQE along with a text to learn about Smith charts. I hope to understand and implement features of Joe's program in the future.  Joe's presentation and explanations of his experiments are helpful and inspire me to better understand.
Thank you Joe and Dislord for your work and for sharing the process.

[realfran]

Stand-alone device portability is useful making the habit of (mobile phone gadget)
"

Using a PC can make it easier and more flexible.  It also provides a system with basically unlimited resources compared with the embedded system.  Still, there is only so much the software can do.  It's at the mercy of how the firmware is designed.

Using the PC resource can make one powerful software to use with this low-cost VNA.
Personally, I learned much and want to learn more to use the VNA, not only one gadget but like a real instrument (with is on limitation).

[joeqsmith]

...proper name

I've never given it any thought.  They are typically named after the instruments they support.   HP3589A.EXE for example.  Let me know if you have something in mind.   

I went ahead and bought the nanovna-h and the v2plus.

I have no plans to further support the older units and many of the new features we are discussing here are only supported by the Lite.   

..want to learn more..

I've been reading "The VNA Applications Handbook".  The first couple of chapters are available free on-line.  It covers many of the basics.  You may want to have a look. 

Lite with firmware avg set to 10 and 20, with common mode transformer and 100uohm resistor attached.   Compared with the original NanoVNA.  Don't ask how long the Lite took to run those sweeps.

[realfran]

I'm computer illiterate hope  someone gives one simple way to get the possibility and freedom to install the Dislord firmware or other on the NanoVNA 2V plus4 

[joeqsmith]

Really odd problem with Flipper's Lite.   We are not sure if it came this way or if this is a problem that has happened over time. 

We were testing with nothing attached to the Lite, except the end caps.   We had programmed in your latest test firmware and looking at the noise of S21 in the 9KHz to 1MHz range.    There is a 20dB step in the noise at 400kHz where it jumps from 80dB to 60dB.   There is no calibrations applied.  We rolled it back to the last released firmware and it had no effect.   If we change the sweep range to 1M to 100M, its roughly 60dB.

If we run it standalone disconnected from the PC, S21 drops to 80dB.  Plugging in the USB cable (but not running any software), it jumps back up to 60dB with the step at 400kHz.   

***
We tried different ports on the PC as well as used a powered hub and different cables, no effect. 

Taking the unit apart, it appears the same as my Lite.   We removed the battery and ran it from the PC, noise still present.   Totally different from how mine behaves.
***
We tried a few different PCs, again no effect.  Shown also is sweeping Flipper's from 1M to 100MHz.

For comparison, my Lite is shown in J1&2.  The USB port on mine seems to have no effect.     



   

[joeqsmith]

If I run 50 averages on mine, we can see the switch point at 400kHz but mine actually decreases rather than increases like Flippers.

[cdev]

By default Ive gotten in the habit of leaving ferrite beads on both pigtails and the USB on my nanovna2. Having an RTLSDR made me strange that way.. lol

Really odd problem with Flipper's Lite.   We are not sure if it came this way or if this is a problem that has happened over time. 

We were testing with nothing attached to the Lite, except the end caps.   We had programmed in your latest test firmware and looking at the noise of S21 in the 9KHz to 1MHz range.    There is a 20dB step in the noise at 400kHz where it jumps from 80dB to 60dB.   There is no calibrations applied.  We rolled it back to the last released firmware and it had no effect.   If we change the sweep range to 1M to 100M, its roughly 60dB.

If we run it standalone disconnected from the PC, S21 drops to 80dB.  Plugging in the USB cable (but not running any software), it jumps back up to 60dB with the step at 400kHz.   

***
We tried different ports on the PC as well as used a powered hub and different cables, no effect. 

Taking the unit apart, it appears the same as my Lite.   We removed the battery and ran it from the PC, noise still present.   Totally different from how mine behaves.
***
We tried a few different PCs, again no effect.  Shown also is sweeping Flipper's from 1M to 100MHz.

For comparison, my Lite is shown in J1&2.  The USB port on mine seems to have no effect.     



 

[joeqsmith]

I suspect this problem is similar to what I see with my V2Plus4.   I suspect it uses a SMPS when running off the USB and this is the source of the noise.  Sadly the schematics do not appear available.    I can use the USB interface with the V2Plus4 without any problems as long as I don't power off it.    Even using a linear supply or batteries will not help.  The noise source is internal to the V2Plus4.   Still, I had Flipper purchase some very lossy cores but doubt it will have any effect.  He has another Lite on order in hopes of getting a good one.    I'll post an update once we have more information.

[cdev]

I have a habit from way back of using a .22 or .33 yellow tantalum capacitor across the USB rails. (used to be common in cheap phone handsets) Not so large that the current draw will cause USB enumeration to glitch but significantly smooths out the DC power. Have never seen any problems from doing this with those low value tants. The original maker of the first nanovna also recommends doing this with USB devices.. (this wasnt referring to nanovna though.. He just, like I always does this.