Difference between revisions of "Minutes-10-23-2014"
Line 17: | Line 17: | ||
# Commissioning [https://hdops.jlab.org/wiki/index.php/Hall_D_Commissioning Wiki Page] (all) | # Commissioning [https://hdops.jlab.org/wiki/index.php/Hall_D_Commissioning Wiki Page] (all) | ||
# Other | # Other | ||
− | |||
− | |||
= Minutes = | = Minutes = | ||
− | Participants: Curtis, Naomi (CMU), | + | Participants: Curtis, Naomi (CMU) Mike, Fernando, Chris, Eugene, Tim, Dave, Beni, Nick, Simon, Vlad, Cody, Sergey, and Lubomir (JLab). |
. | . | ||
== DAQ and electronics == | == DAQ and electronics == | ||
− | - | + | - Cody generated a new version of the firmware that is much more stable, as Beni tested it over the last night. With the new firmware Sasha was also able to have the CDC crates running at >1kHz without crushes for some time (before, they crushed at about 300Hz). However, with the new firmware, some new modules started showing problems, as tested by Beni and Sergey. A chip-scope was installed on the last module of ROCFDC5, but turns out other modules were crushing the DAQ now. |
− | - | + | - Fernando explained the changes in the firmware: in the previous version, Cody let the CAD software do the planing of the changes (in particular going from 16 to 72 channels) to the f250 firmware. As a result, some of the clocks were not routed in an uniform way. Now Cody manually required a separate (clean) area to be used for the clock distribution. |
− | - | + | - Cody: the new bad modules are most likely related to a different problem, could be a hardware problem. We are not confident in the quality of the boards (Fernando). The first article f125 from the new vendor will arrive next week. |
− | - | + | - Eugene: For the first days of running we should simply exclude the bad modules from the DAQ till we find (if any) a stable configuration that runs for at least an hour without crushes. Then, during the several days of down time we may tray to fix/replace the bad modules. At least for the first days, the main priority will be to have the DAQ working in any configuration (even without the chambers!). Then we can think of how to test the detectors, which may be postponed till December. |
− | - | + | - Bryan Moffit is working on a software reset of the module if it crushes, so the you re-sync the events and can use the information from the module further without stopping the DAQ. |
== CDC update == | == CDC update == | ||
+ | |||
+ | <!-- | ||
- Mike is working on the efficiency plots, also charge vs track length, to be used for gain calibration. | - Mike is working on the efficiency plots, also charge vs track length, to be used for gain calibration. |
Revision as of 15:23, 23 October 2014
October 23, 2014 FDC+CDC meeting
Connection
- Instructions for Bluejeans meeting connection
- FDC meeting ID: 290664653
- To join via a Web Browser, go to the page [1] https://bluejeans.com/290664653.
Agenda
- DAQ (Beni)
- f125 status
- Electronics (Fernando)
- CDC update (Mike)
- FDC update (Vlad, Lubomir)
- Commissioning Wiki Page (all)
- Other
Minutes
Participants: Curtis, Naomi (CMU) Mike, Fernando, Chris, Eugene, Tim, Dave, Beni, Nick, Simon, Vlad, Cody, Sergey, and Lubomir (JLab). .
DAQ and electronics
- Cody generated a new version of the firmware that is much more stable, as Beni tested it over the last night. With the new firmware Sasha was also able to have the CDC crates running at >1kHz without crushes for some time (before, they crushed at about 300Hz). However, with the new firmware, some new modules started showing problems, as tested by Beni and Sergey. A chip-scope was installed on the last module of ROCFDC5, but turns out other modules were crushing the DAQ now.
- Fernando explained the changes in the firmware: in the previous version, Cody let the CAD software do the planing of the changes (in particular going from 16 to 72 channels) to the f250 firmware. As a result, some of the clocks were not routed in an uniform way. Now Cody manually required a separate (clean) area to be used for the clock distribution.
- Cody: the new bad modules are most likely related to a different problem, could be a hardware problem. We are not confident in the quality of the boards (Fernando). The first article f125 from the new vendor will arrive next week.
- Eugene: For the first days of running we should simply exclude the bad modules from the DAQ till we find (if any) a stable configuration that runs for at least an hour without crushes. Then, during the several days of down time we may tray to fix/replace the bad modules. At least for the first days, the main priority will be to have the DAQ working in any configuration (even without the chambers!). Then we can think of how to test the detectors, which may be postponed till December.
- Bryan Moffit is working on a software reset of the module if it crushes, so the you re-sync the events and can use the information from the module further without stopping the DAQ.