Controls User Guide

Controls Camera User Guide

For XPP/XCS, there is a convenience scripts for Gige cameras that can be called from the command line called "gige".

"gige -h" will list the available options. If no option is passed, you will get a list of cameras to choose from. By default, the camera viewer described here will be opened for the requested camera. The camera name can be passed using the "-c <cam #/cam name>" options. If you pass "-m" in addition to the "-c XXX" argument, you will get the expert edm screen. Should the viewer not work (e.g. not update), open the edm screen and start simple trouble shooting described here(to be made). If you have a gige object defined in <hutch> python, you can also start the expert screen by using the <gige>.expert_screen() command.

If you would like to record your controls camera in the xtc stream along with the DAQ data, contact your PCDS-POC. The IOC will need to be build with support for timestamps so that images can be assigned to events. After that, they can be added to the DAQ under the "Camera IOCs" section.

EPICS trouble shooting

 If a PV gives you trouble, a first good step is to see if the IOC is up stably and possibly reboot is. For that you will use the IOC manager which has a user guide here. This guides describes how to start it and how to it works. More detailed information for commonly used IOCs can be found

IPIMB

See IPIMB Troubleshooting for Controls IPIMBs.

Motor expert screens

Motor screens can be found in various formats at various places in the different hutches. If you are interested in the "expert" screen for most of our motor types, you can use

(/reg/g/xpp/scripts/)motor-expert-screen <PVNAME> where PVNAME is e.g. XPP:SB2:MMS:19

This script will bring up the right kind of motor screen (old & new IMS as well as Newport screens). In hutch python, you can also start the motor expert screens my using <motor>.expert_screen().

Newport screens are described here.

Link to the old "Controls User Guide"