Aug - Dec 2000
CHRISTOPHE: There was a tunnel access on Thursday. The shutdown activities were: - HV tested and working - camera installed and working - MLBs tested and working - rack monitor + pot moves: when we try to send a message to the rack monitor and move the pots, the RM becomes physically hot and we lose power from the monitor, as if there was a short circuit. Changing the RM, the electronic card, the driver, the cables has no effect. The problem might come because the ground in the tunnel is a floating ground and not a real ground. MIKE MARTENS: The dipole pots (Macacao and Guajara) have been surveyed in the Tevatron tunnel. The side of the pot tip inside the detector chamber (i.e. outside the vacuum) is 3 mm horizontally from the Tevatron ideal center line when the pot is at its fully in limit switch. The center of the pot window is centered about the Tevatron ideal center line. The beam position is now 1 to 1.5 mm to the radial outside of the Tev ideal center line. The beam emittance is still uncertain (horizontal sigma ~ 2 mm at the location of the pots). It is about 30 pi mm-rad (we expect ~ 15 pi mm-mrad). SERGIO: The last two castles were surveyed at the NWA by O' Sheg et al.: Gentil on Wednesday and Pacoval on Friday. We have organized all the information from Newton in a single webpage: http://www-d0.fnal.gov/fpd/FPD_News/Newton/newton.html. This page contains information on the Interface Board, Cartridge, Control Cables and Power System, and several figures. The correct links will be available as soon as I get more disk space in the public area.
PETRA:
- 5 pseudo detectors were made
- Started the test of the amplifier crate and amplifier boards
- 7 X 6m cables (between MAPMT and AMP) were made (Bob Jones) and tested
- First steps to assembly cartridge
- 1 bunch (10 cables) of ribbon cables were pulled between P2 and the
Collision Hall
- 16 sockets and cookies were cleaned for the next detectors that are going
to be built at UTA
- There was problems with the DC offset of the signal coming from some
amplifier boards. On the amplifier board one header and one shaper belong
to different channels. Pins #17 (ground) and #18 (signal) on the shaper
are the outputs that goes to the ribbon cable. The voltage between #18 and
#17 for the different channels are different leading to different
pedestals which are very often too high.
HELIO + SERGIO
- We checked Laranjeiras and Matinada for installation in the tunnel.
Laranjeiras was working fine, and we had just to soften one of the pots
that was sticking when moving at high speed. However, Matinada's upper pot
sticks at high speed and we could not soften it even after spending a long
time trying. We have even open the the upper pot to check. We decided to
replace Matinada by Gentil
* Recommendation: All pots should be periodically moved to avoid the
sticking.
- We went in tunnel and checked that both Macacao and Guajara (dipoles)
also sticks and low velocity but go smooth a slow speed.
* Recommendation: The present velocities (slow = 1.38 rps and fast = 14
rps) should be modified. We suggest: slow = 2 rps and fast = 10 rps if
there is not high resonance effects (Newton).
- We checked the rack monitor heating problem. On Thursday it presented
some intermittent problems but after removing and reinstalling cables it
could be operated from outside and worked fine for ~ 30 minutes. During
this time there was no heating and the motor did not stopped.
- Helio discussed with Fritz Bartlett about the rack monitor. We also
talked with Rick Hansen. We concluded that the problem with the Rack
Monitor is an overload in the 5V line that is used to feed both its
circuits and the Indexer. We opened one rack monitor module and found out
that the part that is overheating is exactly the power module that deals
with the 5V. The solution is to use another 5V power supply to feed the
Indexer.
MIKE MARTENS
Both the P1 and P2 chambers have been installed and surveyed in the
tunnel. The bakeout is scheduled to begin today and last until Wednesday
9/13 morning. As of today, it is estimated that Friday 9/15 will be the
last day for tunnel access.
The pot Gentil was installed in the P1 position instead of Matinada
since there was some problems with the upper arm of Matinada sticking at
high speeds. In the P2 position the Laranjeiras was installed.
Gentil was aligned in the tunnel using the results from the V-star
survey performed after the pot was re-assembled.
CHRISTOPHE:
List of things done/to be done for Engeneering Run/Run II:
==========================================================
1) LVDTs: 18 needed for run II
========
2 in the tunnel calibrated
9 at LAB6
12 were bought, where is the missing LVDT????
2) motors: 18 needed for Run II
==========
2 in tunnel
1 in small control room (now in tunnel for tests with tools)
6 at LAB6
9 at NWA
3) Motor to driver cables: 18 needed for Run II
==========================
16 at LAB6
2 in tunnel
1 in control room
4) CB2 cables (from rack monitor to electronic card): 18 needed for Run II
=====================================================
2 in tunnel
16 simple cables at LAB 6
1 double cable at LAB6
1 double cable in the small control room
Question: is it normal that we have "simple" cables? I mean that we use 16 bits
========= for two electronic cards (8 bits for each), so this means two
connectors for the cards ("double" cables) and not one ("simple"
cables).
Probably not... This has to be checked with Newton. In this case,
all these cables have to be redone by cutting one end of the cable and
putting two connectors instead of one. Do we have enough connectors or
do we need to buy more? Also, if we stick to the "single" cables, we
need more rack monitors, as we use only half of the pins for each
digital input/output...
5) Electronic cards for drivers: 18 needed for RunII
================================
2 in tunnel
16 at LAB 6
1 in small control room
6) Rack monitors: 9-10 needed for Run II???? present configuration
=================
2 in tunnel
5 in small control room ???? (1 more in tunnel for tests now)
Many of them are on the 3rd floor now (probably coming back from PREP) if we
need some more...
Question: we might need to improve the way we use the rack monitors to decrease
========= the number we need... in peculiar with the smoke alarms
7) 1553 cables:
===============
1 long cable (120 m) in tunnel for dipoles. This cable needs to be moved to
P2??? Not obvious if we use the two connections of the power PC. In that case,
one cable goes to P1-P2, the other one to the dipoles.
LAB 6:
======
1 cable 30m (105 feet)
2 cable 10m (40 feet)
1 cable 50m (180 feet)
1 cable 1m (3 feet)
small control room
===================
1 cable 30m (100 feet)
2 cables 20m (70 feet)
Question: Is it better to have one single cable to go to P1 P2 to put the
========== three cables we have already in series. Mike will investigate if we
can have a long 1553 cable from the stock and the connectors (they
are not available at D0). If this is not easy, we stick to the
possibility of having three shorter cables in series. This was tested
in the small control room and worked without any problems.
8) HV boxes:
============
one with 6 connectors (?) in the tunnel
Here, this is a complete mess... We have 3 at LAB6, one in the small control
room, all different...
one with 4+1 connectors
one with 7+1 connectors
one with 8 connectors
one with 6 connectors
Is it enough??? It depends on the number of HV cables in the tunnel... To be
checked by Petra.
9) Racks: 5 needed for Run II
=========
1 installed in the tunnel (dipole side)
2 to be installed for the engeneering run at A0 now ???
Mike is taking care of that.
10) Smoke detectors: 5 needed for Run II
====================
1 in tunnel
2 more needed for the engeneering run, they are in the small control room.
They need to be mounted. The cables, the smoke detectors, and the
connectors are in the small counting room (the connectors are located in one
of the boxes of the smoke detectors sothat they would not be lost).
11) Rack monitor controller: 5 needed for Run II
============================
1 in tunnel
2 in addition needed for the engeneering run, in small control room
12) Blue fans: 5 needed for Run II
==============
They are used to cool the amplifier crates.
1 in tunnel
2 to be installed for the engeneering run, they are in the small control room
13) Green cables: (engeneering run only)
=================
6 installed (3 of 130m, 3 of 120 m)
6 more are needed and should be made a.s.a possible.
question: what is the length of these 6 cables? 104 m would be perfect
========= concerning time delays, but is it enough to reach the detectors????
104 m should be ok if we put the cables along the D0 wall to be
removed when D0 comes in.
14) Multi Anode PhotoMultiplier Amplifier Cables:
=================================================
for the engeneering run:
6 6-meter long cables for P2 up detector, Bob Johns has made these cables,
they are ready
6 3-meter long cables already installed for the dipoles, should be moved to
P1 up. Question: Is 3-meter long cable enough, or do we need longer cables???
This needs to be checked in the tunnel.
15) HV cables:
==============
??? How many installed in tunnel??? TO BE CHECKED
this is correlated with the number of HV boxes we need for the detectors and
the scintillators.
16) Flat ribbon cables:
=======================
Three bunches of cables to be put in series are needed between P1/P2 and the \
small control room, because of the length of these cables.
6 (in fact a bunch of cables) have been installed between P2 and the
collision hall.
6 more need to be installed between P1 and the collision hall, and
2*12 between the collision hall and the small control room.
It would be good to use the cables present already in the collision hall but
they have not been tested yet.
Also, it is better to use 206 ns cables only, and not mix up 206 and 196
cables...
Other cables are at D0, and in the fixed target zone. Should everything be
brought back to D0 and tested????
17) Power boxes:
================
2 installed in tunnel (drivers+amplifier)
8 additional ??? needed for engeneering run, I got one, it is possible to get 7
more if we pay them (cost 180 dollars each)... The bill should be made by Rick
Hanse.
It might be better here to use a flat ribbon cable to transmit the 5V here as we
only to pass one cable in that case instead of all the green cables. The
connector at the end is more tricky in that case and needs to be done.
17) Cameras: 5 for Run II???
============
one installed in tunnel
Two more have to be installed for the engeneering run, the cable has been
purchased (170 dollars). The cable is 1000 feet long, and needs to be
cut into two parts for each camera. The connectors will be installed by
Larry Jackson and do not need to be purchased.
Two cameras have been asked to Larry Jackson. He will install them next week
in the tunnel at P1 and P2. He should be contacted next Tuesday morning either
via phone (4073) or via email (ljack@fnal.gov).
18) PMs for scintillator triggers:
==================================
they are at LAB6
19) Bake out of the pots:
=========================
Should have started now, Mike is taking care of that.
20) Encoders:
=============
They are at LAB 6.
21) Crates:
===========
The crates need to be assembled at LAB6.
ANDREW + CHRISTOPHE + HELIO + LIONEL + MIKE + NEWTON + PETRA + SERGIO
Activities during the last two weeks shutdown:
INSTALLED:
===================
- dipole detectors:
===================
They are fully installed and equipped with real detectors. Electronic
cards between the rack monitors and the drivers have been changed (Indexer
Interface Boards). A separate 5 V power supply was used to power these
cards. We should keep checking the rack monitor for overheating. Only
tests remain to be done (pot moves for D1, amplifier crate tests, LMBs).
Note that it was quite uneasy to put the detector in D1.
=======================
- quadrupole detectors:
=======================
Four pseudo detectors have been installed in P1 up, P2 up, P1 in (aisle),
P2 in (aisle). Unfortunately, we forgot to put black tape in the holes for
real PMs.
All the motors, indexers and LVDTs have been installed (4 for P1, and 4
for P2) and connected only for P1. All the motors (P1 and P2) have been
tested and found to work properly. Sometimes, the motor had some
difficulties to train the pots (it remains stuck), and by doing it many
times, we solved that problem. So far, no cable have been connected to
them.
The switches in front of the driver used for tests together with the "blue
box" were at a wrong position (switches 6, 7, and 8 were at OFF position).
The drive can go up to 5 Amp, however the motors do not handle such a
current. The maximum current for the motors should be 4.3 Amp. The
velocity do not depend on the current.
In order to install the encoders wheel it is necessary to let some small
gap between the wheel and the pot block, about 0.3 mm. There is a
stainless piece off sheet about 1 cm wide in the tool box for this
adjustment. On each support screw there is a brass spacer (cooper tube)
that will hold the correct distance between the Hall sensor support and
the wheel. The nuts should not be overtighted. Do not remove the spacer
and do not permute with another pot. They were individualy adjusted to
compensate diferences on the begining of the worm tread position. Maybe
the spacers should be increased in order to guarantee that they are not
touch on the castle neither in the electronics.
==============
- electronics:
==============
1 rack is almost completed at P1. Only missing are the amplifier crates,
the power supply for the amplifier crate, and the rack monitor interface.
The crate sizes at the dipole position are:
LVDT cr. 26.5 cm
rack monitor 4.5 cm
mon. interface 9 cm
driver cr. 40 cm
1st power supply 15 cm
AMP cr. 40 cm
fan 4.5 cm
2nd power supply 14 cm
=========
- cables:
=========
Christophe has put together the information about all the cable
connections for the FPD in two nice drawings:
http://www-d0.fnal.gov/fpd/FPD_News/fpd1_cables.ps.
and
http://www-d0.fnal.gov/fpd/FPD_News/fpd2_cables.ps.
Any comments are welcome.
Petra put the information how the signal cables for MAPMTs at D1 and D2
are connected at:
http:/www-d0.fnal.gov/~krivkova/fpd/signal_way_D1D2.html/.
The cables should be tested for:
i) Short Circuit: we do not want the ground wire to touch the signal wire
and we must observe infinity. Since sometimes the infinity is also reached
just by the bad contact, it's better also to check how many ohms are
measured during the open circuit test.
ii) Open Circuit: we test for the continuity since we do not want broken
wires. We should observe some finite number (~ 200 ohm) and this number
should be same for all cables. Since we have 16 channel cables so when
this value is smaller by 7ohm or 15ohm, we are possibly dealing with
short circuit.
The numbers of the test of the ribbon cables which were pulled between the
P1, P2 and the collision hall are:
P1 <-> coll.hall
----------------
cable number open circuit short circuit
------------------------------------------
16C20470 233ohm infy
16C20471 219ohm(bad ?) infy
16C20472 220ohm(bad ?) infy
16C20473 231ohm infy
16C20474 234ohm infy
16C20475 234ohm infy
16C20476 234ohm infy
16C20477 234ohm infy
16C20478 234ohm infy
16C20479 233ohm bad (15ohm - 1st end; 1.5ohm -2nd end)
P2 <-> coll.hall
----------------
cable number open circuit short circuit
------------------------------------------
16C20020 226ohm infy
16C20021 215ohm (bad ?)infy
16C20022 228ohm infy
16C20023 228ohm infy
16C20024 227ohm infy
16C20025 229ohm infy
16C20026 228ohm infy
16C20027 227ohm infy
16C20028 228ohm infy
16C20029 227ohm infy
Inside coll.hall (Bunch 1)
----------------
cable number open circuit short circuit
------------------------------------------
16C20580 227ohm infy
16C20581 infy ? (BAD) infy
16C20582 227ohm infy
16C20583 228ohm infy
16C20584 227ohm infy
16C20585 228ohm infy
16C20586 228ohm infy
16C20587 224ohm infy
16C20588 226ohm infy
16C20589 228ohm infy
Inside coll.hall (Bunch 2)
----------------
cable number open circuit short circuit
------------------------------------------
16C20590 203/198ohm 4.8 (BAD)
16C20591 228ohm infy
16C20592 228ohm infy
16C20593 227ohm infy
16C20594 228ohm infy
16C20595 232ohm infy
16C20596 228ohm infy
16C20597 228ohm infy
16C20598 227ohm infy
16C20599 235ohm infy
Remote cables and HV cables connected between the tunnel and the
control room for dipoles (should be check during the next access)
tunnel control room
------ ------------
LMB, SLP in green cable labled as 'D1'
LMB, PIN out green cable labled as 'D2'
D1 L0PMT black thicker cable
D2 L0PMT black thiner cable
AMP remote green cable labled as 'A2I'
driver remote green cable labled as 'A2U'
L0PMT HV red cable labled as 'DIP'
MAPMT HV red cable labled as 'A2D'
The picture on how to connect the extra 12 m cables is:
http://www-d0.fnal.gov/fpd/FPD_News/cable-ex.jpeg.
==============
Next Shutdown:
==============
Presently there are no access scheduled this week. The overall schedule is
to continue with proton only comissionin until sometime next week. Then we
will commision some with pbars. After that the plan/goal/hope is to give
several stores of luminosity per week to CDF (and us.)
CHRISTOPHE There was an access in tunnel this Thursday (Christophe, Sergio, Lionel). Eduardo stayed in the small control room to move the pots with the program. We encountered huge problems during this access while testing the pots at D1, D2: 1) The rack monitors became hot again despite the separate 5V power supply. Again, the consequence of this is that we lose all control from the control room as there is no longer communication between the power PC and the rack monitor. The separate 5V power supply did not cure that problem. The problem is intermittent and we could not find its origin. We tried to remove the ground cable between the IN and HOME switch and the electronic card to see if that had an effect but it was not enough. We also measured the currents and the voltages on the cables going to the rack monitor. We got 100 mA on some pins of the cable between the rack monitor and the interface board. 2) We had huge difficulties to move D2. The motor got stuck when we were trying to move D2 both in low and fast speeds. This is the first time this occurs also in low speed, both while using the program from the small control room or doing it locally in the tunnel. The same test was performed with the same detector fully equipped about two weeks ago, and it was moved fine without any problem. Maybe the weight of the detector could modify a little the inside part, and that it is then more difficult to move it. In fact, we had to remove the detectors to be able to move the pot at D2. We finally managed to move it to IN or HOME positions by alternating fast and low speed when the motor was stuck. 3) When the motor is moving, it is also not moving to the correct position. At low speed the number of turns seem to be exactly what is asked in the program running in the small control room. This is apparently not the case when we move at fast speed (we requested for instance to move 20 turns at fast speed, and the result was more close to 100 turns). This is also not understood. 4) As a consequence, I think we should install a full test of the system at LAB 6. We should move one pot from NWA to LAB6 and install it there fully with the pseudo-detector, the rack monitors, and a PC to be able to run the program. Hopefully, the problems to move the pots and the rack monitor heating will appear there, and it will be easier to solve those problems from there than from the tunnel. The 5 Amps fuse for the amplifier crate (5, 10, 15 V power supplies) was burnt. We replaced it by a 3 Amps fuse, since we had no 5 Amps fuse at that time. LIONEL The source code of Python script written by Lionel to control the pots can be found at: http://www-d0.fnal.gov/fpd/FPD_News/RmMotorFrame1.py. PETRA Information about the Amplifier Boards which are now down in the tunnel at D1 and D2: Setup: I had remotely turned on the AMP power supply. I had the HV turned off. I had the set of three ribbon cables coming from the tunnel connected to FERA's in the following order: layer MAPMT<->AMP 1st ribbon 3rd(control room) FERA (from the left; cable cable ribbon cable starting by 0) d1u 11 16C20489 16C20030 0 d1u' 12 488 031 1 d1v 13 486 033 2 d1v' 14 485 034 3 d1x 15 484 045 4 d1x' 16 483 046 5 d2u 21 569 040 6 d2u' 22 568 041 7 d2v 23 567 042 8 d2v' 24 566 043 9 d2x 25 565 044 10 d2x' 26 482 047 11 There are two MAPMTs per AMPboard. We have 6 AMPboards. board 1 : d1u & d1v' board 2 : d1u' & d1x board 3 : d1v & d1x' board 4 : d2u & d2v' board 5 : d2u' & d2x board 6 : d2v & d2x' In the file http://www-d0.fnal.gov/fpd/FPD_News/y00m09d04t1721.txt. there is info about the pedestal which I received via running 'peds' program. This file is also on our computer (d0lxfpd01): /data/peds/y00m09d04t1721.txt The second column is the number of FERA (same as in my table above), the fourth column is the average value of pedestal, the sixth column is the final (when above 255 - reduced) value of pedestal. When you go through you see that: BOARD 1 : d1u (FERA 0) pedestal is above 255 in the channels: 6,8,11,15 other channels looks ok d1v' (FERA 3) pedestal is above 255 in the channels: 3,9,12,13,14 other channels looks ok BOARD 2 : d1u' (FERA 1) pedestal is above 255 in the channels: 7,8,9,13,14 other channels looks ok d1x (FERA 4) pedestal is above 255 in the channels: 0,1,5,6,7,9,10,11 other channels looks ok BOARD 3 : (BAD - positive pedestal !) d1v (FERA 2) pedestal is too low in the channels: 0-9 other channels looks ok d1x' (FERA 5) pedestal is too low in the channels: 0-2,4,6-15 other channels looks ok BOARD 4 : (BAD - positive pedestals !) d2u (FERA 6) pedestal is too low in the channels: 0-10,12-15 one channel is good d2v' (FERA 9) pedestal is too low in the channels: 10-15 other channels looks ok BOARD 5 : d2u' (FERA 7) pedestal is above 255 in the channels: 1-8,11,15 other channels looks ok d2x (FERA 10) pedestal is above 255 in the channel : 7 pedestal is too low in the channel: 12 other channels looks ok BOARD 6 : d2v (FERA 8) pedestal is above 255 in the channels: 3-15 other channels looks ok d2x'(FERA 11) pedestal is above 255 in the channels: 0,3-15 other channels looks ok [Please, check this info with the attached file] If you look at that file you see that pedestals are only few times higher then 700 (the ADC gate was 310 ns). The memory of FERA's is 2047. I think we should just change the software to be able subtract the higher pedestals. So we have in the tunnel two BAD boards (positive DC offset). We (me and Mario) tested these boards for the signal transmission - all boards - all channels are good. We have also three boards with signal in all channels in the control room or Lab 6 (Lionel should know where he put them). I labeled them like all channels good; higher pedestals'. We can take these and change them with the bad ones in the tunnel (but for sure just check value - see previous mail about the AMP test). I don't think that the value of pedestal change much with the HV on. SERGIO + EDUARDO These are the instructions from Dave Burk (X-3235) on how to construct the plastic frames of our detector: - Clean the mold from any flashing. The molds are made of RTV (Shin-Etsu KE 1310 ST) and you can use a piece of wood, alcohol and acetone to clean it. - Put some mold release (MR300) inside the mold. The spray should be used inside the distillation hood fan. Do not put it too often because it makes the frames to loose precision. After you spray the mold release, brush around. - Close the molds. For the small one, put a rubber band close to the top. For the large frame mold put the 7 brass rods across and finish with the 2 acrylic plates. Be careful to avoid deformation. - Start making the polymer. You have at most 15 minutes to do that before it starts curing. You should use the UC40 from Conap. UC40-A is a urethane prepolymer and UC40-B is the curative. Note that UC40-A is water sensitive so back fill the can with nitrogen each time you refill the small jar. UC40-A and B should be used in the proportion of 2(A):1(B). First of all, mix the UC40-A with 2 % (2 per hundred of resin) of the black dyer additive. Like a good dry martini, please stir, do not shake it! The large frame takes ~ 62 gr. and the small one, ~13 gr. So use 50 gr. of UC40-A and 25 gr. of the UC40-B. - Assemble the funnel plus the plastic tube in each mold and fill with the mixture on the top of the scale. - Put the molds in the vacuum bell. Let it stand in an angle with the horizontal and cover with a plastic bag. Close the air valve (perpendicular to the pipe) and open slowly the vacuum pump (parallel to the pipe). Let is reach ~ 0.5 atm. Shut down the vacuum and start opening the air very slowly. If something gets wrong, do not try to clean the mold. Let it cure first. - Do not take the frames off the mold before 12 hours (best 24 hours) otherwise the mold itself can be damaged. To cure in the oven is faster but we loose precision. EDUARDO Instructions to operate the pots movement software - Login in d0ola from d0mino username: peyricli password: fpd2000 - Set the DISPLAY as needed - On prompt type: fpd - The fpd controller software must pop up in a window. - Click on the pot button you want to be moved. - On the Speed menu box choose the speed; low or high. - Click on Home button to move it to outside most position - On the New Position dialog box, type the position you want the pot to be positioned, in motor turns units, press enter key, and click on the run button. - Click the stop button to make it stop anytime. SERGIO There are two other drawings from Newton available: "Decoder/Counter" and "PDS Driver Interface".
CHRISTOPHE
Here is a short summary of the activities in the tunnel yesterday. This
was a long access between 7:00 am and 5:00 pm.
1) Pull and label cables in the collision hall:
===============================================
Sergio, Mike, Eduardo tested the ribbon cables in the collision hall (the
ones between the collision hall and the small control room), labelled
them, and pulled them to the small control room [see Sergio's comments
below]. It is extremly difficult to pull these cables and to pass them
through the rails. We have to think about another way or path for the next
ribbon cables for all the detectors since there will be not enough space
there.
2) D1 - D2
==========
D1 is moving without any problems now, both with the program and with the
switches locally (see the remarks about the RM in the following). D2 is
completely stuck, and cannot move at all from the home position with the
detectors. I think during the next access (probably next week), we should
try to move D2 back and forth without the detector, and try with the
detector after the 1st test is successful.
3) RM heating problem:
======================
Lionel and Christophe tried to move D1 during the last hour of the access
to try to investigate in more detail the RM heating problem. When one
pushes (even by hand) the switch which tells the HOME/IN position, the
rack monitor becomes hot (probably this produces a spike in the circuit,
which makes the rack monitor crazy). We added a resistor (470 Ohms) to the
circuit, and then, everything was working fine. This makes me think that
we have now found the reason of the problem, and we should modify the
interface board to avoid the spikes coming from the switch. Of course,
more longer and intensive studies at LAB6 will be needed. As Newton said,
we need to put a resistor in series with the switch on the interface board
and not on the alarm line.
4) Wrong position problem:
==========================
Again, Lionel and Christophe tested the problem of the motor going to a
wrong position in the last hour of the access. I remind you that the
numbers of turns of the motor were completely wrong at high speed: if one
requests 100 turns for instance, the motor was going close to 100 turns,
passed it, stopped, restarted, and went to 300 or 400 turns. The reason
seems to be that the decelleration of the motor was too small, and the
motor was always going further than the requested number of turns. By
changing the decelleration speed (increasing it), the problem seemed to be
solved again at D1. This needs to be modified again for all detectors
during the next access and tested extensively at LAB6.
5) Amplifier crate problems:
============================
Petra, Lionel and Christophe tried to change the burnt fuse of the
amplifier crate power supply during the last access. We burnt three other
fuses and were not able to solve the problem. We used 5 A and 8 A fuse
with the same result. There might be a short circuit inside a power
supply. The ampliifer crate was taken out of the tunnel and put to LAB6
where it will be tested.
6) Cable labelling and testing:
===============================
Petra, Lionel and Eduardo labelled the green cables going to P1, P2. The
red cables are not finished yet, and should be tested during the next
access (the procedure is always to send 5V on a given cable from the small
control room and see if these 5V are reaching the tunnel).
7) Electronic racks:
====================
The electronick rack at P1 is ready, Lionel almost finished to install it.
The amplifier crate and its power should be installed during the next
access. P2 still needs to be done.
8) Move pots at P1/P2:
=======================
We tried successfully to move the pots at P1/P2. There is a problem to put
the detector at P2 IN position. First, we need to move the pot IN, and
then, put the detector. If not, there is not enough space to put the
detector inside. Once this is done, there is not enough space to move the
pot totally out (2 to 3 millimeters are missing). Mike went to observe
this, and probably the cryogenic bypass is misaligned.
MIKE
There is no definite schedule yet, but the latest thinking is that there
will be another attempt at a shot early next week. Possibly on Tuesday.
The store would be a 1x8 store (1 proton bunch and 8 pbar bunches) which
would give collisions at both CDF and D0.
There is a reasonable chance that this store would be successful and we
could have a chance to test some of our detectors. We have done a 1x8
store this week in the Tev but the pbar intensity was very low and we
did not go to low beta. Hopefully we get higher pbar intensity next time
and can get to low beta.
Doug Allen will move a pot to Lab 6. It will be on a dolly and under
vacuum. Also, I talked to Doug about the problem with the P2 outer
detector not fitting in our pot because it interfered with the cryo
bypass. Our theory about the bypass being misaligned may be correct. When
they were installing the bypass they had some trouble with interference
with some bolts that were too long and the bypass may have been moved
downward to compensate. During the winter shutdown the bypass will be
removed and when it is re-installed (with shorter bolts) and we can pay
closer attention to its alignment.
I also talked to Doug about the winter shutdown and we will have to
think about removing our detectors, getting cables out of harms way, and
moving our racks out of the way. We will have to do these things in the
first few days of the access before they start removing the pots,
separators, and low beta quads.
MIKE MARTENS + SERGIO
Test of cable:
coll.hall <-> control room
---------------------------
cable number open circuit short circuit
------------------------------------------
16C20600 227ohm infy
16C20601 224ohm infy
16C20602 229ohm infy
16C20603 225ohm infy
16C20604 228ohm infy
16C20605 infy (BAD) infy
16C20606 228ohm infy
16C20607 227ohm infy
16C20608 230ohm infy
16C20609 228ohm infy
Ribbon cable connections between P1, P2, the Collision Hall (CH) and the
Control Room:
P1 -> CH CH
16C20590 (BAD)
16C20470 ===== 16C20591
16C20471 (BAD)
16C20472 (BAD)
16C20473 ===== 16C20593
16C20474 ===== 16C20594
16C20475 ===== 16C20595
16C20476 ===== 16C20596
16C20477 ===== 16C20597
16C20478 ===== 16C20598
16C20479 (BAD) 16C20599
There is still a bunch of cables to be tested and connected but this can
be done outside of the Collision Hall.
P2 -> CH CH CH -> CR
16C20020 ===== 16C20580 ===== 16C20600
16C20021 (BAD) 16C20581 (BAD) 16C20601
16C20022 ===== 16C20582 ===== 16C20602
16C20023 ===== 16C20583 ===== 16C20603
16C20024 ===== 16C20584 ===== 16C20604
16C20025 ===== 16C20585 16C20605 (BAD)
16C20026 ===== 16C20586 ===== 16C20606
16C20027 ===== 16C20587 ===== 16C20607
16C20028 ===== 16C20588 ===== 16C20608
16C20029 ===== 16C20589 ===== 16C20609
PETRA
During the last access:
1) I put the tape into the cartridges of the pseudodetectors (P1I, P2I, P2U).
I didn't have time to put the tape into P1U.
2) I connected P1U, P2U, P1I, P2I with the HV and the signal 104 m long
cables:
HV:
detector cable
-------- -----
P1U P1P
P1I P1M
P2U P2S
P2I P2M
Now I would like to turn on the HV and look at the L0PMT response (noise,
cosmic rays).
When I put the tape inside the pseudodetectors (P1I,P2I,P2U) I saw: there
is an air-gap between the scintillating rode and the PMT about 2mm. Such
gap is also in the real detectors- about 3mm.
3) 8 new green cables and 5 HV cables on the proton side was successfully
tested.
* About the timing and trigger system (detectors at D1, D2):
After the next access we should be able to take data with detector at
D1, D2 (the electronics for proton side will not be probably ready).
Timing:
- Signal from L0PMTs:
D1 - 535ns (black thick cable, 443' long)
D2 - 555ns (black thin cable, 443' long)
(Probably we will have to shorter them)
- Signal from MAPMTs:
D1:
16ns (3m cable between MAPMT and AMP)
7ns (AMP)
600ns (3 ribbon cables)
-------------------------
623ns total
D2:
32ns (6m cable betwee MAPMT and AMP)
7ns (AMP)
600ns (3 ribbon cables)
-------------------------
639ns total
We have to produce the ADC gate before the signal from MAPMT arrive to
FERAs. Now for this we have: ((D1-MAPMT)-(D2-L0PMT))=(623ns-555ns)=68ns
only (I neglected a few ns between D1 and D2.). It's not enough:
- Delays of the individual units which we have to use to create the ADC
gate:
discriminator(NIM): 7ns
logic unit(NIM): 15ns
prescaler(NIM): 10ns (please somebody check this)
LAM(Camac): 28ns
ADCgate (gate generator)(NIM): 14ns
FERAdriver(Camac): 20ns (according to FERAs manual you need to
have the gate created 20ns before the
signal arrives)
cables (at least!): 20ns (put 1ns cables between the NIM
modules and the 4ns cables between the
NIM and Camac modules ! You will
probably a little bit rearrange the
modules in the NIM rack. You should
also find somewhere 4ns cables.
-----------------------------------
to produce the ADCgate: 114ns
The schematic of the trigger system can be found at:
http://www-d0.fnal.gov/fpd/FPD_News/trigger.jpeg
For trigger we need: 114ns
now we have: 68ns
Solutions:
1) Put the extra cables between the MAPMT and AMP. In our control room we
should have 13 12m long cables - 53ns each (68+53=121ns>114ns).
2) Shorter the black cables!
Your comments are more than welcome.
CARLOS AVILA For the Data Aquisition, see the homepage: http://www-d0.fnal.gov/~avila/fpddaq.htm. PETRA Here are some information about: 1) cable connection 2) new green cable test 3) testing of the trigger system 4) test of the rest of the pseudodetectors in Lab6 1) Cable connection ------------------- During the last access I connected the L0PMTs: detector HVcable green cable -------- ------- ----------- P1U P1P GCRP101 P1I P1M GCRP104 P2U P2S GCRP201 P2I P2M GCRP204 Dipole side L0PMT were already connected: detector HVcable green cable -------- ------- ----------- D1 D1P thicker black cable D2 D1P thinner black cable 2) New green cable test ----------------------- I tested the new green cables (8 104m long cables between the CR and proton side). I just plugged these cables to the scope and looked at the noise: - cables GCRP101, GCRP102, GCRP103, GCRP104, GCRP202, GCRP203, GCRP204 are ok (noise is below 1mV) - cable GCRP201 picks up the 60Hz (amplitude of this noise is +5(-5)mV) 3) testing of the trigger system -------------------------------- I turned on the HV and looked at the noise and the cosmic rays signal using the scope: P1U: ---- HV=1800V, noise below 1mV, signal -3mV, frequency of this signal (which looks more like the noise) appr. one per 2min. P1I: ---- HV=2200V, noise below 1mV, no signal P2U: ---- noise 60Hz P2I: ---- HV=2000V, noise below 1mV when the HV is off, signal <5mV every second (is it noise?), signal above 5mV (not higher than 10mV) with frequency 24events per 4min D1: --- HV=2000V, noise below 1mV, no signal D2: --- HV=2000V, noise below 1mV, signal app. 5mV, I saw only two signal in appr. 10min. 4) Test of the rest of L0PMT --------------------------- HV=-1900V. I inserted the pseudodetectors into the castle and varied the air gap. The rate of the signals (higher than 120mV) per 8min: Pseud.#1: -------- gap 5mm 3mm 2mm 0mm rate 81 80 105 93 Pseud.#2: --------- gap 2mm 0mm rate 113 95 About the access of Oct/10: - Before access --------------- I went to the control room and checked the noise and the 'possible' cosmic rays in D1 and D2 detectors, because in that time the Tevatron magnet were turned off and because we have no shielding around our photomultipliers. I didn't see the cosmic rays - I looked for few minutes. - AMP. power supply ------------------- During the last access we took out the amp.power supply (these are actually two power supplies: one:+5V,+15V,-15V, second: +12V, -12V), because it burned fuses. Lionel checked this supply in Lab6 and it worked ok. In the tunnel we installed it back today: - I plugged both power supplies directly to the outlets. It worked ok. outlet outlet | | | |_________+5V,+15V,-15V power s. | |_________________ +12V,-12V power s. - Than I plugged the power supplies to the power box and the power box the the outlet to the second outlet I plugged the fan. I had a green cable with +5V. When I plugged the green cable into the power box the fuse of the +12V,-12V power supply burned. We didn't check the fuse of the second power supply. The power supplies are still in the tunnel, because we didn't have time to move them out. outlet outlet | | | power box <-- +5V (green cable) | | | | | |______+5V,+15V,-15V power s. | | | |_________ +12V,-12V power s. fan Do you have an idea why it could happen ? - AMP boards and crates ------------------------ After the yesterday test we (Eudardo and me) end up with six good amp. boards (all channel good, negative DC offset - it would depend on the ADC gate if these pedestals will be greater than 255). Because the plan was to have D1,P1U,P1I working (possible to move the pots from the control room) and because D2 gets stacked, I put one crate (three amp. board) to D1 and connected them with the cables; I put one crate (three amp. board) to P1; Because we didn't have time to finish the proton side and we had anyway only three amp.boards at D1 I -> see below) : - Pseudodetector at D2 ---------------------- During the weekend: I tested in lab6 two pseudodetectors with the cosmic rays (I measured the signal higher than 120mV at rate 80-100/8min; HV=-1990V). I looked at the cosmic rate and noise at D1 and D2 (i've seen only the small signals 5mV and only two of them in appr. 10min period). Tunnel: Since we installed only three amp.boards at dipole side I put out the detector at D2 and inserted the pseudodector from lab6. After the access I chacked the rates of the cosmic with the pseudodectector at D2. I've seen two signals 5-10mV in few minutes (I will look at this more carefully tomorrow) - AMP headers -------------- The header on the AMP board are kind of loose - bad contact causes the bad channel - when you insert the header better the channel is good again. We should start to prepare the AMP. board for RUNII - solve the header problem EDUARDO + SERGIO During today's access we (Eduardo + Sergio) have tested the movement of the detectors at D1 and D2. The detectors were remotely moved by Eduardo through the software from the small control room. - D1 runs fine in both directions (IN & OUT). It worked even at high velocity perfectly well. We have also measured the reading of the LVDT when it is the IN and OUT position and checked the linearity of the readings. During all the tests the Rack Monitor did NOT get hot and worked fine. There was however some fluctuations of the LVDT reading when the pot was stopped at or near the outside-most position. Below we have a correspondence table for the number of turns and LVDT obtained moving the pot at high speed. The registered values are the ones that were displayed immediately after the "stop" condition appeared. TURNS LVDT (Subsequent readings) HOME-> 0.7 500 3.76 (1.27, 2.89, 2.96, 3.67, 0.03) 1000 6.71 (6.73, 6.72, 6.70, 6.73) 1500 9.73 (9.74) 2000 12.72 3000 18.74 4000 24.74 (24.72, 24.75, 24.76, 24.73) 4500 27.76 (27.77, 27.75, 27.74) 4600 28.38 (28.37) 4700 28.96 (28.97) 4750 29.26 (29.27) IN-> 4757 29.30 (29.29) The pot was then moved back from IN to HOME position at high speed without problems. - D2 moved well going inside. However, when it was moved toward the outside position (HOME) at high speed it got stuck several. After reducing the speed, it went well. - It was possible to move the two pots at the same time. However only the information about one of them is accessible at a time. When the information about D1 was being displayed and D2 got stuck, no warning was noticed. Some problems found: 1) The LVDT reading oscillates close to the HOME position. For D2 it stays around 1.63 (1.61, 1.01, 0.00, 5.09, 1.59); 2) When moved to the position 3000 turns from the HOME position at high speed, it went up to ~31 at the LVDT reading and started to move back to HOME without stopping. It was not possible to built a reliable table for the LVDT as function of the number of turns. 3) In one of the tests the switch limit did not stop correctly the motor when it reached the HOME position. What is strange is that it happened after 4 or 5 times stopping well at HOME. It seems that the screw that determines the right position where the motor must stop becomes loose; 4) Once you reconnect the driver-rack monitor cable to the driver the motor starts running by itself. We had to turn the software ON and send a STOP command; 5) In one of the tests D2 just touched the IN position and keep running back to HOME, without stopping. After the acceleration of driver were changed by Lionel it started working fine LIONEL Before access: * make 6 small resistor boards for Interface Board/Rack Monitor heating problem. * test amplifier crate and Power Supplies (+5V, +10V, -10V, +15V, -15V). It worked ok. During access: * put and test Amplifier crate and Power Supplies at D1-D2. They worked ok when they were connected directly to the outlets. The power supply (+10V, -10V) burned the fuse (5 Amp), when we have connected it to the power box. * move D1 in In and Home position. It worked OK. * connect 1 small resistors board at D2 and 1 at D1. The heating problem disappeared. * put Amplifier Crate and Power Supply at P1. * move P1 Up in In and Home Position. It moved OK but it must be tested with the software. MICHAEL STRANG I've got a preliminary code written up to try to handle multiple hits in a detector. It is generic right now and basically discriminates the DAQ ADC to determine what fibers are on then goes through the simplest (i.e. fewest particle) possible segments combos that could be on. It has a limit on the number of fibers that can be on in a view to try to simplify things but this can be changed if necessary. It is meant to be used as a uwfunc in paw but it is in a standalone mode right now that allows you to type in the number of particles and the detector (xd,yd) locations for the particles. It then determines what fibers would be on. The rest of the code finds the segments and then permutes through all the possible U,V combinations and looks for valid X segments to determine good hits. As the number of particles increases the possiblility of more convoluted segments increases and the code is likely to improperly reconstruct but until we start getting actual data it is unclear whether the effort to include these possibilites is warranted. Also, as the number of segments increase and the particles become close together, incorrect reconstructions increase as well. Anyway, anyone who is interested is free to look at the code and please comment on it. I've tried to put as many comments as to what is going on as possible. The code can be found at: http://www-d0.fnal.gov/~strang/work/fpd/daq_code. After saving all three files to your area, you can compile the code with something like f77 -o cluster.exe cluster.for Then just type cluster.exe. It will output to the screen and wait for you to type some number in to continue. Then the printout shows it going through all the steps and deciding if it is a good reconstruction or a bad reconstruction. It can be bad if it doesn't use all the segments or if it reuses the segments too often. geom.inc contains some constants that are being used and can be used to turn the output on and off by setting the output and output2 variable to 1 or 0. If you change anything in geom.inc you need to recompile. Let me know if it seems like it will work or if you think there are some things I should change or if you have any questions about what I'm trying to do. Thanks.
WAGNER (27/Mar/00) I left the 28 tested PMT's inside our cabinet at Lab 6. All of them should be labeled with their serial number and wraped into bubble plastic. You can find the docummentation at d0mino files: http://www-d0.fnal.gov/fpd/FPD_News/PMT_test.txt. http://www-d0.fnal.gov/fpd/FPD_News/PMT_plateau.ps. The first one describes the testing procedure as well as some more data on PMT's pulse height and counting rates that may be useful. The second file contains the plateau curves for each tube. Unfortunately I did not test the PMT boards, I just forgot it. To test them it should be enough to plug the base to a standard PMT and check that a good signal may be observed, going through the steps: 1- Before starting, certify that HV is OFF!! 2- Open the dark box, carefully connect the base to the tube, close the box; 3- The base must be connected through a HV red cable to the power supply; 4- The PMT signal will be read out through a green cable; 5- Adjust the HV to some standard value, 2000 V for instance (this is the same voltage I used for PMT tests, see PMT_test.txt); 6- Turn the HV ON; 7- Use the osciloscope to observe the PMT signal (if it is not immediately visible try adjusting the osciloscope threshold); 8- Use the scallers to determine counting rate for the PMT; 9- Turn HV off. This procedure should first be done for one of the bases that I have used before and that must still be inside the dark box or around, in order to set a pattern for the bases that will be tested. If the base under test behave in a similar way to the standard, one it should be ok. If no signal is seen, it is likely some disconnected wire, check first a wire that connects the HV termination to the board and which is soldered to the board. The base can also be noisy. In this case the osciloscope signal will be unstable or maybe too high. The noise may be due to a bad connection or soldering, check to see if the HV connections are in good shape. If it is not a bad connection, well, then I am not the person to ask for! Try to find a technician or engineer! CHRISTOPHE We had our first trigger data last Friday (the 13) night with D1. Petra, Eduardo, Lionel and myself were in the small control room while Mike was in the Tevatron control room. There were 4 bunches of antiprotons in the machine and 1 bunch of proton. The antiproton halo rate was about 120 Hz. We put 1600 V on the L0 PMT at D1, and moved the pot millimeter by millimeter. The trigger rate at D1 was found to be small (about 70 counts per minute with a threshold at about 0.2 V) until we moved the pot by about 30 mm (the rate was found to be 1kHz at 30.3 mm). We clearly saw the correlations between the Tevatron clock and our trigger signal, and we also saw the 4 antiproton bunches. The effect on CDF was to increase a little their halo rate by about 10%. The peaks observed in the trigger were between 1 and 3 V, which is astonishingly high. This was the 1st time we were able to move a pot close to the beam and to get some coincidences between the Tevatron clock and our roman pot trigger data. During the 4 hour access last Monday, we manged to get D1 fully working, both the trigger, and the amplifier boards. Lumi is expected either tomorrow or Thursday and we should be able to setup the trigger and get our first data at that time. The short circuit which was present during the last access on the amplifier board is located in the LED calibration system. This is taken out to LAB6. We also tested that it is possible to move D2 (at low speed only, since it is stuck at high speed), and it should be possible to observe some coincidences between D1 and D2 at the trigger level during luminosity. P1 is close to be ready, and will probably be finished during the next access next week. We had a problem which is not yet understood according to which the home position was not detected by the interface board. We took the interface boards to LAB6 to test them. MARIO The voltage should be negative and need to be less than 1kV for the MAPMT. SERGIO The cable connection for the MAPMT's of P1up are: Small Gray Cable == Large Blue (Gray) Cable 1 == 16C20473 == 16C20593 2 == 16C20474 == 16C20594 3 == 16C20475 == 16C20595 4 == 16C20476 == 16C20596 5 == 16C20477 == 16C20597 6 == 16C20478 == 16C20598 Helio and Mario sent me some pictures of the castles. They are: First plastic model of the castle: http://www-d0.fnal.gov/fpd/FPD_News/Pictures/Pot1.jpg. General view of LNLS Synchrotron: http://www-d0.fnal.gov/fpd/FPD_News/Pictures/sincroton.jpg. Castle assembled at LNLS: http://www-d0.fnal.gov/fpd/FPD_News/Pictures/montag1.JPG. Castle chamber assembled at LNLS: http://www-d0.fnal.gov/fpd/FPD_News/Pictures/chamber2.jpg. Castle chamber ready: http://www-d0.fnal.gov/fpd/FPD_News/Pictures/chamber.jpg. Castle prototype at LNLS: http://www-d0.fnal.gov/fpd/FPD_News/Pictures/FERMI02.jpg. Castle performance tests: http://www-d0.fnal.gov/fpd/FPD_News/Pictures/PIC00009.jpg. Castles ready to go to Fermilab: http://www-d0.fnal.gov/fpd/FPD_News/Pictures/PIC00011.JPG. Castle presentation at Fermilab: http://www-d0.fnal.gov/fpd/FPD_News/Pictures/aprefnal.tif. Final preparation of the castles at Fermilab: http://www-d0.fnal.gov/fpd/FPD_News/Pictures/hfpdmont.tif. Quadrupole castle in the tunnel: http://www-d0.fnal.gov/fpd/FPD_News/Pictures/tunel1.jpg. Detectors (Petra) http://www-d0.fnal.gov/fpd/FPD_News/Pictures/FPDLab3.jpg. Detectors at Lab 6: http://www-d0.fnal.gov/fpd/FPD_News/Pictures/FPDLab4.jpg. Detectors (Petra + Newton): http://www-d0.fnal.gov/fpd/FPD_News/Pictures/FPDLab6.jpg. Tunnel (Lionel + Newton): http://www-d0.fnal.gov/fpd/FPD_News/Pictures/FPDTev1.jpg. Tunnel (Newton): http://www-d0.fnal.gov/fpd/FPD_News/Pictures/FPDTev2a.jpg. Detectors in the tunnel: http://www-d0.fnal.gov/fpd/FPD_News/Pictures/FPDTev3.jpg. Detectors in the tunnel (Mario + Newton): http://www-d0.fnal.gov/fpd/FPD_News/Pictures/FPDTev5a.jpg. NEWTON There is apparently sometimes a problem with the castles such that when the pots are inserted they don't stop at the correct position, but hesitate, and then continue moving all the way to the in position. This is a hardware problem. Follow the steps to find the problem origin. - connect the board to driver and motor (with encoder) and hall sensor. - check if you can move the motor with the 3 board switches. - connect the board to the 16 control switches set. There is a 5V power supply attached to the set and it should be turned on in order to have the logic levels. - connect the board to the box switch that simulates the "home and in" switches. - put 5V power on the board. - check if all LEDs are working when you remove the home/in cable (3 leds will turn on) and when you simulate the use of the home and in switch. - Put a osciloscope probe on TP5 (Test point pin 5). The logic level must be zero with a running motor and must go high (5V when the motor reaches the counting and stops only) - Run the motor to home position (using the switches rule) and reset the counter with the box home switch. - Run the motor to some number of turns (few turns, about 10) at low speed and look at the scope signal. It should be low during the motor movement and should go to high and stay there when the motor stops. It must stay high until the next strobe cicle or if you turn of the 5V power. - Repeat the test at high speed to some number (about aprox.100 turns) and look at the scope signal. If the motor stops and runs again by itself and the signal goes from low to high and low again after the motor start again, you may have a problem with CI 9 (74HCT74). Look for a bad solder on CI pins (retouch the solders). Look for a bad disk capacitor (0.1uF, marked 104) very close to this CI, change the capacitor. This is a noise filter capacitor that should maintain the 5V to the CI. If you have a sudden drop on this value, the CI will reset itself and the logic level at TP5 will go to low and the motor will run again. - If the problem persists change the CI9 for a new one. Make sure the pins solders are perfect . - If the problem persists change the board. You may have a non visible short circuit between traces that is very difficult to find. I found all these problem causes in the past. Note that a problem with the strobe line from the rack monitor can generate the same type of problem. VITOR + CARLEY + JORGE We have a C++ version of the tracking code running in lafex_alpha1. This algorithm reads fiber numbers (from Jorge's fortran Code), transforms it first to segments, and then to Pot1 (X,Y) track coordinates. From there, it uses Jorge's and Sasha's strategy, together with Mike's separator model, to find the physical parameters xi and t at IP (z=0). We have checked this algorithm extensively this last week, always comparing it outputs to Jorge's fortran code outputs, and no major differences were found between them. This algorithm is a real C++ code (no f2c!), and we adapted the class Vector.h from CLHEP. At first, we tried to dig into Mike's C++ tracking, but we gave up, since it seemed somehow very complex to us. Xi- and t-resolutions were obtained for the 4 Pots in the proton arm, which you can find at the two ps_files in attachment. As previously seen with Jorge's fortan code, xi- and t-resolutions for vertical pots have Gaussian shapes, while they seemed to be more Lorentzian_typed shapes for horizontal pots. However, it seems that all pots have the same FWHM xi- and t-resolutions, what sounds reasonable, and not as in Jorge's previous results, where horizontal pots had quite large FWHM when compared to vertical pots. Our next steps are, for a first phase: - Work on the pbar arm. For quad pots, it will be a piece of cake. Include dipole pots will not be a very hard task; - Include multiple hits; - Include vertex displacement and reconstruct at z = 0. We think this phase would be done by the beginning of November. Second phase include to make the algorithm to conform with D0 C++ code standards and include it into the D0 framework.
CHRISTOPHE Last night (October 23), Petra, Jon, Lionel and myself were able to get our first data with D1. We used as a trigger D1 and D2 in coincidence, or D1 and D2 alone and wrote only a few events on disk. We moved D1 and D2 into the beam, first D1 and then D2 when D1 was already IN (D1 by 30.9 mm, and D2 by 30.1 mm). We clearly saw some events (halo + real interactions) both at D1 and D2. We also saw the influence of D1 on the halo since the rate at D2 at home position increased by a factor 10 (about 1000 hits per min) when D1 was in the beam. These events are probably only background and halo since the luminosity was extremely low at D0 (even below the scales of D0...). But at least, it shows that our system works, is able to trigger and get data. The next shot from the Tevatron is foreseen for next Thursday, and the aim is to take real p pbar interaction data by asking a coincidence D1/D2 and the luminosity counters from D0. This was not possible to perform it last night since the luminosity counters were blind last night (the luminosity was too small). The luminosity on Thursday is expected to be much higher. On October 25 there was a 4 hour access. Petra, Sergio, Lionel and myself were in the tunnel while Eduardo was in the small control room. We first finished to install the interface boards at P1. It was not obvious to do this since the boards had sometimes some problems to recognize the HOME or the IN position of the pots (I mean that the red LED is not ON on the board). Finally, we tested P1 UP successfully locally, and were able to move it in and out once. Due to the fact that we do not understand the problem of the interface boards, it is probably premature to move P1 remotely since it could remain stuck in the tunnel when there is beam. Further more, it was quite unfortunate that the D0 online was down during the access and we were not able to move the pots remotely during the shut down. At the end of the shutdown, we decided to move a detector to D2 so that we could have two detectors fully installed and working at D1 and D2. During this access, the rack monitors at P1 became hot again many times and this was the case when the RM were plugged in. This makes us think that the RM become crazy each time there is a spike in the voltage whatever the reason is (either it touches the switch indicating home position or we plug a cable to the RM). The LMB was installed back at D1 after having wrapped the circuit with a small insulator (you probably remember we had to move it back from the tunnel last time because of a short circuit). After the access, it was found that it is not yet working. We have no idea why... During the access, we put the 5V on the drivers (D1, D2 and P1), and it was noticed afterwards that D2 moved in by itself when we put the 5V. I know we already noticed that problem before when we were in the tunnel during previous accesses. This is why Lionel always sends a stop signal to all the pots when the program starts. This is of course a temporary solution for this problem since we basically do not understand why the pot is moving when we put the 5V. Unfortunately, the D0 online computer was down during the shut down and we were not able to control the pots remotely and this is why the pot kept up moving and did not stop. This is quite unfortunate and mainly due to the shutdown of the online computer. In the night, the Tevatron people found the dipole pots in the beam as they were turning on the beam. Eduardo was at the lab and got them moved out OK, but only after they had tried injecting beam for a while but could not circulate because the pots were in. One of the pots was at its in position and the other was almost all the way in. I think we should understand why the pots start moving when we put the 5V. This is a strange behavior, and may be this can be tested at LAB6? I also guess we should have at least one or two pagers to contact people in case of problems (fortunately, Eduardo was in his office, but the machine people on shift should have a pager to call in case of problems). We also should get the emergency line installed both in the D0 and in the Tevatron control room which puts automatically all the pots to home position independently of the software. This would still work for instance if the online computer is down. The aim is now to wait for lumi and to take as much data as we can with D1 and D2 before the long shutdown. Some lumi is expected tonight and tomorrow night with 36 bunches and collimators in.
PETRA Data taking on October 31 Record of what was happening in the control room and information on how cables are plugged to CAMAC: http://www-d0.fnal.gov/fpd/FPD_News/data_31Oct.txt Online histograms: http://www-d0.fnal.gov/fpd/FPD_News/adc_run111.ps http://www-d0.fnal.gov/fpd/FPD_News/adc_run114.ps http://www-d0.fnal.gov/fpd/FPD_News/adc_run121.ps http://www-d0.fnal.gov/fpd/FPD_News/tdc_121.ps Example on how the scaler information looked like before the veto output failed: http://www-d0.fnal.gov/fpd/FPD_News/camac_scalers.ps LIONEL On November 1st, we (Mike, Christophe, Lionel and Sergio) had an short access in the tunnel (2 hours). We: - Moved the pot P1 Up, P1 In and P1 Out in HOME and IN Position in high speed with the 3 switches box (blue box). All motors run without problems. - Moved P1 Up and P1 In with the 16 switches box to check if the pots go to the correct position. It is OK. - Moved P1 Up with the software (Sergio was in the small control room). Unfortunately, we can't move P1 In and P1 Out with the Software. I checked yesterday afternoon if the software configuration is OK and I tried again to move the Pots and nothing happened. Maybe we have some bad connections between the Rack Monitor and the Interface Boards. - Moved the detector from D2 to P1 Up and connected the ribbon cables to the Amplifier Boards. Now, we have: Detector 1st Ribbon Cables ??????62 (5) --------> 78 ??????60 (3) --------> 73 ??????60 (2) --------> 74 ??????61 (1) --------> 75 20C20563 (6) --------> 76 20C20463 (4) --------> 77 I'm sorry but I didn't check all the numbers (????), I think that the number in brackets are enough. - Connected the High Voltage Cables for the L0 (P1 In,P1 Out and P1 Up) to the HV Splitter and for MAPMT (P1 Up). For P1 Out, the signal cable (Green Cable) is GCRP1-03 (or P1O). So now, we have: - At D2, one pseudo-detector. When you move the pot, you must do this in low speed. If you have any doubts, stop the motor and put it in Home Position. I'll try to adjust the current position (LVDT) with the real position. - At D1, one detector. It can move at high speed. The difference between the current position (LVDT) and the real position must be small. - At P1 Up, one detector. High speed can be used. The current position (LVDT) must be calibrated. - At P1 In and P1 Out, one pseudo-detector but we can't move the motors. SERGIO Eduardo and I arrived at our Control Room at 9h20. After Christophe gave us some instructions from Petra, we started our shift. The very first thing we decided to do was to double check that the pots were at the HOME position. The FPD program was up with the 5V off. The reading of the Begel's memory monitor was showing 19%. We checked both pots. D2 readings were fine, i.e. at HOME position, however D1 had: LVDT: 26.94 mm D1 Status: STOP IN: YES So, we turned the 5 V on to have a reliable reading and we checked that it remained the same. We then started to try moving D1 to HOME. After several tries there was no change in the readings. We tried to put the pot at 10 mm and again all the readings remained the same. We turned the 5 V off, rebooted the software, starting a new process, running the FPD program and tunning the 5 V on again. We got exactly the same measurements as before for both D1 and D2. The readings of the LVDT's never changed during the whole procedure. After that, we decided to turn the 5 V off and I called at 9h45 the Main Control Room while Eduardo made some counts getting the reading for D1 ~ 100,000/5 sec = 20 kHz, which was much higher than for D2. We learned from the MCR that they just lost the beam after the quench at 3 different points. Mike Martens called from the MCR and decided to come over. After he arrived we discussed the whole situation. Mike Begel joined us and said that all the problem could be related to the memory leakage on the Power PC. So we decided to reboot also the Power PC. We restarted once again the FPD program, without the 5V, and the readings were: Status: Stop Status: Stop D1 LVDT: 26.94 D2 LVDT: 25.93 HOME: No HOME: No IN: No IN: No Since the reading should not be reliable without the 5V, we turned it on and got: Status: Stop Status: Stop D1 LVDT: 26.94 D2 LVDT: 25.93 HOME: No HOME: No IN: YES IN: No We tried to put the D1 pot again to HOME and no readings changed. We decided to move D2 to check if the communication with Rack Monitor was working, since we have visual contact with D2. We sent it to 10 mm. It run fine but the LVDT readings did not change. We STOP it and gave a HOME command. The visual inspection showed that it run OK all the time but the LVDT did not chance: it stop at HOME (HOME: Yes) and the reading still was 25.93. We repeated exactly the same procedure with D1. Sent it IN 10 mm, STOP after 2 minutes and sent it back to HOME. After waiting for 4 minutes the D1 reading did NOT change at all. We turned off everything and decided to ask an access to the tunnel to check which is the real condition of D1. Mike Martens and I will enter now and Eduardo is going to stay at our Control Room. Mike Martens and I had an access to the Tevatron tunnel at 12h30. We found D1 completely in. First of all we started to make some tests to figure out how was the communication with the control room. We asked Eduardo to put 5 V. Nothing happened. Mike turned a little bit the axis of the motor and it started going at high speed to the HOME position. We asked Eduardo to send around 5 or 6 STOP signal to the motor and it did not respond to the command. Finally it got to HOME. We tried to send other commands to the pot but it did not respond. We even turned on and off the 5 V and restarted the program twice. Then we decided to move the pot using the buttons on the board. The pot suddenly started to move in again and we were not able to make it stop. The buttons did not work, even the HOME one. Afterwhile we managed to put the D1 pot out. During the whole procedure the reading of the LVDT stayed the same, even when we tested D2. We called Andrew and decided to unplug all motors. We rechecked that all pots were in HOME position and left the tunnel at 14h30.
NEWTON
I have some comments about power for the interface board and rack
monitor.
I was surprised with the fact that the 5V power box line can turn off
the index interface board and the rack monitor. Itīs not the configuration
I left in the tunnel. When the interface turns off it looses the counter
information (the actual pot position). When it turns on again it can not
compare the position issued by the rack with the actual pot position. It
is necessary to issue a home command first to reset the counters. If the
software freezes and the rack sends a wrong signal , the counters will not
reset and you will have a random motion.
In the original configuration I left, one power box took care of the
stepping motor drivers only. The index interface was powered by the rack
monitor power supply and could not be turned off. Itīs not a good idea to
turn off the interface and rack monitor. If it is really necessary you
must have a separate power box.
It is necessary to have an independent power box for the stepping
motor drivers so the motors will not run while the signals from
computer/rack are not stable. Pay attention to the fact that you will have
a driver failure alarm signal from the driver for several seconds when it
is turning off. The driver power box may be turned on after after you are
sure about the signal good conditions. The alarm and LVDT signals may be
used as an indication. If there is no indication of movement from LVDT and
alarm movement line the driver power box must be turned off until the
problem is found and solved.
By the information I got the problem seems not to be with the
interface but a wrong signal sent to that interface and a lack of
independent control with the driver power box. The wrong reading of LVDT
during Pot motion suggests a software problem or a rack monitor failure or
a LVDT/signal conditioner failure.
SERGIO
The specifications of some of our hardware are:
DRIVER
Parker - Electromechanical Division
Product # PDS 15-2/USA
MOTOR
Parker - Compumotor Division
1.8 Step motor
Model OS 22B - DNFLY
1.54 A Bipolar Series
COUPLER
Berg
MOD COS78A-1
LVDT
Macro Sensors
Division of Howard A. Schaevith Tecnologies Inc.
GHSA 750 1000-0362
S/N 10967
1" Range, 150 C, AC
LVDT Signal Conditioner
LPC - 2000 - 100
ANDREW
There are several FPD issues, these are some of the most critical:
(Task force = *TF; Newton/Mario consult = *N/Mconsult)
1) 100% reliable pot control system (*TF): short term: debugging of IIB's
and verification of fully reliable control of pots; longer term:
multiplexing software upgrades
2) Reliable pot motion on high speed (*TF): right now D2 only operates on
low speed, this is not acceptable we need to have all pots operable on high
speed
3) Reliable amplifier system (*TF): problems with cables staying plugged in,
header contacts, etc. need new dedicated low voltage supplies.
4) Adapter board design (*NM) need to decide who will design boards and
parameters of design
5) aluminum box to house detectors (*N): if Newton comes, he should finalize
this design with Phill)
6) HV system setup (*M): Rick Hance is providing infrastructure but westill
need to get special HV cables and distribution boxes.
7) Trigger and DAQ system (*M)
8) Reconstruction software
9) Cabling (*NM)
10) Online Alarms
11) Shielding of cartridges (*N)
12) ORC (*NM)
13) Information flow
14) Detailed shutdown schedule
JORGE et al. They have posted three D0 Notes: Reconstructing Track Trajectories for the FPD (3788) Detector Identification in the FPD System (3789) Acceptance Studies for FPD (3790) MIKE MARTENS Here is an update on the pots and schedule as I know it as of this afternoon. Others may have more to add. Pots ---- GENTIL: This pot is ready for installation except for a broken IN limit switch on the lower arm. All motors, encoders, and encoder wheels have been removed from the castle. Last night I tested all four arms of Gentil while it was under vacuum. For the inner, outer, and upper pots I had a pseudo-detector in place with a ~5 lb weight on the end (and the lower arm was tested without a pseudo-detector.) The driver was calibrated for a fast speed of 10 rps and all four arms were moved in and out 3 times at fast speed without getting stuck. PACOVAL: Helio reports that this pot has been tested and is ready to go into the tunnel. LARANJEIRAS: The testing of this castle is in progress, but already there are some troubles. It was under vacuum during the testing. The driver was calibrated for a fast speed of 10 rps. The "right" arm. (i.e. looking at the pot head-on with the inner and outer arms farthest away we looked at the right one.) This arm was moved in and out on fast speed 5 times with a pseudo detector installed and ~ 5lb weight on the end. During this testing the motor froze up three times on fast speed while moving inward. Each time I stopped the motor and restarted it in fast speed and it worked OK for a while. The position where it hung up was different each time. Helio continued the testing of Laranjeiras and reported that the upper arm sticks at times when we try to move it. He feels that we will have to open it up to fix it. This is similar to the upper arm of Matinada. MATINADA: This castle has been let up with nitrogen and the top arm has been dis-assembled and cleaned. It will be re-greased and re-tested. (I could only get the grease early this afternoon because safety had to find the grease, I had to remind them what it was for, and had to reconvince them to let us have it.) The holder for the LVDT on the upper arm is stripped. After it was disassembled, Newton found that the nut gear had burrs on the threads at the place where the threads start. You can feel these with your finger and see them clearly with a magnifying glass. This could be the cause of the sticking - either directly or because it scrapes away the grease inside the threads. Newton said he had found this problems on some of the other nut gears when he disassembled the pots that were over baked. For those pots he removed the burrs with a knife edge and polished that portion of the threads. (Perhaps this is why PACOVAL and GENTIL work well now?) The PACOVAL and GENTIL pots were originally installed in A1 and A2 and were the pots that were over baked. Since these are both ready and tested we could put these two pots into A1 and A2 (instead of GENTIL and LARENJEIRAS.) This would give us more time to work on MATINADA and LARANJEIRAS. Schedule, etc. ------------- The tunnel work at C4 and D1 is still on schedule, more or less. The low beta girder on the C4 side is expected to be back in place early the week of November 27th. And our castles for the C4 side (A1 and A2) should be ready by then. I talked with Keith Dillow again about the cryo bypass at D1. He is aware of the situation and will take extra care to make sure the bypasses are installed correctly so that they do not interfere with our inner detectors. I also talked to Keith about the shielding. We still need to work out details amongst ourselves, with D0, and with Mike McGee, but Keith is aware we need a cable penetration and will not complete the shielding until we contact him with a solution. I saw Doug Allen and he will be at the lab Tuesday and Wednesday to let up LARANJEIRAS with nitrogen and pump it back down when we are ready to test the pot motion again. His number is x3691. HELIO The version 4 of the "D0 Roman Pot Castles Manual" is available at: http://www-d0.fnal.gov/fpd/FPD_News/manual4.ps The parts sent by LNLS have arrived. They are in a marked box in the LAB 6 cabinet. There is a motor to replace the one that is damaged, limit switches, some plastic covers and many screws, washes, and alike. There are also parts for the LVDT structure and a LVDT action arm. Here goes a report about the castle situation: ---------------------------------------------- MATINADA: It is now at Lab 6. Upper arm has shown problems moving at high speed. The castle was filled with dry nitrogen and the upper arm disassembled. Old grease was removed and replaced by a new one. Burrs on the gear thread were shaved out and arm was again reassembled. Vacuum must be re-established for final movement tests. Upper arm LVDT supporting structure was replaced by a new one sent by LNLS (thread had been worn out accidentally). All other three arms (left, bottom and right) were tested many times with the castle under vacuum and performed well at high speed. We installed a cartridge into the horizontal arms, what had no bad influence on the pots behavior. LARANJEIRAS: It is now at D0 service building. Upper arm was sticking. We have opened the upper arm and disassembled it. The old grease was removed and a new one applied. The gear threads had minor burrs that have been shaved out. The castle is reassembled. It must be put under vacuum again before a final set of test can be performed. The left arm has already been tested under vacuum. Once in a while it had difficulty at high speed when approaching the home position, but this was easily overcome at slow speed. This is not a problem and will probably disappear with repetition. GENTIL: It is now at D0 service building. All arms were tested at high speed and performed well. The bottom arm POT IN switch has been replaced by a new one sent by LNLS. POT IN position is, consequently, a little bit different from the one previously surveyed (a minimum difference almost certainly). All pots are in the IN position. Castle is ready for action. PACOVAL: It is now at NWA. All arms tested at high speed under vacuum. All arms have performed well. All pots are in the IN position. Castle is ready for action. MACACAO: It is now installed as D1. It has been performing well. GUAJARA: It is now installed as D2. It has been sticking at high speed with the cartridge in. Suggested actions. ------------------ GENTIL and PACOVAL are our two best QUAD castles. After the accident that resulted in their overbaking all arms were disassembled and experienced a complete overhaul (new grease and burrs shaved). They have passed our recent tests (Nov 15 to Nov 20) with flying colors. GENTIL has also gone through a second successful baking what has not, apparently, affect its performance. PACOVAL has also gone to through two bakings: one at LNLS and the overbaking at FERMILAB. I do not see any other thing to do with GENTIL and PACOVAL but to install them and bake them, Tests should be done after baking. LARANJEIRAS must have the vacuum re-established. Then the overhauled top arm must be checked at high speed (move it first slow). The bottom and right arm must be tested (the left arm was already tested and passed despite a few stickings). If arms do not pass test, they must be overhauled. MATINADA vacuum must be re-established. Upper arm (that has been overhauled) must be checked at high speed (move it first slowly). The remaining the aram have already been tested at high speed and passed. MACACAO is working fine. GUAJARA sticking problem must be addressed. If compensation the weight of the cartridge does not solve the problem, then the arm must be overhauled. This can be done in the tunnel. Pay attention to the fact that the castle must be filled with dry nitrogen for this operation, so the valves separating the castle from the rest of the TEVATRON must be closed. The arms that have not gone through a overhaul (three from LARANJEIRAS and three from MATINADA plus the arms from MACACAO and GUAJARA) must me observed. If they work fine, leave them alone. WARNING ------- The arm overhaul is a delicate operation and should be performed only by people with experience on that. Although one person alone can do it, it is strongly recommended a crew of at least two. It requires care not to damage sensible parts and safe measures when handling the grease and disposal of waste. A detailed text describing this operation will be made available. NEWTON This is my task report: 1- I checked 20 index interface boards. All boards were working well and I did not find any problems. 2- I removed the external power connection on all modified boards and now they are powered through the the signal flat cable as was originally intended. 3- I added three 130 ohms in series with C1, C2 and C3 on each board. This will increase the discharge time a little bit and will damp any oscillation caused by cable/wire inductance on the limit switch circuit. This showed to prevent the "latch up" problem with rack monitor input/output CI and consequent heating. 4- We will include more resistors on the multiplex board project to limit the rack monitor output current to a safe value in case of rack monitor failure. 5- Index interface fuses were checked for the proper value (500mA Quick Blow type). This fuse has a lower voltage drop and will guarantee an circuit operational voltage near 5 volts. 6- The control software version Lionel left seems to work well. The motor did not move by itself for a long test period. 7- The rack monitor was tested with an external resistor load draining 130mA for a long time. The voltage drop on 5V normal power was only 50mV below no load value. 8- Coaxial green cables from signal conditioner to rack monitor were made too short and they were replaced by a longer set. 9- Driver crate was improperly assembled. Two driver power grounded cable meshes were passing very close to filter lids, almost touching it. It is a very dangerous situation (short circuit). I reroute that meshes. The mesh terminal must go one of the lower driver support bolt not to the filter bolt. Paint must be removed from the driver attachment point to assure a good contact between the mesh terminal and driver back (and bolt). RF noise must return to the driver back in order to prevent noise irradiation. 10- Lab 6 castle setup cables were disentangled and ordered. 11- Lab 6 castle top pot and Laranjeiras top pot were regreased but not tested (waiting for vacuum). 12- I explained an gave the new detector box drawing (second option) to Phill (NIU). 13- The MAPMTīs silicone rubber support must be molded on the proper cartridge body and must not be removed. Otherwise it will loose the alignment. Imperfection on the aluminum wrapped MAPMT dummy will be copied on the silicone rubber and the real MAPMT will not fit well and will get loose. The aluminum guide tube must be used instead of the wood dowel. All gaps between MAPMTs and the aluminum plate must be properly filled with silicone selant before pouring the liquid silicone rubber.
MARIO ----------------- Document Overview ----------------- The FPD issues considered in this document are presented by order of relevance: 1- Flex cable to connect the flat cables from the Amplifier Shaper boards to the Analog Front End boards, 2- Multiplexer board for the Index Interface and safety devices 3- Amplifier Shaper boards 4- high voltage system for the MAPMT and PMT 5- cabling 6- documentation 7 - Communication, Phone and Video Conferencing 8 - Laboratories ----------------------------- FPD AFE Boards and Flex Cable ----------------------------- To couple to the FPD AFE boards the position detector MAPMT and LMB photodiode signals, that comes from Amplifier Shaper boards through flat cables, requires an flexible printed circuit interface that need to be made now. This development involves an experimental part with AFE boards that is difficult due to the small availability of AFE boards now. Some possible ways to solve this problem, they may be pursued simultaneously : One solution is to acquire the right to use and modify five 8-MCM AFE board from the older design, that is one spare and four to be used at Run II. We can start with only one now. The AFE modification consists in soldering 8 flexible flat cables on the AFE board to replace each Cinapsys connector there. On its other end this flexible cable ends in four connectors to be inserted in the header connectors of the flat cables that come from the Amplifier Shaper boards. Another modification of the AFE is to replace the 100 pF coupling capacitors to the MCM by a two-capacitor charge divider to fit the MAPMT signals into the SIFT chip dynamic range. These AFE boards will be dedicated only to the FPD. Another solution for us is to keep the AFE unchanged, making a FPD Flex Cable as a simpler copy of the VLPC 64 channel readout cable (V64), a special flexible printed circuit fabricated for Fermilab/D0 by a company in the Pittsburgh, Pennsylvania area, called Compunetics. I got the V64 drawings from Mike Matulik, that need to be modified in order to include the charge divider with capacitors. The charge divider by capacitors can be in this flexible printed circuit or in a printed circuit board that will receive this flexible cable and the flat cables from the Amplifier Shaper boards. On one side the Flex cable will have a connector to be plugged in the flex cable connector, the other end will receive a Cinapsys connector to plug into the AFE board. This solution depends on the availability of the Cinapsys, that is an expensive custom connector and was said by Fred and Marvin that DZERO have made not enough of them. There is not enough spares that can be used by FPD, that will need 64 of them, a small number to be produced at reasonable prices in a special order to Cinch. I contacted Compunetics, that did that Flex Cable for D0, one of the firms which were capable of making this circuit. The person I talked to at Compunetics is Brent Mayfield. His direct phone number is 412 858-6148. I sent to him the V64 circuit drawing files Mike Matulik gave me and described what we are attempting to do. I didnīt get any answer from them so I am looking for other companies but I would rather work with Compunetics. Also I am searching alternative connectors to replace Cinapsys. ------------------------------------------------- Index Interface Multiplex board and safety issues ------------------------------------------------- Another important development problem for the FPD is the design of the multiplex board for the Index Interface board. This board is intended not only to solve some problems related with the use of 1553 Rack Monitor to control the Roman Pots movement but also to monitor Amplifier Shaper boards, smoke detectors and power supplies inside the tunnel for safety reasons. I was there looking at Newton testing the Roman Pot movements using Rack Monitor and saw that they work well at Lab 6 but we still do not know what happened in the Tevatron so having to design the multiplex board to reduce the number of 1553 Rack Monitors we may include some the following additional features to it: 1- An optical coupling with the 1553 Rack Monitor Input and Output connectors. This will clear out any doubts about noise and electrical interference, as well as grounding problems, will not cost much. 2- Read back resources to check if the commands were read properly by the Index Interface - II, if it can send to 1553 Rack Monitor input the bits received by the II. 3- Amplifier Shaper board test pulse generation, issued by commands from the control room through the 1553 rack monitor, and power supply voltages monitoring, using the monitoring circuits available at those boards. 4 - Connection between the 1553 Rack Monitor, the Power Boxes and the smoke detector to automatically disable the Power Boxes and inform Control Room when smoke is sensed, as required by D0 safety rules. The smoke detector alarm condition should also be reset from the control room. The use of the Interface Monitor is one alternative solution, but then we will need 5 of those. I am discussing these solutions with Rick Hance, including a possible modification of the Power box to receive directly the smoke detector alarm signal. 5- Low voltage power supplies monitoring. The FPD low voltage power supplies inside the Tevatron need to be bought now. We can choose models that can be monitored from the control room for current and voltage levels. ----------------------- Amplifier Shaper boards ----------------------- The Amplifier Shaper boards - AS - need to be re-tested against bad contacts for amplifiers and headers sub-circuits. Two header flavors can be used for the FPD: FDC and VTX, both non inverting amplifiers. All available AS boards, not included those left inside Tevatron, are in Lab 6 in VME crates. All available headers are inside a card box with the AS VME crates on the side of the wood box to test the fiber detectors. The documentation is in a folder left over the right side of Andrew Brandt desk at his office. I did bring with me the amplifier documentation with a brown folder, but the schematics are available at my homepage at: http://d0br1.lafex.cbpf.br/~mario/ampshaper/description.html. or you can go to http://d0br1.lafex.cbpf.br/~mario. and choose first FPD and second amplifiers. It may be necessary to solder the headers on the boards, but the amount of work is huge: 2016 headers of 16 pins, not including spares. A intermediate solution will be to clean and solder dip the headers to get a new clean surface for their pins and better contact to the board. The minimum effort solution will be to test the boards shaking them a little to see if they have bad contacts, and check those who failed to localize the contact problem, that can be solved by replacing the header or by cleaning it and the board, or eventually re- soldering the defective header pins to make their contact with the board better. It is not possible to automatically solder the boards. I think they are not reliable the way they are. A manual test setup, using LMB and oscilloscope, and can be automated by software to be develloped. The setup was made by Petra and I, in such a way that the detectors in the Roman Pots or in the big wood box can be used with conjunction of the LMB to generate the test pulses to the AS, that can also be provided directly by the pulse generator, which output is connected through a 22 ohm resistor to 2 16-channel flat cable with a 16x2 header connector that goes to the Amplifier Shaper VME crate backplane. Victor from Moscow State University offered to be responsible to do the software for test automation using FERA modules. All NIM and CAMAC modules collected during the Engineering Run were put together over the table by the end of the room. Other NIM and CAMAC modules, also power supplies, are in our Eng. Run Control Run and should be removed to Lab 6 or given back to PREP. --------------------------- High Voltage Power Supplies --------------------------- According to R.Hance and J.Felgulson, we have a place for FPD HV Supply at MCH 2nd floor rack M222. We will need 23 pods, 3 mother boards, 8 fanout units to four 8-channel HV cable, 64 HV RG58 BNC cables, as can be seen in my drawing for the FPD HV Power Supply at http://d0br1.lafex.cbpf.br/~mario/FPDHV.ppt. All these parts can be supplied by D0, according to them. ------ Cables ------ Flat cables need to be tested before and after installation into Tevatron, and repaired there if fail. But it need to be done when the crates are already installed so we cables can be fastened and not moved anymore. Maybe it will be necessary to make a special cable test fixture to be used in the tunnel if the muon cable test fixture made by H.Haggerty result not convenient for our use. ----------------------------------------- FPD Documentation and log books and files ----------------------------------------- We need a mechanical drawing detailing cabling and crates for the FPD rack. During our discussions about the Engineering Run several times was mentioned that we have a poor documentation of schedules, duties, procedures, work done, mistakes made, etc... and also that this documentation can help us in learning how to make our FPD to work. We need to use a single log book for the FPD, and I suggest we use that one left at Lab 6. And also I believe that the software we are using to control the Roman Pots need to have log files registering all the commands and readings, and that these files need to be protected against changing or erasing, being under control of one of us with more experience. There is a log book at Lab 6. It should be used as a general log book for any test or installation or meeting made from now up to the end. I have my personal log book and I wrote from it my notes on this general log book. I want to write also in the computer log book that Sergio Novaes made based on the Fermilab Control Room logbook. I suggest we all start using this double log book approach and also we expand the FPD List Sergio made. I think Sergio Novaes gives a nice contribution for our documentation creating a computer FPD News, FPD List and FPD log book, we should use it all, and start updating the FPD Web page based on that. Files like data files from the Eng. Run Petra made and Andrew lists for Commissioning should be available there. I have my FPD Web page at: http://d0br1.lafex.cbpf.br/~mario/fpgg.htm. It includes an updated list of FPD people that I would like to receive feedback. ------------------------------------------- Communication, Phone and Video Conferencing ------------------------------------------- We really need to have from now up to the end of Commissioning a regular communication between all of us. We need to have at least a phone conference while an ISDN video conference facility is not available in Rio. UERJ got the line and the equipment that now we are waiting to be installed. I volunteer to work with Andre Snajder to speed up that. ------------ Laboratories ------------ We need to get our material together in Lab 6 and Lab 3, bewaring about PREP loans that we need to return. Also we have power supplies for Amplifier Shaper and maybe some crates that will not be necessary for FPD and can be given back to D0, Pat Liston may like to get those back. Before I left I put some order in Lab 6 chaos but a lot need to be done. This also includes Lab 3. LIONEL INTERFACE BOARDS TESTS ---------------------- * WITHOUT SOFTWARE ------------------- 1. connect: - 16 switches box to the Interface Board (IIB). - Input cable with Rack Monitor (RM). - 2 cables in front of IIB 2. check if the switches In and Home Position are OK. Leds must turn on in front of IIB. 3. move the motor witch buttons in front of IIB (In and Out, slow and fast speed). 4. Put 2 small pins on the IIB at positions 3 U8A and 6 U8B of circuit 74HCT32. Connect pin 3 to an Input TTL of module 688AL LECROY, and pin 6 too. Then connect the Outputs (NIM Ouput) on Input of Channel 0 and Channel 1 of the module DUAL CHANNEL BCD SCALER.So we can count the number of half turns when the motor goes in In position (pin 3, Channel 0) and Out position (pin 6, Channel 1). 5. with the 16 switches box, move the motor in Home Position. 6. put the motor to the position 1 in slow speed. 7. reset the 2 channels of the SCALER. 8. Move the pot to the position 32 in slow speed. 9. check the number on channel 0. We must have 31 (+ or - 1). If it's not correct try again (go to 5). 10. Move the pot to the position 1 in slow speed 11. check the number on channel 1. We must have 31 (+ or - 1). 12. go in home position and after to the position 1 in slow speed. 13. reset all channels (0 and 1). 14. Move the pot to the position 512 in fast speed. 15. check on channel 0 the number. We must have 511. 16. Move the pot to the position 1 in fast speed. 17. check on channel 1. We must have 511. 18. check several times and write all numbers (where we want to go, where the pot have gone). * WITH SOFTWARE (Move_P1_In.py or Move_P1_Out.py) ------------------------------------------------- 1. connect all cables between iib and RM. For software Move_P1_In.py, use connector P08 and black cable labeled IN. For software Move_P1_Out.py, connector P02 and black cable labeled OUT. 2. connect to d0ola server: ssh d0ola -l peyricli password: fpd2000 3. start software: python Move_P1_In.py & (or Move_P1_Out.py) 4. click on RUN button. Then motor goes in Home Position. After the software chose a new position (random). Motor goes to the position, stop and software choses an other position ....... 5. stop and exit. 6. edit the file: nedit MOTOR/P1_Out.dat (or P1_In.dat) 7. look if you see one of this messages: - ERROR : Bad direction, Motor in In position - ERROR : Bad direction, Motor in Home Position - Error : Motor restarts Messages 'Bad direction' are written when software send a new position and motor goes, first, in In or Home position and after to the right position. Message 'Motor restarts' is written when motor stops and restart without a new position of software. On a label write: ----------------- Interface board ID : IIB-01 for example Date Your name If all tests are OK or BAD comments MIKE MARTENS Cables Runs =========== I met with Al Ito, and later Rick Hance about cable routes. With both of them I went into the tunnel and looked around. Now that I have a clearer understanding I believe we may want to re-think our cable strategy. Here are some comments: 1) The cables coming from the Tevatron tunnel into the collision hall will have to go up about 6-8 feet from the tunnel pit floor in order to make it over the clamshell shield. Otherwise it appears we have plenty of clearance to get our cables into the collision hall and drop behind the trusses along the north and south walls. 2) The best path for the ribbon cables seems to be along the north or south walls towards the west wall. Then run along the west wall to the platform crate PW08 which is near the center of the west wall and about 3 feet from the west wall. We will need some help from D0 (some cable trays maybe?) to get a clear path along the west wall so we can avoid doorways, etc. 3) The high voltage and PMT cable runs are problematic. We need to get from the collision hall to the movable counting house (MCH.) This is not so simple if we try to do this with a single cable run. There are several options: a) Make the cable runs after the detector and MCH have been rolled in. This is the simplest run. But creates problems if D0 needs to roll out the detector since we would have to uncable everything. (I doubt D0 would agree to let us do this since I estimate it would take several days to uncable this.) It also means we have to do things at the last minute. b) Rick Hance suggested that we run the HV and PMT cables to a patch panel at PW08, then run a second set of cables from PW08 up into the counting house. This makes it easy for us to disconnect from the D0 detector, but we then we need two sets of cables (means more connectors) for every cable run. We would also need patch panels (i.e. more time and money.) Also, the run from the PW08 to the counting house is complicated and twisty, with lots of tight spaces. c) I am not sure if this option would work. But we could use the simple run I described in option a) but have a patch panel somewhere in the collision hall. In any case, I think my estimate of 1 week with 3-4 people for laying cable was probably optimistic. Also I think it will take some work to determine cable lengths. Rick suggested making a run with a rope to measure the cable length needed. I think he is correct that this is the only way to get an accurate measure of the length since the paths are so twisty. Update on Castle Status ======================= Before they left, Newton and Helio de-burred and regreased the top pots of MATINADA and LARANJEIRAS. After they left Sergio and I de-burred and regreased the right arm of LARANJEIRAS and today I finished deburring the left arm of LARANJEIRAS. The nut gear on both the left and right arms had a significant amount of burrs on the end threads. After re-assembly both the left and right arms moved in and out 3 times at fast speed (after one time at slow speed) without any problems. This test was without vacuum and without a detector. Next week, we will pump down LARANJEIRAS and perform motion tests again while under vacuum and with a detector in place. I will also work de-burring on the other arms of MATINADA. GENTIL and PACOVAL are completely ready for installation. The motion of the arms has been thoroughly tested. All motors and encoders are disconnected. All pots are at the IN position. The installation date for these to castles has been delayed once again till at least mid next week. There will be a meeting next Tuesday with Jon Kotcher, Mike McGee, Doug Allen, Dave Augustine, and myself to discuss the schedule for re-installing the low beta quads. (Apparently D0 wants to wait a little longer??) This could affect our schedule so I will be at the meeting. I think a week or so delay cannot hurt us, but more than that could reduce the time we have to install motors, and detectors. ANDREW + SERGIO From the discussion with Mike Fortner. - About the "run_config_mgr" file: We are not supposed to appear there. The FPD crate should be included (listed) in the "cfg.dat" file which is different for each run. This allows for the fact that as Run 2 starts only part of the electronics will be there. If more AFE boards are added then a new cfg.dat would be needed. We hope to start with one AFE board. - Is FPD included with fiber tracker modules (FT_FE)?: Yes. This statement refers to the AFE boards only. We already have 2 designated crates. One of them [M 213-1] contains the VME cards. The other one [M 115-1] contains the timing and vertex boards. For a list containing the Data Crates in the MCH see Fortner's page: http://www.physics.niu.edu/~fortner/d0/algo/unpack/crates.pdf About the Level 1 trigger, is there a FPD_L1 or we should be together with fiber tracker level 1 trigger (FT_L1)? That is not so clear to me. He drew the following scheme: AFE Data Timing & Vertex TM Data (FPD) (FPD & Lum) (FPD & Lum) || || || \/ \/ \/ UnpDataChunck UnpDataChunck UnpDataChunck FT_FE LUM_FE FT_L1 The right and left options are quite clear and should be pursued. For the Timing & Vertex, he said that we could either go in an independent way or try to do it together with the FT. In the first case we must write our own software. I believe that our MRC that reads out the FPD + LM trigger manager will be in the same crate as the CFT trigger managers we are checking on this - Should we write an unpacker for the FPD?: We can use the fiber tracker unpacker for our AFE boards, although we still have to get our MC signals into the right place, but the LM boards are unique and we will have to adapt fiber tracker code to make a new LM chunk. Rich's people will not get to this for a long time yet it seems. He suggested for the next steps: 1) Simulate the AFE boards, filling the standard objects of CVS. Remember that our AFE addresses are very similar to the Fiber Tracker ones; 2) Integrate our code with the Fiber tracker code. SERGIO The position of the switches in front of the driver should be at: 1 - OFF 2 - OFF 3 - ON _______________ 4 - OFF 4000 steps/rev 5 - OFF _______________ 6 - ON 7 - OFF 4.3 Amps 8 - ON _______________
LIONEL * I tested 15 Interfaces Boards : - all boards forget to count some turns when we go to In Position. - the board (ref #: IIB-07) don't move the motor. - the board (ref #: IIB-01) goes In or Home position and after to the correct position. - the board (ref #: IIB-15) stops before or after the correct position (only half turn) and after restarts and goes to the right position. * I have cut 75 ribbon cables (6 m). * I have enrolled 10 ribbon cables (45 m) but not tested. MIKE MARTENS Update on Castle status ======================= The rework of the LARANJEIRAS castle has been completed and the motion of all the arms has been tested. The pot is now ready for installation. All of the arms are in the IN position and all motors and encoders have been removed. All of the tools, motors, drivers, etc. have been moved back to lab six. All of the arms were disassembled, the burrs on the nut gears were removed, the grease on the piston was removed and replaced with the Molycoat grease, and all arms were reassembled. (The upper arm was done by Newton and Helio, the right arm by Sergio and Mike, and the left and lower arms by Mike.) There was some trouble with the lower arm. Two of the six allen bolts connecting the limit switch arm to the dust cover were stripped. The two stripped allen bolts were drilled out in order to separate the limit switch arm from the dust cover. The limit switch arm was re-assembled using only four of the six bolts but this is plenty good enough to keep the dust cover on tightly. After the rework the motion of the arms was tested under vacuum at high speeds (10 rps) and there was no sticking. The top and right arms (the ones that were sticking) were moved in and out 5 times at high speed without sticking. The left and lower arms were moved in and out 3 times at high speed without sticking. The top, left, and right arms were tested under vacuum and with a pseudo detector installed and a 5 pound weight attached at the end of the detector. The lower arm was tested under vacuum but without a detector. Work on MATINADA will resume later this week or early next week. The top arm has already been reworked by Newton, Helio, and Sergio. Cable routes in D0 collision hall ================================= I have included a power point slide of my proposed cable routing for the HV, PMT, and ribbon cables. http://www-d0.fnal.gov/fpd/FPD_News/cable_routing.jpg http://www-d0.fnal.gov/fpd/FPD_News/hv_cables.jpg http://www-d0.fnal.gov/fpd/FPD_News/l1_trigger.jpg I need to check this path with D0 people, but it seems reasonable to me. This plan requires us to find enough space in the PW08, (or PW02 and PW03) crate for two "Fanout to HV 8 ch. cable" modules and a patch panel for 8 PMT cables. This plan is consistent with Mario's "FPD High Voltage Supply and Cables" diagram (which I included here as well.) The only difference is that the HV fanouts are not in the Tevatron tunnel. Other than that the diagram is the same but the cable lengths will have to be adjusted. Here is my reasoning: D0 must be able to roll the detector in or out without uncabling our detectors. Therefore we must be able to connect/disconnect our cables from the platform and movable counting house (MCH) with relative ease. The ribbon cables for the MAPMT are straight forward. The cable will come in from the tunnel, move along the north (or south wall) to the west wall. Along the west wall they will go towards the center of the collision hall where we have easy access to the AFE boards in crate PW08 on the west platform. Therefore we can connect/disconnect these cables fairly easily from the detector. There appears to be plenty of space behind the trusses and along the west wall for these runs. The HV and PMT cables are a bit more complicated since we need to make a run from the MCH to the tunnel. The MCH moves back and forth when the detector is rolled in and out so we cannot make a single cable run from the MCH to the tunnel. We must break the cable run up into two parts. First the HV cables: We follow Mario's diagram except that the second set of HV fanouts are not in the Tevatron tunnel. The fanouts for the pbar side is located in the collision hall near the northeast corner. The fanouts for the proton side are located in crate PW08. This way we can run the Reynolds cables from the MCH to the articulated cable carrier for the pbar side, and to rack PW08 for the proton side. Our cables from the tunnel (RG58 HV) can be run to the same place and once the detector is rolled in we can simply plug in the RG58 BNC cables from the tunnel into the fanouts. Second the PMT cables: We follow the same plan as for the HV. Except, that we need a set of connections in the collision hall or at PW08. (I call these patch panels in my diagram.) Rick Hance gave me a tour of the MCH and platform this plan seems reasonable to him. Hopefully I can get a key to the collision hall tomorrow and look around once more. I am also going to meet with John Foglesong to discuss this in more detail. Once we have a reasonably detailed plan John Kotcher would like us to present the plan at one of the Monday scheduling meetings. More later, but in the meantime let me know if you see any problems. Update on the BD schedule. ========================= The low beta quads will be ready to be inserted into D0 by the end of the day Friday. After this there will be about 3 days to get the cryo bypass installed, and then about a week to get the separators and our pots installed on the C4 side. Because of this, the fact that it takes a week to bakeout and the upcoming Christmas and new years holidays the bakeout of our pots will not start till January 2nd. We should have access to the C4 side pots by January 9th. The baking equipment then gets moved to D1 and another week long bake. This means we will have access to the D1 side pots about January 18th. In the meantime we can still be laying cable, installing electronics, etc. I have heard nothing official about a delay of the March 1 startup date. I did see the director at lunch today and he mentioned that there might be a week or two delay in the beam startup.
PETRA
LMB system for RunII :
I summarized the general information about the LMB:
http://www-d0.fnal.gov/~krivkova/fpd/lmb.html
More about cable connections:
PIN out (suggestion):
---------------------
- 5 black cables (Dip: 40m; A2: 10m; A1: 1m; P1: 70m; P2: 80m; total: 200m)
(we should have the short black cables after cutting the black c. during
the ER)
- these black c. will go from the individual LMBs (at dip,A2,A1,P1,P2) to
the AMP at A1
- we will need to make the interface to connect them as the AMP input
(use one of the 19channel flat cables which is terminated by 5 BNC
connectors ? )
- the signal will go to the spare AFEboard via the ribbon cables
SLP in:
-------
- source: we are sharing the SLP board with ICD (we will have 5 channels).
This board will be positioned in the VME crate on the 2nd floor of the
movable counting house.
- 5 short green cables going from the crate to the platform
- 5 long green cables going from the platform to the individual LMBs
- NOTE: maybe we will have to use the circuits to restore the SLP pulse
before it goes to the LMB
PIN power:
----------
- 5 short grey cables (dip: 3m; A2,P2: 12m; A1,P1: 6m; total: 40-50m)
- special 5-pin connectors
MARIO
--------------------------------------
Adapting FPD flat cables to AFE boards
--------------------------------------
This is a proposal to connect our flat cables from the FPD Amplifier
Shaper boards to the FPD AFE boards, in the following way :
1 - using AFE boards without modification
2 - making the FPD Flex Cable based on the VLPC V64 Flex Cable.
3 - making a mechanical support on PW8 Rack for the flat cables by using
holders for the cables and Amplifier Shaper - A&S - back planes for the
connectors to the flat cables and the FPD Flex Cable. The A&S back planes
need to be modified as explained below.
4 - making a capacitor charge divider, to match the input of the AFE SIFT
chips with our MAPMT signals amplified by Amplifier Shaper boards, to be
included in the Flex cables or in a board that will give the mechanical
support to the flat cables.
The capacitor divider need to be defined by taking a signal from a MAPMT
excited with a LMB LED, amplifying with Amplifier Shaper board that will
send the output signal through 2 flat cables serially connected to a test
board where we can solder the SMD capacitor divider and from it to the AFE
from which we will take data. There are two possible setups for doing
that, one at Lab 3 and the other at 3rd floor of DAB. The main idea is NOT
TO MODIFY THE AFE BOARD FOR FPD USE, if possible.
We have 126 16 channel 75 ohm coaxial flat cables that end at a non
standard 19 x 2 pin header female connector. We will be using two cables
of 50 m serially connected by a 19 x 2 header male-male extension. The
cable will come under PW8 and will be hold by pairs of aluminum bars
sandwiching rows of cables. Sixteen pairs of holders will be necessary, to
be installed under the A&S back planes, under the flat cable connectors.
The flat cables connectors will fit into Amplifier Shaper back plane
connectors, on the other side of the board other connectors will fit into
the Flex Cable connectors that will have its Cin::Apse connector pressed
against their respective pads on AFE board.
The AFE board will be suported in a crate that will include the press
tools for the Cin::Apse connectors. Each of our 4 AFE has 8 Flex Cable,
each Flex Cable has 1 Cin::Apse connector and 4 16x2 or 19x2 header
connector. Each modified A&S back plane has 20 19x2 male header connector
in each side of the board, one side for the Flex Cable and the other for
the flat cable.
We need to have this ready in February of 2001 so we need to put orders to
make now in December.
------------------------------
Flex Cable as copy of VLPC V64
------------------------------
To make a FPD Flex cable we can start from the VLPC 64 channel readout
cable (V64), that is a flexible printed circuit fabricated for Fermilab/D0
by a company in the Pittsburgh, Pennsylvania area called Compunetics.
The "production drawings" or "gerber files" were supplied by Mike
Matulik, that also wrote the text that I slightly modified for the
following explanation about the V64.
To design a Flex Cable to the FPD we need to modify the V64 Accel files
with the V64 schematic, showing the connections between pads at the AFE
end of the circuit that you want to build (which will be the same as the
V64 circuit) and the pads that match with the connector to be used to
insert in the A&S backplane. Creating this schematic allows to generate a
net list (listing of the desired electrical interconnects on a circuit. We
can use Accel at Fermilab, or in Rio. Here also we can convert the Accel
files to be read by the ORCAD Layout program that we have here.
The V64 circuit was designed to connect the output of the Visible Light
Photon Counters (VLPCs) to the Analog Front End (AFE) boards for the D0
Fiber Tracker Upgrade. There are 64 channels, plus some temperature
monitoring/control signals and VLPC bias connections which traverse the
length of the cable. The VLPCs must be kept cold (~8K) to work, the AFE
is held at room temperature. The fact that the cable is made from copper
means that it will act to transfer heat from the AFE end to the VLPC end.
Given the large number of cables and the cost of liquid helium, the copper
trace cross section was made as small it could be and still pass the
electrical signals to the AFE, minimizing the trace width and space
between adjacent traces. To make our Flex Cable less expensive, we can
reduce the size of the circuit that drives the cost up, making it shorter
( CTT length is ~16 inches) and also using wider and thicker traces and
spaces between traces. The traces were made with very thin (5um) copper to
minimize the heat transfer, we do not need that. I am talking to Brent
Mayfield of Compunetics about this (phone number 412 858-6148). I
contacted him mentioning Mike Matulik contact, they had already talked
about this and I am going to supply Brent with our specifications. Let us
not forget that Compunetics was one of only a handful of firms which were
capable of making this circuit.
-----------------------------------------
Cin::Apse connectors availability and buy
-----------------------------------------
The Flex cable will have in one side Cin::Apse connectors made by Cinch.
George Ginther wrote that it may be possible to have 40 connectors from D0
stock. Allan Bross ask us to start buying that but didnīt say no to that.
So Andrew try now to get what we can from them. We need 3 warm end
Cin::Apse connectors to start making a prototype, we need to buy now from
Cinch all our 40 connectors, present the bill to George and Allan to ask
for some connectors now to be paid in near future.
------------------------------------------------------------------------
Using Amplifier Shaper backplanes to interface Flex Cable to flat cables
------------------------------------------------------------------------
To specify this connector, we need to decide how we will work with the
flat cables. The proposal here is to use the Amplifier Shaper backplane
that has 20 connectors in one side, to receive the flat cables header
connectors, and another 20 in the other side, to receive the Amplifier
Shaper boards input connectors. There are another row with the same number
of connectors both sides that receive the output connectors of the A&S
boards. We can have this row removed to save space and allow air flow for
cooling. AFE 1 and 4 each will have 8 Flex cables that will go to 2
modified backplanes to receive each 32 flat cables, AFE 2 and 3 each has
also 8 Flex Cables going to 2 modified backplanes to get each 31 flat
cables.
The backplanes will stay under their respective AFE boards, below them we
will have transversally to the boards aluminum bars that will sandwich the
flat cables to hold them. These bars can support the flat cable connectors
that will go to the backplanes. On the other side of the backplanes come
the Flex cables, ending at 4 header connectors with 16 or 19 x 2 pins yet
to be specified. The Flex cables can have length of 5 in, we need to check
in the Lab 3 AFE setup what will be confortably shortest.
------------
Ordering now
------------
We need to decide soon so I can answer to Brent last email, at the end of
this letter. My answer to Brent Mayfield would be : Yes, we want you to
design for us the flex cable as a VLPC V64 modified in the following way :
1 - shorte length : 5 inches long
2 - with connectors : 1 Cin::Apse in one side, 4 16 x 2 female header in
other side.
3 - traces can be thicker and wider to reduce costs, they will be 64 70
ohm transmission lines from the header connector pads to the pads of a
pair of capacitors making a charge divider before the Cin::Apse connector
pads.
4 - all V64 additional traces for bias, monitoring and control can be
eliminated
5 - we will need 40 cables by February, 3 prototypes by January.
---------------------------------------------------
Work to be done to allow us to order the Flex cable
---------------------------------------------------
We need to know if 5 in long Flex Cable can work and also what connector
will fit into the backplane connector to the flat cable input. We need to
know if we can have the Cin::Apse connector.
From bmayfield@compunetics.com Wed Dec 6 16:20 EDT 2000
From: "Brent Mayfield"
To: "Mario Vaz"
Subject: Re: Flex circuits
Date: Wed, 6 Dec 2000 13:19:52 -0500
Mario,
I wanted to know if you need us to design your flex cable for you. If so,
could you get me the part #'s for all the connectors involved. Also, I'll
need to get some idea how big this circuit needs to be in order to quote.
I can estimate the line widths based on your impedance requirements.
Also, what are you looking for as far as a ground layer. I'm going to
need to get more specifics before I can quote. Could someone there write
up some specifications for this board? In order to deliver by February 1,
I would need to get started in manufacturing by early January.
Thanks,
Brent
Brent Mayfield
Flexible Circuit Products Manager
Compunetics, Inc.
Advanced Interconnect Products Division
bmayfield@compunetics.com
www.compunetics.com
Phone: (412) 858-6148
Fax: (412) 373-4184
Date: Thu, 7 Dec 2000 08:57:34 -0600
From: George Ginther 630-840-2263
To: Andrew Brandt
cc: Marvin Johnson ,
Frederick Borcherding , mario@lafex.cbpf.br,
Michael Matulik , womersley@fnal.gov,
"P. Tuts" , Hendrik Weerts ,
Alberto Santoro , Alan Bross ,
wayne@undhep.hep.nd.edu, Daniel Olis
Subject: Re: Connecting to AFE board
Andrew:
(supressed text)
So, now for the connector accounting update: The current plan is that a
minimal cassette production will be 99 cassettes plus 5 spares. We plan
to produce as many additional spare cassettes as parts will allow, and we
hope and expect that the limiting part should be the VLPCs themselves.
Current best guess is that we might get six additional spares, for a total
of 110 cassettes. There are also three prototype cassettes, and we have
also been asked to provide components for an electronics test stand
(effectively an additional cassette), and a display cassette has been
fabricated for the SC2000 conference. Thus, after cassette fabrication is
complete:
115 cassettes*16 connectors 1840 connectors
projected rejects 45 connectors
total spares 2000-1840-45 115
Obviously, I would have prefered that more than 2000 pieces had originally
been ordered, but the pieces are not inexpensive, and 2000 parts
represents about 25% spares for a target of 100 cassettes. I strongly
suspect that the target number of cassettes has climbed significantly
since the connectors were first quoted and ordered, but by careful
shepherding of parts, we should have sufficient parts to satisfy the DO
cassette needs as long as the people handling bayonets are not careless.
However, a request for 60 connectors is significant compared to the
projected 115 shelf spares. Since the CINCH connector is likely to be the
most expedient solution for the FPD system, the request should be given
serious consideration, and I hope that we can indeed eventually provide 40
connectors for that system (if necessary), but we also need to understand
the implications for cassette production and the other (as yet hidden)
demands on cassette components.
Since Compunetics is still producing the cassette flex circuits, I am
also interested in learning about any orders that D0 intends to place with
Compunetics so that priorities can be appropriately evaluated.
Date: Thu, 07 Dec 2000 12:53:50 -0600
From: Alan Bross
Subject: RE: Connecting to AFE board
In-reply-to:
To: George Ginther 630-840-2263 ,
Andrew Brandt
Cc: Marvin Johnson ,
Frederick Borcherding , mario@lafex.cbpf.br,
Michael Matulik , womersley@fnal.gov,
"P. Tuts" , Hendrik Weerts ,
Alberto Santoro , wayne@undhep.hep.nd.edu,
Daniel Olis
IF the FPD group wants to use cinapse connectors they should initiate
procurement of such immediately. We DO NOT have sufficient spares in the
CFT/PS inventory.
AB
ANDREW
Minutes from 12/13 meeting at Fermi,
1) Discussed cable plan. Mike is proceeding with plan, will present to
Kotcher soon. We decided his idea with 1 HV fan out at platform and one in
collision hall and longer HV cables is probably better due to availability
(or lack) of Reynolds pass through board. He will investigate where in
collision hall this could go, perhaps on detector (PW is not close to pbar
side, so this doesnt work). Eduardo and Hans will meet with Lionel 9:45 on
Friday to see what to do to test flat cables. Note: All cables have still
not been moved to LAB3. This is causing problems both with testing and
preparing cables for bob jones. ***Christophe is this arranged yet?
Eduardo will work 1/2 time on laying or testing cables (1/2 on L3). Hans
will work on cable testing after he checks resolution of black cables so
purchase can go forward. He needs fast scope which will be in use until
Sunday. He also needs black cables (christophe was going on access to get
them). On Hans next trip in Jan he will work on assembling cartridges in
Lab3.
Christophe checked on TV cameras with Larry Jackson. We need to integrate
with D0 to avoid extra expense. ***Christphe did you send outline of plan to
Bill Freeman?
2) We discussed coupler situation. We are worried about failures. Could be
screwed on too tight, could be metal fatigue. Suggestion to buy all new
couplers for Run 2 (note this was amended in today s meeting by Helio who
will determine stronger coupler which we will order right away)
3) Victor is in charge of amp testing. Estimates one week for completing
code upgrade. John Streets has moved to Philadelphia, but responds to email.
Petra and Victor will meet at 9 friday at lab 6 to discuss tests.
4) Lionel will prepare last driver crate. Understands Newtons safety
concerns. Safety was stressed, and Mike M. will verify electronics before
it goes in tunnel (Mario could too if he's here in time).
5) ER summary still not done ***Andrew will attempt to do more this weekend.
6) Discussed including pot pos and magnet data in event stream. Still not
sure how to do this. Possibly Saclay engineer could come to Fermi to help
with this.
7) We need to consider resurrecting small control room in case we dont have
AFE boards or AFE adapter, we could still read out detectors using FERA.
THis is not ideal, since we would not be in D0 event stream, but may be
necessary for early comissioning.
8) Anybody know how we will get trigger scintillator rates? We have all
neglected this point I think. Do we need to have scalars in the FPD_LM
crate? ***Mario?
FPD manpower through Jan:
Hans through Dec. 21 and Jan 9-19 0.5 time
Molina from Jan 3 1.0 time
Carlos Jan 3-24 1.0 time
Lionel through Dec. 22 Jan 3 on 0.8 time
Christophe Jan 3 on 0.5 time
Sergio Jan 2 on 0.5 time
Eduardo will be around all the time through end of Jan 0.5 time
Victor will be available some, I will check.
Mike Strang can come in emergency situation
Naeem might be available in emergency
Mario maybe from mid-Jan.
SERGIO + EDUARDO
We (Hans, Lionel, Eduardo and I) spent the whole day testing the setup at
Lab6. Here is a synthesis of what we found.
We measured in 4 different ways the pot movement:
1) We counted the encoder signal to the IIB (ENCODER): we put an
oscilloscope probe at the board input (JP3) coming from the encoder. We
count visually the number of pulses. We always had at least 2 people counting
at the same time. We reduced a little bit the velocity of the motor to make
this measurements very precise;
2) We counted the number of turns of the motor (MOTOR): With a black strip
at the head of the motor it was possible to count with great precision the
number of turns;
3) We measured the result of the counting at the IIB (IIB_COUNT): Using a
multimeter we measured the voltage (0 or 5 V) at the pins # 3/2/6/7 of the
chips U13/U14/U15/U16. This measurement gives the binary result for the IIB
counting of the number of turns;
4) We measured the input to the IIB coming from the switchboard (IIB_INPUT):
Using the multimeter we measured the voltage (0 or 5 V) at the pins #
10/12/13/15 of the 4 chips.
We have also measured the voltage of the pin # 5/6/7 of the U16 that shows
if the board sent a stop signal to the motor (5 V at # 6) and if it have
stopped before or after the desired position. Every time we made this
measurement we got the pin # 6 with 5 V and pins # 5 and 7 with 0 V.
We made the tests using 2 different arms of the castle (i.e. two different
motors, drivers, encoders) and we also measured the behavior of two
different boards. We did not use the software to move the pots, only the
switchboard.
Some general comments about the results:
- The measurement of ENCODER always agreed with the MOTOR. Therefore we can
conclude that the encoder was counting correctly the actual number of turns
of the motor and was sending the correct number to the board.
- The measurement of the IIB_INPUT always agreed with what was set at the
switchboard. That is, the board was able to read correctly the desired
number of turns.
- The measurement of the IIB_COUNT always agreed with the IIB_INPUT. That
means that
SWITCHBOARD = IIB_INPUT = IIB_COUNT
These measurements were made after the motor had stopped by itself
(IIB_INPUT = IIB_COUNT).
*****************************************************************************
- However, the counts ENCODER = MOTOR is *NOT* always equal to the IIB_COUNT!
The relevant discrepancy only occurs when the motor is going inward.
*****************************************************************************
After several preliminary test measurements, we took the set of data below.
All the data is given in numbers of half-turns of the motor. In the data
below, we first went fast to 1024 and started to go in and out several
times. At the end, we sent the motor at high speed to [1] (1/2 turn), and
after that, to HOME [0] position.
For the board IIB-02 we got:
[SWITCHBOARD = IIB_INPUT = IIB_COUNT] [ENCODER = MOTOR]
1024
+64 +59
+64 +68
+32 +26 (*)
+32 +34
-32 -31
-64 -64
-64 -64
-32 -32
+32 +33
+64 +72
position [1] -> HOME -94
For the board IIB-06 we got:
[SWITCHBOARD = IIB_INPUT = IIB_COUNT] [ENCODER = MOTOR]
1024
+64 +63
+64 +64
+32 +48
+32 +32
-32 -31
-64 -64
-64 -64
-32 -32
+32 +31
+64 +66
position [1] -> HOME -138
The difference between the position [1] and HOME can give us an estimate of
the error of the counting when going to [1024] and making the back and forth
movement. We would expect that the position [1] would be very close (taking
into account the error of the home switch) to the HOME [0]. However, we got
94 and 138!
Two final remarks about observed erratic behavior:
1) It happened once that we set the switchboard to send the motor to HOME
position, and the motor moved in the opposite direction, towards IN
position. It was then stopped by switching off the "strobe" switch. It moved
properly to HOME position after switching it on again.
2) In (*), after setting the new desired position in the switchboard, the
motor started moving *WITHOUT* the "strobe" switch being reset. The number
of counts was then obtained by summing the number of turns as measured by
IIB_COUNT plus the number of turns obtained by visual inspection (ENCODER =
MOTOR). This was the ONLY time that the motor started moving without the
"strobe" switch being reset.
We did not find a reasonable explanation for this erratic behavior but we do
believe that it must be properly addressed in the future.
MIKE MARTENS
Castles
-------
I have worked through the survey data for GENTIL and PACOVAL. I need to
finish preparing the survey data for LARANJERIES and MATINADA (estimate 1
day.)
The C4 castles (GENTIL and PACOVAL) will be going in this week, and the
survey will be scheduled for late this week (or after Christmas.)
We need to get the D1 castles ready soon (by the end of this week.)
MATINADA still needs the left, right, and lower arms reworked and tested.
Bakeouts will not start until after the New Years.
I have taken apart the lower arm of Matinada, removed the burrs, and
regreased the piston. It is now partially assembled. I hope to finish up
this arm and the other two on Matinada during the evenings this week. The
D1 pots were scheduled to be installed and surveyed on 1/4 and the C4 pots
installed and surveyed on 1/8. However this has been delayed due to
scheduling conflicts with the alignment group and the unavailability of a
fork lift to move our pots. I am guessing that the scehdule will slip by 3
or 4 days.
Cables
-------
Several questions we have regarding the high voltage and cable pulls from
the movable counting house to the west platform.
1) After talking with John Foglesong I am not sure if I understand the
situation with the HV fanout boxes for the FPD. I believe that there will
be a box in MCH-222 which will have 4 spigots for our HV cables. (i.e. 32
HV cables going into 4 Reynolds connectors.) We need two more boxes, each
with 2 spigots, to fanout our Reynolds cables into HV cables. After
talking with John, I am not sure if the two more boxes exists and are
reserved for us, or if more need to be made.
2) I think we would need help making Reynolds cables for the MCH to PW08.
John Foglesong believes that there may not be any more Reynolds connectors
and that we would have to order these. He thought I should check with you
about this. Also can we get D0 techs to terminate the cables for us?
3) There are a number of cables running from the MCH to the west platform.
We have HV Reynolds cables from MCH-222 (about 4), some signal cables
running from MCH-132 (about 18), and some LMB cables from MCH-304 (about
5.) When you gave me a tour you showed me the route we could use for the
cable pulls. Is it possible for us (the FPD group) to get manpower from D0
to pull these cables? Or are we expected to get the manpower from within
the FPD group?
I have met with Kurt Krempetz and discussed the FPD cabling plan. He sees
no problems and the next step, according to him, is to present our plan
to Jon Kotcher so he can approve the plan and we can get help with
installing cable trays.
I also talked briefly with Ed Podschweitz about the FPD cable runs from
the MCH to PW08. He can help us terminate cables, but not much more. He
may have some cable we can use but probably we will have to order our own
as well as ordering the cables. He does not have the time or manpower to
help us lay the cables from the MCH to PW08 so we will have to do this
ourselves. Andrew should I order this stuff on IMY?
I am putting together a written list of what we want for Ed, and I hope to
present much of our plan to Jon by Friday. (He would prefer that we
present our plan at the Monday scheduling meetings, but I would like to
get things rolling and I am not free on Monday afternoons.) For the time
being I am only going include the ribbon cables, the PMT cables, and the
LMB cables. I still do not know where the rack monitor cables will go, nor
have I thought of a solution for where our 5V power box cables should go.
ANDREW
Information for the LVDT purchase order:
Macro Sensors
Attn: Eileen Ellis
7300 Industrial Center
Building 22
US Route 130 North
Pennsauken, NJ 08110-1334
Fax 856 317 1005
phone 856 662-8000
(address has changed from previous PO)
Quantity 7 part GHSA 750-1000-0392 $409 each $2836
Quantity 7 part LPC-2000-100 $207 each $1449
Total $4285
Informatin for the step motor driver PO
Professional Control Corporation
Attn: Vickie Stewart
1625 Winnetka Circle
Rolling Meadows, IL 60008
fax 847 797-1052
phone 847 481-7238
5 PDS15-2 Step Motor Driver $640 each $3200 total.
LIONEL
I have found the problem but not a solution.
I have checked the signal at the pin #6 of the chip U8. Normally,
when we go In, we must not see a signal. I put a position (2048) and,
during the motion, I saw 32 pulses. So, the counters are increased AND
DECREASED 32 times !!!! After, I changed the direction (position 1) and I
checked the signal at the pin #3 of the chip U8 (no signal when we go
Out). During the motion, I didn't see signals. I counted the number of
turns between the position 1 and the real Home position. We had 24 turns
(48 half turns). So, it seems that I didn't see all signals of the pin #6
because I counted only 32 pulses.
I checked the pulses of the pin #4 (and #13) and #12 (and #5) of
the chip U12. I didn't see bad pulses for the pin #4 (and #13) only for
the pin #12 (and #5). Sometimes we have 2 pulses for only one half turn
(normally one pulse for one half turn). They appear when we go In AND when
we go Out. But they are not counted for the Out motion.
The pulses at JP3 and JP4 which come from the encoders seem to be
good (no reflexions on the cables).
NEWTON
The last mesurements made by Lionel show two possible causes for the
problem. It seems to be a type of crosstalk between encoder channels in
the cable or a crosstalk internally in the CI U12.
He will do more tests and Iīm assembling a setup with the Interface
prototype in order to investigate more deeply.
The extra pulses happens exactly at half encoder signal period. It
means that the monostable is triggering two times during the pulse period.
This is not possible by circuit logic but it is possible if we have a
crosstalk. Reflections canīt do that so exactly for two diferent encoder
speeds.
The interface input signal from encoder seems to be clean but a very
short duration transition (glitch) due to the other channel crosstalk may
be present and not visible on the osciloscope.
Itīs clear now that the problem is in the CI U12. The pin 9 was supposed
to trigger on negative transition only but it is triggering sometimes on
the positive transition due to internal noise. We can try to fix the
problem with two possible solutions by now.
1- There is a small disk capacitor (103) close to U12 between +5V (pins
10, 11, 16 and 3). This is a filter capacitor. Increase the value to .1uF
(104) and check.
2- Put a small capacitor in parallel with R21 (2k7) You can try .01uF
(103) or less. This capacitor will increase the raising time and it is
possible to kill the crosstalk.
Iīm studying another solution but it means to put one more transistor to
invert the signal and use the positive transition. Iīm avoiding this
solution.
I assembled a setup with a motor, a encoder wheel, the Hall sensor and
the Index interface prototype this weekend to check the problem.
Iīm using the 74HC221 CI on my original prototype (and I made test
development with the 74LS221) and there is no problem. It is working fine.
The 74HCT221 used on ours board was not avaiable when I made the
prototype. HC and HCT performs the same logic functions, both are CMOS
devices with commom specifications. The 74HCT221 is relatively new on the
market and has "direct LSTTL input logic compatibility".
All tests Lionel have done showed an internal CI problem, a kind of
internal crosstalk. I donīt know if it is bad characteristic of this CI
(Manufacture ?) or I bought a bad batch.
All the other CIs used on board are HCT type and they perform very fine.
I asked Lionel to try some fixes but I feel we must replace the HCT
CI. We can use the same Iīm using, the 74HC221 or we can use the older
generation, the 74LS221. D0 stock or Fermi stockroom should have the LS
type.
Both CI can be bought in www.jdr.com or www.jameco.com.
The CI must be removed very carefully. Better to cut each pin from the
top and remove one by one if you donīt have practice. We have a very good
desoldering iron (with red rubber pump) and the CI can be removed
relatively easy.
EDUARDO
Ribbon cable situation.
Since Lionel and Hanz are leaving, cable testing and bunching will stop
and resume only when enough people is back. And it will be need a lot of
people to make the cabling.
Just testing the cables is easy. What takes a lot of time is to unbunch
the existing bunches, separate and roll then, and then rebundle the good
ones. We still could not find the optimum way to perform all it is need to
make a new tested and labeled bunch, but from what we experienced, we
estimate that the whole process takes around 2 hours for three people,
what means 6 man-hours. These benchmark can get better with practice, but
I doubt it can drop bellow 4 man-hours.
We are labeling the cables as RC--, where goes
from 1 to 9. We are not labelling them as being green or blue, but this
information must be taken, as we don't want to connect different cables.
The present situation is as follows:
Bunches ready:
Label Color Location
RC-01 BLUE BOX #7
RC-02 BLUE BOX #7
Cables tested and rolled:
BLUE GREEN
GOOD 38 16
BAD 21 9
Boxes contents:
BOX #4 -> Bunches to be tested
BOX #5 -> Empty
BOX #7 -> 2 good blue bunches
Total number cables tested:
Good Bad Total
Blue 56(72%) 21(28%) 77
Green 16(64%) 9(36%) 25
Total 72(71%) 30(29%) 102
All this report is kind of overshooted for the present situation, but I
think is a good template to be continuasly updated, as the number of
cables (and mess) increases.