Outils pour utilisateurs

Outils du site


upgrade_of_fw_status

Différences

Ci-dessous, les différences entre deux révisions de la page.

Lien vers cette vue comparative

Les deux révisions précédentes Révision précédente
Dernière révision Les deux révisions suivantes
upgrade_of_fw_status [2018/06/19 07:53]
DAQ user [Data Structure]
upgrade_of_fw_status [2018/06/19 08:05]
DAQ user
Ligne 1: Ligne 1:
 ====== Status of the new firmware ​ ====== ====== Status of the new firmware ​ ======
  --- //​[[laurent.mirabito@gmail.com|DAQ user]] 2018/06/18 07:26//  --- //​[[laurent.mirabito@gmail.com|DAQ user]] 2018/06/18 07:26//
 +
 +===== State machine changes =====
 +
 +  - ''​Clear separation of acquisition and data transfer'':​ The firmware is not controlling the acquisition time, it just throws a BUSY when one TDC fifo is ALmost Full (25 over 32). The BUSYs are collected by the MDCC board that terminates the acquisition window when one busy is seen and do not restart a window until all BUSYs are low.
 +  - ''​Data transmit per channel'':​ Once the acquisition window is end, a BUSY is set per FEB until the data transfer is completed. It consists first to an Event packet containing the GTC (window count) and the Absolute BCID (readout time 200 ns steps). Then TDCs are scanned one by one , if not empty a channel packet is sent. Once all TDCs are browsed, BUSY is released and the FEB is in IDLE for the next window.
 +  - ''​ Trigger Mode '':​
  
 ===== Data Transfer ===== ===== Data Transfer =====
upgrade_of_fw_status.txt · Dernière modification: 2018/06/19 08:33 par DAQ user