Troubleshooting guide

the left-hand rack, the other below the perle on the right-hand rack (Figure 6, below). Each has two small
toggle switches, which must be set so that the red and green LEDs are OFF. The LEDs are used only for
testing that the fiber is working.
Figure 6: Fiber optic converter boxes below MCE4 (left panel) and below perle (right panel)
c) Problem: The image acquisition counts past the exposure time without reading out an image.
Solution: This problem rarely happens anymore. With the previous slower version of flamingos1a, it
would sometimes take an extra 5 to 10 seconds to finish reordering the pixels; i.e., applying the look up
table, or LUT, before writing the image to disk. In the MCE4 daemon window you should see a string of
dots being printed out during the apply lut phase:
UFEdtDMA::applyLut> . . . . . . . . . .
You should watch for several seconds to see if this line is present, and that it is printing additional dots.
When it finishes, it should also print something similar to:
UFEdtDMA::takeAndStore> close mmap file: /data/4mguest/Test/test.0002.fits
UFEdtDMA::> completed: 1 -- /data0/4mguest/Test/test.0002.fits
ufgtake> acquired frames: 1
UFEdtDMA::takeAndStore> close mmap file: /data/4mguest/Test/test.0002.fits
UFEdtDMA::> completed: 1 -- /data0/4mguest/Test/test.0002.fits
ufgtake> acquired frames: 1
If this never appears, try typing ufstop.pl -stop -clean at a flamingos1a prompt. Then try taking another
image; if that fails see if ping perle returns with the message that the perle is alive. If the perle is alive,
try rebooting MCE4 and reinitializing. If that completely fails, call for help.
d) Problem: A large number of error messages are printed out either when trying to move a wheel (e.g.,
with config.rel.mv.filter.grism.decker.wheels.pl [Move Wheels]), or during the first part of an image
acquisition, where it sends commands to MCE4.
Solution: It's possible that the perle (formerly iocomm) has crashed, or is very confused. Try ping perle
from flamingos1a; if there is no response, it needs rebooting. Even if there is a response, it may be
advisable to reboot it. To do this telnet baytech, userid perlepow password _________[regular
flamingos1a password]. At the prompt type reboot 1, and then type logout when the prompt returns (e.g.,
see the example output in 3a, above). Now you must close all three daemons (Temperature, Motor, and
MCE4) and the record_temperatures window and run initflam.pl.
FLAMINGOS@4-m, Ver. 2.39, 2013 April 23 Page 38 of 47