To differentiate the code I was experimenting with yesterday, from the source I was starting with I added the date to the end of the file name… Mar1, and followed that with an A, thinking that I might need to “reset” a few times in order to try different things, and a tailing alpha gives me an easy way to differentiate and gauge how well different solutions work.

Adding the sequence Mar1a to the file name really played with my head, as even though I knew what it said I kept reading it as the name “Marla”, and by the end of it, when I saw that my data was finally posting to both the LCD and the internet I was already referring to my transition to the updated code as “the Marla Upgrade”… I can’t believe that I’ve geeked out enough, while working on this that I am now naming my software builds… Actually thinking about it a little more, “Marla” makes for a pretty snazzy name for the O/S itself. Done! That has just been decided,

Incidentally, Marla appears to be mostly stable.
I was going to say that I had looked over approximately 4 hours of uploaded data, and I don’t see any interruptions in the flow of information that would indicate a crash/reset… however I just noticed that my LCD is static… and the timestamp on the spreadsheet is 5:01am (+33min adjustment)… meaning it crashed at 5:34. Unfortunately the serial monitor was not connected to it, so I don’t have any info to use for debugging. (I wanted to give the Colonel a “field test” without any possible outside influences… like the power that would be coming into the NodeMCU via the USB cable.

I tapped the reset button, and everything seems to be fine now… I’m going to move ahead with coding the scheduler for the Uno.