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.
|
Re: Is the NooElec nanoVNA any good?
Yep. I bought one. It came with an older firmware and no battery voltage diode. The battery doesn't have a connector, so adding the diode is easier. It arrived well packed, and has worked great. You'll definitely want to upgrade the firmware when you get it. There have been some nice adds in recent versions.
|
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
toggle quoted message
Show quoted text
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. ;-)
|
Folks,
There is an interesting discussion on hugen79's NanoVNA Issues page on Github regarding circuit changes/mods to reduce overall noise levels.
I'm posting the link here for those who may be interested in the discussion and maybe experimenting with this further.
At this time (Nov 13), there are 14 entries in the discussion regarding the addition of filter caps on the clock generator and change to the battery charging circuit.
73...Larry
|
Added to NanoVNA Wiki Re: DFUseDemo
Added Herman's DFU USB driver advice to the Wiki in the Firmware section.
|
Is the NooElec nanoVNA any good?
Is the NooElec nanoVNA any good?
They have a nice bundle on sale and I'm so tempted.
|
Hello Herman,
Thank you so much Herman, I ow you a lot, you solved my problem !!!!!
I just had to delete the drivers in Windows Device manager under "USB devices/ DFU Bootloader".
After having done this, when I connected the NanoVNA in DFU mode to the USB port,? it did not show up in the device manager under "USB devices" but under? "USB Serial Bus-controllers", that solved it.
You were the only one that reacted on this message sofar, again I ow you a lot !!
Thanks many times.
Jos (pa3cce)
Op 12-11-2019 om 23:41 schreef Herman De Dauw:
toggle quoted message
Show quoted text
I never had to use Zadig in Windows 10 64bit to use DFUseDemo. This is probably a problem by you. Put your Hardware Device Manager window on and examinate following. Try uninstalling Zadig (actually a USB driver) until it no longer appears in Hardware Devive Manager window. This may have to be done multiple times. In the View menu, put the option "show hidden devices", you will see them grayed out in the list, and see if there is an earlier installation of Zadig (Zadig itself is not visible, but 'USB lib device' or something similar - i have not the exact names, but don't delete the 'Universal Serial-Bus Controllers'!) delete or uninstall all gray drivers until they are gone. The Wiki Files contains the manual of DFUseDemo and its installation. Follow it carefully. I test it again here, and you don't need Zadig. If you connect the Nano, with the boot button pressed, a "STM Device in DFU Mode" will first appear in Hardware Device Manager (with a yellow triangle). If you wait 20 seconds, the driver is automatically loaded in Windows, and the "STM Device in DFU Mode" is added to the list "Universal Serial-Bus Controllers". If you turn the Nano off, "STM Device in DFU Mode" will remain in the list, but then turn gray.
on1bes
|
Go right ahead and buy one from this place - but we all know you won't - you just like to complain - as noted in your various posts in this forum.
You get what you give.
toggle quoted message
Show quoted text
On Wednesday, November 13, 2019, 1:00:55 a.m. GMT-5, vaclav_sal via Groups.Io <vaclav_sal@...> wrote:
Stay far away from this 3rd party seller.? There are typos all throughout their company info and their shipping policy looks strange and has many spelling mistakes as well.
Wow,
now we judge products by spelling errors.
Never mind that Wally's business model put many establishment where queens English was practiced out of business,
employs senior citizens? etc.
How shallow can your get?
I am ordering mine from guess who?
|
Hello Norbert,
I've put it on the list for a future release. I don't immediately know how
to do it nicely, but I think it's an important feature, so I'll certainly
try to work on it. :-)
--
Rune / 5Q5R
toggle quoted message
Show quoted text
On Wed, 13 Nov 2019 at 11:03, <norbert.kohns@...> wrote: Hi Rune,
thanks for the great software update!
Would it be possible to show in the log scaled frequency mode the vertical
grid lines logarithmically like 0.1 MHz, 0.2 MHz,...0.9 MHz, 1 MHz,...10
MHz,...100 MHz,...900 MHz? I think, that would give one a much better
overview of the frequency axis.
Best regards
Norbert, DG1KPN
|
Hi Rune,
thanks for the great software update!
Would it be possible to show in the log scaled frequency mode the vertical grid lines logarithmically like 0.1 MHz, 0.2 MHz,...0.9 MHz, 1 MHz,...10 MHz,...100 MHz,...900 MHz? I think, that would give one a much better overview of the frequency axis.
Best regards
Norbert, DG1KPN
|
If you are not in a hurry, you can purchase it next month and I will fix some community feedback issues.
|
Hi John,
my experiments in this field have been very limited - the feature was added
with the encouragement of David F4HTQ. He submitted to me an S2P file of a
measurement of a toroid, and a curve shape:
He believed this could be approximated as R/¦Ø and X/¦Ø, so I implemented it,
and managed to create the following graph:
[image: image.png]
Which seemed to fit quite well, even though the units aren't exactly the
same.
So, for now, all I know how to do is: Given a permeability chart from a
manufacturer, replicate the same curve shape vs frequency using the NanoVNA.
I hope it's useful ;-)
--
Rune / 5Q5R
toggle quoted message
Show quoted text
On Wed, 13 Nov 2019 at 01:22, John AE5X <ae5x@...> wrote: Now that the capability is there in the software, how would one use the
NanoVNA to check a toroid's permeability? New territory for me... :-)
|
Hi Tom,
scaling of the input fields and avoiding "overflow" is on the todo list.
:-) User interface design isn't my strong point, and I probably have a
strong habit of testing the software with my preferred settings - 8pt font,
for example - and never really looking at what other users might set it up
as. Having it run on at least 3 different operating systems doesn't help
that ;-)
But, I am going to look into it, both scaling the interface as the font
size changes, and organising the layout to make the most of a limited
screen size.
I hope you continue to enjoy using the software!
--
Rune / 5Q5R
toggle quoted message
Show quoted text
On Tue, 12 Nov 2019 at 20:35, Tom VA7TA <tma.7ta@...> wrote: Hi Rune,
Many thanks again for your ongoing development of nanoVNA-Saver -
fabulous work!
I am not sure if I should waste your time reporting this as it is
not a significant issue....just apple polishing.
I noticed when I first start version 0.2.0 that the Center, Stop
and Span frequency info within "Sweep Control" section overflows the window
widths. At startup it displays 9 digits as shown below. Once I enter new
sweep control frequencies it displays normally. However Center still
overflows just a little. I have my sweep Stop set at 850M and the Center is
showing 425.025MHz which just exceeds the window width by about a half
digit. With initialization the data is about twice as wide as the window
width with the most significant digits hidden from view then it reverts to
normal upon receiving a new manual frequency entry.
Initialization displayed data:
SPAN 849.949952MHz
STOP 849.999952MHz
CENTER 425.024976MHz
Hope this feedback is useful.
--
Best Regards,
Tom
VA7TA
|
STM32CubeIDE is based on eclipse and allows debugging with with the stm serial jag device which can be gotten cheaply as Chinese clones from ebay. There are several YouTube tutorials on the software. I just started using it yesterday and have built the normal led blink program and single stepped through it on a ST demo board based on the stm32f051c8t6 device. Good luck with your project and let the group how you proceed. On Tue, Nov 12, 2019, 11:22 PM vaclav_sal via Groups.Io <vaclav_sal= [email protected]> wrote: On Tue, Nov 12, 2019 at 09:33 AM, Oristo wrote:
I am using the free STM32CUBEIDE from ST Micro the Mc manufacture
to build some SDR control code for a home project and it seems to work
well.
Silly questions.
Can it be added to Eclipse IDE as "plug-in" ??
But it woudl make more sense , KISS, to use it as standalone IDE, right?
It woudl be easier to have both "running" and just switch between them as
necessary.
I am just looking for real debugger IDE and STM32CUBEIDE seems to be the
ticket.
|
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. ;-) It's worth noting, that any calibration in NanoVNA-Saver is in reference to the particular calibration done on the NanoVNA: So if you re-calibrate your NanoVNA, your NanoVNA-Saver calibration ceases to be valid, and may give incorrect readings. -- Rune / 5Q5R On Tue, 12 Nov 2019 at 01:26, Barry Jackson via Groups.Io <G4MKT= [email protected]> wrote: On 08/11/2019 15:18, Nick wrote:
> Thanks Rune. I did not understand the relationship between device
cals and nvna-s cals.
>
> Please allow me to check my understanding.
>
> Let's say I want to measure a ferrite choke from 1 to 50MHz. I set
up the cables and do a device cal over that frequency range using an
appropriate cal kit. I save that cal to say C0.
>
> With C0 selected on the device, I repeat the cal on nvna-s using the
same frequency range, same cables, same cal kit and save it to cal_0.cal.
>
> I can then measure my choke over the same frequency range using
nvna-s with as many data points as I like using multiple segments.
>
Yes
> Let's say I then want to measure a UHF filter over the range 100MHz
to 900MHz. Obviously I cannot use C0 and cal_0.cal. So I set up with
different cables and a different cal kit. I do a device cal over that
frequency range and save it to C1.
>
No. According to my understanding from Rune. On connection nvna-s reads
cal data from Memory 0 only, so unless your calibration originally
covered the whole of the frequency range and was saved to C0 then as far
as I understand that would not work.
> With C1 selected on the device, I repeat the cal on nvna-s using the
same frequency range, same cables, same cal kit and save it to cal_1.cal..
>
> I can then measure my filter over the same frequency range using
nvna-s with as many data points as I like using multiple segments and
save the results to s*p files.
>
> What if I then want to measure the filter over a restricted frequency
range, say 400 to 500MHz?
>
> Or a VHF filter with the same the cables and connectors from 100MHz
to 200MHz?
>
> Do I need a new pair of cals in either of these cases? (I would say
not.)
I would say that unless you make a full span course cal and use that
from C0 then you would need to save manual cals for the other ranges and
store them in C1..C3 and copy them to C0 before disconnecting from the
nvna and reconnecting to pick up each new cal from C0.
Maybe Rune can clarify whether or not I have misunderstood his comments
in
Barry
G4MKT
|
Re: Nanovna-Saver 0.2.0 MAC
Hello Dana,
thanks for the heads up! :-)
--
Rune / 5Q5R
toggle quoted message
Show quoted text
On Wed, 13 Nov 2019 at 03: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
|
OwO
