Here are some notes on observing with the SONIC - 1992/05/15

  Commands

Most of the useful commands are aliases.  The words "alias comm" will
show what "comm" really does if it is an alias.  A new alias can be
written with "alias comm new command text".  Aliases are read at
startup from the file ".sonic.alias" and can be written with the
"writealias filename" command.  See the realtime manual for more
details. 

Some of the most used commands are detailed below.  Command arguments
are enclosed in <brackets>; replace with a value.

Don't forget that you can get help on commands by typing "help comm."  Many
of the commands must be preceded by "ir"; type "help ir" to get a list.

ft <seconds>	Set frame time to <seconds>.  Frame times must be
                multiples of 1/15 second.

object <name>	Set name of data files.

go <seconds>	Normal start of integration.  Integration time will
		be rounded up to next larger frame time.  For
		example, if frame time is 30, "go 29" will do one
		frame, but "go 30" will do two.

ss		Start an integration in the other beam.

bt		Switch which beam the computer thinks the telescope is in.

sd		Store data.  The previous object name, if any, is used to
		name the file.  Comments will be stored even if not edited.
		The header will get filter and telescope position at file
		storage time, so make sure to store data BEFORE moving
		filter or telescope.

fm <x> <y>	Give an estimated instrumental magnitude of star located at
		position (x,y).  Will sky subtract if data in both object
		and sky frames but will not flat field.  Magnitudes are not
		scaled for exposure time.

dp		Display a "patch" of the current data frame, object beam.

pp		Display a "patch" of the working buffer.  See the realtime
		manual for information on manipulating data in buffers.

wait		Wait until the current integration is done; then continue.
		Used for writing aliases and command files.

sv <name> <val> Set voltage "name" to value "val."

vg <val>	Set gate voltage to value "val."

sac		Stop camera and throw away data.  Use to stop tv mode or
		to throw away bad data.  Use with caution.

darks		Take a standard sequence of dark frames.  Use "comment"
		and make sure filter is on BLK before starting "darks".

comment		Bring up the comment editor.

oldcom <n>	Edit all parameters stored in data file n.  Changing
		the OBJECT keyword changes the file name.

com <n>		Show the comments in data file n.

par <n>		Show the non-comment part of the header in data file n.

dlink now	Set the "dlink" directory to be the current data directory.

dirs		Short display of current "dlink" directory.

int 3		Set diagnostic mode for setting a/d offsets.  Not for
		taking data.

int 4		Set normal data-taking mode.

tv		Start tv mode.

irs <thr> <sat> Set image display threshold and saturation.

o		Set image display for finding typical bright objects.

obj		Set image display for typical faint objects.

std		Set image display for typical standard stars.

irt <n>		Set what image is displayed.  n=1 is object, n=2 is
		sky, n=3 is object minus sky. 

lin		Set linear scaling on image display.

sqrt		Set square root scaling on image display.

bye		Quit the command interpreter.

  Problem Solving

The object and sky beams got mixed up in one of the data files.
     Store data normally, then edit the file header with "oldcom."  Find the
     keyword "SWAPPED = F"; change the "F" to "T".  The iraf routine "rira"
     will then automatically restore the correct beams when it reads the
     data file.

Image display will not update.
     Click button in image display window to see if program is dead.  If
     nothing happens, the display is dead.  The only solution is to exit and
     restart the command interpreter.

Commanded integration doesn't start.  Monitor window says "Expected frame
beginning not found."
     Indicated hardware problem between camera and fifo.  If it happens
     rarely, it is probably safe to ignore it.  If it happens repeatedly,
     check cables and/or perform hardware diagnostics on fifo and camera.

Dark frames show lots of blooming around pixel defects.
     Gate voltage set too negative.  Reset.

Dark frames show lots of variation and/or dark current high.
     Gate voltage set too positive.  Reset, taking care to go from negative
     to positive voltage at the end.

Frames seem to give all zeroes or otherwise look abnormal.
     A to d offsets may be wrong.  Go into "int 3" and check.  Also check
     that all other voltages are set correctly.  If not, make sure camera
     electronics are on, type "comfile .sonic.commands" in command window,
     then turn two switches on back of camera electronics away from pot side
     of board.  Check voltages again.

Star is visible in guider but not in SONIC frames.
     Something is physically blocking the beam.  Check SONIC filter, top box
     filter, and guide probe.  Make sure mirror covers are open, telescope
     looking out dome, etc.  Check that frame time is long enough for star
     brightness and that image display is alive and set to a reasonable
     scale. 

Temperature control program ("tsonic") will not start.
     Turn temperature controller off and back on, then try again.  (At
     present, until we get the serial ports fixed, you will also have to
     reboot the computer if this happens!  Type "godown -r" to do that.)
     Remember not to type tsonic until the command interpreter is up.