https://docs.google.com/spreadsheets/d/12hgbrywB10hGsKt5uc2HnLfZymh8_uvM6cEASbbqnBE/edit#gid=1347508769

[UPDATED 22/4: initial LISE file had incorrect thickness for MACi plastic]

Calculations for Al degrader thickness required to implant ions in AIDA DSSD stack.

Calculations are based on LISE files from main experiment, and done for settings with expected longest and shortest range 
of 
ions 
before implantation setup: 
- LISE++ for the 95Br BigRIPS setting : B1_U_BefissionZDSLAA_95Br_6mmF1.lpp
- LISE++ for the 85Ga BigRIPS setting : B1_U_BefissionZDSLAA_85Ga_6mmF1.lpp

Setup after last beamline detector (IC): 180cm Air + Al degrader + MACi (7mm plastic@45 degrees) + AIDA (3mm silicon) + 
thick 
Al 
plate (1 cm).


+ 84Zn setting (long range):

 - Al degrader of 1 mm required in front of implantation setup to stop 84Zn activity in AIDA (end of stack).  The range in 
Si 
is 
reduced by ~1.1 mm per each mm of Al added in degrader. 

 - Activity from heavier (more intense) isotopes seems to be implanted at similar location as more exotic isotopes (always 
considering 1p knockout channel, might be worth looking also at unreacted channels).

+ 94Se setting (short range):
 
 - Activity stopped before AIDA. We'll need to remove MACi if we want ions implanted in AIDA (unless the tail of energy 
distribution 
after secondary target is very large).
 
 - If we remove the MACi plastic, we would need 2 to 3 mm of Al degrader to stop ions in AIDA (assuming the 1mm veto after 
segmented 
MACi plastics remain).



See attachments for detailed description

Stack has been changed in configuration from a 6 DSSD stack to 8 DSSD stack.
What was detectors 1-6 are now 3-8 with 2 new detectors added to the front.

The stack order is now:
    DSSD 1 3058-25 Top
    DSSD 2 3058-2
    DSSD 3 3058-4
    DSSD 4 3058-3
    DSSD 5 2998-23
    DSSD 6 3058-5
    DSSD 7 3058-6
    DSSD 8 3058-7  Bottom

To handle the new detectors an additional 4 FEE modules 8 FEE64 were installed in the system with MAC addresses:
    FEE 25 - 2B 09 E7
    FEE 26 - 2B 22 55
    FEE 27 - 2A F6 D4
    FEE 28 - 2A ED 8F
    FEE 29 - 2A D0 1A
    FEE 30 - 2B 33 0C
    FEE 31 - 2A B6 45
    FEE 32 - 2A B2 B2

FEE Mapping is now:
                FEE Number
    DSSD     A    B    C    D
     1       25   28   30   31
     2       26   27   29   32
     3       1    20   22   23
     4       2    19   21   24
     5       9    12   14   15
     6       10   11   13   16
     7       17   4    6    7
     8       18   3    5    8

     All 4 new p side cables were made using 33" ribbon cables
     The n side cables for detector 2 were made using 37" cables
     The n side cables for detector 1 were made using 39" ribbon cables (37" was to short)

     Non-isolated cables related to C connector on DSSD

     The detectors were placed inside the snout with two reference lines for insertion.
     The first labelled as June 18 6 stack will place the centre of the detector stack (Between detectors 5 and
6) in the centre of BRIKEN
     when inserted up to this line.

     Distance from edge of BRIKEN to centre is 37.5cm

     The second mark is 1cm along from this and is labelled June 18 8 stack. This positions the centre of the
stack (Between detectors 4 and 5), what would be 3 and 4 if only 6 detectors)
     in the centre of the BRIKEN array.

     One thing to note is that with 8 detectors getting the snout on is a tight fit and can push down the rods
the detectors are held on. This was previously
     a friction fit between the rods and the snout base. The rods had to be pulled out slightly to allow for the
extra length needed for 8 detectors.
     To aid in the rods were not slipping grub nuts were moved to the bottom and locked in position. This may
not hold the strain of someone pushing the snout against them so caution
     is still advised when putting this on.

     When in the 8 stack configuration DSSD 1 is 4.5cm from the end of the snout. To support more detectors
longer rods would be needed though.

18.55 Julabo FL11006 recirculating chiller refilled to "H" marker of the filling level indicator.

      See http://www2.ph.ed.ac.uk/~td/AIDA/Information/Julabo%20FL11006.pdf
      
      To refill from 60% L-H to 100% L-H required c. 4 litres of water.
      Following refill there is a trickle of water from the overflow connector which is being 
      collected by hose and bucket - this flow should cease when the fluid level falls below
      the overflow level.
      
19.20 FEE64 temperatures OK - see attachment 1

