I don't really need any logging function (though I might in the future). So I was thinking of just hard-coding the events into the code rather than a text file.
The idea was to use the logging disk not for logging but its disk as carrier for a file with times and actions.
This way you can update the clock without creating a new executable - anybody could update the textfile on a PC.
By using the disk for events you can in theory have an action for every second of the day (86400 sec/day) thereby
extending the capabilities of the Arduino beyond its internal memory ![]()
Furthermore by placing the times/actions and text on an external memory you have more flash memory free for functional code to implement different actions!