added information for first time users, mt

diff --git a/intro_hints.tex b/intro_hints.tex
index 0f873af7cdc7ba831443d58e388e6e8eaf656c60..262913c46cb338a8deab1417f55ebb0c5eb765ad 100644 (file)
--- a/intro_hints.tex
+++ b/intro_hints.tex
@@ -3,13 +3,26 @@ Just some quick notes from a first user perspectives.
 \begin{itemize*}
 \item The thresholds can either be set by the \verb!padiwa.pl! script
   in the daqtools repository or via the web frontend (choose Padiwa
-  SPI and set the reference to 3300 mV). There's also some script
+  SPI and set the reference to 3300 mV). There's also a script
   which sets the thresholds automatically, see folder \verb!thresholds!.
-\item Due to the somewhat special design, it is expected behaviour
-  that you see no counts for very low thresholds, then some noise at
-  about the bias voltage ($\approx1.7\,\text{V}$) and then again no
-  counts at very high thresholds. The Board is designed for negative
-  input peaks, but positive could also work.
+\item People are sometimes confused about the pinout of the Padiwa3. Check the
+  schematics of the Padiwa3 and realize that GND and signal are alternating on
+  the connector. So, you can rotate a Padiwa3 by 180° around the long axis and
+  it will still work as before.
+\item Due to the somewhat special design, it is expected behaviour while
+  scanning through the threshold that you see no counts for very low
+  thresholds (<~1.3V), then some noise at about the bias voltage (which you
+  could call the pedestal) at $\approx1.7\,\text{V}$ and then again no counts at
+  very high thresholds (>~2.1V). The reason is, that the amplifier on the Padiwa3
+  has a limited drive capability and can not produce output signals above ~400mV.
+  At the pedestal you expect without external
+  noise at the input pins some 8mV band of an undefined area, where the output
+  of the Padiwa will oscillate (discriminator has no hysterysis).
+  Everything which is above this level is external noise on the cable/detector
+  and will deteriorate the result of your measurement.
+  The Board has been designed for negative input peaks, but positive also
+  work. The script \verb!automatic_threshold.pl! needs the 
+  switch \verb!--direction=1! to work for positive signals.
 \item Maybe you need to set the invert feature of the Padiwa board
   such that the TDC in the peripheral accepts the events (only events
   which are green highlighted in the Webinterface seem to be read
@@ -17,9 +30,9 @@ Just some quick notes from a first user perspectives.
   firmwares.
 \item Ensure that the TRB3 and your PaDiWa FEE share the same ground,
   otherwise the \verb!padiwa.pl! might return a random uid or
-  temperature, so your frontend is not accessible. Note that the power
-  supply ``ground'' of the TRB is NOT the same as the ground of the
-  board itself (The TRB3 components are powered over galvanically
+  temperature, so your frontend is not accessible. Note that the 48V power
+  supply ``ground'' of the TRB is *NOT* the same as the ground of the
+  board itself (the TRB3 components are powered over galvanically
   separated supplies on the board itself, again). Thus, you should
   connect your probably galvanically separated ground of the PaDiWa
   power supply with one of the four pins JGND headers of the TRB3.

diff --git a/intro_thresh.tex b/intro_thresh.tex
index af919d39c873bdc786147fb297aff75b798bf916..98db7f19cb7bd6c79050a75ee55b6a4229906c87 100644 (file)
--- a/intro_thresh.tex
+++ b/intro_thresh.tex
@@ -8,10 +8,37 @@ the baseline for FAST and SLOW channels of PaDiWa-AMPS.}
 \label{fig_fast_slow}
 \end{figure}
 
-An script to set the thresholds automatically one can find in \verb!???!. ...tobeadded
+An script to set the thresholds automatically one can find in
+\verb!~/trbsoft/daqtools/thresholds!.
+With
+\begin{verbatim}
+./thresholds_automatic.pl --help
+\end{verbatim}
+you get the syntax. In a normal
+setup you would need to attach all cables to the input of the Padiwa but keep
+the detector signals off. The one needs to call it like this:
+\begin{verbatim}
+./thresholds_automatic.pl -e 0xc000 --chain=0 --polarity=0 --offset=100
+\end{verbatim}
+With
+\begin{verbatim}
+tail -n16 padiwa_threshold_results.log > standard_threshold.log
+\end{verbatim}
+you can save the 16 latest thresholds determined with the script and with
+\begin{verbatim}
+./write_thresholds.pl --offset=100 standard_threshold.log
+\end{verbatim}
+you can write them via you startup-script without need to determine them
+again.
 
+The following is specific information for a setup and software used in
+Mainz. Andreas Neiser is the person to contact...
 To save the thresholds one can use the pearl script in \verb!/thresholds! The
 thresholds can be saved to a file by
-typeing \verb!dump_thresholds_mainz.pl! \verb!>! \verb!filename.txt! (have a look to that script and chose the correct DAQ-chain and
+typeing
+\begin{verbatim}
+dump_thresholds_mainz.pl > filename.txt
+\end{verbatim}
+ (have a look to that script and chose the correct DAQ-chain and
 make it executable by typeing \verb!chmod! \verb!u+x!
 \verb!dump_thresholds_your_script.pl! and loaded to the padiwa by \verb!write_thresholds.pl! \verb!filename.txt!.