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

Compare with Current View Page History

« Previous Version 8 Next »

If something is not working, try troubleshooting steps here first, then call Divya at (929) 247-0432 if urgent, or make a JIRA ticket if not urgent. If Divya doesn't pick up, follow the LCLS Instrument Support Escalation Tree (ECS & DS).pdf

Confluence

Control Room Machines

  • Types:
    • cxi-daq connected to primary daq
    • cxi-monitor: connected to secondary daq
    • cxi-console and cxi-control for general use
  • If screens are out of order, open a terminal and run ‘nvidia.sh
  • To share screen on  ‘showcam show 2’ or ‘showcam show 1
    • One is for the top-right screen of cxi-daq
    • The other is for the top-left screen of cxi-monitor
  • Workaround for when encountering F-12 and F-11 Keyboard shortcuts not working 
    • Restart the gnome shell by pressing, ALT + F2 , typing "r" in the Enter command window. 
    • Reapply the gnome settings by running "gnome-settings.sh"  
    • This seems to be an issue with the red hat and has been observed in other hutches as well. SLAC IT has an open ticket with red hat for the same. Moving this to resolved for now CXI Specific issue. 

EDM Screens

  • Green: Nominal and working
  • White:  IOC is intentionally powered off or problematic , ioc not visible, check in iocmanager to see if the IOC is off. 
  • Pink/Purple: Communication is not achieved. Verify digi/moxa cable is correct and connected, click on reinitialize, if that doesn't work try  rebooting the IOC 

Apps

camViewer

  • camViewer -h   (help options)

  • camViewer -l   (list camera names)
  • camViewer -c <camera name>   (open camera screen)
  • camViewer -c <camera name> -r   (reboot camera ioc)
  • camViewer -c <camera name> -m   (open EDM screen)

EDM screen can be used to debug or change settings.

Check gain, exposure time, acquisition time, trigger mode, and event code.

Some issues can be fixed by clicking the Stop then Start buttons.

IOC Manager (command : iocmanager / iocmanager cxi)

  • Used to turn on/off an ioc

  • Columns ( Refer the image above)
    • Alias: Nicknames for ioc
    • IOC ID : Actual names of1446px the ioc
    • State: Whether it is on/off (Dev and Prod mean on)
    • Status: solid status, RUNNING means the IOC is on. 
    • Host: server the ioc is running on
    • OS: to denote if it is a rhel5 or rhel7 IOC. 
    • Port: port on the server the ioc is accessible at (must be unique from other iocs on the same server)
  • IOC Control drop down

    • Soft IOC reboot
      • Choose this first!
      • Writes to a PV, telling it to restart
    • Hard IOC reboot
      • Second option
      • Tells server to kill the ioc and restart it
    • Reboot Server
      • Last resort since it will restart all iocs running on that server
      • At this point, call/contact Divya, before continuing
      • Takes more time and could kill other IOCs that should not be killed

striptool

<to do>

Motor Expert Screen

  • Example: PIM /YAG 1
    • FIND on CXI home screen in array of green buttons or
    • Command: motor-expert-screen CXI:DG1:MMS:08 
  • If motor position doesn’t seem right, try to re-initialize first.
  • Set parameters(dial vs user):
    • Offset: set dial to be zero , maybe at limit switch, and user set at interaction point
    • Neg/Postive: since in y-direction, going positive actually is negative, so it is switched with these buttoms
    • Do not mess with, UNLESS comfortable: run current/percentage
    • Can move with velocity if experiment requires it
    • Velocity vs speed:
      • V: actual speed in ml/s
      • Speed: rev/s
      • Acceleration: requires calculations
    • If something is not moving: CHECK the comments given in the ‘log messages’
      • Power cycled error
        • Button will show to power-up
        • If not, go into Aux setting: Command response, type ‘pu 0’
          • At the bottom right
        • Error 92:
          • Closed loop postioning error
          • Check the size of deadband
            • Go into aux settings, Command response,type ‘pr db’ or if specific position, ‘pr db 10’
              • At the bottom right

Shell Commands

Run command -h for helptext

serverStat

  • Can be used to cycle a server.
  • e.g. serverStat daq-cxi-master cycle

netconfig

  • Use to find information about the server. Location could be useful if you need to power cycle it in person.
  • e.g. netconfig search daq-cxi-master

motor-expert-screen

  • Open motor expert screen for a certain motor given its PV. Useful if you can't find it on the EDM screen.
  • e.g. motor-expert-screen CXI:PI1:MMS:01 


Grafana

  • In firefox>pswww website>log in> controls Grafana> Dashboards, manage> CXI
  • In Grafana> create>empty panel
  • Used to check any PVs of interest
  • Can look into their history
    • Change timeframe to whatever is of interest
  • To copy and paste: use middle click
  • Can also click on stream: for current state, without the need to refresh

Jungfrau

  • Controls found on CXI home > Detectors tab
  • Documentation and Troubleshooting:
  • takepeds & makepeds:
    1. Configure DAQ
    2. takepeds
    3. makepeds -u <username> -r <run #> -q ffbh3q
    4. (If missing geometry) makepeds -u <username> -r <run #> -g cxic00120

DAQ

  • Use 'restartdaq' to open the daq (there's no 'startdaq' command)
  • Event Codes / Timing
    • Change on the DAQ Control Window: Edit>EVR>Event Codes
      • Set one code to 'Readout' to define when the DAQ records data
      • Set codes to 'Command' to have their states for each shot recorded in the data
    • Event codes:
    • To record only when the sequencer fires, set the DAQ to readout on 187 and put 187 in the sequencer

AMI

  • Will automatically open with the DAQ
  • If you need to restart it or open a second viewer, use 'startami'







  • No labels