Main INDEX
Monthly INDEX
PREV
NEXT
Make New Entry,
Make Followup Entry
User name lselvy
Log entry time 11:29:33 on March14,2011
Entry number 351748
keyword=Added Synch Event Check for 1190
Steve Wood and myself added code to check the sync of the 1190 by dumping out the code after the event read. When the sync_or_unbuff (two fs there) is set it will check to see if any more data is in the 1190. If it is it grabs the number of events and put it into an error word (that is too large to be misunderstood as a data word).
The following Code was added:
//Checking for extra hits and syncing the 1190A
//*************This will only work for single module operation ONLY!!!!!!!!!!!!!**********
if(sync_or_unbuff){
datascan = tdc1190Dready(0);
if(datascan>0){
logMsg("ERROR: Multiple Events in 1190a. N events in FIFO = %d, Event Num = %d\n",nevts,event_no,0,0,0);
//Slot number is 12. We are hardcoding it as a stopgap measure.
*rol->dabufp++ = 0xdcfe0000 + (12<<11) + (nevts & 0x7ff);
*rol->dabufp++ = 0xbad0cafe;
while(datascan>0){
tdc1190ReadBlock(0,&dummyevent);
datascan--;
}
}
}
Backup of the original CRL code can be found at bb_roc5.crl.14Mar2011