September 26, 2007 online meeting minutes: Difference between revisions
No edit summary |
No edit summary |
||
Line 3: | Line 3: | ||
'''DVCS Trigger''' | '''DVCS Trigger''' | ||
We had useful discussion about DVCS Trigger System. | We had useful discussion about DVCS Trigger System. New page http://clonweb/wiki/index.php/DVCS_Trigger_System was created. It contains system requirements along with related materials, and will be updated regularly by adding new materials and updating existing ones. We talked about general design, necessity of external start signal to start DVCS Trigger logic, the source of that start signal (L1 or self), outputs we want to have. Ben expressed an opinion that project can be completed using v1495 boards, he will look closely on the project. We'll have another discussion soon to finalize system design. | ||
'''Projects''' | '''Projects''' |
Latest revision as of 16:38, 30 September 2007
present: Sergey Boyarinov, Sergey Pozdnyakov, Nerses Gevorgyan, Nikolay Balasanyan, Valery Kubarovsky, Eugene Pasyak, Tanest Chinwanawich, Elliott Wolin, Chris Cuevas, Benjamin Raydo
DVCS Trigger
We had useful discussion about DVCS Trigger System. New page http://clonweb/wiki/index.php/DVCS_Trigger_System was created. It contains system requirements along with related materials, and will be updated regularly by adding new materials and updating existing ones. We talked about general design, necessity of external start signal to start DVCS Trigger logic, the source of that start signal (L1 or self), outputs we want to have. Ben expressed an opinion that project can be completed using v1495 boards, he will look closely on the project. We'll have another discussion soon to finalize system design.
Projects
Nerses reported progress on epics support for the SY1527 system. He finished driver modification, all available boards are supported now. Three mainframes (HVDVCS, HVTEST and PCAL) are running fine with the recent version of driver.
Softioc startup script was modified by Nerses: instead of using 'sleep' as ioc input Nerses decided to use 'pipe' named 'softioc.pipe' created in the same directory where ioc config file is located. Command 'exit' can be sent to that pipe to force ioc to exit (actually any command forces ioc to exit).
We discussed ioc restart procedure and decided to add 'ioc reboot' button to existing ioc reboot GUI, so ioc can be rebooted by user 'clasrun'. Currently it can be done by 'root' or by designated users included into 'sudo' list. Along with reboot function it will be good to have heartbeat as well, same way as for vxworks iocs.
Several repair-related issues were discussed. Three Lecroy mainframes were sent for repair, all of them were repaired before, so we hope that those mainframes will be repaired for free. One more mainframe will go to repair for the first time. All mainframes in the Hall B are working but we do not have any spares right now.
CAEN 1533 6-channel HV board have a problem enabling last 3 channels, we be sent to CAEN for repair.
PCAL FASTBUS crate lost +5V power, will be repaired on site. In general PCAL test setup works, but several issues remains, will be investigated.
We attempted to take laser data from CLAS TOF system, several problems were observed including readout, will be addressed.
Modified ET system will be available soon from Carl Timmer, he is working to implement better protocol between multi-network machines. That should solve our problems when et_2_et sometimes cannot connect to the machine with multiple network interfaces running multiple ET systems.
This morning we experienced power outage in counting house because of emergency generator panel repair. It is probably make sense to ask for better power management: when emergency generator is on service, normal power should be supplied. Sergey will submit request.
It will be another power outage during upcoming weekend, we need to turn off as much electronics as possible in the Hall and Counting Room.