Glossary

FEB

Front End Board.

FEB class

The ROC currently supports three classes of FEB's:

• with 1 nXYTER, FEB1nx class, one per ROC port
• with 2 nXYTER, FEB2nx class, one per ROC port
• with 4 nXYTER, FEB4nx class, one per ROC The contrete FEB's in each class share most of the hardware and software interface and can therefore in many cases handled in a generic way. The symbolic constants nxyter::FebBase::kFeb1nx, nxyter::FebBase::kFeb2nx, and nxyter::FebBase::kFeb4nx are used in software interfaces.

FEB1nx class

Currently one FEB with a single nXYTER is implemented:

• nxyter::FEB1nxGen - general purpose FEB

FEB2nx class

Currently one FEB with two nXYTER is implemented:

• nxyter::FEB2nxGas - developed for PANDA GEM TPC

FEB4nx class

Currently one FEB with four nXYTER is implemented:

• nxyter::FEB4nxBT - CBM Beam tracker board

FEB type

The FEB type identifies a concrete FEB, currently available and implemented are:

• nxyter::kFeb1nxGen
• nxyter::kFeb2nxGas
• nxyter::kFeb4nxBT

nXYTER

nXYTER index

The nXYTER index, usually named nxind, is a unique identifier of a nXYTER on a FEB. Valid values are 0 to nxyter::FebBase::numNx()-1. It is used to address a nXYTER on a given FEB, very often to access a nxyter::NxChip object via the nxyter::FebBase::nx() method. See also nXYTER number, which is a unique identifier of a nXYTER on a ROC.

nXYTER number

The nXYTER number, usually named nxnum, is a unique identifier of a nXYTER on a ROC. Valid values are 0 to 3. It is used to address nXYTER specific resources on a ROC. See also nXYTER index, which is a unique identifier of a nXYTER on a FEB.

Note: for a given chip, the nXYTER number differs in general from the nXYTER index.

ROC

Read-out Controler

ROC port

The ROC has 2 user data ports which allow to connect a FEB. They are numbered 0 and 1 in all software interfaces and named CON19 and CON20 in the ROC schematic diagrams and documentation. There are also # defines CON19 and CON20 which provide symbolic names for the two possible port numbers.