¿ªÔÆÌåÓý

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

Re: Possible location of latest VNA source code??

 

You may have pressed the touch screen while adc is initializing.
It might be better to add a wait.

void adc_init(void)
{
rccEnableADC1(FALSE);

/* Calibration procedure.*/
ADC->CCR = 0;
while (ADC1->CR & ADC_CR_ADEN)
;
ADC1->CR |= ADC_CR_ADCAL;
while (ADC1->CR & ADC_CR_ADCAL)
;

ADC1->CR = ADC_CR_ADEN;
while (!(ADC1->ISR & ADC_ISR_ADRDY))
;
}





On Sat, Jul 27, 2019 at 04:45 AM, Lapo Pieri wrote:


Hi Hugen,
01:12 Fri 26 Jul 19 , hugen@... wrote:
I've reshared the code.
I've recompiled and tested it but it hangs on startup. I've found the
problem in internal adc calibration; commenting out that part of code, i.e.:

void adc_init(void)
{
rccEnableADC1(FALSE);

/* Calibration procedure.*/
/* ADC->CCR = 0; */
/* ADC1->CR |= ADC_CR_ADCAL; */
/* while (ADC1->CR & ADC_CR_ADCAL) */
/* ; */

ADC1->CR = ADC_CR_ADEN;
while (!(ADC1->ISR & ADC_ISR_ADRDY))
;
}

It do the job and nanovna works, fine to me at a first test.

Internal adc is used for touch screen readings, right? So if it isn't
calibrated it should have problems in touch-screen to display allignment,
right? But it doesn't happen to me or it's very small.

So, could you explain me why this adc calibration problem?

I've also notice that after fw update one has to power off the nanovna and
wait until blue led is off and than power on again and issue a new
calibration, otherwise it's impossible to calibrate correctly
(i.e. after a complete calibration measuring tha same open used for
calibration gives ~-8.5dB of return loss...).

Many thanks, I'm going to work on the code!

Lapo, IK5NAX
On Sat, Jul 27, 2019 at 04:45 AM, Lapo Pieri wrote:


It do the job and nanovna works, fine to me at a first test.

Internal adc is used for touch screen readings, right? So if it isn't
calibrated it should have problems in touch-screen to display allignment,
right? But it doesn't happen to me or it's very small.

So, could you explain me why this adc calibration problem?

I've also notice that after fw update one has to power off the nanovna and
wait until blue led is off and than power on again and issue a new
calibration, otherwise it's impossible to calibrate correctly
(i.e. after a complete calibration measuring tha same open used for
calibration gives ~-8.5dB of return loss...).


Re: nano cases

Dr. David Kirkby from Kirkby Microwave Ltd
 

On Mon, 29 Jul 2019 at 06:17, kh6sky <kh6sky@...> wrote:

These cases look nice and fulfill a need but my tendency to spastically
knock stuff off the bench means I will use a larger metal box with switches
and connectors moved to the outer box. The power and control switches seem
too delicate to last. Another reason to put the unit in a box is the
delicate USB connector.

I agree entirely. I think any case should extend out *everything* so you
never put any strain on the device apart from the screen, which I can see
no way of avoiding.

So I think these should be on a case

1) RF connectors - I would use N, not SMA,
2) USB
3) Toggle switch
4) Power switch

For the LED, one could have 3 possibilities
* Small hole
* light pipe
* desolder LED and run wire.

For the battery, I guess one can get away with using the tracks on the


If the plastic case were re-enforced around the USB connector it might help
prevent disasters like mine.

I personally don¡¯t think any amount of reinforcement is going to work as a
long term solution. That will only delay the inevitable a while.

Dave.

Dave.
--
Dr. David Kirkby,


Re: nano cases

 

These cases look nice and fulfill a need but my tendency to spastically knock stuff off the bench means I will use a larger metal box with switches and connectors moved to the outer box. The power and control switches seem too delicate to last. Another reason to put the unit in a box is the delicate USB connector. If the plastic case were re-enforced around the USB connector it might help prevent disasters like mine. On my white Gecko first NanoVNA purchase, the USB connector came loose from the circuit board on the first day. This weakness was also pointed out in the documentation when the NanoVNA was sold as a kit. This was really not easy to fix as some of the traces were pulled from the board, though I did manage with some microscope aided soldering. When my black version arrives, I want to get it into a larger box as soon as I verify it works. You can purchase a small USB extender cable that mounts easily to the outer box. I bought one for my uBitX project.

Perhaps the printed case might be improved by addition of a tongue or bracket that the USB cable could be affixed to. Any sort of strain relief on that connection should be welcomed. Most of you may get by without destroying your USB connection, but for those like me suffer from the dropsies, I suggest you do something to protect that connector.

Jim


Locked Re: Correct button?

 

You are correct and I confirmed on the big box, that is the function performed.

This turns CAL ON or OFF. Again, I suspect hp as well others, added this function as an aid to be sure the correction data sets make sense as a corrective measurement is conducted on a component. Its much easier to do this then preset the instrument and have to do a complete re calibration.

Alan

________________________________
From: [email protected] <[email protected]> on behalf of alan victor <avictor73@...>
Sent: Monday, July 29, 2019 1:20 AM
To: [email protected] <[email protected]>
Subject: Re: [nanovna-users] Correct button?

Good suggestion and it does appear to toggle in that manner.

Now, I have to think why I would toggle corrections ON and OFF, other than to see if the corrections ON make sense.

