SGPro 4.5.0.1456 Public Alpha Available for Test

Last target end time was ignored, I have a target that was set as an end time of 10:52, but the sequence ended early at 05:22 with a reason of “Target Marked as Past of End Time: True”

[11/22/24 05:22:08.799][DEBUG][Sequence Thread][SQ;] Current start time 22/11/2024 04:28:00)
[11/22/24 05:22:08.799][DEBUG][Sequence Thread][SQ;] New start time 22/11/2024 04:28:00)
[11/22/24 05:22:08.799][DEBUG][Sequence Thread][SQ;] M81 and M82 - End time has altitude lock, calculating end time for 51.9
[11/22/24 05:22:08.799][DEBUG][Sequence Thread][SQ;] Transit data -> nt: 05:52:25; ot: 05:52:25
[11/22/24 05:22:08.799][DEBUG][Sequence Thread][SQ;] Transit delta -> 0 seconds (nt: 1.05:52:25; ot: 1.05:52:25)
[11/22/24 05:22:08.799][DEBUG][Sequence Thread][SQ;] Adjusting end time by 0 seconds...
[11/22/24 05:22:08.799][DEBUG][Sequence Thread][SQ;] Current end time 21/11/2024 10:52:00)
[11/22/24 05:22:08.799][DEBUG][Sequence Thread][SQ;] New end time 21/11/2024 10:52:00)
[11/22/24 05:22:08.799][DEBUG][Sequence Thread][SQ;] Looking at event[0]...
[11/22/24 05:22:08.799][DEBUG][Sequence Thread][SQ;] Found event event[0] with remaining frames.
[11/22/24 05:22:08.799][DEBUG][Sequence Thread][SQ;] Event[0] frame count: 0/151...
[11/22/24 05:22:08.799][DEBUG][Sequence Thread][SQ;] Target is active: True
[11/22/24 05:22:08.799][DEBUG][Sequence Thread][SQ;] Target is complete: False
[11/22/24 05:22:08.799][DEBUG][Sequence Thread][SQ;] Target marked as past end time: True
[11/22/24 05:22:08.799][DEBUG][Sequence Thread][SQ;] Target has end time: True
[11/22/24 05:22:08.799][DEBUG][Sequence Thread][SQ;] Target end time: 21/11/2024 10:52:00
[11/22/24 05:22:08.799][DEBUG][Sequence Thread][SQ;] Sequence complete.
[11/22/24 05:22:08.799][DEBUG][Sequence Thread][SQ;] No valid targets remain, aborting...
[11/22/24 05:22:08.799][DEBUG][Sequence Thread][SQ;] ********* Run post sequence *********
[11/22/24 05:22:08.799][DEBUG][Sequence Thread][SQ;] RunPostSequence=>EndReason is set: Complete

That last error is just something I need to remove. It’s not related to this issue. Are you using the eagle ASCOM drivers are the Eagle native drivers for these switches?

The scenario here is not clear to me. Logs may help… Is it that you are trying to leave the sequence running during the day and just start up or something else?

No, the sequence end time was 05:50, but it stopped at 05:22 stating that the last target end time had passed, which it had not, as the end time was 10:52, you can see it here:

[11/22/24 05:22:08.799][DEBUG][Sequence Thread][SQ;] Target is active: True
[11/22/24 05:22:08.799][DEBUG][Sequence Thread][SQ;] Target is complete: False
[11/22/24 05:22:08.799][DEBUG][Sequence Thread][SQ;] Target marked as past end time: True
[11/22/24 05:22:08.799][DEBUG][Sequence Thread][SQ;] Target has end time: True
[11/22/24 05:22:08.799][DEBUG][Sequence Thread][SQ;] Target end time: 21/11/2024 10:52:00
[11/22/24 05:22:08.799][DEBUG][Sequence Thread][SQ;] Sequence complete.

ASCOM drivers. I can produce this on demand, it seems that if you abort the sequence with end of sequence options selected, all the end of sequence options run perfectly except for setting the switch state. Allowing the sequence to end “Normally” sets the switch state as expected

To be clear, you are saying that, when a sequence ends normally of its own accord, end of sequence switch state does run?

Yes indeed, it is only when you manually abort the sequence with end of sequence options selected that it does not. I have not tested an automated abort sequence yet though

Do you have a camera warmup included in end of sequence options? If so, it’s worth noting that end of sequence switch state will not happen until after warmup completes.

Yes, and when an imaging sequence ends “Naturally” the Switch State changes happen as expected. But when you cancel a sequence, end of sequence options run, which includes camera warm up, but the expected behaviour of changing the switch state after the camera warm up completes does not happen.

I’m unsure. I was able to simulate this scenario without issue:

  • Mount parks
  • Camera finishes cooling
  • Switch state set

I did add additional logging though.

Ok… I think I am going to shut the alpha down and move SGPro 4.5 into beta.

Thank you all very much for helping with 4.5’s very early state.

Note: This is not to say that all the things you identified in the various alpha builds are corrected, just that it seems generally stable enough to enter beta.

Ken,

Will the Beta show up here or where will I need to look?

SGPro 4.5 has moved onto the normal beta release track and can be found there. Here is the latest:

Sequence Generator Pro 4.5.0.1460 (BETA) is Released for Test - Releases - Main Sequence Software

Ken,

Just installed the BETA and entered Equipment Profile Manager to delete the 3 installed profiles, (Cannon template, LRGB template and NB template). Upon selecting any of these profiles I get the below message:

image

When selecting OK

and then deleting the profile:

Then upon closing and reentering Equipment Profile Manager:
image

Selecting OK:

The remaining Profiles are intact, minus the one deleted.

All of my Profiles open properly.

Hi

I am seeing the same thing ?

Regards

Harry

I’ll get it taken care of in the near future. For now, it’s safe to ignore

I also got the equipment profiles issue

Ok, so with respect to these 3 starter profiles, I have gone ahead and removed them for now. The issue here is that the profiles do not conform to new standards in SGPro 4.5. While it would be easy enough to update them, I think that when I have time (which is not right now), I will make install of these profiles an installer option instead of a default option.

So, for those of you who delete these every time, you should no longer need to do this…

Thanks Ken. An installation option would be better.

Any idea how many people use them? If not a “lot”, maybe they could be a separate download, like the SBIG built-in guide chip software.