This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
handover:r4762 [2016/10/21 05:57] Jim Lovell |
handover:r4762 [2016/10/21 11:59] (current) Jim Lovell |
||
---|---|---|---|
Line 22: | Line 22: | ||
* 21:08 UT - "ALARM: error s5 -104 rfpcn: time-out, connection closed" error again, this time I restarted Monica, scan affected is 294-2107. (Tiege) | * 21:08 UT - "ALARM: error s5 -104 rfpcn: time-out, connection closed" error again, this time I restarted Monica, scan affected is 294-2107. (Tiege) | ||
* 21:14 UT - "ALARM: error s5 -104 rfpcn: time-out, connection closed" error again, tried restarting Rxmon again this time, scan affected is 294-2114a. Restarting of Rxmon and/or Monica are the solutions listed in the wiki, however, they haven't seemed to help much here. It seems when these errors do crop up in observations, they tend to reoccur. Jim will be taking over soon and I will mention the problem to him so he can check it out and hopefully determine whether the problem is something more sinister. (Tiege) | * 21:14 UT - "ALARM: error s5 -104 rfpcn: time-out, connection closed" error again, tried restarting Rxmon again this time, scan affected is 294-2114a. Restarting of Rxmon and/or Monica are the solutions listed in the wiki, however, they haven't seemed to help much here. It seems when these errors do crop up in observations, they tend to reoccur. Jim will be taking over soon and I will mention the problem to him so he can check it out and hopefully determine whether the problem is something more sinister. (Tiege) | ||
+ | * 06:28 UT - "ALARM: error s5 -104 rfpcn: time-out, connection closed" error again, with Jesse's help fixed by halting the schedule and stopping then restarting DIM which seemed to be running but wasn't really. Missed scans ... (Liz) | ||
**Yarragadee** | **Yarragadee** |