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.
TID Image/PGP/Timing Camera Controls (pgpCamTop)
This screen can be used to help diagnose problems with the screen.
- 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.
- This is the primary diagnostic to see if something is not going on with the camera other than the Timing Button (See 3).
- 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.
- More information on this screen is in a below section.
- Camera Plugin Stack Button: this screen covers
- 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.
- More information on this screen is in a below section.
Timing Button: this screen covers the timing information that is displayed here is exclusively for the camera listed.
- Unlike the EvrV2:RateSel on the pgpCamTop screen, the PV that logs the trigger code on this screen works.
- More information on this screen is an a below section
Exposure time PV: this is where you can change the exposure time for the camera.
- 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.
The iocs in question can be found on the Profile Monitor Control Room Help page, typically -pm01 or -pm04 with some exceptions.
- 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.
- This an cause the capture rate to be different than the timing rate
Acquire PV: this PV needs to be set to "Collecting" by hitting "Start" in order to acquire images assuming timing is running.
- EvrV2:RateSel: This PV controls which timing signal you are connecting to. See Control Sequence Bit for LCLS-II timing.
- Timing:TriggerSource and Timing:RateType: When beam is active you should see Timing:TriggerSource as EVR and Timing:RateType as ControlWord
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
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