-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PHD2 cannot handle mount and camera on different indi server #1090
Comments
@gnthibault thanks for letting us know about the issue |
The way to do that with INDI is to link the server together as explained in the page: There is multiple advantage to that, specifically the INDI server can still fill the FITS header with the telescope information even it is connected to the other server. To prevent multiple image transport on the network be sure you connect PHD2 to the server with the camera and create the link to the telescope on this server. |
Thank you very much for the feedback @pchev . |
Sorry I changed my mind, I think there are still good reason for having phd2 to manage more than one client. Linking indi server is a good workaround but still a workaround from my point of view (I tag fits with observatory informations with my own application for instance) |
To whom it may concern,
I am currently facing an issu with openPHD2. Whenever I click on the connection button to setup my profile, I notice that I need to select mount an camera device given an Indi server and port.
Unfortunately it appears that I cannot use one camera on one server, and one mount on another server.
Unfortunately, this is exactly what I need to do currently on my setup. I think this is more or less a bug, as one can enter a different value for indi server host in camera and mount, but later on the software crashes.
Supporting multiple parallel indi client would definitely be the way to go for me.
Thank you in advance for your help and support.
The text was updated successfully, but these errors were encountered: