Hi Karsten,
I answer partially instead Rune's.
The limitation of 100Hz comes from the firmware, and maybe even hardware.
Another solution to determine the motionals parameters of a crystal is to use SNASharp with a compatible scalar analyzer.
Look here:
SNASharp official page (in french sorry):
David, F4HTQ.
toggle quoted message
Show quoted text
-----Message d'origine----- De : [email protected] [mailto: [email protected]] De la part de Karsten, DD1KT Envoy¨¦ : jeudi 14 novembre 2019 14:24 ? : [email protected]Objet : Re: [nanovna-users] NanoVNA-Saver 0.2.0 Hello Rune, I am quite new to the group and am already scanning all the messages for information. So please excuse, if I missed the information I am now askig for: Which functions are taken over from your Software NanoVNA-Saver and which functions are still based on the Firmware. e.g. I understand, you have your own calibration values for the correction of the traces, you do not use the values stored in the Firmware my concrete questions: - if I need small steps to measure a crystal filter (I read that the original old (September) Firmware has 100 Hz steps), can I do it with your software, or is the frequency generation taken from the firmware? - to take a screen-shot, would I need an other Firmware and other PC-Programm, or is it also possible with your Software? - Is there the need or proposal to use a specific Firmware to get all possibilities of your Software? vy73 de Karsten, DD1KT
|
Hello Rune,
I am quite new to the group and am already scanning all the messages for information.
So please excuse, if I missed the information I am now askig for:
Which functions are taken over from your Software NanoVNA-Saver and which functions are still based on the Firmware.
e.g. I understand, you have your own calibration values for the correction of the traces, you do not use the values stored in the Firmware
my concrete questions:
- if I need small steps to measure a crystal filter (I read that the original old (September) Firmware has 100 Hz steps), can I do it with your software, or is the frequency generation taken from the firmware?
- to take a screen-shot, would I need an other Firmware and other PC-Programm, or is it also possible with your Software?
- Is there the need or proposal to use a specific Firmware to get all possibilities of your Software?
vy73 de Karsten, DD1KT
|
Re: Is the NooElec nanoVNA any good?
Thanks to jwd270 and Joe St. Clair AF5MH, I placed my order an hour ago, I've downloaded the lastest firmware and will look into adding the battery voltage diode.
I expect to use mine with a netbook most of the time.
|
Hi Rune,
Thanks a lot for this fantastic software. The newly added TDR markers are very useful when dealing with roof antennas. :-)
Great job.
Thanks again
Jean
|
@Rune Broberg
forgive me Rune, maybe it has already been said a million times but I still have doubts.
Let's say I have the nanoVNA turned on "Recall 4".
I connect NanoVNA-Saver to the device and the program synchronizes to the same frequency range as the device.
What else does NanoVNA-Saver read from the NanoVNA? calibration values? other?
thanks and congratulations for the excellent program.
73, Lucio I0LYL
|
Re: NanoVNA software developers wanted
#hacking
I'm using eclipse to edit and the github gui to sync with github. Apart from remembering to save the files you edited because otherwise the make file will not do anything this works well. For eclipse and build environment I followed the edy555 guide (see the nanoVNA wiki) -- NanoVNA Wiki: /g/nanovna-users/wiki/homeNanoVNA Files: /g/nanovna-users/files?Erik, PD0EK
|
Re: Correction menu option ?
Thanks. Interesting to see.
|
Rune,
While verifying a cable that I just constructed, I noticed that you had implemented a second marker in the TDR graph. Thanks a lot! Its nice to be able to mark other anomalies, in addition to the peak, and get a readout of where they occur. The attachment shows the TDR graph with a second marker showing the minor discontinuity caused by the BNC "bullet" at 0.3 meters.
The phase delay graph is telling me something, just not sure how to interpret it ; )
- Herb
|
Re: Added to NanoVNA Wiki Re: DFUseDemo
Yes, you can edit the link I made to your forum post.? ?
The trick is that you have to edit the whole wiki page - so please be careful.?
Unfortunately, the forum owner disabled the ability to edit posts although you can delete and repost if you need to make a correction. The only drawback is every post gets sent out to those who subscribed to individual postings.? ?
What Oristo and I have done in some areas is to create a pdf document, place it in the files area and then create a link to in in the wiki.? ?
As for filenames, I'm starting to use dashes or underscores instead of spaces to stop the group.io subsystem from substituting %20 for them and making a mess of the filename.? ?
... Larry
On Wed, 13 Nov 2019 at 6:47 PM, Herman De Dauw<on1bes@...> wrote: Thank you Larry.
Zadig is usually required to install a driver for an RTL-SDR DVB-T2 TV dongle. I use it often.
If you use it incorrectly, you can expect problems with Windows hardware.
But the given tip was made very quickly. It can still be fine-tuned. Can I still edit it if necessary?
on1bes Herman
|
Re: Is the NooElec nanoVNA any good?
I agree. I bought one too and my experience was the same.
|
Re: Nanovna-Saver 0.2.0 MAC
Dana, a couple of things.
¡°Older version¡± begs the question - which one? My version of Catalina seems to continue along with Python 3.6. I tried to install 3.7 as recommended as per the instructions in the nanosave groups.io <> group. That turned into a disaster as I kept getting "access denied¡± errors.
So installed 3.8 from the Python site. Have you tried nanovna save wiht this version of Python?
Thanks,
-rick. K7LOG
toggle quoted message
Show quoted text
On Nov 12, 2019, at 18:40, Dana Shtun <ve3dss@...> wrote:
The latest version seems to be working just fine on my mac.
Just remember with Catalina, the latest Python isn¡¯t working completely
so use an older version.
Dana VE3DS
Toronto Canada
where its going - 15C tonight
|
Re: Added to NanoVNA Wiki Re: DFUseDemo
Thank you Larry.
Zadig is usually required to install a driver for an RTL-SDR DVB-T2 TV dongle. I use it often.
If you use it incorrectly, you can expect problems with Windows hardware.
But the given tip was made very quickly. It can still be fine-tuned. Can I still edit it if necessary?
on1bes Herman
|
Rune,
I understand that NanoVNA-Saver calibrations aer saved to my computer.
Thanks,
Mike N2MS
toggle quoted message
Show quoted text
On November 13, 2019 at 2:06 PM Rune Broberg <mihtjel@...> wrote:
Hi Mike,
you can - but the NanoVNA-Saver calibrations are not saved on the device,
but as files on your computer.
So I think you understand it right? :-)
--
Rune / 5Q5R
On Wed, 13 Nov 2019 at 19:31, MICHAEL ST ANGELO <mstangelo@...>
wrote:
Rune,
I forgot some information about the NanoVNA Saver Cal:
If I calibrate my NanaVNA full span and save it to Cal 0 can I calibrate
via NanoVNA Saver the same full span using 10 "Segments" to Cal 0?
For HF work - Can I calibrate my NanaVNA 1-30Mnz and save it to Cal 1 and
then I calibrate via NanoVNA Saver the same 1-30Mhz span using 10
"Segments" to Cal 1?
Mike N2MS
On November 13, 2019 at 10:39 AM n2msqrp <msangelo@...> wrote:
Rune,
Let me see if I understand this.
If I calibrate my NanaVNA full span and save it to Cal 0 can I calibrate via NanoVNA Saver the same full span using 10 "Segments"?
For HF work can I If I calibrate my NanaVNA 1-30Mnz and save it to Cal 1
and then I calibrate via NanoVNA Saver the same 1-30Mhz span using 10
"Segments"?
Mike N2MS
On November 13, 2019 at 2:12 AM Rune Broberg <mihtjel@...>
wrote:
Hi Barry,
I don't know that you would need to do the whole copy around thing. I
haven't tried it, but I think it would work fine selecting a
calibration
slot, slot 1 for example, and then using NanoVNA-Saver with the device
with
that calibration active in the calibrated range.
*However*: My personal preference is to have Cal 0 be full span, and
then
making a calibration within NanoVNA-Saver, using the calibration
assistant,
with the "Segments" count set to perhaps 10 or even 20 - which gives
you
1010 or 2020 data points for the calibration. This calibration can be
full
span, or for the range you are interested in. You can then save this,
or
any other calibration you make, as files which you can name more
intuitively than "cal 0", "cal 1" etc. ;-)
|
Hi Mike, you can - but the NanoVNA-Saver calibrations are not saved on the device, but as files on your computer. So I think you understand it right? :-) -- Rune / 5Q5R On Wed, 13 Nov 2019 at 19:31, MICHAEL ST ANGELO <mstangelo@...> wrote: Rune,
I forgot some information about the NanoVNA Saver Cal:
If I calibrate my NanaVNA full span and save it to Cal 0 can I calibrate
via NanoVNA Saver the same full span using 10 "Segments" to Cal 0?
For HF work - Can I calibrate my NanaVNA 1-30Mnz and save it to Cal 1 and
then I calibrate via NanoVNA Saver the same 1-30Mhz span using 10
"Segments" to Cal 1?
Mike N2MS
On November 13, 2019 at 10:39 AM n2msqrp <msangelo@...> wrote:
Rune,
Let me see if I understand this.
If I calibrate my NanaVNA full span and save it to Cal 0 can I calibrate via NanoVNA Saver the same full span using 10 "Segments"?
For HF work can I If I calibrate my NanaVNA 1-30Mnz and save it to Cal 1
and then I calibrate via NanoVNA Saver the same 1-30Mhz span using 10
"Segments"?
Mike N2MS
On November 13, 2019 at 2:12 AM Rune Broberg <mihtjel@...>
wrote:
Hi Barry,
I don't know that you would need to do the whole copy around thing. I
haven't tried it, but I think it would work fine selecting a
calibration
slot, slot 1 for example, and then using NanoVNA-Saver with the device
with
that calibration active in the calibrated range.
*However*: My personal preference is to have Cal 0 be full span, and
then
making a calibration within NanoVNA-Saver, using the calibration
assistant,
with the "Segments" count set to perhaps 10 or even 20 - which gives
you
1010 or 2020 data points for the calibration. This calibration can be
full
span, or for the range you are interested in. You can then save this,
or
any other calibration you make, as files which you can name more
intuitively than "cal 0", "cal 1" etc. ;-)
|
On Wed, Nov 13, 2019 at 09:52 AM, Gabriel Tenma White wrote:
I would really like to see si5351 reach 3GHz ;) We also have a full two port (4 S params at once) design in the pipeline too.
______________________________________________________________ Gabriel, In my opinion, 3GHz would be great but if you were able to offer reasonable performance to 2.4 GHz to cover the WIFI band, that would satisfy a lot of potential buyers. By reasonable performance, I would think the current performance specifications for the NanoVNA in the 600 - 900 MHz band would be the target. Best of luck, - Herb
|
Rune,
I forgot some information about the NanoVNA Saver Cal:
If I calibrate my NanaVNA full span and save it to Cal 0 can I calibrate via NanoVNA Saver the same full span using 10 "Segments" to Cal 0?
For HF work - Can I calibrate my NanaVNA 1-30Mnz and save it to Cal 1 and then I calibrate via NanoVNA Saver the same 1-30Mhz span using 10 "Segments" to Cal 1?
Mike N2MS
toggle quoted message
Show quoted text
On November 13, 2019 at 10:39 AM n2msqrp <msangelo@...> wrote:
Rune,
Let me see if I understand this.
If I calibrate my NanaVNA full span and save it to Cal 0 can I calibrate via NanoVNA Saver the same full span using 10 "Segments"?
For HF work can I If I calibrate my NanaVNA 1-30Mnz and save it to Cal 1 and then I calibrate via NanoVNA Saver the same 1-30Mhz span using 10 "Segments"?
Mike N2MS
On November 13, 2019 at 2:12 AM Rune Broberg <mihtjel@...> wrote:
Hi Barry,
I don't know that you would need to do the whole copy around thing. I
haven't tried it, but I think it would work fine selecting a calibration
slot, slot 1 for example, and then using NanoVNA-Saver with the device with
that calibration active in the calibrated range.
*However*: My personal preference is to have Cal 0 be full span, and then
making a calibration within NanoVNA-Saver, using the calibration assistant,
with the "Segments" count set to perhaps 10 or even 20 - which gives you
1010 or 2020 data points for the calibration. This calibration can be full
span, or for the range you are interested in. You can then save this, or
any other calibration you make, as files which you can name more
intuitively than "cal 0", "cal 1" etc. ;-)
|
I would really like to see si5351 reach 3GHz ;) We also have a full two port (4 S params at once) design in the pipeline too.
|
On Wed, Nov 13, 2019 at 07:51 AM, Gabriel Tenma White wrote: "On the V2 design we worked around 3.3V rail supply noise " --------------------------------------------------------------------------------------------------------------- Gabriel, I hope you are able to get your V2 design to market before continued performance improvements to the NanoVNA again leapfrog your anticipated product. - Herb
|
On Wed, Nov 13, 2019 at 07:16 AM, Larry Rothman wrote: "There is an interesting discussion on hugen79's NanoVNA Issues page on Github regarding circuit changes/mods to reduce overall noise levels." ------------------------------------------------------------------------------- Larry, Thanks for posting the link to the discussion. It looks like the current 600 - 900 MHz NanoVNA performance specifications are close to being extended to the 900 MHz to 1.5 GHz range. Probably more realistically to at least 1.3 GHz. - Herb
|
On the V2 design we worked around 3.3V rail supply noise by using a very wide PLL loop bandwidth (~200kHz), since the noise at the 12kHz IF frequency is impossible to filter out and using an LDO was not an option (the adf4350 draws quite a bit of current). The wide loop filter forces phase coherency between the two PLLs even with a noisy VCO.
5V rail noise is suppressed by using a mixer with differential output and using a differential amplifier for the baseband signal. Even with a single ended output mixer it's possible to suppress power supply influence by experimentally determining the the coefficient of supply voltage on the output DC voltage, and using a difference amplifier with the right gain, since the IF frequency is so low it's basically DC.
|
OwO