Status of InterCommunication on FeeControl

1. Status of InterCommunication on FeeControl Meeting Report Communication between DCS-Layers State of 2003-09-08 Sebastian Bablok Christian Kofler Ralf Keidel http://www.ztt.fh-worms.de

2. Status of InterCommunication on FeeControl PVSS Client (DIM - Client) Layers PVSS Server (DIM - Server) Database Access InterCom Layer (Application layer) FEE Client (DIM - Client) FEE Server (DIM - Server on RCU - Card) FEE Server (DIM - Server on RCU - Card) FEE Server (DIM - Server) CE (Detector specific) 2003-09-08, http://www.ztt.fh-worms.de

3. Status of InterCommunication on FeeControl TOC • Interface FeeServer - ControlEngine • Sequence of communication FeeServer - ControlEngine • Data access on InterComLayer 2003-09-08, http://www.ztt.fh-worms.de

4. Status of InterCommunication on FeeControl Interface FeeServer - Control Engine 2003-09-08, http://www.ztt.fh-worms.de

5. Status of InterCommunication on FeeControl Interface FeeServer  Control Engine void initializeCE() • Initializes the ControlEngine on the board. • bus driver can be loaded • Items for monitoring can be published • runs in its own thread (controlable from FeeServer) 2003-09-08, http://www.ztt.fh-worms.de

6. Status of InterCommunication on FeeControl Interface FeeServer  Control Engine int publish(Item* item) • Informs FeeServer about values for monitoring. • gives „Item“ to the FeeServer • name (char*) and location (volatile float*) [value] • returns an error code, if call was unsuccessful, else 0 • has to be called for every Item to be published 2003-09-08, http://www.ztt.fh-worms.de

7. Status of InterCommunication on FeeControl Interface FeeServer  Control Engine void signalCEready() • Informs FeeServer that initialization has been finished • the termination of this thread is in charge of the CE • the init - thread has to continue, if „publish()“ • has been called. 2003-09-08, http://www.ztt.fh-worms.de

8. Status of InterCommunication on FeeControl Interface FeeServer  Control Engine int issue(char* command, char** result, int* size) • FeeServer relays a command to the CE and retrieves • the result of it. • command: pointer to the command data • (allocated and freed by FeeServer) • result: pointer to the pointer where CE stores the • result data (allocated by CE, freed by FeeServer) • size: when called: size of command, • when returning: size of result 2003-09-08, http://www.ztt.fh-worms.de

9. Status of InterCommunication on FeeControl Interface FeeServer  Control Engine int issue(char* command, char** result, int* size) • returns an error code, if call was unsuccessful, else 0 • is executed in an own thread to determine if CE is • working (Watchdog) • thread will be terminated by FeeServer after timeout, • if CE gets stuck 2003-09-08, http://www.ztt.fh-worms.de

10. Status of InterCommunication on FeeControl Interface FeeServer  Control Engine void cleanUpCE() Tells CE to clean up to shut down properly when the FeeServer exits. 2003-09-08, http://www.ztt.fh-worms.de

11. Status of InterCommunication on FeeControl Sequence of Communication (initialization, called once) FeeServer init process CE initializeCE() publish(Item*) signalCEready() start server 2003-09-08, http://www.ztt.fh-worms.de

12. Status of InterCommunication on FeeControl Sequence of Communication (serving state, executed n-times) FeeServer command received CE issue(...) execute Command return result deliver result to FeeClient 2003-09-08, http://www.ztt.fh-worms.de

13. Status of InterCommunication on FeeControl Sequence of Communication (clean up, called once) FeeServer exit - command received CE cleanUpCE(...) do the clean up stuff clean up FeeServer and exit 2003-09-08, http://www.ztt.fh-worms.de

14. Status of InterCommunication on FeeControl Data access on InterComLayer • Structure of Database ??? • Naming conventions ??? • When will it be defined ??? ? 2003-09-08, http://www.ztt.fh-worms.de