Setup & Diagnosing

The camrecorder process for recording EPICS camera data on a local disk runs on psrec01.

The PV is OTRS:DMP1:695:Image:ArrayData

Some instructions

ssh -X psrec01

To view recorded XTCAV data:

/reg/g/pcds/dist/pds/amo/ami-current/build/ami/bin/x86_64-linux-opt/offline_ami -p /u2/REC/daq

To check incoming XTCAV data:

bash
export EPICS_CA_AUTO_ADDR_LIST=NO
export EPICS_CA_ADDR_LIST=192.168.0.3
export EPICS_CA_SERVER_PORT=5068
export EPICS_CA_MAX_ARRAY_BYTES=10000000
camonitor -# 10 OTRS:DMP1:695:Image:ArrayData

caget OTRS:DMP1:695:Image:ArraySize0_RBV   /* width */

caget OTRS:DMP1:695:Image:ArraySize1_RBV   /* height */

 

We need to record additional information to properly analyze the XTCAV image:

 

Possibly BLD

        BPMS:LTU1:250:X - Beam position (in X) at LTU1:250 (in mm)
        BPMS:LTU1:450:X - Beam position (in X) at LTU1:450 (in mm)
        BPMS:DMP1:502:TMIT - Bunch charge arriving in the electron dump (in
Nel)
        TCAV:DMP1:360:ABR - XTCAV Amplitude (MV)
        TCAV:DMP1:360:PBR - XTCAV Phase (deg)

Slow configuration data (1Hz in epicsArch)

        SIOC:SYS0:ML01:AO216
        OTRS:DMP1:695:TCAL_X
        SIOC:SYS0:ML01:AO214
        SIOC:SYS0:ML01:AO215
        SIOC:SYS0:ML01:AO212
        OTRS:DMP1:695:BLEN
        SIOC:SYS0:ML01:AO213

Known Issues

The fiducial number (pulseID) recorded for this camera is late compared to the DAQ/BLD if the height of the readout image is too large (>330?).

 

2 Comments

  1. Very outdated. No psrec01, raw image PV name has changed, much more data is currently recorded along with image. #archive
  2. Page is outdated and important information are available elsewhere (where it's also updated). #archive