All user stages should be entered in what is currently a google document (link in procedure below). This document lists the part number, has a link to manufacturer documentation and gives each stage a "name". This name corresponds to the configuration in the parameter manager which contains all the settings of the controller that make the stage work well. Entering this name in the questionnaire for a beam time will enable a single command to push all the right settings to the motor controller after the stage has been connected. These configuration are shared among hutches as stages are moving between hutches. This list is also shared with the beam line engineer/designer so that they know what stages are available when planning an upcoming experiment. The idea behind this process is outlines in this presentation.
During the 2018 shutdown, work will happen to populate the spreadsheet with all user stages that could easily be located.
The procedure will evolve, but is currently as follows:
- open the motor spreadsheet
- pick a stage
- ideally, you would add some load to the motor the mock up a read experiment
- connect it to the current smart/dumb motor channels wherever you will test (preferably a HXR hutch so that the command used below are easily available)
- reboot the IOC (using the "findPV" function of the iocmanager, the needed PV should be gotten from the label on the PPL and/or the hutch documentation
- locate a hutch python session (in XPP this should be done by typing "xpppython" in a terminal)
- for now, the user motors on SB4 will make names like "userMotor_SB4_33" where the last number is the last two digits of the basePV the motor has been hooked up to
- open the expert GUI by using "x.userMotor_SB4_<xx>.expert_screen()"
- click on aux setting and move that screen next to the main screen.
- have a view of the stage (either by being next to it or by opening a webcam that has sight to where ever the motor is set up)
Overview
Content Tools