Seeking Beta Testers for Advanced PHD2 Planetary Guiding Module – Enhance Your Solar, Lunar, and Planetary Imaging

LOVE THIS! Always struggled with existing guiding/tracking solutions for planetary/solar/lunar so am excited to give this a shot.

Interested in solar and planets.

Leo Shatz:

Dunk:
Probably stupid question, but in the above screenshots is that a guide cam pointing at the sun, or the main camera? 

i ask because I’m using a daystar quark and no guidecam…

D.

It's a screenshot using PHD2 special version using Camera device 'Simulator' modified and updated by me to use image source from a given file (the image scale is not strictly enforced in this simulation) - it's used solely for internal testing and illustration purposes. Of course, PHD2 is still designed to use guiding camera for planetary imaging. Using the same camera both for imaging and guiding could be great, but it's currently not supported. Guiding camera/scope will need to be protected by a proper energy reduction filter and/or white light filter and other filters or all of them. I hope it answers your question.

I suppose it is possible to connect OAG between Quark and the main imaging camera and add the guiding camera. It's something I would like to try by myself when my gear and conditions will allow it.

Lasse Skov:
Hi Leo

Is it possible to participate in the beta without using Facebook? That platform is not for me

The Windows binaries can be found in Releases section under Assets at this GitHub location: https://github.com/Eyeke2/phd2.planetary/releases

I'm providing the following information for users of the PHD2 custom version with Planetary Tracking who do not have access to the Facebook platform and thus cannot view all the information shared on the dedicated Facebook forum.

The preferred method for guiding on the entire planetary disk, as well as full solar or lunar disks, is through the Eclipse mode. While I discourage disabling the Eclipse mode, the option remains available as a fallback in cases where Eclipse mode detection may fail. The Eclipse mode has sub-pixel detection accuracy, unlike the algorithm used when this mode is disabled. The Surface Features Tracking mode has the highest precision, but it requires higher magnification or longer guide scope focal length, while atmospheric turbulence, more pronounced with solar imaging, may worsen the detection accuracy.

Key parameters to focus on are the minimum and maximum radii settings. These should be carefully adjusted to match the radius of the planetary disk, with the minimum radius being slightly smaller and the maximum radius slightly larger than the actual disk radius.

Highlighting an Existing Feature - Separate Profile Management for Different Guiding Sessions:

I would like to bring your attention to a particularly useful feature in PHD2 that, while not new, I have recently discovered. This feature allows users to create and manage separate profiles for different guiding sessions, such as planetary guiding and night-time star guiding.

By using the command line parameter -i [instance number] in the PHD2 application shortcut, you can effectively run separate instances of the application, each with its own set of configurations. For instance, specifying -i 2 launches a second instance of PHD2, enabling it to operate with its unique settings for variables like exposure times, delays, algorithm settings, equipment profiles, and window positions.

This functionality is especially advantageous for astrophotographers who switch between planetary and star guiding. It allows for easy transitioning between sessions without the need to manually adjust settings each time. Simply use a different instance number (1 is the default for the primary instance) to maintain multiple, independent sets of configurations that cater to your specific observing needs.

Leveraging this feature can significantly streamline and enhance your astrophotography experience by keeping your planetary and star guiding environments distinct and readily accessible.

Malcolm Park:

Leo Shatz:
I'm providing the following information for users of the PHD2 custom version with Planetary Tracking who do not have access to the Facebook platform and thus cannot view all the information shared on the dedicated Facebook forum.

The preferred method for guiding on the entire planetary disk, as well as full solar or lunar disks, is through the Eclipse mode. While I discourage disabling the Eclipse mode, the option remains available as a fallback in cases where Eclipse mode detection may fail. The Eclipse mode has sub-pixel detection accuracy, unlike the algorithm used when this mode is disabled. The Surface Features Tracking mode has the highest precision, but it requires higher magnification or longer guide scope focal length, while atmospheric turbulence, more pronounced with solar imaging, may worsen the detection accuracy.

Key parameters to focus on are the minimum and maximum radii settings. These should be carefully adjusted to match the radius of the planetary disk, with the minimum radius being slightly smaller and the maximum radius slightly larger than the actual disk radius.

Highlighting an Existing Feature - Separate Profile Management for Different Guiding Sessions:

I would like to bring your attention to a particularly useful feature in PHD2 that, while not new, I have recently discovered. This feature allows users to create and manage separate profiles for different guiding sessions, such as planetary guiding and night-time star guiding.

By using the command line parameter -i [instance number] in the PHD2 application shortcut, you can effectively run separate instances of the application, each with its own set of configurations. For instance, specifying -i 2 launches a second instance of PHD2, enabling it to operate with its unique settings for variables like exposure times, delays, algorithm settings, equipment profiles, and window positions.

This functionality is especially advantageous for astrophotographers who switch between planetary and star guiding. It allows for easy transitioning between sessions without the need to manually adjust settings each time. Simply use a different instance number (1 is the default for the primary instance) to maintain multiple, independent sets of configurations that cater to your specific observing needs.

Leveraging this feature can significantly streamline and enhance your astrophotography experience by keeping your planetary and star guiding environments distinct and readily accessible.

Greetings, I love the idea of Eclipse Mode. Is there documentation? I assume you call it this because it will track the sun or moon as they become crescents during the partial phases? If not, then it wouldn't be an eclipse mode right? Has eclipse mode been tested during an eclipse? Great concept, cheers!

Hi, sorry for late reply. I haven't been checking for messages in this area. I've created Wiki pages on the GitHub project, which could be helpful. Please refer to the Wiki section for more information https://github.com/Eyeke2/phd2.planetary