Remove the perspex cover from the top of the Fabry-Perot, taking
great care not to drop the screws onto the etalon.
Setting the parallelism
The F-P and its controller appear to be stable enough that the
plate parallelism can be dialed-up and forgotten about as long as the
temperature and humidity do not change dramatically. Nevertheless, it
is good practice to check the parallelism, since if wrong it will make
your data very hard to analyse. The parallelism can be checked most
easily during the daytime using an argon comparison lamp.
- Recheck the resistive balance of the CS-100.
- Place an A4 sheet of white paper above the F-P on the aluminium
mounting flange to cover the 200mm hole (use sticky tape to hold
the paper in place). The purpose of the paper is to act as a
diffuse reflector for the comparison lamp.
- Place an argon comparison lamp in the UNSWIRF box. The lamp itself
should rest on the black aluminium cover into which the F-P retracts
when moved out of the beam. Use some sticky tape to stop the lamp from
moving around (and possibly falling onto the F-P).
- Plug the lamp power supply into one socket of the mains outlet that
is controllable from the console (ensure that the UNSWIRF rack is
not plugged into this socket).
- Turn off the lights (incandescents and fluoros) in the cass cage.
It is not necessary to turn off the dome lights.
- On the IRIS VAX terminal select METHOD 1, CYCLES 2, PERIOD 1,
TIME 1.5, IME 1, ITIME 1.5, LF open, UF 1.65. These parameters are
suitable for the 1.6519 micron argon line.
- On UNSWIRF do ``x -490 y 499 z -30''.
If necessary, put the F-P in the beam
with the command ``slide in slide 150''.
- With the lamp off, take an exposure and use it as a dark (i.e.,
``use nnn dark'').
- Turn the lamp on. You should see an obvious increase in flux, hopefully
in a circularly symmetric pattern.
- Now tweak the ``z'' setting (using commands such as
``dz 5'' or ``dz -5'')
and note the affect on the display. As you go to more negative z,
you should see a donut of light steadily moving out towards the
edges of the plates. Make a note of the ``z'' setting at which the
donut is at the periphery (or 90% of the way there).
- Use the Perl script cube.pl to set up a run file (use
``./cube.pl > /vaxdata/obsred/unswirf/yourfilename.dat'') of 16 or so
images at delta-z of 2 about the line centre, and execute this
file using ``unsw yourfilename.dat''.
- Convert the data to FITS format by running docube on the output files,
then read the FITS cube
into IRAF with rfits.
- Run the unswslope.cl script.
- Take the dX and dY values output by unswslope.cl,
and append them to the lines $xx=... and $yy=... in BOTH arc.pl and
cube.pl.
- Repeat the comparison lamp cube, rerun ``unswslope'', and
iterate the correction if necessary. The absolute values of the X and
Y slopes should both be less than about 0.01 (corresponding to a
precision in the X and Y settings of about 2).
Problems that have occurred with UNSWIRF in the past:
- A dodgy 50-ohm ethernet terminator resulted in intermittent
communication with the PC.
- Damaged ethernet cables.
- Dodgy high-voltage cables from the CS-100 to the F-P caused an
inability to close the F-P loop. An electrical shock was
experienced when touching some of the cables.
- CS-100 loosing lock. Possibly humidity related (both too high and
too low), possibly related to the above arcing problem. The only
remedy appears to be to open the loop, power-cycle the CS-100, and
close the loop.
- The etalon drifts in both Z and parallelism about a factor of ten
more than it should. Correlated with humidity/temperature. The
settings are also sensitive to the resistive balance, and may be
affected by gravity (i.e., telescope position).
- A loose connector to the National Instruments 96-bit DIO card in
the PC caused unreliable operation of the CS-100.
- Contacts pushed out in the green box high-voltage connector.
- DITS_NETSTART failed on the VAX due to software modifications.
- Offset run files failed due to software modifications.
- Communication problems between the VAX and the Sun. See the
earlier section on how to fix this.
- Sometimes the NFS fileserving between the Vax and the Suns has
problems. It can be fixed by rebooting the MicroVax 3800 and
restarting the Observer and UNSWIRF software.
Existing problems:
- The UNSWIRF ``slide in'' command does not return control to the
user when it should (workaround: send a carriage return after waiting
60 seconds). This may be due to a faulty limit switch.
- Offset-run files sometimes crash with an error in END OBEY.
- XMEM crashes about once a night.
- Vax crashes about once every couple of nights.
- SLEW commands from ICL often fail.
Planned enhancements:
- Software-operable comparison lamps and flip-mirror.
Last updated 19-Apr-1997
UNSWIRF: hardware / Michael Ashley /
mcba@newt.phys.unsw.edu.au