Each sample chamber at CXI has two cameras – inline and off-axis – used for alignment and automation, experiment viewing, and analysis. The image streams are served via an EPICS IOC viewable from the camViewer, and can be included in the CXI primary or secondary DAQ data streams via the IOC recorder.
Each camera has a host server that is running an EPICS IOC to handle low-level command, image acquisition, and to broadcast the data via channel access. Recorded cameras need to run on IOC hosts with hard disk drives, so the CXI sample chamber cameras run on ioc-cxi-rec03 (Rack 59 : Red Hat 7) and ioc-cxi-rec04 (Rack 52A : Red Hat 7). Access to the host and IOC process can be achieved using the IOC manager. The cameras are also synced to LCLS timing, and thus require a TTL trigger signal from their host's EVR hardware – typically a SLAC EVR PCI card in the server chassis. This is usually routed from the host to the camera via a user patch panel over coaxial cable.
Troubleshooting Tip:
If the trigger signal is disconnected from the camera, the IOC will continue to report that the camera is connected but will stop acquiring images! If a camera is not triggering properly, verify that there are no trigger cable connection interruptions between the host and the camera and take a look at the camera's trigger settings on its expert screen.
The expert screens for each camera can be pulled up from the CXI Home Screen, on the left sidebar under the "IOC Cameras" dropdown menu or from the bottom embedded tabs: Detector → Control Cams Config
Curveball:
Adimec Opal cameras will always sync to an external trigger, and actually run reliably in Free Run mode.
The "Yag Viewer" button will open the camViewer from which you can select and view the camera feeds for the yags. Example: dg1_yag.
Bottom embedded tabs: Detector → Viewer Cameras (Beamline/User Camera/Viewer SC Cameras) will open camViewer for the respective cameras.
As a result of changing setups, hutch reconfiguration and different experiment requirements, the cameras at the sample chambers may come and go or even change types. Most often GigE type cameras such as the Allied Vision Manta 146C or "framegrabber" type cameras such as an Adimec Opal are used. GigEs are usually powered over ethernet so they need only be connected to a trigger signal and a network switch port on the cds-cxi.pcdsn subnet with PoE capability to maintain function at the sample chamber. Frame grabber cameras, on the other hand, communicate over optical fiber which is transceived on both sides by EDT RCX camera links. RCX camera links require separate power (5V), and must be configured to the correct blink code in order to send and receive data between the camera and frame grabber PCI card. If a camera link fails then the IOC host will lose connection to the camera. Frame grabber cameras and their RCX links are usually powered using DC voltage supply available at the user patch panels. Network and fiber connections to the sample chamber cameras are also accessed via the user patch panels.
How to be a Good Beamline Scientist:
If you are setting up a GigE at the sample chamber and cannot find a CDS PoE ethernet port on the patch panel because none of the ports are labeled properly, senselessly harass the nearest PCDS engineer.
When changing cameras, be sure to enable or disable its corresponding IOC using iocmanager.
| Camera | camViewer name | Gige name | Cam Type | Host | Build | IOC Manager Alias | IOC Name |
|---|---|---|---|---|---|---|---|
| SC1 on-axis | cxi_sc1_inline | NA | Alvium 240um | ioc-cxi-qadc | rhel7 | CAM - SC1 Inline | ioc-cxi-alv-01 |
| SC1 off-axis | cxi_sc1_offaxis | gige-cxi-08 | Gige Mako G319C | ioc-cxi-rec03 | rhel7 | CAM - SC1 Offaxis | ioc-cxi-gige-08 |
| SC1 Navitar | cxi_sc1_navitar | gige-cxi-navitar1 | Gige Mako G319C | ioc-cxi-cam2 | rhel7 | CAM - SC1 Navitar Gige | ioc-cxi-navitar1-gige |
| SC2 on-axis | cxi_sc2_inline | gige-cxi-06 | Gige Manta 146C | ioc-cxi-cam2 | rhel7 | CAM - SC2 Inline Gige 06 | ioc-cxi-gige-06 |
| SC2 off-axis | cxi_sc2_offaxis | gige-cxi-07 | Gige Mako G319C | ioc-cxi-rec03 | rhel7 | CAM - SC2 Offaxis Gige 07 | ioc-cxi-gige-07 |
| SC2 Navitar | NA | NA | NA | NA | NA | NA | NA |
| SC3 on-axis | cxi_sc3_inline | gige-cxi-05 | Gige Manta 146C | ioc-cxi-rec04 | rhel7 | CAM - SC3 Inline Gige 05 | ioc-cxi-gige-05 |
| SC3 off-axis | cxi_sc3_offaxis | gige-cxi-03 | Gige Manta 146B | ioc-cxi-rec04 | rhel7 | CAM - SC3 Offaxis Gige 03 | ioc-cxi-gige-03 |
| Timetool | cxi_timetool | gige-cxi-timetool | Gige Mako G319C | ioc-cxi-cam5 | rhel7 | CAM - Timetool Gige | ioc-cxi-timetool-gige |
| DG1 Yag | cxi_dg1_yag | gige-cxi-dg1 | Gige Manta 146C | ioc-cxi-rec01 | rhel7 | CAM - DG1 PIM Gige 01 | ioc-cxi-dg1-gige |
| DG2 Yag | cxi_dg2_yag | gige-cxi-dg2 | Gige Manta 146C | ioc-cxi-rec01 | rhel7 | CAM - DG2 PIM Gige 02 | ioc-cxi-dg2-gige |
| DG3 Yag | Pulnix | ioc-cxi-rec03 | rhel7 | CAM - DG3 PIM | ioc-cxi-dg3-p6740 | ||
| Laser Near field | cxi_las_nearfield | gige-cxi-las01 | Basler acA2500-20gm | ioc-cxi-acromag | rhel7 | CAM - Laser Enclosure Near Field Tutti Frutti | ioc-cxi-las-gige-01 |
| Laser Far field | cxi_las_farfield | gige-cxi-las02 | Basler acA1440-73gm | ioc-cxi-acromag | rhel7 | CAM - Laser Enclosure Far Field Tutti Frutti | ioc-cxi-las-gige-02 |
Gige Debugging tips:
To check if the camera is online and if the camera is a gige, then it should be pingable on the network. Use the name from column #3 from the above table, "Gige name" to check if the camera is seen by the cds network. Example: ping gige-cxi-timetool.
camViewer:
To open the camera with camviewer, use name from column #2 "camViewer name", Example : camViewer -c cxi_timetool
When a new camera is added or changed and a new IOC is deployed, the camviewer configuration file needs to be changed to make the new camera viewable in the camViewer. Comment out the line from the previous camera and uncomment or create a new entry for the camera. The camviewer configuration file can be found be found at /reg/g/pcds/pyps/config/cxi/camviewer.cfg.