Page History

...

We have a convenience script for Gige controls cameras that can be called from the command line called "gige" camViewer. In case "which gigecamViewer" does not return anything, this script is located at /reg/g/pcds/engineering_tools/<hutch>/scripts. This should be on the path for <hutch>opr accounts if the currently existing .bashrc was sane enoughis following our common pattern.

"gige camViewer -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). You can reboot the IOC either using the iocmanager or adding "-r" to your gige camViewer command. "gige camViewer -c camID -n " will ask the IOC to start acquiring images again: when you put a camera back online, it will often not acquire and needs to be told to. A reboot does the same thing, but with a lot more overhead. If you have a gige object defined in <hutch> python, you can also start the expert screen by using the <gige>.expert_screen() command.

...

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

motor-expert-screen <PVNAME> where PVNAME is e.g. XPP:SB2:MMS:19

...

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

For a given PV you can also determine which server the IOC is running on and if rebooting the IOC does not help you can consider rebooting the server. Be mindful that this will restart all the IOCs on that server. ! One way to do that is using "serverStat <machine name> cycle" for any machine with ipmi. serverStat also has a "reset' option that should ideally be tried first, in particular for recorder nodes which have a RAID array. serverStat also takes DAQ devices names (aliases) or PVs (only for PVs originating from the same subnet). 

...

The configuration GUI for your IPIMB or Wave8 boxes can be started using: "ipmConfigEpics <-b boxname>". If you don't pass the "-b" option, you get a list of ipimb and wave8 boxes relevant for your hutch. 

A troubleshooting guide for ipimb boxes can be found here: IPIMB Troubleshooting for Controls IPIMBs.

...

Expert guides (restricted viewing)

Link to the old "Controls User Guide"