INDIGO Script Editor

Getting started with the INDIGO agents based backyard astrophotography application suite

About eight years ago we started to develop a software with the idea to make Apple macOS and iOS the first class platforms for backyard astrophotography.

At the beginning, the most important task was to add as many hardware drivers as possible. So we used the existing INDI framework. Later we focused on the performance and reliability and transferred the whole development to INDIGO framework.

In the latest generation we made so far the most radical change. We left the traditional client server approach and switched to multi-tier agent based architecture allowing even higher performance and reliability.

Core and utility applications of astrophotography suite

Unlike the other similar systems, our suite is not a single monolithic application, we use standalone loosely coupled applications instead. This approach has some advantages and some drawbacks. The major advantage is that you can select just tools you really need and use them only when you really need. The disadvantage is that you need to understand how the applications work to configure them to talk to each other properly.

There are five core applications and a couple of utility applications in our suite. The core applications are:

The utility applications are:

Please note, that every core application contains an embedded server, control panel and script editor. The standalone versions are intended for advanced use and are not necessary in the most cases.

About INDIGO and INDIGO agents

INDIGO is a system of standards and frameworks for multiplatform and distributed astronomy software development.

You can consider it as a next generation of INDI, based on layered architecture and software bus. INDIGO uses the same astronomical hardware abstraction as INDI, but removes some of its design limitations, dramatically improves its performance in some typical scenarios and overcomes license restrictions to allow both non-commercial and commercial use.

If you don't want to, you don't need to care about INDIGO complexity and its distributed nature. Each application contains embedded INDIGO Server together will all necessary drivers. You can just use it.

Although INDIGO was always well prepared for a distributed computing, for many situations the traditional client/server is not the best approach. The most important driver for the change was implementation of webGUI on INDIGO server. The thin client running in a browser needs a much smarter backend than INDIGO server itself, it needs a server side application logic. We use term INDIGO agent for this code, acting on the server side and controlling the local devices on behalf of the client.

Such an agent is independent of the connection to the client. The client can configure it, disconnect and keep it running, doing its job and connect later to monitor the status or to take the results. The communication between the driver and the agent is also not limited by network bandwidth as far as they both live in the same INDIGO server and can communicate to each other over the software bus on a procedure call speed.

And last but not least, as far as agent code contains the vast majority of application logic for typical operations supported by the applications for amateur astronomy. Implementation of the client is in this case  just implementation of native GUI for a given operating system. It is faster, easier and possible bugs can be fixed on one place.

To learn more about INDIGO or INDIGO agents or to ask a question, visit FAQ section of our users forum.

What's new in the version 4.14

What's new in the version 4.13

What's new in the version 4.12

What's new in the version 4.11

What's new in the version 4.10

What's new in the version 4.9

What's new in the version 4.8

What's new in the version 4.7

What's new in the version 4.6

What's new in the version 4.5

What's new in the version 4.4

What's new in the version 4.3

What's new in the version 4.2

What's new in the version 4.1

What's new in the version 4.0

INDIGO Script Editor overview

INDIGO Script is a built-in scripting language based on ECMA Script with binding to the INDIGO objects and functions. Scripts may be executed manually, on agent load or unload or registered as event handlers and triggered by any INDIGO events.

Scripts are executed by Duktape engine wrapped into a scripting agent. To learn more about the language, visit Duktape site.

To learn more about INDIGO bindings, read scripting agent README.

To see some real world scripts look at INDIGO Script subforum.

INDIGO Script Editor is a standalone version of the embedded editor included with all other INDIGO suite applications. It has its own INDIGO client and is packaged with built-in control panel.

It can be used to create, rename, delete, execute, schedule, upload or download scripts on all visible servers.

INDIGO Script Editor preferences

In INDIGO Script Editor preferences you can set various settings for the embedded INDIGO client.

On the INDIGO pane you can configure access token and logging verbosity for GUI. Read this post to learn how to make a debug or trace log.

On the INDIGO Services pane you can see automatically detected INDIGO services and also to configure some of them manually, e.g. legacy INDI servers or services running outside your local network.

On the INDIGO Ports pane you can configure a serial port for those drivers which need it. Note, that these settings supersede the saved value of PORT property of the driver.

Script management

Each time the content editor is changed, you can save or discard the changes.

You can execute or delete the script and to configure it to execute on load or unload of the script agent. You can also save the script to the file or load it from the file.

Script editor features

You can enable line numbering or line wrapping. You can enable JSLint to for on-line script validation. You can also decrease or increase font size or change colour palette.

Further questions?

Please contact us at or