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.

--- operations:documentation.errors [2017/05/05 00:32]
Lucas Hyland
+++ 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. ====
-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.
@@ Line 126: / Line 132: @@
 Restart the field system and the changes will be implemented. Shout out to Arwin for figuring this one out.
+==== Ceduna Network Down ====
+First ssh into hobart and make sure to forward the X server
+<code>ssh -X oper@hobart.phys.utas.edu.au</code>
+From terminal on hobart, VNC into the 'manager' PC
+<code>vncviewer manager</code>
+Go to network connections in the bottom right, left-click on this icon and then right-click on 'CEDUNA-NETWORK' and connect. May need to click 'dial' on a pop up window. Once this connection is established open up TightVNC (should be in start menu). VNC into the router PC, details should already be in, just press connect. **The password is not standard for this PC** (ask for it in group chat and remember/write it down).
+Check status of 3G network on the status page, navigate to system tools on the left. Click on the reboot sub-menu. Click reboot and confirm.
+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>
+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>
+Once you have established connection (can ping the gateway), exit out of the router PC VNC window, then go down to network connections on 'manager', **right-click on CEDUNA-NETWORK and click disconnect. This is important.**
+Now you are done!
+Brett is the expert on this setup, so if anything is not as described above, he is the best contact person.
+Not really in the ideal spot, however, not sure I have the ability to add to the RA wiki -Tiege 14/08/17

AuScope VLBI Operations Wiki

User Tools

Site Tools

This wiki is not maintained! Do not use this when setting up AuScope experiments!

Differences

Page Tools