@@ -2,10 +2,11 @@ This document will describe most aspects of the DAQ used for experiment I257.
The guide is divided into the following sections:
# Table of Contents
+[Hardware](####hardware)
+[Software](####software)
+[How to start the DAQ](####how-to-start-the-daq)
+[Analysis](####analysis)
+[Hardware](#hardware)
+[Software](#software)
+[Startup Guide](#startupguide)
+[FAQ](#faq)
+[Troubleshoot](#troubleshoot)
#### Hardware
The DAQ is running on a VME computer (__MOT2__) and a trigger module (__VULOM4b__). The VME computer boots via ethernet from a laptop (__Bumblebee__), which also acts as the final DAQ computer. All user interaction goes through __Bumblebee__.
...
...
@@ -133,7 +134,7 @@ To push data to Grafana, open a terminal and issue (__DAQC__ must be running)
monitor
```
## Startup guide
#### Startup guide
This section will give you the step-by-step guide to how to start up the acqusition from scratch. It is usually only required if the VME computer lost power or was rebooted. Otherwise a simple restart of __DAQC__ should be enough.
1. __Turn on the VME-crate and the NIM-crates__: Make sure that all crates have power and are running. Wait a minute or two, to make sure both VME computers are online by ssh'ing into mot2.
...
...
@@ -171,7 +172,7 @@ This section will give you the step-by-step guide to how to start up the acqusit
monitor
```
## FAQ
#### FAQ
- __Start DAQC__:
Simply open a terminal and issue:
...
...
@@ -271,7 +272,7 @@ This section will give you the step-by-step guide to how to start up the acqusit
monitor
```
## Troubleshooting
#### Troubleshooting
Since the DAQ consists of so many moving parts, a lot can go wrong. However, a lot of these moving parts are non-essential, i.e. data can still be taken. The readout itself is very, very stable, i.e the two __RIO__'s and the event builder on __Bumblebee__. We have yet to see a proper crash of these.
What is much more likely to cause problems, and probably will during every experiment is __Go4__. Therefore, this should be the first suspicion.
