- First working version of the TRICS collision protection module
This commit is contained in:
14
devexec.w
14
devexec.w
@ -175,6 +175,17 @@ take care of invoking the apropriate commands on all registered counting
|
||||
devices.
|
||||
|
||||
|
||||
\subsubsection{Locking the Device Executor}
|
||||
In some instances user code may wish to lock the device executor. An
|
||||
example is a long running data saving operation. In order to do this
|
||||
two functions are provided:
|
||||
|
||||
@d devlock @{
|
||||
void LockDeviceExecutor(pExeList self);
|
||||
void UnlockDeviceExecutor(pExeList self);
|
||||
|
||||
@}
|
||||
|
||||
\subsubsection{The Rest}
|
||||
The rest of the interface includes initialisation and deletion routines
|
||||
and some access routines. With the devexec being such an important system
|
||||
@ -266,7 +277,8 @@ to the global SICS device executor.
|
||||
connection with non blocking operation such as motors started
|
||||
with run.
|
||||
*/
|
||||
|
||||
/*--------------------------- Locking ---------------------------------*/
|
||||
@<devlock@>
|
||||
/* -------------------------- Executor management -------------------------*/
|
||||
|
||||
pExeList GetExecutor(void);
|
||||
|
Reference in New Issue
Block a user