On sequence start with autoflats (sky flats) before sequence:
the camera does not start cooling at the beginning of autoflats
the equipment connects, but the dome does not open and rotates to the right position
when manually selected “slave to telescope”, autoflats does not wait for the dome to rotate, and begins to mesure explosure on wrongly rotated dome
when I try to abort autoflat sequence, the confirm button “yes” does abort autoflats sequence, but does not abort whole sequence (it does the same like the button “cancel”)
This warnings (see up) I get every time I start the sequence with autoflats enabled, even if I set min. time to 1s and max. time to 60s. I get it 2 times when I have the Autoflats scheduler set for before and after sequence start (see picture).
The autoflats sort order “Narrowband toward light” is great, but it would be better if default order will be L, B, G, R, OIII, SII, Ha in the morning, and reverse order at evening. Also it would be fine if the autoflat sequence will not stop after error “Maximum/Minimum exposure length violation was detected”, but try to continue on next filter.
Those warnings are not related to min and max exposure lengths. They refer to the fact that the filter used in the flat events do not have a default flats time defined and that AutoFlats was unable to locate any other data that might inform it of a proper exposure (to start with).
See about half way down to set the defaults for your filters:
I have been troubleshooting the issue where the observatory is still moving when AutoFlats starts and I just dont have enough information in the logs to come to any particular conclusion. By all accounts, all of the code to properly wait for both scope and observatory to complete slew is in place. The next beta won’t attempt to fix this issue, but if you could attempt to recreate it, I hope to have enough info in the logs to pinpoint what is failing. The failure is occuring in SGPro or in the driver reporting that it is done slewing too early. In this early state of AutoFlats, it is likely an issue in SGPro, but I can’t see where just yet.
I confirm, that in version 4.3.0.1108 this was fixed.
I could not test “Fixed the “Run / Cancel” button being disabled forever.”, because I had not enough time.
I thing that at the begining of sequence with AutoFlats enabled, the mount is sleewing without unparking the mount, because even I set the “Mount Unpark Opens Shutter”, the shutter is not opened and slaved to telescope.
can’t start AutoFlats (Flat Frame Cature Tool) window, even after restarting SGP
minimum exposure can not be set below 1 sec. (in preview before, preview after, scheduler and possibly also in AutoFlats (Flat Frame Cature Tool))
AutoFlats scheduler and preview mode not match (or not clear how this two depend on each other)
AutoFlats in preview mode after “reset” (removing all flat events) and “Add Flat Event” the number of capture frame per event don’t match with the “Frames per event” in preview or scheduler
there are four places where AutoFlats settings can be set (in preview before, preview after, scheduler and AutoFlats (Flat Frame Cature Tool)) - and it seems that some of that are independent from the others which is a litle confusing, may be the documentatatin will explain this
I dont know what you mean here. You literally cant open the AutoFlats window? Can you include logs and let me know at what time you tried to open it?
This is likely because you are referring to the “default” number of flat frames that AutoFlats will use if it is unable to acquire an override value from the filter’s settings. See the section titles Flats Dialog.
I’ll work on clarifying this… For now: There are only two areas that matter.
The standalone AutoFlats tool is wholly independent of any sequence, but still uses values found in the equipment profile. Any changes made here will be saved with the sequence, but when AutoFlats is used as part of a sequence, this data is not considered (unless you have directed the sequence to use the “Custom Sequence” here):
The only other area that matters is the AutoFlats scheduler. Data here is used when AutoFlats is run in conjunction with the sequence.
Any changes made to AutoFlats form values in either before or after previews are completely ignored. These are read-only displays that show what AutoFlats will do when it runs as part of the sequence and nothing else. I will work on making this clearer.
Maybe I am misunderstanding… I think you are in Germany or nearby? I’m wondering if it’s maybe a localization issue with the decimal separator?
Thanks for explanation. It would be fine, that the before and after previews would be really read-only. I mean that the user should be unable to give here any input or change anything.
still on sequence start the dome is not opening and set to slave to telescope (link to log below)
it would be fine to have the posibility to pause the Auto Flats sequence to change some settings and then continue to take flats
still when maximum/minimum exposure is reached, the Autoflats sequence is aborted instead of trying to continue on next filter
when taking before Auto Flats on narrowband filters and then coninuing on RGB filters and there is still too much light, the sequence should enter a wait state to wait for better conditions for sky flats for RGB filters
It’s a mystery. I wonder if it’s related to the other issue I just fixed. Let me know. In any case, here is the minimum exposure after I completely restarted SGPro and then open the custom AutoFlats sequence:
I think I have this one figured out. The hour angle was zeroed out before the slaving started.
Right now AutoFlats only does this check at the start of the sequence. I’ll look at moving this functionality into the parts that run between events instead.
I have this corrected also.
Of all the things you’ve reported, this will be the most difficult to address. Will need to think about what’s happening here…
The reason for the crash remains unclear, but the root cause of the issue is that SGPro
Did not force shutdown actions when a sequence ended normally (only when a sequence was terminated early)
Failed to clear a safety timer that will force end of sequence actions to finish running if some part of the rig becomes unresponsive.
