开云体育

Apologies in advance for what is probably a very basic question, but I am a complete newbie when it comes to Python. My Mac installation runs perfectly from the Terminal Window, but is it possible to run NanoVNASaver as an application rather than from the Terminal window?

I've tried to set up a "Run Shell Script" Application using Automator, but I'm not sure of how the path needs to be set up or even if this approach is the best one to use. I'm using the following command: python3 /Users/john/nanovna-saver/NanoVNASaver, but I get the following error:
Traceback (most recent call last):
File "/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.7/lib/python3.7/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
File "/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.7/lib/python3.7/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/Users/john/nanovna-saver/NanoVNASaver/__main__.py", line 21, in <module>
from PyQt5 import QtWidgets, QtCore
ModuleNotFoundError: No module named 'PyQt5'

I have also tried "cd /Users/john/nanovna-saver" and then NanoVNASaver, but I get a different error: -: line 1: NanoVNASaver: command not found.

I receive no errors when executing "NanoVNASaver" from the Terminal Window. I am running Catalina 10.15.4. Many thanks in advance for any possible suggestions!

John

Hi DiSlord,

It's working now , see screenshot attached (after 2 port calibration).

This is shown in Tera Term :

?CMD0 Ok
?CMD8 Ok
?CMD8 0xAA010000
?CMD8 Ok, run ACMD41
?ACMD41 99
?ACMD41 0x0080FFC0
CardType 4
filename VNA_20200525_00983.bmp
open 0
close 0

Thanks again for you fantastic work.

Jos

