We now have a drasi DAQ running for our (p,g) experiments.
The RIO we have it installed right now is: r4l-58
It shall be used with the user <litv-exp>

The DAQ-controle shall be done from lxg1275 inside a SCREEN SESSION named "daq"
tab 0 >> drasi 
tab 1 >> logger
tab 2 >> rate
tab 3 >> stream server
tab 4 >> file writing (optional)

To check and control running daq:

login on lxg1275
> ssh litv-exp@lxg1275

enter screen session
> screen -x daq

DRASI
go to tab 0
> ctrl-a 0 
should be quite, no errors showing, no terminal outputs
full restart proceedure
> ssh r4l-58
> cd esrdaq_2018/r4l-58
> ./start.sh (for det. triggered daq)
> ./pulser.sh (for internal pulser trigger)
> ctrl-c (for killing daq)

LOGGER
go to tab 1
> ctrl-a 1
should be quite, no errors showing, no terminal outputs
full restart proceedure
> ssh r4l-58
> cd esrdaq_2018/r4l-58
> ./logger.sh

RATE MONITOR
go to tab 2
> ctrl-a 2
rates should update each second
"incr" should be event rate per sec 
"send" column should be reasonable value if data is written
full restart proceedure
> ssh r4l-58
> cd esrdaq_2018/r4l-58
> ./rate.sh

EMPTY STREAM SERVER
go to tab 3
> ctrl-a 3 
empty stream should be running  
number of processed events should keep increasing
you should see the number of clients connected
full restart proceedure (on lxg1275)
> empty stream://r4l-58 --server=stream:6002

WRITE A FILE
can be done by litv-exp from any lgx-machine
ROOT FILE:
> e127_unpack --stream=lxg1275 --ntuple=RAW,/data.local1/e127/pre_data/file.root
LMD FILE:
> e127_unpack --stream=lxg1275 --output=/data.local1/e127/pre_data/test.lmd
COMMENT: better use a transport server for reliable data writing: https://elog.gsi.de/esr/NucAR+lab/2

TRANSPORT SERVER
> for writing lmd files

the transport servers provided by ucesb are made for reliable data writing. This means the will not miss any
data processed by the daq, but the data taking of the daq will be limited by the writing speed.

STREAM SERVER
> for online/quick check

the stream is able to neglect events which the client cannot process fast enough. So events/data will be missing
if writing is slower than data taking. This is good for online monitors etc.

with the DRASI environment one can interact with the vulom 

Attached are all downloads available for the DT1419ET from CAEN on 29.10.19.

Using this commands i made an image of an sd card of the epics_pi_v0:

sudo dd bs=4M if=/dev/mmcblk0 | gzip > /home/litv-exp/slow_control/sd_card_backups/epics_pi_v0.gz

To make clones of the sd card use the command:

sudo gzip -dc /home/litv-exp/slow_control/sd_card_backups/epics_pi_v0.gz | dd bs=4M of=/dev/mmcblk0

This was done on astrum1 laptop (ATPNBG004).

Here is a brief description of how to change the VME hardware of an exisiting DAQ system to a new configuration.

Our DAQ folders are located in /lynx/Lynx/esr/usr/litv-exp/

The current DAQ running on a specific rio4 is always located in a subfolder named as the hostname of the rio4, e.g. r4l-58.

If you want to change the DAQ on this rio you have to change the config in this folder. Be aware, that the folder name HAS TO BE THE HOSTNAME, no exeptions are allowed! Because of this the r4l-XX folders are usually softlinks to further folders, that contain different versions of the DAQ. 
In practice this means:

1. copy the current folder (e.g. r4l-58_dev) to a new one (e.g. r4l-58_new) and make sure that the link (r4l-58) is set to your new folder (ln -s /../r4l-58_new /../r4l-58)

2. change the hardware of your VME crate and check all VME addresses

3. edit main.cfg in your new DAQ folder, see the example attached here
   - always have a BARRIER between the modules
   - make sure you get the VME addresses right (MesyTec, CAEN board specialties)
   - the order of the modules in this file from top to bottom is important for the next step!

