I'm quite new using PI4 and astroberry and I appreciate the the general philosophy of this solution (PI gadget + open software).
By the way I wanted to use the scheduler to have an automated solution (all the rig is in the garden) and capture images during the week without waiting all the night long.
My first attempts are frustrating me since every night something is going wrong. 
For instance, this night I schedule a first sequence on NGC3628 (hamburger galaxy) from 10pm to 2am (I have trees in my neighbour's  garden) and then a second  sequence from 2am to 5am on M64.
For each sequence I wanted to use a LUM filter and an IRpass Filter (it's a test to avoid light pollution). So my sequence was 12 images with Lum + 12 images with IRpass repeated for 2 runs.
This morning I have 12 Lum images, and 11 IRpass images. Just before the 12th IRpass image, the mount do the meridian flip (all is correct) and the guiding hangs and never resumes...  The mount waits until 5am and then parks! The second sequence never starts.
So, what should be the best strategy to be sure that after an error or perhaps x minutes without any image captured (This night I have no error, just the capture module waiting for guiding!)  to skip current sequence and go to the next one? 

Thanks for your help 



 

What was the reason that guiding hangs? Does it really hang or does each starting attempt fail?

The Scheduler has an error strategy, but it handles only the cases when aligning, capturing etc. really fail. As long as the Capture module waits for guiding to start, the Scheduler does not step in and might leave the Capture module wait for ever.

In any cast: it would be great if you provide a log file of last night.

HTH
Wolfgang

I recognize the issue you ran into. I have not much to add other than that I know it is being worked on.

As a stop-gap intended for observatories that can close a roof or shutter I wrote a small python program Ekos-Sentinel.py that can park and close the roof in case of emergency (like rain or mains power is out and UPS battery is about to die) when EKOS does not handle it because it is stuck, or waiting for something, or just crashed.
You can find it at github.com/d33psky/rolloffroof/blob/mast...kos/ekos_sentinel.py
This does not fix your second-schedule-does-not-start though.

-- Hans

I do not have Logs. I will try this night. But in guiding console (still opened this moring) I can't see any error message. 
This is a copy of the Analyse Tab
 
After 2 sequences and Flip non more guiding and capture.
 

Thanks Hans
My only security problem is ti stop motors in the morning.
To be sure everything is stopped at 6am I use this !
 

Joe