SGPro 220.127.116.11 is a beta release (actually it is all of the changes from 18.104.22.168 through 22.214.171.124 wrapped up in a single installer). While we love that folks help us test, make sure you are a fairly knowledgeable SGPro user before hopping onto the beta track.
- Fixed an issue where PHD2 profile gear would nor reconnect after resetting and re-running the sequence.
- Better detection of external disconnect in focuser and telescope
- Instrumenting some problematic end of sequence code
- Fixing a potential issue where failure to determine flat box shutter state could cause the sequence to hang.
- Failure to change the filter during a solve and sync action will now properly abort the sequence.
- More trace logging to analyze issue where SGPro UI can hang at sequence end.
- More trace logging to ASCOM mount park.
- Possible automatic registration of comdlg32.ocx on install (for PlateSolve2). This is a blind attempt at fixing the issue.
- MFW now understands how to find stars (HIP catalog) from SIMBAD
- Fixed the issue where SGPro would clobber old sequences
- More trace logging to find mysterious crash / hang that can happen for certain folks at random times.
- Easier setup for Astrometry.NET / ANSVR URL setup. You can now choose human friendly points like “Astrometry.NET (Remote)” or “ANSVR (Local Astrometry.NET) -> Assumes port 8080” and SGPro will figure out what you mean. The field will also continue to accept actual URLs also (this is good if you are not running ANSVR on port 8080 or for any other reason really…)
- More logging for successful Astrometry.NET solves.
- Forcing FLI camera settle time for transition from normal to high speed.
- Added “Fast Event Entry” feature
- Removing debug code that broke Nikon cameras when “Auto Connect” was not used.
- Better logging for an image save failure that can occur (not a fix).
- Fixed a bug that could cause a profile application to an existing sequence to fail if the user marked a filter as inactive.
- Updating the SGPro API in support of possible PemPro integration (general bug fixes)
- Moving back to the “zip” download format so Firefox users won’t be so confused.
- Fixed a possible lockup on abort condition for the camera.
- Fixed an issue where the camera might be left in an invalid state after abort.
- Sequence and target end times are now checked during the settle process
- Sequence end time now properly considers the length of the exposure it is about to begin
- Updating minimum usable version of PHD2 to 2.6.0
- Adding support for the Nikon 7200
- Increasing the max event repeat count to 999
- Moved between frame delay to be after the dither event (again)
- Small change to the guider interface that uses a check box to toggle the option to wait for the guider to settle over a period of time. You used to have to type in 0 seconds to turn this off. If your guider supports distance reporting, providing a minimum settle value is still required for dithering operations. This should be a more intuitive way to enable or disable the option when SGPro yells at you after trying to start a sequence. If you keep a non-zero value in this field, make sure to turn it on in your profiles!!!
- The default time to wait for the guider to settle over a period of time is now 10 seconds.
- Started work on “Smart Dithering”. Moved dithering event to the beginning of the current frame instead of the end of the last frame. Here is has a whole host of information with which to make smart choices about whether or not to dither. Dither is no longer performed after flips or target centering. Code for smarter dither on event rotation sequences is not yet available.
- Blocking calls to move the focuser now have a watch dog timer (5 minutes). This will prevent situations where the focuser can bite it so badly that it never returns control to SGPro (and thus never runs any end of sequence options). The need for this protection is very rare.
- Did some work on better handling ASCOM cameras that do not support aborting an exposure. Exposure will finish normally, data from the camera will not be provided (like a normal abort).
- Reducing environment device data poll to 30 sec from 10 sec.
- Removed all pressure based warnings.
- Temperature based warnings will only be issued when a downward trend can be confirmed.
- SGPro will only attempt to calculate trends after ~20 minutes of data has been collected.
- SGPro no longer issues any type of dialog based warning from environment based conditions.
- SGPro no longer issues any warnings from environment based conditions outside of a running sequence.
- Failure to initialize the monitoring system will no longer allow the sequence to start.
- Fixed a timing error that could very rarely cause auto focus to fail
- Fixed an issue where the Environment Device “Pressure” label could be set to NA
- The new “Environment Device” has its first usable implementation (and also the ASCOM 6.2 Observing Conditions Interface). See here for more details: Initial Implementation of ASCOM ObservingConditions
- Removed TEMPerHUM graphs
- Added TEMPerHUM as an Environment device (just so there is no confusion… it is still our stance that support for TEMPerHUM devices is discontinued, but if it works for you… feel free to use it)
- Fixed a bug with Canon Mirror Lock.
- Fixed a bug that would not allow Atik cameras to cool down on connect.
- Fixed a bug that could prompt for manual flat box placement at the end of a sequence.
- Added code that attempts to block the sequence from continuing while the scope parks (no guarantees here)… just more likely that your scope will be fully parked before any further actions are taken.
- Fixed a bug where the Target Settings dialog could no longer blind solve without RA and DEC hints