Thank you Joe.
I'm a hardware engineer with some programming skills. I mean I can understand a piece of code unless it uses pointers to pointers referencing other pointers and tend to do things using simple for/while/if statements instead of #define code art.
Now I see that I can reserve 4K for the BL using fuses, which for me on 2560 is next to nothing. I would prefer reserving 16K for a bootloader instead of trying to optimize things, but 4K is the limit it seems.
Also all my nodes run wall powered for now, so power saving as long as it doesn't glow red hot it's nothing to bother for now.
I was contemplating having more networks, but it seems having a single one is simpler, still waiting for some parts from the far east to build more nodes and test rf crowding and rf separation for multiple networks running in the same space.
For now the plan is: the sketch sets the network parameters in EEPROM and the BL reads from there, tries to find a server/update, if available download and flash then boot. 2-3-5-10 second boot delay is not a problem either.
If it's possible just drop the code on me
of course after removing all sensitive security data.
If I can use it I'll let you all guys know, though it might get a little less readable after I do my things. For example I took the clickEncoder library and because it didn't work with multiple encoders I stripped all the classes, functions, unnecessary variables and fancy coding, it's reduced now to just two functions and works for me, but for somebody having input active high it's harder to find and change the code than it was in it's original form. I'm a little code barbarian so to speak.
Best wishes.
