Date   

Re: Homebrew sheilding

Dave W6OQ
 

Thin brass solders easily with regular electronic solder (at least it did before they took the lead out). You might want to tin it along the edges you are soldering together. Also cuts fairly easily with ordinary scissors.


Re: NanoVNA #calibration

DiSlord
 

On run external program scan, calibretion data always rebuild, and use interpolation
Do not pay attention to it, if start stop freq some, no difference


Re: NanoVNA #calibration

Radu Bogdan Dicher
 

I never change the frequency range (center/span) - at least, not
intentionally. I really only expect to be using this to sort IF
filters, and for these a range from 10.4 to 11MHz or so works pretty well.

If I leave everything alone and just insert a filter in my socket, the
device seems to execute a spontaneous scan, "C1" stays in caps, and if I
look on the device's screen, I still see the tilt (harder to read, as it's
on the small device screen, but if on the left side the trace matches a
horizontal grid line, on the right it goes right half way between two, and
higher).

If I run the scan from the Saver app, "C1" changes to "c1" but readings
stay very much the same, as far as I can tell.

<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virus-free.
www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Sun, May 24, 2020 at 11:13 AM Bill Cromwell <wrcromwell@gmail.com> wrote:

Hi,

I wonder if before recall a saved calibration we should do a reset first.

73,

Bill KU8H

On 5/24/20 1:58 PM, Radu Bogdan Dicher wrote:
Larry - I re-executed the calibration over 10.4 through 11MHz, saved to
"1," and I always recall it before measuring. However, the letter changes
every time I start the scan (from "C1" to "c1") - I press sweep, flop!,
it
changes. Not sure why, as far as I can tell I have the same settings on
device and computer application (center: 10.7MHz, span: 600kHz), and I
RECALL 1 it every time I prepare for scanning.

David - yes, I am using 56.2ohm and 301ohms, 1% tolerance resistors. It's
the closest I could come up with by calculating for minimum loss. The
filters are 150kHz Muratas (JAs), but I also measured about four
different
bandwidths, and from multiple sources. I have at least 7 or 8 different
batches and they all have the 5dB difference L/R. I think my calibration
is
not getting applied, based upon Larry's feedback above.

Still trying to figure out how to maintain calibration settings while
executing the scan.

Thank you both,
Radu.

<
http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail

Virus-free.
www.avg.com
<
http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Sun, May 24, 2020 at 6:19 AM <david.hostetler@ieee.org> wrote:

What I see in the plot that you posted is a filter that is about 170 kHz
wide at the -3 dB points and centered at 10.715 MHz. This is consistent
with a Murata SFELF10M7HA00-B0 that has a spec of 180 +/-40 kHz and a
center frequency of 10.7 MHz +/-30 kHz. The fact that all the filters
exhibit the same response wouldn't surprise me if you purchased them at
the
same time, they probably came from the same batch, and the tolerance is
likely based on batch to batch differences caused by process variations
rather than random variations within a batch.

It is a little harder to understand/explain the fact that the low
frequency side runs out of dynamic range at -60 dB and the high side
gets
there at 5 dB higher at -55 dB. Since these filters are symmetrical,
have
you tried swapping the input and output by turning the filter around at
the
fixture?

Also, you haven't really detailed your circuit for matching the 50 ohm
of
the VNA to the 330 ohm of the filter. If I were doing it, I would use a
minimum loss matching pad. This would consist of a 54.281014769949586
ohm
resistor (it is the value that the calculator gave - LOL) across the
input
and output coax to the VNA and a series resistor of 304.01167774007837
ohms
up to the filter input/output. This would give a loss of
13.867585162369918
dB on each side. 5% values: 56 and 300. 1% values: 54.9 and 301. I am
sure
the 5% values would be just fine. You could bridge the filter location
with
a short on your test fixture to determine the exact loss through the
pads,
then place the filter in the fixture and easily find the filter
insertion
loss.





--
bark less - wag more



<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virus-free.
www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>


Re: Homebrew sheilding

Dave VE3LHO
 

Dave,

I am curious how you soldered (braized?) the brass shim. I've been thinking about making my own shields (not for my nano) but am a bit intimidated by my lack of experience with brass.

Thanks,
Dave L

On Sat, May 23, 2020 at 07:04 AM, Dave B wrote:


Hi just spent a UK windy afternoon confined to my radio 'shack' , so decided
to upgrade the screening on my 'basic' clone nanoVNA to see if the INPUT
'noise' could be reduced.
I made the screens out of some 'shim' brass foil and formed them round some
srbp (Tufnol) formers THAT I made first.
I am pleased with the improvement that just a couple of hours 'metal bashing'
has produced.
Hopefully this will inspire others to have a go?
Dave


Re: NanoVNA #calibration