4. edit your start.sh script and all connected scripts and config-files (trloii_setup.sh, vulom.trlo..., a dedicated entry for vulom-configuration will follow)
   - check if DAQ in running, when triggers are provided

5. set up a new unpacker
   -go to the unpacker directory /u/litv-exp/unpacker/unpackexps/ and copy the old unpacker to a new directory:  
   -> cp -r old_up new_up
   -rename the main .spec file:
   -> cd new_up
   -> mv old_up.spec new_up.spec
   -open the Makefile with editor, search and replace "old_up" by "new_up", try compiling:
   -> make clean
   -> make -j

6. configure the data structure of the unpacker
   -make sure you have all the module spec-files that you need included in "new_up.spec", check nurdlib or Hans Törnqvist/Basti Löher in case you do not have it
   -edit the "main_user_esr.spec" to include all your modules (see example attached)
   -the (geom=0x1) field of each module has to be numbered according to the module order in the main.cfg above, starting from 0x1, some modules require additional things (crate=0)
   -edit the "det_mapping.hh" to assign names and types for each channel (example attached)
   -recompile and check upacker with running data stream from the daq:
   -> make -j
   -> ./new_up --stream=r4l-58 --debug (will print only error events)

The PicoScope is currently connected by USB to the astrum1 laptop (atpnbg004.gsi.de, IP: 140.181.78.126).
The PicoScope Software is installed and can be run on this machine.
A VNC server can be used to allow remote usage of the PicoScope.

Start a VNC server:
> ssh litv-exp@atpnbg004.gsi.de
> vncserver :1
> exit

Access the VNC server by a local VNCviewer (tigerVNC):
> vncviewer atpnbg004.gsi.de:1

The control software (win10) ist linked here:
https://sf.gsi.de/f/c031d925ec844a2685a2/?dl=1

To use the ctrl binary for the vulom4 you need to find the binary in you trloii directory on the RIO4.
For 2020/21 E127 this is at
/esr/usr/litv-exp/2020_e127/trloii/trloctrl/fw_426cb99c_trlo/bin_ppc-linux_4.2.2/trlo_ctrl

An example for this DAQ is:

trlo_ctrl --addr=5 --mux-src-scalers (this shows the scaler rates for all vulom I/O)

The complete usage:
  --addr=HEX               Module address (HEX=dummy for dummy).
  --clear-setup            Set all setup to 0 (muxes to wired 0).
  --print-config[=debug]   Show configuration.
  --trig-status[=n]        Print trigger status.  (every n s.)
  --mux-src-scalers[=NAME,n,ptn,rate,limit=i,reset]
                           Dump all MUX source scalers, or per requested NAMEs.
                           Show currently active pattern (ptn, : or *).
                           Difference or (rate).  Every n s (default 1).
                           Limit to #i displays.  Reset scalers.
  --config=FILE            Load command file (to memory only).
  --call=SECTION           Execute SECTION from loaded configuration.
  --cmd="EXPR"             Execute EXPR as an command.
  --show[=setup,dest,src]  Show available setup parameters, etc.
  --tracer[=single]        Soft-scope for TRIG LMU inputs.
  --sampler=ecl-in-N|ecl-io-in-N|lemo-in-N
                           Multi-hit timer-latch (stop with Ctrl+C).
  --rec-mlatch=A,B,[diff]  Multi-hit timer-latch #A,#B,... record to stdout.
  --serial-stamp-rate      Test serial receiver rate. (Avoid with running DAQ).
  --debug[=N]              Debugging of tracer and sampler.
  --addrtest               Run VME test; address readback.
  --ramtest                Run VME test; RAM block write/read.
  --rawread:ADDROFF        Read from VULOM at given VME offset.
  --rawwrite:ADDROFF=VALUE Write to VULOM at given VME offset.

screen -S session-name -c config_file

screen -S e127 -p 0 -X stuff "^C"
screen -S e127 -p 0 -X stuff "sleep 2;./start.sh^M"
screen -S e127 -p 4 -X stuff "sleep 10; empty stream://r4l-58 --server=stream:6002^M"

stuff "^C"

stuff "top^M"

exec /usr/bin/ssh-agent xterm -g 100x20 -e "ssh-add; screen -S session-name -c config_file" &

#define R4L_58 ADDR(10, 99, 2, 39)

c_lmu_label[]

draw_header()

show_lmu()

show_lmu_line()

ser2net can be used to forward /dev/ttyUSBx or /dev/ttySx to a tcp port.
One can then use telnet for connecting.

The config has to be done in /etc/ser2net.conf

This is an example:
3333:telnet:0:/dev/ttyUSB1:9600 8DATABITS NONE 1STOPBIT

Here ttyUSB1 with the named options is forwarded to telnet port 3333 on the local machine.

You then need to start "/sbin/ser2net"
You can stop it by "sudo service ser2net stop"

This is realized on atpnuc006 now.

The vulom can be flashed via VME-bus from the RIO by using the binaries located here:
/nfs/groups/daq/usr/kurz/gsi_vme/flash/vulom/

There are subdirectories for several platforms, like
RIO4_Linux_2.6.33 (this is for our linux-RIOs)
RIO4_Linux_2.6
RIO4_Lynx
RIO3_...
IPV_...

IFC will follow soon...

The binaries needed for flashing are the following:

eraseflash <add> <slot>              
progflash  <add> <slot> <bitfile>
veriflash  <add> <slot> <bitfile>
restart    <add> <slot>

When invoked in the above order, things should work.
For 2.6.33 there are ALIASes:
vulom_erase
vulom_flash
vulom_verify
vulom_reset


The bitfiles for vulom4b are located here:

/nfs/groups/daq/usr/kurz/gsi_vme/flash/vulom/bitfiles/

Attached is the UI diagram of the new double-sided silicon strip detector (DSSD). [Micron W1, ID: 3305-9] 
It was taken during the internship of Emily Voigt and Rebanna Klawitter.

Conditons:
- DSSD in dark test chamber
- under atmosphere pressure
- no alpha source or similar

Analysis:
The current is roughly linear with voltage up to values of about 110-120V. After this point the current increases more slowly, kind of a plateau.
The comparison to an older measurement [https://elog.gsi.de/esr/E127/292] with another, identical DSSD is not fully understood. No plateau seems to reached in the range up to 150V. The currents are also significanlty higher.

Conclusion:
Save operation is possible up to 100V. 
Voltages above 100V should only be used in case of ion damage and related performance losses.

Detektor: Micron DSSD W1 ID: 3305-9
Start: 26.01.2023, 15.20
Stopp: 27.01.2023, 09.16
triple Alpha-Quelle
U_si = -100V
Daten: Lxg1275:/data.local2/2023_dssd_test/messung001.lmd

Detector: W1 3305-09 
Setup: 
- on vacuum (p=5e-5mbar)
- dark chamber
- triple alpha source

Daten: Lxg1275:/data.local2/2023_dssd_test/messung001.lmd

The resolution (sigma) is consistently below 0.5% for all strips.

dE/E = sigma/mean (root analysis)

strip dE/E
y1 0.0040
y2 0.0043
y3 0.0037
y4 0.0034
y5 0.0037
y6 0.0035
y7 0.0044
y8 0.0034
y9 0.0037
y10 0.0035
y11 0.0037
y12 0.0033
y13 0.0038
y14 0.0036
y15 0.0046
y16 0.0035

x1 0.0050
x2 0.0041
x3 0.0042
x4 0.0045
x5 0.0042
x6 0.0036
x7 0.0041
x8 0.0041
x9 0.0039
x10 0.0040
x11 0.0038
x12 0.0035
x13 0.0043
x14 0.0038
x15 0.0044
x16 0.0036

Attached is the UI diagram of the new double-sided silicon strip detector (DSSD). [Micron W1, ID: 3305-11] 

Conditons:
- DSSD in dark test chamber
- under atmosphere pressure
- no alpha source or similar

Analysis:
The current plateau extends up to about 80V. Beyond this point the current increases more rapidly with voltage.

Conclusion:
Operation between 70-80V is optimal.
Depletion voltage is 40V according to Micron.