Hello everyone,
I developed an INDI driver to control the INDI server.
It let's you start and stop drivers over the INDI protocol using your favorite client.
Given proper permissions you can also shut down or reboot the host computer.
If you store the driver configuration you can also use it to automatically start your necessary drivers!
Known issues:
- Stopping drivers can cause glitches or problems in your client since the code to handle this event was only added to the library a few weeks ago.
- The driver can only manage drivers it started.
- Representation of the properties depends on ordering properties by name. If your favorite client doesn't do this you won't be able to know witch buttons are for witch driver. This was done to keep labels readable in KStars/Ekos. (Is the bleeding Kstars/Ekos interface more dynamic Jasem?)
Installation instructions, usage instructions, an easy install script and an auto startup (init.d) script can be found on GitHub.
I developed an INDI driver to control the INDI server.
It let's you start and stop drivers over the INDI protocol using your favorite client.
Given proper permissions you can also shut down or reboot the host computer.
If you store the driver configuration you can also use it to automatically start your necessary drivers!
Known issues:
- Stopping drivers can cause glitches or problems in your client since the code to handle this event was only added to the library a few weeks ago.
- The driver can only manage drivers it started.
- Representation of the properties depends on ordering properties by name. If your favorite client doesn't do this you won't be able to know witch buttons are for witch driver. This was done to keep labels readable in KStars/Ekos. (Is the bleeding Kstars/Ekos interface more dynamic Jasem?)
Installation instructions, usage instructions, an easy install script and an auto startup (init.d) script can be found on GitHub.