Touptek G3M662M and ATR585M settings in newer Sharpcap versions

A place to report problems and bugs in SharpCap
Forum rules
‍

If you have a problem or question, please check the FAQ to see if it already has an answer : https://www.sharpcap.co.uk/sharpcap-faqs

Please also read about Troubleshooting USB Issues before posting.

*** Please do not post license keys - please report any problems with licensing to 'admin' by private message ***

Please include the following details in any bug report:

* Version of SharpCap
* Camera and other hardware being user
* Operating system version
* Contents of the SharpCap log after the problem has occurred.
[If SharpCap crashes, please send the bug report when prompted instead of including the log]
RadHard
Posts: 10
Joined: Mon Apr 07, 2025 8:24 pm

Re: Touptek G3M662M and ATR585M settings in newer Sharpcap versions

#21

Post by RadHard »

Hello Robin,

Thank you. Since i was doing 500ms exposures, i wanted to try if i can keep the amount of data down by letting the SharpCap live stack and i set the Save and Reset option for one minute. Dark subtraction was set in SharpCap, but since the livestack was reset every minute worth of good subs, i think it might have less benefit from not clipping negative values. I was not saving the raw subs. In the end i have got 140 of those one minute stacks and then i stacked those in Siril without applying any further calibration.

I have noticed at that quite extreme gain of 50000 the pixel values jump quite a lot, i will try this mode later at lower gain, or add more offset.
It might be maybe difficult to calibrate that when the dark frames have some extreme values.

For the FWHM, it could be named simply FWHM, i have made my own python script to sort/categorize the frames as they come out from SharpCap. Then i do no need to collect everything after multiple sessions/interrupted live stack, etc. and everything is grouped together based on target, filter and camera settings.
File name then for example looks like this: NGC5457_(M101)_G_120s_1365_396_-10degC_20250410_215500.fits

I have now also added analysis of the star roundness, so i can sort the subs based on some quality criteria, but astropy takes good 2-3seconds to perform the star detection and then some analysis. Furthermore i did not manage to make it to output useful FWHM calculation, but in the end i found the star roundness to be quite good quality indicator. At least for the situation where the bad quality was causes by the wind shaking the mount.
If i can take the FWHM simply from the header, that will be much faster for the sorting.

Thanks!
Post Reply