Correct measurement of the detector trigger is described - cu

diff --git a/trb3/TdcBuildingBlocks.tex b/trb3/TdcBuildingBlocks.tex
index 95589a43fe459d744886b071b7d2099c0674a99c..7b60d4c809c858edd9e70014b4fdad400f5bad9f 100644 (file)
--- a/trb3/TdcBuildingBlocks.tex
+++ b/trb3/TdcBuildingBlocks.tex
@@ -31,7 +31,7 @@ In each TDC channel the measurement result of the fine time measurement block is
       \label{eq:tdcDeltaT}
     \end{minipage}}
   \vspace{-0.2cm}
-%   \caption{\subref{fig:tdcTimeDiff} Illustration of two time measurements and \subref{eq:tdcDeltaT} calculation of the time interval between them.}
+   \caption{\subref{fig:tdcTimeDiff} Illustration of two time measurements and \subref{eq:tdcDeltaT} calculation of the time interval between them.}
   \label{fig:tdcDeltaTime}
 \end{figure}
 

diff --git a/trb3/TdcDataFormat.tex b/trb3/TdcDataFormat.tex
index fc451336b2fb0e602fe82f3cb3392412b5042a14..06e931215b82f8426d2ddb8c249517536f9f0d71 100644 (file)
--- a/trb3/TdcDataFormat.tex
+++ b/trb3/TdcDataFormat.tex
@@ -27,9 +27,9 @@ Any word starting with the bits "001" indicates a header word from the TDC in th
 
 The trigger random code \textendash\ 8 bits \textendash\ is generated by the trbnet for each trigger in order to distinguish the trigger. It is repeated in the TDC HEADER, so data \& trigger matching can be tested.
 
-The error bits are used to indicate any error might occurred in the TDC since the last trigger. The error bits coded in the header is given in Table \ref{tab:tdcHeaderErrorBits}
+The error bits are used to indicate any error might occurred in the TDC since the last trigger. The error bits coded in the header is given in Table \ref{tab:tdcHeaderErrorBits}.
 
-\begin{table}[h]
+\begin{table}[ht]
   \centering
     \begin{tabular}{|c|l|}
       \hline
@@ -50,7 +50,7 @@ The error bits are used to indicate any error might occurred in the TDC since th
 
 The data format of the \textbf{\textit{time data}} word is shown below:
 
-\begin{table}[h]
+\begin{table}[ht]
   \centering
     \begin{tabular}{|W{0.7cm}|W{1.3cm}|W{2.18cm}|W{3.3cm}|W{0.73cm}|W{3.63cm}|}
       \hline
@@ -64,7 +64,7 @@ The data format of the \textbf{\textit{time data}} word is shown below:
 
 \begin{tabbing}
   "1" \hspace{1.5cm}\= 1 bit \hspace{0.8cm}\= Time Data marker\\
-  reserved     \> 3 bits       \> Reserved for future use\\
+  reserved     \> 2 bits       \> Reserved for future use\\
   channel no   \> 7 bits       \> 7 bits The channel number of the TDC\\
                \>              \>      “000000” is the reference channel\\
   fine time    \> 10 bits      \> The fine time value of the measurement\\
@@ -138,10 +138,7 @@ The debug words sent with DAQ can be accessed also via slow control registers (s
 \newpage
 
 \subsubsection{EPOCH Counter}
-
-As the global coarse counter has the time limit of \~10~us, a overflow counter
-(EPOCH counter) is implemented in order to increase the measurement range. The
-data format of the \textbf{\textit{EPOCH Counter}} word is shown below:
+As the global coarse counter has the time limit of $\sim$10~us, an overflow counter (EPOCH counter) is implemented in order to increase the measurement range. The data format of the \textbf{\textit{EPOCH Counter}} word is shown below:
 
 \begin{table}[h]
   \centering
@@ -155,16 +152,7 @@ data format of the \textbf{\textit{EPOCH Counter}} word is shown below:
   \label{tab:tdcEpochCounte}
 \end{table}
 
-The EPOCH counter is designed with 28 bits increasing the total
-measurement range up to \texttildelow45,8~min. For each channel an individual EPOCH
-counter is implemented and they are incremented, when the coarse counter
-wraps around. The value of the EPOCH counter is kept in a register before it
-is written in the channel memory. It is only written in the memory, if a time
-measurement takes place after the last increment of the EPOCH counter. The
-EPOCH counter word is written in the memory only once per channel for each
-increment, thus saving bandwidth. In order to be on the safe side and not
-overflow the EPOCH counter, the readout trigger frequency can be set minimum
-to 24~Hz.
+The EPOCH counter is designed with 28 bits increasing the total measurement range up to $\sim$45,8~min. For each channel an individual EPOCH counter is implemented and they are incremented, when the coarse counter wraps around. The value of the EPOCH counter is kept in a register before it is written in the channel memory. It is only written in the memory, if a time measurement takes place after the last increment of the EPOCH counter. The EPOCH counter word is written in the memory only once per channel for each increment, thus saving bandwidth. In order to be on the safe side and not overflow the EPOCH counter, the readout trigger frequency can be set minimum to 24~Hz.
 
 
 \subsubsection{RESERVED}

diff --git a/trb3/main.tex b/trb3/main.tex
index d407b405a67c7d0688a12c76215a659b69f0953b..17b9a3dfe6bd19f672a93e7316da971df6dec9fc 100755 (executable)
--- a/trb3/main.tex
+++ b/trb3/main.tex
@@ -189,6 +189,8 @@
 
 
 \part{Experimental Setups and Configurations}
+  \section{Trigger Time vs Reference Time}
+  \input{ExperimentalSetup}
 
 \input{trb3qs_part}
 

diff --git a/trb3/trb3qs_daqstartup.tex b/trb3/trb3qs_daqstartup.tex
index 9087b3efa96cb08979f990807ea8f103acc3352d..2c94c2adcfdeafe9c15d95953945889690dbe055 100644 (file)
--- a/trb3/trb3qs_daqstartup.tex
+++ b/trb3/trb3qs_daqstartup.tex
@@ -49,7 +49,7 @@ where value for parameter \verb+-S+ should be the same like for
 
 \subsection{Starting TRB3}
 
-Startap of the whole TRB3 boards system can be encoles in startup script
+Startup of the whole TRB3 boards system can be encoles in startup script
 shown of Listing \ref{start-system} (it is also available in user scripts,
 see Section \ref{sec:userscripts}).