Differences

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

--- chara:trouble_shooting [2023/11/21 01:42]
charaobs [No Power for Aperture Wheels]
+++ chara:trouble_shooting [2025/04/17 21:39] (current)
charaobs [Metrology]
@@ Line 43: / Line 43: @@
   * E1 does not track past 218 degrees azimuth. The finder camera may be needed to find the star again. It will be off in azimuth, but should still show in the finder.
   * If a telescope is lost and star does not appear in the finder either, such as after a dome server crash and restart, a bright star, the moon or Jupiter can be used to get the scope pointing correctly. Anything brighter than Vmag 1 will show on the Spycam 1 view and can be used to get the scope close enough to find it in the finder, then ACQ. It should be placed just below the top bar of the telescope, centered left to right using the telescope paddle. You may have to pan up and down to see it move through the finder view. Use the obsgtk ADJUST tab scope paddle and set a step of 3000 and go up and down after centering it in the SPY 1 view below the top telescope bar. When you get it centered in the finder, manually init the scope to the AZ and EL on the MANUAL tab of the dome gui to one decimal place. Use Stellarium online or any resource to get the current position. You should then be able to slew to a star and center it in the finder, then ACQ and init on the obsgtk to get the scope back to usual.
 ===== The new OPLE system =====
@@ Line 53: / Line 52: @@
 If a cart cannot be started, stopped or otherwise commanded, look to the OPLESystem gui to see if a green indicator has turned red. A message will also often pop up on the ople gui saying the command could not be sent. This may require a simple start command to restart the server or a reboot of the computer to get it back to yellow and then a start to get it back to green. Do either of these steps with a right click of the red button and then select start or reboot. After a reboot, select start to load the servers after the indicator has turned yellow. When this is done, the ople server will need to be connected to the newly restarted server. Type "oo" into the ople server to open ople comms with the new ople server. It should now reappear on the ople server display and say System Ready to indicate comms are restored.
-Some times a cart is stopped and cannot be commanded. If the cart has gone to the front hard or back hard switch, it will not be usable until it is moved from the switch and the Ople Controller box is reset. There are 6 silver boxes for these controllers with two green LED's for the front and back switches and two red LED's for the back hard and front hard switches. If a red LED is lit, there will be an error displayed on the message window and the cart is disabled. The cart will need to be moved off the switch and then the box can be reset with the RESET button on the front. The error display will go away and the red LED will be off. The cart is now controllable.
+Some times a cart is stopped and cannot be commanded. If the cart has gone to the front hard or back hard switch, it will not be usable until it is moved from the switch and the Ople Controller box is reset. There are 6 silver boxes for these controllers with two green LED's for the front and back switches and two red LED's for the back hard and front hard switches. If a red LED is lit, there will be an error displayed on the message window, saying "FAULT" and the cart is disabled. The cart will need to be moved off the switch and then the box can be reset with the RESET button on the front. The error display will go away and the red LED will be off. The cart is now controllable.
 ===== Restarting Servers =====
@@ Line 105: / Line 104: @@
 Have the powers been turned on to the drives? Are the scopes disabled? The usual state of the telescopes is disabled until enabled. This is due to the stall function of the scopes which eventually disables the scopes when they are stowed. Enable the scopes by hitting [ENABLE] on the dome gui, the telescope gui control tab, or the bottom of the obsgtk. If a scope disables itself during a slew, it may be just an overcautious stall function or the slew gains may be too high or low. Check the gains and if they are OK, Hit ENABLE and the scope should continue to slew. If it disables again without moving, there may be something wrong at the scope, ie. a hatch left open, a ladder not put away, a tool on the floor, or something else physically impeding the motion of the scope. You will need to go to the dome to see what it is. The computer in the dome will give you control of the scope to turn it away from the problem. Make sure the scope is in a position that allows the opening of the hatch if you need to go upstairs. It can be moved back from the bunker as needed.
-Sometimes the dome guis get hung up and can cause erratic motion or no motion of the scopes. Check them for current times and continuous updates of numbers. If they are not updating, try to REOPEN them first. If that does not work, close the gui and open a new one. If a new one does not open, the dome server may be dead or Sockman lost track of it. See **Dome Server Restart**  below. \\  \\ **Azimuth Limit Switches** \\  \\ <font 14px/Arial,Helvetica,sans-serif;;inherit;;inherit>As of 11-'17, the azimuth limit switches are enabled and can stop the motion of the scopes if they try to go beyond -90º or 450º. The scopes will not be movable with normal inputs so follow these instructions to return them from the out of range condition. \\
+Sometimes the dome guis get hung up and can cause erratic motion or no motion of the scopes. Check them for current times and continuous updates of numbers. If they are not updating, try to REOPEN them first. If that does not work, close the gui and open a new one. If a new one does not open, the dome server may be dead or Sockman lost track of it. See **Dome Server Restart**  below.
+**Special Note for new drive (currently only S2 EL): **If the drive stops or will not begin a move, try clicking "manual" in the manual tab, then "auto" in the auto tab. If this doesn't help, then try the **Dome Server Restart.** \\  \\ **Azimuth Limit Switches** \\  \\ <font 14px/Arial,Helvetica,sans-serif;;inherit;;inherit>As of 11-'17, the azimuth limit switches are enabled and can stop the motion of the scopes if they try to go beyond -90º or 450º. The scopes will not be movable with normal inputs so follow these instructions to return them from the out of range condition. \\
 \\
 . On the domegui MANUAL tab, click STOP so pulses won't be sent to the drive by the control software. \\
@@ Line 116: / Line 117: @@
 <font 14px/Arial,Helvetica,sans-serif;;inherit;;inherit>1. On the domegui MANUAL tab, click STOP so pulses won't be sent to the drive by the control software. \\  \\
-.</font><font inherit/inherit;;initial;;white>M</font>ake sure all the scopes’ demand positions agree – for example, sometimes bringing a scope to a configuration that’s already on sky and issuing a slew command will make the additional scope go around North the “wrong” way. \\  \\ <font 14px/Arial,Helvetica,sans-serif;;inherit;;inherit>3. Click the OVERRIDE ON button in domegui MANUAL tab. After this, the hardware doesn't care about the limits switches and you're free to move the telescope.</font>
+.</font><font inherit/inherit;;initial;;white>M</font>ake sure all the scopes’ demand positions agree – for example, sometimes bringing a scope to a configuration that’s already on sky and issuing a slew command will make the additional scope go around North the “wrong” way. \\  \\ <font 14px/Arial,Helvetica,sans-serif;;inherit;;inherit>3. Click the OVERRIDE ON button in domegui MANUAL tab. After this, the hardware doesn't care about the limits switches and you're free to move the telescope. **NOTE: ****Using the overide is potentially damaging to the telescopes. **Only use override if you are certain the cable wrap or any other obstruction is not causing the drive to stall. If at all possible, go to the telescope and check the telescope position, drives, and cable wrap before using override.</font>
 <font 14px/Arial,Helvetica,sans-serif;;#333333;;inherit>4. Move the scope a bit back toward the direction it was coming from – for example, if the scope stopped at AZ 268 while rotating clockwise, move it back to 265 or so using AZ DEC. Then press STOP.</font>
@@ Line 125: / Line 126: @@
 <font 14px/Arial,Helvetica,sans-serif;;#333333;;inherit>7. When you have time, go to the scope and reset the limit switch; otherwise, it will stop each time you pass AZ 270/90. The LED will show red when on the limit switch and is tripped, ie. limiting motion of the scope. The LED will be yellow if it has tripped and is in the caution range, but not on a limit switch. A fine Allen key can be used to push the internal reset button or use the magnet and touch the box. It will turn the LED green when restored.</font>
