¿ªÔÆÌåÓý

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

Firmware font size - 2 versus 4 trace


 

I like the new 1500 MHz firmware - but I do miss the larger font size of the original 2 trace "antenna analyzer" version my nanoVNA shipped with. Wondering if there is some inherent reason why the larger font can't be used with 4 trace firmware, other than the screen getting too crowded with text.


 

Erik,
Is there enough firmware space on the uP for one more firmware on-screen option to display either 2 larger or 4 smaller traces?
I think that would be a nice option to have.
I know Hugen's firmware for the 2 trace version was quite a bit larger in size though.

Thanks,
Larry

On Wed, Sep 25, 2019 at 08:24 AM, Bruce KX4AZ wrote:

I like the new 1500 MHz firmware - but I do miss the larger font size of the
original 2 trace "antenna analyzer" version my nanoVNA shipped with.
Wondering if there is some inherent reason why the larger font can't be used
with 4 trace firmware, other than the screen getting too crowded with text.


 

Indeed, larger fonts need more memory. Prefer to spend memory on more useful features. Suggest to buy small reading glasses. I did.....
Hugen does not have the large font size version on github (I can not find it) and I'm using the edy555 version as a starting point


 

On Wed, Sep 25, 2019 at 09:26 AM, <erik@...> wrote:


Indeed, larger fonts need more memory. Prefer to spend memory on more useful
features.
Erik,
Thanks for confirming memory capacity is a factor in the font sizes. My progressive bifocals work fine with the smaller fonts, but I imagine it's just a matter of time before someone releases a new firmware "flavor" with two traces & 1500 MHz extended range.

With the newest firmware versions, can you give us any sense of how close we are the memory capacity "ceiling"?
Thanks,
Bruce


 

There are two flash parts, one 96k and one 32k
Assuming the 32k flash holds the data store (did not analyze yet), the 96kByte flash has maybe 1kByte left. (code + initialized data is in total 97440 Bytes)
But I am not very familiar with the memory layout


 

I have seen a technique where the font is "enlarged" simply by outputting each scan of the character font twice. This makes the character appear taller. It can make the text surprisingly more legible with no more font RAM and just a small hit on the code space. Of course you still will need screen space. Because the characters, while more legible, are a bit ill formed, this might be available as an selectable "ZOOM" mode unneeded by those who purchase the reading glass option.