source: fact/FADctrl/History.txt @ 10813

Last change on this file since 10813 was 10813, checked in by ogrimm, 8 years ago
Corrected dcm_ready and dcm_lock bit evaluation
File size: 1.8 KB
Line 
1Version history of FADctrl
2
322/10/2010      First check-in of FADctrl. Initial version derived from drsdaq revision 10007.
45/1/2011        First version of amplitude calibration (no secondary calibration, yet). New 'socketmode' command.
513/1/2011       Amplitude calibration data is written to text file.
619/1/2011       Implemented secondary calibration.
721/1/2011       DIM event thread now informed through pipe of new data
823/1/2011       Data can be written to disk in M0 format
924/1/2011       Integrated amplitude calibration into FADBoard class
1027/1/2011       Moved OpenOtherSockets() to FADBoard class
112/2/2011        Warning if amplitude calibration missing for data taking
124/2/2011        Fixed exitHandler() being stuck at pthread_join()
1311/2/2011       Moved connect() call to thread of FADBoard class
1414/2/2011       Moved initialisation commands to Evidence configuration file
1518/2/2011   Added 'reconnect' command
1628/2/2011       Removed 'static' keywords in FADBoard::ReadLoop()
171/3/2011        Board list can be passed via command line
182/3/2011        Implemented new FAD data format
1928/3/2011       Boards with communication error set themselves inactive
2029/3/2011       Added Status message service for each board (removed several console messages in turn)
21                        Limited update rate of slow control data to 1 second or interval set by 'update'
221/4/2011        Added DIM frequency service
235/4/2011        Added DIM rate service for each board
246/4/2011        Bug fix in internal pipe communication 
254/5/2011        Removed 'daqmode' (had no function). Added 'reset_trigger' and 'runnumber' commands.
26                        Event format adapted (ADC data not sent in network byte order anymore).
2720/5/2011       Missing pthread_mutexattr_init() in FADBoard constructor caused spurious errors when
28                        locking mutex
29                        Added cleanup handler to thread in FADBoard class to ensure mutex is unlocked when thread
30                        cancelled
3125/5/2011       dcm_lock and dcm_ready bits were incorrectly evaluated.
Note: See TracBrowser for help on using the repository browser.