You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Current user stages should be entered here. This page 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 configurations 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. As more stages become available in LCLS, the page should also be updated. Also seeing as though some stages under the same name can be outfitted with a gear reducer, these configurations should be saved within the parameter manager and the confluence page updated

The procedure for setting up IMS/dumb motor stages:

  1. Open the confluence page and look for the stage you will be using and note its corresponding parameter manager name. If a new stage is being used, discuss with your local ECS staff member on the support available.
  2. Open the questionnaire for the specific experiment and navigate to the "CDS" tab
    1. You will notice that there is a space to enter information about the various motor stages needed. The information entered in these columns allows the stages to be automatically loaded into the local hutch python sessions and the archiver without the need for manual additions to separate experiment files. Scientists and ECS staff work can together to populate these columns.
      1. Purpose -
      2. python/archive name -
      3. Stage Identifier -
      4. Location  -
      5. Base PV -
  3. Fill in the necessary information to the best of your ability. Keep in mind that the stage identifier should match exactly what can be found in the parameter manager (i.e. confluence page)
  4. Begin the experimental set up of your motors and stages.(i.e, affix to the beamline, connect cables to appropriate motor controllers, etc...). Contact your local ECS staff member if assistance is needed during this step.
    1. If you haven't input the base PV in the questionnaire before this step, now is the time since all motors should be connected to a smart/dumb motor controller channel. The controller should be labeled with some information regarding the base PV of each channel or found in hutch documentation.
  5. Open a terminal and start a new hutch python session (i.e. <hutch>3) on the specific hutch machine (i.e. <hutch>-control, <hutch>-daq, etc...).
    1. You will notice that among the devices loaded on the screen, there should be a section that loads in the experiment questionnaire. Following this you will be prompted with the motors for which the specified configuration differs from the current motor PV parameters. Later you should run x.<python name>.diff_configuration() **needs to be coded**. This command brings up all the parameters that have changed.
  • 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)
  • No labels