Getting exposure time into project

[theskyhound]

Hello Roy,

I appreciate your patience. There is definitely something very wrong with that OIII filter. The SNR numbers in the preview really don't make sense.

One thing: the only way to be absolutely certain that the changes made to the imaging system were seen by the Scheduler is to navigate away from the Scheduler tab by selecting a different tab, and then come back. Clear any existing schedule and try schedule again. Please try that and let me know if it is still misbehaving.

If it is still not working properly, the best way to proceed is to send me your imaging system so I can test it directly. To do that, open the Imaging Systems dialog, select your system, and click the Save button. This will create a .stx file that you can share with me by uploading it here.

[Mystic Hill]

Greg,

Thanks for sticking with me on this. I am learning this part of the program at the while trying to understand what it is doing for me.

I am becoming quite the expert at clearing schedules and rescheduling. One reason is the date fails to keep up with me and I have to change the day and start over.

This time I played with scheduling multiple imaging projects for the same night. I think I get it now. I still could not make the OIII event at 00:41:40 display properly with a non-zero exposure time. I still think it has something to do with the Imaging Project's Exposure Goal for Sub exposures being set to "Auto". My other projects are forced to 1 minute.

Please see Schedule information screenshot and stx file.

Roy

---

Greg,

Since it was cloudy tonight, I went and made sure the first three imaging projects were set to Auto sub exposures.  This created more squirrelly times for some filters as seen in the screenshot (attached).  for these events the scheduled exposure times are zero.

Roy

[theskyhound]

Thanks for the uploads. I will get back to you as soon as I figure it out.

[theskyhound]

Hello Roy,

I tried loading your .stx file into my personal copy of SkyTools and it failed. But when I loaded it with the debugger running in my development copy it worked fine. Sometimes the debugger can mask some kinds of faults. I'm still looking into that, but it may be a clue.

Anyhow, I looked over your settings and all seems good. I just have one question: there is on one available sub exposure time (60 sec). Is that they way it was when it failed, or did you change that to get it to work? If it failed with different allowed exposure time settings in the Imaging System setup, what were they?