Sequence Generator Pro Beta is Released for Testing


U P D A T E D   O N   D E C E M B E R   1 3 th,  2 0 1 7

Hi folks,

SGPro is a beta release. While we love that many of our users are eager to help us test, make sure you are a fairly knowledgeable SGPro user or have received explicit instructions by MSS staff before hopping onto the beta track.

Please note that this beta will expire in 45 days. There is no risk to installing it unless:

  • You do not intend to purchase SGPro 3.0
  • You will not have access to the internet when this beta expires (SGPro 2.X will continue to work for you)

MSS will always release new betas within the 45 day window. After the official release of SGPro 3.0, betas will not expire until the first SGPro 4.0 beta.

Please report beta issues here: SGPro 3.0.0.X Issue Thread Changes:

  • Support for Canon Digic 6 and 7 cameras
  • Native support for ZWO cameras (will hopefully avoid issues our users see with the ZWO ASCOM driver… VERY BETA)
  • Initial support for Optec Focus Lock (FocusLock usage instructions)!
  • Docking module added to convey FocusLock status directly inside SGPro
  • Open, connect gear, start and stop your lock all from within SGPro
  • Block integration start until Focus Lock reports good focus
  • Ask SGPro to restart your current frame if Focus Lock reports that focus is lost
  • Ask SGPro to ensure FocusLock does not move your focuser during integration
  • Removed “AtHome” check from observatory slaving
  • Removing “AtPark” check for dome slaving
  • Fixed the AstroBin target importer
  • Added camera gain to the file namer (%cg)
  • Planner errors (anything that causes a blank graph) are now visible even if the target is not using start / end times Changes:

  • Recovery mode stabilization
  • Fixed a bug in the activity planner graph that would sometimes not plot start and end times properly
  • Installer will now always prompt for installation directory Changes:

  • Fixed an issue where the SGPro installer might be flagged as malware (it never was though)
  • Various bugs fixed for the target planning tool graph
  • Fixed bug where opening a target with no user profile would throw an exception
  • Fixed a bug that could prevent end of sequence options on guider failure Changes:

  • Beta implementation of the SGPro “Planning Assistant” (more here: Planning Tools Release Candidate). There are likely issues where the graph feature does not work properly for all latitudes (needs testing for southern latitudes).
  • SBIG RBI Implementation
  • User profile selection now contains an option to open the user profile manager (shortcut). Known issue: selecting this option will deselect the user profile so that you will need to select it again after closing the user profile manager.
  • SGPro addons (MFW and Notification Wizard) are no longer licensed individually (they are part of the main SGPro license now) Changes:

  • Implemented “per-event” gain control for ASCOM cameras.
  • A sequence can now import targets from other SGPro sequences.
  • Initial implementation of Gemini SnapCap FlatBox device.
  • Restored old TEC cooling code that was, by chance, allowing the QHY driver to work properly (the real fix for this must come from QHY as the rate of reading temperature should be independent of the rate at which the TEC cools).
  • Any park command issued through SGPro will now be followed by a stop tracking command.
  • Fixed a bug where SGPro’s internal temp comp was broken if using an external device to read ambient temperature.
  • Updated CTYPEn FITS headers to report projection as gnomonic (instead of default).
  • SGPro will now more accurately detect the need to auto connect with a flats box.




Just a note on the native ZWO support. As Ken mentioned this is VERY BETA. Use with caution and please note the following in terms of gain/offset:

  • When “Not Set” is used the last set values in the driver will automatically be used. So if you set these values with the ASCOM driver then they will still be used in SGP.
  • When gain is set the offset will be set to the “Highest Dynamic Range” value for that camera. Currently offset is not exposed as we don’t have any where to put it on the SGP UI.

Also images taken with this camera are likely not compatible for calibration with those taken with the ZWO Ascom driver. You can try, but don’t be surprised if you get weird results and need to retake any calibration frames.

All that said I have used the native implementation with very good success and it seems a good deal more stable and has considerably smaller memory footprint as compared with the ASCOM driver.