From de16c2a7f1b374cbd3e65b712d8dcfd4ea345b7d Mon Sep 17 00:00:00 2001 From: Gemma Tinti Date: Mon, 20 Mar 2017 12:42:28 +0100 Subject: [PATCH] manual --- manual/manual-client/Eiger_short.tex | 36 ++++++++++++++++++---------- 1 file changed, 23 insertions(+), 13 deletions(-) diff --git a/manual/manual-client/Eiger_short.tex b/manual/manual-client/Eiger_short.tex index 4a92a8d58..f11d81d5b 100644 --- a/manual/manual-client/Eiger_short.tex +++ b/manual/manual-client/Eiger_short.tex @@ -261,7 +261,7 @@ sls_detector_put 0-subexptime [time_in_s] One needs to realize that the readout time, for each subframe is 10.5~$\mu$s if the detector is in parallel mode. 500~$\mu$s if the detector is in non parallel mode. Note that in {\tt{dr 32}}, as the single frame readout from the chip is 500~$\mu$s, no {\tt{subexptime}}$<$500~$\mu$s can be set in {\tt{parallel}} mode. To have smaller {\tt{subexptime}}, you need the {\tt{nonparallel}} mode, although this will have a larger deadtime than the acquisition time.\\ -Online rate corrections can be activated. They are particularly useful and implemented \textbf{only} in the autosumming mode, i.e. when {\tt{dr 32}} is activated as every single subframe is corrected before summing it. To correct for rate, the subframe duration has to be known to the correction algorithm. +Online rate corrections can be activated for {\tt{dr=32, 16}}. They are particularly useful in the autosumming mode as every single subframe is corrected before summing it. To correct for rate, the subframe duration has to be known to the correction algorithm. To activate the rate corrections, one should do:\\ \begin{verbatim} sls_detector_put 0-ratecorr [tauval_in_ns] @@ -461,28 +461,38 @@ If you need to program a new kernel (only needed when told to do so): ./bcp kernel_local bebxxx:/kernel sleep 300; #or till the screen over netcat has told you Successuful \end{verbatim} - do the same for the other boards. You can program in parallel many boards, but you cannot load two bitfiles on the same board till loading and copying one process has finished. So load all left febs together, then proceed to the right febs, then the bebs. Power off completely everything. Power it on. \section{Pulsing the detector} -\begin{description} -\item [pulsechip n] sets the chip into test mode with \textit{resmat} = 0 and \textit{externalenable} =1. Pulses chip by togglying the enable n number of times. The acquire is then done with no pixel matrix reset before the acquisition. If n$=-1$, the chip will be set into normal mode. This is necessary to restore normal chip operations after the test. -\item[pulse n x y] Pulses pixel at coordinates (x,y) n number of times. -\item[pulsenmove n x y] Pulses pixel n number of times and moves relatively by x value (x axis) and y value (y axis) -\end{description} +Thre are two ways to pulse the detector: +\begin{itemize} +\item \textbf{Pulse digitally:} when you are interested to the output readout and do not care about the analog response from the pixels: + \begin{verbatim} +sls_detector_put vthreshold 4000 +sls_detector_put vtr 4000 +sls_detector_put pulsechip N #to pulse N +sls_detector_put pulsechip -1 #to get out of testing mode +\end{verbatim} +Note that the answer will be $2 \cdot \textrm{{\tt{N}}} +2$ in this case. -Analog pulsing {\tt{N}} counts in the whole detector: -\begin{verbatim} -for i in $(seq 0 7) ; do -px=$((-255+i)) -sls_detector_put pulse 0 $px 0 +\item \textbf{Pulse analogically:} You want to really check the analogical part of the detcetor, not just the readout. + + \begin{verbatim} +sls_detector_put vcall 3600 +sls_detector_put vthreshold 1700 +sls_detector_put vrf 3100 +for i in $(seq 0 7) ; +do px=$((-255+i)); +sls_detector_put pulse 0 $px 0; for j in $(seq 0 255) ; do -sls_detector_put pulsenmove N 0 1 +sls_detector_put pulsenmove N 0 1; done; done; sls_detector_p resmat 0 sls_detector_acquire \end{verbatim} +You read {\tt{N}} in every pixel if you are setup correctly. +\end{itemize} \section{Running the (9M at cSAXS. For now)}