= Trouble Shooting - Drivectrl

The list of states can be found in dimcrl (HowToDimctrl) or here
http://fact-project.org/FACT++/namespaceDrive_1_1State_a0620e65c19529fd0318fd5ec880f8df3.html


== drivectrl in !PositioningFailed or other error state 

__Symptom__

- drivectrl in state PositioningFailed or higher

__Solution__

- at the end of the night, when parking the telescope
 - first check if the telescope is parked. 
- go to /home/fact/operation
- "dimctrl"
- "DRIVE_CONTROL/RESET"
- restart script (or park telescope if at the end of the night)

__Not Helping__

- DRIVECTRL/STOP
- DRIVECTRL/PARK
- killing / quiting / restarting drivectrl 
- switching off/on drive hardware


== drivectrl in state ERROR

__Solution__

- check drivelog which error it is
- if you are not sure what to do, contact an expert Protected/ContactInfo

__Information for Experts__

indra-drive: http://www.astro.uni-wuerzburg.de/~tbretz/DriveDoku/IndraDrive/Firmware%20MPH-05%20-%20Stoerungsbeseitigung.pdf



== drivectrl in state ERROR and giving message "error in zd indradrive f2075"

This error means that the telescope was moved while the drive hardware was switched off. It might occur after there was ice on the telescope or in case of manual interaction while the drive was off. 

__Symptom__

- drivectrl in state ERROR
- in drivelog you find the message "error in zd indradrive f2075"

__Solution__

- check the position of the telescope visually
- try to find out what happened while the drive hardware was switched off
- if the telescope is NOT in the expected position
 - manual interaction needed -> contact experts
- if the telescope is in the expected position: 
 - switch drive off and on
 - wait for hardware to boot 
 - drivectrl should go to 'Initialized' now
 - check whether position seen by the software is as expected


== drivectrl in state LOCKED

__Symptom__

- drivectrl is in status LOCKED

__Solution__

- drivectrl goes in this status when the sun is rising, so if this "problem" occurs in the morning it is properly not a problem, it's only the way the telescope should behave, due to the rising sun
- if this problem occurs during startup, you have to unlock the telescope:
 - DRIVECTRL/UNLOCK

__Not Helping__

- DRIVECTRL/STOP
- killing / quiting / restarting drivectrl 


== Manual parking of the telescope

__Symptom__

- drivectrl does not accept / react to commands, for example an error with the IndraDrives occur


__Solution__

- if it's not to late in the night, try to call an expert before you park manually
- Park the telescope manually:

0. Proceed all parts of the Shutdown procedure you can do in the current situation (see [[shutdown here]])
 - be sure the bias voltage is OFF!
 - wear a helmet when going to the telescope
0. there are two bars near the door, to move the telescope in the azimuth and zenith direction:
 - long bar: zenith
 - short bar: azimuth
0. These bars, you can use for turning the telescope manually on the spots provided for this
 - azimuth: below the telescope
 - zenith: right of the mirrors
 - be aware that you don't turn in a way, that the cables get damaged
0. Turn the telescope in the Parking Position (pointing north, towards the old container)