Skip to content

A
AIDA-2020 TLU
Commit e320dd79 authored by Paolo Baesso's avatar Paolo Baesso
Browse files
Options

Expanded shutter chapter, clarified which signal is sent to DUT

parent b960fd2c
Hide whitespace changes
Inline Side-by-side
Showing with 28 additions and 25 deletions
Documentation/ch_Shutter.tex
View file @ e320dd79
\section{Shutter}\label{ch:shutter} \section{Shutter}\label{ch:shutter}
An optional ``shutter'' can be enabled. When the shutter is ``closed'' triggers are vetoed and no triggers are sent. When the shutter is ``open'' triggers can be generated and sent to active DUTs.\\ An optional ``shutter'' can be enabled to synchronize the acquisition window to a signal, such as the spill signal from a beam line.\\
The shutter cycle can either be started by an external signal or synchronized by a counter clocked by the system clock.\\ When the shutter is ``closed'' triggers are vetoed and no triggers are sent. When the shutter is ``open'' triggers can be generated and sent to active \gls{dut}s.\\
The external signal, if used, must be connected to one of the trigger inputs (i.e. of the the six the LEMO inputs).\\ The shutter cycle can either be started by an external signal or synchronized by a counter clocked by the system clock (i.e. internally-generated shutter, which can be used to debug hardware).\\
\begin{alertinfo}{If the external signal is used, an appropriate threshold should be set to the corresponding input. The input used for synchronizing the shutter should not be used in the trigger mask.} The external signal, if used, must be connected to one of the six LEMO trigger inputs.\\
\end{alertinfo} \begin{alertinfo}{If the external signal is used, an appropriate threshold should be set to the corresponding input. The input used for synchronizing the shutter should not be used in the trigger mask.}
Figure~\ref{fig:shutter_timing} illustrates the timing of the shutter.\\ \end{alertinfo}
Behaviour of the shutter is controlled by the IPBus registers that can be configured using the configuration parameters described in table~\ref{tab:shutter_registers}. The parameters should be included in the config file described in section~\ref{ch:configFile}. Figure~\ref{fig:shutter_timing} illustrates the timing of the shutter sequence.\\
When the shutter is open, the \gls{tlu} will assert the \verb|CONT| line (see table~\ref{tab:HDMIpins}), indicating to the \gls{dut} that the sequence is active.\\
Behaviour of the shutter is controlled by the IPBus registers described in table~\ref{tab:shutter_registers}. If using EUDAQ, the registers can be written by including the corresponding steering parameters.
The parameters should be included in the config file described in section~\ref{ch:configFile}.
\begin{figure} \begin{figure}
\centering \centering
\includegraphics[width=.95\textwidth]{./Images/aida-tlu-sitra-shutter-timing_02.pdf} \includegraphics[width=.95\textwidth]{./Images/aida-tlu-sitra-shutter-timing_02.pdf}
\caption{Shutter Timing} \caption{Shutter Timing: the E$_{min}$ signal is fed to one of the trigger inputs and initiates the shutter sequence: after a programmable delay t$_{1}$ the \gls{tlu} asserts the \emph{shutter} signal. The unit will start to issue trigger signals to the \gls{dut} once a programmable time t$_{2}$ has elapsed. The window between t$_{1}$ and t$_{2}$ can be used to ensure the \gls{dut} is configured and ready to accept triggers. The unit will issue triggers until the end of the shutter window, determined by t$_{3}$.}
\label{fig:shutter_timing} \label{fig:shutter_timing}
\end{figure} \end{figure}
%\begin{table} %\begin{table}
...@@ -28,19 +31,19 @@ Behaviour of the shutter is controlled by the IPBus registers that can be config ...@@ -28,19 +31,19 @@ Behaviour of the shutter is controlled by the IPBus registers that can be config
%\end{table} %\end{table}
\begin{landscape} \begin{landscape}
\begin{table}[] \begin{table}[]
\begin{tabular}{llll} \begin{tabular}{llll}
\textbf{\begin{tabular}[c]{@{}l@{}}CONFIGURATION\\ PARAMETER\end{tabular}} & \textbf{FUNCTION} & \multicolumn{1}{c}{\textbf{NOTE}} & \textbf{\begin{tabular}[c]{@{}l@{}}REGISTER \\ NAME\end{tabular}} \\ \hline \textbf{\begin{tabular}[c]{@{}l@{}}CONFIGURATION\\ PARAMETER\end{tabular}} & \textbf{FUNCTION} & \multicolumn{1}{c}{\textbf{NOTE}} & \textbf{\begin{tabular}[c]{@{}l@{}}REGISTER \\ NAME\end{tabular}} \\ \hline
EnableShutterMode & \begin{tabular}[c]{@{}l@{}}If 1, shutter mode is enabled.\\ If 0, shutter mode is disabled.\end{tabular} & & ControlRW \\ \hline EnableShutterMode & \begin{tabular}[c]{@{}l@{}}If 1, shutter mode is enabled.\\ If 0, shutter mode is disabled.\end{tabular} & & ControlRW \\ \hline
ShutterSource & Selects which input is used to trigger shutter sequence. & Range 0:5 & ShutterSelectRW \\ \hline ShutterSource & Selects which input is used to trigger shutter sequence. & Range 0:5 & ShutterSelectRW \\ \hline
InternalShutterInterval & \begin{tabular}[c]{@{}l@{}}Internal shutter period when using internal sequence.\\ Set to 0 to not use internal shutter generator.\end{tabular} & \begin{tabular}[c]{@{}l@{}}32-bit vale.\\ Units of 25 ns clock cycles.\end{tabular} & InternalShutterPeriodRW \\ \hline InternalShutterInterval & \begin{tabular}[c]{@{}l@{}}Internal shutter period when using internal sequence.\\ Set to 0 to not use internal shutter generator.\end{tabular} & \begin{tabular}[c]{@{}l@{}}32-bit vale.\\ Units of 25 ns clock cycles.\end{tabular} & InternalShutterPeriodRW \\ \hline
ShutterOnTime & Time between start of sequence and shutter asserted (t$_{1}$). & \begin{tabular}[c]{@{}l@{}}32-bit vale.\\ Units of 25 ns clock cycles.\end{tabular} & ShutterOnTimeRW \\ \hline ShutterOnTime & Time between start of sequence and shutter asserted (t$_{1}$). & \begin{tabular}[c]{@{}l@{}}32-bit vale.\\ Units of 25 ns clock cycles.\end{tabular} & ShutterOnTimeRW \\ \hline
ShutterVetoOffTime & Time between start of sequence and veto being de-asserted (t$_{2}$). & \begin{tabular}[c]{@{}l@{}}32-bit vale.\\ Units of 25 ns clock cycles.\end{tabular} & ShutterVetoOffTimeRW \\ \hline ShutterVetoOffTime & Time between start of sequence and veto being de-asserted (t$_{2}$). & \begin{tabular}[c]{@{}l@{}}32-bit vale.\\ Units of 25 ns clock cycles.\end{tabular} & ShutterVetoOffTimeRW \\ \hline
ShutterOffTime & \begin{tabular}[c]{@{}l@{}}Time between start of sequence and time at which\\ shutter de-asserted and veto reasserted (t$_{3}$).\end{tabular} & \begin{tabular}[c]{@{}l@{}}32-bit vale.\\ Units of 25 ns clock cycles.\end{tabular} & ShutterOffTimeRW \\ \hline ShutterOffTime & \begin{tabular}[c]{@{}l@{}}Time between start of sequence and time at which\\ shutter de-asserted and veto reasserted (t$_{3}$).\end{tabular} & \begin{tabular}[c]{@{}l@{}}32-bit vale.\\ Units of 25 ns clock cycles.\end{tabular} & ShutterOffTimeRW \\ \hline
\end{tabular} \end{tabular}
\caption{Configuration parameters and corresponding IPBus registers controlling behaviour of shutter.} \caption{Configuration parameters and corresponding IPBus registers controlling behaviour of shutter.}
\label{tab:shutter_registers} \label{tab:shutter_registers}
\end{table} \end{table}
\end{landscape} \end{landscape}
......
Documentation/ch_TLU_Hardware.tex
View file @ e320dd79
...@@ -16,8 +16,6 @@ Table~\ref{tab:HDMIpins} shows the pin naming and the corresponding output enabl ...@@ -16,8 +16,6 @@ Table~\ref{tab:HDMIpins} shows the pin naming and the corresponding output enabl
The enable signals can be configured by programming two \gls{gpio} bus expanders via \gls{i2c} interface as described in section~\ref{ch:i2c}. The enable signals can be configured by programming two \gls{gpio} bus expanders via \gls{i2c} interface as described in section~\ref{ch:i2c}.
\begin{table}[] \begin{table}[]
\centering \centering
\caption{HDMI pin connections.}
\label{tab:HDMIpins}
\begin{tabular}{|l|l|l|} \begin{tabular}{|l|l|l|}
\hline \hline
\textbf{HDMI PIN} & \textbf{HDMI Signal Name} & \textbf{Enable Signal Name} \\ \hline \textbf{HDMI PIN} & \textbf{HDMI Signal Name} & \textbf{Enable Signal Name} \\ \hline
...@@ -42,6 +40,8 @@ The enable signals can be configured by programming two \gls{gpio} bus expanders ...@@ -42,6 +40,8 @@ The enable signals can be configured by programming two \gls{gpio} bus expanders
18 & n.c. & \\ \hline 18 & n.c. & \\ \hline
19 & n.c. & \\ \hline 19 & n.c. & \\ \hline
\end{tabular} \end{tabular}
\caption{HDMI pin connections.}
\label{tab:HDMIpins}
\end{table} \end{table}
\begin{figure} \begin{figure}
\centering \centering
...@@ -147,5 +147,5 @@ The LEMO connectors used to power the \gls{pmt}s are wired according to the foll ...@@ -147,5 +147,5 @@ The LEMO connectors used to power the \gls{pmt}s are wired according to the foll
\end{enumerate} \end{enumerate}
\begin{alertinfo}{\gls{tlu} Control voltage on modified units} \begin{alertinfo}{\gls{tlu} Control voltage on modified units}
Some users requested the possibility to use different types of \gls{pmt}s. To enable this, a few power modules have been modified to provide +5~V (instead of +12~V) and to have a maximum control voltage of 1.1~V (instead of 1~V).\\ Some users requested the possibility to use different types of \gls{pmt}s. To enable this, a few power modules have been modified to provide +5~V (instead of +12~V) and to have a maximum control voltage of 1.1~V (instead of 1~V).\\
The modified units are clearly labelled and use different style of \gls{pmt} connectors, so that confusion should be minimized. The modified units are clearly labelled and use different style of \gls{pmt} connectors, so that confusion should be minimized.
\end{alertinfo} \end{alertinfo}
\ No newline at end of file \ No newline at end of file
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment