 Mon May 23 07:28:38 2016, TD, 23 May 2016 25x
|
12.45 Rly16 'Sequence ALL On' operational
15.20 Startup remote control of CAEN N1419 4-ch HV modules
DSSSD #1-7 leakage currents OK - see attachments 1-2
Ambient temperature +24.8 deg C
15.35 Plot Temperature appears to plot the first 15,000 (or so) temperature readings
and not the *most recent* 15,000 (or so) readings. See attachment 3.
There is no way to change the time window for the temperature plot
As a workaround, empty file using the command
cp /dev/null /MIDAS/log/temperatures.txt
17.10 For all FEEs (*except nnaida19 & nnaida26) which are currently disconnected)
reprogram FEE flash memory using FEE_GF_Feb16_17.bin
Power cycle
attempt #1 - wait 4'
STATE for nnaida9 returned with an error
connect failed
NONE
connect failed
attempt #2 - wait 6'
STATE for nnaida4 returned with an error
connect failed
NONE
connect failed
attempt #3 - wait 8' - OK
Installed updated Check software - Check.tml .tcl .js and Common.js
Started DAQ - histogramming enabled - data transfer disabled
Large fraction of FEEs not producing SYNCs, SYNC rate low (~20-30Hz) for other FEEs - see attachments 4 & 5
Note slow comparator 0xc8 (i.e. high) and fast discriminators (LEC/MEC) disabled
Firmware version - attachment 6
System wide checks ASIC clock sync (30/30 fail) and ADC calibration (7/30 fail) work as before but
new checks produce errors - see attachments 7-11
Additional screenshots from Master Timestamp Control - see attachments 12-17
00:40 PJCS identifies workaround to above problems - correlation controls now enabled for master timestamp
FEE (nnaida5) only. May also explain issues with nnaida19 & nnaida26.
PJCS will produce detailed, separate Elog entries
Currently, all (30) FEE64s running OK with sensible AIDA SYNC rates.
But. No spare fuses (16A/250V slow blow) for USB-controlled ac mains relay. Until Chris arrives in
c. 9h. We will explore options to use *second* USB-controlled ac mains relay. |
|
Sat May 14 11:27:09 2016, AE, VP, [How To] DAQ correlation monitor (June16 campaign)
|
The program for online monitoring the correlation of the DAQ systems (AIDA-EURICA-BigRIPS) through a common scaler is SyncCheck (J.
Agramunt).
The code runs in the d05 server, receiving data transferred to a DataSink from each of the individual DAQs. The data transfer is
done with the DataRelayFilter code for AIDA (AE), and the euricatssender and ribftssender (Baba-san) codes for EURICA and RIBFdaq,
respectively.
The attached screenshots show how to setup these programs. Follow these steps:
1) Log in to d05 as user 'aida'. Start an instance of the DataSink code with option -i 3 (3 data stream, which will use ports 10305
to 10307). The code is saved in /home/aida/DataPackage/DataSink/Linux64
2) In the d05 server start the following codes: euricatssender (in /home/aida/ribfts/euricatssender/ directory), and ribftssender
(in /home/aida/ribfts/ribftssender/ directory). If you give the codes dummy command line option (e.g. -X) the value of transferred
timestamps will be printed to screen as diagnostics.
3) In the AIDA computer (aidas1), start the DataRelayFilter program (will work from any directory). As command line arguments
provide the IP address of d05, and the TCP port and id of the data stream for the DataSink program: DataRelayFilter -n 10.32.0.12 -
p 10307 -I 2
Only the master FEE will produce correlation scalar items (?). The code has as default NNAIDA5 for the module where to search for the Corr Scaler
items; if this has to be changed use command line option -m X (where X is NNAIDAX number for new master FEE)
4) Back in the d05 server start the SyncCheck program, in the directory /home/aida/SyncCheck/. You can give as an argument the ID
of the Master data stream for the synchronization check, through "-M ID" (should be done if one of the three data streams is down).
For example "SynCheck -M 2" will use AIDA as the master timestamp.
5) Perform a manual correlation reset request to synchronize the value of the correlation scaler in all three DAQs. This is done with the
button 'Force Correlation Reset' of the AIDA "Correlation Status & Control" webpage (attachment 2), which can be accessed from the MIDAS web-
based control of AIDA.
The SyncCheck code will display a few spectra for onine monitoring of DAQ correlation (attachment 3, shown only with AIDA and EURICA running).
A peak will appear showing the offset in the correlation scaler between the different DAQs. The counts in the peak should increase
continuously, and its position should not change. If it doesn't, try sending a Correlation Reset signal (step 5). If this does not fix the
monitor, report a correlation error!
Further information on the scheme for data synchronization is here:
https://elog.ph.ed.ac.uk/BRIKEN/6
https://elog.ph.ed.ac.uk/BRIKEN/5 |
|
Fri May 13 13:27:50 2016, patrick Coleman-Smith, Power supply changes and blowing fuses !
|
Reading about the power supply changes and the requirement to replace fuses leads me to be concerned.
I think the power being changed is the AC input to the FEE64 power supplies.
Which Fuses are failing ? |
|
Fri May 13 13:24:42 2016, Patrick Coleman-Smith, An idea that might help when everything grinds to a halt
|
When using the T9 system and running with too much rate in one FEE64 so the system is unbalanced.
I found a good way to understand this and to be able to operate the controls of the FEE64s was to place the Merger in "Pause" mode.
Then the data is extracted from the busy FEE64 but it can still be controlled.
When there is unbalance in the system it is possible for one or more queue in the Merger to become full and so the communication with that FEE64 is not possible.
Placing the Merger in Pause mode will mean all the data is discarded, the links run at full speed and action can be taken on the problem FEE64(s) to help balance the system out better.
I hope this helps .... it is highly likely that this is already being done.....
Perhaps a wise sequence when starting the whole DAQ is to operate with the Merger in Pause mode and only switch it to merging when the user is happy with the rates.
In the statistics window of the FEE64 there is an indication of the data being transferred over the link.
When deciding how to run the experiment thought needs to be given to the various maximum rates. The rate from the FEE64 is 500k events/sec. If running with 26 FEE64 then this goes up to 13M events/sec. An event is 64 bits.
I'm not sure what the maximum rates are in the Merger and the TapeServer.
|
|
Fri May 13 06:18:53 2016, AE, VP, BM, Friday May 13th 9x
|
11 am: Changed configuration of power source for AIDA PSU (see paper logbook). Now both cables with power for
USB relay are connected to the 'C' unit of the F11 power supply. They use different socket pads, and share them
with power cables for raspberry pi and NIM crates. Situation intermediate to what we have on Tuesday.
Resolution of pulser peaks improved slightly w.r.t. yesterday, but still we have the high frequency noise
(500kHz) present (attachments).
12 pm: We found the FEEs crash (loose connection/synchronization) when we enable the fast discriminators (see
attach. 1). This could be in the case when some of the discriminator channels are triggering at a fast rate
(noise above threshold). We observed the same pattern a few times.
5 pm: During all afternoon we've not been able to put AIDA in an operational state. There is always one or more
FEEs that do not synchronize or loose connection. Also the fuse of the PSU broke and we had to replace them.
Source for state of the system could be related to current configuration of PSU power, or the presence of noise
we observed in last couple of days.
6 pm: Back to configuration of PSU from yesterday:
F11 power supply 'C' ---->----> PSU relays 1-4
|
|---> NIM crates, RPI, etc
F11 power supply 'B' ----> PSU relays 5-8
Started by checking the options. Loaded Options 2016May03-20.44.33. It looks like settings of ASICs are not the
standard ones (e.g. threshold 47). Tried restore settings in Save/Restore option. It worked for all but NNAIDA25
(fri22.png), but other have proper settings (but values of #25 also look ok!).
Performed 'Check ASIC clock timestime' in systemwide checks: all failed (fri23.png)
Performed 'Check ADC calibration' in systemwide checks: all passed, except for nnaida26 (fri24.png)
Master Timestamp Control -> Perform ReSYNC: worked for all modules except nnaida26
we lost connection to 26..... (fri26.png)
Attempted ADC calibration of NNAIDA26 (FADC align and control) failed (fri27.png)
Disabled NNAIDA from Run Control, and Reset all modules. But now after reset the setup button does not appear,
just Reset one as if the action had no effect.
Tryed restore settings again. Again nnaida25 returned problem, but yet again nnaida26 is the one that actually
doesn't have proper ASIC settings. Confirmed this with 'Check ASIC control' (fri29.png). Is there an error in the
error report message of 'Restore Settings'?
We checked cable connections (HDMI, ethernet), and afterwards NNAIDA26 keeps giving problems. We give up on it,
remove it from DAQ configuration (https://elog.ph.ed.ac.uk/AIDA/189), and system nos seems to be runing ok
without it.
8 pm: disconnected all remaining cables from MACB->other crates (only daq correlation in macb1), and went back to
yesterdays configuration of PSU power with all power from 'C'
F11 power supply 'C' ---->----> PSU relays 1-4
| |
| |---> PSU relays 5-8
|
|--->---> NIM crates, RPI, etc |
|
Thu May 12 16:55:37 2016, AE, VP, BM, Thursday May 12 7x
|
Continued work on beta-trigger for EURICA. However the system seems to have different noise condition than before, which
we think appeared after we changed power source for FEE's PSU (https://elog.ph.ed.ac.uk/AIDA/220). This is high frequency
noise of low amplitude, with a period of 10 usec.
The effect on the resolution measured with the pulser is not too large - thus our conclusion in elog entry 220 that noise
conditions had not changed much - but the noise does create a large trigger rate that would not allow us to set a low
trigger threshold (for MAC-B outputs from fast discriminators). The rate of singles from front or back, as well as coincidence of
front-back strips, increased by more than a factor of ten compared to previous conditions (e.g. ~200 coincidences for one ASIC
enables in each side of DSSD1, and fast threshold of 10).
Saved some data in this conditions, with a threshold of 16 for the fast discriminators (enabled in one ASIC for 8 of the
FEEs). When fast discriminator lowering threshold to 9, the system got upset and lost synchronization. Tomorrow we'll
attempt to revert to previous configuration of PSUs.
R16*gz:
DSSD HV: +100 for all.
Leakage current (uA): 4.2, 4.9, 3.7, 3.9, 4.2, 3.8, 10.7 (from Det#1 to veto)
Enabled fast discriminators in ASIC2 of DSSD1 and DSSD5 (NNAIDA#: 25, 30, 27, 32, 9, 13, 11, 16)
DSSD#1 is next to 207Bi source |
|
Thu May 12 15:50:48 2016, Patrick, System Checks and firmware update
|
| Added two checks to the System wide checks.
Modified the Firmware so the checks work properly.
One check reads the status of the FEE64 clocks and checks against expected value.
The other check reads the value from all the FEE64 Sync Error Counters, pauses for one second, then reads them again and compares with the first reading. Any change is reported as an error.
The Sync Error counter is incremented if the SYNC pulse arrives at a FEE64 when the Timestamp counter in the FEE64 is not at the correct value. |
|
Wed May 11 11:24:09 2016, Patrick, Correlation Controls
|
Please note that the Force Trigger and Reset buttons in the Correlation Browser only have meaning if the FEE64
selected is the Master. |
|
Wed May 11 06:37:32 2016, AE, VP, BM, Wednesday 11 May
|
*2:30 pm*: changed power source of USB-controlled power supply for FEEs. Now one of the power cables is connected
to the 'B' power supply of F11, and the second to the 'C' power supply (these are in the unit on top of WASBI
crates). The reason for change is that before both were connected to 'C', and drained current was very close to
limit of 10 A (and power cord getting noticeable hot). We'll check resolution after this switch.
Detectors 1, 2, 3, and 4 biased to 100V, detectors 5, 6, and veto biased to 70V.
n-side is more noisy than p-side, but resolution comparable to previous configuration:
NNAIDA# FWHM [ch]
1 91
2 61
3 84
4 -
5 160
6 -
7 79
8 84
9 71
10 76
11 101
12 81
13 69
14 78
15 199
16 107
17 82
18 62
19 -
20 89
21 168
22 70
23 80
24 73
25 81
26 13
27 109
28 13
29 15
30 126
31 13
32 100
*5 pm*: Set-up correlation scalers for AIDA<->EURICA<->BigRIPS (detail diagram coming soon, now only in paper
logbook).
*6:30 pm*: Started EURICA DAQ with Pieter and Gabor.
A folder is created to record data of June campaign: /raid/11/mbs/2016_ucampaign/
Tested correlation of AIDA and EURICA with a pulser run, triggering EURICA and AIDA correlation scaler with 250
Hz. The corresponding files are
/raid/11/mbs/2016_ucampaign/test0003.lmd
/TapeData/may2016/R12_0.gz
Phong did a quick analysis and the pattern of correlation scalers in both files is similar (attached figures). It
is also consistent with the number of reset requests we sent during the data taking (three requests closely spaced
in the middle of run, and two more in the end of the run). |
|
Wed May 11 06:01:16 2016, AE, VP, BM, Beta trigger
|
Please find attached the best diagram of the beta trigger logic circuit for EURICA campaign 2016 |
|
Wed May 11 06:00:56 2016, AE, VP, BM (Byul Moon), FEE64 <-> MACB trigger mapping
|
Here is the mapping of the trigger output of MAC-B modules to FEE64 modules
3.1 NNAIDA5 veto-X2
3.2 NNAIDA14 D4-X2
3.3 NNAIDA13 D5-X2
3.4 NNAIDA6 D6-X2
4.1 NNAIDA28 -
4.2 NNAIDA27 D1-Y1
4.3 NNAIDA20 D2-Y1
4.4 NNAIDA19 D3-Y1
5.1 NNAIDA12 D4-Y1
5.2 NNAIDA11 D5-Y1
5.3 NNAIDA3 veto-Y1
5.4 NNAIDA4 D6-Y1
6.1 NNAIDA25 D1-X1
6.2 NNAIDA17 D3-X1
6.3 NNAIDA18 D2-X1
6.4 NNAIDA26 -
8.1 NNAIDA29 -
8.2 NNAIDA30 D1-X2
8.3 NNAIDA22 D2-X2
8.4 NNAIDA21 D3-X2
9.1 NNAIDA15 D4-Y2
9.2 NNAIDA16 D5-Y2
9.3 NNAIDA7 D6-Y2
9.4 NNAIDA8 veto-Y2
10.1 NNAIDA1 veto-X1
10.2 NNAIDA9 D5-X1
10.3 NNAIDA10 D4-X1
10.4 NNAIDA2 D6-X1
11.1 NNAIDA23 D2-Y2
11.2 NNAIDA32 D1-Y2
11.3 NNAIDA31 -
11.4 NNAIDA24 D3-Y2
MACB modules are labeled, from left to right, according to their position in the NIM crate.
D1 is the most upstream DSSD, and veto the most downstream one. |
|
Wed May 11 05:49:51 2016, AE, VHDL update to FEE_GF_Feb16_16
|
The firmware of all FEEs was updated to the version in FEE_GF_Feb16_16.bin (https://elog.ph.ed.ac.uk/AIDA/215).
This provides a 25 MHz clock output from MACB, plus a manual reset request signal.
Attached are screen captures from smooth updating procedure.
Checked correlation request signal from output2 of MACB: it's a pulse with ~180ns width and -0.7V. We could only
observe it when selecting 'act no all FEEs' in Correlation Control browser window (looking at MACB module on the
top of the tree). However, we didn't check that the output is produced from only one MACB module, if we select
the one of the corresponding FEE. |
|
Tue May 10 16:03:50 2016, TD & VFEP, Latest version of Rly16
|
Do not forget to backup the current versions of the attached files before
installing the latest versions. The latest version features the sequential
power up of each of the eight mains relays - this will help minimise instantaneous
network loads during power/boot up.
On 05/05/2016 06:45, Thomas Davinson wrote:
Hello
Coould we have a copy of the latest USB power replay .tml file please?
Our current version does not permit sequential power on and Patrick says
that may be helpful when attempting to start 32 FEEs.
attached
=> /MIDAS/TclHttpd/Aida/Rly16
Vic |
|
Mon May 9 16:46:30 2016, Patrick, Update for FEE64 VHDL and Correlation browser windows
|
| The attached VHDL file should be saved to /MIDAS/Aida and the FlashPgm.csh file edited to load "FEE_GF_Feb16_16.bin"
Use the Run Control Expert command to update the firmware on all the FEE64s.
Power cycle the FEE64s.
This will give a 25Mhz clock from the MACB Fast NIM output 0.
The attached .js and .tml files will change the Control browser window to allow access to a Correlation control window.
I have already installed the Correlation directory and files on aidas.
The Correlation Control window has two extra buttons. One to cause a Correlation trigger and the other to cause a reset to be sent out.
The Reset is only sent out if the Run Control is in the GO state.
To complete the change first make backup copies of the Aida.js and Aida.tml files that are currently in /MIDAS/TclHttpd/Html/AIDA
then copy the attached new versions into /MIDAS/TclHttpd/Html/AIDA.
These two files are in the attached .zip file. The Elog didn't like the .js file extension.
The Browser window reload should work but it may be required to clean your browser history to ensure the new version of the file is used. |
|
Thu May 5 14:44:48 2016, Patrick, Trigger selection explanations
|
Please request more information if the attached is not clear. |
|
Thu May 5 11:10:36 2016, CG,PV,TD, Thursday 5 May 2016 8x
|
Detector configuration - see https://elog.ph.ed.ac.uk/AIDA/193
Ribbon cable to nnaida19 FEE adaptor PCB disconnected due to noise issues
associated with nnaida19 or crate slot or power/timestamp/network cabling
to nnaida19 - to be investigated May 22-
207Bi source ~3cm upstream of DSSSD #1
rate and hit rate spectra for all FEE64s - see attachments 1-4
example ADC spectra for all FEE64s - attachment 5 p+n strips, attachment 6 n+n strips
Default ASIC settings, shaping time 8us (which may, or may not, be optimum - to be
investigated May 22- )
p+n junction strips n+n ohmic strips
FEE64 Pulser peak width FEE64 Pulser peak width
(ch FWHM) (ch FWHM)
1 108 3 88
2 64 4 84
5 112 7 76
6 - 8 85
9 75 11 122
10 82 12 98
13 84 15 127
14 99 16 115
17 77 19 ?
18 69 20 100
21 77 23 89
22 91 24 84
25 80 27 138
26 14 28 16 } not connected to DSSSD
29 17 31 17 }
30 130 32 111
DSSSD bias voltages and leakage currents - attachments 7-8
All bias voltages +100V cf. depletion ~70V for 3058 sequence (MSL type BB18)
Additional bias may be helpful (to be investigated May 22-) |
|
Thu May 5 09:52:20 2016, TD, MERGE test OK 7x
|
Slow comparator 0x10 -> 0x20
Fast comparator LEC/MEC 0x10 -> 0xff
To start DAQ
1) open disk file with tapeserver
2) merge
select data links 0-31
setup & go
start
toggle merge data transfer state (xfer enabled)
toggle merge program pause state (paused)
3) enable #1 all *only*
DAQ GO
4) statistics
check all FEEs producing AIDA SYNC
5) merge
reload (several times over period of ~10s) to check all data links active (green)
toggle merge program pause state (merging)
reload (several times over period of ~10s) to check non-zero merged data rate
6) tapeserver
reload to check data transfer
7) observe spinners in merger and tapeserver server terminal windows
To stop DAQ
1) DAQ STOP
2) toggle merge program pause state (paused)
3) stop disk file with tapeserver
To restart
1) open disk file with tapeserver
2) DAQ GO
5) merge
reload (several times over period of ~10s) to check all data links active (green)
toggle merge program pause state (merging)
reload (several times over period of ~10s) to check non-zero merged data rate
etc
DAQ/merge/tapeserver test OK
Server terminal session logs and screenshots appended
Custom startup from /MIDAS@aidas/config/TclHttpd/aidas1@8115/startup.tcl
/TapeServer
/DataBaseAccessServer
Loaded MemSasAccess
/SpectrumService
/NetVarService
/SigTaskService
loading tcl/MERGERunControl.tcl for namespace ::
/DataAcquisitionControlServer
DefineMessage unknown
Run Control Server Implementation for MERGE
RunControlServer loaded
loading Html/RunControl/implementation.tcl for namespace ::
RunControl loaded
loading Html/MERGE/RunControl/implementation.tcl for namespace ::
ReadRegister failed: Name=NetVar.EXEC.ID; Code= 0x10004; Info= Register name does not exist
created SigTask registers 0 0 0 0
Created UI registers
MERGE RunControl loaded
Completed custom startup from /MIDAS@aidas/TclHttpd/Html/MERGE/RunControl/stats.defn.tcl
Shared memory area located at 0x7f35b6609000
Tape Server comms table located at 0x7f35b6609000
setup Merge
DataAcqCommand 1 Halt
Halt (1)
DataAcqCommand 8 Unmapping spectra
Unmapping spectra (1)
DataAcqCommand 3 Setup
Setup (1)
go Merge
DataAcqCommand 2 Go
Go (1)
DataAcqCommand 16 MergeStart
MergeStart (1)
DataAcqCommand 17 MergePause
MergePause (1)
DataAcqCommand 17 MergePause
MergePause (1)
stop Merge
DataAcqCommand 17 MergePause
MergePause (1)
DataAcqCommand 1 Halt
Halt (1)
setup Merge
DataAcqCommand 1 Halt
Halt (1)
DataAcqCommand 8 Unmapping spectra
Unmapping spectra (1)
DataAcqCommand 3 Setup
Setup (1)
go Merge
DataAcqCommand 2 Go
Go (1)
DataAcqCommand 16 MergeStart
MergeStart (1)
DataAcqCommand 17 MergePause
MergePause (1)
DataAcqCommand 17 MergePause
MergePause (1)
MERGE Data Link (4469): accepted connection from 10.1.1.21, port 47760
MERGE Data Link (4473): buffer size changed to 65536
MERGE Data Link (4469): buffer size changed to 65536
MERGE Data Link (4467): accepted connection from 10.1.2.19, port 35051
MERGE Data Link (4467): buffer size changed to 65536
MERGE Data Link (4461): data_transfer - data received for link 12
MERGE Data Link (4471): accepted connection from 10.1.2.23, port 39835
MERGE Data Link (4471): buffer size changed to 65536
MERGE Data Link (4475): accepted connection from 10.1.2.27, port 41369
MERGE Data Link (4475): buffer size changed to 65536
MERGE Data Link (4480): accepted connection from 10.1.2.32, port 33003
MERGE Data Link (4477): accepted connection from 10.1.1.29, port 47070
MERGE Data Link (4480): buffer size changed to 65536
MERGE Data Link (4477): buffer size changed to 65536
MERGE Data Link (4478): accepted connection from 10.1.1.30, port 51732
MERGE Data Link (4478): buffer size changed to 65536
MERGE Data Link (4460): data_transfer - data received for link 11
MERGE Data Link (4459): data_transfer - data received for link 10
MERGE Data Link (4454): data_transfer - data received for link 5
MERGE Data Link (4476): accepted connection from 10.1.2.28, port 43974
MERGE Data Link (4476): buffer size changed to 65536
MERGE Data Link (4465): data_transfer - data received for link 16
MERGE Data Link (4479): accepted connection from 10.1.2.31, port 46899
MERGE Data Link (4479): buffer size changed to 65536
MERGE Data Link (4474): accepted connection from 10.1.1.26, port 34630
MERGE Data Link (4474): buffer size changed to 65536
MERGE Data Link (4463): data_transfer - data received for link 14
MERGE Data Link (4464): data_transfer - data received for link 15
MERGE Data Link (4462): data_transfer - data received for link 13
MERGE Data Link (4466): data_transfer - data received for link 17
MERGE Data Link (4470): data_transfer - data received for link 21
MERGE Data Link (4472): data_transfer - data received for link 23
MERGE Data Link (4468): data_transfer - data received for link 19
MERGE Data Link (4473): data_transfer - data received for link 24
MERGE Data Link (4469): data_transfer - data received for link 20
MERGE Data Link (4471): data_transfer - data received for link 22
MERGE Data Link (4467): data_transfer - data received for link 18
MERGE Data Link (4480): data_transfer - data received for link 31
MERGE Data Link (4475): data_transfer - data received for link 26
MERGE Data Link (4478): data_transfer - data received for link 29
MERGE Data Link (4477): data_transfer - data received for link 28
MERGE Data Link (4479): data_transfer - data received for link 30
MERGE Data Link (4476): data_transfer - data received for link 27
MERGE Data Link (4474): data_transfer - data received for link 25
Merge: Restarting from timestamp 1 or greater
MERGE Data Link (4449): client closed connection
MERGE Data Link (4449): listening on port 11001
MERGE Data Link (4452): client closed connection
MERGE Data Link (4452): listening on port 11004
MERGE Data Link (4455): client closed connection
MERGE Data Link (4455): listening on port 11007
MERGE Data Link (4450): client closed connection
MERGE Data Link (4450): listening on port 11002
MERGE Data Link (4451): client closed connection
MERGE Data Link (4451): listening on port 11003
MERGE Data Link (4456): client closed connection
MERGE Data Link (4456): listening on port 11008
MERGE Data Link (4453): client closed connection
MERGE Data Link (4453): listening on port 11005
MERGE Data Link (4457): client closed connection
MERGE Data Link (4457): listening on port 11009
MERGE Data Link (4454): client closed connection
MERGE Data Link (4454): listening on port 11006
MERGE Data Link (4458): client closed connection
MERGE Data Link (4458): listening on port 11010
MERGE Data Link (4461): client closed connection
MERGE Data Link (4461): listening on port 11013
MERGE Data Link (4459): client closed connection
MERGE Data Link (4459): listening on port 11011
MERGE Data Link (4460): client closed connection
MERGE Data Link (4460): listening on port 11012
MERGE Data Link (4465): client closed connection
MERGE Data Link (4465): listening on port 11017
MERGE Data Link (4464): client closed connection
MERGE Data Link (4464): listening on port 11016
MERGE Data Link (4462): client closed connection
MERGE Data Link (4462): listening on port 11014
MERGE Data Link (4463): client closed connection
MERGE Data Link (4463): listening on port 11015
MERGE Data Link (4466): client closed connection
MERGE Data Link (4466): listening on port 11018
MERGE Data Link (4467): client closed connection
MERGE Data Link (4467): listening on port 11019
MERGE Data Link (4468): client closed connection
MERGE Data Link (4468): listening on port 11020
MERGE Data Link (4469): client closed connection
MERGE Data Link (4469): listening on port 11021
MERGE Data Link (4472): client closed connection
MERGE Data Link (4472): listening on port 11024
MERGE Data Link (4470): client closed connection
MERGE Data Link (4470): listening on port 11022
MERGE Data Link (4473): client closed connection
MERGE Data Link (4473): listening on port 11025
MERGE Data Link (4471): client closed connection
MERGE Data Link (4471): listening on port 11023
MERGE Data Link (4480): client closed connection
MERGE Data Link (4480): listening on port 11032
MERGE Data Link (4477): client closed connection
MERGE Data Link (4477): listening on port 11029
MERGE Data Link (4476): client closed connection
MERGE Data Link (4476): listening on port 11028
MERGE Data Link (4479): client closed connection
MERGE Data Link (4479): listening on port 11031
MERGE Data Link (4478): client closed connection
MERGE Data Link (4478): listening on port 11030
MERGE Data Link (4475): client closed connection
MERGE Data Link (4475): listening on port 11027
MERGE Data Link (4474): client closed connection
MERGE Data Link (4474): listening on port 11026
Merge state now Paused
Merge state now Stopped
Merge: debugging initialised: off.
Event Buffer virtual address: 0x2602c50
Merge: initialising for 32 links: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28
29 30 31
Link Data buffer 0 (Link0), length 3932160 (0x3c0000) bytes mapped at: 0x7ff6c5974010 - 0x7ff6c5d3400f
Link Data buffer 1 (Link1), length 3932160 (0x3c0000) bytes mapped at: 0x7ff6c55b3010 - 0x7ff6c597300f
Link Data buffer 2 (Link2), length 3932160 (0x3c0000) bytes mapped at: 0x7ff6c51f2010 - 0x7ff6c55b200f
Link Data buffer 3 (Link3), length 3932160 (0x3c0000) bytes mapped at: 0x7ff6c4e31010 - 0x7ff6c51f100f
Link Data buffer 4 (Link4), length 3932160 (0x3c0000) bytes mapped at: 0x7ff6c4a70010 - 0x7ff6c4e3000f
Link Data buffer 5 (Link5), length 3932160 (0x3c0000) bytes mapped at: 0x7ff6c46af010 - 0x7ff6c4a6f00f
Link Data buffer 6 (Link6), length 3932160 (0x3c0000) bytes mapped at: 0x7ff6c42ee010 - 0x7ff6c46ae00f
Link Data buffer 7 (Link7), length 3932160 (0x3c0000) bytes mapped at: 0x7ff6c3f2d010 - 0x7ff6c42ed00f
Link Data buffer 8 (Link8), length 3932160 (0x3c0000) bytes mapped at: 0x7ff6c3b6c010 - 0x7ff6c3f2c00f
Link Data buffer 9 (Link9), length 3932160 (0x3c0000) bytes mapped at: 0x7ff6c37ab010 - 0x7ff6c3b6b00f
Link Data buffer 10 (Link10), length 3932160 (0x3c0000) bytes mapped at: 0x7ff6c33ea010 - 0x7ff6c37aa00f
Link Data buffer 11 (Link11), length 3932160 (0x3c0000) bytes mapped at: 0x7ff6c3029010 - 0x7ff6c33e900f
Link Data buffer 12 (Link12), length 3932160 (0x3c0000) bytes mapped at: 0x7ff6c2c68010 - 0x7ff6c302800f
Link Data buffer 13 (Link13), length 3932160 (0x3c0000) bytes mapped at: 0x7ff6c28a7010 - 0x7ff6c2c6700f
Link Data buffer 14 (Link14), length 3932160 (0x3c0000) bytes mapped at: 0x7ff6c24e6010 - 0x7ff6c28a600f
Link Data buffer 15 (Link15), length 3932160 (0x3c0000) bytes mapped at: 0x7ff6c2125010 - 0x7ff6c24e500f
Link Data buffer 16 (Link16), length 3932160 (0x3c0000) bytes mapped at: 0x7ff6c1d64010 - 0x7ff6c212400f
Link Data buffer 17 (Link17), length 3932160 (0x3c0000) bytes mapped at: 0x7ff6c19a3010 - 0x7ff6c1d6300f
Link Data buffer 18 (Link18), length 3932160 (0x3c0000) bytes mapped at: 0x7ff6c15e2010 - 0x7ff6c19a200f
Link Data buffer 19 (Link19), length 3932160 (0x3c0000) bytes mapped at: 0x7ff6c1221010 - 0x7ff6c15e100f
Link Data buffer 20 (Link20), length 3932160 (0x3c0000) bytes mapped at: 0x7ff6c0e60010 - 0x7ff6c122000f
Link Data buffer 21 (Link21), length 3932160 (0x3c0000) bytes mapped at: 0x7ff6c0a9f010 - 0x7ff6c0e5f00f
Link Data buffer 22 (Link22), length 3932160 (0x3c0000) bytes mapped at: 0x7ff6c06de010 - 0x7ff6c0a9e00f
Link Data buffer 23 (Link23), length 3932160 (0x3c0000) bytes mapped at: 0x7ff6c031d010 - 0x7ff6c06dd00f
Link Data buffer 24 (Link24), length 3932160 (0x3c0000) bytes mapped at: 0x7ff6bff5c010 - 0x7ff6c031c00f
Link Data buffer 25 (Link25), length 3932160 (0x3c0000) bytes mapped at: 0x7ff6bfb9b010 - 0x7ff6bff5b00f
Link Data buffer 26 (Link26), length 3932160 (0x3c0000) bytes mapped at: 0x7ff6bf7da010 - 0x7ff6bfb9a00f
Link Data buffer 27 (Link27), length 3932160 (0x3c0000) bytes mapped at: 0x7ff6bf419010 - 0x7ff6bf7d900f
Link Data buffer 28 (Link28), length 3932160 (0x3c0000) bytes mapped at: 0x7ff6bf058010 - 0x7ff6bf41800f
Link Data buffer 29 (Link29), length 3932160 (0x3c0000) bytes mapped at: 0x7ff6bec97010 - 0x7ff6bf05700f
Link Data buffer 30 (Link30), length 3932160 (0x3c0000) bytes mapped at: 0x7ff6be8d6010 - 0x7ff6bec9600f
Link Data buffer 31 (Link31), length 3932160 (0x3c0000) bytes mapped at: 0x7ff6be515010 - 0x7ff6be8d500f
Queue 0 (Link0) starts at 0x7ff6c5974010
Queue 1 (Link1) starts at 0x7ff6c55b3010
Queue 2 (Link2) starts at 0x7ff6c51f2010
Queue 3 (Link3) starts at 0x7ff6c4e31010
Queue 4 (Link4) starts at 0x7ff6c4a70010
Queue 5 (Link5) starts at 0x7ff6c46af010
Queue 6 (Link6) starts at 0x7ff6c42ee010
Queue 7 (Link7) starts at 0x7ff6c3f2d010
Queue 8 (Link8) starts at 0x7ff6c3b6c010
Queue 9 (Link9) starts at 0x7ff6c37ab010
Queue 10 (Link10) starts at 0x7ff6c33ea010
Queue 11 (Link11) starts at 0x7ff6c3029010
Queue 12 (Link12) starts at 0x7ff6c2c68010
Queue 13 (Link13) starts at 0x7ff6c28a7010
Queue 14 (Link14) starts at 0x7ff6c24e6010
Queue 15 (Link15) starts at 0x7ff6c2125010
Queue 16 (Link16) starts at 0x7ff6c1d64010
Queue 17 (Link17) starts at 0x7ff6c19a3010
Queue 18 (Link18) starts at 0x7ff6c15e2010
Queue 19 (Link19) starts at 0x7ff6c1221010
Queue 20 (Link20) starts at 0x7ff6c0e60010
Queue 21 (Link21) starts at 0x7ff6c0a9f010
Queue 22 (Link22) starts at 0x7ff6c06de010
Queue 23 (Link23) starts at 0x7ff6c031d010
Queue 24 (Link24) starts at 0x7ff6bff5c010
Queue 25 (Link25) starts at 0x7ff6bfb9b010
Queue 26 (Link26) starts at 0x7ff6bf7da010
Queue 27 (Link27) starts at 0x7ff6bf419010
Queue 28 (Link28) starts at 0x7ff6bf058010
Queue 29 (Link29) starts at 0x7ff6bec97010
Queue 30 (Link30) starts at 0x7ff6be8d6010
Queue 31 (Link31) starts at 0x7ff6be515010
MERGE Merge setup complete
Merge state now Going
Merge: Searching for timestamp 0 or greater
TCP transfer library version 3.12
TCP socket send buffer was 16384 - now 249856
TCP socket receive buffer was 87380 - now 249856
TCP socket created OK - now connecting to localhost port 10305
Connected to localhost port 10305
Merge state now Paused
MERGE Data Link (4450): accepted connection from 10.1.1.2, port 33272
MERGE Data Link (4450): buffer size changed to 65536
MERGE Data Link (4449): accepted connection from 10.1.1.1, port 44572
MERGE Data Link (4449): buffer size changed to 65536
MERGE Data Link (4451): accepted connection from 10.1.2.3, port 41720
MERGE Data Link (4451): buffer size changed to 65536
MERGE Data Link (4457): accepted connection from 10.1.1.9, port 58755
MERGE Data Link (4457): buffer size changed to 65536
MERGE Data Link (4452): accepted connection from 10.1.2.4, port 44539
MERGE Data Link (4452): buffer size changed to 65536
MERGE Data Link (4456): accepted connection from 10.1.2.8, port 58367
MERGE Data Link (4456): buffer size changed to 65536
MERGE Data Link (4455): accepted connection from 10.1.2.7, port 35016
MERGE Data Link (4458): accepted connection from 10.1.1.10, port 37593
MERGE Data Link (4455): buffer size changed to 65536
MERGE Data Link (4458): buffer size changed to 65536
MERGE Data Link (4460): accepted connection from 10.1.2.12, port 43714
MERGE Data Link (4460): buffer size changed to 65536
MERGE Data Link (4454): accepted connection from 10.1.1.6, port 39318
MERGE Data Link (4454): buffer size changed to 65536
MERGE Data Link (4463): accepted connection from 10.1.2.15, port 46057
MERGE Data Link (4463): buffer size changed to 65536
MERGE Data Link (4461): accepted connection from 10.1.1.13, port 59797
MERGE Data Link (4461): buffer size changed to 65536
MERGE Data Link (4466): accepted connection from 10.1.1.18, port 45269
MERGE Data Link (4466): buffer size changed to 65536
MERGE Data Link (4468): accepted connection from 10.1.2.20, port 39429
MERGE Data Link (4468): buffer size changed to 65536
MERGE Data Link (4459): accepted connection from 10.1.2.11, port 40296
MERGE Data Link (4459): buffer size changed to 65536
MERGE Data Link (4453): accepted connection from 10.1.1.5, port 39444
MERGE Data Link (4453): buffer size changed to 65536
MERGE Data Link (4462): accepted connection from 10.1.1.14, port 51022
MERGE Data Link (4462): buffer size changed to 65536
MERGE Data Link (4472): accepted connection from 10.1.2.24, port 51137
MERGE Data Link (4472): buffer size changed to 65536
MERGE Data Link (4470): accepted connection from 10.1.1.22, port 51868
MERGE Data Link (4470): buffer size changed to 65536
MERGE Data Link (4464): accepted connection from 10.1.2.16, port 42981
MERGE Data Link (4465): accepted connection from 10.1.1.17, port 49966
MERGE Data Link (4464): buffer size changed to 65536
MERGE Data Link (4465): buffer size changed to 65536
MERGE Data Link (4473): accepted connection from 10.1.1.25, port 33551
MERGE Data Link (4473): buffer size changed to 65536
MERGE Data Link (4467): accepted connection from 10.1.2.19, port 49975
MERGE Data Link (4467): buffer size changed to 65536
MERGE Data Link (4471): accepted connection from 10.1.2.23, port 36808
MERGE Data Link (4471): buffer size changed to 65536
MERGE Data Link (4469): accepted connection from 10.1.1.21, port 51687
MERGE Data Link (4469): buffer size changed to 65536
MERGE Data Link (4477): accepted connection from 10.1.1.29, port 53480
MERGE Data Link (4478): accepted connection from 10.1.1.30, port 32906
MERGE Data Link (4478): buffer size changed to 65536
MERGE Data Link (4477): buffer size changed to 65536
MERGE Data Link (4480): accepted connection from 10.1.2.32, port 42651
MERGE Data Link (4480): buffer size changed to 65536
MERGE Data Link (4476): accepted connection from 10.1.2.28, port 58374
MERGE Data Link (4476): buffer size changed to 65536
MERGE Data Link (4474): accepted connection from 10.1.1.26, port 52835
MERGE Data Link (4474): buffer size changed to 65536
MERGE Data Link (4479): accepted connection from 10.1.2.31, port 42097
MERGE Data Link (4479): buffer size changed to 65536
MERGE Data Link (4475): accepted connection from 10.1.2.27, port 36452
MERGE Data Link (4475): buffer size changed to 65536
Merge: Restarting from timestamp 1 or greater
Merge: Starting at timestamp 221552400a0
MERGE Data Link (4450): client closed connection
MERGE Data Link (4450): listening on port 11002
MERGE Data Link (4449): client closed connection
MERGE Data Link (4449): listening on port 11001
MERGE Data Link (4451): client closed connection
MERGE Data Link (4451): listening on port 11003
MERGE Data Link (4452): client closed connection
MERGE Data Link (4452): listening on port 11004
MERGE Data Link (4457): client closed connection
MERGE Data Link (4457): listening on port 11009
MERGE Data Link (4454): client closed connection
MERGE Data Link (4454): listening on port 11006
MERGE Data Link (4456): client closed connection
MERGE Data Link (4456): listening on port 11008
MERGE Data Link (4455): client closed connection
MERGE Data Link (4455): listening on port 11007
MERGE Data Link (4458): client closed connection
MERGE Data Link (4458): listening on port 11010
MERGE Data Link (4460): client closed connection
MERGE Data Link (4460): listening on port 11012
MERGE Data Link (4463): client closed connection
MERGE Data Link (4463): listening on port 11015
MERGE Data Link (4453): client closed connection
MERGE Data Link (4453): listening on port 11005
MERGE Data Link (4459): client closed connection
MERGE Data Link (4459): listening on port 11011
MERGE Data Link (4461): client closed connection
MERGE Data Link (4461): listening on port 11013
MERGE Data Link (4462): client closed connection
MERGE Data Link (4462): listening on port 11014
MERGE Data Link (4464): client closed connection
MERGE Data Link (4464): listening on port 11016
MERGE Data Link (4466): client closed connection
MERGE Data Link (4466): listening on port 11018
MERGE Data Link (4468): client closed connection
MERGE Data Link (4468): listening on port 11020
MERGE Data Link (4467): client closed connection
MERGE Data Link (4467): listening on port 11019
MERGE Data Link (4465): client closed connection
MERGE Data Link (4465): listening on port 11017
MERGE Data Link (4470): client closed connection
MERGE Data Link (4470): listening on port 11022
MERGE Data Link (4471): client closed connection
MERGE Data Link (4471): listening on port 11023
MERGE Data Link (4469): client closed connection
MERGE Data Link (4469): listening on port 11021
MERGE Data Link (4473): client closed connection
MERGE Data Link (4473): listening on port 11025
MERGE Data Link (4472): client closed connection
MERGE Data Link (4472): listening on port 11024
MERGE Data Link (4474): client closed connection
MERGE Data Link (4474): listening on port 11026
MERGE Data Link (4478): client closed connection
MERGE Data Link (4478): listening on port 11030
MERGE Data Link (4477): client closed connection
MERGE Data Link (4477): listening on port 11029
MERGE Data Link (4476): client closed connection
MERGE Data Link (4476): listening on port 11028
MERGE Data Link (4475): client closed connection
MERGE Data Link (4475): listening on port 11027
MERGE Data Link (4480): client closed connection
MERGE Data Link (4480): listening on port 11032
MERGE Data Link (4479): client closed connection
MERGE Data Link (4479): listening on port 11031
Merge state now Paused
Tidy up
master(3162): Operation not permitted
master: no process killed
stats: no process killed
driver: no process killed
linkTCP: no process killed
Starting Tape Server
MIDAS Tape Server: Message logger not contacted.
MIDAS Tape Server: MIDAS Tape Server Build February 14 2014
MIDAS Tape Server: Unable to change scheduling priority - Permission denied
MIDAS Tape Server: Using default startup
MIDAS Tape Server: Configuration: UDP port = 10205, SHM key=10205.
MIDAS Tape Server: File mapped object /SHM_10205 of size 1331104 created
MIDAS Tape Server: Shared memory ID is 3
MIDAS Tape Server: Shared memory segment located at address 7fbd51737000.
MIDAS Tape Server: Configuration file used - /MIDAS/TapeServer/Linux64/TS_configuration
MIDAS Tape Server: Stats task ./stats
MIDAS Tape Server: Using device file /dev/file/0 ./driver
MIDAS Tape Server: Using device sink /dev/null/0 ./driver
MIDAS Tape Server: Data link ./linkTCP
MIDAS Tape Server: Message reporting level = 0x180fff8
MIDAS Tape Server: Message logging level = 0xfff8
MIDAS Tape Server: Tape Server Options = 0x6
MIDAS Tape Server: File device path base = /TapeData
MIDAS Tape Server: Data buffer size = 65536
MIDAS Tape Server: Tape block size = 65536
MIDAS Tape Server: File mapped object /SHM_110205 of size 4195880 created
MIDAS Tape Server: Shared memory ID is 3
MIDAS Tape Server: Shared memory segment located at address 7fbd51336000.
MIDAS Tape Server: File mapped object /SHM_210205 of size 3100 created
MIDAS Tape Server: Shared memory ID is 3
MIDAS Tape Server: Shared memory segment located at address 7fbd51898000.
MIDAS Tape Server: Capabilities restored.
MIDAS Tape Server: Master global area initialised.
MIDAS Tape Server: Stats task has pid 4522
MIDAS Tape Server: Driver process for /dev/file/0 has pid 4523
MIDAS Tape Server: Driver process for /dev/null/0 has pid 4524
MIDAS Tape Server: Link task 0 has pid 4525
MIDAS Tape Server: Starting the RPC interface
MIDAS Tape Statistics: Message logger not contacted.
MIDAS Tape Statistics: MIDAS Tape Statistics Build February 14 2014
MIDAS Tape Statistics: Started with args 10205
MIDAS Tape Statistics: Configuration: SHM key=10205
MIDAS Tape Statistics: File mapped object /SHM_10205 of size 1331104 created
MIDAS Tape Statistics: Shared memory ID is 3
MIDAS Tape Statistics: Shared memory segment located at address 7f0f7088e000.
MIDAS Data Link (4525): Message logger not contacted.
MIDAS Data Link (4525): MIDAS Tape Data Link Build February 14 2014
MIDAS Data Link (4525): Started with args 10205
MIDAS Data Link (4525): Configuration: SHM key=10205, TCP port = 10305
MIDAS Data Link (4525): File mapped object /SHM_10205 of size 1331104 created
MIDAS Data Link (4525): Shared memory ID is 3
MIDAS Data Link (4525): Shared memory segment located at address 7fecd723a000.
MIDAS Data Link (4525): Starting the network interface
MIDAS Data Link (4525): TCP socket receive buffer was 87380 - now 249856
MIDAS Data Link (4525): TCP socket send buffer was 16384 - now 249856
MIDAS Data Link (4525): MIDAS Data Link thread 0 using TCP port 10305.
MIDAS Data Link (4525): Entering server loop
MIDAS Data Link (4525): thread 0 listening on port 10305
MIDAS Tape Server: Created RPC Program 28000205 Version 4 on UDP port 10205.
MIDAS Tape Server: Entering server loop
MIDAS Tape Server: MIDAS Tape Server now available on UDP port 10205.
MIDAS Tape Driver (4523): Message logger not contacted.
MIDAS Tape Driver (4523): MIDAS Tape Driver Build February 14 2014
MIDAS Tape Driver (4523): Started with args 0 10205
MIDAS Tape Driver (4523): Configuration: driver=0, key=10205.
MIDAS Tape Driver (4523): File mapped object /SHM_10205 of size 1331104 created
MIDAS Tape Driver (4523): Shared memory ID is 3
MIDAS Tape Driver (4523): Shared memory segment located at address 7f6c9a83f000.
MIDAS Tape Driver (4523): Using device /dev/file/0 of type file.
MIDAS Tape Driver (4524): Message logger not contacted.
MIDAS Tape Driver (4524): MIDAS Tape Driver Build February 14 2014
MIDAS Tape Driver (4524): Started with args 1 10205
MIDAS Tape Driver (4524): Configuration: driver=1, key=10205.
MIDAS Tape Driver (4524): File mapped object /SHM_10205 of size 1331104 created
MIDAS Tape Driver (4524): Shared memory ID is 3
MIDAS Tape Driver (4524): Shared memory segment located at address 7fcfa0949000.
MIDAS Tape Driver (4524): Using device /dev/null/0 of type sink.
MIDAS Tape Server: Capability 000692d95729f724 issued.
TapeServer: f_int: No such file or directory
Error 2 in f_int - No such file or directory
MIDAS Tape Driver (4523): Error 2 in f_int - No such file or directory
MIDAS Tape Server: Capability 000430285729f765 issued.
TapeServer: f_int: No such file or directory
Error 2 in f_int - No such file or directory
MIDAS Tape Driver (4523): Error 2 in f_int - No such file or directory
MIDAS Tape Server: Capability 00077f1a5729fc25 issued.
MIDAS Tape Server: device /dev/file/0 allocated.
MIDAS Tape Server: Mounting volume NULL on device /dev/file/0.
TapeServer: f_int: Permission denied
Error 13 in f_int - Permission denied
MIDAS Tape Driver (4523): Error 13 in f_int - Permission denied
MIDAS Tape Server: Capability 77f1a5729fc25 released.
MIDAS Tape Server: Capability 000ad90b5729fc58 issued.
MIDAS Tape Server: Mounting volume NULL on device /dev/file/0.
MIDAS Tape Server: Opening file R1 on device /dev/file/0.
MIDAS Tape Server: Closing file on device /dev/file/0.
MIDAS Tape Server: Dismounted volume on device /dev/file/0.
MIDAS Tape Server: Mounting volume NULL on device /dev/file/0.
MIDAS Tape Server: Opening file R2 on device /dev/file/0.
MIDAS Data Link (4525): thread 0 accepted connection from 127.0.0.1, port 34620
MIDAS Data Link (4525): buffer size changed to 65536
MIDAS Tape Server: Closing file on device /dev/file/0.
MIDAS Tape Server: Dismounted volume on device /dev/file/0. |
|
Thu May 5 08:47:49 2016, TD, [How To] Mask Fast Discriminators
|
From the 'AIDA Control' tab select 'Discriminator control'
From the 'Discriminator controls' tab
select 'Reload'
select FEE64 required
select (or deselect) 'Act on ALL FEE64 modules?' as required
select ASIC channel(s) to mask
The current default value (set by AIDA Settings) is 0x0 (no fast discriminator masks defined)
ASIC channels commonly masked include #2 (AS0 01) and #55 (AS3 06) |
|
Thu May 5 08:30:00 2016, TD, [How To] Set MACB Trigger Output Mode
|
From the 'AIDA Control' tab select 'Local Controls'
From the 'LOCAL controls' tab
select 'Reload'
select FEE64 required
select (or deselect) 'Act on ALL FEE64 modules?' as required
enter 'Trigger O/P control register' value required
The current default value (set by AIDA Options) is 0xe (logic 0) |
|
Thu May 5 08:12:14 2016, TD, Current AIDA settings and options
|
Current AIDA settings DB Key: 2016May03-20.44.33
Current AIDA settings directory: /MIDAS/DB/EXPERIMENTS/AIDA/2016May03-20.44.33
Default ASIC settings *except*
Input Polarity
Positive Negative
preAmp reference 0x20 -> 0x30
diode link threshold 0xca -> 0xbf 0x11 -> 0x23
slow comparator 0x10
fast comparator HEC 0x2
fast comparator LEC/MEC 0x10
Shaping time 8us with appropriate reset/hold timings
AIDA options directory: /MIDAS/DB/EXPERIMENTS/AIDA/Options
See attachment 1 |
|