Difference between revisions of "ITSDAQ for full petals"
(correction: previous page is DAQ Genesys) |
(add info from readme) |
||
(One intermediate revision by the same user not shown) | |||
Line 3: | Line 3: | ||
<math>\blacktriangleleft</math> ''<big>[[DAQ systems: Genesys]]</big>'' | <math>\blacktriangleleft</math> ''<big>[[DAQ systems: Genesys]]</big>'' | ||
----Fully loaded petals are tested with the official itsdaq repo, on master branch: https://gitlab.cern.ch/atlas-itk-strips-daq/itsdaq-sw | ----Fully loaded petals are tested with the official itsdaq repo, on master branch: https://gitlab.cern.ch/atlas-itk-strips-daq/itsdaq-sw | ||
+ | |||
+ | |||
+ | Before running a scan: | ||
+ | |||
+ | adapt st_system_config.dat (saying which modules you are testing), power supplies (specifying wchih power supplies you are using and which channels you are using) and another one and then RUNITSDAQ.sh | ||
+ | |||
+ | |||
+ | <nowiki>======================================</nowiki> | ||
+ | |||
+ | Configuration files | ||
+ | |||
+ | itsdaq-sw/config: The files in this directory are provided as example configurations for the ITSDAQ software to use online. It reads these from $SCTDAQ_VAR/config, so files should be placed there and modified as appropriate. | ||
+ | |||
+ | |||
+ | 1. System configuration -------------------- | ||
+ | |||
+ | The system configuration mapping are described in the file st_system_config.dat. This includes both the connection to the DAQ and the stream configuration for the modules. The module configurations are described in separate files in the same directory, linked by name. | ||
+ | |||
+ | |||
+ | 2. Detector configuration ---------------------- | ||
+ | |||
+ | The chip level configurations are described by .det files, which are named in the system configuration. A variety of examples are provided here for different hybrid geometries. If "mymodule.det" does not exist, the "default.det" file (in sctvar) will be used. Strip masks can be loaded from files list "mymodule.mask". This is a list of channels to be masked, one per line. This is interpreted as pairs of numbers, the first being the chip address and the second being the channel number within the chip. The same information can also be included in the detector configuration file, see examples for a description. Trims are loaded from trim files "mymodule.trim" (description to be added). | ||
+ | |||
+ | |||
+ | 3. Power supply configuration -------------------------- | ||
+ | |||
+ | The power supplies can be configured using a json file, located in: $SCTDAQ_VAR/config/power_supplies.json. This file is used by LoadSupplies.cpp to determine which serial ports have supplies connected to them. Currently, using this method requires changing lv_type and/or hv_type to -1. Currently, all other settings such as the power supply model are detected automatically by sending the ''*IDN? command (but doing this requires a working serial link, which means that it will only work if the device uses ITSDAQ's default settings of 9600 Hz, 8 bits, no parity, 1 stop bit, and line feed as the termination character). The configuration uses psName to locate the device, either as a linux device file (e.g. /dev/serial/by-id/usb-TTi_MX_Series_PSU_483216-if00, or /dev/ttyS0), or a reference to an NI-VISA instrument (eg ASRL6::INSTR). In order to use NI-VISA, it needs to be configured to enable VISA when configuring the build. The channel and output fields will default to 1 if not given for LV and HV supplies, respectively. The deviceType field must be given for HV sources which are not SCPI-compliant, to tell ITSDAQ that it should use a special set of commands. It should be set to 1 for older Keithley supplies (236, 237, 487) and 2 for the Cambridge HV supply (ITKHV). If the deviceType field is omitted, it is set to its default value, 0, which indicates an SCPI-compliant supply (i.e. a Keithley 2410 or 2657A).'' | ||
+ | |||
+ | <nowiki>======================================</nowiki> |
Latest revision as of 12:01, 21 October 2024
Author: Andrea García Alonso aalonso@nikhef.nl
Fully loaded petals are tested with the official itsdaq repo, on master branch: https://gitlab.cern.ch/atlas-itk-strips-daq/itsdaq-sw
Before running a scan:
adapt st_system_config.dat (saying which modules you are testing), power supplies (specifying wchih power supplies you are using and which channels you are using) and another one and then RUNITSDAQ.sh
======================================
Configuration files
itsdaq-sw/config: The files in this directory are provided as example configurations for the ITSDAQ software to use online. It reads these from $SCTDAQ_VAR/config, so files should be placed there and modified as appropriate.
1. System configuration --------------------
The system configuration mapping are described in the file st_system_config.dat. This includes both the connection to the DAQ and the stream configuration for the modules. The module configurations are described in separate files in the same directory, linked by name.
2. Detector configuration ----------------------
The chip level configurations are described by .det files, which are named in the system configuration. A variety of examples are provided here for different hybrid geometries. If "mymodule.det" does not exist, the "default.det" file (in sctvar) will be used. Strip masks can be loaded from files list "mymodule.mask". This is a list of channels to be masked, one per line. This is interpreted as pairs of numbers, the first being the chip address and the second being the channel number within the chip. The same information can also be included in the detector configuration file, see examples for a description. Trims are loaded from trim files "mymodule.trim" (description to be added).
3. Power supply configuration --------------------------
The power supplies can be configured using a json file, located in: $SCTDAQ_VAR/config/power_supplies.json. This file is used by LoadSupplies.cpp to determine which serial ports have supplies connected to them. Currently, using this method requires changing lv_type and/or hv_type to -1. Currently, all other settings such as the power supply model are detected automatically by sending the *IDN? command (but doing this requires a working serial link, which means that it will only work if the device uses ITSDAQ's default settings of 9600 Hz, 8 bits, no parity, 1 stop bit, and line feed as the termination character). The configuration uses psName to locate the device, either as a linux device file (e.g. /dev/serial/by-id/usb-TTi_MX_Series_PSU_483216-if00, or /dev/ttyS0), or a reference to an NI-VISA instrument (eg ASRL6::INSTR). In order to use NI-VISA, it needs to be configured to enable VISA when configuring the build. The channel and output fields will default to 1 if not given for LV and HV supplies, respectively. The deviceType field must be given for HV sources which are not SCPI-compliant, to tell ITSDAQ that it should use a special set of commands. It should be set to 1 for older Keithley supplies (236, 237, 487) and 2 for the Cambridge HV supply (ITKHV). If the deviceType field is omitted, it is set to its default value, 0, which indicates an SCPI-compliant supply (i.e. a Keithley 2410 or 2657A).
======================================