NanoVNA Custom Software

[purpose]

Whilst mine was the cheapest H4 on aliexpress, it came in the presentation box that I would expect a real H4 to come in.
Clone or not, it works well, so I don't think you could go wrong with anything claiming to be an H4, as there's so little to them.

Nooelec appear to be the official N. American H4 distributor....
https://www.nooelec.com/store/test-equipment/analyzers/nanovna-h4.html
A few bucks more expensive than China, but you get the real deal for sure.

Chasing the identical jobbie might be futile.

Peter

[joeqsmith]

I suggest you post pictures of your PCB to the group and ask there.  Maybe someone there can confirm if they are the same.   

If I am going to attempt to solve these problems your having  when attempting to use unsupported firmware and hardware,  I need an identical setup.   The real deal could cause a huge time waste.   

One option if you don't want to take the time to dig into it, you could buy the same product from the same supplier.   

****
Looking at the manual in the link you provided, it's basically a rib off from the original.  No big deal but when I compare the schematic in the manual against the original hardware I have, there are very few changes.  The same micro is is used.   I thought the H4 had a different micro to support that 401 data points your wanting to play with?    Maybe I missed something.   

[purpose]

If I am going to attempt to solve these problems you're having

I'm not having any problems. Everything appears to be fully functional.
Possibly a few questions about your software post v1.08, but other than that, nothing.

[joeqsmith]

If I am going to attempt to solve these problems you're having

I'm not having any problems. Everything appears to be fully functional.
Possibly a few questions about your software post v1.08, but other than that, nothing.

Odd, maybe your short term memory is starting to fail you.  I didn't order that hardware because everything was all fine in the world of Purpose!     
https://www.eevblog.com/forum/rf-microwave/nanovna-custom-software/msg3552390/#msg3552390

Or, maybe you're suggesting you will not attempt to use the newer software with unsupported hardware/firmware or at least not question it when it doesn't work.   

[purpose]

Odd, maybe your short term memory is starting to fail you.

Could easily be amnesia, or early onset Alzheimers.

I didn't order that hardware because everything was all fine in the world of Purpose!

I hear that and thought it very nice of you to offer to buy an identical gizmo in order to see why your software was not working as expected with my gizmo,  but v1.08 worked nicely and it was only the later stuff that didn't. If memory serves me (cough), we agreed to stick with 1.08.

Or, maybe you're suggesting you will not attempt to use the newer software

I've said, or thought no such thing. You make em... I'll try em... was something I did say.

with unsupported hardware/firmware or at least not question it when it doesn't work.

I was reporting, not questioning. I'll try any version of your software you want me to.

If I have to buy something to add to your collection, then so be it, but if you ordered from the link I sent and you didn't receive it, then we might have a problem getting the identical piece.

[joeqsmith]

I was reporting, not questioning. I'll try any version of your software you want me to.

Morning Mr. Smith,

In v1.11 I adjusted the points box to 401 (highlighting and inputting from the keyboard) and saved to defaults. Restarting shows 401, but as soon as I link, it jumps
back to 101.
...

Am I missing something other than grey matter?

Peter

That looks like a question to me, not reporting.   The manual is clear about what the software supports.  Reporting on unsupported combinations isn't helpful.  In the future I will handle it differently.   

...   but v1.08 worked nicely and it was only the later stuff that didn't. If memory serves me (cough), we agreed to stick with 1.08.

You may certainly use any version I have made available but I have no intent on sticking with it.

If I have to buy something to add to your collection, then so be it, but if you ordered from the link I sent and you didn't receive it, then we might have a problem getting the identical piece.

Maybe but my track record with Amazon has been good.  With them stocking the product, I doubt it would have been a problem. 

[purpose]

That looks like a question to me, not reporting.
That was quite obviously a report, followed by a question which was nothing to do with the software.
You're not getting away with that.

You may certainly use any version I have made available but I have no intent on sticking with it.
Fair enough.

I doubt it would have been a problem.
Jeff Bezos to the rescue.
Personally, I prefer to give my dosh to the little guy.

[cdev]

I have a whole bunch of fair-rite very tiny balun cores, beads, etc. I have several materials.

