Changes between Version 5 and Version 6 of TroubleShootingFads

Timestamp:

08/20/21 13:44:16 (3 years ago)

Author:

tbretz

Comment:

--

TroubleShootingFads

@@ -4 +4 @@
 == Crate Reset
 
-There exist a script which will do the __Crate Reset__ automatically:
+Please use Smartfact or the script for a Camera Reset (former: "Crate" Reset). The following step-by-step instructions is mainly meant for experts during debugging.
+
+There exists a script which will do the __Crate Reset__ automatically:
 
 - dimctrl --quit --cmd ".js scripts/doCrateReset.js crate[n]=true"
 - n = number of crate you want to reset (e.g. crate2=true)
 
+Note that the current setup does not allow anymore to reset individual crates. So whatever option you give, the whole camera will be reset. This previous instructions explain how to start the script directly in a local instance of dimctrl. This is __not__ recommended. The recommended way is to use dimctrl to start the script in the dimserver. If you decide to start the script locally, make sure that the script that you start is the right one (i.e. in operator/scripts on newdaq/newdata).
+
 Crate Reset manually:
 
 - disable all FTUs (in the FTU tab of your screen session) ftmctrl/ENABLE_FTU -1 0
-- disconnect the 10 FADs in the crate, by clicking the LEDs
-- ftmctrl/RESET_CRATE x (x corresponding crate)
+- disconnect all FADs, either by FAD_CONTROL/STOP or if that fails by disconnecting them one-by-one
+- FPGAFTM_CONTROL/RESET_CAMERA
+- wait for 2min(!)
 - enable all FTUs (in the FTU tab of your screen session) ftmctrl/ENABLE_FTU -1 1
-- reconnect the 10 FADs, one by one with 3 seconds waiting in between (the FAD needs this time to boot)
+- reconnect the FADs with FAD_CONTROL/START or one-by-one
 
 == start up - connection problem