Bill Cromwell
 

Hi,

I wonder if before recall a saved calibration we should do a reset first.

73,

Bill KU8H

On 5/24/20 1:58 PM, Radu Bogdan Dicher wrote:
Larry - I re-executed the calibration over 10.4 through 11MHz, saved to
"1," and I always recall it before measuring. However, the letter changes
every time I start the scan (from "C1" to "c1") - I press sweep, flop!, it
changes. Not sure why, as far as I can tell I have the same settings on
device and computer application (center: 10.7MHz, span: 600kHz), and I
RECALL 1 it every time I prepare for scanning.
David - yes, I am using 56.2ohm and 301ohms, 1% tolerance resistors. It's
the closest I could come up with by calculating for minimum loss. The
filters are 150kHz Muratas (JAs), but I also measured about four different
bandwidths, and from multiple sources. I have at least 7 or 8 different
batches and they all have the 5dB difference L/R. I think my calibration is
not getting applied, based upon Larry's feedback above.
Still trying to figure out how to maintain calibration settings while
executing the scan.
Thank you both,
Radu.
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virus-free.
www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Sun, May 24, 2020 at 6:19 AM <david.hostetler@ieee.org> wrote:

What I see in the plot that you posted is a filter that is about 170 kHz
wide at the -3 dB points and centered at 10.715 MHz. This is consistent
with a Murata SFELF10M7HA00-B0 that has a spec of 180 +/-40 kHz and a
center frequency of 10.7 MHz +/-30 kHz. The fact that all the filters
exhibit the same response wouldn't surprise me if you purchased them at the
same time, they probably came from the same batch, and the tolerance is
likely based on batch to batch differences caused by process variations
rather than random variations within a batch.

It is a little harder to understand/explain the fact that the low
frequency side runs out of dynamic range at -60 dB and the high side gets
there at 5 dB higher at -55 dB. Since these filters are symmetrical, have
you tried swapping the input and output by turning the filter around at the
fixture?

Also, you haven't really detailed your circuit for matching the 50 ohm of
the VNA to the 330 ohm of the filter. If I were doing it, I would use a
minimum loss matching pad. This would consist of a 54.281014769949586 ohm
resistor (it is the value that the calculator gave - LOL) across the input
and output coax to the VNA and a series resistor of 304.01167774007837 ohms
up to the filter input/output. This would give a loss of 13.867585162369918
dB on each side. 5% values: 56 and 300. 1% values: 54.9 and 301. I am sure
the 5% values would be just fine. You could bridge the filter location with
a short on your test fixture to determine the exact loss through the pads,
then place the filter in the fixture and easily find the filter insertion
loss.



--
bark less - wag more


Re: NanoVNA #calibration

DiSlord
 

Big letter mean used calibration data stored in flash
If you change frequency, or use multisegment scan from NanoVNA saver or another program, calibration table rebuild and use interpolated values from main data
Big 'C' mean not interpolated values
Small 'c' interpolated

In most cases mo matter, interpolation good work if start/stop freq range not big


Re: NanoVNA #calibration

Radu Bogdan Dicher
 

Larry - I re-executed the calibration over 10.4 through 11MHz, saved to
"1," and I always recall it before measuring. However, the letter changes
every time I start the scan (from "C1" to "c1") - I press sweep, flop!, it
changes. Not sure why, as far as I can tell I have the same settings on
device and computer application (center: 10.7MHz, span: 600kHz), and I
RECALL 1 it every time I prepare for scanning.

David - yes, I am using 56.2ohm and 301ohms, 1% tolerance resistors. It's
the closest I could come up with by calculating for minimum loss. The
filters are 150kHz Muratas (JAs), but I also measured about four different
bandwidths, and from multiple sources. I have at least 7 or 8 different
batches and they all have the 5dB difference L/R. I think my calibration is
not getting applied, based upon Larry's feedback above.

Still trying to figure out how to maintain calibration settings while
executing the scan.

Thank you both,
Radu.

<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virus-free.
www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Sun, May 24, 2020 at 6:19 AM <david.hostetler@ieee.org> wrote:

What I see in the plot that you posted is a filter that is about 170 kHz
wide at the -3 dB points and centered at 10.715 MHz. This is consistent
with a Murata SFELF10M7HA00-B0 that has a spec of 180 +/-40 kHz and a
center frequency of 10.7 MHz +/-30 kHz. The fact that all the filters
exhibit the same response wouldn't surprise me if you purchased them at the
same time, they probably came from the same batch, and the tolerance is
likely based on batch to batch differences caused by process variations
rather than random variations within a batch.

It is a little harder to understand/explain the fact that the low
frequency side runs out of dynamic range at -60 dB and the high side gets
there at 5 dB higher at -55 dB. Since these filters are symmetrical, have
you tried swapping the input and output by turning the filter around at the
fixture?

