I just updated from H17 to D50. I am using a 162 mm guide scope with the 120 MM mini. It has a FOV of 98x78 arc-min. I now constantly get plate solve errors like "only 17 stars found...adjust exposure...". This seems to happen around the meridian. With H17, plate solving always failed right at the meridian but now it fails if I am anywhere near the meridian (with maybe 10 degrees are maybe even more). And the error is strange because 17 or 19 stars seems like more than enough to solve the image.
Any thoughts??
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Han,
Ok if I need more stars I will increase the exposure. It just seemed to always work well with few stars. I usually use around 2 seconds and it almost always worked with the old database. I will try solving with more stars and see if the helps before I waste any of your time. Thanks for the quick response.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The D50 should work equal or better then the H17. If it doesn't work for you tell me.
For best operation also ASTAP should be updated because the newer ASTAP will understand the density limitation of the D50 database. This will only be notable for a smaller field-of-view then your setup.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Han, I already updated ASTAP to the latest. Here is an image that failed to solve. I think before updating to D50, this would typically solve easily. It said it only found 11 stars. I can't remember the exact exposure but I typically use around 2 seconds with the ASI 120MM mini.
I just updated from H17 to D50. I am using a 162 mm guide scope with the 120 MM mini. It has a FOV of 98x78 arc-min. I now constantly get plate solve errors like "only 17 stars found...adjust exposure...". This seems to happen around the meridian. With H17, plate solving always failed right at the meridian but now it fails if I am anywhere near the meridian (with maybe 10 degrees are maybe even more). And the error is strange because 17 or 19 stars seems like more than enough to solve the image.
Any thoughts??
Hi David,
Difficult to explain why it would fail at the meridian. I like to investigate. Can you share some images where it fails?
19 stars is not much. 30 or more stars would be much better. The FOV should be more then enough to capture 500 stars. Exposure time?
Han
Hi Han,
Ok if I need more stars I will increase the exposure. It just seemed to always work well with few stars. I usually use around 2 seconds and it almost always worked with the old database. I will try solving with more stars and see if the helps before I waste any of your time. Thanks for the quick response.
The D50 should work equal or better then the H17. If it doesn't work for you tell me.
For best operation also ASTAP should be updated because the newer ASTAP will understand the density limitation of the D50 database. This will only be notable for a smaller field-of-view then your setup.
Hi Han, I already updated ASTAP to the latest. Here is an image that failed to solve. I think before updating to D50, this would typically solve easily. It said it only found 11 stars. I can't remember the exact exposure but I typically use around 2 seconds with the ASI 120MM mini.