¿ªÔÆÌåÓý

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

Re: Build timestamp as proxy for FW build version

 

We could do with better documentation on this device eg the wiki. If
features/behaviours are different between builds they'll need documenting
and users will need to know which version they have to understand the
documentation fully. In addition users will be better informed if newer,
hopefully improved, builds become available.

Mike

On Sun, 28 Jul 2019, 18:43 Dave Daniel, <kc0wjn@...> wrote:

I should have asked what is the problem for which a solution is being
sought?

DaveD

Sent from a small flat thingy

On Jul 28, 2019, at 13:01, Mike Brown <mbmail@...> wrote:

Apologies if this has already been suggested but pressing the FW info
button in NanoVNA 1.03 returns information on the Nano's firmware,
including build 'time'.

Might the build timestamp be usable as a way to tell the different
versions
apart?

As a starter, my NanoVNA is a 2-trace 900MHz antenna analyser with build
time May 5 2019 - 08:35:00.

Best regards

Mike


---------- Forwarded message ---------
From: Michael Brown <mike.g4raa@...>
Date: Sun, 28 Jul 2019, 17:53
Subject: NanoVNA FW info 2-trace 900MHz Antenna Analyser
To: mbmail@... <mbmail@...>


Attached



Sent from Mail <> for
Windows
10



<Semi-bad 2 trace 900 MHz antenna analyser FW info.jpg>



Re: Build timestamp as proxy for FW build version

 

I should have asked what is the problem for which a solution is being sought?

DaveD

Sent from a small flat thingy

On Jul 28, 2019, at 13:01, Mike Brown <mbmail@...> wrote:

Apologies if this has already been suggested but pressing the FW info
button in NanoVNA 1.03 returns information on the Nano's firmware,
including build 'time'.

Might the build timestamp be usable as a way to tell the different versions
apart?

As a starter, my NanoVNA is a 2-trace 900MHz antenna analyser with build
time May 5 2019 - 08:35:00.

Best regards

Mike


---------- Forwarded message ---------
From: Michael Brown <mike.g4raa@...>
Date: Sun, 28 Jul 2019, 17:53
Subject: NanoVNA FW info 2-trace 900MHz Antenna Analyser
To: mbmail@... <mbmail@...>


Attached



Sent from Mail <> for Windows
10



<Semi-bad 2 trace 900 MHz antenna analyser FW info.jpg>


Re: Build timestamp as proxy for FW build version

 

Well, build timestamp and the file set used in the build are not necessaily correlated. One could build the code repeatedly using the same files; each build will have a different timestamp. It is more or less true, though, that it would be difficult to create two builds with different file sets that have exactly the same timestamp.

Version control is really the only method that works reliably. Many, many engineers have westled with the question of how to provide SCM for many decades. So far, we are still using SCM tools to manage version control.

DaveD

Sent from a small flat thingy

On Jul 28, 2019, at 13:01, Mike Brown <mbmail@...> wrote:

Apologies if this has already been suggested but pressing the FW info
button in NanoVNA 1.03 returns information on the Nano's firmware,
including build 'time'.

Might the build timestamp be usable as a way to tell the different versions
apart?

As a starter, my NanoVNA is a 2-trace 900MHz antenna analyser with build
time May 5 2019 - 08:35:00.

Best regards

Mike


---------- Forwarded message ---------
From: Michael Brown <mike.g4raa@...>
Date: Sun, 28 Jul 2019, 17:53
Subject: NanoVNA FW info 2-trace 900MHz Antenna Analyser
To: mbmail@... <mbmail@...>


Attached



Sent from Mail <> for Windows
10



<Semi-bad 2 trace 900 MHz antenna analyser FW info.jpg>


Marker control "knob"

 

I haven't seen any mention this, but you don't need a stylus to use the menus. You just press down the center of the marker knob, and the menus come up. You use the left and right (+ & -) to move the green "bar" up and down, then press down again
Frank


Build timestamp as proxy for FW build version

 

Apologies if this has already been suggested but pressing the FW info
button in NanoVNA 1.03 returns information on the Nano's firmware,
including build 'time'.

Might the build timestamp be usable as a way to tell the different versions
apart?

As a starter, my NanoVNA is a 2-trace 900MHz antenna analyser with build
time May 5 2019 - 08:35:00.

Best regards

Mike


---------- Forwarded message ---------
From: Michael Brown <mike.g4raa@...>
Date: Sun, 28 Jul 2019, 17:53
Subject: NanoVNA FW info 2-trace 900MHz Antenna Analyser
To: mbmail@... <mbmail@...>


Attached



Sent from Mail <> for Windows
10


