Tools / Plate solve with Test Camera

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]
Post Reply
User avatar
carlomuccini
Posts: 260
Joined: Mon Apr 27, 2020 12:42 pm
Location: Montecatini Terme (PT), Italy
Contact:

Tools / Plate solve with Test Camera

#1

Post by carlomuccini »

When with the Deep Sky Camera Test I open a FIT file previously saved the night before and already solved by SharpCap and I repeat the plate solve operation, SharpCap does a 180° search until after several seconds it recognizes the star field.
It seems that it does not read the coordinates saved in the FIT file but that it starts again from an arbitrary position, perhaps a position found previously ?

Carlo
User avatar
admin
Site Admin
Posts: 17544
Joined: Sat Feb 11, 2017 3:52 pm
Location: Vale of the White Horse, UK
Contact:

Re: Tools / Plate solve with Test Camera

#2

Post by admin »

Hi,

if the FIT file has RA/Dec headers stored in it the SharpCap should use those and start the search at that point. However, SharpCap only writes those headers in general if a GOTO mount is connected when the image is captured, not as a result of previous plate solving. So, maybe that was the cause?

cheers,

Robin
User avatar
carlomuccini
Posts: 260
Joined: Mon Apr 27, 2020 12:42 pm
Location: Montecatini Terme (PT), Italy
Contact:

Re: Tools / Plate solve with Test Camera

#3

Post by carlomuccini »

I use a Celestron CGX-L connected with CPWI to Sharpcap and everything always works fine.
After a GOTO I always do SharpSolving which is instantaneous: ASI294MM and ASI 533MC

We always talk about PlateSolving with the deepsky simulator

If I load a FIT taken with the ASI 294MM B/W camera, SharpSolving is practically instantaneous
If I load a FIT taken with the ASI 533MC color camera, SharpSolving does a full 180° turn and then, in the end, it solves.
The problem only exists with the shots taken with my color camera; the header of the FIT file the data is all there.

Carlo
User avatar
admin
Site Admin
Posts: 17544
Joined: Sat Feb 11, 2017 3:52 pm
Location: Vale of the White Horse, UK
Contact:

Re: Tools / Plate solve with Test Camera

#4

Post by admin »

Hi Carlo,

can you share one of each sort of file so I can see if I can make it happen in testing please?

thanks,

Robin
User avatar
carlomuccini
Posts: 260
Joined: Mon Apr 27, 2020 12:42 pm
Location: Montecatini Terme (PT), Italy
Contact:

Re: Tools / Plate solve with Test Camera

#5

Post by carlomuccini »

Hi

I wanted to post the FIT file but it's too big; I zipped it but it's too big..... >> Google Drive
It is a 16bit FIT file generated in live stacking with the ASI 533MC and Baader UHCS filter
Running Plate solve / Solve only starts from RA 00:00:00 and continues until it finds it

https://drive.google.com/file/d/1TGRUZh ... sp=sharing

Carlo
User avatar
admin
Site Admin
Posts: 17544
Joined: Sat Feb 11, 2017 3:52 pm
Location: Vale of the White Horse, UK
Contact:

Re: Tools / Plate solve with Test Camera

#6

Post by admin »

Hi Carlo,

thanks for sharing - I do have a 1Mb limit on attachments to stop the forums being used as 'Astrobin for SharpCap'... It keeps the amount of data I have to backup under control ;)

I see the issue with that image too - it's because the image is an RGB three channel image from live stacking, but by default the deep sky camera converts to RAW16 to simulate a typical astro camera. The positional info is not being preserved through the conversion, but I will fix that for the next update.

cheers,

Robin
Post Reply