--- /dev/null
+\subsection{Data Format}
+The module has two distinct output formats that can be selected before synthesis and cannot be changed during runtime.
+Both share a common first word, containing the received running number as well as status- and the error-bits.
+If indicated in the header, two additional words storing information to reconstruct the arrival time of this MBS data follow:
+
+In this case, the first additional word (2nd in stream) holds a timestamp with a granularity of 5~ns.
+The timestamp was reset by the arrival of the timing trigger belonging to the LVL1 trigger as indicated by the 3rd word in the data stream.
+Observe that this information is only valid, if a timing trigger was received not more than 20~s before the arrival of the data word.
+
+{\small
+\begin{longtable}{ p{4cm} l c p{8cm} }
+ \toprule
+ \textbf{Word} & \textbf{Addr} & \textbf{Bits} & \textbf{Description} \\
+ \textbf{CommitReg} & 0 & & Header \\
+ \quad MBSNumber & & 0--23 & MBS-Number received \\
+ \quad DataFormat & & 24 & 0: Only this header, 1: Two words follow\\
+ \quad MBSStatus & & 29--30& MBS-Status bits received\\
+ \quad MBSError & & 31 & MBS-Error bit (high-active)\\
+ \rowcolor{light-gray}
+ \textbf{Timestamp} & 1 & 0--31 & Time (in 5~ns steps) since timing trigger of event indicated in next word\\
+ \textbf{LVL1Info} & 2 & & LVL1-Trigger information of timestamp \\
+ \quad TriggerNumber& & 0--15 & Trigger number sent by CTS\\
+ \quad TriggerCode & & 16--23& Trigger code sent by CTS\\
+ \bottomrule
+ \caption{Read-out format of MBS receiver}\label{tab:CBMMBSRecvRDO}
+\end{longtable}
+}
\ No newline at end of file