¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Expand calibration slot count from 5 to 7


 

One slot for calibration requires a lot of space. 5 tables of 101 points for 2 channels of 4 bytes each value + another table for frequencies of 101 points and 4 bytes each (and round off at 0x800 border due to the peculiarities of rewriting flash processor) 4040 + 404 + a couple of bytes of additional information
Total one slot for calibration takes 0x00001800 (or 6 kilobytes, 5 tables + 2 kilobytes config = 32 kilobytes there is a slot for settings)

If you exclude the table for frequencies (they can be calc if necessary, but more difficult), then you can fit in the size 0x1000 (4096) and this will make it possible to store 7 calibration tables. But it is necessary to significantly change the code

Excluding the frequency table was the first thought for expanding the memory size, but I managed to solve it by optimizing the code now for the code about 24 kilobytes of memory are still free (you can add 2-3 more slots, but it¡¯s easier to optimize the configuration structure itself and throw out the frequencies).

Who can implements that?


 

You mean changing the memory map to give more space to calibration data and less to code?
Or to remove the frequency table from the stored data as this can be recalculated?
Or check if the isolation correction contains only noise so it can be removed?
Or something else?
--
NanoVNA Wiki: /g/nanovna-users/wiki/home
NanoVNA Files: /g/nanovna-users/files
Erik, PD0EK


 

On Tue, Apr 14, 2020 at 01:20 PM, <erik@...> wrote:


Or to remove the frequency table from the stored data as this can be
recalculated?
This, single data from freq table need in marker operation

On all others cases need from 0 to N points step like on generation


 

What about just tacking in an additional Serial EEPROM for such things
with the appropriate code (HW Engineer speaking here).

Sam Reaves
ARS W3OHM
Owner and Moderator of:
LeCroy Owners Group on Groups.io (Current and Future Group)


 

On Tue, Apr 14, 2020 at 04:41 PM, Sam Reaves wrote:


What about just tacking in an additional Serial EEPROM for such things
with the appropriate code (HW Engineer speaking here).

Sam Reaves
ARS W3OHM
Owner and Moderator of:
LeCroy Owners Group on Groups.io (Current and Future Group)
Possible use SD-Card (as in F version, H4 version have unsoldered SD card slot). But for H version need made HW mod.

But in existing hardware at this time more easy remove frequency table (it contain start, start + 1*step, start + 2*step, ..... start + 100 * step, stop) start, stop, points count also save in properties. It allow more better use flash space for properties config.

Possible use function in real time calculate frequency for index (need only optimize in speed)


 

Doesn't the H4 already have more flash memory? The firmware isn't using
the extra capacity for anything yet but it could...

On Wed, Apr 15, 2020 at 12:51 AM DiSlord <dislordlive@...> wrote:

On Tue, Apr 14, 2020 at 04:41 PM, Sam Reaves wrote:


What about just tacking in an additional Serial EEPROM for such things
with the appropriate code (HW Engineer speaking here).

Sam Reaves
ARS W3OHM
Owner and Moderator of:
LeCroy Owners Group on Groups.io (Current and Future Group)
Possible use SD-Card (as in F version, H4 version have unsoldered SD card
slot). But for H version need made HW mod.

But in existing hardware at this time more easy remove frequency table (it
contain start, start + 1*step, start + 2*step, ..... start + 100 * step,
stop) start, stop, points count also save in properties. It allow more
better use flash space for properties config.

Possible use function in real time calculate frequency for index (need
only optimize in speed)




 

H4 now have 201 point count and need x2 size (64kB)

But yes total size 256kB, and firmware size at this moment ~80kB, it allow add additional slots (for H version can`t)

The previous H version was limited in resources and further development went in a simple way to increase processor performance (which did not give much as a result and stop evolution H version). By simply optimizing and refactoring the code, it was possible to reduce the size of the firmware and improve performance (you can compare perfomance and firmware size edy555 v0.6 and 0.7.1 vs my size and perfomance fixes and my last 0.8.4 for H. And hugen 0.5 based on edy555 v0.6 and my 0.8.4 port for H4). But of course it¡¯s easier to put a more powerful processor

PS For additional info, base gcc compiler sin and cos functions use big size table and interpolate it in calc. Possible use extended FFT sin cos table for this and save addidional 5-6kB flash size


Glen K4KV
 

Yes, a larger processor does not cost a whole lot more.? A F446 M4 chip has HUGE memory.

One big limitation for me is to be able to SAVE a scan for later download to a PC.

I just used my H4 for tuning 8 12 element LFA 2M antennas.? Each one was a little different, and in my XPOL

configuration, I had to move the reflectors to get the impedance right.? The H4 was outstanding except for weak

brightness outdoors.

73

Glen K4KV

On 4/15/2020 04:11, DiSlord wrote:
H4 now have 201 point count and need x2 size (64kB)

But yes total size 256kB, and firmware size at this moment ~80kB, it allow add additional slots (for H version can`t)

The previous H version was limited in resources and further development went in a simple way to increase processor performance (which did not give much as a result and stop evolution H version). By simply optimizing and refactoring the code, it was possible to reduce the size of the firmware and improve performance (you can compare perfomance and firmware size edy555 v0.6 and 0.7.1 vs my size and perfomance fixes and my last 0.8.4 for H. And hugen 0.5 based on edy555 v0.6 and my 0.8.4 port for H4). But of course it¡¯s easier to put a more powerful processor

