ELOG AIDA

AIDA GELINA BRIKEN nToF CRIB ISOLDE CIRCE nTOFCapture DESPEC DTAS EDI_PSA 179Ta CARME StellarModelling DCF K40

AIDA, Page 25 of 46

Full | Summary | Threaded | Hide attachments

920 Entries

Goto page Previous 1, 2, 3 ... 24, 25, 26 ... 44, 45, 46 Next

Tue Mar 8 12:11:56 2016

CG, AE

RIKEN maintenance progress

Quote:

07/03/16

The new snout doesn't fit due to the screw holes being misaligned. I am going to try modifying the old one (that was in conflict with some material in the base) over the next couple of days. It is too long by 11mm, so if I can remove that it should then fit..

So after some modifications to the supports, the PSUs and NIM crates are now fully isolated from the frame.

I am currently working through changing all the guide pins for the new plastic ones and adding the shielding gasket.

Shunji made an interesting comment when we were discussing isolating the FEEs yesterday, in that, the ground connections for the chiller and the power we provide to our PSUs are connected to the same network.

- I measure the resistance between the chiller ground and the power ground to be 2.5 Ohms.

- The resistance between the chiller ground and the main Cu water pipe is ~2.2 kOhms.

- We have three possible options here (that we have come up with so far):

* disconnect the chiller ground from the network -> potentially very dangerous

* put a large resistance in between the chiller and the ground

* Shunji has available a noise cut trans with up to 30A capability that could be used for our NIM crates and power supplies (I think we draw < 30A IIRC) [photos attached]

I will carry out some short pulser tests with a DSSSD connected via the most recent kaptons this afternoon to see what effect the isolation and gasket has had so far.

Have you identified a specific noise issue with the Julabo recirculating chiller?

The STFC DL T9 test system has the recirculating chiller and AIDA PSUs connected to the same ac mains extender.

663

Thu Jun 15 07:44:41 2017

RIKEN Cable Inventory

List of the type and quantity of cables we have at RIKEN that are not currently in use.

Attachment 1: 170615_Cable_Inventory.xlsx

286

Mon Jun 6 15:57:51 2016

TD, ML & YS

R1121 (AIDA)

R1120 stalled shortly after DAQ GO
      'unable to connect' etc

      power cycle & reboot FEE64s

R1121 currently running 
      AIDA SYNCs currently but rates <100Hz in many FEE64s - see attachment 2
      link64 processes consuming large fraction of available CPU - see attachment 1

Attachment 1: 43.png

Attachment 2: 44.png

285

Mon Jun 6 15:06:22 2016

1TD, ML & YS

R1119

R1118 ended OK

R1119 DAQ GO, check AIDA SYNCs OK, toggle merge input etc 

Merge then halted with the usual unable to connect to COUNTER, nnaida1, nnaida1 etc error messages
so unable to reset, setup etc

Power-cycling and rebooting

Attachment 1: 41.png

Attachment 2: 42.png

284

Mon Jun 6 14:24:07 2016

TD, ML & YS

R1118 (AIDA)

22.14 R1118 starts

      aidas1 has been rebooted


      Changed /MIDAS/linux-ppc_4xx/startup/aidacommon from

     netint DACQ_PushEnable 60
     netint DACQ_FlushEnable 60

     to

     netint DACQ_PushEnable 10
     netint DACQ_FlushEnable 10

      AIDA FEE64s then power-cycled and rebooted  

      nnaida19 data link to merger disabled

      see attachments 1-8

22.30 R1118 stops

      AIDA SYNCs & good events at end of R1118 - see attachments 9-10

Attachment 1: aidacommon

#!/bin/bash
#
    UM=`umask`
    umask 0
#

     cd /MIDAS/linux-ppc_4xx/drivers/spi/module
     ./load
     sleep 5

     cd /MIDAS/linux-ppc_4xx/drivers/xaida/module
     ./load
     sleep 5

     cd /MIDAS/linux-ppc_4xx/drivers/aidamem/module
     ./load
     sleep 5

   MIDAS_MEMSAS_PORT=0
   export MIDAS_MEMSAS_PORT

