Hi
I was working on stacking some of my images from my ASI2600MC pro camera.
When looking at some of my captured raw frames in ASTAP i noticed the following image information
ADCBITS = 14 / Bit depth of camera sensor ADC in current mode
BIASADU = 160 / ADU for bias level (no photons) at current sett
IMAGETYP= 'Light' /
INSTRUME= 'ZWO ASI2600MC Pro' /
SWCREATE= 'SharpCap v4.1.14155.0, 64 bit' /
When I stacked the images in Seti Astro Pro , the log file was reporting the image size as ( 6072 x 4042)
The ZWO ASI2600MC Pro' camera specs state
ADC 16bit
Resolution 6248 x 4176
Do you think the reported reduction in pixel resolution ( 6072 x 4042) from (6248 x 4176)
something real ?
Is the ADC bit depth being reduced?
Is there a resolution limitation happening in SC?
Thanks for help on this.
ASI2600MC pro reported pixel count, ADC bit depth
Re: ASI2600MC pro reported pixel count, ADC bit depth
The problem appears to be in SAS pro.
ASTAP and Astrophotography Tool report the correct resolution for the ASi2600 MC pro
I will check with Frank at SAS pro
Thanks
ASTAP and Astrophotography Tool report the correct resolution for the ASi2600 MC pro
I will check with Frank at SAS pro
Thanks
- admin
- Site Admin
- Posts: 17510
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: ASI2600MC pro reported pixel count, ADC bit depth
Hi,
have you done your own sensor analysis of the ASI2600? The ADCBITS header value comes from that data, so if something odd happened during the analysis then it could record a 14 bit sensor incorrectly and that will then go through to the saved FITS files. The data itself will be genuine 16 bit data, so nothing to worry about there, but 'smart histogram' recommendations might be wrong if you have the wrong bit depth in your local analysis file.
I did check the default analysis file that is installed with SharpCap and that does have 16 bits for the ASI2600.
cheers,
Robin
have you done your own sensor analysis of the ASI2600? The ADCBITS header value comes from that data, so if something odd happened during the analysis then it could record a 14 bit sensor incorrectly and that will then go through to the saved FITS files. The data itself will be genuine 16 bit data, so nothing to worry about there, but 'smart histogram' recommendations might be wrong if you have the wrong bit depth in your local analysis file.
I did check the default analysis file that is installed with SharpCap and that does have 16 bits for the ASI2600.
cheers,
Robin