Skip to content
Snippets Groups Projects

29idcScienta IOC

Components

Camera

ArrayFxns

LabVIEW control

Operation

Note currently only BabySweeps have been setup

softIOC startup

Start up IOC on surly (connected to camera) as 29id

/home/beams/29ID/bin/29idcScienta.sh start

LabVIEW Bridge

Start up ScientaBridge software (on Glick)

  1. Open D:\LabVIEW code\ScientaBridge\ScientaBridge.lvproj
  2. A message box will probably pop indicating that some LabVIEW package has expired. This can be ignored and you can simply press "Launch"
  3. Once the Project Explorer opens up, click on Main.VI (In the "Items" tab within Project: ScinetaBridge.lvproj::My Computer.
  4. When the Front Panel pops up, click the white arrow to start the VI.

LabVIEW notes

If the IOC crashes, you'll have to restart the bridge program.

Setup and Run Baby Sweep

  1. Pull up Scienta UI (29idcScienta.ui)
    • From terminal, navigate to /net/s29dserv/xorApps/ui
    • Run start_caQtDM_29idcScienta
  2. set element set, lens mode, pass energy
    • "High Voltage" button on 29idcScienta.ui leads to ScientaHV.ui where values can be entered
    • PVs:
      • element set: 29idcScienta:HV:ElementSet
      • lens mode: 29idcScienta:HV:LensMode
      • pass energy: 29idcScienta:HV:PassEnergy
  3. load baby sweep config
    • Method 1
      • "HV Scan" button on 29idcScienta.ui, choose "scan1Menu"
      • Load "babySweep"
    • Method 2
      • Choose "Spectra" for Acquistition mode on left side of 29idcScienta.ui
      • Click Baby-Sweep" from the subsequent Spectra mode
  4. set center energy of baby sweep by either
    • entering a value in CenterEnergy in Scan/Spectra Parameters box in 29idcScienta.ui OR
    • putting directly to PV (29idcScienta:HV:babySweepCenter.VAL)
  5. The number of steps for baby sweep is set to 51 but can be changed by puts to 29idcScienta:HV:babySweepSteps.VAL
  6. The step energy (29idcScienta:HV:babySweepStepSize.VAL) is determined directly from the Pass Energy
  7. start scan by either
    • pulling up scan #2 under "HV Scan" button and pressing "Scan" OR
    • proc'ing 29idcScienta:HV:scan2.EXSC
  8. In the scan.ui the Kinetic energy values are truncated/rounded. More precise values can be monitored either by:
    • the PV directly (29idcScienta:HV:KineticEnergy.VAL)
    • ScientaBridge on Glick OR
    • by opening the arrayFxnsDebug.ui which is accessed by clicking the NDDriverStdArrays button on the 29idcScienta.ui and choosing ArrayFxns (this also displays a bunch of other values needed for the compilation of arrays and is good place to check if images seem off)

Setup and Run Fixed Sweep

Steps 1-3 are basically the same except to choose Fixed instead of Baby-Sweep 4. Set energy of interest by either: * entering a value in FixedEnergy in Scan/Spectra Parameters box in 29idcScienta.ui OR * putting it directly into PV (29idcScienta:HV:fixedEnergy.VAL) 5. Set number of images to be compiled by either: * entering the desired value in CompiledImages entry on right side of 29idcScienta.ui OR * putting it directly into PV (29idcScienta:ExpFrames.VAL) 6. start scan by either * pulling up scan #2 under "HV Scan" button and pressing "Scan" OR * proc'ing 29idcScienta:HV:scan2.EXSC

General Notes

  1. Lens mode readback (29idcScienta:HV:LensMode) reports Transmission as "Transmissio" which shows up as an error in IOC console
  2. Element set updated whenever PV (29idcScienta:HV:ElementSet) changes 3 Lens Mode and Pass Energy PV values aren't set to Scienta until Kinetic Energy changes --> if Lens Mode and Pass Energy are invalid, then error won't pop up until kinetic energy changes
  3. Validity checks on Pass Energy are currently not setup (it had been previously in the PyDM interface)
  4. still need to setup sweep and fixed scan configs