Reactive targeting centering change: Because use of this setting requires plate solving and solving images can take several minutes (sometimes), SGPro does not wait for the location delta calculation to complete before starting the next frame. This, of course, means that the even can fire during integration of the next frame. Because of this, there is now a setting that will allow you to react passively or actively to a location error event. The default is to act passively and, without aborting the current frame (because its data is likely still usable), conduct a centering operation after the completion of the current frame. Alternatively, you can opt to react immediately and, upon firing the event, SGPro will discard the current frame, recenter and then restart it.
Observatory telescope-slave settings have been moved directly into the control panel (because there is actually room now)
The old “Slave to telescope” checkbox settings has been removed and replaced by a toggle switch. This setting is no longer savable! It represents a state of being (see item below) and not a setting. If you want to automate slaving the observatory to the telescope, you’ll want to choose one of the 2 auto-slave options:
Because slaving the observatory has several requirements that must be met, the toggle switch can be interpreted as a state, but in some cases as a “promise”. If a pre-requisite for slaving is not met, it will be displayed in detail to the right so it can be corrected. The observatory will continue to attempt to slave to the telescope as long as the toggle switch is to the right.
To be consistent with other Control Panel tabs, the observatory control items are now grouped at the top and those controls oriented toward governing sequence behavior are below it.
Updated the settings search index to include several missing settings.
Fixed an issue where the Flats Calibration Issue could not be closed.
Fixed an issue where periodic and reactive recentering events would not automatically pause the autoguider before starting.
With respect to several today / tomorrow labels for end times, the UI now shows the expected next occurrence and no longer shows the label for the internally held SGPro date.
Sequence and target end today / tomorrow labels also now update in real time as the persistence of time imposes its will.
Fixed an issue where shortcuts into specific areas of the Control Panel would open the correct tab, but its corresponding tab in the new tab list would not be selected.
Fixed an issue where the parking related buttons on the docking module were permanently disabled.
Fixed an issue where a sequence end time may be adjusted such that it is in the past and terminate the sequence immediately.
Known Issues:
Have not looked into making resizing windows from the bottom edge issues yet (only when the window has a status bar).
There is an issue in the new Equipment Profile Manager that, upon delete of a profile, causes the remaining profiles to disappear. Looking into this, but cannot recreate this issue so far…
It does not work, if it says 00:00 or 05:10 “Today” the imaging sequence ends straight away
[11/10/24 19:47:46.809][DEBUG][Sequence Thread][SQ;] Current target has end time at 10/11/2024 19:58:00
[11/10/24 19:47:46.809][DEBUG][Sequence Thread][SQ;] End time of next frame is at 10/11/2024 19:52:46
[11/10/24 19:47:46.809][DEBUG][Sequence Thread][SQ;] Target is still before end time, continuing...
[11/10/24 19:47:46.809][DEBUG][Sequence Thread][SQ;] Sequence has end time at 10/11/2024 00:00:00
[11/10/24 19:47:46.809][DEBUG][Sequence Thread][SQ;] Target past specified sequence end time, ending sequence...
1455 is not setting the Eagle “Switch” ports to the desired state at the end of the sequence despite the values being set
Also
How does this affect RoR? In previous versions it would slave to the mount and ensure the mount was “Parked” before closing the roof, now I see that Slaving is Enabled but not active because it is expcting a Dome
Just downloaded 4.5.0.1456 and I find that the Framing & Mosaic Wizard window now opens and closes properly.
In testing the parking related buttons it appears they still are disabled. Upon connecting the mount the module shows “Park” and should be showing “Unpark”. After a slew with mount tracking, pressing “Park” has no effect.
Finally got around to some quick indoor testing of 4.5.0.1456 and can confirm:
the “Park” and “Set Park” are now available to click and do function, for my set up anyway, to both “Unpark” and “Park” the mount, after a slew with mount tracking. However, when the mount is parked the button text does still state “Park” instead of “Unpark”
the docking modules option button (down triangle in top right of the module next to the “x”) now opens the correct section in the control panel, regardless of the currently selected section
Apologies, but I cannot seem to attach the log file to this thread, but have added an extract from the log that shows it all works fine, regarding the “Park” and “Unpark” functionality of the button.
It is just the text on the button that should read “Unpark” when the mount is in a parked state.
Are you certain about this? In 1456? As of 1445, these buttons (in the docking module) are literally enabled 100% of the time. They are now even enabled if the mount is not connected or if the mount does not support park. There should be no code, whatsoever to enable / disable these buttons any longer. Maybe some series of actions I am unaware of?
This I was able to confirm and fix. Thx.
Did the mount report finishing the slew? What does the control panel report here?
We may be able to look at this again. It’s something we have considered before but previous attempts failed because “downloading” was not an official state of an ASCOM camera. As such SGPro did not not have certainty that the camera was done and risk streaking the image in the very last milliseconds (and we pilled a bunch). We tried several implied “is camera actually done” things like only calling dither after we request the data, but this, we learned, is not a gurantee that the camera is done and may just “pause” the request for data until it is done.
In any case, it is an official status of an ASCOM camera now and may warrant a re-look
Confirmed 1456. After a slew the “Park” does indeed park the mount. My confusion is the same as MStringfield in that should read “Unpark” when the mount is in a parked state.
in some cases a second Button could be fine [Home] [Set Home] because some mounts have this option, like my ZWO AM5 mount. Home and Park position are different!
Home Position = to Polaris
Park Position = horizontal
@Ken I can confirm tonight it did the same thing, I selected “Abort Sequence” with the End of Sequence options selected, everything went accordingly, Park, roof close, camera warm up, disconnect equipment, but the Eagle Switch State was not changed, all ports remained powered on, and the USB ports remained on also. In the logs I do not see anything that stands out, I can see the request go through and then this line:
[11/20/24 20:49:40.364][DEBUG][Main Thread][NONE] Adding sequence level notification: End of sequence actions completed and end of sequence switch state has been set.
[11/20/24 20:49:40.381][DEBUG][Unknown][NONE] Sending Notification: Status - End of sequence actions completed and end of sequence switch state has been set.
[11/20/24 20:49:53.855][DEBUG][Main Thread][NONE] PopulateDataModel: await serialization lock...
[11/20/24 20:49:53.855][DEBUG][Main Thread][NONE] PopulateDataModel: Transferring view to the data model...
[11/20/24 20:49:53.855][DEBUG][Main Thread][NONE] Generate external switch cache for ASCOM.EagleSwitch.Switch...
But then…
[11/20/24 20:49:53.856][DEBUG][Main Thread][NONE] Failed to repair cache switch value state, continuing : Value cannot be null.
Parameter name: source
at System.Linq.Enumerable.Where[TSource](IEnumerable`1 source, Func`2 predicate)
at jz.cj(EquipmentProfile A_0)
