Page History

...

Newport screens are described here.

Motor setup

Newport

Turn XPS off before connecting motor!

Once everything is connected, turn XPS back on. Go to the IOC edm screen and reconnect, then click the "autoconfig" button. On success, a screen should come up telling you the motors the XPS found. Now your next steps are to initialize all motors and home or reference them. Now they should be accessible though the IOC.

To get them into your hutch python, you either have to:

(old python): add them to the correct epicsArch file. All motors found in the user/experiment specific file will be added to the "x" module (XPP/XCS).

(new python): motors added to the questionnaire (where they should be anyways) will be instantiated automatically.

IMS - smart motors

If you have a (old) hutch python (XPP/XCS), add the motor to the epicsArch file. A motor python object will be instantiated upon restart. This module has a function called "auto setup" which will initizlize the motor, clear the power cycle and check for a configuration based on matching the motor controllers serial ID in the parameter manager. Alternatively, you can open the exert screen from the motor python object, re-initialize from there & clear the power cycle. You can then use "<motor>.pmgr.diff()" to see the difference of current and saved configurations. "<motor>.pmgr.apply_config()" will apply the configuration. Check after applying the config that all parameters "made" it by calling pmgr.diff() on the same motor again.

IMS - dumb motors (HXR)

This works very similar to the smart motor procedure, except that the serial number cannot be used to find the configuration. You will need to  pass the configuration name to the "diff" or "apply_config" functions. If you don't, you will be asked. There is a search option where smart string matching is used when you don't know the config name. It is planned to alliviate this issue my labelling the stages with their config name (HXR).

Expert guides (restricted viewing)

...