Hi, i'm experimenting a problem in pixinsight when the keyword CCD-TEMP comes with an non integer value, because sharpcap use "," as decimal point separator in FITS header and in pixinsight forum says this is incorrect.
mey be a way to solve that?? if not i could not be able to use Sharpcap unfortunatelly.
[FIXED 3.1.5157] FITs keyword CCD-TEMP error in pixinsight
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]
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]
-
gvillarroel
- Posts: 1
- Joined: Thu Apr 26, 2018 12:06 pm
-
admin
- Site Admin
- Posts: 13295
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: FITs keyword CCD-TEMP error in pixinsight
Hi,
the only fix for now is to update your Windows settings so that you use a '.' as a decimal separator rather than a ','. If you keep your settings like this while capturing then SharpCap should write the numbers with '.' into the FITS header and everything should be fine. I will change the code to use '.' regardless of the windows settings in a future update of SHarpCap.
cheers,
Robin
the only fix for now is to update your Windows settings so that you use a '.' as a decimal separator rather than a ','. If you keep your settings like this while capturing then SharpCap should write the numbers with '.' into the FITS header and everything should be fine. I will change the code to use '.' regardless of the windows settings in a future update of SHarpCap.
cheers,
Robin