12:32 Chiller found almost empty & still working at 20C. Refilled to overflow.

3ph 100VAC/50Hz to Julabo FL11006 3ph 230VAC/50Hz via local transformer

After changing degrader to optimize 40Mg, hit pattern in AIDA is shown in figure below.

The implantation position changed from right side position of  first DSSD to center position of last DSSD.

 With the system in T9 and a Keithley Source Meter supplying HV to the detector.

The source meter supplies 200V and measures the current .... 

I noticed that the current value was not stable... varying by +/-0.5uA. In conversation with Marcello i learnt that normally much more stable than this. 

I have carried out the following changes.

added a 22nF X7R capacitor at the detector end of the Kapton cable from the HV connector pin  ( G/R ) to the ground plane of the Kapton.

added a 14k resistor in series with the HV supply +ve signal before it connects to the adaptor board.

isolated the G/R connection on the second Kapton that would normally be connected to the HV on the detector.

The HV now is a lot quieter +/-0.01uA.

Next i disconnected the HV -ve input from ground at the adaptor board. This resulted in all the FEE64 being equally noisy!!

Next I connected a 22nF X7R capacitor between the HV negative and ground at the adaptor. This resulted in all FEE64 becoming equally calm. 

The FWHM of the spectra is not good at 250 to 300 but the fact that all FEE64 are equal now is interesting.

I will update this post with pictures.

 Update:- 

This change was not stable and repeatable. I changed back to the original connections and things haven't gone back. 

So power down and leave for today.... It doesn't make sense to me ... but then that's nothing new :-)

It appears that something is heating/charging up during the day and the noise becomes swamped by this effect ????

Inventory is currently packaged up under the AIDA desk in B3F


2 FEE64 Modules

Module 1 - MAC Addresses
2B:33:15
2B:22:6E <- Loose HDMI

Module 2 - MAC Addresses
2B:09:DA <- ASIC #1 HEC Hot Channel, LEC noisy
2B:11:C5 <- Missing ASIC

MACB A-MP 202394 -2    72-38

MACB RevB Ser38 AMP 202394-2

MACB RevB AMP 202394-2   81-49

Attached is an updated inventory of the cables and adapter boards we have in RIKEN.

Got the error Server Internal Error
while trying to obtain /AIDA/SaveRestore/SaveRestore.tml.
can't read "env(MIDASBASE)": no such variable while executing "file join $env(MIDASBASE) XilinxLinux ppc_4xx rfs $fee64 tmp SaveState.log" (procedure "do_Save" line 17) invoked from within "do_Save" ("SAVE" arm line 1) invoked from within "switch -glob [lindex $w 0] { RESET {set started 0} CLEAR {EmptyLog} ELOG {PrintLog} ..." (procedure "do_click" line 21) invoked from within "do_click" invoked from within "if {$started != 0} { variable JS "" variable LogFlag if {$LogFlag == 1} {InsertLog "Last Updated: [clock format [clock seconds] -forma..." (file "SaveRestore.tcl" line 8) invoked from within "source SaveRestore.tcl" (in namespace eval "::AIDA_SaveRestore" script line 6) invoked from within "namespace eval AIDA_SaveRestore { global env source [file join $env(MIDASBASE) TclHttpd tcl Common common.tcl] source [file join ..." invoked from within "subst \n\n\[Doc_Dynamic\]\n\n<html>\n<head>\n\n<title>Module\ Settings\ Save/Restore</title>\n\n\[global\ env\;\ source\ \[file\ join\ \$env(MIDASBASE..." ("uplevel" body line 1) invoked from within "uplevel #0 [list subst $script]" (procedure "SubstFile" line 12) invoked from within "SubstFile /MIDAS/TclHttpd/Html/AIDA/SaveRestore/SaveRestore.tml {}" ("uplevel" body line 1) invoked from within "uplevel 1 [list SubstFile $path $interp]" (procedure "Subst_File" line 7) invoked from within "Subst_File $template $interp" invoked from within "TemplateInstantiate $sock $path {} $suffix {} $Template(templateInterp)" (procedure "Doc_application/x-tcl-template" line 9) invoked from within "$cmd $path $suffix $sock" (procedure "Doc_Handle" line 20) invoked from within "Doc_Handle $prefix $path $suffix $sock" (procedure "DocDomain" line 44) invoked from within "DocDomain / /MIDAS/TclHttpd/Html sock8 AIDA/SaveRestore/SaveRestore.tml" ("eval" body line 1) invoked from within "eval $Url(command,$prefix) [list $sock $suffix]"

Tcl Call Trace

Installed Xilinx 14.7 LabTools + (free) WebPack license

Start iMPACT

Connect Xilinx programmer via 14-way ribbon cable to MACB PCB jtag connector
and connect USB cable to laptop

