Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

We left the cooling running, and the MPOD off.

1/21/2015

The poorly crimped pin (pin 20) on pigtail P4 corresponding to DVDD+ sense was repaired by Danh Du.  Shortly after, FEB L5b was powered on and the previously observed power issues (sense voltage = 0 and terminal voltage maxed out) were no longer present.

The SVT box was opened up and the high speed cables connected to L4t and L4b were re-seated.  Once this was done, a control link was established with FEB L4t and L4b. 

It was noticed that the current drawn by DVDD on FEB L6b (FEB 15) was lower than expected.  After probing the board, it was determined that the A+2.9V_DVDD regulator circuit had blown up.  The FEB support plate was then removed from the SVT box and the troublesome FEB was replaced by FEB 13.  Once the FEB support plate was reinserted into the SVT box, FEB L6b was powered on and everything looked as expected.

After reconnecting all of the high speed cables and power, all mounted FEB's were powered on and the control links on all of the were checked.  This check took place after the new firmware which allowed the control DPM to receive all 12 links had been loaded.  The test showed that all FEB's had control links, however, the control link associated with FEB L6b had several errors.  This is a previously known problem that can be fixed by switching FEB L6b to another flange channel.  The data links also looked fine. 

Once all FEB's were verified to work, the SVT box was sealed up, the FEB support plate cooling was connected and the chillers were turned on.  The cooling was left on and power was left off for the night.

1/22/2015

5:00PM System status

Detector fully hooked up.
FEB chiller at +20C.
SVT chiller at +20C.   
FEB power looks good on all boards.

Summary:

Two FEBs have issues. Including notes on those below.

Physical FEB: L4b Serial: 8 FebFpga: 8 Fiber: F
==============================================
DataDPM 0, DP 0, Hybrid 3, all sync 
DataDPM 0, DP 1, Hybrid 2, all sync 
DataDPM 0, DP 2, Hybrid 1, all sync
DataDPM 1, DP 0, Hybrid 0, 4/5 synced

All of these synced initially, but after trying to resync, they began to have issues. The APV's on Hybrid 0 seem to drop in and out of sync. After power cycling, the issues persist with Hybrid 0. The peak and base values on APV 4 look off. After playing with the AdcClkPhaseShift and Data delays and setting them back to what they initially were, the sync and base values on APV 4 improved. We will know if there is an issue with the data after a run is taken.

Physical FEB: L6b Serial: 13 FebFpga: 6 Fiber: F 
==============================================
Control link has several errors which don't allow communication to the board. Switched control fibers E and C at the COB. The FPGA number switched to 3. There were no data links present. Looking at the oscillator that is used to driver the links, the frequency is at half of what is it suppose to be.

 

Detailed log on each FEB below:  

Physical FEB: L1t Serial: 9  FebFpga: 2 Fiber: A
==============================================
DataDPM 0, DP 0 (No hybrid connected)
DataDPM 0, DP 1 (No hybrid connected)
DataDPM 0, DP 2, Hybrid 1, all sync
DataDPM 1, DP 0, Hybrid 0, all sync

 

Physical FEB: L2-3t Serial: 14 FebFpga: 5 Fiber: D
==============================================
DataDPM 4, DP 0, Hybrid 3, all sync
DataDPM 4, DP 1, Hybrid 2, all sync
DataDPM 4, DP 2, Hybrid 1, all sync
DataDPM 5, DP 0, Hybrid 0, all sync

 

Physical FEB: L4t Serial: 5 FebFpga: 9 Fiber: H
==============================================
DataDPM 1, DP 3, Hybrid 2, all sync
DataDPM 3, DP 3, Hybrid 1, all sync
DataDPM 5, DP 3, Hybrid 0, all sync
DataDPM 6, DP 2, Hybrid 3, all sync

 


Physical FEB: L5t Serial: 11 FebFpga: 10 Fiber: H
==============================================
DataDPM 5, DP 1, Hybrid 3, all sync
DataDPM 5, DP 2, Hybrid 2, all sync
DataDPM 6, DP 0, Hybrid 1, all sync
DataDPM 6, DP 1, Hybrid 0, all sync

 

