Bill Sahr EVLA Advisory Committee MeetingSeptember 8-9, 2003

1

EVLA Monitor & Control

EVLA M&C and e2e Software

Proposal Tool

Proposal generationand submission

Observing Tool

Program blocks forsubmission to

Scheduling Tool

Scheduling Tool

Sends schedulingblocks (SBs) to M&C

system

Archive

Monitor Data

Quick-Look Pipeline(QLP)

Astronomer's"What's Up"

Screen

Default Archive ImagePipeline

Atmospheric Model

/users/bsahr/EVLA/architecture_design/overall_design/evla_m&c_e2e.vsd, 8/2003

PBs

MIB Devices

CALC

EVLA M&CObserving Layer

Cmnds

CorrelatorBack End

WIDARCorrelator

EVLA M&C and e2e software

Raw AntennaData

RTCAT output- goes to the M&C system- is archived- is to be available to the Quick Look Pipeline- is to be available to the Astronomer's What's Up Screen

The EVLA SSR requires that the timebetween data collection by the real-timesystem and its availability to the QLP be

< 30 seconds.

Activationevent

The EVLA SSR requires that the time-lagbetween when data is collected by the real-time system or produced by the Quick-Look

Pipeline and when it is available to the "What'sUp" screen should be < 10 seconds.

Activationevent

Fast Data Store

Archive

Visibility Data

- Antenna gains- Autophasing info- pointing solutions- focus determinations

SBs, including Control Scripts

Real-Time CalibratorAnalysis Tool

(RTCAT) FormatterSharedMemory

(?)

MCCC

CMIBsVCI

Bill Sahr EVLA Advisory Committee MeetingSeptember 8-9, 2003

3

Requirements

We now have requirements produced by the NRAO user community rather than Computer Division internally generated documents.• EVLA e2e Science Software Requirements, April 15, 2003• EVLA Data Post-Processing Software Requirements, July 3, 2003• EVLA Array Operations Software Requirements, June 6, 2003• EVLA Engineering Software Requirements, August 8, 2003• EVLA Science Requirements for the Real-Time Software, to be

started 9/2003• Scientific Requirements for the EVLA Real-Time System, Sept, 2000

EVLA M&C Software

/users/bsahr/EVLA/architecture_design/overall_design/evla_m&c_01.vsd 8/2003

CALC

CorrelatorBack End

WIDARCorrelator

Raw AntennaData

RTCAT output- goes to the M&C system- is archived- to the Quick Look Pipeline- to the Astronomer's What's Up Screen

Activationevent

- Antenna gains- Autophasing info- pointing solutions- focus determinations

CMIBs

real timeobservation

queue

controlscripts(jython)

configuration andmetadata Correlator config,

metadata, ? viaCMIBS

CBE config &metadata

monitor data,flagging, alarms

TCP/IP ?

commands

EVLA Antenna

ArchiverMonitor data

database(Oracle)

monitordata

ProxyServer

Observing Layer

remote cmnds &monitor data

Cur

Prv

Nxt

ArchiveVisibility Data

Real-Time CalibratorAnalysis Tool

(RTCAT)SharedMemory

Fast DataStore

Formatter

MCCC

VCI

PrvCurNxt

system parametersdatabase(Oracle)

Antenna

Feed Rcvr IF System

LO

DTS

Servo

Ready

InProgress

Bill Sahr EVLA Advisory Committee MeetingSeptember 8-9, 2003

5

Antenna MIBs

• MIB – Module Interface Board– Refers to the TC11IB processor board that will be used

to control antenna subsystems– 96 MHZ processor– 1.5 Mbytes on-chip RAM– 8 Mbytes Flash– SPI bus– GPIO (parallel I/O lines)– Ethernet Interface

Bill Sahr EVLA Advisory Committee MeetingSeptember 8-9, 2003

6

Antenna MIB Software

• Quality of the MIB software is seen as crucial to the quality of the EVLA M&C software

• The MIB software consists of:– Systems software– MIB framework software– Module software

Bill Sahr EVLA Advisory Committee MeetingSeptember 8-9, 2003

7

MIB Systems Software

• RTOS kernel• Network stack• Telnet server

– Automatically activates the shell• Shell

– Shell provides memory display and memory modification– Shell is being extended to provide module specific

commands & displays• All of the systems software is up and running on MIB

hardware

Bill Sahr EVLA Advisory Committee MeetingSeptember 8-9, 2003

8

MIB Framework Software

• Common to all MIBs• Device definition, instantiation, and initialization• A data port, broadcasts monitor data• A service port

– Accepts time-tagged commands

– Information services

• C++, ASCII text, XML, Xpath (likely),

Bill Sahr EVLA Advisory Committee MeetingSeptember 8-9, 2003

9

MIB Module Software

• HW module specific, chiefly written in C

• Responsible for– Device Control

– Collection of monitor point values

– Warnings, errors, alarms

• L301 (12-20 GHZ synthesizer) module software has been tested

• L302 (10.8-14.8 GHZ synthesizer) module software currently under development

Bill Sahr EVLA Advisory Committee MeetingSeptember 8-9, 2003

10

Device Browser

• Generic, discovery-based, remote client application – Obtains a list of all devices connected to a MIB

– Obtains a list and description of all monitor and control points associated with a device

• Can display any/all monitor point values for a device

• Can modify monitor point attributes

• Can be used to command devices

• Peek/Poke capabilities

• Multiplatform, written in Java

Bill Sahr EVLA Advisory Committee MeetingSeptember 8-9, 2003

11

ALMA/EVLA Cooperation

• At the low levels there is little commonality between the AMLA & EVLA M&C systems. The differences are driven by differences in the hardware.

• We hope sharing can occur at the higher levels of the two systems.

• Ralph Marson of ALMA and I have agreed to begin monthly meetings to explore the possibilities for sharing designs and code at the higher levels of the two systems.

Bill Sahr EVLA Advisory Committee MeetingSeptember 8-9, 2003

12

Questions/Issues

• Are we headed in the right direction ?

• Overall design ?– Have we now positioned ourselves to produce a

high quality overall design?