There should be some high level documentation of what's happening in the system and what you should expect to see at every stage. This would be useful, not only to be able to hand off to some one else, but also as a general resource to help someone understand how the system should behave and respond under different circumstances.
Even for now, something simple thing like the following could be helpful:
Bootloader starts:
Powers NC on failsafe media if early NC power flag enabled.
Start setup process.
Setup process:
Get and clear boot flags.
Enable reset the watchdog.
Setup persistant records.
Setup hardware / sensors.
Update boot time and counts.
Setup device states.
Start main process.
Main process:
Start next device, if start timer expired.
Update device processes.
Process commands.
Send logs every 60 seconds.
Reset system, if reset requested.
Reset watchdog.
Device process (normal operation):
...will add more...
Device process (failsafe operation / 30+ failures):
Every 4 hours, the device is killed and then started on its other boot media.
Heartbeat process:
A background heartbeat check is run on a timer in the background. It checks if the last read state of a heartbeat pin has changed, and if so, it increments that pins changed counter. The devices later check if this change count is above a certain threshold and if so, trigger a heartbeat event.
There should be some high level documentation of what's happening in the system and what you should expect to see at every stage. This would be useful, not only to be able to hand off to some one else, but also as a general resource to help someone understand how the system should behave and respond under different circumstances.
Even for now, something simple thing like the following could be helpful:
Bootloader starts:
Setup process:
Main process:
Device process (normal operation): ...will add more...
Device process (failsafe operation / 30+ failures): Every 4 hours, the device is killed and then started on its other boot media.
Heartbeat process: A background heartbeat check is run on a timer in the background. It checks if the last read state of a heartbeat pin has changed, and if so, it increments that pins changed counter. The devices later check if this change count is above a certain threshold and if so, trigger a heartbeat event.