Hi everyone
When starting to guide, there is a message which needs manual intervention complaining about the capture and guide cameras being the same. This doesn't make sense.
No camera needs to be set since it is set in the PHD2 profile. PHD2 connects to the correct camera when ekos asks it to begin guiding.

Please could we remove the need to include a guide camera if PHD2 is specifed and hence (I think) remove the error message?
TIA,
Steve

Thanks for reporting this! You did not include the guide camera in the list of cameras Ekos can manage and Ekos is missing your point. I completely agree on this use case, and you can probably work around the annoying pop-up by adding the guide cam to your profile, even if you don't use it. We'll fix this.

-Eric

Hi
If I include the guide camera (a zwo120mm) in the profile, the image from the native zwo driver under PHD2 is trashed.
Would really appreciate the fix as if the guider drops during capture, the message appears again and manual intervention is required; defeats the purpose of a scheduler!
Cheers,
Steve

I bumped bugs.kde.org/show_bug.cgi?id=391344 for this issue.

-Eric

Yeah. Best to simply lose the popup for phd2 guiding.
Is that easily doable?
TIA.

Actually one thing that I have been thinking would be a good idea for awhile would be to have PHD2 as an option in the combo box in the Guide module. So that way it doesn't need to have a camera associated with it. I've mentioned this to Jasem before. I think we really need to do this before the 3.0 release. It is important. I probably will have time to work on this soon.

Thanks,

Rob

Build: 2018-09-01T10:49:35Z
Well, it appears fixed. Here is the nice all new sparse PHD2 screen. No popups in sight:)



Big thanks to whoever corrected this
log: drive.google.com/open?id=1Y-NAHmMc5X4dLWa0NCQifQ_XMZ-x9kkq