search

ttrftech / NanoVNA

Very Tiny Palmtop Vector Network Analyzer
1.06k stars 297 forks source link

Use 1 16bit word to define firmware capabilities - ENHANCEMENT REQ #88

Open nlroth opened 4 years ago

nlroth commented 4 years ago

Is it possible for the 4-5 main developers of the various NanoVNA firmware flavours to agree on a simple identification word that would be included in the VERSION console command? This single 16bit word would be able to identify the presence (or absence) of up to 32 items. There could be more items defined if sub-bits are used in a binary counting fashion. For example: Bit 0 can be a 0 or 1 to define the presence of a feature Bits 1, 2 & 3 would allow 8 sub-levels of the preceding feature.

The problem is not in defining the table, bit it is having the table implemented and followed by the various NanoVNA firmware developers.

Please refer to forum post https://groups.io/g/nanovna-users/message/5610 where I have attached an Excel sheet as an example.

This type of ID 'string' would be very helpful in the case of a Black Box version of the NanoVNA.

edy555 commented 4 years ago

Thanks for the proposal. I think that using strings of expressing features is better than a number of 16bit integers. I'd like to add a new command for that.

nlroth commented 4 years ago

QRP suggested using both the help and version commands to determine features.The drawback is ensuring the help command string is kept up to date as other modules are updated. Personally, I like to keep things simple (My 1977 SOL20 had 2K ram and 1K of that was the display - it is amazing what you can squeeze into 1K ram :-) )

On Thursday, October 24, 2019, 7:13:28 a.m. GMT-4, TT <notifications@github.com> wrote:

Thanks for the proposal. I think that using strings of expressing features is better than a number of 16bit integers. I'd like to add a new command for that.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.