Difference between revisions of "Logbook CameraCommissioning ORM Oct18"
DirkHoffmann (talk | contribs) m (sort out some typos, add measurement range, links to run catalog) |
|||
Line 6: | Line 6: | ||
|- style="background:#efefef;" | |- style="background:#efefef;" | ||
! style="width: 100px;" | Date !! style="width: 200px;" | Who did it? !! style="width: 200px;" | Action !! style="width: 800px;" | Comments !! style="width: 300px;" | Documents | ! style="width: 100px;" | Date !! style="width: 200px;" | Who did it? !! style="width: 200px;" | Action !! style="width: 800px;" | Comments !! style="width: 300px;" | Documents | ||
+ | |||
+ | |- valign="top" | ||
+ | | 2018-10-15 || [[User:Ljouvin|Léa]], [[User:DirkHoffmann|Dirk]], Julien, taka, Saiya, Mitsunari || style="background: #CCFFCC;" | Small run summary | ||
+ | [https://portal.cta-observatory.org/WG/lst/DAQ/SitePages/RunCatalog.aspx#ORM Runs0016-0019] | ||
+ | || - Cut busy propagation from BP, dragon on local clock | ||
+ | |||
+ | - 7 GotoSafe and GoToReady for the ECC due to too high temperatures so switch ON/Off of the Modules/BP: | ||
+ | |||
+ | 1) 1 module OFF: 10.1.6.28, 2 BPs OFF associated to module 10.1.6.24 and 10.1.6.27 | ||
+ | |||
+ | |- valign="top" | ||
+ | | [[User:Ljouvin|Léa]], Taka, Julien, Seiya, [[User:DirkHoffmann|Dirk]] || style="background: #FFCCCC;" | writing speed limitation in data taking || | ||
+ | 1 ZFW: validate speed 300 MB writing speed | ||
+ | 8 ZFW: validate 8* 300 MB/s writing speed | ||
+ | 16 ZFW: writing speed: 16*150 MB writing speed. Maybe problem due to the disk. To investigate | ||
|- valign="top" | |- valign="top" | ||
Line 28: | Line 43: | ||
6) All modules ON, 1 BPs OFF associated to 10.1.7.147 | 6) All modules ON, 1 BPs OFF associated to 10.1.7.147 | ||
− | 7) All modules ON, 1 BP OFF associated to module 10.1.7.147 | + | 7) All modules ON, 1 BP OFF associated to module 10.1.7.147 |
+ | |||
+ | |||
|| | || | ||
Revision as of 08:55, 15 October 2018
Enter comments in reverse time order
Glossary at the end!
Date | Who did it? | Action | Comments | Documents | |
---|---|---|---|---|---|
2018-10-15 | Léa, Dirk, Julien, taka, Saiya, Mitsunari | Small run summary | - Cut busy propagation from BP, dragon on local clock
- 7 GotoSafe and GoToReady for the ECC due to too high temperatures so switch ON/Off of the Modules/BP: 1) 1 module OFF: 10.1.6.28, 2 BPs OFF associated to module 10.1.6.24 and 10.1.6.27 | ||
Léa, Taka, Julien, Seiya, Dirk | writing speed limitation in data taking |
1 ZFW: validate speed 300 MB writing speed 8 ZFW: validate 8* 300 MB/s writing speed 16 ZFW: writing speed: 16*150 MB writing speed. Maybe problem due to the disk. To investigate | |||
2018-10-14 | Léa, Dirk, Julien | Small run summary | - No TIB/UCTS
- Cut busy propagation from BP, dragon on local clock - 7 GotoSafe and GoToReady for the ECC due to too high temperatures so 7 switch ON/Off of the Modules/BP 1) All modules ON, 2 BPs OFF associated to module 10.1.6.24 and 10.1.6.27 2) All modules ON, didn't check the BPs 3) All modules ON, didn't check the BPs 4) All modules ON, 1 BPs OFF associated to module 10.1.7.147 5) All modules ON, 2 BPs OFF associated to module 10.1.7.147 and 10.1.7.171 6) All modules ON, 1 BPs OFF associated to 10.1.7.147 7) All modules ON, 1 BP OFF associated to module 10.1.7.147
|
||
2018-10-14 | Eric, Dirk | All (DATA) fibres straight now! |
|
||
2018-10-14 | Dirk | Direct measurement of TX lasers |
INFO: Direct measurements can be done without danger for Photom-211 測定範囲 -70 ~ +5dBm according to datasheet. That is 3.16 mW to 0.1 µW. |
||
2018-10-14 | Léa, Dirk, Julien | First full-cam data run up to 15kHz! | That is what we would have liked to see last week.
Now it's Champagne time. :-) |
||
2018-10-14 | Julien, Eric | Fibres DATAsp1-6 tested | Optically, between DC and Cam. | ||
2018-10-13 | Léa, Dirk, Julien | Run0015 | Still no UCTS(/TIB); fibre broken between DC and Cam. Running with half-cam and two additional missing modules (BP problem): 6.24, 6.27.
- r0015 all events (at runstart), 300Hz and 10kHz, but ZFW problems (testing with 16 instances). |
||
ALL | Door knob! | Falling apart from the CC door. Urgent action needed. (Bigger screw?) | |||
Taka, Seiya, Mitsunari | Fiber Check | We checked optical connection between DC and Camera because some labels were lost due to UV damage. We checked Data2, Data 6, SlowControl and UCTS. Only UCTS had a problem (no splicing at Drive PP). The rest where OK. | |||
Taka, Seiya, Mitsunari | Labeling fibers | We labeled optical fibers of the data (DATA 1 - 6) at patch panels in Drive contaniner and in IT container. The spare cables have not been done yet because a ribbon ran out. | |||
Seiya, Mitsunari | Connection validation | We validated 12 optical fiber connection (No. 1-6, 13-18) from Drive coontainer to IT container. Strength is -35 to -38 dBm. | |||
2018-10-12 | Léa, Taka, Julien, Seiya, Dirk | Runs0012 sqq. | No UCTS/TIB today.
These runs have 3 modules missing (as identified in the preparatory phase: 6.21, 6.25, 6.28). According to a quick check, all EventNb=TriggerNb otherwise for all runs today. See RunCatalog for details. |
||
Dirk | Creation of logbook | ||||
Dirk, Taka, Julien, Seiya, Léa | Data acquisition |
- Pb with the ClusCo on tcs01. The root propagation for the BPs for the trigger doesn't work. Using exactly the same script it works on CacoOperator. - We validate for 3 fibers the new connections to the dataswitch fiber. Eric is fixing the one missing or broken. So for now only the right part of the camera is used for data acquisition - No TIB/ UCTS - Few runs were taken with no external trigger from TIB. 3 Modules didn't appear busy but didn't sent any data. In those test the busy from the CBP was cut. Those missing modules have to be investigated in more details but due to a lot of slow control deconnection problem and high temperature in the camera it was not possible. Script used in CLusCo: init7_noextTrigger_Test.uic. To not cut the busy, name is: init7_noextTrigger_noBusyCut_Test.uic - One try with no external trigger and clock but with the CBP delivering the clock and pps and using 10 MHz clock as default clock for the dragons. L1 local Trigger didn't generated. No we come back to a configuration of dragon on their local clock but this issue has to be investigated. Script used in CLusCo: init7_noextTriggerClock_Test.uic | |||
Dirk, Taka, Julien, Seiya, Léa | Too high temperatures in the Camera |
- Limit fix to 27 for the aire temperature inside and 35 for the BP temperature. Pression also get some alarms - During the day, due to high temperatures we have to gotosafe to wait for the camera to cool almost 11 times but never the BP max temperature went more than 34 degree. The air inside reach at the maximum 26.5. | |||
Dirk, Taka, Julien, Seiya, Léa | ECC lost connection (2 times!) |
- In the afternoon, 3 lost of ECC slow control communication due to the interruption between IT-Container/Driver-Container. Miscomunnication with AMC people... First time, temperature was already high in the camera, we had to switch OFF the 233 and 400V for security reasons. Two other times, we get the ECC connection back quite fast and ECC was in the same state that when the connection was lost meaning state 2 ready. Just no more current in the pulse bar so we have to gotosafe and gotoready both times. After that the current was -247 in the pulse bar... Not understood for the moment - The second interruption happened, when the Moxa switch was reconnected, probably not correctly configured. It was disconnected again. Presently this impacts AMC and drive operation, until the Moxa can be reconnected. | |||
Léa, Taka, Julien, Seiya, Dirk | Discovered SLOW control fiber lost, fibers changed connection recover | Interruption. Using UCTS section for replacement. | |||
2018-10-11 | Eric, Armand | Cable splicing | UCTS fibres ready and checked. | ||
Léa, Taka, Julien, Seiya, Dirk | DATA5-upstream broken | Located between DC-PP. and IC-PP. Eric is going to have a look on Friday, when working on the other (spare) fibres. | |||
Léa, Taka, Julien, Seiya, Dirk | Found correct order of DATA1-DATA6 | We eventually found that the fibres DATA1-6 were connected in (exactly) wrong order to the camera, which lead to a mismatch of switches/modules with respect to interfaces/addresses in osaka.
This is an item for our "learned lessons": The indoor fibres had been labelled (switch-interface), but stayed in Mirca. The new fibres had been confectioned at ORM, and labels had to be "guessed" in one way or the other. |
Glossary
- CC = Commissioning Container (present LST1 Control Room)
- DC = Drive Container
- IC = IT-Container