• Created by Unknown User (phansson), last modified on Aug 12, 2014

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

Compare with Current View Page History

« Previous Version 15 Next »

SVT DAQ channel map

Link to excel file.

 

SVT Hybrid EPICS

Instructions to run on hpstracker in group C

The epics setup for HPS has been checked to run on the zed board but is developed mainly on the hps tracker machine in group C. 

The development is based from the standard epics_example at:

/home/tracker/pelle/epics/example

and is currently on SVN: 

svn://svn.freehep.org/hps/epics/trunk

NOTE: I should fix the SVN so that I can commit our SVT code separately from the IOC code which enables the transition between the arm and intel environments to be smooth. Right now I only checked out the interesting folders (src and db stuff) into the hpstracker and work on those ignoring the setup scripts that was originally checked in from the arm setup on the zed board. 

Instructions
Start IOC

Setup EPICS environment (part of the DAQ setup script):

$ cd /u1/software/software_new

$ source setup_env.csh

Go to the IOC base directory:

$ cd /home/tracker/pelle/epics/example/

Start the IOC

$ cd /home/tracker/pelle/epics/example/iocBoot/iocmyexampleApp

$./st.cmd

This should run the epics IOC and you should see output to the screen where it queries the socket for information. Depending on the debug level (see below) there might be lots of output here. If there is no control server running or it's not configured properly (see below) you should see it retrying to connect. 

Setting up the control server

Power the FEB

Start the control server and GUI

$ cd /u1/software/software_new

$ source setup_env.csh

$ ./bin/frontEndTestGui &

If the IOC is running (if not start it) you should see that the IOC now gets information from the control server. 

NOTE: if you don't see a connection you might need to change the TCP/IP settings (see below).

Setting up for editing or running the SVT slow control GUIs

Setup MEDM environment (part of the DAQ setup script):

$ cd /u1/software/software_new

$ source setup_env.csh

Go to the SVT MEDM directory:

$ /home/tracker/pelle/epics/medm_hps

This directory is also in SVN at 

svn://svn.freehep.org/hps/epics/trunk/medm_hps

Start GUIs:
Temperature:
$ medm svtTempSensors.adl &
 
Power supply:
$ medm svtStatusPS_latest_onoff_control.adl &
Hybrid GUIs:
$ medm hps_svt_hybrid_LV_bot_1.adl &

For execution mode:  click "Execute" mode in the mddm X-window that pops up. 

Change debug output

Change debug level in  /home/tracker/pelle/epics/example/iocBoot/iocmyexampleApp/st.cmd (0=least) by changing line:

var mySubDebug 0

 
Notes
6/24/14

 

  • Alarm handler
    • Add two hybrid temperature and the front end board temperature to alarm handler. 
       
  • Front End power supply GUI:
    • Can we add a button at the top that turns ALL ON/OFF?
    • Also we might want to make a GUI that has only monitoring and ON/OFF and small expert GUI’s for each FE board where we can set voltages? Similar to for the hybrid.
    • Can we link the ALL ON/OFF so that ANAN and ANAP is turned on at the same time followed by DIG  (not exact delay is not critical). 
    • The individual “LV ON/OFF” shouldn’t be linked together.
  • Main Status GUI:
    • During stable running I think it make sense that a shifter has this as a kind of main as it is the most directly linked with the modules. 
    • If we want it to control the full system (i.e. the capability to power the whole SVT from scratch) we should probably add (from the top going down if possible on the GUI)
      • Flange board power button
      • Front End board Power button
    • I don’t know if need to control everything from this GUI, in my instructions I ask people to find the individual GUI’s and power from there but I thought I’d bring it up for feedback. The links to the individual GUIs might be ok if you ask me. 
    • There is a “SVT ALL ON/OFF” at the top. What is that doing? I think it would turn on all the “Front End” since they are powered directly from MPODs? Anyway I would remove it as powering the FE and Flange is equally important and actually the FEB will not respond without Flange power. 
    • I think we don’t need the set point for bias on this GUI since we are, at the moment, not expecting to turn it on/off from here?

 

  • No labels