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

Compare with Current View Page History

« Previous Version 12 Next »

XIP Pulse Selector: Files, modes, schematics

EVR Settings:

In case the server ioc-tst-cam5 was power cycled:
  1. Connect to the server: 
     ssh ioc-tst-cam5
  2. Run the startup command that contains EVR ioc in: 
     sudo /reg/d/iocCommon/sioc/ioc-tst-cam5/startup.cmd
  3. You should see with psproc: 
     [paiser@ioc-xrt-xcscam04 ~ 12:18:20] psproc
 PID   USER-ID   SIOC                      COMMAND   HOSTNAME            PORT
 4851  tstioc    caRepeater                procServ  ioc-xrt-xcscam04    30000
 5147  tstioc    ioc-tst-cam5              procServ  ioc-xrt-xcscam04    30001
 5150  tstioc    ioc-tst-cam5              procServ  ioc-xrt-xcscam04    40000
EVR startup script from pslogin:

Note: you need to have your securekeys.

ssh ioc-tst-cam5 evr.sh EVR=TST:CAM:05:EVR
In case you need to power cycle ioc-tst-cam5 do:
 ipmitool -I lanplus -U ADMIN -P <you_should_know> -H ioc-tst-cam5-ipmi power status
 ipmitool -I lanplus -U ADMIN -P <you_should_know> -H ioc-tst-cam5-ipmi power reset

Where: <you_should_know> is the standard ipmi password that you_should_know...

Test Screens

Python homing script:
/reg/neh/home1/jsludvik/test-python/xip-home.py

XIP main GUI:
/reg/neh/home1/jsludvik/svn/trunk/ioc/xpp/xip_pp/current/motionScreens/xip_gui.sh

XPP motor GUIs:
/reg/g/pcds/package/epics/3.14/modules/pcds_motion/R2.3.4/launch-motor.sh XPP:TST:MMS:01
/reg/g/pcds/package/epics/3.14/modules/pcds_motion/R2.3.4/launch-motor.sh XPP:TST:MMS:02
/reg/g/pcds/package/epics/3.14/modules/pcds_motion/R2.3.4/launch-motor.sh XPP:TST:MMS:03

Startup.cmd:

/reg/d/iocCommon/sioc/ioc-xpp-trigger-ims/startup.cmd

Mode Descriptions

Mode 1: Single pulse
Mode 2: Continuous trigger

Mode 1 and 2 should be the same program, as the Seq will generate the pulses to the motor, and open/close operation shouldn't make any difference whether it is 1 or more. The motor sees a trigger and moves.

This mode is accessed by <PV>:RUN_MODE2

Mode 3: The motor opens on a pulse, counts N pulses and closes on the Nth pulse. The pre-trigger and close trigger should be factored in by the upper layer software to determine the proper N value to put into the motor. All the motor does is, open on N=1, count, then close on N=N.

This mode is accessed by <PV>:RUN_MODE3

Mode 1 was programmed like just mode 2 with a User "Trigger" enable/disable, which may or may not be useful for us. Sort of like 2 layers of enabling, versus just 1 for mode2
This mode is accessed by <PV>:RUN_MODE1

Homing Sequence

1) EPICS Motor Record: HOMF
2) Zero Position
3) Move Relative -76.25 degrees
4) Zero Position

MCode Program State Diagram

<insert VISIO diagram>
<code example>

Motor Interlock Scheme

Screenshots

Pulse Selector Test/Checkout Procedure (6/10/2013)

X motor calibration

  • Found offset from X zero position: 5.8075 mm from + limit
  • Offset for X zero position: 5.7332 mm from - limit
  • Limits performed as expected, and in place before hardstops

Y motor calibration

  • Offset from +Y limit to zero: 15.6689 mm
  • Offset from -Y limit to zero: 7.9956 mm
  • Limits performed as expected, and in place before hardstops

New Interlock:

Add Y motor interlock, position >= 2 mm above 0 position, no X movement allowed

X-Y interlock stopped working today, need to investigate.

1/ login in ioc-tst-cam5:

2/ cd /reg/neh/home1/paiser/bin

3/ evr.sh EVR=TST:CAM:05:EVR

then configure EVR...

If the evr is not connected, then:

4/ sudo /reg/d/iocCommon/hosts/ioc-xrt-xcscam04/startup.cmd

  • No labels