1. Recent developments of communication between DOOCS & ODR B Valeria Bartsch M Andrzej Misiejuk W Tao Wu

2. How to communicate? ODR LDAs ODR Control Interface Storage DOOCS Device server Stream Sockets ENS DOOCSClients GUIRPC/Display Results

3. Mockup version of device server eq_init_prolog(); EqFctODR::init() eq_init_epilog(); EqFct * eq_create EqFctODR::update(); refresh_epilog(); refresh_prolog(); Build a socket stream in the heap or stack, Set ODR Header params Activate a device server & create device instances Send/Recv messages via socket stream, update data every period. If device offline, Delete socket stream

4. Sending and Receiving data containing ODR/LDA headers from DOOCS to ODR Control interface have been tested; Talk to ODR Control Interface ODR LDAs ODR Control InterfaceDOOCS Device server Stream Sockets ENS DOOCSClients GUIRPC/Display Results ODR 1 RcvMsgFromODRSendMsgToODR Build Socket Stream HostPort Control parameters Nice

5. One-to-many relationship: One device server can serve many instances, i.e. many ODR cards armed in different DAQ PC. One server, many instances ODR LDAs ODR Control InterfaceDOOCS Device server Stream Sockets ENS DOOCSClients GUIRPC/Display Results ODR 1 RcvMsgFromODRSendMsgToODR Build Socket Stream ODR 2 ODR 3 HostPort Port Port Host+Port number can be same or different. Nice

6. Hostname & Port number Hostname + Port: in configuration file

7. Socket Stream Communication test Sender/Receiver Control Marker/Commands Control

8. DOOCS ODR Control Interface SendMsg Commands: 0 Stop 1 Start 2 GetStat 3 Write 4 Read 5 UpStreamWrite 6 UpStreamRead 7 Terminate Headers: ODR/LDA Receiver RecvMsg ODR Control Interface Commands CTL Parameters Socket Stream Packets

9. DOOCS: Send & Receive Send message Receive Packet Show statistics Change to LDA Marker Send message Receive Packet Show statistics

10. ODR Control Interface CMD = Start CMD = GetStat Change to LDA Marker CMD = Stop CMD = Terminate

11. Data Rate ~320 MB/s

12. Summary The communication between DOOCS device server and ODR Control Interface via socket streams has been successfully built and tested; A GUI control/display has been correctly configured for client server, one device server can serve many ODRs armed in PC(s); Use CVS to maintain the codes at DESY DOOCS source/server/calice/pcix_dma; Some GUI control buttons need to be customized for a purpose of convenience. To plot more histograms in order to monitor the statistics during sending and receiving packets.

13. Summary The sending and receiving methods can be improved; Need to use threads to manage the sender and receiver;