We are running an MBS DAQ to record the attached list of slow control values of the ring and the target. In most cases this is achieved by converting analog monitor voltages to frequencies and recording them with a VME scaler (VULOM4B with scaler-firmware). The complete list of signals is attached including a channel mapping.
!! Target values are currently not provided, we can only record ring/cooler values !!
We do a scaler readout with a 1Hz trigger rate right now. This can be changed. This generates events with trigger number 1.
Additionally, we receive triggers from motor movement (trigger 2 & trigger 3) and from target ON and target OFF (trigger 12 & trigger 13).
Each event of any trigger type is WR timestamped.
There is also a Go4 configured for online monitoring.
Details below. Or contact Jan Glorius.
----------------------------------------
Basic info and how-to for MBS
----------------------------------------
linux-user: cry_exp
VME CPU: r4l-58
DAQ PC: atppc025
data storage: lxg1275:/data.local2/2024_CRYRING_16O_jet
The DAQ is running in a screen session "target_DAQ" on atppc025. Enter by typing
> screen -x "target_DAQ"
SSH connections to r4l-58 are active in tabs 0 and 1. Type [ctrl]+[a] then [x] to switch to tab x.
If the SSH connection is lost type
> ssh cry_exp@r4l-58
> cd /esr/usr/cry_exp/2024_CRYRING_jet/mbs
MBS is running in tab 1. If it has an error, type [ctrl]+[z] to exit MBS, then
> resl
> mbs
mbs> @startup
mbs> @connect
to start a new file recording type
mbs> @runstart
If an error occures during @runstart, try @connect again.
Inside MBS you monitoring options:
mbs> show acq (will show you trigger and data rates and status)
mbs> show file (will show you the file status)
mbs> type ev -v 10 (will display 10 subsequent events from the data stream)
The trigger rate is currently 1Hz.
The trigger logic and setup in configured in /esr/usr/cry_exp/2024_CRYRING_jet/mbs/jet.trlo
-----------------------
Go4 monitoring
-----------------------
Go4 is running on atppc025 in the directory /u/cry_exp/Beamtimes/202402_O2+/go4_target
From this directory you can run it by typing
> go4 monitoring.hotstart
|