May 12, 2010 online meeting minutes: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
dc10 trouble: | dc10 trouble: | ||
* trouble reading TDCs, replace SFI, CPU, termination cards, works now; one TDC | |||
was replaced; probably it was termination card, will test that card to confirm | was replaced; probably it was termination card, will test that card to confirm | ||
l2reset first test results: | l2reset first test results: | ||
* 6 adb crates connected (SF level1 south) | |||
* works, log file updated | |||
* need to set a limit on the number of reset attempts, if unsuccessful send | |||
error to alarm browser and continue monitoring until fixed, then remove error | error to alarm browser and continue monitoring until fixed, then remove error | ||
from alarm browser | from alarm browser | ||
* need epics gui to reset manualy, crate by crate (30 buttons) plus one common | |||
button - will ask Hovanes | button - will ask Hovanes | ||
* to finish project, need to run cables - in progress, also BNC cable | |||
connectors, T-s and BNC-lemo adapters; cables must be labels | connectors, T-s and BNC-lemo adapters; cables must be labels | ||
Revision as of 14:55, 12 May 2010
present: Sergey Boyarinov, Sergey Pozdnyakov
dc10 trouble:
- trouble reading TDCs, replace SFI, CPU, termination cards, works now; one TDC
was replaced; probably it was termination card, will test that card to confirm
l2reset first test results:
- 6 adb crates connected (SF level1 south)
- works, log file updated
- need to set a limit on the number of reset attempts, if unsuccessful send
error to alarm browser and continue monitoring until fixed, then remove error from alarm browser
- need epics gui to reset manualy, crate by crate (30 buttons) plus one common
button - will ask Hovanes
- to finish project, need to run cables - in progress, also BNC cable
connectors, T-s and BNC-lemo adapters; cables must be labels
DAQ: seems sometimes cannot end run properly if front end busy issued; probably clastrig2 problem, will investigate
terminal server etherlite2 failed twice, will replace and investigate
test setup (especially fastbus) in counting room must be restored promptly to test boards