# Presentation: 445847

## When to Turn HV ON

- HV can be turned **ON **after the detectors are powered
- under two conditions:
- _No Beam_:  If there is no beam of any kind in the Tevatron, then it is safe to bias powered detectors.  Biasing is typically done at such times for commissioning or calibration studies like SDAQ runs.
- _Clean, Stable Beam_: This is the case *after* shot setup, injection and scraping have been *successfully* completed.  Check with the shift captain to confirm the status of the beam.

_**When to Turn HV OFF**_

- HV must be turned **OFF** *before*:
- _Shot Injection_:  The detectors cannot be biased when beam is first put into the Tevatron.  During shot setup, check with the shift captain to ascertain the accelerator schedule, and start turning off the HV at least 20 minutes before injection.
- _End of Store_: HV must be turned off before the beam is dumped.  Again, check the schedule with the shift captain, and start turning the HV off several minutes before the end of store.
- _Beam Studies_: No HV during any accelerator studies.

## Global HV Monitoring & Control GUI

- To run the global HV GUI:                                                   Open a terminal window on the upper SMT monitor, and then
- > setup d0online
- > cd /online/config/smt/hv
- > ./hv_det_mod.py smtAll.hvd &

- This is a representation of all the HV crates in MCH2.  Each colored rectangle represents one HV pod, and each crate is designated by its name (e.g. smts1).  Note that smts9 and smtnA are actually one crate with some South pods and some North pods.

## Global HV Monitoring & Control GUI

**OFF**: turn off pods

**ON**: turn on pods

**RAMP**: start ramping pods to set voltages

**Set HV**: pull-down menu to define set voltages

**UNLOCK**: unlock locked pods

**LOCK**: lock pods at current settings

**RESUME**: resume paused ramping

**PAUSE**: pause ramping

**RESET**: reset tripped pods

- Pod states are indicated by color:
- Blue: turned OFF
- Orange: turned ON
- Yellow: ramping
- White: paused
- Light Green: OK, ramped up
-    and holding at set voltage
- Dark Green: locked
- Flashing Red: tripped
- Flashing Black: disabled

## Ramping Procedure

- Start the Global HV crate GUI		 		> setup d0online 		 		> cd /online/config/smt/hv	                   	> ./hv_det_mod.py smtAll.hvd &
- _Ramp-Up_:
- Turn on all pods: click the **ON **button
- Set the target ramping voltage for all pods: use the **Set HV** pull-down menu and select “**100% + underdepletion list**”
- Start ramping: click the **RAMP** button
- If any pods trip (i.e. start flashing red), click the **RESET** button *immediately*, and then click **RAMP** again.
- When all pods are fully ramped and holding (i.e. green), lock the pods: click the **LOCK** button.
- _Ramp-Down_:
- Unlock all pods: click the **UNLOCK **button
- Set the target ramping voltage to “**0%**” with the **Set HV** pull-down menu.
- Start ramping: click the **RAMP** button
- If any pods enter a **PAUSED** state (i.e. white), click the **RESUME** button to continue ramping.
- When all pods have ramped down to less than 5 V, turn off the pods: click the **OFF** button*

## Crate HV Monitoring & Control GUI

_**Crate HV Monitoring & Control GUI**_

- A page for each HV crate

- To run this GUI:
- > setup d0online
- > cd /online/config/smt/hv
- > ./smt.hvc

- The Crate GUI is particularly useful for working with
- individual pods and troubleshooting (resetting trips, tracking currents, etc.).

## Crate HV Monitoring & Control GUI

_**Crate HV Monitoring & Control GUI**_

**State**: shows current state of the HV pod

**I_Read**: bias current reading

**V_Read**: bias voltage reading

**V_Set**: bias voltage set point

**V_Max**: bias voltage maximum
-             (i.e. bias voltage for full depletion)

**I_Max**: bias current trip point

**V_Trip**: bias voltage hardware trip point

**Reset**: reset tripped pods

**Unlock**: unlock locked pods

**Lock**: lock  pods at current setting

**Resume**: resume paused ramping

**Pause**: pause ramping

**Ramp**: start ramping

**On**: turn on pods

**Off**: turn off pods

**Channel**: HV pod name

## Crate HV Monitoring & Control GUI

_**Crate HV Monitoring & Control GUI**_
**States and Actions**

**Off**: turned off, options from this state are:
- 	- **On**: turn on the pod
**On**: turned on but not ramped, options from this state are:
- 	- **Off**: turn off the pod
- 	- **Ramp**: ramp the pod to **V_Set**
**Ramp**: ramping to **V_Set**, options from this state are:
- 	- **Off**: turn off the pod
- 	- **Pause**: pause the ramping
**Paused**: ramping has paused, options from this state are:
- 	- **Off**: turn off the pod
- 	- **Resume**: resume ramping to **V_Set**
**Holding**: ramping to **V_Set **completed, options from this state are:
- 	- **Off**: turn off the pod
- 	- **Ramp**: ramp to **V_Set**
- 	- **Lock**: lock the pod at its current setting
**Locked**: locked at current setting, options from this state are:
- 	- **Unlock**: unlock the pod
**CX OC/CX OV**: tripped (overcurrent/overvoltage), options from this state are:
- 	- **Reset**: reset the pod to **On**
- Pod states can be changed globally using the buttons at the bottom of the GUI,
- or individually by clicking on a pod’s **State** box.

## Troubleshooting