I am not sure this is a good place to bring up the fact that the STANDARDS provided with the nanoVNA are taken, I believe, by the device and the firmware as IDEAL. Point in fact, they are NOT. Not an issue at lower frequencies unless you want to split hairs. But as you approach 900 MHz, bottom line, when measuring a component, you are not going to get the correct answer.

I emailed the developer on this topic but as of now, no response.

Alan

________________________________
From: [email protected] <[email protected]> on behalf of Roger Henderson <hendorog@...>
Sent: Monday, July 29, 2019 1:10 AM
To: [email protected] <[email protected]>
Subject: Re: [nanovna-users] Correct button?

I would guess it is a mode switch between: 'Apply calibration corrections'
and 'Don't apply calibration corrections'

This feature is present in other VNA's. Am not in front of a device to
confirm it though.

Regards,
Roger

On Mon, 29 Jul 2019 at 13:06, alan victor <avictor73@...> wrote:

Good question Ernst. Let me take a look and see if I can figure it out. I
have a guess that it may have to do with the fact that the standards, open,
short, load are NOT perfect. But... the softkey selection does not lead to
additional menu selection. So far now, it appears to be a PLACE HOLDER for
further work.

Alan

________________________________
From: [email protected] <[email protected]> on behalf of
dk1vi <dk1vi@...>
Sent: Sunday, July 28, 2019 11:44 PM
To: [email protected] <[email protected]>
Subject: [nanovna-users] Correct button?

Hi,
what is the purpose of the "CORRECT" button in the calibration menu?
I have not read anything about it or did I miss something?
Ernst







Locked Re: Correct button?

 

Good suggestion and it does appear to toggle in that manner.

Now, I have to think why I would toggle corrections ON and OFF, other than to see if the corrections ON make sense.

I am not sure this is a good place to bring up the fact that the STANDARDS provided with the nanoVNA are taken, I believe, by the device and the firmware as IDEAL. Point in fact, they are NOT. Not an issue at lower frequencies unless you want to split hairs. But as you approach 900 MHz, bottom line, when measuring a component, you are not going to get the correct answer.

I emailed the developer on this topic but as of now, no response.

Alan

________________________________
From: [email protected] <[email protected]> on behalf of Roger Henderson <hendorog@...>
Sent: Monday, July 29, 2019 1:10 AM
To: [email protected] <[email protected]>
Subject: Re: [nanovna-users] Correct button?

I would guess it is a mode switch between: 'Apply calibration corrections'
and 'Don't apply calibration corrections'

This feature is present in other VNA's. Am not in front of a device to
confirm it though.

Regards,
Roger

On Mon, 29 Jul 2019 at 13:06, alan victor <avictor73@...> wrote:

Good question Ernst. Let me take a look and see if I can figure it out. I
have a guess that it may have to do with the fact that the standards, open,
short, load are NOT perfect. But... the softkey selection does not lead to
additional menu selection. So far now, it appears to be a PLACE HOLDER for
further work.

Alan

________________________________
From: [email protected] <[email protected]> on behalf of
dk1vi <dk1vi@...>
Sent: Sunday, July 28, 2019 11:44 PM
To: [email protected] <[email protected]>
Subject: [nanovna-users] Correct button?

Hi,
what is the purpose of the "CORRECT" button in the calibration menu?
I have not read anything about it or did I miss something?
Ernst







Locked Re: Correct button?

 

I would guess it is a mode switch between: 'Apply calibration corrections'
and 'Don't apply calibration corrections'

This feature is present in other VNA's. Am not in front of a device to
confirm it though.

Regards,
Roger

On Mon, 29 Jul 2019 at 13:06, alan victor <avictor73@...> wrote:

Good question Ernst. Let me take a look and see if I can figure it out. I
have a guess that it may have to do with the fact that the standards, open,
short, load are NOT perfect. But... the softkey selection does not lead to
additional menu selection. So far now, it appears to be a PLACE HOLDER for
further work.

Alan

________________________________
From: [email protected] <[email protected]> on behalf of
dk1vi <dk1vi@...>
Sent: Sunday, July 28, 2019 11:44 PM
To: [email protected] <[email protected]>
Subject: [nanovna-users] Correct button?

Hi,
what is the purpose of the "CORRECT" button in the calibration menu?
I have not read anything about it or did I miss something?
Ernst







Locked Re: Correct button?

 

Good question Ernst. Let me take a look and see if I can figure it out. I have a guess that it may have to do with the fact that the standards, open, short, load are NOT perfect. But... the softkey selection does not lead to additional menu selection. So far now, it appears to be a PLACE HOLDER for further work.

Alan

________________________________
From: [email protected] <[email protected]> on behalf of dk1vi <dk1vi@...>
Sent: Sunday, July 28, 2019 11:44 PM
To: [email protected] <[email protected]>
Subject: [nanovna-users] Correct button?

Hi,
what is the purpose of the "CORRECT" button in the calibration menu?
I have not read anything about it or did I miss something?
Ernst


Re: LabView Interface

Joe Smith
 

I uploaded a short video clip showing the current status of my LabView interface.? It's not ready for prime time yet.?

Link is on the EEVBLOG site, same as before.

On Saturday, July 27, 2019, 8:34:11 PM CDT, Joe Smith via Groups.Io <joeqsmith49@...> wrote:

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


Locked Correct button?

 

Hi,
what is the purpose of the "CORRECT" button in the calibration menu?
I have not read anything about it or did I miss something?
Ernst


Re: Possible location of latest VNA source code??

DMR
 

Hi to all! I ask for help, is it possible to compile the source code in the Windows 10 OS?


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.