This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
handover:rd1611 [2016/11/29 19:50] Bryn Emptage |
handover:rd1611 [2016/11/30 03:22] Bryn Emptage |
||
---|---|---|---|
Line 12: | Line 12: | ||
* 17:50UT ERROR 5k -602 SCAN_CHECK missing bytes is not zero. Can't find reference to this on the wiki. No major alarm sounded so feel safe to wait until Jamie takes over. Non-critical? (Liz) | * 17:50UT ERROR 5k -602 SCAN_CHECK missing bytes is not zero. Can't find reference to this on the wiki. No major alarm sounded so feel safe to wait until Jamie takes over. Non-critical? (Liz) | ||
* 19:40UT System temps have been on the high side ~100 across all bands on and off. Some instances of major overflow in a number of bands but also long periods where they remain in an acceptable range. Monitoring for now. (Liz) | * 19:40UT System temps have been on the high side ~100 across all bands on and off. Some instances of major overflow in a number of bands but also long periods where they remain in an acceptable range. Monitoring for now. (Liz) | ||
+ | * 21:30UT turns out system temps were high because the receiver was still on l band. now fixed (Liz) | ||
+ | * 21:30UT ERROR 5k -602 SCAN_CHECK missing bytes is not zero. THIS IS NOT GOOD. Jamie is trying to fix now. (Liz) | ||
+ | * 22:00-22:45 Attempted to use jive5ab 7 in2file to fix the problem, but m5test indicates the same problem in the data. Warren and Brett now investigating the connections between the mark4 rack and mark5a unit (JMc) | ||
+ | * 23:00 No change, scan_check still reports dropped bytes. m5test indicates occasional loss or time codes/sync in recorded data using both disk_record and in2file. Continuing experiment with disk recording (JMc). | ||