Control & Readout Software Documentation and Howto's: Difference between revisions
(Created page with "== Getting Started ==") |
No edit summary |
||
Line 1: | Line 1: | ||
== Getting Started == | == Getting Started == | ||
*[[Media:Requirements.pdf | Requirements]] | |||
== Documentation == | |||
The test software communicates with the readout unit and the ALPIDE via a series of registers. Once the test is initiated, a communication link with the readout unit will be set up. The register values specified in the test will set up the readout board and the ALPIDE. Data is then transferred from the ALPIDE to the readout unit via a firefly cable and offload from the readout unit is done via a 10 Gb high speed link. | |||
The data is transferred to the the pRU parser, which is responsible for debugging and writing the data to a .root format. This data can then be analyzed to verify the results of the test in question. | |||
=== ALPIDE Registers === | |||
Alpide Registers are registers that can be set on the ALPIDE chip. | |||
This includes configuration registers to specify masking, pusling, strobe generation and configuration of the electrical part on the ALPIDE. | |||
Specification on registers can be found in the ALPIDE manual | |||
=== Readout Unit Registers === | |||
Readout unit registers are registers that can be set on the readout board. | |||
This includes offload, triggering, global regs, alpide control and monitoring of different register via alpide data | |||
Specifications on registers can be found in their respective modules | |||
== Test examples == | |||
*[[Media:Digital Scan.pdf | Digital Scan]] | |||
*[[Media:Analog Scan.pdf | Analog Scan]] | |||
*[[Media:Threshold Scan.pdf | Threshold Scan]] | |||
*[[Media:Single Event.pdf | Single Event]] | |||
== Module Registers == | |||
*[[Media:Alpide control.pdf | Alpide control]] | |||
*[[Media:Alpide data.pdf | Alpide data]] | |||
*[[Media:Global regs.pdf | Global regs]] | |||
*[[Media:Trigger manager.pdf | Trigger manager]] | |||
*[[Media:Offload.pdf | Offload]] | |||
== ALPIDE Manual == | |||
*[[Media:ALPIDEmanual_v0_3.pdf | Alpide manual]] | |||
== .root format == | |||
* readout unit id | |||
* stave id | |||
* chip id | |||
* frame id | |||
* abs time (120 Mhz clock) | |||
* bunch counter (40 Mhz clock) | |||
* xy (hit coordinate) |
Revision as of 12:24, 17 September 2019
Getting Started
Documentation
The test software communicates with the readout unit and the ALPIDE via a series of registers. Once the test is initiated, a communication link with the readout unit will be set up. The register values specified in the test will set up the readout board and the ALPIDE. Data is then transferred from the ALPIDE to the readout unit via a firefly cable and offload from the readout unit is done via a 10 Gb high speed link. The data is transferred to the the pRU parser, which is responsible for debugging and writing the data to a .root format. This data can then be analyzed to verify the results of the test in question.
ALPIDE Registers
Alpide Registers are registers that can be set on the ALPIDE chip.
This includes configuration registers to specify masking, pusling, strobe generation and configuration of the electrical part on the ALPIDE.
Specification on registers can be found in the ALPIDE manual
Readout Unit Registers
Readout unit registers are registers that can be set on the readout board.
This includes offload, triggering, global regs, alpide control and monitoring of different register via alpide data
Specifications on registers can be found in their respective modules
Test examples
Module Registers
ALPIDE Manual
.root format
- readout unit id
- stave id
- chip id
- frame id
- abs time (120 Mhz clock)
- bunch counter (40 Mhz clock)
- xy (hit coordinate)