Server Configuration

Operating and Configuring a Live odin-control Server on LOKI systems

Background

LOKI-based control systems provide their control interface using an instance of odin-control, a modular framework for control system development. This instance is brought up with an application-specific adapter, which will be developed as part of system integration with hardware. This guide assumes that the adapter has already been developed- odin-control adapter development is out of scope. See LOKI-based Adapter Creation.

By default, this adapter will run automatically on boot, and present a web interface on port 8888. The HTTP REST API can be accessed via the same port.

Starting and Stopping the odin-control Service

The PetaLinux image produced for LOKI uses System V scripts to control services. Currently, it is only possible to control the service while logged in to the device over SSH or UART.

There are helper aliases to stop and restart the server (as root; use su -):

# loki_stop_app
# loki_restart_app

Alternatively, use the init script to start, stop, and restart the odin-control server directly (as root):

# /etc/init.d/loki-config.sh start
# /etc/init.d/loki-config.sh stop
# /etc/init.d/loki-config.sh restart

Accessing odin-control Logs

By default, the instance will output logs to /var/log/loki/detector.log. This file can be read by the loki user, and is accessible from a logged in terminal only (unless redirected to a network mounted location).

Remounting the Host Mountpoint

System V scripts are relatively primitive, and do not have dependencies. Therefore , you should stop the control service while you restart this one.

# /etc/init.d/loki-config.sh stop

#TODO

• Background; this is more aimed at general use
• Unique system identifiers
• Starting and stopping the odin-control server
• Link to 'process for creating odin-control instance' wiki article
• Control Host intention and functionality
• odin-control hosted configuration file
• Link to 'creating live virtual environments'