7.3 Booting

7.3.2 EPICS / VxWorks example

The above requirements can be met by an EPICS / VxWorks system in the following way. Other environments can presumably employ corresponding strategies.

1. the subsystem sequence will handle this and will maintain its state in k2:ao:ss:state, where ss is the subsystem mnemonic

2. the VxWorks boot parameters will reference a start-up script which will load and start EPICS and application software (note: VxWorks systems typically boot via Ethernet from a Unix host machine)

3. code which references EPICS variables from other processors must be written to expect these variables occasionally to disconnect and reconnect (Keck II DCS EPICS sequences contain such logic)

4. each processor will indicate whether it is running in k2:ao:ss:proc:state, where proc identifies the processor

5. each processor will support k2:ao:ss:proc:reboot to control a warm reboot

6. VME bus reset lines will be wired to digital outputs controllable from the UI via EPICS variables (accessed via a terminal server port?)

Generated with Harlequin WebMaker