User Tools
operations:documentation.errors
This wiki is not maintained! Do not use this when setting up AuScope experiments!
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
operations:documentation.errors [2017/08/13 22:09] Tiege McCarthy |
operations:documentation.errors [2017/09/27 06:29] (current) Jamie McCallum [Antenna stuck | Warning: error st -27 computer acu time difference exceeded 0.25 seconds, see value above.] |
||
|---|---|---|---|
| Line 42: | Line 42: | ||
| ==== Antenna stuck | Warning: error st -27 computer acu time difference exceeded 0.25 seconds, see value above. ==== | ==== Antenna stuck | Warning: error st -27 computer acu time difference exceeded 0.25 seconds, see value above. ==== | ||
| - | Normally this error can be ignored, but there was an additional error with this - WARNING: error st -10 rampepochtime not -1 when preparing to load, check antenna is in "operate". Error presented as drive status not ready, with drives green in HMI. HMI was unresponsive - could not turn drives off. Antenna=operate and Antenna=open both return Antenna OK, but don't work. The clock on the right of HMI interface on cnsshb (CURRENT TIME UT1) was not updating. | + | Normally this error can be ignored, but there was an additional error: |
| + | |||
| + | <code> | ||
| + | WARNING: error st -10 rampepochtime not -1 when preparing to load, check antenna is in "operate". | ||
| + | </code> | ||
| + | |||
| + | Error presented as drive status not ready, with drives green in HMI. HMI was unresponsive - could not turn drives off. Antenna=operate and Antenna=open both return Antenna OK, but don't work. The clock on the right of HMI interface on cnsshb (CURRENT TIME UT1) was not updating. | ||
| Solution to issue is using HMI and selecting the reboot central button under resets. This reset the clock connection to the antenna, allowing the drives to communicate again. | Solution to issue is using HMI and selecting the reboot central button under resets. This reset the clock connection to the antenna, allowing the drives to communicate again. | ||
| Line 139: | Line 145: | ||
| Start pinging the ceduna gateway (131.217.61.129) on your PC (not in the VNC window). In a terminal or command prompt: | Start pinging the ceduna gateway (131.217.61.129) on your PC (not in the VNC window). In a terminal or command prompt: | ||
| <code>ping 131.217.61.129</code> | <code>ping 131.217.61.129</code> | ||
| - | After the router finishes rebooting, click on the status menu (top-left) and check the 3G status. Ideally, the pings will start reaching the the Ceduna gateway, If so skip the next step, If not it may be the VPN that needs fixing, to do this run putty.exe (on the desktop), ssh into 192.168.1.61, login as 'physics' and run the following command: | + | After the router finishes rebooting, click on the status menu (top-left) and check the 3G status. Ideally, the pings will start reaching the the Ceduna gateway, If so skip the next step, If not it may be the VPN that needs fixing, to do this run putty.exe (on the desktop), ssh into 192.168.1.61, login as 'physics' (different password again) and run the following command: |
| <code>clear crypto ipsec client ezvpn</code> | <code>clear crypto ipsec client ezvpn</code> | ||
/home/www/auscope/opswiki/data/attic/operations/documentation.errors.1502662164.txt.gz · Last modified: 2017/08/13 22:09 by Tiege McCarthy
Page Tools
