Problems - updated as we go along!

• 8 flat noisy spectra. Check the Signal generator in the top of the Correlator Rack. For a 64MHz band it should be set to 128MHz, RF output should be on. (It says OFF in the bottom right box if it's off). Output level isn't critical, but I usually set it about 5dBm.
• 8 flat noisy spectra. Check the band width settings on the rear of the signal conditoning boxes (they're labelled). The set of three switches control which filters are selected as follows:-

  Filter Set Enable Switchbank

  Switch settings-ABC	Filterbank no.	Bandwidth (MHz)	Centre Frq. (MHz)	Filters
  000	1	64	160	8
  100	2
  010	3	8	36	8
  110	4	1	32.5 (5 element)	2 (chan 7/8)
  001	5
  101	6
  111	7	1	32.5 (10 element)	1 (ch 7)

• Some flat noisy spectra. Check power levels with MBD - If they're too low - spectra will be poor/non-existant. (Power saturates at 65535 counts - so too large a signal can also cause problems see notes on ATTSET to insert or remove some attenution)
• MBCOR reports Calibration signal not present. Check correlator CAL output connected to noise diode.
• No spike at 1420MHz. Check LO setting on top of main rack. Should be 391.25MHz for a 64 MHz wide band with centre frequency 160MHz, to give spectra centred on 1405 MHz (Or you could be looking at a very empty bit of sky - can you see the interference spike at 1390-ish?)
  To check LO setting. Centre Frequency of data = LO x 4 - CF of filter.
• Near total loss of power signal on all channels - no CAL. Last time this happened, we noticed the SYNC/BLANK lights on the correlator sampler cards were acting out of character. When doing 5 sec integrations, the SYNC should be ON for 5 secs, with a quick blip of BLANK at the end of each integration. The CAL output mirrors this, with the 500Hz TTL showing during the 5 second intgration. Other faults noticed have been both SYNC and BLANK lights stuck on, on some of the cards. Power cycle the BCC (not just reset) and cards by eg. pulling the chunky mains lead. (You might want to restart multi/mbcor and tkmulti as well).
• Mailbox full errros in MBCORR (lots of beeps) Try typing FLUSH command in MBCORR or perhaps in tkmulti command box, but I don't hold out much hope, so power cycle everything (see above) and perhaps restart all the software).
• Error: MBmode not set in multi/tkmulti Telescope fallen out of ARTHURs control. (eg Elevation servo fault). If it's still running, shutdown the scheduling in tkmulti by pressing STOP (this may take a minute or so to work its way through the deluge of error messages). Note the scan and schedfile name so that you restart at the right place. Wait until telescope control is returned. Give tkmulti the enable antenna, enable FCC commands. Enter the correct scan start number and restart the schedule. If you can't stop multi tidyly, try CTRL-Y a couple of times on the screen running the multi process. (You want to get a message something like 'glish-control exited' ). Shutdown tkmulti. Restart multi, then tkmulti. You should be able to leave MBCOR running.
• Error: FCC something or other in multi/tkmulti Same error as above - you've lost control of the telescope, but it was trying to rotate the feed, rather than sending source coordinates. Solution same as for MBmode not set in multi/tkmulti
• Error: Allocate fail. Dev offline in multi/tkmulti Telescope not available. Talk to the controller. See above for restarting things.
• Error: CTRL-C in drive to scan start in multi/tkmulti You pressed the STOP button in tkmulti
• When trying to start MULTI, you get an error message about "glish_ctrl.exe" not found. Don't continue with multi, either close the window and start afresh in a new one or change directory to multi$work and try again.
• Unable to interrupt a drive to source, a running schedule or various other tasks, until they've finished.
  Glish_ctrl is not running (crashed or not found on start of multi - see note above). On ARTHUR, type WHO to get a list of current processes, and see if you can see Glish_ctrl. If it's not there, you'll have to stop multi (it's probably ignoring the EXIT command as well - so try CTRL-Y), and tkmulti, and restart them (MBCOR should be OK).
• Can't find sched file!
  The command line parsing will snap at any file name and try and match it to what have been designated the significant letters of any multi commands, (Bug or Feature ?!). So, for example the command SCHEDFILE HERCULESA_4BEAMS comes out of the parser as SCHEDFILE HELP. This also effects fitsfile names and source names.
  Here's a list of the current multi commands - you have been warned!

  AZ
  BANDW
  CALO    CALIB   CALS    CALT    CLOS    CONF   
          COORD   CYC
  DAZ     DCOORD  DEC     DECB    DECJ    DECH    
          DDEC    DDECB   DDECJ   DDECH   DEL
          DEPOCH  DGLAT   DGLON   DHA     DLST    
          DRA     DISAB   DOPPD   DOPPR   DOPPL   
          DRAB    DRAJ    DRIVE   DUT 
  EL      ENABL   EPOCH   EX
  FCC_R   FCC_P   FITSN   FREQ    
  GLAT    GLON    
  HA      HE
  INP
  LOAD    LST
  OFFS    OPEN
  QU
  RA      RAB     RAJ     RATE    REC     REFB    
          xxREF
  SAV     SCAN    SCH     SET     SOU     STEP    
          START   STARTC  STEPS   STOP    STOPC   
          STOW    
  TRA     
  UT
  WEL
  ?       @
  

• Livedata. Don't AUTOQUEUE files to get them processed as ARTHUR collects data. Livedata does a timeout on the write process, they appear in the processed data window, but don't exist! (Livedata should be restarted).

• Livedata and gridzilla won't start. Use top in another window, if you've got a megaserver use 99% of your CPU and doing nothing, kill all the megaservers you can find, and try deleting /home/multi/aips++/aips++.log.

• Gridzilla, says processing, then processing complete about 2 seconds later - and hasn't produced any output. See how much memory you've told it to use. If it can't get that much, it won't run.