Diles, Folders and Wikis on the nanovna group

 

All,

I have enabled files, photos and wikis for this group. You should be able to upload files and photos and create wikis now.

Please, please, create subfolders when you upload files or photos. For single files or photos which do not warrant their own subfolder, I have created subfolders named "Miscellaneous".

The Photos folder contains 110 photos which are those attached to previous posts (groups,io did this automatically).

If anyone has questions about these, or discovers a problem, please let me know.

DaveD


Re: Suggestion to have a wiki

 

Since groups.io has a built in wiki: using that one seems like a path of
least resistance...

The list owner just has to enable it.

Neil

On Sat, Jul 27, 2019, 18:14 Dave Daniel <kc0wjn@...> wrote:

Ok, with what do you agree? It¡¯s not clear from your post whether you
think we need a wiki or not.

Just to be clear, I don¡¯t have a problrm with having a wiki. But someone
will have to create it and administer it. That will probably be time
intensive.

DaveD

Sent from a small flat thingy

On Jul 27, 2019, at 20:43, Jeremy Dunman W1BO <jeremy@...> wrote:

TOTALLY agree! Going back through message after message is difficult at
best. Case in point today working on my antenna and went to pull the
VNAsharp down for my lap top and spent probably 30 minutes searching for
the location of the file.

Jeremy Dunman
W1BO

------ Original Message ------
From: "Dave Daniel" <kc0wjn@...>
To: [email protected]
Sent: 7/27/2019 8:21:57 PM
Subject: Re: [nanovna-users] Suggestion to have a wiki

Yes.

Typically, this is what SCM (Source Control Management) is all about. A
wiki is usually not the first tool of choice for providing SCM, though
(I've used a bunch of them over the years for both hardware and software
design files). The wiki could be used to *document* the contents of the SCM
repository, but then there is the problem of keeping the repository and the
wiki in sync, and if they are out of sync, the purpose of the wiki is
obviated (the repository is what it is, good, bad or indifferent; if the
contents are "broken", then the product is probably broken, but the code in
the repository can be "fixed"). So, my thoughts on using a wiki to provide
documentation for what is where and what is what for the nanoVNA stuff are
mixed. Is something that is out of sync better than nothing? How would one
know that they are out of sync? What would be the consequences of relying
on information that is out of sync? Do we care? I'd have to cogitate on
that a bit.

DaveD


On 7/27/2019 7:50 PM, Dave Daniel via Groups.Io wrote:
David,

Why does the nanoVNA group need one more than most other groups?

I have administered Wikis in the past. The one that I like the most is
MediaWiki. MediaWiki is the one used for the TekWiki (w140.com) wiki.

Maintaining a wiki, particularly one edited by a group of people, can
be challenging.

DaveD


On 7/27/2019 1:26 PM, Dr. David Kirkby from Kirkby Microwave Ltd
wrote:
groups.io supports the creation of wikis. I think it would be useful
to
have one, with different pages allocated to different topics - a user
manual, instructions to build from source, bugs, etc.

I don't have much experience of wikis. I have thought of setting one
up for
the HP/Agilent/Keysight group I am owner of, but have not done so. I
think
the NanoVNA needs one more than most others.












Re: LabView Interface

Joe Smith
 

I now have both channels sorted out.? Took a little time away from the project? to have a fresh look.?? I've posted a couple of updated pictures.?? There still some work to do but the basics are working now.?

"www.eevblog.com/forum/rf-microwave/nanovna-custom-software/new/#new"

NanoVNA Custom Software - Page 1

|
|
| |
NanoVNA Custom Software - Page 1

NanoVNA Custom Software - Page 1
|

|

|

On Friday, July 26, 2019, 12:08:06 PM CDT, Joe Smith via Groups.Io <joeqsmith49@...> wrote:

I started to look at the "data 1" array to implement S21.?? So far, no luck.? Like the "data 0" array, it appears to send two different arrays that are interlaced.? ? One thing I did run into when I first tried it, the communications was not reliable. ? It seems that sending the two commands "data 0 data 1" too quickly can cause the VNA some distress.? Adding some delay between commands appears to have solved it. ??
? On Wednesday, July 24, 2019, 4:15:55 PM EDT, Joe Smith via Groups.Io <joeqsmith49@...> wrote:

? Thanks for taking the time to dig up all those links.??? The first link uses the included Smith chart.? This is what I show in my screen shot.?? This works but I really want some basic features like cursors.??? The others appear to use the same method I have done in the past, basically overlaying graphics on an X-Y.?? This is the direction I am planning once again as looking at NI's site, it appears they have nothing new to offer.??
? On Wednesday, July 24, 2019, 3:38:11 PM EDT, Larry Rothman <ac293@...> wrote:

