status of intercommunication on feecontrol

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

FEE Server(DIM - Server on RCU - Card)

FEE Server(DIM - Server on RCU - Card)

FEE Server(DIM - Server)

PVSS Server(DIM - Server)

FEE Client(DIM - Client)

InterCom Layer(Application layer)

DatabaseAccess

PVSS Client (DIM - Client) Layers

2003-09-08, http://www.ztt.fh-worms.de


CE (Detector specific)


TOC

• Interface FeeServer - ControlEngine

• Sequence of communication FeeServer - ControlEngine

• Data access on InterComLayer


Interface FeeServer - Control Engine



Interface called by implemented by amount of calls

void initializeCE() FeeServer CE once

int publish(...) CE FeeServer zero to several times on start up

void signalCEready() CE FeeServer once

int issue(...) FeeServer CE n - times

void cleanUpCE() FeeServer CE once

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)




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




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.



int issue(char* command, char** result, int* size)

FeeServer relays a command to the CE and retrievesthe 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



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





void cleanUpCE()

Tells CE to clean up to shut down properlywhen the FeeServer exits.



FeeServerinit process

CEinitializeCE()

signalCEready()

publish(Item*)

start server

Sequence of Communication(initialization, called once)



FeeServercommandreceived

CEissue(...)

return result

deliver resultto FeeClient

Sequence of Communication(serving state, executed n-times)

executeCommand



FeeServerexit - command

received

CE

cleanUpCE(...)

clean up FeeServerand exit

Sequence of Communication(clean up, called once)

do the cleanup stuff



Data access on InterComLayer

• Structure of Database ???

• Naming conventions ???

• When will it be defined ???

?

status of intercommunication on feecontrol

Documents