LIONEL

LIST OF ELECTRONIQUE INSTALLATION TASKS WITH ESTIMATED MANPOWER AND TIME
REQUIRED.

Electronique Installation
-----------------------------

                     |   Manpower  |   time / castle 
                     |             | (installation and tests)
_____________________|_____________|_________________________
LVDTs                |       2     |       1 h
                     |             |       
Encoder              |       2     |       1 h
                     |             |
Motors               |       2     |       1 h
                     |             |
Rack monitor         |       2     |       0 h 30
                     |             |
Driver crate         |       2     |       1 h 30
                     |             |
Electronique crate   |       2     |       1 h
                     |             |
Smoke detector       |       2     |       0 h 30
                     |             |
1553 cables          |       2     |       0 h 30
_____________________|_____________|_________________________
                                           7 h 

All the motors are installed. The Encoders are installed at P1. We can
finish the installation at D1-D2 (connect the interface boards) and at P1.
We must pull the 1553 cables between D1 and the small control room, and
between P1 and the SCR. Then we can test the pot motion with the python
script. 2 Drivers Crates are ready and can be installed.

LIST OF ALL EQUIPMENTS (SMOKE DETECTORS, RACK MONITOR, POWER BOX)

Equipments list
_______________

Smoke detector :
	* 1 in the tunnel at D1-D2
	* 2 at lab 6

Controller for the smoke detector :
	* 3 in the tunnel (1 at D1-D2, 2 at P1-P2)

Power boxes :
        * 4 in the tunnel (2 at D1-D2, 2 at P1)
	* 3 at lab 6

Rack monitors :
	* 2 at lab 6
	* 5 in the tunnel (2 at D1-D2, 3 at P1-P2)


        We need one smoke detector per rack. This smoke detector is
connected to the rack monitor interface (RMI). If it detects smoke, it
must turn OFF the power box (Drivers for the motors). But we need to
control the power box with the 5V too.

          ___________________               _________________
          |   Smoke detector |              |     5 V       |
          |__________________|              |_______________|
                   |                                |
                  \|/                              \|/
                   |___                          ___|
                      |                          |
                 _____|__________________________|___
                 |                                  |
                 |  Rack monitor Interface (RMI)    |
                 |__________________________________|
                                |
                               \|/
                 _______________|___________________
                 |                                  |
                 |          Power Box               |
                 |__________________________________|



  On the rear panel of RMI, we have :

        - 2 BNC connectors (Blower Interlock) for the smoke detector:
                * one attached to a normally closed relay.
                * one attached to a normally high TTL signal.

        - 2 Fault Input (TTL Input, BNC conntector)

        - 1 Fault Ouput (TTL Ouput, BNC connector)

  First we need to connect the smoke detector to the Sensor Input. Then we
