Navigating The Profile Monitor Screens

For these examples I will be using the LCLS-II OTR11B device in L1B/BC1B location. There are two designs used for the Profile Monitor Devices; A standard device with 1 target, 2 filters, 2 lamps, and 3 motors and the PAL device with 2 target screens, 1 filter, 1 target lamp, and 1 motor. There is also and EDM and a PYDM of most screens.

PYDM Screen Version

Main Location Screen (Unreleased)


EDM Screen Version

Main Location Screen

  1. Link to Profile Monitor MATLAB GUI
    where you are able to see all of the Profile Monitor Cameras and capture images for the e-Logbook.

  2. Brightness Controls: this is dependent on which chassis the slider controls. If you are not seeing the brightness change when there are multiple brightness options double check which one you are using
    1. In future iterations the brightness bar will be attached to each of the Profile Monitor Device Controls.
    2. PAL device has only the target brightness bar.

  3. Profile Monitor Device Controls: this widget controls and displays the status of the Profile Monitor Device. All sections, other than the indicator light in the top right, have visibility rules for the devices set automatically during IOC start but can be turned on after the fact if needed.
    1. Camera Image and On/Off button: $(DEVICE):CAMTYPE
    2. Target Button: $(DEVICE):TGTINSTALLED
    3. Filter 1: $(DEVICE):FLT1INSTALLED
    4. Filter 2: $(DEVICE):FLT2INSTALLED
    5. Target Lamp: $(DEVICE):TLAMPINSTALLED
    6. Grid Lamp: $(DEVICE):GLAMPINSTALLED
    7. Motor Controls (not visible):$(DEVICE):MTRINSTALLED
    8. Indicator light will be green if the camera is powered (Standard) or has framerate (PAL)

  4. TID Image/PGP/Timing Camera Controls: this screen confirms if the FEB and Camera are communicating, controls camera exposure time, camera trigger delays, camera gain, image mode, trigger mode, image collection, camera setup, chosen triggers and timing.

Main Profile Monitor Location Screen

TID Image/PGP/Timing Camera Controls (pgpCamTop)

Currently there are bugs in this screen so if the camera is not working properly please read through numbers 4-8 for easy things to double check on this screen.

This screen can be used to help diagnose problems with the screen.

  1. Rogue pgp Vars Button: this screen looks at the PGP card in the cpu and gives more information about the camera along with the trigger codes for the other attached cameras. 
    1. This is the primary diagnostic to see if something is not going on with the camera other than the Timing Button (See 3).
    2. Unlike the EvrV2:RateSel on the pgpCamTop screen, the PV that logs the trigger code on this screen works but you will need to know which channel the camera is attached to.
    3. More information on this screen is in a below section.

  2. Camera Plugin Stack Button: this screen covers
    1. With new/replaced cameras some settings will need to be set as enabled from this screen. Otherwise you will not be able to acquire images or be able to see them in MATLAB.
    2. More information on this screen is in a below section.

  3. Timing Button: this screen covers the timing information that is displayed here is exclusively for the camera listed.

    Use this screen if all that is being doe is changing timing
    1. Unlike the EvrV2:RateSel on the pgpCamTop screen, the PV that logs the trigger code on this screen works.
    2. More information on this screen is an a below section

  4. Exposure time PV: this is where you can change the exposure time for the camera.

    There is a bug with this PV where when entering a number the incorrect number is logged. Double check that the number shown on the right matches the number entered on the left.

    • Typically we see an incorrect "e-##" but sometimes the primary number is also incorrect.
    • Re-entering the PV sometimes works but typically you need to change the number and revert back to the desired exposure time.
    1. If the cpu or primary control ioc are rebooted the exposure time may be set to the wrong exposure time or the camera may have the wrong exposure time saved. 

      1. The iocs in question can be found on the Profile Monitor Control Room Help page, typically -pm01 or -pm04 with some exceptions.

  5. Image/Trigger Mode PV: if the capture rate is different than the EvrV2:RateSel this could be due to these two PVs got set incorrectly on the camera. This is typically due to the camera being powered off and lost the correct trigger and image code. Resubmit them as the seen modes in the image.
    1. This an cause the capture rate to be different than the timing rate

  6. Acquire PV: this PV needs to be set to "Collecting" by hitting "Start" in order to acquire images assuming timing is running.

    There is a known bug where sometimes this PV needs to be turned On and Off a few times in order to acquire images. If Capture Rate still 0Hz, see Quick Help

  7. EvrV2:RateSel: This PV controls which timing signal you are connecting to. See Control Sequence Bit for LCLS-II timing.

  8. Timing:TriggerSource and Timing:RateType: When beam is active you should see Timing:TriggerSource as EVR and Timing:RateType as ControlWord

Timestamps section out of date, missing FEB TrigCnt, Dropdown Rate Selection, and manual entry field.

Getting Things Set Up

Finding Beam on Screen

From the device's camera control screen, pgpCamTop, slowly adjust the Trigger Delay and Exposure time values, in the Acquisition Settings, until beam is found. It is recommended to start with the largest Exposure time without loss of Capture rate, this ranges depending on camera used, then adjusting the Trigger Delay until beam is found. Then dialing in the Exposure time and Trigger Delay from there. If unable to find beam regardless of settings, inform the physicists that the reflection may not be bright enough at the location with the installed target screen.

If you are trying to locate the beam after the initial setup is done try making small adjustments to the Exposure time.

Quick Help

Trigger Without Beam

Normal Conducting:

  • On pgpCamTop screen in the Timestamps section
    • Set LCLS-I Event Code to NC Test
      • If doesn't work Set to MANUAL ENTRY
        • Input 43 for fixed 10 Hz

Super Conducting:

  • On pgpCamTop screen in the Timestamps section
    • Set Lcls2:RateSel to MANUAL ENTRY
      • 0 for 1 Hz
      • 1 for 10 Hz
      • 2 for 100 Hz
    • Set Timing Rate Type to FixedRates
      • Be sure to return to ControlWord to return to ACR rates

Things to Check if 0Hz Capture Rate

On pgpCamTop Screen:

  • To big of exposure time, found in Acquisition Settings, is being used
  • Image mode, found in Acquisition Settings, is not on Continuous
  • Trigger mode, , found in Acquisition Settings, is not on Pulse
  • Incorrect RateSel is used, found in Timestamps
    • If drop down is not updating use "MANUAL ENTRY" and enter in the correct Event Code
  • Timing:RateType, found in Timestamps, is not on ControlWord
  • Timing:Trigger,  found in Timestamps, is not on EVR

On pgpClDiag Screen, found by clicking Rogue pgp Vars.. button on pgpCamTop screen:

  • Timing:FidCout/sofCount/eofCount, found in Timing, are not updating
    • Click between Timing and Mini mode typically will solve the issue, may take a second for the Count to start updating again.
  • PgpRx/EventBuilder values are not updating when image is Acquiring.
    • Click Reboot Camera button on pgpCamTop screen



  • No labels