markusb68 wrote:Yes, these lines do activate the RTC and set the system clock.
They don't give errors executed manually and all is working fine now.
I just have to keep them below the "RASPIMJPEG SECTION" after the next update.
I'm wondering if I could use the Scheduler to activate timelapse full-res picture capture on a sun-based schedule.
But can't figure out a way to set it up. It looks to me as the Scheduler is just for motion capture (video).
The scheduler is fairly general purpose and not constrained to motion capture video.
Any sequence of the supported commands can be put into the motion start, motion stop, and period start fields. This can include changing camera settings, taking still images, videos, or controlling time lapse sequences.
Motion Start and Motion Stop commands get executed whenever a trigger (1=Start, 0=Stop) get entered into the scheduler FIFO1. Normally these would come from the motion detection logic but can come from anywhere (e.g. PIR motion detectors, door triggers etc).
The Period Start commands get executed whenever a period change is detected. In All Day mode there is only one set, but time based and Sun based allow different commands at different periods of the day. In a lot of cases these are used to determine what camera settings to use or whether to enable motion detection, but they can be used for anything. So for example, a time lapse sequence could be started at the beginning of a period and terminated at the next period start.
For additional flexibility one can use the Management command facility of the scheduler. Any commands here are periodically run at the Management interval. Typically one would use a sy command to execute a macro periodically that could do whatever logic was required and in turn issue further commands back to the command queue FIFO to initiate, image, video and time lapse operations.