...
- Open terminal from the mfx-daq machine
go to the daqcontrol directory
Code Block language py theme Midnight firstline 1 cd daqcontrol/misc ls
you should now be in
/reg/neh/operator/mfxopr/daqconfig/misc or /cds/home/opr/mfxopr/daqconfig/misc
The files saved into the daq are stored in the epicsArch.txt
file. This file calls the other text files, for cleanliness. Each "sub-text" file, such as epicsArch_sds.txt
contains the alias in the data stream and the corresponding PV.
current epicsArch.txt
is recording beamline and sequencer data, but we are not using the ePix10K or SMB setup and so these values are commented out.
Note | |||||||||
---|---|---|---|---|---|---|---|---|---|
| |||||||||
logbook.txt show the variables that post in the logbook. Notice that simply add to the file:
or any other "sub-text" file that needs to be added. |
...
You can see the files commented out at the top. These are no longer deployed and so the daq throws out errors. The daq will still record though.
The syntax seems to be is an asterisk precedes the alias name for the data in the XTC file, preceded by an asterisk. Below , the alias is the EPICS PV name you want recorded.
If you place multiple aliases with the same name before the first underscore, then the DAQ will sort these into the same dropdown menu. For example, laserfs_T_phase, laserfs_TT_amp, and laserfs_atm will all be added to a dropdown menu labeled "laserfs" in the PV list. Dropdown menus can be nested within other dropdown menus by creating aliases with the same name before the next underscore.
Info |
---|
Restart the DAQ after editing the PVs. |
Related articles
Content by Label | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Page properties | |||
---|---|---|---|
| |||
|