On Tue, Jun 23, 2020 at 11:11 PM, Terry VK5TM wrote:
Even with reading glasses I find the screen of the NanoVna too small, so it's not getting used at the moment until I can sort a better solution.
--
Terry,
? ?The display of the tinySA isn't as congested as the NanoVNA so its much easier to read if you wear glasses.? I would compare its readability to the NanoVNA using the AA firmware.? If only one marker is used, the marker information is displayed in a font size similar to the H4.? It has a companion PC application, tinySA.exe, but I think most users will only need it for capturing screenshots.



- Herb

There is already,

开云体育

I almost always use my nanoVNA in the shack and connected to the PC with the nanoVNA saver program, much more convenient operation not only by the screen size.

I suppose that there will be a similar companion program for the TinySA.

73 de Ignacio EB4APL

On Wed, Jun 24, 2020 at 08:11 AM, Terry VK5TM wrote:

Even with reading glasses I find the screen of the NanoVna too small

It is just a matter of good reading glasses. Also in my age of 72 it is possible
to read that 2.8 inch display of the nanoVNA.

I think the price is important. The lower the cost, how more toys you can buy ;-)

73, Rudi DL5FA

On Wed, Jun 24, 2020 at 08:11 AM, Terry VK5TM wrote:

Even with reading glasses I find the screen of the NanoVna too small

It is just a matter of good reading glasses. Also in my age of 72 it is possible
to read that 2.8 inch display of the nanoVNA.

I think the price is important. The lower the cost, how more toys you can buy ;-)

73, Rudi DL5FA

You will have to wait for the 4" version.

Even with reading glasses I find the screen of the NanoVna too small, so it's not getting used at the moment until I can sort a better solution.
--
Terry VK5TM

Dear Dick,

I am assuming that people with reduced eyesight already have reading glasses lying around everywhere, at least I do.

开云体育

开云体育

I want one !!! >:o

As the tinySA FW and HW are nearing completion I made a short introduction video that is available

As the tinySA FW and HW are nearing completion I made a short introduction video that is available

The testers have been asking for some extra functionality and it was still possible to fit it into the available space.
Here you see two functions in one picture.

One tinySA is used as signal generator and does a power sweep from -10 to -60dBm in a sweep time set to 6 seconds. Level sweep can ramp up or ramp down.
The second tinySA is set to zero span and a trigger level of -12dBm and also with a saweep time set to 6 seconds. There is still a bit of switching noise in the ramp.

A small status update. Progress is good. The performance measurements by the testers is confirming the specification and the user interface has been updated based on user feedback.
Preparations for a small first pilot run to confirm manufacturability are starting.
We will keep you informed.

Measuring the 1dB compression point is a lot of work as you manually have to step through many signal levels to find the level where the detected signal is 1dB below the expected level.
Using the internal step attenuator and the LINEARITY measurement in the MEASURE menu most of the manual step are automated.
The green line in the picture below shows 9 measurements shown for each 1 dB step starting at 29dB attenuation.

Using an external signal generator at any of the supported low input frequencies at a level above the expected compression point level (such as?+10dBm) will allow a quick measurement of the linearity.
As the green line shows little disturbances below where the compression starts it is safe to conclude the internal step attenuator is very linear.

Next to the performance of the first LO and the first mixer, the performance of the various resolution filters does have a huge impact on the performance of a spectrum analyzer. To provide some understanding of what the tinySA resolution filters can (not) do I added a page to the wiki:

One of the beta testers did a very good job at measuring the power linearity of an uncalibrated tinySA.
Uncalibrated implies the absolute level may be a couple of dB off but the relative steps should be accurate

First the low input



And the high input



From these measurements that are a couple of conclusions.

The 1dBc of the low input is possibly at or a bit above 0dBm
The 1dBc of the high input is expected to be close to -10dBm
The low input LPF is at -3dB around 300MHz and at -6dB at 350MHz. This will have to be compensated for.
Below 1MHz the low input is having some problems. These possibly can be corrected by adjusting AGC and LNA
Below 0.4MHz the phase noise limits the low end of the power measurement range
The high input is flat +/- 1.5dB over the whole range
The power level measurement is close to the official +/- 1dB overall linearity.

Overall this measurement confirms the spec on the wiki.

I write all info about in NanoVNA group in my firmware topic
/g/nanovna-users/topic/nanovna_firmvare_compiled_by/73181877

For transfer data need eject SD card from slot and put in PC card reader, screenshots stored in standart Windows *.bmp file format vs 16bpp color.

If not use FatFS lib for support Fat32 filesystem, possible save and load data by sectors 512 byte size (can be useful for stand alone use) or use more simple filesystems. If need just read (and write vs some limitations), possible use very compact PetitFS lib, it need just ~2kB flash and very fast

PS Sorry for my typo, not SC, it SD card

On Fri, May 22, 2020 at 09:52 AM, DiSlord wrote:

At this moment i implement SC Card support for NanoVNA H4, it very simple and good work. Use SPI interface some as display, need only SD_CS,?SPI_MOSI,?SPI_SCLK signals (SPI shared vs display and work on some speed), good if exist SD_CD (for SD card insert);

It very low cost solution, need ~7kB flash and ~600 bytes RAM for full dile read/write Fat16/32 support (can extend, use FatFS lib)

Dislord,
? ?Will your SC Card support also include transferring stored traces to a PC?? What formats do you anticipate being a to store to the SC Card?

- Herb

Will be a good solution for a future 4" version of the tinySA. In the 2.8" version there is not enough spare space at the edge of the PCB to place the SD cardslot

On Thu, May 7, 2020 at 01:41 AM, <erik@...> wrote:

As the internal flash can endure above 10k write cycles I assume using the internal flash with a warning not to store too often is OK.

Saving settings to one of the internal memory slots now also saves the stored trace and loading a saved setting will restore the stored trace.

This provides 4 memory slots to save traces?

At this moment i implement SC Card support for NanoVNA H4, it very simple and good work. Use SPI interface some as display, need only SD_CS,?SPI_MOSI,?SPI_SCLK signals (SPI shared vs display and work on some speed), good if exist SD_CD (for SD card insert);

It very low cost solution, need ~7kB flash and ~600 bytes RAM for full dile read/write Fat16/32 support (can extend, use FatFS lib)