Physical FEB: L6t Serial: 10 FebFpga: 11 Fiber: H
==============================================
DataDPM 4, DP 0, Hybrid 3, all sync
DataDPM 4, DP 1, Hybrid 2, all sync
DataDPM 4, DP 2, Hybrid 1, all sync
DataDPM 5, DP 0, Hybrid 0, all sync

 

Physical FEB: L1b Serial: 7 FebFpga: 0 Fiber: A
==============================================
DataDPM 2, DP 2 (No hybrid connected)
DataDPM 3, DP 0 (No hybrid connected)
DataDPM 3, DP 1, Hybrid 1, all sync
DataDPM 3, DP 2, Hybrid 0, all sync

 

Physical FEB: L2-3b Serial: 6 FebFpga: 3 Fiber: D
==============================================
DataDPM 1, DP 3, Hybrid 2, all sync
DataDPM 3, DP 3, Hybrid 1, all sync
DataDPM 5, DP 3, Hybrid 0, all sync
DataDPM 6, DP 2, Hybrid 3, all sync

 

Physical FEB: L4b Serial: 8 FebFpga: 8 Fiber: F
==============================================
DataDPM 0, DP 0, Hybrid 3, all sync
DataDPM 0, DP 1, Hybrid 2, all sync
DataDPM 0, DP 2, Hybrid 1, all sync
DataDPM 1, DP 0, Hybrid 0, 4/5 synced

 

All of these synced initially, but after trying to resync, they began to have
issues. The APV's on Hybrid 0 seem to drop in and out of sync. 

After power cycling, the issues persist with Hybrid 0.

 

The peak and base values on APV 4 look off. After playing with the
AdcClkPhaseShift and Data delays and setting them back to what
they initially were, the sync and base values on APV 4 improved. We will
know if there is an issue with the data after a run is taken.

 

Physical FEB: L5b Serial: 12 FebFpga: 7 Fiber: F
==============================================
DataDPM 1, DP 1, Hybrid 3, all sync
DataDPM 1, DP 2, Hybrid 2, all sync
DataDPM 2, DP 0, Hybrid 1, all sync
DataDPM 2, DP 1, Hybrid 0, all sync

 

Physical FEB: L6b Serial: 13 FebFpga: 6 Fiber: F
==============================================
Control link has several errors which don't allow communication to the board.

 

Switched control fibers E and C at the COB. The FPGA number
switched to 3.

 

There were no data links present. Looking at the
oscillator that is used to driver the links, the
frequency is at half of what is it suppose to be.

1/23/15 - TKN

Checked the grounding scheme of the detector.

L1-3 u-channel / SVT Box: 0.1 Ohms

FEB cooling plate / SVT Box: 6.7 Ohms

FEB cooling plate / table: 4.6 Ohms

SVT Box / table: 3.4 Ohms

Seems to imply that the table is between the FEB cooling plate and the SVT Box.  Perhaps implies a connection from FEB cooling plate to vacuum box (e.g. via data cable edge contact) and then vacuum box to table then table to SVT Box?

We should try to break this when we can.

6:40pm

The hybrid power monitoring and control now works through the hybrid GUI. It's mapped using feb index. Getting the physical name for it on the GUI is a little tricky but I'm working on it so until then you need to find out which feb nr you have powered (either from the non-zero hybrid currents that are updating, the temperature GUI or the daq GUIs). 

1/30/15

10:00AM - PH
Testing L4b (serial #15) mounted on production plate placed on the test bench. Using one of the spare flanges that are not potted.The FEB ID is 2, data "DPM:channel" is 0:0, 0:1, 0:2 and 1:0. I see a few data link errors on 0:2. All hybrids sync. Took ~5000 events, file name is test.dat_000785.evio.0.

10:30AM - PH
Testing L1t (serial #01) with same setup as the L4b above. All hybrids sync. Took ~6400 events, file name is test.dat_000787.evio.0.

11:50AM - PH

There is a broken pin on L1t (serial #01). That particular one is not used. Retesting with same setup as the L4b above.  All hybrids sync. Took ~4800 events, file name is test.dat_000789.evio.0.

Equipment

Interlock board

see Group C interlock board for instructions on monitoring and controls.

...