Thanks for made test (i don`t found old SD cards at home for check it)

As i see all SD card types work

SD cards work
SD HC cards work
SD XL cards should work if format to Fat32, but need test, possible i enable exFat support

Read/Write speed not big, but this limits of SD card SPI bus mode and processor.

In future i try

revert SPI speed slowdown to 36MHz
add save s1p and s2p data files as *.s1p or *.s2p (need read more about this format, it just text but possible variants)

I think this a good extend NanoVNA capabilities.

On Mon, May 25, 2020 at 11:30 PM, DiSlord wrote:

Found my error in card type detect

try this

Thank you very much, it works now.

Found my error in card type detect

try this

Yes, but you card answer
CMD58 CCR = 0x0080FF80
Not set Card Capacity Status (CCS) bit

Need read datasheet

It still doesn't work, SDHC card uses block as read/write unit and small capacity SD card uses byte as read/write unit, is there no driver for small capacity SD card?

Yes possible old cards can`t work on high SPI speed like 36MHz

I try set 18MHz speed for work, this little slowdown write from 150kB/s to 140kB/s

Also, i found RTC clock (internal timer) run to fast, as i see in datacheet STM32F303 use internal 40kHz LSI, but ChibiOS use default 32kHz value settings

SD_SendCmd CMD17, 0x20, 0x0000003F

Its mean Card answer on CMD17 (read sector) Incorrect address specified
1 variant i`m not correct detect card type (old cards use another adress mode)
2 variant card not correct deocode adress (from bigger speed)

Try this variant vs slowdown SPI for SD card (to 18MHz) and fixed RTC clock (for set normal clock timer need run time command and set new time)
Also i add read/write speed log stat for test

On my cards result ~180-220kB/s for read and ~90-140kB/s for write.

Hello DiSlord, I installed a microSD card slot and tested that both 8GB and 32GB microSDHC cards can work normally, but I found an ancient 1GB microSD card that does not work.

The following is the information displayed by the terminal when using a 1GB microSD card.

CMD0 Ok
CMD8 Ok
CMD8 0xAA010000
CMD8 Ok, ACMD41 99
CMD58 CCR = 0x0080FF80
CardType 4
SD_SendCmd CMD17, 0x20, 0x0000003F
SD_SendCmd CMD17, 0x20, 0x0000003F

Thank you very much for your guidance. Now there is a problem that 617DB-1023 has been discontinued. I tried to use YB006T-1023 instead, but the consistency of YB006T-1023 will be worse. I need to find more 617DB-1023 before larger production Or alternatives with consistent performance.

We have started to use the original file of OwOComm to make S-A-A-2, and now you can buy it through
This is the previous test situation /g/nanovna-users/topic/i_produced_s_a_a_v2_2/73993300

Known issue:
1.The touch pin connection of the LCD we use is slightly different from other sold versions. You may need to recalibrate the touch after updating the firmware. The manual of xpt2046 has been checked, and we believe that the connection sequence of our LCD is correct.
2.Above 3GHz, the performance will be seriously degraded. I will try to make some improvements, but for the time being, I have not designed a new PCB plan. The original GitHub file lacks the sym file and cannot be directly modified, and it takes a long time to verify after the modification.

The 4-inch version is already in the plan, and I will still use OwOComm's original PCB files to make it, but I will properly handle the installation of the 4-inch display.
Making S-A-A is not my main job, I only make them in my spare time and sell them by Maggie, so the arrival of the 4-inch version may be slow.

If Gabriel Tenma White and your team can help with further verification, I can provide some samples.

hugen

Alton,
Everything you need is in the forum Wiki and File areas.?
Print off a copy of the user guide and that will get you started.?
There is a lot of information that has been created in the forum posts as well so do you the search tool and use hashtags as well.?
Enjoy!



On Sun, 24 May 2020 at 7:50 PM, ALTON MCCONNELL via groups.io<nu8l@...> wrote: Hello Everyone.

Wonderful project!
I received my H4 instrument about two weeks ago.? It was in a black box with gold printing with cables, cal stds, etc.

I should upgrade the firmware to the latest.? I have version 0.5.0.? Build time Feb 21, 2020. Kernal 5.1.0.

I am using a Levovo Thinkpad T500 with Win 10.

What steps are required to update my firmware?? Does anyone have a step by step guide for anon-professional Win 10 user?

Thanks!

Alton, NU8L

There is a pdf file in the files section like 2nd or third from the bottom
entitled how to write firmware for windows, it something similar

On Sun, May 24, 2020, 18:50 ALTON MCCONNELL via groups.io <nu8l=
[email protected]> wrote:

Hello Everyone.

Wonderful project!
I received my H4 instrument about two weeks ago. It was in a black box
with gold printing with cables, cal stds, etc.

I should upgrade the firmware to the latest. I have version 0.5.0. Build
time Feb 21, 2020. Kernal 5.1.0.

I am using a Levovo Thinkpad T500 with Win 10.

What steps are required to update my firmware? Does anyone have a step by
step guide for anon-professional Win 10 user?

Thanks!

Alton, NU8L

Hello Everyone.

Wonderful project!
I received my H4 instrument about two weeks ago. It was in a black box with gold printing with cables, cal stds, etc.

I should upgrade the firmware to the latest. I have version 0.5.0. Build time Feb 21, 2020. Kernal 5.1.0.

I am using a Levovo Thinkpad T500 with Win 10.

What steps are required to update my firmware? Does anyone have a step by step guide for anon-professional Win 10 user?

Thanks!

Alton, NU8L

On the previous question about why using the OPEN cal standard instead of nothing. The standard prevents the ingress of any stray RF that might be floating around.

Try this variant of firmware vs you card
Now for card init used low speed SPI bus (~280kHz)

If not work, need try check Card slot pins, and card should be inserted as on foto
Used pins:

2 - SD_CS
3 - SPI_MOSI
4 - VDD
5 - SPI_SCLK
6 - GND
7 - SPI_MISO

And send logs
All read/write after init go on max speed (36MHz), possibly it to big, datasheet say max speed = 25MHz

Larry and all,
I executed the calibration via app/Saver, and tried a bunch of filters,
some reversed also. I enclose the scans.
For less narrow filters, I enlarged the scan window, but I assume the
impact from calibration should be minimal (as I think DiSlord said).

<>
Virus-free.
www.avg.com
<>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Sun, May 24, 2020 at 12:28 PM Larry Rothman <nlroth@...> wrote:

Radu,
If you're using NanovnaSaver, use that app to perform and save the
calibration and see if you get different results. I know that you can save
a number of calls in the Saver app.
Larry



On Sun, 24 May 2020 at 1:58 PM, Radu Bogdan Dicher<vondicher@...>
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.

<

Virus-free.
www.avg.com
<

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

On Sun, May 24, 2020 at 6:19 AM <david.hostetler@...> 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.

<>
Virus-free.
www.avg.com
<>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

Yes I just made a former out of 1/4" thick 'Tufnol' that measured 34mm x
13mm which is good for the two outer shields.
Then using 0.005" thick brass foil I marked out the shapes of the shields
34mm x 13mm and added 4mm tall sides to fold down. (see pics)
I carefully folded the foil over the former and bent the little tabs round
over the ends and soldered the flaps down.
Easy with ordinary soldering iron as the brass is so thin.
Once the shields were fabricated I rubbed them back and forth on a smooth
flat file to make sure all the sides were flush with the pcb.
ie filed off any high spots.
I then kept offering the shields to the pcb and marked out where I needed
to file away the side to avoid the SMD components going to the audio codec.
I then 'tinned' the edges with solder and tinned the 'fixing pads' on the
board.
Carefully lined up the shield and tinned one corner in place.
Final adjustments and then soldered the other pads.
Phew!
Dave

Radu,
If you're using NanovnaSaver, use that app to perform and save the calibration and see if you get different results. I know that you can save a number of calls in the Saver app.?
Larry



On Sun, 24 May 2020 at 1:58 PM, Radu Bogdan Dicher<vondicher@...> 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.

<>
Virus-free.
www.avg.com
<>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

Excellent! Thanks again for all the hard work.



On Sun, 24 May 2020 at 10:27 AM, DiSlord<dislordlive@...> wrote: 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