Changes between Version 6 and Version 7 of TroubleShootingDrivectrl


Ignore:
Timestamp:
04/24/17 22:04:28 (8 years ago)
Author:
Daniela Dorner
Comment:

updated according to https://www.fact-project.org/logbook/showthread.php?tid=5062 and discussion with Thomas

Legend:

Unmodified
Added
Removed
Modified
  • TroubleShootingDrivectrl

    v6 v7  
     1
    12= Trouble Shooting - Drivectrl
    23
     
    45http://fact-project.org/FACT++/namespaceDrive_1_1State_a0620e65c19529fd0318fd5ec880f8df3.html
    56
    6 
    7 == drivectrl in !PositioningFailed or other error state
     7== drivectrl in state LOCKED
    88
    99__Symptom__
    1010
    11 - drivectrl in state PositioningFailed or higher
     11- drivectrl is in status LOCKED
    1212
    1313__Solution__
    1414
     15- 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
     16- if this problem occurs during startup, you have to unlock the telescope:
     17 - unlock in smartfact
     18 - or DRIVECTRL/UNLOCK in dimcrl (HowToDimctrl)
     19
     20__Not Helping__
     21
     22- DRIVECTRL/STOP
     23- killing / quiting / restarting drivectrl
     24- switching off/on drive hardware
     25
     26
     27== timeout while waiting for expected state (e.g. Moving, !OnTrack, ...)
     28
     29__Sympton__
     30
     31- Main.js stopped because drivectrl is not in expected state
     32
     33__Solution__
     34
     35- check status of drivectrl
     36- in case of warning/error, see below
     37- in case the expected state is reached in the meantime (i.e. waiting time was not long enough), restart Main.js
     38
     39== drivectrl in !PositioningFailed
     40
     41__Symptom__
     42
     43- drivectrl in state !PositioningFailed
     44
     45__Solution__
     46
     47- check drivectrl log
    1548- at the end of the night, when parking the telescope
    1649 - first check if the telescope is parked.
    17 - go to /home/fact/operation
    18 - "dimctrl"
    19 - "DRIVE_CONTROL/RESET"
     50- send RESET to drivectrl
     51 - either via smartfact
     52 - or DRIVE_CONTROL/RESET via dimcrl (HowToDimctrl)
    2053- restart script (or park telescope if at the end of the night)
    2154
    2255__Not Helping__
    2356
     57- restart Main.js
    2458- DRIVECTRL/STOP
    2559- DRIVECTRL/PARK
     
    2862
    2963
    30 == drivectrl in state ERROR
     64== drivectrl in !OutOfRange or !InvalidCoordinates
     65
     66__Symptom__
     67
     68- drivectrl in state !OutOfRange or !InvalidCoordinates
     69
     70__Solution__
     71
     72- check drivectrl log
     73- in case you are doing a special test:
     74 - check coordinates
     75 - make sure that the coordinates are valid
     76 - if coordinates where fine, contact experts
     77 - else send RESET to drivectrl (via smartfact or dimctrl (HowToDimctrl)) and restart with correct coordinates
     78- in case of normal operation:
     79 - contact experts
     80
     81__Not Helping__
     82
     83- restart Main.js
     84- DRIVECTRL/STOP
     85- DRIVECTRL/PARK
     86- killing / quiting / restarting drivectrl
     87- switching off/on drive hardware
     88
     89
     90== drivectrl in !HardwareWarning
     91
     92__Symptom__
     93
     94- drivectrl in state !HardwareWarning
     95
     96__Solution__
     97
     98- check drivelog which warning it is
     99- in case of ''[e8260]: Torque limit active!''
     100 - note to the logbook in which situation it happened and on which axis
     101 - send RESET to drivectrl (via smartfact or dimctrl (HowToDimctrl))
     102 - restart Main.js
     103- in case it is another warning
     104 - contact expert
     105
     106__Not Helping__
     107
     108- restart Main.js
     109- DRIVECTRL/STOP
     110- DRIVECTRL/PARK
     111- killing / quiting / restarting drivectrl
     112- switching off/on drive hardware
     113
     114
     115== drivectrl in state ERROR, !HardwareError or FATAL
    31116
    32117__Solution__
    33118
    34119- check drivelog which error it is
    35 - if you are not sure what to do, contact an expert Protected/ContactInfo
     120- contact experts
     121
     122__Not Helping__
     123
     124- restart Main.js
     125- DRIVECTRL/STOP
     126- DRIVECTRL/PARK
     127- killing / quiting / restarting drivectrl
     128- switching off/on drive hardware
    36129
    37130__Information for Experts__
    38131
    39 indra-drive: http://www.astro.uni-wuerzburg.de/~tbretz/DriveDoku/IndraDrive/Firmware%20MPH-05%20-%20Stoerungsbeseitigung.pdf
     132- indra-drive: http://www.astro.uni-wuerzburg.de/~tbretz/DriveDoku/IndraDrive/Firmware%20MPH-05%20-%20Stoerungsbeseitigung.pdf
    40133
    41134
    42135
    43 == drivectrl in state ERROR and giving message "error in zd indradrive f2075"
     136=== drivectrl in state !HardwareError and giving message "error in zd indradrive f2075"
    44137
    45138This 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.
     
    63156
    64157
    65 == drivectrl in state LOCKED
    66 
    67 __Symptom__
    68 
    69 - drivectrl is in status LOCKED
    70 
    71 __Solution__
    72 
    73 - 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
    74 - if this problem occurs during startup, you have to unlock the telescope:
    75  - DRIVECTRL/UNLOCK
    76 
    77 __Not Helping__
    78 
    79 - DRIVECTRL/STOP
    80 - killing / quiting / restarting drivectrl
    81 
    82 
    83158== Manual parking of the telescope
    84159
     
    90165__Solution__
    91166
    92 - if it's not to late in the night, try to call an expert before you park manually
     167- if it's not too late in the night, try to call an expert before you park manually
    93168- Park the telescope manually:
    94169