7.0 IMPLEMENTATION

7.3 Booting

The AO system consists of five subsystems, each of which executes on one or more processors.

AO subsystems and their software environments
Subsystem	Environment	Notes
User Interface (UI)	KTL / EPICS / Solaris / S-bus	processor also runs non-AO tasks
Supervisory Control (SC)	EPICS / VxWorks / VME	processor is dedicated to SC[4]
Optical Bench (OBS)	EPICS / VxWorks / VME	processor is dedicated to OBS<Superscript><Superscript>a
Wavefront Controller (WFC)	EPICS / Solaris / VME	processors are dedicated to WFC
Laser (LS)	EPICS / VxWorks / VME	processors are dedicated to LS

As can be seen from Table 7-5, UI does not run on a dedicated processor. The only involvement of UI in the booting process is that it will provide a screen from which the rest of the system is booted.

Booting may imply any of:

unconditionally resetting all processors and allowing them to boot
resetting only those processors which correspond to a given subsystem
resetting only those processors which are not currently running
resetting nominated processors

The first is the simplest. The others are desirable for efficient operation and can be handled relatively easily if all subsystems and processors provide the necessary control and status.

EPICS sequences take no part in the booting process. Each processor boots independently of any other processor. Sequences are started on completion of booting, at which point all EPICS databases have been initialized and are in a known state.

[4] SC and OBS will be in the same VME crate. They may share the same processor.

7.3.1 - Booting subsystems and processors
7.3.2 - EPICS / VxWorks example

AO Software Design Book - 25 FEB 1997

Generated with Harlequin WebMaker

Back to the Keck Home Page

Back to the Keck AO Page