\documentstyle[11pt,a4wide]{article}
\begin{document}
%
\title{\bf Resource Manager VXI meeting}
\date{Strasbourg, 31-July-1990}
\author{Marie Madeleine Al\'eonard}
\maketitle
\begin{center}
\small
{\bf Pr\'esents:} M.M. Al\'eonard, Ch. Ender, B. Humbert, P. Kadionic, F.
K\"ock, Ch. Ring.
\end{center}
%
%
\vspace{2.0cm}
%
%
 This meeting was held to coordinate software development for the Resource
Manager VXI card, following the 17th july Daresbury meeting.
 
 It was first recalled, according to PSC documents,
 that for the RM software B.\ Humbert in France and
 V.\ Pucknell
 in UK are the responsible persons; while for the hardware these are
respectively Ch.\ Ring and P.J.\ Coleman-Smith.
 
The collaboration and contribution of both Ch.\ Ender and Frank K\"ock from
Heidelberg were greatly welcomed and this meeting was the starting point of a
detailed collaboration.
%
%
 
\section{VXI "scope" functionality :}
 
 As a result of the Darebury meeting (july 17th) Ch. Ender is in charge of
developping flash ADC for pulse analysis of some  VXI lines. It was agreed
that Ch. Ender would be also in charge of developping the appropriate
 software. But we are first expecting a full specifications document by
mid-august. The prototype is expected end of year.
%
%
\section{Software  for the Resource Manager and VXI crate controller
board: }
 This VXI board has 2 functions:
\begin{itemize}
 
\item Slot 0 RM function related to standard VXI definitions. In this respect
 only the mandatory and needed spec  for EUROGAM (i.e.\ Register based RM
 function) would be implemented.
\item Crate controller functions.
\end{itemize}
 
\subsection{Resouce Manager subset sofware}
 A document will be produced on all startup procedures, keeping in mind that
for development, VxWorks will be available both in France and UK and some
  of its features will be very usefull. The aim is to have  an autoboot
configuration. For this a PROM autoboot will be needed. To manage a wide
 kind of situations the minimum VXI configuration will be Promed: the
RM autoconf and test(?) and the  autoconfiguration of the VXI boards located
in the crate, this the  first step of a start up phase ($\leq$ 5s).
 
 
The second phase is in relation with the data base for further diagnostics.
In principle the VXI card do not undergo an autotest since they are
processorless, hence the RM software should provide boards'tests in relation
with the data base where all the parameters of the configuration are stored.
At this point 2 solutions are in view:
%
%
\begin{itemize}
\item the RM (now a crate controller) waits for {\it a "claim crate" procedure}
 from any acquisition software which {\bf should} provide it. Appropriate bits
 will be set in the "status report" register for the  claim crate procedure.
A document will be provided; bits will range from "power crate" to
 "crate available and fully in function".
%
%
\item the RM sends to the "acquisition system" a broadcast-all-RPC "i am awake"
with an appropriate status.
 Repeat it for some time and goes asleep.
\end{itemize}
 
%
%
 Some feedback is needed on this aspect: both ways may be implemented (?).
Some aspects of the first exchange on the ethernet may be dependent of the
local network and acquisition software.Some of us feeled that the "Acquisition
 system" should always remain the master, and some view the other aspect.
 
%
%
\subsection{Database software aspects}
 The data base is related in several ways to the RM. Through the desciption of
the VXI boards (module type, characteristics... ) needed for tests at start up,
 and through the parameters needed to be loaded to start an acquisition
whichever the complexity of the setup. Other aspects such as on line
 checkings, tuning ... are also to be managed.
 
It was feeled that this aspect needed a discussion with David Brightly
 in charge of the Data Base. A document will be submitted for discussion.
%
%
 
 
\subsection{Crate contoller VXI functions}
 As soon as the first phase of the VXI autoconfiguration is done the RM
can be viewed as a crate controller with the following  VXI functionnalities.
 
 
\begin{itemize}
\item {\it Diagnostics :} {\bf This need to know  the local structure of the
data base} in each VXI crate. Checks of consistancy of module type, ... ,check
of parameters loaded in card versus the data base.
 
\item {\it  In tuning phase:} change parameters...
At least have specific processes i.e bloc transfers r/w ... need ad hoc RPC
 or file management or agreed procedure. need to use the appropriate spectrum
structure, may use the NFS ? for spectrum transfers it is during tuning.
 
\item {\it Test phase:} allows all manipulations of registers and memories via
 the network (this is already provided by VxWorks), builds spectrum in memory.
All calculations or graphics display are performed on a remote station (at
least in a fisrt stage).
 
\item {\it RM procedures:} some crate controller procedures typical of th VXI
carte controller may be: initialise module, read module configuration, write
module configuration, get module description, error handling(?), ... . A
document will be provided for that.
\end{itemize}
 
%
%
\subsection{RPC software}
>From the previous remarks some specific VXI procedures may be needed and
document will be provided for. It is under study at CRN to explore the
possibilities of Sun RPC and  VxWorks for task management and file transferts.
We are relying on Daresbury for specific RPC and design of the data base
 
 
%
%
\section{Summary: priorities and responsabilities}
\begin{enumerate}
\item Document of software specifications for RM and VXI crate controller:\\
 {\bf C Ender to provide spec mid august}.
 
\item test code for first level autoconfiguration in RM (no PROM yet):   \\
{\bf Ch. Ender in corelation with B.Humbert} for checkings (several CPU
 are used, it would be good to have in the future some other VXI cards ).
Checkings of the RM boards from Struck: end september in Strasbourg.
 
\item Basic diagnostics (registers,memories..):{\bf B.Humbert }
 
\item Full data base specifications. Need feedback with D.Brightly.\\
{\bf Some document to be forwarded for discussion  by C.Ender }. Expected final
spec end of 1990.
 
\item Full diagnostics {\bf B.Humbert and P.Kadionik}. With or witout the data
 base specs a preliminary release IS NEEDED end of 1990!
 
\item  Specifications of flash ADC: {\bf Document provided by Ch. Ender mid
august}.
 
\item Prototype for "scope functionality" of RM: end of the year for hard and
software.
\end{enumerate}
 
%
%
{\small\bf Note: although noted 6 and 7 in the priorities these points are of
great interest and will be needed for boards testing as soon as the VXI cards
are ready.}
 
%
%
\end{document}