Changes between Version 6 and Version 7 of TroubleShootingDrivectrl
- Timestamp:
- 04/24/17 22:04:28 (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TroubleShootingDrivectrl
v6 v7 1 1 2 = Trouble Shooting - Drivectrl 2 3 … … 4 5 http://fact-project.org/FACT++/namespaceDrive_1_1State_a0620e65c19529fd0318fd5ec880f8df3.html 5 6 6 7 == drivectrl in !PositioningFailed or other error state 7 == drivectrl in state LOCKED 8 8 9 9 __Symptom__ 10 10 11 - drivectrl i n state PositioningFailed or higher11 - drivectrl is in status LOCKED 12 12 13 13 __Solution__ 14 14 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 15 48 - at the end of the night, when parking the telescope 16 49 - first check if the telescope is parked. 17 - go to /home/fact/operation18 - "dimctrl" 19 - "DRIVE_CONTROL/RESET" 50 - send RESET to drivectrl 51 - either via smartfact 52 - or DRIVE_CONTROL/RESET via dimcrl (HowToDimctrl) 20 53 - restart script (or park telescope if at the end of the night) 21 54 22 55 __Not Helping__ 23 56 57 - restart Main.js 24 58 - DRIVECTRL/STOP 25 59 - DRIVECTRL/PARK … … 28 62 29 63 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 31 116 32 117 __Solution__ 33 118 34 119 - 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 36 129 37 130 __Information for Experts__ 38 131 39 indra-drive: http://www.astro.uni-wuerzburg.de/~tbretz/DriveDoku/IndraDrive/Firmware%20MPH-05%20-%20Stoerungsbeseitigung.pdf132 - indra-drive: http://www.astro.uni-wuerzburg.de/~tbretz/DriveDoku/IndraDrive/Firmware%20MPH-05%20-%20Stoerungsbeseitigung.pdf 40 133 41 134 42 135 43 == drivectrl in state ERRORand giving message "error in zd indradrive f2075"136 === drivectrl in state !HardwareError and giving message "error in zd indradrive f2075" 44 137 45 138 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. … … 63 156 64 157 65 == drivectrl in state LOCKED66 67 __Symptom__68 69 - drivectrl is in status LOCKED70 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 sun74 - if this problem occurs during startup, you have to unlock the telescope:75 - DRIVECTRL/UNLOCK76 77 __Not Helping__78 79 - DRIVECTRL/STOP80 - killing / quiting / restarting drivectrl81 82 83 158 == Manual parking of the telescope 84 159 … … 90 165 __Solution__ 91 166 92 - if it's not to late in the night, try to call an expert before you park manually167 - if it's not too late in the night, try to call an expert before you park manually 93 168 - Park the telescope manually: 94 169