Pulse Picker Edm Screens

Image Added

                 Image Added                    Image Added  

Fig 1. pp_mode_control.edl waiting for mode selection                                                                      Fig 2. pp_mode_control.edl, Pulse picking mode has been selected                                                        Fig 3. pp_mode_control.edl, Blade position unknown motor, homing required

Image Added

Fig 4. pp_gui.edl

• pp_mode_control.edl

  • Shown in Fig 1. through Fig 3.
  • User screen for pulse picker motor
  • Displays current motor status including: blade position, pulse picker mcode status and version, fan status, limit violations, error mode, mcode heartbeat, and selected pulse picking mode.
  • Contains buttons to select pulse picking mode and perform  perform a hard reset of the pulse picker mcode. 
  • Contains button to open to open pp_gui.edl, labeled CNTRL.
  • The edm macro for the screen is MOTOR=<Motor Base PV>, ie edm -x -eolc -m "MOTOR=CXI:ATC:MMS:29" pp_screens/pp_mode_control.edl &

• pp_gui.edl

  • Shown in Fig 4.
  • Expert screen for pulse picker motor
  • Contains all displays and controls contained the in pp_mode_control.edl screen
  • Contains displays and controls for all variables for pulse picker Mcode.

• Pulse picker screen logic

  • Both screens have built in logic to assist the user in the correct operation of the pulse picker, the logic is the same for both screens.
  • If the user has selected a mode for the pulse picking motor all of the mode selecting buttons will become invisible until the motor has been returned to 'Waiting for Mode Select'. This logic is show in Fig 2.
  • If the position of the pluse picker blades is unknown, DF=99, only the home motor button will be shown to the user and the user will be shown a message stating that the motor needs to be homed. Once the blade position returns to a know position the other buttons will become visible. The homing process takes a few seconds. This logic is show in Fig 3.

• Pulse Picker Screen Launch Script

  • The script edm-pp-screens.cmd can be used to launch the pp_mode_control.edl screen with the correct motor name for each hutch
  • To launch screen for a specific hutch pass the three letter acronym of the hutch to the script, the script will accept upper, lower and mixed case arguments. 
  • Currently the script is located in: /reg/neh/home/alexd/ioc/common/xip_pp/current, the script will be moved to a release at the next update to the pulse picker ioc.
    
    

  Code Block
  language bash title edm-pp-screens.cmd
  $ ./edm-pp-screens.cmd mec

   

   

Epics IOC

Motor Interlocks

• If pules picking motor is in pulse picking mode, $(MOTOR):SE_L != 0, X and Y stepper motors are disabled
• If Y motor position is greater than 10mm X motor is disabled
• If X motor position is greater then 5mm or less then -5mm Y motor is disabled.
• Interlock records can be found in the 2-axis-control.sub-db file.

Records located in xip.template

...

• Raw pulse picking mode select number
• Reads Se from Mcode
• Returns number corresponding to selected pulse picking mode\
• See Pulse Picker MCode Pseudocode & Reference for number description

...

• Sends a hard reset to the Mcode
• Sets Se to 99
• Executes program 1
• Most variable used in the pulse picking mcode will be reset to standard values.
• Motor will need to be re-homed if this is called

...

• Resets pulse picking mode
• Sets Se to 0
• Mcode will see Se=0, branch to close , the blades then return to mode select

...

• Mcode Heartbeat
• Reads HB from mcode
• Passive scanning
• Scanned at IOC start

$(MOTOR):NS

• Pulse picker mcode version
• Reads NS from mcode
• Passive Scanning
• Scanned at 1 secondIOC start

Records contained in xip_evr_seq.template

...

Info
title EVR SEQ Records
All records in template do not have inputs or outputs. They are read by python module to select proper pulse selecting mode

...

• Tasks to complete for PP ioc
  • Add records to write to desired sequencer and evr records and hold desired information
  • Edit EDM screen to reflect changes to ioc
  • look in to turning on scanning so motion is displayed on screens, may be covered by MV scanning
  • Update confluence page