Gregorian amp failures feb07

20nov06


plots:
The position and status bits  of the system during the failure (40 seconds)  (.ps) (.pdf).
The status bits  of the system during the failure  (25 minutes) (.ps) (.pdf).
Gregorian motor torques during the failure (.ps) (.pdf)
 


Intro: (top)

    Amplified 21 and 22 on the dome have failed with amplifier not ready. This has occurred on :     The failures have occurred when the dome is at high za and starting to move downhill. The failure occurs 3 or 4 seconds after it starts moving downhill. To recover from the error, the operator has sent a reset command to the vertex system.


Position, status bits during failure (40 secs of data).  (top)


 The position and status bits  of the system during the failure  (.ps) (.pdf).  There are 4 pages for each plot showing the four separate failures. Data is recorded once a second. For the status plots the leftmost * on each line is the zero (false) value for each bit.  Each plot contains 40 seconds of data.


Status bits during failure (25 minutes of data).  (top)


The 2nd set of plots shows the status bits for 25 minutes of time starting before the failure.
     The status bits  of the system during the failure  (25 minutes) (.ps) (.pdf).

    These plots show the same data as the first set but extended to about 25 minutes. The only interesting behavior is that some of the other amplifiers seem to be going not ready a while after the failures. I looked at the normal behaviour of the status bits when a reset/stop sequence was issued. It did not change the amplifier ready status. The software must be in a different state when the first error occurs.


Motor torques during failure.  (top)

     Gregorian motor torques during the failure (.ps) (.pdf). These plots show the motor torques for each motor during the failures.  The torques are measured once a second.     The motor torques when the error occurred do not differ appreciably from when the error did occur. The torques are complicated since:     The torques for motor 31 (which never failed) seem to differ from the others (when there was a failure and when there was no failure). This may be a calibration problem or some other problem.


Summary  (top)

Processing: x101/070213/agcampfail.pro


<- page up
 home_~phil