Changes between Version 4 and Version 5 of TroubleShootingDrivectrl

Timestamp:

03/08/16 12:35:55 (9 years ago)

Author:

Daniela Dorner

Comment:

updated to new drivectrl version

TroubleShootingDrivectrl

@@ -1 +1 @@
 = Trouble Shooting - Drivectrl
 
-== Cosy in state Error
+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 and Cosy in state ERROR
-- drivectrl and Cosy in state ARMED (when just the Tracking stopped accidently)
+- drivectrl in state PositioningFailed or higher
 
 __Solution__
 
-- DRIVECTRL/RESUME
-
-The RESUME command will proceed the following steps (so only RESUME is necessary to solve the Drive Error):
-
-- DRIVECTRL/STOP (now drivectrl shut be in state armed)
-- DRIVECTRL/TRACK_SOURCE x y sourcename
- - last Tracking command: see output of dimctrl 
- - see [[datatakingdetails#pointingpositions Current Pointing Positions]]
+- 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__
 
-- all other
+- DRIVECTRL/STOP
+- DRIVECTRL/PARK
+- killing / quiting / restarting drivectrl 
+- switching off/on drive hardware
 
-== drivectrl in state ERROR [=#DriveControlError]
+
+== drivectrl in state ERROR
+
+__Solution__
+
+- check drivelog which error it is
+- if you are not sure what to do, contact an expert 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
-- sending a STOP via dim is ineffective
+- in drivelog you find the message "error in zd indradrive f2075"
 
 __Solution__
 
-- go to /home/fact/operation
-- restart drive control: "dimctrl —restart DRIVE_CONTROL"
-- follow the command line output of drive control: "follow.sh drivectrl"
+- 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
 
-__Remark__
 
-- Be patient and wait for the service to reboot !!!
-
-== drivectrl in state 3
+== drivectrl in state LOCKED
 
 __Symptom__
@@ -55 +78 @@
 
 - DRIVECTRL/STOP
-- killing / quiting drivectrl or cosy
+- killing / quiting / restarting drivectrl 
+
 
 == Manual parking of the telescope
@@ -61 +85 @@
 __Symptom__
 
-- drivectrl and Cosy don't accept / react to commands, for example an error with the IndraDrives occur
+- drivectrl does not accept / react to commands, for example an error with the IndraDrives occur
+
 
 __Solution__
@@ -75 +100 @@
  - short bar: azimuth
 0. These bars, you can use for turning the telescope manually on the spots provided for this
- - azimuth: below the telecope
+ - azimuth: below the telescope
  - zenith: right of the mirrors
  - be aware that you don't turn in a way, that the cables get damaged