= Trouble Shooting - Hardware

== Power Cycling the camera

__Symptom__

- A Crate Reset didn't solved a FTU or FAD problem

__Solution__

- stop all scripts: dimctrl --stop from a bash
- set bias to 0:  - BIAS_CONTROL/SET_ZERO_VOLTAGE
- Stop Trigger: 
 - FTM_CONTROL/STOP_TRIGGER
 - or Stop Trigger in the left part of the GUI
- FTM_CONTROL/DISCONNECT
- FEEDBACK/STOP
- if fadctrl is in state WritingData
 - FAD_CONTROL/CLOSE_OPEN_FILES
 - fadctrl now should be in state connected
- FAD_CONTROL/STOP

Now __power cycle__ the camera

0. Switch off the agilent camera in the FACT Container
 - open the page 10.0.100.100 from a computer in the internal network of La Palma (can be your computer if you use vpn)
 - push 'Camera Off' to stop the camera (now only 'Bias Power' and '24VDC Interlock Power' should be 'yes')
0. wait for about 15 min
0. switch the agilent on
 - open the page 10.0.100.100 from a computer in the internal network of La Palma
 - push 'Camera On' to start the camera (now all 5 points should be 'yes')
0. make sure that clock-conditioner is locked
0. follow the [[preparation#startup Start-Up procedure]] to get the system running again

To check if the __clock-conditioner__ is locked, you may check in the gui in the tab 

- 'Trigger' the led next to the pulldown 'DRS sampling frequency'
- 'FAD' with mouse over on the LED next to 'Reference Clock' whether all 40 values are roughly 1/1024
(some more information in a post by Patrick: https://www.fact-project.org/logbook/showthread.php?tid=1102&pid=6070#pid6070 )

== Switching off the bias crate
In case you need to switch off the bias crate, please do first BIAS_CONTROL/DISCONNECT