Would this help?

An Old Friend in New Clothes:Smith Charts in LabVIEW
? Proceedings of the 2013 ASEE North Central Section Conference
? Copyright ? 2013, American Society for Engineering Education OFNC1
? ?

There are also:
?
?
?
?
?
I hope these help you and others.

Cheers,
Larry


Re: Case for black VNA

 

I just looks at the 2 units I have (A black one from Alan). The SMA spacing is the same, the the biggest difference on the SMA end, is the spacer size. This makes the cases different

On 7/27/2019 4:48 AM, Mike Brown wrote:
Just got my calipers out in case a few measurements would be helpful. My
sma sockets are as best I can measure, 33.3 mm apart. PCB/panels 86.5mm x
54.65mm. Total height, including slight bulge in plastic rear due to
battery attached with sticky pad, 14.2mm.

I just noticed my sma sockets are only soldered one side of the pcb despite
pads on both sides. About to get my soldering iron out!


Mike

On Sat, 27 Jul 2019, 09:11 Mike Brown via Groups.Io, <mbmail=
[email protected]> wrote:

Hi Frank

My semi-bad clone from seller sqcase has USB C. NB it looks different to
the one in the listing:



Dimensions seem slightly different to others. I printed a case designed for
another black clone. I'm using the same printer as the designer but found I
had to increase the size of the case by 0.7pc to get the clone to fit. The
screw holes don't line up with the screws and didn't before scaling
(fortunately they're not needed as the case is a nice tight fit).

The SMAs were slightly too close together and the USB slightly closer to
the switch so I had to do some filing. Probably partly due to the rescaling
but I think the SMAs really are in a slightly different position.

Mike


On Sat, 27 Jul 2019, 02:52 Frank S, <ka2fwc@...> wrote:

I was able to get a Black unit to measure to see if the case is
different. From shat I found, the white one has nylon standoffs (of the
same size) and the black one has brass standoffs (that are a different
size). This black one has a USB "C" connector, and the switch is a thru
hole mount. It is a little higher than the PCB (as compared to the white
that is flush with the PCB).
Can anyone tell me if all the black units have USB "C" and what the
switch looks like?
Thanks trying to make the best fitting cases for these "toys".
Frank





Re: Suggestion to have a wiki

 

Ok, with what do you agree? It¡¯s not clear from your post whether you think we need a wiki or not.

Just to be clear, I don¡¯t have a problrm with having a wiki. But someone will have to create it and administer it. That will probably be time intensive.

DaveD

Sent from a small flat thingy

On Jul 27, 2019, at 20:43, Jeremy Dunman W1BO <jeremy@...> wrote:

TOTALLY agree! Going back through message after message is difficult at
best. Case in point today working on my antenna and went to pull the
VNAsharp down for my lap top and spent probably 30 minutes searching for
the location of the file.

Jeremy Dunman
W1BO

------ Original Message ------
From: "Dave Daniel" <kc0wjn@...>
To: [email protected]
Sent: 7/27/2019 8:21:57 PM
Subject: Re: [nanovna-users] Suggestion to have a wiki

Yes.

Typically, this is what SCM (Source Control Management) is all about. A wiki is usually not the first tool of choice for providing SCM, though (I've used a bunch of them over the years for both hardware and software design files). The wiki could be used to *document* the contents of the SCM repository, but then there is the problem of keeping the repository and the wiki in sync, and if they are out of sync, the purpose of the wiki is obviated (the repository is what it is, good, bad or indifferent; if the contents are "broken", then the product is probably broken, but the code in the repository can be "fixed"). So, my thoughts on using a wiki to provide documentation for what is where and what is what for the nanoVNA stuff are mixed. Is something that is out of sync better than nothing? How would one know that they are out of sync? What would be the consequences of relying on information that is out of sync? Do we care? I'd have to cogitate on that a bit.

DaveD


On 7/27/2019 7:50 PM, Dave Daniel via Groups.Io wrote:
David,

Why does the nanoVNA group need one more than most other groups?

I have administered Wikis in the past. The one that I like the most is MediaWiki. MediaWiki is the one used for the TekWiki (w140.com) wiki.

Maintaining a wiki, particularly one edited by a group of people, can be challenging.

DaveD


On 7/27/2019 1:26 PM, Dr. David Kirkby from Kirkby Microwave Ltd wrote:
groups.io supports the creation of wikis. I think it would be useful to
have one, with different pages allocated to different topics - a user
manual, instructions to build from source, bugs, etc.

I don't have much experience of wikis. I have thought of setting one up for
the HP/Agilent/Keysight group I am owner of, but have not done so. I think
the NanoVNA needs one more than most others.










Re: Suggestion to have a wiki

 

TOTALLY agree! Going back through message after message is difficult at
best. Case in point today working on my antenna and went to pull the
VNAsharp down for my lap top and spent probably 30 minutes searching for
the location of the file.

Jeremy Dunman
W1BO

------ Original Message ------
From: "Dave Daniel" <kc0wjn@...>
To: [email protected]
Sent: 7/27/2019 8:21:57 PM
Subject: Re: [nanovna-users] Suggestion to have a wiki

Yes.

Typically, this is what SCM (Source Control Management) is all about. A wiki is usually not the first tool of choice for providing SCM, though (I've used a bunch of them over the years for both hardware and software design files). The wiki could be used to *document* the contents of the SCM repository, but then there is the problem of keeping the repository and the wiki in sync, and if they are out of sync, the purpose of the wiki is obviated (the repository is what it is, good, bad or indifferent; if the contents are "broken", then the product is probably broken, but the code in the repository can be "fixed"). So, my thoughts on using a wiki to provide documentation for what is where and what is what for the nanoVNA stuff are mixed. Is something that is out of sync better than nothing? How would one know that they are out of sync? What would be the consequences of relying on information that is out of sync? Do we care? I'd have to cogitate on that a bit.

DaveD


On 7/27/2019 7:50 PM, Dave Daniel via Groups.Io wrote:
David,

Why does the nanoVNA group need one more than most other groups?

I have administered Wikis in the past. The one that I like the most is MediaWiki. MediaWiki is the one used for the TekWiki (w140.com) wiki.

Maintaining a wiki, particularly one edited by a group of people, can be challenging.

DaveD


On 7/27/2019 1:26 PM, Dr. David Kirkby from Kirkby Microwave Ltd wrote:
groups.io supports the creation of wikis. I think it would be useful to
have one, with different pages allocated to different topics - a user
manual, instructions to build from source, bugs, etc.

I don't have much experience of wikis. I have thought of setting one up for
the HP/Agilent/Keysight group I am owner of, but have not done so. I think
the NanoVNA needs one more than most others.







Re: Suggestion to have a wiki

 

Yes.

Typically, this is what SCM (Source Control Management) is all about. A wiki is usually not the first tool of choice for providing SCM, though (I've used a bunch of them over the years for both hardware and software design files). The wiki could be used to *document* the contents of the SCM repository, but then there is the problem of keeping the repository and the wiki in sync, and if they are out of sync, the purpose of the wiki is obviated (the repository is what it is, good, bad or indifferent; if the contents are "broken", then the product is probably broken, but the code in the repository can be "fixed"). So, my thoughts on using a wiki to provide documentation for what is where and what is what for the nanoVNA stuff are mixed. Is something that is out of sync better than nothing? How would one know that they are out of sync? What would be the consequences of relying on information that is out of sync? Do we care? I'd have to cogitate on that a bit.

DaveD

On 7/27/2019 7:50 PM, Dave Daniel via Groups.Io wrote:
David,

Why does the nanoVNA group need one more than most other groups?

I have administered Wikis in the past. The one that I like the most is MediaWiki. MediaWiki is the one used for the TekWiki (w140.com) wiki.

Maintaining a wiki, particularly one edited by a group of people, can be challenging.

DaveD


On 7/27/2019 1:26 PM, Dr. David Kirkby from Kirkby Microwave Ltd wrote:
groups.io supports the creation of wikis. I think it would be useful to
have one, with different pages allocated to different topics - a user
manual,? instructions to build from source, bugs, etc.

I don't have much experience of wikis. I have thought of setting one up for
the HP/Agilent/Keysight group I am owner of, but have not done so. I think
the NanoVNA needs one more than most others.



"Clones"

 

Has anyone determined if there is more than 2 PCBA for these units? I see there is a USB Micro B (which I have) and the USB C,?? on the black (which I have seen advertised on some white units also). I Know the SMA spacing between the 2 units I have played with , and the power switch is also different


Re: Suggestion to have a wiki

 

I think the biggest thing is since there seems to be a bunch of "different" variations, there would be one source to determine which one you have (bad, semi bad etc)
It would also help with the different FW and the function they provide
Frank

On 7/27/2019 7:50 PM, Dave Daniel wrote:
David,

Why does the nanoVNA group need one more than most other groups?

I have administered Wikis in the past. The one that I like the most is MediaWiki. MediaWiki is the one used for the TekWiki (w140.com) wiki.

Maintaining a wiki, particularly one edited by a group of people, can be challenging.

DaveD


On 7/27/2019 1:26 PM, Dr. David Kirkby from Kirkby Microwave Ltd wrote:
groups.io supports the creation of wikis. I think it would be useful to
have one, with different pages allocated to different topics - a user
manual,?? instructions to build from source, bugs, etc.

I don't have much experience of wikis. I have thought of setting one up for
the HP/Agilent/Keysight group I am owner of, but have not done so. I think
the NanoVNA needs one more than most others.




Re: Suggestion to have a wiki

 

David,

Why does the nanoVNA group need one more than most other groups?

I have administered Wikis in the past. The one that I like the most is MediaWiki. MediaWiki is the one used for the TekWiki (w140.com) wiki.

Maintaining a wiki, particularly one edited by a group of people, can be challenging.

DaveD

On 7/27/2019 1:26 PM, Dr. David Kirkby from Kirkby Microwave Ltd wrote:
groups.io supports the creation of wikis. I think it would be useful to
have one, with different pages allocated to different topics - a user
manual, instructions to build from source, bugs, etc.

I don't have much experience of wikis. I have thought of setting one up for
the HP/Agilent/Keysight group I am owner of, but have not done so. I think
the NanoVNA needs one more than most others.


Re: nano cases

 

I use connector savers and do not screw DUTs onto the SMA's which are mounted on the PCB. After awhile the connector savers go tainted and I replace them. The SMA on the units stay pretty clean.

Now I do not use a torque wrench to tighten elements. I agree, if that were the case, I suspect those SMA connectors are eventually going to become intermittent or get ripped off the PCB.

If you really want a more robust arrangement, then I agree go the type N route via a short interconnect cable and place into a robust box.

Alan

________________________________
From: [email protected] <[email protected]> on behalf of Dr. David Kirkby from Kirkby Microwave Ltd <drkirkby@...>
Sent: Saturday, July 27, 2019 10:08 PM
To: [email protected] <[email protected]>
Subject: Re: [nanovna-users] nano cases

On Sat, 27 Jul 2019 at 22:07, Frank S <ka2fwc@...> wrote:

Here are pictures of the black and the white cases. The original front
and back plate are re mounted with longer screws.
When I feel confident these will fit both units,(with input from the
group), I will setup something to sell them (may eBay) . Estimated price
$12.50 plus shipping including longer screws.
??I am still looking into inexpensive international options.
Frank
I can¡¯t help but feel that the case should ensure that the DUT is not
connected to the SMA connectors.


--
Dr. David Kirkby,


Re: nano cases

Dr. David Kirkby from Kirkby Microwave Ltd
 

On Sat, 27 Jul 2019 at 22:07, Frank S <ka2fwc@...> wrote:

Here are pictures of the black and the white cases. The original front
and back plate are re mounted with longer screws.
When I feel confident these will fit both units,(with input from the
group), I will setup something to sell them (may eBay) . Estimated price
$12.50 plus shipping including longer screws.
??I am still looking into inexpensive international options.
Frank
I can¡¯t help but feel that the case should ensure that the DUT is not
connected to the SMA connectors.


--
Dr. David Kirkby,


Re: Frequency correction

Dr. David Kirkby from Kirkby Microwave Ltd
 

On Sat, 27 Jul 2019 at 22:14, alan victor <avictor73@...> wrote:

According to the schematic it is 26 MHz. And the diagram shows NO freq
adjust pin. The TC on these is decent at 2.5 ppm or less. However MAKE
tolerance is a different animal. At 900 MHz we are looking at a little
over 2 kHz. Not bad...

If anyone does want to go mad, an OCXO is going to be the best that¡¯s
practical. I suspect that there are some cheap ones, but the first I found
was from Farnel, but its nearly 4x the cost of the NanoVNA




But the fact 26 MHz is available as a standard part, might mean there are
others. But OCXOs use a fair bit of power.

As I wrote earlier though. I don¡¯t see frequency accuracy as a big deal on
a VNA, but someone mentioned using it as a signal generator, where one is
likely to be more concerned about frequency accuracy.

I have my VNAs locked to GPS, simply because I have a distribution unit
with enough outputs to do so. It is hardly necessary.

Dave


--
Dr. David Kirkby,


Re: nanoVNA Menu Structure Drawing

 

I thought I saw your email direct earlier... Any way, contact me at avictor followed by the number 73 at hotmail dot com. I am good on QRZ with an email address at the bottom of the bio...

Alan W4AMV


Re: nanoVNA Menu Structure Drawing

 

Sure Larry,

Let me send you an email direct. I can contact you by phone as well.

Alan