I am assuming you want to try the effect of a small decoupling transformer vis-a-vis smoothing out the peakiness shown in the images?


Now I have an original nanona2 and a bunch of TH components, probably the ones you used (including the coil) as well as the toroids, probably. As well as the breadboards. I also have some gold plated DIP plugs with solderable pins ideal to carry the xformer. From experience this works great up to a few hundred MHz.

Can I attempt to replicate what you are trying to do which I am guessing likely involves either a 1:1 or fixed ratio transformer (1:4?) to match the nanoVNA to the "transmission line" on the breadboard?

I'd be happy to bang it together, scan the DUT at the proper range and then show you what the results are via screenshot here. I would be using the software that I have which is the QT software (which works fine for me)

I dont have a windows box so cant run windows apps. My wine install is broken now too.

This is not an inconvenience because I have been meaning to try exactly this, to check this out for a while.

I also have the nanovna test board and a bunch of stripboard (good for series and shunt testing fTH components but ...

And SMA connectors. and my x-acto knife and soldering iron. would be good for HF, too much capacitance to work well much above that. But okay for banging out filters for HF.

Sweeping 20KHz to 100M, still no transformer and unit is not calibrated.    Plot A, starting with a tant for the bulk. B, adding a 0.1.  C adding a 0.001uF.

Should be fine at 100 MHz.

[joeqsmith]

I have a whole bunch of fair-rite very tiny balun cores, beads, etc. I have several materials.
..

Can I attempt to replicate what you are trying to do which I am guessing likely involves either a 1:1 or fixed ratio transformer (1:4?) to match the nanoVNA to the "transmission line" on the breadboard?
..

I am guessing that you are talking about making that crystal test jig on a breadboard which seems like it could work.  You may get better results building it up on perfboard.   I have never looked at any of the other software for the NanoVNA but assume what ever you are using supports the measurement.   

Sweeping 20KHz to 100M, still no transformer and unit is not calibrated.    Plot A, starting with a tant for the bulk. B, adding a 0.1.  C adding a 0.001uF.

Should be fine at 100 MHz.

   

The quote you mention from the following post is testing out some new routines to look at the impedance of the power rails.   The mentioned transformer  is not the impedance matching bifilar transformer used for the crystal test fixture.  Instead its a coaxial transformer used to break the ground loop when making shunt through measurements at low frequencies.   The breadboard allows me to build up simple networks used to test the software.   

https://www.eevblog.com/forum/rf-microwave/nanovna-custom-software/msg3559860/#msg3559860

[joeqsmith]

I doubt it would have been a problem.
Jeff Bezos to the rescue.
Personally, I prefer to give my dosh to the little guy.

No worries.  I have no plans to pursue it further.   

[purpose]

That'll do me.

[ars_ha3hz]

Hello joeqsmith,
I read earlier (in 2019) in the forum group, a lot of changes have happened since then. Yesterday I downloaded the program and tested NanoVNA v1.08. I attach the difference between the current firmware 1.0.62 (not yet released by DiSlord) and the shell commands in version 0.8.0. I hope you find it useful. I find the program interesting, but I have a lot to learn about using it. A small spelling: there is an unnecessary 'i' in the text in the info window: 'Th (i) e quick brown fox jumps over the lazy dog' telex test text in which all letters are included.

Gyula

[joeqsmith]

I wouldn't be surprised if you found other spelling errors in the software or documentation.  Please feel free to post them as you find them and I will correct them on the next release.   

Radiolistener's firmware running on the original hardware from a more than a year ago seems to be the only stable combination I have found.   

I think I am up to four software problems with 1.08 so far.  I have no plans to fix any of them.  If I get something I feel is useful working with the PDN measurements, I will release 2.0 for both the original hardware and the V2Plus4.   If you have read the last few pages, this new software will most likely be even less compatible with the newer versions of firmware and various hardware that pops up. 

[joeqsmith]

My latest version of software for the original NanoVNA only uses three commands.  One of those is obviously Freq where I only use two of the sub commands.  After working with the V2Plus, I settled on a much simpler approach. 

[DiSlord]

For NanoVNA version greater 0.7 you can use one command
scan start stop points 7

start - start frequency in Hz
stop - stop frequency in Hz
points - points count (up to 101 for H version, up to 201 or 401 (on my fw) for H4)

It return all measured data after
Example see screenshot
Command return list of measured data
freq s11_re s11_im s21_re s21_im

PS you can use faster exchange mode im my fw (in binary format as vs V2)
scan start stop points 15
In this case returned binary
uint16_t mask;
uint16_t points;
struct {
 uint32_t freq;
 float s11_re;
 float s11_im;
 float s21_re;
 float s21_im;
}data[points]

[purpose]

Mr. DiSlord,
Спасибо for the great firmware. 

[joeqsmith]

DiSlord,

Hopefully my last response solves your regional settings problem.  Make sure you read it carefully. 

Without having the H4 hardware, there is little reason for me to try and run your firmware at this time.   The goal would have been to replicate Purpose's setup in an attempt to help them out.  They have some flavor of an H4 which I was unable to obtain.    Not a big deal as the original hardware will do what they need and it seems that my software at least somewhat works with his H4 setup.   

Again, thanks for providing me with help on the command set.   

[joeqsmith]

Shown with a 7805 regulator, 1.84MHz oscillator, meter and various caps.   The DC blocks and transformer are installed.     

[harrimansat]

Shown with a 7805 regulator, 1.84MHz oscillator, meter and various caps.   The DC blocks and transformer are installed.   

good job!, where can I download VI?

Thanks

[joeqsmith]

Shown with a 7805 regulator, 1.84MHz oscillator, meter and various caps.   The DC blocks and transformer are installed.   

good job!, where can I download VI?

Thanks

I have never released the source code (VIs), only the EXEs.  You will find the link to my Github account in my signature.

Make sure you read the README BEFORE you try and download and install it.   One of the most common problems people ask me is they will download the EXE and then they try and find the runtime for it, then if they manage to find the right version, the software won't find the device because they still haven't installed VISA.      The next problem is people will try and use the wrong software for their device.  They have the V2Plus and are trying to use the software for the original hardware.    I suspect DisLords problem with their regional settings is they didn't change their .INI file covered in the manual. 
There are also cases of trying to use the software with unsupported firmware/hardware.  Most likely 2.x is be be even less compatible.   I suggest archiving the current versions.      If you manage to get it running, the next hurdle will be reading the manual.   

The PDN measurement features are still being developed.  The changes will need to be added to the V2Plus and the manual needs to be updated.  So it's a ways off. 

[joeqsmith]

Using the same setup, the original NanoVNA was swept from 10kHz to 1.5GHz using a thru.  The data was then normalized.   Next both ports were terminated using a common shield.

[joeqsmith]

Looking at the calculated resistance with both ports terminated, it's a bit under 3mOhms from 20kHz to 70MHz.   

The V2Plus4 is limited to 50kHz which we saw from looking at the 100uOhm resistor is already on the high side. 

[joeqsmith]

Using the same setup but removing the homemade common mode transformer.   We wouldn't expect there to be any difference as we are after all testing with the two ports terminated and there should be no ground loop.    More a sanity check than anything.

[joeqsmith]

Using the completed setup to sweep the 100mOhm, 25mOhm and 1mOhm resistors from 20kHz to 70MHz.   Still a few more things to work out but for a $50 VNA, I'm impressed.  The V2Plus4 is limited to 50Khz which is better then my new boat anchor. 

When I was looking for a new VNA I was interested in finding something that would be usable at these lower frequencies.  Asking about what was available in the HPAK group,  some of the feedback suggests not many people have a use for it.   I'm keeping my fingers crossed that the new low cost VNAs are able to measure narrow band devices as well as make some of these low impedance measurements. 

True, but wanting your Microwave VNA to go down to DC is like
wanting your Ferrari to have tank tracks.

It just isn't right.  Better would be to have a Ferrari and
a tank.  They serve different functions.

-Chuck Harris

[joeqsmith]

25, 1 and 0.1 mOhms.   The 0.1 mOhm appears less inductive but we can see its beyond what the original NanoVNA can measure.