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.
...
Instructions for hybrid power control
1. Start IOC
Setup EPICS environment (part of the DAQ setup script):
...
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.
2. Setting up the control server
Power the FEB
Start the control server and GUI
...
NOTE: if you don't see a connection you might need to change the TCP/IP settings (see below).
...
Power control GUIs
Setup MEDM environment (part of the DAQ setup script):
...
$ /home/tracker/pelle/epics/medm_hps
This directory is also in SVN at
svn://svn.freehep.org/hps/epics/trunk/medm_hps
Start GUIs Start ALL GUIs using scripts:
$ medm svtTempSensors.adl &
$ ./runSVTGUIs.sh x
Individual GUIs can be opened with
$ medm gui-name.adl & (if you don't add -x it will open in edit mode and you'll have to hit "execute" in one of the windows popping up.
Changing debug output for hybrid IOC
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.
Changing debug output
The debug level for the subProcess (essentially stuff in myexampleApp/src/dbSubExample.c) is controlled by "int mySubDebug". (0=least output)
This can be controlled from the IOC startup script /home/tracker/pelle/epics/example/iocBoot/iocmyexampleApp/st.cmd by changing line:
The debug level for some of the low-level SVT code is controlled by "int client_util_debug" which is in myexampleApp/src/client_util_debug.c
Hybrid IOC development
Compiling source and DB
$ cd /home/tracker/pelle/epics/example/myexampleApp
...