ObsProblems Trouble-shootingThe Parkes general trouble-shooting guide can be found at: http://www.parkes.atnf.csiro.au/observing/documentation/user_guide/pks_ug_7.html#TroubleShooting Please jump to the following sections: CASPSR stops recording data CASPSR stops recording dataTo fix CASPSR in event of a failure, do the following:
Please see the caspsr user guide for detailed information CASPSR is offlineYou may experience an 'timeout' error in TCS. This may occur for example, if the previous observing session was using BPSR, and CASPSR was stopped.
DFB problems[Taken from the troubleshooting section of the Correlator Guide] If you have issues getting DFB4 going, or getting multiple XFER timeout errors, follow the procedures below: 1. Try reconfiguring the DFB (click CONFIG button on DFB GUI); Try this at least 2 times before moving to #2. 2. If #1 is not sufficient, quit and restart DFB GUI (pdfb4/sdfb4 according to the observing mode) Try this at least 2 times before moving to #3; 3. If #2 is not sufficient, use the bcckill and corkill procedures:
Try this at least 2 times before moving to #4 4. If #3 is not sufficient, reboot the two l-bcc06 (DFB3 only) and l-bcc11 boards:
Try this 2 times before moving to #5 5. (No longer an option for remote observing!)
PSRMON problemsPSRMON suddenly stops working.
CASPSR digitiser saturatedDuring a good observation, CASPSR's digitiser histogram should look something like this, preferably with the two pols - red and green lines - overlapping, and the counts clustered around state 0, within the range +/- 20 being ideal: ![]() In certain circumstances such as continuous or large bursts of RFI, you may notice that the CASPSR histogram however looking something like this: <picture of saturated digitiser> This is an indication that that the digitiser has become saturated, clipping occurs and the system is driven non-linear as a result, and therefore detrimental to observation quality. Under these conditions it may be necessary to adjust the attenuator levels in loGui. Please follow the steps below - if you are unsure about what to do, make a note in the Dashboard log and contact Matthew K. or Ryan:
![]() |