- Some pods may trip while ramping up, holding, or ramping down. For most
- trips, all that is required is:
- Reset the tripped pods: click the **Reset** button
- Ramp the reset pods: click the **Ramp** button.
- Sometimes if a tripped pod is not reset quickly, **V_Read** drifts to a voltage
- of the opposite polarity.  In these cases, the pod is serving double-sided
- detectors, and is being pulled to the opposite side voltage.  The tripped pod
- cannot be reset until its partner has been ramped down.
- Ramp down the tripped pod’s partner (this may take several minutes).   Be sure to **Lock** all other pods if using the **Set HV** pull-down menu, or else enter the target value for the voltage directly into the pod’s **V_Set **field.
- Reset the tripped pod: click the **Reset** button.
- Set the pods’ target voltages with **Set HV** or **V_Set**.** **
- Ramp the pods: click the **Ramp** button.
- If a pod cannot be ramped to its full (or underdepletion – see next section)
- voltage, ramp it to as high a percentage as possible without causing a trip.  In
- the unlikely case that a pod for a double-sided detector cannot be ramped at
- all, do not turn the pod **Off**.  Set the voltage to 0 V and **Ramp**.  If the pod is
- turned **Off**, it will drift to the opposite side voltage resulting in no bias at all
- for the detector.
_**Underdepleted Detectors**_
- Some detectors cannot be ramped to full depletion.  There is a list of HV
- pods that are only to be ramped to a fraction of full depletion.  These
- fractions are automatically loaded when “**100% + underdepletion list**” is
- selected from the Global HV GUI **Set HV** menu.  However, when ramping
- pods individually or with the Crate HV GUI, check the list and only ramp
- underdepletion pods to the indicated percentage. Then, **Lock **those pods so
- that they will not be ramped further.

_**Troubleshooting**_

## Troubleshooting

- 	The StripTool utility allows tracking of bias voltages and currents.
- This is very useful for debugging problem HV channels.  A StripTool chart
- can be launched from the command line by:
- > setup d0online
- > StripTool &
- In the Control window, enter a signal name (e.g. SMT_HVC_101P/VOLT,
- SMT_HVC_101P/CURR) and click **Connect** to start the graph.  Plotting
- parameters can be modified in the Control GUI.
- 	StripTool charts for HV pods can also be launched automatically
- from the Crate HV GUI by left-clicking on a HV pod’s name in the **Channel**
- field.

_**Troubleshooting**_

## Troubleshooting

- 	Any information related to actions taken with the HV system should
- be logged in the electronic logbook.  In addition, problems with particular
- HV pods should be entered into the Commissioning DB
- (_[http://d0server1.fnal.gov/projects/silicon/run_2a/d0smtcommissioning/database/database.asp](http://d0server1.fnal.gov/projects/silicon/run_2a/d0smtcommissioning/database/database.asp)__)._
- Click on a pod to pull up its history, and then enter a “**New Rec**”.

_**Troubleshooting**_

## Troubleshooting

- 	A HV crate trip is indicated by a flashing red crate name bar in the global HV GUI.  In all likelihood the trip is due to a Rack Monitor trip in the HV rack (M220,M221, or M222).  To reset a crate:
- Identify and correct the cause of the crate trip
- Go to MCH2 and check if the RM has tripped.  If so, press the **Reset Alarms** button to reset the RM.
- Click on the flashing crate name in the global HV GUI
- Click **Reset **in the window that pops up.

_**Troubleshooting**_

_**Resetting Pods Tripped During Crate Turn On**_
- 	Sometimes when a whole crate is turned **On**, a lot of the HV pods will immediately trip without ramping them.  Resets from the global GUI or crate GUI will not reset these trips.  To reset pods tripped in this manner:
- Click on the crate name in the global HV GUI.  A detail window will pop up showing all the HV pods in this crate.
- Click on the **Reset** button in this detail GUI.

## Finding HV Pod/Channel Info

-    There are several ways to obtain HV information for a particular channel.  Either of the following may be more useful depending on what you are doing.
- _Download GUI_:  If you are working with the download GUI, then you
-    can conveniently find HV information for a complete interface board.
- 		              Click this...
- 		                 ...and get this...
-    ...giving HV information and control for each channel on that
-    interface board.  A HV GUI for the entire VRB crate can be obtained
-    by left-clicking on the VRBCR_# button and selecting “HV GUI”.
- _Command line_:  HV information for a particular detector or IB channel
-    (e.g. B2-4-6 or SMT_IB_NE0A04-C) can be obtained by:
-  cd ~d0smt/monitoring
-  show_det_info.py B2-4-6
- 	or
-  show_IB_info.py SMT_IB_NE0A04-C
-    which will produce
-    a window, which
-    shows the HV pods
-    connected to that
-    detector/channel, and the
-    other detectors/channels
-    connected to those pods.

_**Finding HV Pod/Channel Info**_

## Finding HV Pod/Channel Info

- _Commissioning DB_:

_**Finding HV Pod/Channel Info**_

- Web DB Pics go Here

## Finding HV Pod/Channel Info

- _Commissioning DB_: from the “HV testing” display... (_[http://d0server1.fnal.gov/projects/silicon/run_2a/d0smtcommissioning/database/database.asp](http://d0server1.fnal.gov/projects/silicon/run_2a/d0smtcommissioning/database/database.asp)__)_
- 					    Click on a pod, to
- 					    get its history.
-   Click on the pod name
-   to get details on all the
-   devices connected to it.

_**Finding HV Pod/Channel Info**_

## Finding HV Pod/Channel Info

- _Command line_:  A window showing the devices connected to a
-    particular HV pod (e.g. 133N) can be obtained by:
-  cd ~d0smt/monitoring
-  show_hv_info.py 133

_**Finding HV Pod/Channel Info**_