Difference between revisions of "Minutes-6-10-2010"
From GlueXWiki
| Line 33: | Line 33: | ||
- According Bryan Moffit, the fADC125 module shows problems when operated above 50 Hz rate. Fernando explained, this is just the initial version of the firmware made by Gerard that we can use for cosmic test. Gerard and Bryan are working to solve the issue. | - According Bryan Moffit, the fADC125 module shows problems when operated above 50 Hz rate. Fernando explained, this is just the initial version of the firmware made by Gerard that we can use for cosmic test. Gerard and Bryan are working to solve the issue. | ||
| − | - Bryan, Beni, and Lubomir connected the fADC125 with the Lunux CPU to the FDC and are performing tests since Wednesday using the | + | - Bryan, Beni, and Lubomir connected the fADC125 with the Lunux CPU to the FDC and are performing tests since Wednesday using the Gerard's code to read the fADC. The fADC was powered on for already 24 hours without heating problems; initially the temperature goes up to 53ded Celsius and stays there. Lubomir investigated the problem of the delay of the signals from one of the cathode cards w.r.t the anode signals. By swapping card inputs and fADC inputs, it turned out the the delay is caused by one of the pre-amp cards or by its cable. Fernando will look into that. Lubomir is analyzing the data from this second run with fADC. He showed a plot (page 483) |
- Fernando informed us that the DAQ group (Bryan Moffit) is working on the drivers for the fADC125 with LINUX CPU and also for VXWorks. Beni said he would prefer to use the CPU we have now (VXWorks) because if we can have the LINUX one it will be temporary. Eugene suggested buying a LINUX CPU. Beni explained the three CPUs available now are from different companies, the DAQ people are evaluating them and we better wait before buying such a CPU. Fernando will ask Bryan when we may expect the drivers for the VXWorks CPU. By that time we will use the fADC with the Gerard's program. | - Fernando informed us that the DAQ group (Bryan Moffit) is working on the drivers for the fADC125 with LINUX CPU and also for VXWorks. Beni said he would prefer to use the CPU we have now (VXWorks) because if we can have the LINUX one it will be temporary. Eugene suggested buying a LINUX CPU. Beni explained the three CPUs available now are from different companies, the DAQ people are evaluating them and we better wait before buying such a CPU. Fernando will ask Bryan when we may expect the drivers for the VXWorks CPU. By that time we will use the fADC with the Gerard's program. | ||
Revision as of 12:23, 11 June 2010
June 10, 2010 FDC meeting
Tentative Agenda
- Production
- 727 B.C. status
- production planning
- wire stringing
- tension measurement system
- Electronics
- fADC125 status (Gerard, Fernando)
- noise/grounding investigations(Fernando)
- Cathode redesign Bill's changes proposed on the last meeting (Bill, Roger)
- Full-scale prototype tests
- cosmics tests FDC Log Book, page 478 - 482 (Beni)
- new tests with fADC125 (Lubomir)
- Other
Minutes
Participants: Bill, Casey, Glenn, Roger, Beni, Chuck, Fernando, Simon, and Lubomir
Production
- We discussed only the production planning. Bill with the help of Chuck put the cathode production on the FastTrack. When a pdf version will be available it will be linked to the minutes of this meting. The production of one cathode sandwich (cathode and ground planes) will take about four days with five people: four techs cutting, gluing, stretching the foil and one electrical tech doing the soldering work. The second type of cathode sandwich doesn't have a ground plane which makes it by a half day faster, but if assuming the same time we will have 8 days per chamber layer or for 30 layers, 240 days in total.
-Fernando had to go to another meeting, so moved to electronics
