For those who are? concerned with amount of memory used, there are "Conditional Compile Options" that can be used to switch on or switch off compilations based on #define. This lets you select which options you want to compile by commenting out or adding certain triggers in your code.? If memory size is not a concern it might be possible to include user configuration options for things like 2-Line LCD, 4-Line LCD, and so on up to graphics displays allowing user to have boot-up options for selecting hardware configuration, software configuration, and function configuration as three separate menu lists.? Of course all firmware in source code format assumes that the builder/user will have knowledge and equipment to compile and install his/her own code.? Not all have that ability.? Solution to that might be an on-line tutorial describing step-by-step procedure for installing the IDE, obtaining the source code, compiling source, and installing the resulting .hex files.? Maybe this could be included in build instructions and/or at .? Doing this would mean that the instruction would need to be verified usable for Linux, Windows, and Mac-OSX.? For those who do not want to download and install the Arduino IDE and do not want to use some other IDE for compiling BITX code, there is an on-line compiler available at .? This lets you write and compile your own code using a web browser on a PC or cell-phone. Arv _._ On Mon, May 14, 2018 at 10:53 AM, Michael Babineau <mbabineau.ve3wmb@...> wrote: I agree with K9ZC.? The easiest way to free up code space in the Nano is to use conditional compilation for "optional" features that not everyone wants. |