--
You received this message because you are subscribed to the Google Groups "Open PHD Guiding" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-phd-guidi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/39cc6bca-c44f-4840-8f9e-1b3701bf4717n%40googlegroups.com.
IMO, the .fit image you sent had no real stars in it. So that’s the problem you will need to figure out, whatever the source. It had significant sensor noise so you should always be using a dark library – doing so is not going to reduce your ability to find real stars assuming it’s been built correctly (meaning there were no light leaks while collecting dark frames). In the current dev releases, the new-profile-wizard does disable star-mass detection but that was a comment unrelated to your problem. I suggest you slew the scope to a star-rich field, one with a range of star brightness values, and re-examine the focus. Use whatever exposure times you need to find stars. Once you can confirm focus and collect guide cam frames that have usable stars – based on how auto-find behaves - you can move ahead knowing that the guide camera and focus are right. Then is the time to consider whether the necessary exposure times are too long for your mount. You can capture a guide cam image with the File/Save menu option at any time to record what’s happening. If you become convinced that the frames do have usable stars despite what I’m telling you, you can reduce the Min-HFD value to 1.0 and start guiding. If you’re guiding on sensor noise, you will know it very quickly based on the guiding results.
Good luck,
Bruce
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/956b8ae4-d1c5-4498-95cc-519a5531a97an%40googlegroups.com.