ASCOM driver SX camera setup
111 views
Skip to first unread message
bulrichl
Oct 1, 2017, 5:50:54 AM10/1/17
to Open PHD Guiding
I have a new guiding camera, a SX Lodestar X2 which I am using with the ASCOM driver and want to build a Dark Library or Bad Pixel Map. In an answer to the posting "Workflow in building Dark Library or Bad Pixel Map?" Andy recommended:
If you are using the SX ASCOM driver to attach to the camera, make sure you are not using any of the noise reduction or interlacing adjustment options in the ASCOM driver settings. (This is a moot point if you are using the built-in SX camera support, "Starlight Xpress SXV").
This is unclear to me, because I do not see any noise reduction adjustment. Relating to interlacing adjustment: have I to uncheck "Equalize Frames" and "Double Expose Short"?
(The default setting of the ASCOM driver are appended as JPG file.)
Bernd
If you are using the SX ASCOM driver to attach to the camera, make sure you are not using any of the noise reduction or interlacing adjustment options in the ASCOM driver settings. (This is a moot point if you are using the built-in SX camera support, "Starlight Xpress SXV").
This is unclear to me, because I do not see any noise reduction adjustment. Relating to interlacing adjustment: have I to uncheck "Equalize Frames" and "Double Expose Short"?
(The default setting of the ASCOM driver are appended as JPG file.)
Bernd
Andy Galasso
Oct 1, 2017, 11:08:34 AM10/1/17
to OpenPHD Guiding
Bernd,
For a Dark Library, it does not really matter what settings you use. For a Bad-pixel map, disable Square lodestar pixels and gaussian blur. Equalize frames and double expose short are probably ok either way.
The reason for these suggestions is we want to disable any ASCOM driver options that cause neighboring pixels to be affected by a hot pixel so the bad pixel map can deal with them effectively.
Andy
bulrichl
Oct 1, 2017, 12:13:59 PM10/1/17
to Open PHD Guiding
Andy,
then the default setting that I appended are OK. Thank you for the quick answer.
Bernd
then the default setting that I appended are OK. Thank you for the quick answer.
Bernd
Bill McLaughlin
Oct 1, 2017, 5:26:04 PM10/1/17
to Open PHD Guiding
I have to ask why you need to use the ASCOM? I have been using the built in support which works great and does not involve any of these issues.
bulrichl
Oct 2, 2017, 4:53:37 AM10/2/17
to Open PHD Guiding
Hi Bill,
the reason is, that the two drivers deal differently with the Lodestar's interlaced readout. The internal driver "Starlight Xpress SXV" is binning even and odd rows together (camera binning 1x2), thereby losing some spatial resolution due to the binning, whereas the ASCOM driver does not. I have a short focal length guide scope, so I prefer to use the ASCOM driver.
Andy explained this here:
https://groups.google.com/d/msg/open-phd-guiding/6qU2gBEuHsM/-a0vy_gqEgAJ
By the way, there are no issues involved at all: the setup of the driver has to be done only once.
Bernd
the reason is, that the two drivers deal differently with the Lodestar's interlaced readout. The internal driver "Starlight Xpress SXV" is binning even and odd rows together (camera binning 1x2), thereby losing some spatial resolution due to the binning, whereas the ASCOM driver does not. I have a short focal length guide scope, so I prefer to use the ASCOM driver.
Andy explained this here:
https://groups.google.com/d/msg/open-phd-guiding/6qU2gBEuHsM/-a0vy_gqEgAJ
By the way, there are no issues involved at all: the setup of the driver has to be done only once.
Bernd
Reply all
Reply to author
Forward
0 new messages