开云体育

Thank you very much DiSlord for your help and work.

I will install this file this afternoon and inform you for the result.

Regards,

Rudi

30Hz in 100MHz.

That is just 0.00003% low in frequency.

For the money we spent, why would anybody not be satisfied with that?

I'm still happy with the accuracy of my Grid Dip Meter.

73, Alek, VK6APK.

May I ask, what is the assembly house of Saa V2? It has small chips, 4 layer board and components on both sides of the board. All these could make an expensive boards but apparently it is not expensive.
Regards
Leif M

This is a different device.

100 mHz, 299 mHz.

Try this firmware, just quick build vs XTALFREQ 25997748

Hello,

For the moment, my friend has no access to the labo for component replacement (virus).

I would try your XTALFREQU modification but i'm not able to modify and recompile your software.

How can i proceed, may be with an other FW including the OFFSET command not active

on my NanoVNA-H ?

Thank you for helping me.

Regards,

Rudi

After searching for this component numbering, i found nothing at LCSC.

I've done many frequency measurements and? had a great drift with temperature.

May be it's not a TCXO but a XO with +/- 100 ppm tolerance ?

Just an idea..

Regards,

Rudi

At this time code very dirty and contain a lot of debug and test info and i not add it to git (if need i can send code on mail), at this time it only of 'proof of concept'

SD card support need only ~8-9kB for FatFS vs long filenames (possible reduce size on 3kB if use old DOS format 8.3 names)
RTC need additional 1kB (most of code for convert/user input output)
Low level functions for init/read/write SD card need ~2kB
FatFS need ~1.5kB of RAM (possible reduce to ~800bytes)

512 bytes for file directory search read buffer
512 bytes for read/write buffers (FatFS allow use directory search buffer for this)
and about ~200 bytes for

At begin i try use another lib for filesystem support like PetitFS

It size only ~2kB and need 600byte of Ram (512 read/write buffer can removed, but it huge reduce read/write speed all data need read every time), but have very limited create/write file support

VinxFS - possible better, but i not test it

So at this time need only ~12kB flash and 1.5kB Ram (i think possible also add this to NanoVNA - H it have ~14kB free flash and possible free ~1kB ram from spi buffer or use it)
Possible not use filesystem and use direct sector read write, it huge reduce code size, but need add additional PC mode/soft for get data from it.
Also not added USB support for use NanoVNA as card reader (USB still in Serial mode)

Gyula Molnar search LCSC and I found some slot variants: XUNPU TF-115K and THD THD2528-11SD-GF

Need search

microSD? Memory Card "connector&Ejector"

option for easy insert and remove card (use Push In，Roll out option)

On Fri, May 22, 2020 at 04:10 PM, Larry Rothman wrote:

DiSlord,
This absolutely fantastic!? How much free flash is left over now for other
enhancements?
As for the card detect switch, can you use one of the spare pins on the uP as
a sense input from the card slot switch? That way, you can verify quickly if a
card is present.
Please add the code to your GitHub repo (if not there already) as I would like
to see how you implemented this.
Thanks!
Larry

Yes, I want to screw a 4-inch display to my V2, I can’t see anything on the small display!

On Sat, May 23, 2020 at 12:39 PM, <aleks07111971@...> wrote:

Hi, will you screw the 4 inch V2 display?

It will be available later and a structure must be made that can support a 4" LCD.

Hi, will you screw the 4 inch V2 display?

Thank you all so much for your help so far!

I've taken the cable down to analyze it. I removed all adaptors and intermediate cables as Allison suggested. Using the lambda/8 method suggested by Jose, I get an impedance of 54.1 ohms. I have also found the open circuit impedance at lambda/4 and lambda/2, which should average out to the characteristic, and gives me 53.2 ohms, so it looks like the cable impedance is somewhere around 53.6 ohms. I'm not sure if this is within usual tolerance, but it seems questionable for such expensive cable.

My antenna is definitely not matched. (I got the vna to design a matching network). As the blog post shared by John points out, properly matched coax should not cause the ripples that I see. It should cause a frequency-dependent phase shift in the impedance, but not affect the magnitude/SWR. So it seems the ripples are likely caused by the mismatch between the cable and vna, and greatly increased in magnitude by the mismatch between the cable and antenna.

So it looks like these SWR ripples can be explained without any problem with the calibration or vna. However, if anyone has suggestions for verifying the output impedance of my nanovna, I'd still like to do it!

Thanks again!
Ed
KC1DKY

DiSlord,
This absolutely fantastic!? How much free flash is left over now for other enhancements?
As for the card detect switch, can you use one of the spare pins on the uP as a sense input from the card slot switch? That way, you can verify quickly if a card is present.?
Please add the code to your GitHub repo (if not there already) as I would like to see how you implemented this.?
Thanks!
Larry



On Fri, 22 May 2020 at 6:12 PM, DiSlord<dislordlive@...> wrote: Preliminary alfa update for NanoVNA H4 v0.9.0

As you know H4 have SD Card support (see images), but MicroSD slot not installed on board
I install it (get from old card reader), and implement read/write functional.

SC card Read/Write use:

SPI bus (shared vs LCD display), not decrease SPI bus speed, on test card not big amount errors on this speed
For read operation use CRC16 check, for not lost data
For write operation use multiple repeat on write errors
Supported cards: SD v1, SD v2, MMC (check only SD v2)
SD card slot pin CD not connected (it used for define inserted card in slot), so on every write need check it (it slowdown speed).

