cant run phd and stellarium telescope control same time

CANT RUN PHD AND STELLARIUM TELESCOPE CONTROL SAME TIME DRIVERS
CANT RUN PHD AND STELLARIUM TELESCOPE CONTROL SAME TIME PC

Further, whilst LinGuider is built in for EKOS use, you use PHD2 for actual guiding instead. When using EKOS, an on-line connection to is used for 'plate solving', however this CAN be done on your own local Client hardware (by downloading the catalogues). The INDI Server at the telescope might use EQMod (for NEQ6 'goto') + GPhoto (for a Canon 450D imaging camera) and V4L2 (to drive the auto-guider camera). The *nix 'planetarium' GUI of choice is usually KStars (plus KStars 'EKOS' plug-in for auto guiding - and EKOS in turn comes with an 'Align' module that assists polar alignment using the drift method)

CANT RUN PHD AND STELLARIUM TELESCOPE CONTROL SAME TIME DRIVERS

Stellarium can be used on both Windows and *nix systems, however it's not a good choice for the Raspberry Pi (even on a Pi B3 with OpenGL GPU drivers Stellarium runs rather slowly) These can then link to any INDI Server equipped remote telescope (including one running on *nix / Raspberry Pi) For example, when using INDI Client on a Windows PC, Cartes du Ciel is typically used as the 'planetarium' GUI for 'goto' control and 'CCD-Ciel' for camera control. The client/server nature of INDI means you have an almost infinite choice of which package to run where.

CANT RUN PHD AND STELLARIUM TELESCOPE CONTROL SAME TIME PC

The Windows PC 'equivalent' to an INDI Telescope Server would be an ASCOM Server It's quite possible to control the Telescope locally 'at the same time' by running another Client directly on (or 'next to') the local Telescope computer (see here, for an example of an INDI Server (on one Pi) being directly controlled by an INDI Client running on a directly connected second Pi NB. Whilst you would expect one 'client' to be 'in control' at any one time, it is possible to divide the functions = so one client (with a Planetarium GUI) might control the selection of the telescope 'target' position, another imaging, and yet another 'tracking' The 'client/server' concept is based on the idea of a (single) 'remote' Telescope (the 'server') being 'controlled' from one of many 'clients' across the Internet or your local LAN Ethernet/WiFi). (running GUI 'planetarium' software) to remotely control a Telescope 'Server' computer (running Telescope 'control' software) across any IP network (i.e. The INDI system allows a 'Client' computer - PC, laptop, tablet, smart-phone etc. Pi Indi Server The INDI system for Robotic Imaging

Cant run phd and stellarium telescope control same time