#Indigo server remove update#
#Indigo server remove driver#
#Indigo server remove software#
#Indigo server remove code#

indigo_change_text_property() - change multiple items of a text property.There are also higher level functions to request a property change, which do not require properly initialized indigo_property structure: indigo_enable_blob() - enable and disable BLOB transfer.indigo_change_property() - request for change of property item values.indigo_enumerate_properties() - send request for definition of available properties.There are several functions that can be used by the client to send messages to the device: The bus instance should be initialized and started by indigo_start() call and stopped by indigo_stop() call.Ī client should be attached to the bus by calling indigo_attach_client() and detached with indigo_detach_client() call. indigo_client - definition of a client containing both client private data and pointers to callback functions.

#Indigo server remove driver#

indigo_device - definition of a logical device made available by driver containing both driver private data and pointers to callback functions.

indigo_property - definition of property container.

indigo_item - definition of property item container.

Basics of INDIGO APIĪ basic common API shared by both driver and client roles is defined in indigo_bus.h. The description of the INDIGO protocols used for communication is available in PROTOCOLS.md. INDIGO uses XML or JSON transport protocols for message passing. The list of the well known properties is available in PROPERTIES.md.ĭifferent instances of the INDIGO bus can be connected in a hierarchical structure, but from a driver or a client point of view it is fully transparent.

Each device class has a set of mandatory properties that should always be defined, a set of optional properties that may or may not be defined and a set of device specific properties which may not exist if there is no need. There are three classes of properties: mandatory, optional, and device specific. request for change of property item values - client can request change of the values of one or several property items.request for enumeration of available properties - client can request the definitions of one or all available properties associated with the device.The messages sent from a client to the device can be: deletion of a property - lets the client know that the property is removed and can not be used any more.

#Indigo server remove update#

update of property item values - lets the client know that certain property items have changed their values.

definition of a property - lets the client know that the property can be used, the message contains the property definition: name, type, list of items etc.

The messages sent from the device to a client may contain one of the following events: Messages sent over the INDIGO bus are abstraction of INDI messages. Set of variables as they may store values like the width and height of the CCD frame or routines like start 1 second exposure. One can think of the properties as both set of variables and routines. Properties on the other hand contain one or more items of a specified type. The communication between different entities attached to the bus is done by INDIGO messages which contain property events. INDIGO is asynchronous in its nature, so to be able to communicate over the bus, the client and device have to register a structure containing pointers to callback functions which are called by the INDIGO bus upon specific events.

#Indigo server remove code#

A piece of code registering one or more devices on the bus is referred as the driver.

These entities are typically either in a device or a client role, but there are special entities often referred as agents which are in both device and client role.

#Indigo server remove software#

INDIGO is a platform for the communication between software entities over a software bus.