INDI Library

INDI Library
Name	INDI Library
Developer	Hakan Sökmen; contributors from Space Telescope Science Institute, European Southern Observatory, National Aeronautics and Space Administration, Jet Propulsion Laboratory
Released	2003
Latest release version	1.9.9
Programming language	C, C++
Operating system	Linux, macOS, FreeBSD, Windows Subsystem for Linux
License	GNU General Public License

INDI Library

The INDI Library is an open-source device control framework designed for astronomical instrumentation and robotic observatories. It provides a protocol and software stack for controlling telescopes, cameras, filter wheels, focusers, and environmental sensors, integrating with observatory automation projects, telescope control systems, and imaging pipelines. The library interoperates with numerous observatory projects and institutions, enabling networked control, remote operation, and service-oriented architectures.

Overview

The INDI Library implements a network-transparent protocol that separates device drivers from client applications, enabling interoperability between projects such as KStars, Ekos, INDI Web Manager, CCDStack, and observatory control systems used at facilities like Lowell Observatory, CalTech, and Mount Wilson Observatory. It supports instrument types common at facilities such as Mauna Kea Observatory, Palomar Observatory, and La Silla Observatory, and integrates with scheduling software inspired by initiatives like Las Cumbres Observatory Global Telescope Network and Large Synoptic Survey Telescope. The architecture emphasizes modularity, remote operation similar to models used by National Radio Astronomy Observatory and European Southern Observatory, and standards compliance that facilitates adoption by universities, amateur groups, and commercial vendors.

Architecture and Components

The core consists of a server daemon providing device abstraction, a client protocol, and a collection of drivers. The server model echoes designs from projects like Apache HTTP Server in modularity and D-Bus in bus-oriented communication. Components include a device manager, property vectors, event handling, and transport layers compatible with TCP/IP stacks and message routing systems used by ZeroMQ and RabbitMQ. The driver set commonly interfaces with hardware APIs from vendors like ZWO, SBIG, ASCOM-compatible devices (bridged via adapters akin to Wine), and observatory middleware developed at Space Telescope Science Institute and European Southern Observatory. Tools for diagnostics, logging, and testing borrow patterns from GitLab CI pipelines and continuous integration practices implemented at GitHub and Travis CI.

Supported Devices and Drivers

Supported device classes include charge-coupled device cameras from manufacturers such as ZWO ASI and Starlight Xpress, cooled CMOS imagers used at Jet Propulsion Laboratory prototypes, telescope mounts from suppliers like Losmandy and Paramount, and adaptive optics components similar to those deployed at Keck Observatory and Very Large Telescope. Ancillary support covers filter wheels, focusers, rotators, spectrographs, weather stations (interfaces comparable to Vaisala instrumentation), and guider systems modeled after products from SBIG and Finger Lakes Instrumentation. Community-maintained drivers have expanded to support USB/serial bridges, Ethernet-based controllers, and instrument control electronics developed by university labs at MIT and Harvard–Smithsonian Center for Astrophysics.

Programming Interface and APIs

APIs are provided in C and C++ with bindings and client libraries used by GUI front ends like KStars and scripting environments inspired by Python-based ecosystems at NASA missions. The protocol defines XML-based property vectors and message exchange patterns similar to those used by SOAP-era web services but optimized for low-latency telescope control. Developers integrate with build systems and package managers such as CMake, Autotools, and distribution channels used by Debian and Homebrew. Language bindings and adapters exist for Python, leveraging libraries and frameworks from NumPy and Astropy workflows common in astronomical data reduction pipelines like those at Space Telescope Science Institute and European Southern Observatory.

Use Cases and Applications

Common deployments include remote imaging rigs operated by institutions like Siding Spring Observatory, educational observatories at universities such as University of Arizona, citizen science networks akin to Globe at Night, and automated survey instruments modeled after Pan-STARRS and Zwicky Transient Facility. Applications span time-domain astronomy, robotic follow-up for transient alerts from facilities like LIGO and Fermi Gamma-ray Space Telescope, observatory automation for photometric monitoring in programs run by American Association of Variable Star Observers, and instrument testing in laboratory environments at Jet Propulsion Laboratory and NASA Ames Research Center.

Development, Community, and Licensing

Development is community-driven with contributions from academic institutions, observatories, and hobbyist developers. The project uses collaborative hosting and issue tracking practices found at GitHub and GitLab, continuous integration approaches promoted by Travis CI and CircleCI, and documentation conventions similar to Read the Docs. Licensing under the GNU General Public License encourages open collaboration while commercial integration is facilitated through adapter layers. Outreach and support occur via mailing lists, forums, and workshops often attended by members from International Astronomical Union communities and regional observatory networks.

History and Versioning

The project originated in the early 2000s to address limitations in proprietary control systems, drawing on lessons from automation initiatives at European Southern Observatory and Space Telescope Science Institute. Version history reflects expanding device coverage, protocol refinements, and cross-platform portability efforts influenced by portability work at Free Software Foundation projects. Release milestones correspond to major feature additions such as asynchronous property handling, JSON/XML protocol variants, and broader language bindings, mirroring evolution patterns seen in open-source observatory software stacks like those supporting ALMA and Subaru Telescope.

Category:Astronomical instrumentation