Also, you haven't really detailed your circuit for matching the 50 ohm of
the VNA to the 330 ohm of the filter. If I were doing it, I would use a
minimum loss matching pad. This would consist of a 54.281014769949586 ohm
resistor (it is the value that the calculator gave - LOL) across the input
and output coax to the VNA and a series resistor of 304.01167774007837 ohms
up to the filter input/output. This would give a loss of 13.867585162369918
dB on each side. 5% values: 56 and 300. 1% values: 54.9 and 301. I am sure
the 5% values would be just fine. You could bridge the filter location with
a short on your test fixture to determine the exact loss through the pads,
then place the filter in the fixture and easily find the filter insertion
loss.




Re: Calibration using Anritsu "tee" #calibration #solt

aparent1/kb1gmx <kb1gmx@...>
 

At HF the Anritsu tee is likely not going to be that much better a cal
as the supplied SOL. To test it cal with the ANritsu Tee and then
measure the supplies SOL. Likely any difference you see will be
due to the N to SMA adaptors adding length to the calibration plane.

At upper UHF it may make a difference.

Generally while good there is a finite level of accuracy available
and you have to go to extremes to verify it.

Allison
-----------------
No direct email, it goes to bit bucket due address harvesting in groups.IO


Re: Calibration using Anritsu "tee" #calibration #solt

Oristo
 

You want to calibrate with as nearly to test jig configuration as possible.
For example, when measuring with alligator clips, I calibrate using alligator clips.


Re: NanoVNA firmvare, compiled by DiSlord #firmware with MiniSD support #firmware

Jos Stevens
 

Hi DiSlord and Larry,

Thanks for all info.

DiSlord,  I did flash the latest  0.9.1 firmware initially, but to be sure and in case you updated the 0.9.1 release I loaded the one you gave me the link to and flasherd it, same result.   When I have the memory card inserted in the NanoVNa and start "Terra Term" it immediately reports :

SD_SendCmd err CMD0, 0xFF, 0x00000000
 SD_SendCmd err CMD0, 0xFF, 0x00000000
CardType 0

And I also get a report from my system that a portable storage device has been connected to it.  So I'm afraid that , for some reason, my SD card that is marked MicroSD HC I (Capital i) 8 GB not is detected by your firmware.   So I have to wait untill I receive the ordered new card and see what happens then. If it's not working either, I will buy one of your type of cards.

Larry, thanks for your suggestion.

Best regards
Jos


Re: NanoVNA firmvare, compiled by DiSlord #firmware with MiniSD support #firmware

DiSlord
 

My test SD cards foto


Re: NanoVNA firmvare, compiled by DiSlord #firmware with MiniSD support #firmware

DiSlord
 

In my test i use
Samsung EVO Plus 128Gb HD XL
Samsung EVO Plus 32Gb SD HC
Kingston MicroSD HC1 16Gb

All worked, detected
128Gb flash not write (used exFat filesystem, not supported), but card answer and read sectors ok

