Siril and some others have an option to import the required data for photometric calibration directly from the FITS header. This is obviously convenient.
I am not able to find a way to enter the telescope data when capturing in Sharpcap. It does the platesolving fine, so the image scale must be captured somewhere.
If it helps, SC is connected to my mount which does have the FL and pixel size data stored in its software.
How do I get SC to store the scope FL in the FITS header?
Thanks
Entering telescope details in FITS header
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
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
-
- Posts: 156
- Joined: Mon Mar 01, 2021 5:24 am
- admin
- Site Admin
- Posts: 13280
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: Entering telescope details in FITS header
Hi,
thanks for the suggestion - this isn't implemented in SharpCap at the moment, although you should get the pixel size which comes from the camera. I will note down the idea to get the focal length from the ASCOM setup.
cheers,
Robin
thanks for the suggestion - this isn't implemented in SharpCap at the moment, although you should get the pixel size which comes from the camera. I will note down the idea to get the focal length from the ASCOM setup.
cheers,
Robin
-
- Posts: 156
- Joined: Mon Mar 01, 2021 5:24 am
Re: Entering telescope details in FITS header
Thanks.
Yes, the pixel size is stored in the header.
Suggestion - could also keep an option to enter it manually in SC, to take care of the case where SC is not connected to the mount.
So if there is no connection, SC will populate the header with the manual entry (maybe with a popup reminder of the current data)
If connected, the mount/ASCOM data will override the manual entry.
Yes, the pixel size is stored in the header.
Suggestion - could also keep an option to enter it manually in SC, to take care of the case where SC is not connected to the mount.
So if there is no connection, SC will populate the header with the manual entry (maybe with a popup reminder of the current data)
If connected, the mount/ASCOM data will override the manual entry.
- admin
- Site Admin
- Posts: 13280
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: Entering telescope details in FITS header
Hi,
yes, agreed - I was thinking about something like the polar alignment settings where the location can either come from the ASCOM mount or be entered manually.
cheers,
Robin
yes, agreed - I was thinking about something like the polar alignment settings where the location can either come from the ASCOM mount or be entered manually.
cheers,
Robin
Re: Entering telescope details in FITS header
Would it be possible in the SharpCap Settings menu to have a tab where the focal length for telescopes could be stored, and also written to the fits header? Perhaps under hardware with a user generated list of telescopes for those who image with more than one OTA/focalreducer combination etc.This would be useful for subsequent data processing.
- admin
- Site Admin
- Posts: 13280
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: Entering telescope details in FITS header
Hi,
currently the plate solving setting for focal length is used for this - so if you have set a manual focal length then that should end up in the FOCALLEN header, alternatively it can come from the ASCOM driver if you have that set up.
An equipment list is a nice thought - I need to collect all these ideas and bring them together in a consistent way, so thanks for suggesting.
cheers,
Robin
currently the plate solving setting for focal length is used for this - so if you have set a manual focal length then that should end up in the FOCALLEN header, alternatively it can come from the ASCOM driver if you have that set up.
An equipment list is a nice thought - I need to collect all these ideas and bring them together in a consistent way, so thanks for suggesting.
cheers,
Robin