+**Elevation Limit Switches**
+On occasion, the telescopes will trigger the upper or lower elevation limit switches. This can happen if the scope gets lost and is poorly inited in elevation or if the dome server fails. Sometimes the scope will go down in elevation even when the demand position is up.
+If a limit switch is triggered, try to back it out of the position by following the same rules as above.
+<font 14px/Arial,Helvetica,sans-serif;;inherit;;inherit>1. On the domegui MANUAL tab, click STOP so pulses won't be sent to the drive by the control software.</font> \\  \\ <font 14px/Arial,Helvetica,sans-serif;;inherit;;inherit>2. Click the OVERRIDE ON button in domegui MANUAL tab. After this, the hardware doesn't care about the limits switches and you're free to move the telescope. **NOTE: ****Using the overide is potentially damaging to the telescopes. **Only use override if you are certain the cable wrap or any other obstruction is not causing the drive to stall. If at all possible, go to the telescope and check the telescope position, drives, and cable wrap before using override. \\  \\
+. Click ENABLE then you can move the telescope back to its normal range of operation. Move the scope up or down to get out of the upper or lower limit situation. If it comes out, then go to the next step. \\  \\
+. After the telescope is back in it normal range, click OVERRIDE OFF which makes the hardware aware of the limits again and then hit AUTO on the AUTO tab to resume normal operation.</font>
+<font 14px/Arial,Helvetica,sans-serif;;inherit;;inherit>If the scope goes the opposite direction as commanded, disable the scope and</font>turn off the powers to the drives.
+Restart the dome server and type otcs in the telescope server. Reopen the dome gui. Make sure the demand position is the same as the scope position and not 0.0, 0.0.
+If it is not at the original position as when it stalled, enter that position in the manual tab and init the scope until the server and dome gui read correctly. Make sure the gains are at the same values as before and not all 22. Lower them as needed.
+If the scope position is correct and the demand position is above the lower limit, turn the powers back on and enable the scope. Watch as it comes out of the over limit position. Be ready to disable the scope if something else happens.
+The scope may need to be reinited if it doesn't find the star.
 ==== The Telescope won't track ====
@@ Line 139: / Line 160: @@
 Sometimes, the gains can be too low and the scope will overshoot the star position. Disable the scope, adjust the Slewing gain up one increment and enable the scope. It should return to the star.
+<font 14px/Arial,Helvetica,sans-serif;;inherit;;inherit>**NOTE: Whenever a gain is turned up, there is a chance of inducing telescope vibration ("foghorning"). **Whenever possible use the Amcrest cameras or go to the telescope to listen to it to make sure it's not foghorning.</font>
 ==== Dome Server Restart ====
@@ Line 174: / Line 197: @@
 This might mean that the gain for the tracking servo is wrong. Note that changing this gain can be dangerous, especially if you set it too high as that can cause the telescope to oscillated and damage the drives. Please only do this if you are very very sure that it is necessary. Symptoms of bad gain are: The scope over shoots the position while slewing. The star will be seen to move out of the window and may come back after a few seconds. This means the slewing gain is too low. The scope oscillates when tracking or after a slew. The star will be tracing an ellipse, figure eight or other looping shape. This means the tracking gain is too low. You can damp this out with the telescope or dome gui by disabling the scope, then re-enabling it. Adjust the gain upward and watch it on the next slew. In all cases if either gain is too high the scope will go into "Fog Horn" mode, which is bad. This can be seen during slews on the twfs or labao as vibrating spots, usually in one axis.