SD card use SPI bus for read/write operations (not fast speed, but easy to add), Stm32f303 processor not have hardware support SDIO :(

For filesystem support use last FatFS R0.14, options:

Support Fat16/Fat32 filesystem
Support long filenames
Support RTC use (real time clock)
Support read/write file

For take screenshot need click on Bandwidth text on bottom (see screenshot)
For get and write 1 screenshot need ~2-3 seconds (filesize ~300kB), output format 16bpp *.bmp

If screenshot success on middle screen show

SCREENSHOT
VNA_20200522_86284.bmp

or in some cases (i can`t find how check CRC on write operations)

SCREENSHOT
? Fail write

All screenshots put in root directory, filename format:

VNA_year mounth day_number.bmp

For support time in Fat filesystem and filename, implemented RTC clock in VNA
For set clock need use command 'time'

usage: time [y|m|d|h|min|sec] value

Warning! command time not check correct value input
RTC clock not reset while battery in

All logs go to console, so possible see some errors (connect to PC, run Putty or another console programm and made some screenshots)
Warning!!!! For not lost data, not use card vs important data, use formatted on Fat32 filesystem cards.

PS support SD card take 2 days, but now i know how it work :) (read a lot of manuals and datasheet)

Here additional foto.
At the place where the card slot is located, a hole was cut. Now the card can be removed and put without any problems.

Preliminary alfa update for NanoVNA H4 v0.9.0

As you know H4 have SD Card support (see images), but MicroSD slot not installed on board
I install it (get from old card reader), and implement read/write functional.

SC card Read/Write use:

SPI bus (shared vs LCD display), not decrease SPI bus speed, on test card not big amount errors on this speed
For read operation use CRC16 check, for not lost data
For write operation use multiple repeat on write errors
Supported cards: SD v1, SD v2, MMC (check only SD v2)
SD card slot pin CD not connected (it used for define inserted card in slot), so on every write need check it (it slowdown speed).

SD card use SPI bus for read/write operations (not fast speed, but easy to add), Stm32f303 processor not have hardware support SDIO :(

For filesystem support use last FatFS R0.14, options:

Support Fat16/Fat32 filesystem
Support long filenames
Support RTC use (real time clock)
Support read/write file

For take screenshot need click on Bandwidth text on bottom (see screenshot)
For get and write 1 screenshot need ~2-3 seconds (filesize ~300kB), output format 16bpp *.bmp

If screenshot success on middle screen show

SCREENSHOT
VNA_20200522_86284.bmp

or in some cases (i can`t find how check CRC on write operations)

SCREENSHOT
Fail write

All screenshots put in root directory, filename format:

VNA_year mounth day_number.bmp

For support time in Fat filesystem and filename, implemented RTC clock in VNA
For set clock need use command 'time'

usage: time [y|m|d|h|min|sec] value

Warning! command time not check correct value input
RTC clock not reset while battery in

All logs go to console, so possible see some errors (connect to PC, run Putty or another console programm and made some screenshots)
Warning!!!! For not lost data, not use card vs important data, use formatted on Fat32 filesystem cards.

PS support SD card take 2 days, but now i know how it work :) (read a lot of manuals and datasheet)

I did not see it as mocking, but rather a brilliant and feasible
explanation of what might be the cause of the VSWR 'ripple'.

I received the 25 dollar unit from Amazon today.
It is the gen111.taobao.com unit. I looked at that web site and it is a Chinese NanoVNA store.
This one defaults to 50KHz to 900 MHz at power-up.
Hans was correct: the open and short calibrators were screwed onto the unit and the 50
ohm calibrator was screwed onto one of the two included cables with a fem-to-fem adaptor.
It's all good. It has a plastic storage case that everything just fits in.
The lcd screen is a little misaligned, not square with the cutout, but not a problem. It is only off by a minor amount
and doesn't affect readability.
I am thoroughly happy with it.
I have to wear my magnifier glasses to read it.
I will probably get the 4.3 inch screen version in the future.
73 de N8MIB, Mike

On Fri, May 22, 2020 at 04:07 PM, Birdman wrote:

KV5,
That sounds fantastic! I had a hard time following what version of firmware
does this, and where is the "Ch-0 Info" screen? I don't recall seeing that
option when I tried the big font software a few weeks ago.

Thanks in advance....!

--
Regards,
Chris

Disregard, just reloaded the big font and found it under "Config". I missed that the last time I tried it. Love this functionality: Select a marker on SWR, and then use the scroll clicker to move around and find the best SWR values, without the use of a microscope!!

@Hugen, you really should make this functionality part of your standard firmware!! There are certainly a lot of folks asking/discussing this subject.... And if nothing else, the larger fonts are really helpful. I can barely read the tiny little normal fonts WITH my reading glasses on, at my desk. I can only image somebody trying to use this out in the "field".

--
Regards,
Chris

On Sun, Nov 10, 2019 at 01:33 AM, KV5R wrote:

Also, noted that the "Ch-0 Info" screen works even if all traces are off
(reduces clutter) and freq is CW, so it works like a text-based antenna
analyzer and is very easy to read, with those 5mm high digits! And with only
SWR trace on, and a small span, the jog switch will move the frequency in
small steps, and Marker > Search > Minimum will find lowest SWR point in the
swept span.
I'm sure these added features will make the nano more attractive to hams with
primary interest being antenna analyzer.

KV5,
That sounds fantastic! I had a hard time following what version of firmware does this, and where is the "Ch-0 Info" screen? I don't recall seeing that option when I tried the big font software a few weeks ago.

Thanks in advance....!

--
Regards,
Chris