SharpCap Forums

Hi, what format do the co-ordinates for the asteroids come in (is there a standard format from some online source like the Minor Planet Center?). SharpCap already has code to detect and interpret data created by the AAVSO web site when pasting custom targets or reading custom catalogs, so I don't mi...

Hi,

thanks, that's good to know - I will try to work out a way to make a button or similar for this...

cheers,

Robin

Hi, you are right that closing and re-opening the camera will reset the stack, but there are a couple of other options that might do the trick 1) Use the 'Reconnect Camera' option from the camera menu - that might be sufficient, although it doesn't quite reset everything that close/reopen does. It m...

Hi Ken,

thanks for reporting back - that wasn't something I had expected at all, so good of you to share, just in case someone else hits the same problem!

cheers,

Robin

Hi Willian, yes, RAW16 is the right option to choose for deep sky imaging, as it will retrieve the data from the camera with the full bit depth of the imaging sensor, rather than only at 8 bit in the RGB24 option. You should use RAW16 for both light and dark frames, and keep other settings like expo...

Hi, some mounts can move to the Home position via the ASCOM driver, but SharpCap doesn't have any built in functionality to trigger it - most people just use the park position the same as the home position, so 'Parking' the mount does the trick. You can test out if your mount supports this using Sha...

Hi, Ok, that's good to know - the mount is reporting JNOW and SharpCap is converting to JNOW. The only reason that you would be out in that situation would be if the mount reports JNOW but is really J2000, but I think that's unlikely. The time on the mount seems OK - from the log Info 20:56:52.51877...

Hi folks, as far as I am aware, the problem affects a number of different models - there are various reports in the 'QHY cameras' forum on here. I don't have a list to hand unfortunately. I last updated the QHY SDK in March, adding an update published in January. If you go back to SharpCap 4.1.11961...

Hi Louis, oh, that's a pain - either the cover really is in an error state, or the ASCOM driver from Alnitak is reporting an error state for no good reason. It may be worth checking to see if the Alnitak ascom driver can record its own log information - if it can do that then maybe it would record s...

Hi Ken, the only reason that SharpCap would deliberately show a different value to the raw focuser value is if you have turned on backlash compensation in the SharpCap focuser settings. If that setting is turned on, SharpCap will be trying to compensate for the backlash adjustment size you have set,...