| | 1 | = Trouble Shooting - FTUs |
| | 2 | |
| | 3 | == ftm in state ERROR: |
| | 4 | |
| | 5 | __Symptom__ |
| | 6 | |
| | 7 | - ftmctrl in state ERROR |
| | 8 | - one FTU is not green in the FTU tab of the GUI |
| | 9 | |
| | 10 | __Solution__ |
| | 11 | |
| | 12 | - stop dimscript |
| | 13 | - dimctrl --stop from a bash |
| | 14 | - switch off the trigger and try *Ping* (FTU-tab) |
| | 15 | - a FTU can erroneously be marked as *in error* after the GUI has been restartet, a *Ping* resolve that |
| | 16 | - if this doesn't help do a Crate Reset (see <A HREF="#tscratereset">above</A>) |
| | 17 | |
| | 18 | __Not Helping__ |
| | 19 | |
| | 20 | - stopping fadctrl or ftmctrl |
| | 21 | - Reset other or all Crates |
| | 22 | - quiting or killing any program |
| | 23 | - power cycling the camera |
| | 24 | |
| | 25 | == ftmctrl in state ClockCondError: |
| | 26 | |
| | 27 | __Symptom__ |
| | 28 | |
| | 29 | - ftmctrl in state ClockCondError |
| | 30 | - clock conditioner is not locked |
| | 31 | |
| | 32 | __Solution__ |
| | 33 | |
| | 34 | - FTM_CONTROL/RESET_CONFIGURATION |
| | 35 | - or the MCP Reset button |
| | 36 | - make sure that the clock conditioner is locked before data taking |
| | 37 | |
| | 38 | __Not Helping__ |
