| ... | ... | @@ -2,21 +2,21 @@ There are many types of computer setups, consisting of different software instal |
|
|
|
|
|
|
|
One thing to keep in mind is that the below definitions are combined onto the same machine very often in test-stand setups. For example, running the RTS and DAQ on the same machine is quite common making that machine a "Frontend/DAQ".
|
|
|
|
|
|
|
|
- Frontend (FE) Computer
|
|
|
|
- ***Frontend (FE) Computer***
|
|
|
|
- Runs the Real Time System (RTS)
|
|
|
|
- The main job of the RTS is to run real-time controls models. These are designed in MATLAB and built with the Real Time Code Generator (RCG). Models take inputs from ADCs and other hardware and control DACs/ send data to the DAQ.
|
|
|
|
- The RTS is usually attached to hardware (I/O chassis [ADCs/DACs]).
|
|
|
|
- [How to setup a Frontend](Debian-Frontend-Installation-Guide)
|
|
|
|
- Workstation Computer
|
|
|
|
- ***Workstation Computer***
|
|
|
|
- Runs MATLAB for model editing and workstation tools like ndscope, dtt, etc.
|
|
|
|
- DAQ Computer
|
|
|
|
- ***DAQ Computer***
|
|
|
|
- Runs the Data Acquisition Daemon (DAQ) and other supporting software.
|
|
|
|
- On small test stands DAQ components are often run on the Frontend with the real-time models (making a Frontend/DAQ).
|
|
|
|
- CyMAC Configuration
|
|
|
|
- ***CyMAC Configuration***
|
|
|
|
- A machine that combines functionality of the Frontend, DAQ and workstation all on one computer.
|
|
|
|
- One drawback of this setup is MATLAB and other workstations tools can take up a lot of resources (CPU/memory) and negatively impact the functionality of the RTS.
|
|
|
|
- [How to setup a CyMAC](https://git.ligo.org/cds/software/advligorts/-/wikis/Debian-CyMAC-Installation-Guide)
|
|
|
|
- Bootserver
|
|
|
|
- ***Bootserver***
|
|
|
|
- A central bootserver supports multiple diskless frontend machines. A second network connects the RTS frontends to one or more DAQ computers.
|
|
|
|
- Once you have more than one FE computer it can become complicated to manage the RTS on each one individually. In these cases a bootserver is setup so that the FE software can be configured in a single place and FE computers will PXE boot from it.
|
|
|
|
- The DAQ is usually moved to its own server at this level of complexity because the output from each FE needs to be aggregated by the DAQ.
|
| ... | ... | |
