READ LIST BEFORE STARTING UP
Last update on: December 16, 1996
This section documents known faults that can occur, and for which at the moment no permanent cure is made.
Symptoms: Bad pointing, even after a repeated SNAFU procedure.
Diagnosis: Most likely cause a fault on one of the Ferranti encoders. In order to check this run the task ENCODER from the Telescope Control System VDU by typing:
This will produce a status report on the three Ferranti encoders. If one of them ia baulking, it will show up in the form of deviant encoder readings.
Remedie Disable the faulty encoder by setting its weight to zero. Refer to section 11.1.6 for full details.
Symptoms: one or more of the following messages appear:
OBSNPACK: BDP error: Specified version different from actual version
AGBXPACK: BDP error: F (Error code not found on file SYS:bdp.err/G)
SPECPACK: BDP error: F (Error code not found on file SYS:bdp.err/G)
Error writing archive packets to disc
Possible Solution: Look to see if files PKTTYPES.DAT and PKTTYPES.BCK exist on account 180. If not, ask the Duty Technician to restore the PACKETS tape.
Symptoms: Image with bars accross it, or one part slipped with respect to another, or some other obvious fault.
Diagnosis: Either a DMA transfer problem, which should produce a message on the ADAM terminal, or the data were written onto a corrupted part of the EGLE disc.
Remedie: None! These errors are irrecoverable. Refer to section 9.5 to read about what to do or NOT to do with the data.
Symptoms: The MIMIC display signals errors or flash remarks which you can scarcely credit.
Diagnosis: There may be a real error, but often the error messages are the result of a minor corruption of the A&G box micro processor.
ADAM:> IDS OPEN
If this does not cure the problem then you probably have a real fault so call the Duty Technician.