I think there is a fundamental misconception here.
PHD2 provides a single INDI driver and it is available on top of the CCD list. You select this driver in PHD2. This lets PHD2 connect to INDI, on which you should run CCD driver for whatever camera is supported by INDI. So PHD2 -> INDI driver -> INDISERVER with CCD DRIVER (e.g. QHY)
Thank you for this reply. No misconception. Before the last PHD2/KSTARS updates, QHY5 worked. Today, it doesn’t work.
Under AB 1.1, I get the INDI QHY5LII device in the PHD2 pick list. PHD2 cannot connect to it, timeout error.
Under AB 2.0, PHD2 presents PHD2 drivers only. QHY5 is the singular option. Yet, I connect the mount to the INDI driver. Why not include all the other CCD resources managed by INDI?
Under AB2.0 and 1.1, the PHD2 promised QHYCCD Camera option is not given. QHY5 is it. To me, Either the program is prejudiced against the QHY5L. The PDF says so. Why? This is analogous to Analog and Digital. QHY5 devices can take video, while the newer ones take digital frames. The ZWO takes frames. The INDI driver can get the ZWO to take video. I will reorder my configuration to meet PHD2 requirements.
Also, PHD2 is very spartan under AB2.0 and Raspbian. One PHD2 window is shown with a option bar. I can use Linguider.
Yes it is misconception.
First of all Astroberry Server is using the latest PHD2 with no customization whatsoever. So any PHD2 functionality should be addressed to PHD2, not Astroberry.
Second, If you use INDI driver in PHD2 you can choose CCDs running on INDI server, that's how it works and it always worked this way.
EDIT: Not to leave you with just this comment I will give you an advice - add to your INDI profile your cameras and make sure that you select PHD2 as a guider, start INDI server with your profile, start PHD2, select INDI as a CCD driver, click next at SELECT one of cameras you run on INDI server. You're done
Thank you for the confirmation. I was able to get the dance between EKOS and PHD2 working last night.
The CONNECT to PHD2 is the start of the Dance. PHD2 must be running before the EKOS button click. I finally received the promised INDI Camera option within PHD2. The other hill to climb is the CONNECT Camera button. Under INDI camera, I received a beautiful pick list of all of the available CCD cameras as I was expecting. With the QHY5LII selected, I was presented with a configuration page to get PHD2 and INDI to talk with each other as I was expecting.
Within this configuration, DEVICE PORT is the singular option blank. I researched the net for what goes into DEVICE PORT. Under ASCOM, (all PHD2 documents are ASCOM focused), DEVICE PORT is COMn. Under LINUX, INDI, and PHD2, my trial results says, Leave it blank. Everything is working when DEVICE PORT is blank.
My post was seeking answers with this connection dance between EKOS and PHD2. PHD2 can operate independently from EKOS. Its stock driver support is limited to 6 devices. INDI is the manager of the CCD toys. A bridge must be established under the CONNECT button in EKOS with PHD2. PHD2 documentation says INDI CAMERA is the software bridge head to accept from EKOS what EKOS has.
What started me down this path was the connect button experience was yielding PHD2 thinking it was in standalone mode and EKOS thinking it had connected. No bridge head was being offered.
Under EKOS, CCD device types are considered by default under OPTIONS tab SCOPE or CAMERA. On each camera option, I configured the device as camera and saved the configuration. Hence, my success was configuring EKOS properly to give PHD2 its list to enumerate the CCD options in EKOS. Once done, EKOS and PHD2 can dance all night.
Under PHD2, the QHY5 is no longer standalone supported. Use the INDI CAMERA option.
To use the INDI CAMERA option, EKOS must have CCD devices to present. CCD devices must be configured to be CCD and not OTA types. EKOS is the starting point of the CCD dance.
Or EKOS has nothing to present. PHD2 will think it is in standalone mode. Posts like this one will occur. Who has time to document the requirements of the EKOS and PHD2 dance?
My hope is this discussion may help someone else. Thank you for each contribution. Clear skies.
Anyone else having any issues since last updates...
When Kstars opens now I get an error saying that there is no ASTAP loaded or it’s pointing to the wrong folder, and then if I hit the align tab, it shuts Kstars down, all other tabs are ok, it worked before...any ideas...??
Looks like this time I get to say mine ASTAP is working with the EKOS PolarAlign after the KSTARS bleeding update. Just confirmed.
On a side note, I upgraded and found my QHY devices not recognized. I had just finished working on my PoleMaster-QT install. Apparently, the FXLOAD driver was old. I went to QHY and downloaded the RPI SDK for Nov 2019. This cleared up the udev issues. Back in the saddle again.