All others card answer and work
My card powerup log on 1 screenshot
SD_SendCmd err CMD0, 0xFF, 0x00000000
CMD0 Ok
CMD8 Ok
CMD8 0xAA010000
CMD8 Ok, run ACMD41
ACMD41 99
ACMD41 0x0080FFC0
CardType 4
My card powerup log on 2 screenshot
CMD0 Ok
CMD8 Ok
CMD8 0xAA010000
CMD8 Ok, run ACMD41
ACMD41 99
ACMD41 0x0080FFC0
CardType 4
Try made several screenshots, possible card can`t powerup from first 2 commands


Calibration using Anritsu "tee" #calibration #solt

robertinzano@...
 

I have access to an Anritsu VNA at my job, and with it we have the calibration "tee" which has open, short and load using N connectors. Would I make more accurate measurements using this for calibration or do the standards that come with the NanoVNA work well enough? Also, will using this for S-O-L but using the through that came with it have any adverse effect? Should I use an "N" through or will that make no difference?

Thanks for any help! I'm a decent tech but am definitely not anything close to an RF engineer lol!


Re: NanoVNA firmvare, compiled by DiSlord #firmware with MiniSD support #firmware

Larry Rothman
 

Hi Jos
I think you might ask DiSlord if the SD card driver supports SDHC type cards or the older type. 
Larry


Sent from Rogers Yahoo Mail on Android

On Sun, 24 May 2020 at 9:28 am, Jos Stevens<jrs@xs4all.nl> wrote: Hi DtSlord,

Thank you very much for the new firmware with microSD support, fantastic
!    I have added the connector to my H-4 and flashed the firmware.

I have 2 questions  :

1 I tried to set the time by the new "time"command, but when I type
"time 2020 05 24 13 30 00", I get back : "Too many arguments, max 4".   
I tried several formats but no success, could you please give me the
correct format ?

2) I have one 8 GB microSD-HC card only , when I insert it and press the
bandwitdth display on the NanoVNA-H4, I get the error message :  
"SD_Send Cmd err CMD0, 0xFF , 0x00000000" twice and "CardType 0".   Does
this mean that this card is not supported  ? It is empty and formatted
in FAT32.  I have ordered another card :  "Sandisc 32 GB Ultra
memorycard UHS-1 A1",     Will this one is will be Ok ?

In advance, thanks for your response.

Jos


Re: NanoVNA firmvare, compiled by DiSlord #firmware with MiniSD support #firmware

DiSlord
 

Flash last fitmware from this post
https://groups.io/g/nanovna-users/message/13787
In it i fix some problems

Time command syntac is:
time y 2020
time m 5
time d 24
time h 13
time min 30
time sec 10
"SD_Send Cmd err CMD0, 0xFF , 0x00000000" twice and "CardType 0"
Card not detected or answer, try update firmware


Re: NanoVNA firmvare, compiled by DiSlord #firmware with MiniSD support #firmware

Jos Stevens
 

Hi DtSlord,

Thank you very much for the new firmware with microSD support, fantastic !    I have added the connector to my H-4 and flashed the firmware.

I have 2 questions  :

1 I tried to set the time by the new "time"command, but when I type "time 2020 05 24 13 30 00", I get back : "Too many arguments, max 4".    I tried several formats but no success, could you please give me the correct format ?

2) I have one 8 GB microSD-HC card only , when I insert it and press the bandwitdth display on the NanoVNA-H4, I get the error message :   "SD_Send Cmd err CMD0, 0xFF , 0x00000000" twice and "CardType 0".   Does this mean that this card is not supported  ? It is empty and formatted in FAT32.  I have ordered another card :  "Sandisc 32 GB Ultra memorycard UHS-1 A1",     Will this one is will be Ok ?

In advance, thanks for your response.

Jos


Re: Homebrew sheilding

G7TAO <sheriff.s@...>
 

On Sat, May 23, 2020 at 02:04 PM, Dave B wrote:


round some srbp (Tufnol) formers THAT I made first.

Hello,

Have you got any images of the formers you made and any more close ups of your finished work? I've got a clone, non-shielded and wondered about adding something to it. Given the plethora of units on eBay I don't think I could have been sure to get one with shielding


Re: NanoVNA bricked

Dr.Heblik@...
 

Hi folks,

I got a bricked VNA (white screen) from a very frustrated OM (very cheap: a glass of beer only, hi).
- First: I tried the "DfuSe"-way - no success - as expected.
- Second: I used the "STM32CubeProgrammer" and shortened Pin "VCC" with Pin "Boot0" to reach the programming mode. Using the concerning "nnn.hex" File - IT WORKS !
- Third: I tried the method which is decribed above with the ST-Link - IT WORKS also !
So nobody need a "sacrificial" device in his stock - I think. Give it away (for much more than one glass of beer only.., hi)
(I use WIN10 prof.)

Peter , DD6USB

P.S.
It was worth a glass of beer I think.......


Re: NanoVNA #calibration

Dave W6OQ
 

What I see in the plot that you posted is a filter that is about 170 kHz wide at the -3 dB points and centered at 10.715 MHz. This is consistent with a Murata SFELF10M7HA00-B0 that has a spec of 180 +/-40 kHz and a center frequency of 10.7 MHz +/-30 kHz. The fact that all the filters exhibit the same response wouldn't surprise me if you purchased them at the same time, they probably came from the same batch, and the tolerance is likely based on batch to batch differences caused by process variations rather than random variations within a batch.

It is a little harder to understand/explain the fact that the low frequency side runs out of dynamic range at -60 dB and the high side gets there at 5 dB higher at -55 dB. Since these filters are symmetrical, have you tried swapping the input and output by turning the filter around at the fixture?

Also, you haven't really detailed your circuit for matching the 50 ohm of the VNA to the 330 ohm of the filter. If I were doing it, I would use a minimum loss matching pad. This would consist of a 54.281014769949586 ohm resistor (it is the value that the calculator gave - LOL) across the input and output coax to the VNA and a series resistor of 304.01167774007837 ohms up to the filter input/output. This would give a loss of 13.867585162369918 dB on each side. 5% values: 56 and 300. 1% values: 54.9 and 301. I am sure the 5% values would be just fine. You could bridge the filter location with a short on your test fixture to determine the exact loss through the pads, then place the filter in the fixture and easily find the filter insertion loss.


Re: NanoVNA-V2 Support Page

aleks07111971@...
 

Who can increase the font size in the firmware?

8241 - 8260 of 21827