AO Control and Automation Software

1
AO Control and Automation Software

• Thang Trinh
• (and David Hale)
• PALM-3000 Software Preliminary Design Review
• February 2, 2009

2
AO Control and AutomationSoftware Top-Level
Design

• Purpose To provide a preliminary top-level
  design for the P3K AO Control and Automation
  (AOCA) component.
• Software Architectural Constraints
• Conform to PALM-3000 software architecture as
  specified in the SWAD (e.g., component-based
  architecture).
• Use Publish/Subscribe framework for data and
  control.
• Software Design Requirements
• AO automation requirements as specified in the
  PALM-3000 SWRD.
• AO automation functions shall be externally
  callable (e.g., from IDL scripts)
• Support existing external system interfaces.

2
3
AOCASoftware Context Diagram

IDL Scripts
GUI
AOCA
Publish/ Subscribe
AODB
TCS
Science Instruments
Commands
Data
4
AOCASoftware Top-Level Design
Prim Cmds

Publish/ Subscribe
Cmd Dispat-cher
AO Cmds
AO Status
OffldTT.Start OffldTT.Cancel
AFn.Start AFn.Cancel
RegDM.Start
AFn
Offload TT
Reg DM
Prim Cmds
Prim Cmds
Tlm Data
Tlm Data
Tlm Data
Publish/ Subscribe
Prim Cmds
AODB
5
AOCASoftware Top-Level Design

• Command Dispatcher
• Implemented as nesC component
• Provide AO command and automation interface
  (e.g., to the operator via the Graphical User
  Interface component).
• Validate and manage the execution of commands
  sent to the AO system.
• Publish validated AO primitive commands.
• Activate requested AO automation functions.
• Subscribe to AO status.
• Resource management
• Support existing external system interfaces via
  socket-based Net Services.
• Automation Functions (AF)
• Independent nesC components running concurrently
  in user threads.
• Activated/canceled by the Command Dispatcher on
  users request.
• Perform single AO automation procedure.
• Publish sequence of one or more primitive AO
  commands.
• Subscribe to AO telemetry data.
• Command TCS as required.
• Special Purpose Ports
• E.g. TCS broadcast messages (1 Hz)
• All connections on DB port publish incoming data

6
Command Example Primitive
validation
GUI
CD
Device Driver
MOTOR IDname POSxxxx
DEVICE
TCP/IP
Publish/ Subscribe
7
Command Example Automation
validation
IDL
CD
RegDM.Start
TCP/IP
Publish/ Subscribe
8
AOCA Command Flow

• Client sends command to AOCA Server over TCP
  socket
• Clients can be GUI, IDL, Science Instruments
• GUI subscribes to Status
• Command Dispatcher validates command
• Command may be primitive or automation
• Command arguments are not checked by the
  dispatcher
• Command Dispatcher provides immediate reply
• Acknowledgement of receipt of valid command, or
  error if invalid
• No command syntax checking here
• Command Dispatcher acts on command
• Primitive
• Publish the command
• Subscribes to Status
• Automation
• Spawns thread which calls appropriate Automation
  Function (AFn)
• Automation Function Publishes Status

9
AOCA Software DesignNext Steps

• P3K AO Software Architectural Design
• Design/extend AO command set with AF command set.
• AOCA Software Detailed Design
• Identify all AO automation functions.
• Specify nesC components and their respective nesC
  interface.
• Provide detailed design for all external/internal
  data interfaces.