Spelling and typos
r2008 | dcl | 2007-06-13 10:05:00 +1000 (Wed, 13 Jun 2007) | 2 lines
This commit is contained in:
Douglas Clowes
22
emonitor.tex
22
emonitor.tex
@ -18,15 +18,15 @@ maintained.
|
||||
\end{itemize}
|
||||
|
||||
Controller objects will be able to share some code among them. Each
|
||||
environemnt controller will hold a target value, a permissable tolerance,
|
||||
a selctor variable which defines the type of error handling to perform and
|
||||
an interrupt code to issue when that form of error handling is choosen.
|
||||
environment controller will hold a target value, a permissible tolerance,
|
||||
a selector variable which defines the type of error handling to perform and
|
||||
an interrupt code to issue when that form of error handling is chosen.
|
||||
Furthermore each environment controller needs to implement the drivable
|
||||
interface (for driving to new values) and the environment interface (for
|
||||
monitoring the controller). Controller object will also share the error
|
||||
monitoring the controller). Controller objects will also share the error
|
||||
handling during the monitor phase between them. The scheme is that each controller will have a
|
||||
variable which selects the error handling mechanism. Depending on this
|
||||
variable an error managment routine will be invoked. Current two schemes for
|
||||
variable an error management routine will be invoked. Current two schemes for
|
||||
handling errors are supported:
|
||||
\begin{itemize}
|
||||
\item Print a warning but do nothing else.
|
||||
@ -57,7 +57,7 @@ controllers. It will be called from the main loop to check if each
|
||||
registered environment controller is still within tolerances. If not, emon
|
||||
has to enforce error processing. Else it does nothing.
|
||||
|
||||
The environment monitor uses the following datastructures:
|
||||
The environment monitor uses the following data structures:
|
||||
\begin{flushleft} \small
|
||||
\begin{minipage}{\linewidth} \label{scrap1}
|
||||
$\langle$emondat {\footnotesize ?}$\rangle\equiv$
|
||||
@ -90,8 +90,8 @@ As it it will be accessible as SICS object emon needs an object descriptor.
|
||||
The other data member is a list of active controllers.
|
||||
|
||||
The EVEntry structure contains the data held in the list for each active
|
||||
controller. It is, disguised as pDum, a pointer to the controllers
|
||||
datastructure, the name of the controller, and the environment interface of
|
||||
controller. It is, disguised as pDum, a pointer to the controller's
|
||||
data structure, the name of the controller, and the environment interface of
|
||||
the controller.
|
||||
|
||||
The following interface is implemented by the environment monitor:
|
||||
@ -143,7 +143,7 @@ controller.
|
||||
\item {\bf pName}. The name of the controller object.
|
||||
\item {\bf pData}. A pointer to the data structure belonging to the
|
||||
controller object.
|
||||
\item {\bf pCon}. A pointer to the client connection to which erros shall be
|
||||
\item {\bf pCon}. A pointer to the client connection to which errors shall be
|
||||
reported.
|
||||
\end{itemize}
|
||||
|
||||
@ -160,7 +160,7 @@ specified.
|
||||
{\bf EVWrapper} is the wrapper function necessary to make the emon
|
||||
available from SICS. The user may interact with the emon through SICS. The
|
||||
user will be enabled to list the currently registered environment
|
||||
controllers and their current state and to register and unnregister
|
||||
controllers and their current state and to register and unregister
|
||||
controllers.
|
||||
|
||||
{\bf EnvMonTask} is the task function associated with the environment
|
||||
@ -168,7 +168,7 @@ monitor. This is called by the task handling object and eventually
|
||||
invokes EVMonitorControllers for checking on the environment
|
||||
controllers configured into SICS.
|
||||
|
||||
{\bf EnvMonSignal} is the signale handler for the environment monitor task.
|
||||
{\bf EnvMonSignal} is the signal handler for the environment monitor task.
|
||||
|
||||
\begin{flushleft} \small
|
||||
\begin{minipage}{\linewidth} \label{scrap3}
|
||||
|
||||
20
emonitor.w
20
emonitor.w
@ -18,15 +18,15 @@ maintained.
|
||||
\end{itemize}
|
||||
|
||||
Controller objects will be able to share some code among them. Each
|
||||
environemnt controller will hold a target value, a permissable tolerance,
|
||||
a selctor variable which defines the type of error handling to perform and
|
||||
an interrupt code to issue when that form of error handling is choosen.
|
||||
environment controller will hold a target value, a permissible tolerance,
|
||||
a selector variable which defines the type of error handling to perform and
|
||||
an interrupt code to issue when that form of error handling is chosen.
|
||||
Furthermore each environment controller needs to implement the drivable
|
||||
interface (for driving to new values) and the environment interface (for
|
||||
monitoring the controller). Controller object will also share the error
|
||||
handling during the monitor phase between them. The scheme is that each controller will have a
|
||||
variable which selects the error handling mechanism. Depending on this
|
||||
variable an error managment routine will be invoked. Current two schemes for
|
||||
variable an error management routine will be invoked. Current two schemes for
|
||||
handling errors are supported:
|
||||
\begin{itemize}
|
||||
\item Print a warning but do nothing else.
|
||||
@ -57,7 +57,7 @@ controllers. It will be called from the main loop to check if each
|
||||
registered environment controller is still within tolerances. If not, emon
|
||||
has to enforce error processing. Else it does nothing.
|
||||
|
||||
The environment monitor uses the following datastructures:
|
||||
The environment monitor uses the following data structures:
|
||||
@d emondat @{
|
||||
typedef struct __EnvMon {
|
||||
pObjectDescriptor pDes;
|
||||
@ -77,8 +77,8 @@ As it it will be accessible as SICS object emon needs an object descriptor.
|
||||
The other data member is a list of active controllers.
|
||||
|
||||
The EVEntry structure contains the data held in the list for each active
|
||||
controller. It is, disguised as pDum, a pointer to the controllers
|
||||
datastructure, the name of the controller, and the environment interface of
|
||||
controller. It is, disguised as pDum, a pointer to the controller's
|
||||
data structure, the name of the controller, and the environment interface of
|
||||
the controller.
|
||||
|
||||
The following interface is implemented by the environment monitor:
|
||||
@ -118,7 +118,7 @@ controller.
|
||||
\item {\bf pName}. The name of the controller object.
|
||||
\item {\bf pData}. A pointer to the data structure belonging to the
|
||||
controller object.
|
||||
\item {\bf pCon}. A pointer to the client connection to which erros shall be
|
||||
\item {\bf pCon}. A pointer to the client connection to which errors shall be
|
||||
reported.
|
||||
\end{itemize}
|
||||
|
||||
@ -135,7 +135,7 @@ specified.
|
||||
{\bf EVWrapper} is the wrapper function necessary to make the emon
|
||||
available from SICS. The user may interact with the emon through SICS. The
|
||||
user will be enabled to list the currently registered environment
|
||||
controllers and their current state and to register and unnregister
|
||||
controllers and their current state and to register and unregister
|
||||
controllers.
|
||||
|
||||
{\bf EnvMonTask} is the task function associated with the environment
|
||||
@ -143,7 +143,7 @@ monitor. This is called by the task handling object and eventually
|
||||
invokes EVMonitorControllers for checking on the environment
|
||||
controllers configured into SICS.
|
||||
|
||||
{\bf EnvMonSignal} is the signale handler for the environment monitor task.
|
||||
{\bf EnvMonSignal} is the signal handler for the environment monitor task.
|
||||
|
||||
@o emon.h -d @{
|
||||
/*--------------------------------------------------------------------------
|
||||
|
||||
Reference in New Issue
Block a user