connect :
        - the high TTL signal of the Blower Interlock to one Fault Input
          (Fault #1)

        - the 5V to the other Fault Input (Fault #2)
                                 
        - the Fault Ouput to the power box.

  On the top of RMI, we have some swithes. We must turn its like this:

                 SW3   SW2
         DRIP    OFF   OFF
         SMOKE   ON    OFF
         AIR     OFF   OFF
         WATER   OFF   OFF

         TRIP    SW1
          1      OFF
          2      OFF
          3      OFF
          4      OFF

  So now, the power box is turned OFF if we detect smoke or if we turn
OFF the 5V.

MARIO

From mariovaz@d0chb.fnal.gov Sat Feb  3 11:05:30 2001
Date: Fri, 02 Feb 2001 11:59:42 -0600
From: Mario Vaz <mariovaz@d0chb.fnal.gov>
To: ROYON Christophe <royon@hep.saclay.cea.fr>
Cc: novaes@fnal.gov, santoro@fnal.gov, Andrew Brandt <brandta@fnal.gov>
Subject: Re: red / green cables

Stock room has green and red coaxial cables:

Ref Number	Price		Available	Description
1170-034000     $.17 / FT       10220           CABLE, GREEN RG58C/U
1170-036000     $.10 / FT	10354		CABLE, RED RG58C/U 

CHRISTOPHE

Today, Mike, Eduardo, Molina, Sergio, Lionel and myself went into the
tunnel to see what was happening with the ribbon cables. The conclusions
are the following:

- one bunch of ribbon cables is enough to reach A1 and P1 provided one
uses the longest bunches coming from the collision hall. For this purpose,
one should not put the ribbon cables going to A1 and P1 fully on the upper
cable tray coming from the collision hall, but put it down a bit before to
gain about one meter (as it stands now, one meter is missing to reach the
rack).

- two bunches are enough to reach the dipoles

- the bunches going to A2 and P2 should not go on the upper trail above
the beam line but rather in the space under the beam line (the trays are
small and the ribbon cables pretty heavy)

- We labelled all bunches of ribbon cables sothat people could know where
they should be pulled (A1, A2, D1-D2, P1, P2) according to their length.

This means we have now some spares for the ribbon cables (12 bunches now),
some of which will be used to go to the small control room.

We also had a look on the red HV cables, and there are 10 of them in the
tunnel:

- 2 going to dipoles (3 are needed)
- 3 going to A2 (5 are needed)
- 0 going to A1 (5 are needed)
- 5 going to P1, P2 (10 are needed)

They need to be tested. For this purpose, I will ask Lionel to build a
tester.

There are also about 10 green cables, which need to be tested. How many do
we need for the 5V? Is one cable per castle enough, or should we be able
to control each motor separately?

I think that all ribbon cables will be pulled by the end of this week, and
I hope that I will be able to test all bunches again on Friday afternoon.
I will ask Lionel to build a tester for this.

This afternoon 0o2/feb), Sergio, Lionel and myself went in the collision and
in the tunnel to test the ribbon cable. The result is not too bad, and will
be included in the cable database (I only quote here the list of bad cables,
all the others are good):

Cables from collision hall to P1
=================================
RC05 (8 cables): cable 8, channel 1 dead
RC12 (8 cables): cable 1, channel 15 connected to ground
                 cable 8, channel 15 connected to ground
RC19 (8 cables): cable 6, channel 1  connected to ground
RC20 (8 cables): all good

Cables from collision hall to P2 (1st bunch)
=================================
RC06 (8 cables): all good
RC24 (8 cables): all good
RC23 (8 cables): cable 1, short circuit channels 10 and 11
RC25 (7 cables): all good

Cables from collision hall to A1
=================================
RC14 (7 cables): cable1, channel 11 dead
RC03 (9 cables): all good
RC08 (8 cables): cable7, channel 16 connected to ground
RC17 (7 cables): all good

Cables from collision hall to A2 (first bunch)
=================================
RC11 (8 cables): all good
RC15 (7 cables): all good (NB cable 5, connector broken channel 16)
RC18 (7 cables): all good
RC04 (9 cables): all good

Cables fron collision hall to D1,D2 (first bunch)
====================================
RC10 (8 cables): all good
RC07 (8 cables): cable 6, channel 6 connected to ground

Cables to P2 (bunches in tunnel only):
=======================================
RC33(?) (8 cables): all good
RC31 (8 cables): cable 3, channel 6 and 7 dead
RC01 (9 cables): cable 1, channel 1 connected to ground
                 cable 9, channel 6  connected to ground
RC35 (8 cables): cable 5, good but connector broken
                 cable 8, channel 8 dead

Cables to A2 (bunches in tunnel only):
=======================================
RC02 (9 cables): all good, cable 1, connector broken channel 16
RC26 (8 cables): cable 6, channel 16 connected to ground
RC34 (8 cables): cable 3: short circuit channels 12 and 13
                 cable 7: short  circuit channels 14, 15, 16
                 cable 8: short  circuit channels 14, 15, 16
RC30 (8 cables): all good

Cables to D1,D2 (bunches in tunnel only):
=========================================
RC36 (8 cables): all good

MIKE MARTENS

Cable pulling estimate.

On the web page

http://www-ap.fnal.gov/~martens/fpd/cable_run.htm

You can find my estimate of the cable pulling effort.

These are the list of cables and time estimates for the cables from the D0
detector electronics to the FPD crates in the Tevatron or the FPD pots. It
does not include cables from the pots to the crates, or cables from the
AFE boards to the D0 trigger system. I have done my best of estimate the
times for installation. It seems there is about 2.5 to 3.0 weeks full time
of cable pulling plus the time to finish up with the ribbon cable
pulling. 

I have NOT included any time estimates for motor, encoder, driver
installation, FPD detector installation, etc.

There was a general meeting on pulling cables across the bridge this
morning. The bridge will be open until about Tuesday when the level zero
cables will be finished. There are a few other cables besides ours which
must be pulled after the cable bridge is covered. We have to give Jon
Kotcher the size of the opening we need for the 20 LMR400 cables, 5 RG58
cables, 5 LMB cables. I will do this this afternoon. It is not clear to me
when we will be able to pull these cables because we may not be able be in
the area while they are stacking the shielding blocks.

After this meeting, I met with Kurt, Delmar, and Jon about our other
cables. Jon has said that D0 cannot give us any more help because they are
too busy already. He cannot even get a cable tray pulled along the north
wall between the tev tunnel and labrynth. Jon also had several
question/concerns about our plans. Eventually he wants to sit down with us
(meaning Andrew) and discuss our plans but some of his concerns are

1) We need to give him the amount of space we need for laying our cables
above the bridge.

2) They cannot get cable tray layed for us between the tev tunnel and the
labyrnth. Jon turned us down flat, he will think about waht they can do
for us in April.

3) To make sure we discuss with Marv Johnson our plans for laying
"non-standard" cables. These include the cable that come from the Tevatron
tunnel to the MCR of FCH. Jon was worried about grounding issues.

4) When we will be able to pull our PMT cables from the MCH to PW08. We
may not be able to finish this by March 1, because we cannot be in that
area while the shielding is being stacked.

5) Our cables going from the west wall to PW08 may get in the way of some
of the muon cables. I had discussed this with Rick Hance, and Kurt
Krempetz before and they thought my plan was OK. However Jon and Delmar
stated emphatically that the FPD group and muon group had talked to each
other and that the FPD group already knew about this. This meeting was the
first I had heard of this.

6) We can pull cables from PW08 to the tunnel, but we must be carefull
not to block the access way because it is a means of egress.

7) As far as I can tell we will have access to the collision hall until
March 1st, but I am not sure if certain parts will be off limits during
parts of the remaining installation.

8) Jon feels we should really have someone attending to these details full
time and Jon thinks we really should have someone at every installation
meeting on Monday afternoon.

In general Jon was upset by what he feels is our lack of planning but the
amount of work that D0 has to do in the next month is overwhelming so Jon
may not be able to give us much attention in the next month. He suggests
that we get our plan together and have Andrew and him meet to discuss what
arangements we can make. (Personally I feel the FPD group bears some
responsibility in this, but also that the FPD group has not always been
given enough information from D0 and this is also a factor in the
confusion/chaos we are experiencing.)