This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
usb_data_acquisition_setup_guide [2013/12/11 19:38] pereira created |
usb_data_acquisition_setup_guide [2019/06/22 04:42] pereira |
||
---|---|---|---|
Line 7: | Line 7: | ||
The first mode is typically used when setting up the modules contained in the crate, such as gains, thresholds and so on, while the second mode is used for acquiring event-driven data. The two modes are mutually exclusive, and issuing an interactive command while in data acquisition mode will typically result in an error or lockup of the controller. | The first mode is typically used when setting up the modules contained in the crate, such as gains, thresholds and so on, while the second mode is used for acquiring event-driven data. The two modes are mutually exclusive, and issuing an interactive command while in data acquisition mode will typically result in an error or lockup of the controller. | ||
- | The USB DAQ is a Tcl-based software | + | The USB DAQ is a Tcl-based software. It is capable of handling multiple crate controllers (CC-USB or VM-USB) connected to the same computer. |
- | The machine-level calls to the USB interface are handled by a library called " | + | The data streams coming from the various crates are synchronized |
- | The data streams coming | + | The time-ordered |
- | The software is distributed into the following folder structure: | ||
- | * TclXXUSB: contains the USB DAQ main program (RunControl.tcl) as well as class definitions for different types of modules | ||
- | * libTclXXUSB: | ||
- | * eventbuild: contains the event builder program and its debug files | ||
- | * Scripts: contains the Tcl scripts for the various crates and sequences | ||
- | * Configs: contains the configuration files of the various modules used in the setup | ||