Page History

...

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 motor object has a function called "<motor>.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 expert screen from the motor python object <motor>.expert_screen(), 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.

...

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. <that is NOT what happened in XPP on 2/5/18> 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). Dumb motor recognition does rely on the parameter manager knowing the serial numbers of the dumb motor controllers. Should you have a new chassis or a newly repaired one, this might not work and PCDS personnel will have to fix this.

Expert guides (restricted viewing)

...