Powerup NIM bin with MACB (serial #13)

Auto-install Xilinx programmer driver

Use iMPACT Wizard to automagically find Xilinx device of MACB

Load new *.jed file
 Operations -> Program
 Operations -> Verify

TTY console log

Welcome to iMPACT
iMPACT Version: 14.7
Project: C:\Xilinx\14.7\LabTools\LabTools\auto_project.ipf created.
// *** BATCH CMD : setMode -bs
// *** BATCH CMD : setMode -bs
// *** BATCH CMD : setMode -bs
// *** BATCH CMD : setMode -bs
GUI --- Auto connect to cable...
// *** BATCH CMD : setCable -port auto
INFO:iMPACT - Digilent Plugin: Plugin Version: 2.4.4
INFO:iMPACT - Digilent Plugin: no JTAG device was found.
AutoDetecting cable. Please wait.
*** WARNING ***: When port is set to auto detect mode, cable speed is set to default 6 MHz regardless of explicit arguments supplied for 
setting the baud rates
PROGRESS_START - Starting Operation.
Connecting to cable (Usb Port - USB21).
Checking cable driver.
 Driver file xusb_xp2.sys found.
 Driver version: src=2301, dest=2301.
 Driver windrvr6.sys version = 10.2.1.0. WinDriver v10.21 Jungo (c) 1997 - 2010 Build Date: Aug 31 2010 x86_64 64bit SYS 14:14:44, 
version = 1021.
 Cable PID = 0008.
 Max current requested during enumeration is 300 mA.
Type = 0x0005.
write (count, cmdBuffer, dataBuffer) failed C0000004.
 Cable Type = 3, Revision = 0.
 Setting cable speed to 6 MHz.
Cable connection established.
Firmware version = 2301.
File version of C:/Xilinx/14.7/LabTools/LabTools/data/xusb_xp2.hex = 2401.
Firmware hex file version = 2401.
Downloading C:/Xilinx/14.7/LabTools/LabTools/data/xusb_xp2.hex.
Downloaded firmware version = 2401.
PLD file version = 200Dh.
 PLD version = 200Dh.
PROGRESS_END - End Operation.
Elapsed time =      1 sec.
Type = 0x0005.
ESN option: 000013E7C24E01.
Attempting to identify devices in the boundary-scan chain configuration...
INFO:iMPACT - Current time: 01/10/2016 09:30:42
// *** BATCH CMD : Identify -inferir 
PROGRESS_START - Starting Operation.
Identifying chain contents...'0': : Manufacturer's ID = Xilinx xc2c128, Version : 1
INFO:iMPACT:1777 - 
Reading C:/Xilinx/14.7/LabTools/LabTools/xbr/data/xc2c128.bsd...
INFO:iMPACT:501 - '1': Added Device xc2c128 successfully.
----------------------------------------------------------------------
----------------------------------------------------------------------
done.
PROGRESS_END - End Operation.
Elapsed time =      6 sec.
// *** BATCH CMD : identifyMPM 
// *** BATCH CMD : assignFile -p 1 -file "C:/Users/td/Local Documents/misc/macb_top_revB.jed"
'1': Loading file 'C:/Users/td/Local Documents/misc/macb_top_revB.jed' ...
done.
INFO:iMPACT:501 - '1': Added Device xc2c128 successfully.
----------------------------------------------------------------------
----------------------------------------------------------------------
INFO:iMPACT - Current time: 01/10/2016 09:32:54
// *** BATCH CMD : Program -p 1 -e -v 
PROGRESS_START - Starting Operation.
Maximum TCK operating frequency for this device chain: 33000000.
Validating chain...
Boundary-scan chain validated successfully.
'1': Erasing device...
'1': Erasure completed successfully.
'1': Programming device...
done.
'1': Verifying device...
done.
'1': Setting ISC done bits...done
'1': Programming completed successfully.
PROGRESS_END - End Operation.
Elapsed time =      2 sec.
INFO:iMPACT - Current time: 01/10/2016 09:33:01
// *** BATCH CMD : Verify -p 1 
PROGRESS_START - Starting Operation.
Maximum TCK operating frequency for this device chain: 33000000.
Validating chain...
Boundary-scan chain validated successfully.
'1': Verifying device...
done.
'1': Verification completed successfully.
PROGRESS_END - End Operation.
Elapsed time =      0 sec.

Connected to aidas from daresbury.
Started Firefox with windows for Rpi, Merge, Runcontrol.
Power on FEEs from Pi.
All power-up/RESET/SETUP ok.

Change Firmware from 0x17500C15 to 0x16600C1B which adds SYNC counters to the Master and Slave Timestamp logic.
Power cycle using Pi.
nnaida20 failed to start properly. Logged in as Root ok. TclHttpd Server not in place. dmesg showed no start of
XAIDA or XAIDAMEM. Instigated "reboot" by command line not power cycle. All fine after this completed.

Copied /MIDAS/TclHttpd/Html/AIDA to a backup copy.
Changed LOCAL.*, Aida.*, Check.*

System wide checks now has check SYNC counters.

Checked temperatures. Max is nnaida12 with 68.62

SYNC check :- All read 693248.
The Master counts how many SYNC pulses are issued. All Slaves count SYNC pulses received.
The Check uses a Re-Sync pulse generated without telling the Slaves a Re-Sync is due. The Master and Slaves copy
their SYNC counter to a register when the Re-SYNC occurs. These are read back and displayed.

Started the DAQ as setup with no transfer.
Good event rates range from 502Kitems/sec to 594K.

SYNC counter check : All 839680

Stop DAQ/ Enable Transfer/Merge in Pause/Go DAQ.
All the following times are DAQ local.

19:15 Good Events 414k to 484k across all 23 FEEs.

Stop DAQ/change all thresholds to 200/Go DAQ

Good Events 4.2K to 348K

19:38 Sync counter check :- 1653760 all
Temperatures Max nnaida12 69.12

20:01 Temperatures Max nnaida12 69.19
Sync counter check :- 2181120 all

20:19 Temperatures Max nnaida12 69.25
Sync counter check :- 2590720 all

21:09 Temperatures Max nnaida12 69.19
Sync counter check :- 3729408 all

21:23 Toggled Merge Pause. Doesn't SYNC.
Check statistics. SYNC rate ok, SYNC counts uneven. PAUSE range from 0 to 1158.
DAQ stop/zero statistics/restart Merge/setup and configure/Go Merge/Pause Merge/Go DAQ/Toggle Pause
21:43 Merging now at 4943691 items/sec.

Temperatures Max nnaida12 69.25

DL to RIKEN communication link failed.

23:02 Reconnect by firefox in ribfdaq.
Temperatures Max nnaida12 69.31
Merging still active.

23:20 Sync counter check :- 6722560 all
no sysc errors in system check.

23:45 Merger running 5.4M items/sec
Temperatures max nnaida12 69.44

Stop DAQ/Toggle Pause on Merger All ok.
23:51 Sync counter check 7439360 all except nnaida22 which returns -1
Retry Sync counter check 7478272 all except nnaida22 which returns -1

Log in to nnaida22, Servers look ok. AIDAExec running ok. dmesg has nothing extra.
Runcontrol shows nnaida22 as stopped.
Access nnaida22 alone and shows undefined.

Using diagnostics checked able to read registers correctly and read the sync counter register as 7478272.

Retry Sync counter check all 8006655 except nnaida22 which shows 8006388.

Check SYNC error counters and all ok except nnaida22 which has 6363 errors.

Finishing work ..... power off FEE64s using Pi, check a couple with ping from aidas1 .... fine.

Write up ELOG.

Repeat tests on Monday.

Data for ~3 hrs: Nov 28th, 20:06 to 23:16

Bigrips run 1060 to 1062

AIDA run R30_ 2 to R30_40

Degrader setting: variable= (0.3mmW/1mmAl + 1mmW/1mmAl) + fixed= ( 8 mm Al)

IMPLANT PROFILE: Compare to previous setting (with 3mm Pb as fixed degrader) in elog entry https://elog.ph.ed.ac.uk/AIDA/487

In particular, attachment: https://elog.ph.ed.ac.uk/AIDA/161127_195411/run104x_imp_profile.png

The implantation positin for 40Mg seems to be well optimized (perhaps we can add ~0.5 mm Al to move it further downstream, but not more than that!).

IMPLANT EFFICIENCY: If we compare the number of Al and Mg ions in the ZDS PID for the three runs (~46000, see attachment 5) to the number of ions identified as implants (9389, see attachment 2), we get:

Implant efficiency ~ 20 %   (=9389/46000)

P/S: attachment: hit pattern in BRIKEN with F11 plastic (beam), only for BigRIPS run 40Mg1060

Bigrips run 1127

AIDA run 43_ 33 to 43

Degrader setting:
Variable degrader:
0.5 mm W + 1 mm Al : in
0.3 mm W + 1 mm Al : in
1 mm W + 1 mm Al : in
Fix degrader:
20mm Al+ 0,2 mm Al

See https://elog.ph.ed.ac.uk/AIDA/502 for comparison

Degrader setting was:
Variable degrader:
0.5 mm W + 1 mm Al : in
0.3 mm W + 1 mm Al : out
1 mm W + 1 mm Al : in
Fix degrader:
20mm Al+ 0,2 mm Al

Large portion of the beam is passing through AIDA! We need to change the degrader