export PATH=/MIDAS/linux-ppc_4xx/bin:${PATH}
export LD_LIBRARY_PATH=/MIDAS/linux-ppc_4xx/lib:${LD_LIBRARY_PATH}

    /MIDAS/TclHttpd/linux-ppc_4xx/TclHttpd-server&
     sleep 10

     cd /MIDAS/linux-ppc_4xx/bin

#
#    define netints and access registers
#

    netint Output_BufferSize 64
    netint Format_Option 4
    netint Xfer_Option 3

    netint Xfer_NoBlock 0
    netint Xfer_Overlap 0
    netint Xfer_Priority 0

    netint DACQ_TxInit 1
    netint DACQ_StatsTime 5
    netint DACQ_PushEnable 10
    netint DACQ_FlushEnable 10

    cd /MIDAS/Data_Acq/bin/linux-ppc_4xx
#    ./ExecV1
    nice ./AidaExecV8
#
    umask $UM
#

Attachment 2: 30.png

Attachment 3: 31.png

Attachment 4: 32.png

Attachment 5: 35.png

Attachment 6: 36.png

Attachment 7: 37.png

Attachment 8: 33.png

Attachment 9: 38.png

Attachment 10: 39.png

550

Sun Apr 2 03:32:30 2017

DK, OH

Pulser walkthrough

11:32 Pulser walkthrough, 90k down to 10k, 10k steps, 1 min per step
      R26
    
11:41 stop run R26


11:44 Pulser walkthrough, 10k to 2k in 2k steps, 90 seconds per step
      R27
11:53 stop run R27

11:56 Pulser walkthrough, 2k to 10k in 2k steps (90 sec each) & 10k to 40k in 10k steps (60 sec per step)
      R28

12:05 Attachment 1 shows biases ("bias_2_a.png")

12:07 stop run R28

12:15 background run, R29

12:39 stop run 29.

Attachment 1: bias_2_a.png

324

Tue Jul 5 13:43:02 2016

DK, PV

Pulser Test Run after AIDA is moved

Needed to run startx and start the TcLHttpd server on rpi

Following along here: https://elog.ph.ed.ac.uk/AIDA/242

Can now access http://nnrpi1:8015/AIDA/Rly16/

Window at first connection reads:

Using /dev/ttyUSB0 firmware version 0

Using /dev/ttyUSB1 firmware version 0901

Looks good. Sequence ALL On was selected