-You always want to use the lowest gain that still allows the scope to work as best as possible. If the tiptilt tells you the scope is oscillating slowly, the gain may be too low. If it is oscillating quickly it may be too high.
+Watching the drive position errors ("Er:) in the dome gui under "Az Vel" and "El Vel" are also a good place to look for drive tuning issues. These errors should ideally be <0.0003 and be stable, not oscillating. It may take some seconds for the errors to settle after tuning changes.
-The usual values for slewing gains are 4-7 and tracking gains are 7-10. Note that these values may change as the temperatures change rapidly. Gains are usually higher when cold and lower when warm. Be sure to set mode back to AUTO if changing the gains left it in Slewing or Tracking mode.
+**You always want to use the lowest gain that still allows the scope to work as best as possible.**  If the tiptilt tells you the scope is oscillating slowly, the gain may be too low. If it is oscillating quickly it may be too high.
+The usual values for slewing gains are 4-7 and tracking gains are 7-10. Note that these values may change as the temperatures change rapidly. Gains are usually higher when cold and lower when warm. **Be sure to set mode back to AUTO**  if changing the gains left it in Slewing or Tracking mode.
 ==== How to Adjust CPUMotor Gains ====
@@ Line 183: / Line 208: @@
 The GAIN controls the gain of the feedback between the encoder and the drive velocity. A high gain means a "stiffer" response, but can lead to oscillations or fog-horning if it's too high. \\  \\
 The Fn controls the maximum frequency of the servo response. A high Fn means higher frequencies are allowed through, which can mean correcting for faster problems but if too high can also lead to oscillations or fog-horning. \\  \\
-The software will not make changes to either of these quickly as that is a dangerous thing to do. There is NO POINT to clicking the up or down buttons more than once every few seconds. Indeed it is bad to do so as you will confuse the software. The change between slewing and tracking is also slow for similar reasons. This is why sometimes the "wrong" thing seems to change. It is a sign that you are trying to do things too quickly. \\  \\
+The software will not make changes to either of these quickly as that is a dangerous thing to do. **There is NO POINT to clicking the up or down buttons more than once every few seconds.**  Indeed it is bad to do so as you will confuse the software. The change between slewing and tracking is also slow for similar reasons. This is why sometimes the "wrong" thing seems to change. It is a sign that you are trying to do things too quickly.
+  - Identify if the issue is in Slew mode or Track mode, click "slewing" or "Tracking" to set the mode you're adjusting.
+  - Idenfity the telescope drive with which the issue is occuring, El or Az, and only adjust that gain and/or Fn.
+  - (optional) Quit the dome gui and open a new one, this should make sure the numbers are accurate in the CPUMOTOR tab.
+  - If at all possible, listen to the telescope drive for foghorning! If foghorning occurs immediately turn down the gain or Fn.
+  - Adjust the gain and/or Fn:
+      - For tracking issues: Watch the star in acq for signs of oscillation and turn down the gain and/or Fn one step for fast oscilation or foghorning. For slow response, telescope not reaching/slowly chasing target, slow oscilations, or switching between slew and track modes: turn up the gain and/or Fn one step. change only gain or Fn at a time and after an adjustment watch for ~10 seconds for the change to gradually be implemented.
+      - For slewing issues: Watch the "Er" numbers for the appropriate axis and try to get them to <0.0002 and stable, not increasing or decreasing.
+**Special Note: S2 El drive is tuned in entirely different way and adjusting the CPUMOTOR settings will not help.**  If there are issues with the S2 El drive, contact nic.
 Slew and tracking mode work differently, mostly because the speeds are so different. \\  \\
 IN SLEWING MODE \\  \\
@@ Line 208: / Line 243: @@
 {{:chara:files:e1_hut_coms_recovery.pdf|E1 HuT and Cooler Communications Recovery}}
-==== S2 Acquisition Server Restart ====
+==== Acquisition Server Restarts ====
+Most ACQ servers run on the wfs computer at the scope. 2 scopes do not.
+S2's acquisition server resides on "S2pi4" computer. Logging on to it (ssh s2pi4) and running bootlaunch will restart it.
-S2's acquisition server resides on "S2pi4" computer. Logging on to it (ssh s2pi4) and running bootlaunch will restart it
+E1 ACQ and Finder both live on the e1zwo rasperry pi computer. Use ssh e1zwo to log in and run bootlaunch_master to find its PID and kill it and bootlaunch_master again to start it.
 ==== Focusing the Telescope ====
+**NOTE: Focusing the telescope is a RARELY needed occurance and should not be done often (on the order of 1-2 times per year).**  Often the issue has a different cause and adjusting the focus of the telescope makes everything worse. The telescopes are extremely carefully focused after mirror recoats and realignments, and only on exceptional seeing nights when all other optical systems have been aligned extremely carefully. Do Not adjust the telescope focus unless you are very sure these requirements are met. Contact Nic, Rob, or Karolina if in doubt and email the tech email list that the focus has been adjusted, and by how much (note the before and after positions for the X, Y, and Z actuators).
   - Fully align beacon to labao and TWFS, especially making sure the focus terms between the two agree very well.
   - Open a secondary gui: mergurygtk W2_SECONDARY.
@@ Line 289: / Line 329: @@
   * To home the carts, turn off the [OL] and [MAN] buttons on each cart and it will automatically return to the front switch. If the cart has no issue, it will arrive at the target position of 0m and the home switch at the same time. The X in the OPLE server under the HM will indicate it has stopped on the home switch. If a cart does not reach the home switch when it returns to position 0m, it was lost and likely the cause of the difficulty in finding fringes. The X does not guarantee the cart has retained its home position. This home position can be checked by using the CHECK button on the ople gui or by typing the command “homechk S1” into the ople server. When the error value is displayed on the ople server, hit ESC to clear the display. Click on the [OL] and [MAN] buttons and hit [TRACK] to send the cart to the desired cart position.
-==== Metrology ====
-  * Good metrology signals are important to the proper positioning of the carts. Monitor the signal strength by running [RUN MULTIPLE] on the Metrology Monitor. Place the windows above the TV windows for each scope you are using. They should show white sine waves that are around the height of the window. Erratic, fluctuating waves indicate self-interference or a weak signal. This may cause the carts to lose their place as the signal strength falls too low. Red waves indicate that some displayed signal has gone too low and the carts will all need to be homed. A careful adjustment of the MET2 mirror can sometimes bring the signal back. Do not adjust the MET1 mirror
-Steps for adjusting MET2:
-  - Looking at the met signal while the cart is at the back.
-  - Peak so that the beam is aligned as well as possible. Does not need to be perfect but not loose.
-  - All beams have a signal between 1-2 volts while at the back. Sometimes the signal strength can change for no apparent reasons.
-  - Using steps of 50, try moving 3 times in one direction. After each step, wait 5 seconds or so for things to update. If nothing then try the other way.
-  - Return to starting position.
-  - Repeat for the other axis.
-===== Beam Samplers =====
-==== Beam Samplers are not moving (not a problem anymore) ====
-This happens most frequently with the E1 beam sampler. If you are doing alignments and are using E1, try to move it forward first to see if it dies. If it does, follow this procedure.
-  * Turn off power on Newport Universal Motion Controller/Driver for the Beam Samplers (on top of rack in computer area, labelled "BS")
-  * Then go behind the racks and locate the serial port for BS. Look for all of the blue ethernet cables coming out. BS is labelled in prt 2. Remove the ethernet cable for BS. The step stool is available to make it easier to reach the blue ethernet cable at the back of the BS controller box.
-  * Restart BS controller (press power button again). Wait for all axes to appear on screen.
-  * Plug the ethernet cable back in.
-  * Restart BS server on ctrscrut using commands in /etc/rc.local (see instructions below)
-  * Reopen Beam Sampler GUI. You will need to home each Beam Sampler one by one. You should be able to do this from the regular Beam Sampler GUI. If that doesn't work, try opening "espgtk BS" from the command line.
-==== Restarting the Beam Sampler Server ====
-The most common cause for getting multiple copies of a server is using the socket manage RESTART button, which is flaky at best. Don't do this. If you need to restart a server you should do it manually.
-. Make sure you are logged into the right machine: ssh ctrscrut
-. If you are not sure see if the socket manager will tell you. If it doesn't have a look in the file: /ctrscrut/chara/etc/sock_manager/socket_manager.list
-. See if there are any ghosts running
-ps aux | grep esp_server
-Yes, it's hard to know which one it is with the esp servers. You can work out which ones are ghosts by typing the command
-tsockman |grep ctrscrut
-which will give you a list of the servers running on the machine you are interested in. Checking for non-matching PIDs will tell you which processes you need to stop.
-. Stop those processes:
-kill -9 PID1 PID2 ….
-. Make sure there is no sign of it in the socket manager
-tsockman rm BS
-. Restart the beam sampler servers (this starts both beam sampler servers BS1 and BS2):
-bootlaunch_beamsamp
-==== "Failed to request position of S1" ====
-Cosmic Debris reports "Failed to request position of S1" when trying to set the beam order. This indicates that ople is no longer talking to the beam samplers. If the beam sampler server has been restarted recently, then the ople server will also need to be restarted to re-establish the connection. \\  \\
-The beam sample server runs on ctrscrut. The ople server tries to open a connection to the beam sampler when it starts. If the beam sampler is not there, or dies, \\
-you need to restart the ople server as there is no command to reopen that connection.
-===== Remote Observing =====
-==== VPN connection is not working ====
-To re-establish the VPN connection, follow these steps:
-  * Open VPN status page from the firefox web broswer. To do this, click on the "AROC VPN reconnect" icon on the zoot desktop. Alternatively, you can open the firefox web browser and go to 192.168.3.1/vpn_sta.htm
-  * The browser will prompt you for the admin user name and password. If these entries are not already filled in, then look for this information on the papers near the console.
-  * If the browser does not open, then check if there are other instances of firefox already running. To do this, open a terminal window, type "ps auxw | grep firefox", and kill the other instances of firefox so that you can open a new window.
-  * When the VPN connection is working, it will report "Phase 1: M-ESTABLISHED / Phase 2: ESTABLISHED" under the state column.
-  * If either Phase 1 or Phase 2 states say IDLE for a given VPN, then you need to re-establish the connection. To do this, click on the "DROP" button for that VPN. Then click on the "CONNECT" button and wait for the Phase 1 and Phase 2 connections to be established.
-  * Make sure to close Firefox by using CTRL-Q to quit the program and not just close the window.
-===== Network Problems =====
-==== User accounts not recognized ====
-The gps computer does the user authentication for the control side while ctrscrut provides the home directories. Yellowpages is gone, the new paradigm is LDAP (local directory access protocol). If you can't log on to computers on the control network, then make sure both ctscrut (michelson) and gps computers are running. If the login screen screen on ctrscrut says "Ubuntu Administrator" and has no user accounts, then check to make sure gps computer is on. If you restart gps, then you might have to reboot ctrscrut to get the user accounts. If ctrscrut was rebooted, you might have to reboot other control network computers if you can't log on.
-If gps computer does not start, check the power distribution unit (PDU) at the top of that rack. If any units show both " " and "-" then you can use the arrow buttons to move through the units and cycle the units to on " ". That should automatically start the computer connected to those units.
-===== General Problems =====
-==== GUIs are frozen ====
-Check to see if Sockman is working. Click the [LIST] button on sockman. If the list doesn't come up, Sockman may be hung up. Follow the Sockman restart procedure in the text file on the desktop if it won't respond.
-Hit [REOPEN] on the gui to see if it reconnects with its server. if that does not fix it, the server may be dead. From the LIST on Sockman, select the server suspected of being frozen. Ping it and if it reports back as being dead, see [[:chara:trouble_shooting#server_is_frozen|Server is frozen]] section below.
-Telescope guis often freeze. Hit reopen on the gui to bring it back to life. Hitting [MOVE] on the telescope gui before the star has stopped moving can cause the gui to freeze. Avoid doing this. Close the dead one and open a new one to fix the problem.
-==== Server display is blank or filled with jibberish ====
-  * If the top of a server goes blank, try typing "sb" (start background) on the server command line.
-  * If the server screen fills with jibberish, try hitting CTRL-L in the server to clear it.
-  * If a server freezes, sometimes hitting CTRL-C and then N, for NO, will unfreeze it.
-==== Server is frozen ====
-Try quitting the server using CTRL-C and entering "Y". If that doesn't work, try the following:
-  * On Sockman, click [LIST] and select the appropriate server. It will give a PID number you can use to kill the server in a terminal. Open a terminal and follow the directions for Restarting Servers above.
-  * If a server window does not close, click the X in the upper right corner to close it, but only after getting the PID from Sockman.
-  * Click [REOPEN] on Cosmic Debris and relevant GUIs to re-initialize communication with the server after it is restarted.
-  * A folder is on the desktop that has the restart commands for CTRSCRUT servers and the Shutters server restart command running on OPLE. Use it to restart servers that will not reopen from the menu.
-  * if a telescope server does not close after using CTRL-C when restarting them after UT midnight and the Send ON button is green on the obsgtk, turn the Send ON to OFF and the server will close. Turn the Send ON button back on to resume the setup for the night.
-==== PAVO Server - Error communicating with IFW ====
-The following error message sometimes appears when starting the PAVO server: "Error communicating with IFW. Could not read from IFW. Is the filter wheel plugged in and on?" Most of the time, restarting the PAVO server will clear this error message and allow PAVO to communicate with the filter wheel. If restarting the server doesn't help, then check that the cables going into the small, black IFW box on the PAVO table and into the back of the PAVO computer are plugged in securely.
-==== Adding or Finding a Star in the CHARA Database ====
-The command "dbadd" can be used to look up the CHARA number for a star or to add a star to the CHARA database. To use dbadd, open a terminal window, and type "dbadd starname" where starname is the common name (e.g., Vega) or identifier of the star (e.g., IRC, HR, HD, SAO, FK5, HIP, GJ, or 2MASS designation). If the object is in the database, then it will return the CHARA number.
-You can also look up different identifiers for the star by using the SIMBAD database: [[http://simbad.u-strasbg.fr/simbad/sim-fbasic|http://simbad.u-strasbg.fr/simbad/sim-fbasic]]
-DBADD uses SIMBAD to look up the coordinates of the star and then searches to see if the star is already in the CHARA database. If the star is in the database, it will return the CHARA number. If the star is not in the CHARA database, it will ask if you want to add it and will assign a CHARA number if you answer yes.
-If an object is not in SIMBAD (such as a recently discovered nova), then you must enter the object manually using the instructions below.
-**Finding a star in the CHARA database**
-Here is an example of how to find the CHARA number of a star, nova, or AGN that is already in the CHARA database:
-[ctrscrut:502] dbadd NGC 4151 \\
-Object "NGC 4151" found as CHARA number: 320263
-Note: If the target information stored in the CHARA database does not match SIMBAD, then dbadd will provide the coordinates and magnitudes listed in SIMBAD, and it will also list the CHARA numbers of objects in the database located within 10 arcsec. Please check these nearby entries before adding a new star to the database.
-**Targets that are not in the CHARA database**
-If an object is not in the CHARA database, then you can use dbadd to query SIMBAD and add the star to the CHARA database. This might need to be done for faint stars, novae, and AGN. If the object is found in SIMBAD, then dbadd will return the target's coordinates, magnitudes, and spectral type and ask if this it the object for which you are looking. If you answer yes, then dbadd will issue a CHARA number and add the object to the database. Please check the target coordinates to make sure that they are correct before adding a new star to the database.
-Here is an example of how to add an object to the CHARA database:
-[ctrscrut:534] dbadd BD 41 3807
-SIMBAD found this for "BD 41 3807":
-ID 2MASS_J20340850 4136592 \\
-CHARA 320414 \\
-.0 \\
-CAT8 2MASS_J20340850 4136592 \\
-RA 20 34 08.5148 \\
-DEC 41 36 59.408 \\
-PMRA -2.32 \\
-PMDEC -3.87 \\
-PAR 0.58 \\
-RVEL -27.50
-VMAG 10.03 \\
-HMAG 6.23 \\
-KMAG 5.99 \\
-SP O5.5Ifc \\
-END
-Is the above the object you are looking for? [y/n] y \\
-Added "BD 41 3807" to the database.
-In the example above, the object "BD 41 3807" has been added to the database as CHARA number 320414.
-**Targets that are not in SIMBAD**
-Some objects like recently discovered novae are not in SIMBAD. Entering dbadd <star designation> for a star not in the SIMBAD database returns the message "Simbad is unable to find an object matching <star designation>. Try using a different catalog designation, or use the "-m" switch to add the object manually."
-The command dbadd -m is used by entering the star name and coordinates in this format:
-Usage: dbadd -m <name> <RA> <Dec> \\  \\
-<name>: Object ID (no spaces) \\  \\
-<RA> : XXhXXmXX.X or XXhXX.X (no spaces) \\  \\
-<Dec> : XXdXXmXX.X or XXdXX.X (no spaces) \\  \\
-There are cases where an object is not in SIMBAD and doesn't return a result in dbadd, but is in fact in the CHARA database. Novae and AGN's are the likely objects that cause this result. At times, objects have multiple entries and several CHARA numbers since the names can be so unique. A system will be developed to find these entries without knowing or having a conventional database designation.
-**Binary stars**
-Some binary stars have a common HD number with an A or B after them. These can cause problems as Cosmic Debris does not accept non numerical entries when filling in star designation. These stars are likely in CHARA's database but need to be searched in dbadd or on SIMBAD to get the CHARA number or another designation.
-When a recognized identifier is entered, the HD number with A or B will usually display. Confirm that the coordinates, magnitudes and spectral type match the star desired. If they do not match, you may have the wrong star or the database may have the wrong info and the baseline solution will be affected. Offsets based on incorrect coordinates or misidentifications can move the fringes many thousands of microns away from the calculated position. This can happen when observing a dim companion (B) using the brighter (A) companion's coordinates. Inform the observers that saving and using the CHARA number will save time the next time the target is observed.
-**Editing the database:**  If you find a mistake in the database, please send an email to Nils to have it corrected. Identify what you believe to be the error and what is the correct information.
-==== Adding an anchor to the wiki page ====
-To add an anchor to the wikipage, type the following where you want the anchor inserted (without the spaces between the symbols): \\
-[ [ #AnchorName ] ]
-Highlight the text you want to be a link to the anchor, click the link symbol above and select anchor. Select a page(such as Trouble Shooting) where the anchor is located and give the same name for the anchor.
-==== Displays for the MIRC-X wolverine2 monitors ====
-Follow instructions in the [[:chara:mircx_monitors|linked page to display the MIRC-X wolverine2 monitors]] in the control room.
-===== The new OPLE system =====
-With the implementation of the new ople system which replaced the VME in Fall of 2021, new troubleshooting issues have arisen. Since there are now 6 new ople computers to run the carts for each scope individually, many issues will be specific to one computer or telescope and not to the system as a whole. Restarting the VME is now a thing of the past.
-The traditional ople server will still be used to communicate with each new ople computer, identified as OPLE 1 to OPLE 6. When the communications are good, each active cart will be displayed in the ople server or ople gui status tab as before. At times, an ople computer can lose communications or a server can crash and the server or comms needs to be restarted.
-If a cart cannot be started, stopped or otherwise commanded, look to the OPLESystem gui to see if a green indicator has turned red. A message will also often pop up on the ople gui saying the command could not be sent. This may require a simple start command to restart the server or a reboot of the computer to get it back to yellow and then a start to get it back to green. Do either of these steps with a right click of the red button and then select start or reboot. After a reboot, select start to load the servers after the indicator has turned yellow. When this is done, the ople server will need to be connected to the newly restarted server. Type "oo" into the ople server to open ople comms with the new ople server. It should now reappear on the ople server display and say System Ready to indicate comms are restored.
-Some times a cart is stopped and cannot be commanded. If the cart has gone to the front hard or back hard switch, it will not be usable until it is moved from the switch and the Ople Controller box is reset. There are 6 silver boxes for these controllers with two green LED's for the front and back switches and two red LED's for the back hard and front hard switches. If a red LED is lit, there will be an error displayed on the message window and the cart is disabled. The cart will need to be moved off the switch and then the box can be reset with the RESET button on the front. The error display will go away and the red LED will be off. The cart is now controllable.
 ===== Restarting Servers =====
@@ Line 583: / Line 418: @@
 Have the powers been turned on to the drives? Are the scopes disabled? The usual state of the telescopes is disabled until enabled. This is due to the stall function of the scopes which eventually disables the scopes when they are stowed. Enable the scopes by hitting [ENABLE] on the dome gui, the telescope gui control tab, or the bottom of the obsgtk. If a scope disables itself during a slew, it may be just an overcautious stall function or the slew gains may be too high or low. Check the gains and if they are OK, Hit ENABLE and the scope should continue to slew. If it disables again without moving, there may be something wrong at the scope, ie. a hatch left open, a ladder not put away, a tool on the floor, or something else physically impeding the motion of the scope. You will need to go to the dome to see what it is. The computer in the dome will give you control of the scope to turn it away from the problem. Make sure the scope is in a position that allows the opening of the hatch if you need to go upstairs. It can be moved back from the bunker as needed.
-Sometimes the dome guis get hung up and can cause erratic motion or no motion of the scopes. Check them for current times and continuous updates of numbers. If they are not updating, try to REOPEN them first. If that does not work, close the gui and open a new one. If a new one does not open, the dome server may be dead or Sockman lost track of it. See **Dome Server Restart** below.\\
+Sometimes the dome guis get hung up and can cause erratic motion or no motion of the scopes. Check them for current times and continuous updates of numbers. If they are not updating, try to REOPEN them first. If that does not work, close the gui and open a new one. If a new one does not open, the dome server may be dead or Sockman lost track of it. See **Dome Server Restart** below.
+**Special Note for new drive (currently only S2 EL): **If the drive stops or will not begin a move, try clicking "manual" in the manual tab, then "auto" in the auto tab. If this doesn't help, then try the **Dome Server Restart.** \\
 \\
 **Azimuth Limit Switches** \\
@@ Line 605: / Line 442: @@
 .</font><font inherit/inherit;;initial;;white>M</font>ake sure all the scopes’ demand positions agree – for example, sometimes bringing a scope to a configuration that’s already on sky and issuing a slew command will make the additional scope go around North the “wrong” way.\\
 \\
-<font 14px/Arial,Helvetica,sans-serif;;inherit;;inherit>3. Click the OVERRIDE ON button in domegui MANUAL tab. After this, the hardware doesn't care about the limits switches and you're free to move the telescope.</font>
+<font 14px/Arial,Helvetica,sans-serif;;inherit;;inherit>3. Click the OVERRIDE ON button in domegui MANUAL tab. After this, the hardware doesn't care about the limits switches and you're free to move the telescope. **NOTE: ****Using the overide is potentially damaging to the telescopes. **Only use override if you are certain the cable wrap or any other obstruction is not causing the drive to stall. If at all possible, go to the telescope and check the telescope position, drives, and cable wrap before using override.</font>
 <font 14px/Arial,Helvetica,sans-serif;;#333333;;inherit>4. Move the scope a bit back toward the direction it was coming from – for example, if the scope stopped at AZ 268 while rotating clockwise, move it back to 265 or so using AZ DEC. Then press STOP.</font>
@@ Line 614: / Line 451: @@
 <font 14px/Arial,Helvetica,sans-serif;;#333333;;inherit>7. When you have time, go to the scope and reset the limit switch; otherwise, it will stop each time you pass AZ 270/90. The LED will show red when on the limit switch and is tripped, ie. limiting motion of the scope. The LED will be yellow if it has tripped and is in the caution range, but not on a limit switch. A fine Allen key can be used to push the internal reset button or use the magnet and touch the box. It will turn the LED green when restored.</font>
+**Elevation Limit Switches**
+On occasion, the telescopes will trigger the upper or lower elevation limit switches. This can happen if the scope gets lost and is poorly inited in elevation or if the dome server fails. Sometimes the scope will go down in elevation even when the demand position is up.
+If a limit switch is triggered, try to back it out of the position by following the same rules as above.
+<font 14px/Arial,Helvetica,sans-serif;;inherit;;inherit>1. On the domegui MANUAL tab, click STOP so pulses won't be sent to the drive by the control software.</font>\\
+\\
+<font 14px/Arial,Helvetica,sans-serif;;inherit;;inherit>2. Click the OVERRIDE ON button in domegui MANUAL tab. After this, the hardware doesn't care about the limits switches and you're free to move the telescope. **NOTE: ****Using the overide is potentially damaging to the telescopes. **Only use override if you are certain the cable wrap or any other obstruction is not causing the drive to stall. If at all possible, go to the telescope and check the telescope position, drives, and cable wrap before using override.\\
+\\
+. Click ENABLE then you can move the telescope back to its normal range of operation. Move the scope up or down to get out of the upper or lower limit situation. If it comes out, then go to the next step.\\
+\\
+. After the telescope is back in it normal range, click OVERRIDE OFF which makes the hardware aware of the limits again and then hit AUTO on the AUTO tab to resume normal operation.</font>
+<font 14px/Arial,Helvetica,sans-serif;;inherit;;inherit>If the scope goes the opposite direction as commanded, disable the scope and</font>turn off the powers to the drives.
+Restart the dome server and type otcs in the telescope server. Reopen the dome gui. Make sure the demand position is the same as the scope position and not 0.0, 0.0.
+If it is not at the original position as when it stalled, enter that position in the manual tab and init the scope until the server and dome gui read correctly. Make sure the gains are at the same values as before and not all 22. Lower them as needed.
+If the scope position is correct and the demand position is above the lower limit, turn the powers back on and enable the scope. Watch as it comes out of the over limit position. Be ready to disable the scope if something else happens.
+The scope may need to be reinited if it doesn't find the star.
 ==== The Telescope won't track ====
@@ Line 628: / Line 489: @@
 Sometimes, the gains can be too low and the scope will overshoot the star position. Disable the scope, adjust the Slewing gain up one increment and enable the scope. It should return to the star.
+<font 14px/Arial,Helvetica,sans-serif;;inherit;;inherit>**NOTE: Whenever a gain is turned up, there is a chance of inducing telescope vibration ("foghorning"). **Whenever possible use the Amcrest cameras or go to the telescope to listen to it to make sure it's not foghorning.</font>
 ==== Dome Server Restart ====
@@ Line 663: / Line 526: @@
 This might mean that the gain for the tracking servo is wrong. Note that changing this gain can be dangerous, especially if you set it too high as that can cause the telescope to oscillated and damage the drives. Please only do this if you are very very sure that it is necessary. Symptoms of bad gain are: The scope over shoots the position while slewing. The star will be seen to move out of the window and may come back after a few seconds. This means the slewing gain is too low. The scope oscillates when tracking or after a slew. The star will be tracing an ellipse, figure eight or other looping shape. This means the tracking gain is too low. You can damp this out with the telescope or dome gui by disabling the scope, then re-enabling it. Adjust the gain upward and watch it on the next slew. In all cases if either gain is too high the scope will go into "Fog Horn" mode, which is bad. This can be seen during slews on the twfs or labao as vibrating spots, usually in one axis.
-You always want to use the lowest gain that still allows the scope to work as best as possible. If the tiptilt tells you the scope is oscillating slowly, the gain may be too low. If it is oscillating quickly it may be too high.
+Watching the drive position errors ("Er:) in the dome gui under "Az Vel" and "El Vel" are also a good place to look for drive tuning issues. These errors should ideally be <0.0003 and be stable, not oscillating. It may take some seconds for the errors to settle after tuning changes.
-The usual values for slewing gains are 4-7 and tracking gains are 7-10. Note that these values may change as the temperatures change rapidly. Gains are usually higher when cold and lower when warm. Be sure to set mode back to AUTO if changing the gains left it in Slewing or Tracking mode.
+**You always want to use the lowest gain that still allows the scope to work as best as possible.** If the tiptilt tells you the scope is oscillating slowly, the gain may be too low. If it is oscillating quickly it may be too high.
+The usual values for slewing gains are 4-7 and tracking gains are 7-10. Note that these values may change as the temperatures change rapidly. Gains are usually higher when cold and lower when warm. **Be sure to set mode back to AUTO** if changing the gains left it in Slewing or Tracking mode.
 ==== How to Adjust CPUMotor Gains ====
@@ Line 674: / Line 538: @@
 The Fn controls the maximum frequency of the servo response. A high Fn means higher frequencies are allowed through, which can mean correcting for faster problems but if too high can also lead to oscillations or fog-horning.\\
 \\
-The software will not make changes to either of these quickly as that is a dangerous thing to do. There is NO POINT to clicking the up or down buttons more than once every few seconds. Indeed it is bad to do so as you will confuse the software. The change between slewing and tracking is also slow for similar reasons. This is why sometimes the "wrong" thing seems to change. It is a sign that you are trying to do things too quickly.\\
+The software will not make changes to either of these quickly as that is a dangerous thing to do. **There is NO POINT to clicking the up or down buttons more than once every few seconds.** Indeed it is bad to do so as you will confuse the software. The change between slewing and tracking is also slow for similar reasons. This is why sometimes the "wrong" thing seems to change. It is a sign that you are trying to do things too quickly.
-\\
-Slew and tracking mode work differently, mostly because the speeds are so different.\\
+   - Identify if the issue is in Slew mode or Track mode, click "slewing" or "Tracking" to set the mode you're adjusting.
-\\
+  - Idenfity the telescope drive with which the issue is occuring, El or Az, and only adjust that gain and/or Fn.
-IN SLEWING MODE\\
+  - (optional) Quit the dome gui and open a new one, this should make sure the numbers are accurate in the CPUMOTOR tab.
-\\
+  - If at all possible, listen to the telescope drive for foghorning! If foghorning occurs immediately turn down the gain or Fn.
-- If the gain is too low you will overshoot the target.\\
+  - Adjust the gain and/or Fn:
-\\
+      - For tracking issues: Watch the star in acq for signs of oscillation and turn down the gain and/or Fn one step for fast oscilation or foghorning. For slow response, telescope not reaching/slowly chasing target, slow oscilations, or switching between slew and track modes: turn up the gain and/or Fn one step. change only gain or Fn at a time and after an adjustment watch for ~10 seconds for the change to gradually be implemented.
-- If the gain is too high it will fog-horn.\\
+      - For slewing issues: Watch the "Er" numbers for the appropriate axis and try to get them to <0.0002 and stable, not increasing or decreasing.
-\\
-- If the Fn is too high it will also fog-horn, even at low gains.\\
+**Special Note: S2 El drive is tuned in entirely different way and adjusting the CPUMOTOR settings will not help.**  If there are issues with the S2 El drive, contact nic.
-\\
-You need to have the lowest possible gain and Fn in slew mode that doesn't overshoot the target. Fn in slew mode should almost never be higher than 4. If it is, please turn it back down to 4. If you think this is a problem please let Theo know, along with a detailed explanation of what happened.\\
+Slew and tracking mode work differently, mostly because the speeds are so different. \\  \\
-\\
+IN SLEWING MODE \\  \\
-IN TRACKING MODE\\
+- If the gain is too low you will overshoot the target. \\  \\
-\\
+- If the gain is too high it will fog-horn. \\  \\
-- If the gain is too low it will keep moving between slewing and tracking.\\
+- If the Fn is too high it will also fog-horn, even at low gains. \\  \\
-\\
+You need to have the lowest possible gain and Fn in slew mode that doesn't overshoot the target. Fn in slew mode should almost never be higher than 4. If it is, please turn it back down to 4. If you think this is a problem please let Theo know, along with a detailed explanation of what happened. \\  \\
-- If the gain is too high it will fog-horn.\\
+IN TRACKING MODE \\  \\
-\\
+- If the gain is too low it will keep moving between slewing and tracking. \\  \\
-- The same goes for Fn.\\
+- If the gain is too high it will fog-horn. \\  \\
-\\
+- The same goes for Fn. \\  \\
-In tracking mode you want the highest gain and Fn that allows the telescope to track well without fog-horning. If it "oscillates", which you will see in the green dots of tiptilt oscillating, try turning up the gain, and also try turning down the Fn.\\
+In tracking mode you want the highest gain and Fn that allows the telescope to track well without fog-horning. If it "oscillates", which you will see in the green dots of tiptilt oscillating, try turning up the gain, and also try turning down the Fn. \\  \\
-\\
+Some final remarks: \\  \\
-Some final remarks:\\
+- The gain is temperature dependent, so when the temperature changes these things will change, but more so for tracking. \\  \\
-\\
+- The tiptilt system almost never causes oscillations, it almost always shows you that the scope is oscillating. If the white dots are centered on tiptilt and the green dots are moving the tiptilt is doing it's job and correcting for scope motion. \\  \\
-- The gain is temperature dependent, so when the temperature changes these things will change, but more so for tracking.\\
-\\
-- The tiptilt system almost never causes oscillations, it almost always shows you that the scope is oscillating. If the white dots are centered on tiptilt and the green dots are moving the tiptilt is doing it's job and correcting for scope motion.\\
-\\
 - If a drive gets disabled at the end of a slew, the gain is too low. At low gain and low velocity the encoder signal changes very slowly or doesn't change at all. After 5 secs the software interprets this as a stall and disables the drive. The tricky part is that increasing the gain to avoid this situation might make the telescope to oscillate during the next slew. So the gain should be low (4 or even 1) during slewing but higher 7 or 10 when the telescope is basically at the target position.
@@ Line 714: / Line 574: @@
 {{:chara:files:e1_hut_coms_recovery.pdf|E1 HuT and Cooler Communications Recovery}}
-==== S2 Acquisition Server Restart ====
+==== Acquisition Server Restarts ====
+Most ACQ servers run on the wfs computer at the scope. 2 scopes do not.
+S2's acquisition server resides on "S2pi4" computer. Logging on to it (ssh s2pi4) and running bootlaunch will restart it.
-S2's acquisition server resides on "S2pi4" computer. Logging on to it (ssh s2pi4) and running bootlaunch will restart it
+E1 ACQ and Finder both live on the e1zwo rasperry pi computer. Use ssh e1zwo to log in and run bootlaunch_master to find its PID and kill it and bootlaunch_master again to start it.
 ==== Focusing the Telescope ====
+**NOTE: Focusing the telescope is a RARELY needed occurance and should not be done often (on the order of 1-2 times per year).**  Often the issue has a different cause and adjusting the focus of the telescope makes everything worse. The telescopes are extremely carefully focused after mirror recoats and realignments, and only on exceptional seeing nights when all other optical systems have been aligned extremely carefully. Do Not adjust the telescope focus unless you are very sure these requirements are met. Contact Nic, Rob, or Karolina if in doubt and email the tech email list that the focus has been adjusted, and by how much (note the before and after positions for the X, Y, and Z actuators).
   - Fully align beacon to labao and TWFS, especially making sure the focus terms between the two agree very well.
   - Open a secondary gui: mergurygtk W2_SECONDARY.
@@ Line 805: / Line 670: @@
   - Peak so that the beam is aligned as well as possible. Does not need to be perfect but not loose.
   - All beams have a signal between 1-2 volts while at the back. Sometimes the signal strength can change for no apparent reasons.
-  - Using steps of 50, try moving 3 times in one direction. After each step, wait 5 seconds or so for things to update. If nothing then try the other way.
+  - Using a step size of 23, try moving 3 times in one direction. After each step, wait 5 seconds or so for things to update. If nothing then try the other way.
-  - Return to starting position.
+  - Return to the starting position.
   - Repeat for the other axis.
@@ Line 996: / Line 861: @@
 {{:chara:d859af0efb2dab690d3a44526d7b8afc.png}}
+==== Restarting the STST Computer ====
+{{:chara:ccd9641c95c5221f810129e671f441f0.png}}
+ \\
+Last updated 2024-07-22 END HERE
+===== Beam Samplers =====
+==== Beam Samplers are not moving (not a problem anymore) ====
+This happens most frequently with the E1 beam sampler. If you are doing alignments and are using E1, try to move it forward first to see if it dies. If it does, follow this procedure.
+  * Turn off power on Newport Universal Motion Controller/Driver for the Beam Samplers (on top of rack in computer area, labelled "BS")
+  * Then go behind the racks and locate the serial port for BS. Look for all of the blue ethernet cables coming out. BS is labelled in prt 2. Remove the ethernet cable for BS. The step stool is available to make it easier to reach the blue ethernet cable at the back of the BS controller box.
+  * Restart BS controller (press power button again). Wait for all axes to appear on screen.
+  * Plug the ethernet cable back in.
+  * Restart BS server on ctrscrut using commands in /etc/rc.local (see instructions below)
+  * Reopen Beam Sampler GUI. You will need to home each Beam Sampler one by one. You should be able to do this from the regular Beam Sampler GUI. If that doesn't work, try opening "espgtk BS" from the command line.
+==== Restarting the Beam Sampler Server ====
+The most common cause for getting multiple copies of a server is using the socket manage RESTART button, which is flaky at best. Don't do this. If you need to restart a server you should do it manually.
+. Make sure you are logged into the right machine: ssh ctrscrut
+. If you are not sure see if the socket manager will tell you. If it doesn't have a look in the file: /ctrscrut/chara/etc/sock_manager/socket_manager.list
+. See if there are any ghosts running
+ps aux | grep esp_server
+Yes, it's hard to know which one it is with the esp servers. You can work out which ones are ghosts by typing the command
+tsockman |grep ctrscrut
+which will give you a list of the servers running on the machine you are interested in. Checking for non-matching PIDs will tell you which processes you need to stop.
+. Stop those processes:
+kill -9 PID1 PID2 ….
+. Make sure there is no sign of it in the socket manager
+tsockman rm BS
+. Restart the beam sampler servers (this starts both beam sampler servers BS1 and BS2):
+bootlaunch_beamsamp
+==== "Failed to request position of S1" ====
+Cosmic Debris reports "Failed to request position of S1" when trying to set the beam order. This indicates that ople is no longer talking to the beam samplers. If the beam sampler server has been restarted recently, then the ople server will also need to be restarted to re-establish the connection. \\  \\
+The beam sample server runs on ctrscrut. The ople server tries to open a connection to the beam sampler when it starts. If the beam sampler is not there, or dies, \\
+you need to restart the ople server as there is no command to reopen that connection.
+===== Remote Observing =====
+==== VPN connection is not working ====
+To re-establish the VPN connection, follow these steps:
+  * Open VPN status page from the firefox web broswer. To do this, click on the "AROC VPN reconnect" icon on the zoot desktop. Alternatively, you can open the firefox web browser and go to 192.168.3.1/vpn_sta.htm
+  * The browser will prompt you for the admin user name and password. If these entries are not already filled in, then look for this information on the papers near the console.
+  * If the browser does not open, then check if there are other instances of firefox already running. To do this, open a terminal window, type "ps auxw | grep firefox", and kill the other instances of firefox so that you can open a new window.
+  * When the VPN connection is working, it will report "Phase 1: M-ESTABLISHED / Phase 2: ESTABLISHED" under the state column.
+  * If either Phase 1 or Phase 2 states say IDLE for a given VPN, then you need to re-establish the connection. To do this, click on the "DROP" button for that VPN. Then click on the "CONNECT" button and wait for the Phase 1 and Phase 2 connections to be established.
+  * Make sure to close Firefox by using CTRL-Q to quit the program and not just close the window.
+===== Network Problems =====
+==== User accounts not recognized ====
+The gps computer does the user authentication for the control side while ctrscrut provides the home directories. Yellowpages is gone, the new paradigm is LDAP (local directory access protocol). If you can't log on to computers on the control network, then make sure both ctscrut (michelson) and gps computers are running. If the login screen screen on ctrscrut says "Ubuntu Administrator" and has no user accounts, then check to make sure gps computer is on. If you restart gps, then you might have to reboot ctrscrut to get the user accounts. If ctrscrut was rebooted, you might have to reboot other control network computers if you can't log on.
+If gps computer does not start, check the power distribution unit (PDU) at the top of that rack. If any units show both " " and "-" then you can use the arrow buttons to move through the units and cycle the units to on " ". That should automatically start the computer connected to those units.
+===== General Problems =====
+==== GUIs are frozen ====
+Check to see if Sockman is working. Click the [LIST] button on sockman. If the list doesn't come up, Sockman may be hung up. Follow the Sockman restart procedure in the text file on the desktop if it won't respond.
+Hit [REOPEN] on the gui to see if it reconnects with its server. if that does not fix it, the server may be dead. From the LIST on Sockman, select the server suspected of being frozen. Ping it and if it reports back as being dead, see [[:chara:trouble_shooting#server_is_frozen|Server is frozen]] section below.
+Telescope guis often freeze. Hit reopen on the gui to bring it back to life. Hitting [MOVE] on the telescope gui before the star has stopped moving can cause the gui to freeze. Avoid doing this. Close the dead one and open a new one to fix the problem.
+==== Server display is blank or filled with jibberish ====
+  * If the top of a server goes blank, try typing "sb" (start background) on the server command line.
+  * If the server screen fills with jibberish, try hitting CTRL-L in the server to clear it.
+  * If a server freezes, sometimes hitting CTRL-C and then N, for NO, will unfreeze it.
+==== Server is frozen ====
+Try quitting the server using CTRL-C and entering "Y". If that doesn't work, try the following:
+  * On Sockman, click [LIST] and select the appropriate server. It will give a PID number you can use to kill the server in a terminal. Open a terminal and follow the directions for Restarting Servers above.
+  * If a server window does not close, click the X in the upper right corner to close it, but only after getting the PID from Sockman.
+  * Click [REOPEN] on Cosmic Debris and relevant GUIs to re-initialize communication with the server after it is restarted.
+  * A folder is on the desktop that has the restart commands for CTRSCRUT servers and the Shutters server restart command running on OPLE. Use it to restart servers that will not reopen from the menu.
+  * if a telescope server does not close after using CTRL-C when restarting them after UT midnight and the Send ON button is green on the obsgtk, turn the Send ON to OFF and the server will close. Turn the Send ON button back on to resume the setup for the night.
+==== PAVO Server - Error communicating with IFW ====
+The following error message sometimes appears when starting the PAVO server: "Error communicating with IFW. Could not read from IFW. Is the filter wheel plugged in and on?" Most of the time, restarting the PAVO server will clear this error message and allow PAVO to communicate with the filter wheel. If restarting the server doesn't help, then check that the cables going into the small, black IFW box on the PAVO table and into the back of the PAVO computer are plugged in securely.
+==== Adding or Finding a Star in the CHARA Database ====
+The command "dbadd" can be used to look up the CHARA number for a star or to add a star to the CHARA database. To use dbadd, open a terminal window, and type "dbadd starname" where starname is the common name (e.g., Vega) or identifier of the star (e.g., IRC, HR, HD, SAO, FK5, HIP, GJ, or 2MASS designation). If the object is in the database, then it will return the CHARA number.
+You can also look up different identifiers for the star by using the SIMBAD database: [[http://simbad.u-strasbg.fr/simbad/sim-fbasic|http://simbad.u-strasbg.fr/simbad/sim-fbasic]]
+DBADD uses SIMBAD to look up the coordinates of the star and then searches to see if the star is already in the CHARA database. If the star is in the database, it will return the CHARA number. If the star is not in the CHARA database, it will ask if you want to add it and will assign a CHARA number if you answer yes.
+If an object is not in SIMBAD (such as a recently discovered nova), then you must enter the object manually using the instructions below.
+**Finding a star in the CHARA database**
+Here is an example of how to find the CHARA number of a star, nova, or AGN that is already in the CHARA database:
+[ctrscrut:502] dbadd NGC 4151 \\
+Object "NGC 4151" found as CHARA number: 320263
+Note: If the target information stored in the CHARA database does not match SIMBAD, then dbadd will provide the coordinates and magnitudes listed in SIMBAD, and it will also list the CHARA numbers of objects in the database located within 10 arcsec. Please check these nearby entries before adding a new star to the database.
+**Targets that are not in the CHARA database**
+If an object is not in the CHARA database, then you can use dbadd to query SIMBAD and add the star to the CHARA database. This might need to be done for faint stars, novae, and AGN. If the object is found in SIMBAD, then dbadd will return the target's coordinates, magnitudes, and spectral type and ask if this it the object for which you are looking. If you answer yes, then dbadd will issue a CHARA number and add the object to the database. Please check the target coordinates to make sure that they are correct before adding a new star to the database.
+Here is an example of how to add an object to the CHARA database:
+[ctrscrut:534] dbadd BD 41 3807
+SIMBAD found this for "BD 41 3807":
+ID 2MASS_J20340850 4136592 \\
+CHARA 320414 \\
+.0 \\
+CAT8 2MASS_J20340850 4136592 \\
+RA 20 34 08.5148 \\
+DEC 41 36 59.408 \\
+PMRA -2.32 \\
+PMDEC -3.87 \\
+PAR 0.58 \\
+RVEL -27.50
+VMAG 10.03 \\
+HMAG 6.23 \\
+KMAG 5.99 \\
+SP O5.5Ifc \\
+END
+Is the above the object you are looking for? [y/n] y \\
+Added "BD 41 3807" to the database.
+In the example above, the object "BD 41 3807" has been added to the database as CHARA number 320414.
+**Targets that are not in SIMBAD**
+Some objects like recently discovered novae are not in SIMBAD. Entering dbadd <star designation> for a star not in the SIMBAD database returns the message "Simbad is unable to find an object matching <star designation>. Try using a different catalog designation, or use the "-m" switch to add the object manually."
+The command dbadd -m is used by entering the star name and coordinates in this format:
+Usage: dbadd -m <name> <RA> <Dec> \\  \\
+<name>: Object ID (no spaces) \\  \\
+<RA> : XXhXXmXX.X or XXhXX.X (no spaces) \\  \\
+<Dec> : XXdXXmXX.X or XXdXX.X (no spaces) \\  \\
+There are cases where an object is not in SIMBAD and doesn't return a result in dbadd, but is in fact in the CHARA database. Novae and AGN's are the likely objects that cause this result. At times, objects have multiple entries and several CHARA numbers since the names can be so unique. A system will be developed to find these entries without knowing or having a conventional database designation.
+**Binary stars**
+Some binary stars have a common HD number with an A or B after them. These can cause problems as Cosmic Debris does not accept non numerical entries when filling in star designation. These stars are likely in CHARA's database but need to be searched in dbadd or on SIMBAD to get the CHARA number or another designation.
+When a recognized identifier is entered, the HD number with A or B will usually display. Confirm that the coordinates, magnitudes and spectral type match the star desired. If they do not match, you may have the wrong star or the database may have the wrong info and the baseline solution will be affected. Offsets based on incorrect coordinates or misidentifications can move the fringes many thousands of microns away from the calculated position. This can happen when observing a dim companion (B) using the brighter (A) companion's coordinates. Inform the observers that saving and using the CHARA number will save time the next time the target is observed.
+**Editing the database:**  If you find a mistake in the database, please send an email to Nils to have it corrected. Identify what you believe to be the error and what is the correct information.
+==== Adding an anchor to the wiki page ====
+To add an anchor to the wikipage, type the following where you want the anchor inserted (without the spaces between the symbols): \\
+[ [ #AnchorName ] ]
+Highlight the text you want to be a link to the anchor, click the link symbol above and select anchor. Select a page(such as Trouble Shooting) where the anchor is located and give the same name for the anchor.
+==== Displays for the MIRC-X wolverine2 monitors ====
+Follow instructions in the [[:chara:mircx_monitors|linked page to display the MIRC-X wolverine2 monitors]] in the control room.
+==== No Power for Aperture Wheels ====
+To minimize heat sources in the lab, the power for the apwheels is turned off. If you need to use aperture wheels during the night, the operator will need to plug the power into the outlet next to the metrology table (see photo below). If there are any communication issues after plugging in the power, try restarting the server using bootlaunch on ctrscrut. It's probably a good idea to home the apwheels after turning on the power.
+{{:chara:d859af0efb2dab690d3a44526d7b8afc.png}}
+==== Restarting the STST Computer ====
+{{:chara:ccd9641c95c5221f810129e671f441f0.png}}
  \\
-Last updated 2023-11-20 by Norm Vargas END HERE
+Last updated 2024-07-22 END HERE

The CHARA Array Wiki

User Tools

Site Tools

Differences

Page Tools