PS For additional info, base gcc compiler sin and cos functions use big size table and interpolate it in calc. Possible use extended FFT sin cos table for this and save addidional 5-6kB flash size


 

On Wed, Apr 15, 2020 at 01:11 AM, DiSlord wrote:

H4 now have 201 point count and need x2 size (64kB)

But yes total size 256kB, and firmware size at this moment ~80kB, it allow add additional slots (for H version can`t)
============================================
One of the reasons I purchased the H4, in addition to its larger display size, was its additional flash memory and faster processor. I was hoping it would allow many more enhancements, like the current 201 point beta firmware, before flash memory space became a concern. I can now see that certain enhancements can consume the free ~176kB pretty quickly.

Is support for the un-populated flash memory card already enabled or will that also require some of the free ~176kB?


 

On Wed, Apr 15, 2020 at 06:24 AM, hwalker wrote:


§±§à§Õ§Õ§Ö§â§Ø§Ü§Ñ §ß§Ö§Ù§Ñ§ß§ñ§ä§à§Û §Ü§Ñ§â§ä§í §æ§Ý§ï§ê-§á§Ñ§Þ§ñ§ä§Ú §å§Ø§Ö
§Ó§Ü§Ý§ð§é§Ö§ß§Ñ §Ú§Ý§Ú §Õ§Ý§ñ §ß§Ö§Ö §ä§Ñ§Ü§Ø§Ö §á§à§ä§â§Ö§Ò§å§Ö§ä§ã§ñ
§é§Ñ§ã§ä§î ~ 176 §¬§¢?
I port H version to H4, no support SD cart in H, but not big problem add it. ( then i test FAT32 support in arduino, it not need big amount flash space).
In most cases big amount of flash need for images, texts and UI. In H4 version exist ~112kB free flash space, and ~30kB RAM. But if use next ChibiOS 18 (as in release it require more flash and ram for work).

I show easy way for increase calibration slot amount, need just optimize properties struct size, but answer - use better CPU.
At this time i can`t work under code (at another town work under this , and need full day in work)


Pierre Martel
 

I once took a Tupolev airplane from Cubanair in mars 1995
I was going from Montreal Canada to Varadero Cuba.

I dont remember what model it was. But I was surprised about the brand.

Le mer. 15 avr. 2020 ¨¤ 12:56, DiSlord <dislordlive@...> a ¨¦crit :

On Wed, Apr 15, 2020 at 06:24 AM, hwalker wrote:


§±§à§Õ§Õ§Ö§â§Ø§Ü§Ñ §ß§Ö§Ù§Ñ§ß§ñ§ä§à§Û §Ü§Ñ§â§ä§í §æ§Ý§ï§ê-§á§Ñ§Þ§ñ§ä§Ú §å§Ø§Ö
§Ó§Ü§Ý§ð§é§Ö§ß§Ñ §Ú§Ý§Ú §Õ§Ý§ñ §ß§Ö§Ö §ä§Ñ§Ü§Ø§Ö §á§à§ä§â§Ö§Ò§å§Ö§ä§ã§ñ
§é§Ñ§ã§ä§î ~ 176 §¬§¢?
I port H version to H4, no support SD cart in H, but not big problem add
it. ( then i test FAT32 support in arduino, it not need big amount flash
space).
In most cases big amount of flash need for images, texts and UI. In H4
version exist ~112kB free flash space, and ~30kB RAM. But if use next
ChibiOS 18 (as in release it require more flash and ram for work).

I show easy way for increase calibration slot amount, need just optimize
properties struct size, but answer - use better CPU.
At this time i can`t work under code (at another town work under this
, and need full day in work)




 

On Wed, Apr 15, 2020 at 04:01 AM, Glen K4KV wrote:

... One big limitation for me is to be able to SAVE a scan for later download to a PC...

...The H4 was outstanding except for weak brightness outdoors.
========================================
Glen,
One possible solution to both problems is to connect the H4 to your cell phone using the NanoVNA android app when you are taking measurements outside. The phone's display is brighter and the android app will allow you to save the scan to s1p or s2p format for later use on a PC. It does mean one more cable and device, but most of us are tethered to our cellphones anyway.

- Herb


Glen K4KV
 

I have never tried using the Android phone.? I have brought the laptop out in the field to

run NanoSaver, not my preferred method.

Thanks Herb

73

Glen K4KV

On 4/15/2020 16:46, hwalker wrote:
On Wed, Apr 15, 2020 at 04:01 AM, Glen K4KV wrote:

... One big limitation for me is to be able to SAVE a scan for later download to a PC...

...The H4 was outstanding except for weak brightness outdoors.
========================================
Glen,
One possible solution to both problems is to connect the H4 to your cell phone using the NanoVNA android app when you are taking measurements outside. The phone's display is brighter and the android app will allow you to save the scan to s1p or s2p format for later use on a PC. It does mean one more cable and device, but most of us are tethered to our cellphones anyway.

- Herb



 

Create firmware for H4 device, remove frequency table from properties struct, rebuild this table on load properties

It allow reduce properties size (on 201 points) from 0x3000 to 0x2000 (8kB for one slot), and allow save in last 64kB flash 7 calibration config slots (5 before) + one config slot

For H device, this not help (need reduce size more, at 40 bytes).