(By mistake, I then clicked Relay # to turn off...misread instructions...Switch all OFF, then sequence ALL on again)

7:51 they are turned on. Waiting several minutes now.

Add 4 L of water to the chiller

8:12

Save/Control Settings from Hardware Control tab:

Selected: 2016Jun13-00.53.55 and Restore. (missing from elog 242)

From Run Control, Enable Histogramming, Data Transfer: Enable #1 All (missing from elog 242)

TapeServer / Merger / Httpd started on Workspace 2

TapeServer reports

Cannot issue more Access Tokens: Claim TapeServer returned:- 3 Capability table is full

Make a new directory for storing test data: /data10/TapeData/July2016

Merger: Setup and configure

Data Statistics shows about ~5 x 10^5 events in many nnaida. Should we use a different setting file?

Now we try 2016Jun12-10.10.08

Perform ReSync

Probably event rate can be high because the SSD bias is off? We set up Putty and turn on all biases to -100 V.

Attachments 1 and 2 show the bias settings after they are turned on.

Good Events rate improves, factor 2 to 4 (now about 100k roughly)

Pulser settings: around ~900 on dial, attenuator x10, x10, x2 switches down, 5x up. Frequency ~250 Hz

21:19

Now we change the Control ASICs (select act on all ASICs, act on all FEEs)

Slow Comparator from 0x8 to 0x20

LEC/MEC Fast Comparator 0x4 to 0x80

Now the Good Events go down to about 10k to 25k roughly

TapeServer starts a run.

Merger started / paused / unpaused

Merger rate is 500k / sec. TapeServer is 4 k / sec.

AIDA Syncs shown in Attachment 3

Temps in Attachment 4

Good Events Attachment 5

Run Number 1

Setting file: 2016Jul05-21.37.20 (Note: I wrote the wrong setting file name last night...this is the right one!)

Show sample pulser peak in Attachment 6, 7, 8

July 6 - 12:29: Stop the run. 114 run files, 2.0 GB each.

Attachments 9, 10 show biases at the end of the run

Attachment 1: bias1-2016-07-05_21.12.png

Attachment 2: bias2_2016-07-05_21.12.png

Attachment 3: aida_sync.png

Attachment 4: temps.png

Attachment 5: good_evt.png

Attachment 6: pulser_peak.png

Attachment 7: pulse_2.15_nnaida13.png

Attachment 8: pulser-nnaida3.png

Attachment 9: bias1_run1_finish.png

Attachment 10: bias2_run1_finish.png

Mon Apr 20 09:45:38 2015

CG, TD, Patrick Coleman-Smith

Progress 20th April + RPi procedure + reply ++

Quote:

20/04/15

1200: Complete all points on first part of check list, except checking the PSU voltages.

System now in powered and has all network/HDMI cables attached.

1300: Connect RPi to power switch but when powered on it didn't find the switch. A reliable procedure to start seems to be...

connect USB power switch to RPI, make sure serial cable is disconnected from hub
power up RPi and power switch
check connection using dmesg, should see ...FT232RL for USB power switch on USB0
check connection from aidas1 by pinging RPi inet address 10.1.1.251
if good, Rly16 page should work from aidas1
connect serial cable, open PuTTY session, select AIDA console settings, open
should assign serial cable as USB1 an allow use of both the power switch and FEE console.

Currently this all works, we can control the power switch both from the RPi and aidas1, and see the FEE console via PuTTY session.

1400: Powered on system and tried to set up DAQ but received error (attachment 1) when doing the initial system reset in Run Control.

DAQ still usable for spectrum/temperature viewing, and all FEEs can be accessed to check ASIC control, but it seems timestamping will not be correct.

Tried to perform manual ReSync from master timestamp window and received similar error (attachment 2).

1430: nnaida8 running quite hot (ASIC temp ~65^oC) and ASIC temp on nnaida7+15 read as 0.00^oC. Otherwise, from pulser/stats data, both seem to be working correctly.

Unplugged power cable for nnaida7+8 at PSU end.

1600: Could timestamping issue originate from MACBs?

In rebuilding AIDA MACB - > FEE cabling redone. Should it follow a particular pattern/tree?

Current tree structure looks like (with MACB numbering going 1->11 L->R as you look at it):

MACB1 (setting: 0) ------- out 1: MACB2 (setting: 2) ---------- out 1: MACB3 (setting: 2) -> nnaida3+4, 11+12

&nb sp; &nb sp; ---------- out 2: MACB4 (setting: 3) -> nnaida19+20, 27+28

&nb sp; &nb sp; ---------- out 3: MACB5 (setting: 3) -> nniada1+2, 9+10

&nb sp; &nb sp; ---------- out 4: MACB6 (setting: 3) -> nnaida17+18, 25+26

&nb sp; --------- out 2: MACB7 (setting: 3) ---------- out 1: MACB8 (setting: 3) -> nnaida21+22, 29+30

&nb sp; &nb sp; ---------- out 2: MACB9 (setting: 3) -> nnaida7+8, 15+16

&nb sp; &nb sp; ---------- out 3: MACB10 (setting: 3) -> nnaida5+6, 13+14 -----> nnaida5 is the master and this comes from output2.

&nb sp; &nb sp; ---------- out 4: MACB11 (setting: 3) -> nnaida23+24, 31+32

Patrick - Is this set up OK? Do certain FEEs need to receive the MACB signal from certain MACBs or just all at the same point in the tree?

Also, MACBs 2+3 are on setting 2 on the dial, whereas the others (except MACB1, the 'grandparent') are set to 3. It seems like a hard thing to change accidentally so are they supposed to be like this or should they all be on the same setting?

1630: Voltages to nnaida7+8 OK at PSU output (+6V, +6V, +6V, -6.5V, +8V). Issue with contact to cooling rack?

With pulser input to all FEEs, only see pulser data in spectra for n-side (nnaida3+4, 7+8, 11+12, 15+16) FEEs. Other FEEs all show zero statistics.

The MACB system of clock and SYNC pulse distribution does have to follow some rules.

The Master needs to be in a very particular place. The rest are less important as long as they are all at the same level in the tree.

In the tree you report above and using the numbering you report. The Master should be in MACB3:out1.

The settings you have shown are correct if the Master is placed correctly ...

I will input a separate Elog entry detailing the settings for the MACB and the rules for the tree.

Thanks

Regarding nnaida7+8. I agree the issue to tackle first is the cooling plate contact to the module. Where do they feature in the layout ?

Is the plate tightened up correctly ?

As far as I am aware this module/crate has not recently been opened so the 'contact' should be as good (or bad) as it ever was.

But it would, of course, bear checking.

Regarding the P side FEE64s ... sorry about this ... but is the P pulser working ... well i did have to ask ;-

According to a DSO the positive and negative pulser inputs and cabling are OK

Regarding the P side problem.

What is the result if you change one of the N-Side FEEs to use the P-side pulser and vice-versa ?

Regarding the temperature problem.

Which position are the problem modules in ?

Mon Apr 20 09:07:59 2015

CG, TD, Patrick Coleman-Smith

Progress 20th April + RPi procedure + reply

Quote:

20/04/15

1200: Complete all points on first part of check list, except checking the PSU voltages.

System now in powered and has all network/HDMI cables attached.

1300: Connect RPi to power switch but when powered on it didn't find the switch. A reliable procedure to start seems to be...

connect USB power switch to RPI, make sure serial cable is disconnected from hub
power up RPi and power switch
check connection using dmesg, should see ...FT232RL for USB power switch on USB0
check connection from aidas1 by pinging RPi inet address 10.1.1.251
if good, Rly16 page should work from aidas1
connect serial cable, open PuTTY session, select AIDA console settings, open
should assign serial cable as USB1 an allow use of both the power switch and FEE console.

Currently this all works, we can control the power switch both from the RPi and aidas1, and see the FEE console via PuTTY session.

1400: Powered on system and tried to set up DAQ but received error (attachment 1) when doing the initial system reset in Run Control.

DAQ still usable for spectrum/temperature viewing, and all FEEs can be accessed to check ASIC control, but it seems timestamping will not be correct.

Tried to perform manual ReSync from master timestamp window and received similar error (attachment 2).

1430: nnaida8 running quite hot (ASIC temp ~65^oC) and ASIC temp on nnaida7+15 read as 0.00^oC. Otherwise, from pulser/stats data, both seem to be working correctly.

Unplugged power cable for nnaida7+8 at PSU end.

1600: Could timestamping issue originate from MACBs?

In rebuilding AIDA MACB -> FEE cabling redone. Should it follow a particular pattern/tree?

Current tree structure looks like (with MACB numbering going 1->11 L->R as you look at it):

MACB1(setting: 0) ------- out 1: MACB2 (setting: 2) ---------- out 1: MACB3 (setting: 2) -> nnaida3+4, 11+12

---------- out 2: MACB4 (setting: 3) -> nnaida19+20, 27+28

---------- out 3: MACB5 (setting: 3) -> nniada1+2, 9+10

---------- out 4: MACB6 (setting: 3) -> nnaida17+18, 25+26

--------- out 2: MACB7 (setting: 3) ---------- out 1: MACB8 (setting: 3) -> nnaida21+22, 29+30

---------- out 2: MACB9 (setting: 3) -> nnaida7+8, 15+16

---------- out 3: MACB10 (setting: 3) -> nnaida5+6, 13+14 -----> nnaida5 is the master and this comes from output2.

---------- out 4: MACB11 (setting: 3) -> nnaida23+24, 31+32