![]() ![]() Dazzling to look at, this unexpected intruder in the heavenly vault gave off a light that almost rivaled that of the full Moon, drowning out the familiar patterns of stars with its glare. Nobody could remember having seen its like before. If no driver_name is specified, the first driver in INDI server that matches driver_path_name will be stopped.SketchingtheSkies Suddenly and without warning, a new star appeared in the night sky, and everyone in the community was alarmed. But if you are running more than one instance of the driver, you should also specify the driver_name. To stop a driver, you must specify the driver_path_name at least. When redirecting commands to FIFO via echo, ensure to add blackslash to quotes so that they do not get escaped:Įcho "start indi_lx200generic -n \"My ETX 90\"" > myFIFO It is critical to enclose all optional variables (driver_name, driver_config_path_name, and skeleton_file_path_name) with double quotation marks when issuing FIFO commands.įor example, to start indi_lx200generic driver, but with two driver names (LX90 and "My ETX 90"), we write to FIFO start indi_lx200generic -n "LX90" ![]() All drivers based on INDI::DefaultDriver automatically check the environment variable and set the device name accordingly. It is important to note that INDI server only defines these environment variables, and it is up to the driver to read and utilize them upon startup. These variables are set to environment variables INDIDEV, INDICONFIG, and INDISKEL respectively. Finally, skeleton_file_path_name designates the skeleton file to be used for this driver if desired. The optinal driver_config_path_name specifies the configuration file to be used, if any. The driver_name parameter is optional and specifies the name of the driver to be defined to the client. To use INDI server in FIFO mode, first create a FIFO. ![]() If it does exit, it prints a message to stderr and exits with status 1. Indiserver is intended to run forever and so never exits normally. Conversely, remote connections specify the name of the Device, irrespective of the name of its Driver program. Note well that local programs specify the name of the executable file, not the Device it implements. The program is presumed to implement the INDI protocol on its stdin and stdout channels, and may send ad-hoc out-of-band error or trace messages to its stderr which gets merged in with the indiserver stderr.Ī remote Device is given in the form where device is the INDI device already available on another running instance of indiserver, host is the TCP host name on which said instance is running and the optional port is the port on which to connect if other than the standard port 7624. A local program is specified as the path name of the execuble to run. r r : maximum driver restarts on error, default 10.Įach additional argument can be either the name of a local program to run or a specification of an INDI Device on a remote indiserver. m m : kill client if gets more than this many MB behind, default 10 -p p : alternate IP port, default 7624 -f path : Path to fifo for dynamic startup and shutdown of drivers. l d : log driver messages to /YYYY-MM-DD.islog The syntax for INDI server is as following: $ indiserver driver Typical INDI Client / Server / Driver / Device connectivity is illustrated in Figure 2: If desired, a client may run and connect to INDI Drivers directly. ![]() indiserver only provides convenient port, fork, and data steering services. indiserver launches each driver process and arranges for it to receive the INDI protocol from clients on its standard input (stdin) and expects to find commands destined for clients on the driver's standard output (stdout).Īnything arriving from a driver process' stderr is copied to indiserver's stderr. INDI server is the public network access point where one or more INDI clients may contact one or more INDI Drivers. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |