User Tools

Site Tools


handover:r1740

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
handover:r1740 [2016/05/17 23:58]
Warren Hankey
handover:r1740 [2016/05/18 04:21]
Warren Hankey
Line 30: Line 30:
 All scans before missed. (Lucas) All scans before missed. (Lucas)
  
-  * 23:50 UT: Manually power cycled GPIB to try and fix error ib -10 - Talk light was constantly on (possible communication jam). After power cycle - talk light is no longer constantly on. However, error remains. (Bryn)+  * 23:50 UT: Manually power cycled GPIB to try and fix error ib -10 - Talk light was constantly on (possible communication jam). After power cycle - talk light is no longer constantly on. Error persists. (Bryn) 
 +  * 02:06 UT: Restarted fs to try fix error ib -10. //Missed scans 139-0212 and 139-0217//. Unsuccessful - Will reboot pcfs during next gap in schedule. (Bryn) 
 +  * 02:37 UT: Rebooted pcfs. (Bryn) 
 +  * 02:50 UT: error ib -10 fixederrors with dbbc communication - cycling power. (Bryn) 
 +  * 03:04 UT: Reconfigured DBBC and synced time with fmset. (Bryn) 
 +  * 03:10 UT: LO was not locked, restarted Rxmon. System temperatures are way off (values between -180000 and 90000) (Bryn) 
 +  * 03:25 UT: Halted schedule again - trying to sort out system temperatures. (Bryn) 
 +  * 04:15 UT: Schedule resumed - IF attenuation levels were not being automatically set due to a communication ​error (causing the errant tsys values) - First scan will be 139-0417a**Missed/​bad scans are 139-0247 through 139-0415** ​(Bryn) 
 +  * 
  
  
/home/www/auscope/opswiki/data/pages/handover/r1740.txt · Last modified: 2016/05/18 04:21 by Warren Hankey