This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
chara:trouble_shooting [2023/11/21 00:45] charaobs [Can't find the star] |
chara:trouble_shooting [2024/06/18 00:21] charaobs [S2 Acquisition Server Restart] |
||
---|---|---|---|
Line 42: | Line 42: | ||
* Is the star too low or obstructed by a tree or dome? W1 and S2 have trees nearby that can obscure the star below 40 degrees. Refer to the horizon maps to see if they are the cause. | * Is the star too low or obstructed by a tree or dome? W1 and S2 have trees nearby that can obscure the star below 40 degrees. Refer to the horizon maps to see if they are the cause. | ||
* 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. | * 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 star does not appear in the finder either, such as after a dome server crash and restart, | + | * 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 |
Line 198: | Line 198: | ||
- The gain is temperature dependent, so when the temperature changes these things will change, but more so for tracking. \\ \\ | - 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, | - The tiptilt system almost never causes oscillations, | ||
+ | - 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' | ||
+ | |||
+ | ==== E2 AOB Dichroic Recovery ==== | ||
+ | |||
+ | {{: | ||
+ | |||
+ | ==== E1 Hut and Cooler Communications Recovery ==== | ||
+ | |||
+ | {{: | ||
+ | |||
+ | ==== Acquisition Server Restarts ==== | ||
+ | |||
+ | Most ACQ servers run on the wfs computer at the scope. 2 scopes do not. | ||
+ | |||
+ | S2's acquisition server resides on " | ||
+ | |||
+ | 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 ==== | ||
+ | |||
+ | - 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. | ||
+ | - Note the current M2 actuator positions and send them to Nic for the log. | ||
+ | - Turn off the beacons and lock the star on TWFS tiptilt. | ||
+ | - Turn the servo on in the mercurygtk gui. | ||
+ | - On the align tab of the wfsgtk there is a button for FOCUS SCOPE. | ||
+ | - Press the button. | ||
+ | - When done the focus term of starlight on the TWFS should be zero. | ||
+ | - Turn off the servo on the mercury_gtk gui. | ||
+ | |||
+ | A couple of notes: | ||
+ | |||
+ | * If large moves of M2 are made, tiptilt tracking may be lost. Pay careful attention so that M2 doesn' | ||
+ | * If it takes too long to start the autofocus procedure, the mercury_gtk servo will automatically turn off and nothing will happen. So just make sure the servo is on right before hitting the FOCUS SCOPE button. | ||
+ | |||
+ | ===== Dome issue ===== | ||
+ | |||
+ | At times the domes do not rotate, open or close, or otherwise behave. Some problems are simple and others are more complex. | ||
+ | |||
+ | ==== Dome does not rotate ==== | ||
+ | |||
+ | Sometimes when observing, the dome will not follow the telescope during a slew. This can happen when the Autodome feature is not turned on. Click the ON button on the MAIN tab of the telescope gui to enable it. This may happen after a server restart so always check the dome position with the spycam during a slew after a server restart. Also make sure the target position of the dome matches the telescope' | ||
+ | If the dome does not turn at all, even with the manual controls on the telescope or dome guis, the control may be set to manual on the control box instead of computer. This can happen if there was work done at the dome during the day. If the dome opens, but does not turn, check the controller box just inside the door of the bunker. Sometimes the drive wheel jumps in the track and cannot turn the dome, even when the motor works. This will need to be fixed during the day. A fuse can also blow out in the dome control box and leave the dome stuck. | ||
+ | |||
+ | ==== Dome does not open ==== | ||
+ | |||
+ | Is the SPYCAM on and updating? An old image may show the dome is closed, but it has actually started to open. If the dome won't open, try hitting the SLIT CLOSE button on the telescope gui first. It may be that there was a computer or server issue and the computer thinks the dome is open already and won't allow it to open again. Hit the SLIT OPEN button to see if it works now. If it still won't open, go to the bunker and look to see if the power switch is on to the dome. It will be up and red if on. | ||
+ | |||
+ | Also look to see if the power cable is connected to the computer box. If it's connected up high to the manual dome controls, the cable needs to be brought back to the computer box connector. __Turn the power off first, | ||
+ | |||
+ | ==== Dome does not close ==== | ||
+ | |||
+ | If a dome will not close after observing, it may need to be closed manually at the bunker. Turn the power to the dome off at the switch, disconnect the cable from the computer control box and connect it to the manual control switches above. Turn on the power to the dome after connecting the cable and use the two controls to close the dropout first, then the slit. The dropout must be fully closed and the slit closed over it to be shut properly. Inform the staff that the dome did not function properly so someone can look at it in the morning. | ||
+ | |||
+ | ===== HUT servers ===== | ||
+ | |||
+ | The HUT servers control functions such as beacon and dichroic movements, heater and dehumidifier usage, and various AO functions. An observer may find that the obsgtk is no longer controlling the beacon LED's, beacon flat or dichroic alignments. This happens on occasion with E2 and other scopes. The HUT server may be the cause if it has quit or lost connection or the AOB may be at fault. To see if it is the server, open the HUT gui for the desired telescope from the CHARA menu. If the alignments can be changed from the gui, then the HUT server is ok. You can use the hut gui to continue observing. If the hut gui gives move error messages, cycle the power on the AOB and open a new hut server to restore the connection to the obsgtk. On the POWER gui, turn off the power to the AOB for the offending telescope and turn it back on. Stop the hut server by logging into the appropriate telescope computer and identifying the PID with the bootlaunch_master command and killing the process with the kill -9 #### command. Start the new server via the bootlaunch_master command. Hit REOPEN on the obsgtk to reopen the connection to the HUT server and hit reopen on Cosmic Debris as well. | ||
+ | |||
+ | If the server won't restart, a reboot of the power supply in the telescope bunker might be necessary. The power supply that controls the acquisition and finder cameras as well as their controllers is located on top of the computer rack in each bunker. The power supply has green readouts of volts and current. After turning the power off for 10 seconds and back on, try restarting the server from the computer in the bunker to see if it starts cleanly. If so, then restart the telescope server, reopen the connection to the telescope gui, and hit REOPEN on Cosmic Debris. Part of the HUT server also controls the AO table. If the AOB part of the HUT server doesn' | ||
+ | |||
+ | ===== Tiptilt Server. (These sections apply to the old lab tiptilt system retired in April 2021) ===== | ||
+ | |||
+ | [[: | ||
+ | |||
+ | ===== LabAO ===== | ||
+ | |||
+ | ==== LabAO Shutters Not Working ==== | ||
+ | |||
+ | <font 10.5pt font-family:/ | ||
+ | |||
+ | <font 10.5pt font-family:/ | ||
+ | |||
+ | <font 10.5pt font-family:/ | ||
+ | |||
+ | ==== LabAO DM Electronics ==== | ||
+ | |||
+ | If a labao server complains that it failed to find the EDAC40 device, try unplugging the power and ethernet cables for DM and then replugging in again. The boxes for these are under the respective tables. | ||
+ | |||
+ | ===== OPLE and Metrology ===== | ||
+ | |||
+ | ==== OPLE Server doesn' | ||
+ | |||
+ | This usually happens if someone runs a "make clean" in the cvs tree but doesn' | ||
+ | |||
+ | * Open a terminal window and type " | ||
+ | * Change to the appropriate directory under the CVS tree by typing "cd control/ | ||
+ | * Update the CVS tree by typing "cvs update" | ||
+ | * Run the Makefile script by typing " | ||
+ | * Log on as root by typing " | ||
+ | * Type "make install" | ||
+ | * This will install run_ople. Try opening the ople server again. | ||
+ | |||
+ | ==== Homing carts ==== | ||
+ | |||
+ | * 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/ | ||
+ | * 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 / | ||
+ | * 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' | ||
+ | |||
+ | ==== 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. | ||
+ | |||
+ | 1. Make sure you are logged into the right machine: ssh ctrscrut | ||
+ | |||
+ | 2. If you are not sure see if the socket manager will tell you. If it doesn' | ||
+ | |||
+ | 3. 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. | ||
+ | |||
+ | 4. Stop those processes: | ||
+ | |||
+ | kill -9 PID1 PID2 …. | ||
+ | |||
+ | 5. Make sure there is no sign of it in the socket manager | ||
+ | |||
+ | tsockman rm BS | ||
+ | |||
+ | 6. Restart the beam sampler servers (this starts both beam sampler servers BS1 and BS2): | ||
+ | |||
+ | bootlaunch_beamsamp | ||
+ | |||
+ | ==== " | ||
+ | |||
+ | Cosmic Debris reports " | ||
+ | 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" | ||
+ | * 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", | ||
+ | * When the VPN connection is working, it will report "Phase 1: M-ESTABLISHED / Phase 2: ESTABLISHED" | ||
+ | * 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 " | ||
+ | * 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 " | ||
+ | |||
+ | If gps computer does not start, check the power distribution unit (PDU) at the top of that rack. If any units show both " " and " | ||
+ | |||
+ | ===== General Problems ===== | ||
+ | |||
+ | ==== GUIs are frozen ==== | ||
+ | |||
+ | Check to see if Sockman is working. Click the [LIST] button on sockman. If the list doesn' | ||
+ | |||
+ | 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 [[: | ||
+ | |||
+ | 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 " | ||
+ | * 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 " | ||
+ | |||
+ | * 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' | ||
+ | |||
+ | ==== Adding or Finding a Star in the CHARA Database ==== | ||
+ | |||
+ | The command " | ||
+ | |||
+ | You can also look up different identifiers for the star by using the SIMBAD database: [[http:// | ||
+ | |||
+ | 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: | ||
+ | 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' | ||
+ | |||
+ | Here is an example of how to add an object to the CHARA database: | ||
+ | |||
+ | [ctrscrut: | ||
+ | |||
+ | SIMBAD found this for "BD 41 3807": | ||
+ | |||
+ | ID 2MASS_J20340850 4136592 \\ | ||
+ | CHARA 320414 \\ | ||
+ | 2000.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> | ||
+ | |||
+ | The command dbadd -m is used by entering the star name and coordinates in this format: | ||
+ | |||
+ | Usage: dbadd -m < | ||
+ | < | ||
+ | <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' | ||
+ | |||
+ | **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' | ||
+ | |||
+ | When a recognized identifier is entered, the HD number with A or B will usually display. Confirm that the coordinates, | ||
+ | |||
+ | **Editing the database: | ||
+ | |||
+ | ==== 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 [[: | ||
+ | |||
+ | ===== 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, | ||
+ | |||
+ | 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 " | ||
+ | |||
+ | 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 ===== | ||
+ | |||
+ | ==== Restarting Servers using the bootlaunch paradigm ==== | ||
+ | |||
+ | If a server is not running or Socket Manager reports that a server is dead, then look at the socket manager list to find out what computer the server runs on ([[: | ||
+ | |||
+ | To restart a server, log on to the machine that runs the server and type " | ||
+ | \\ | ||
+ | A number of servers use an interim bootlaunch paradigm to restart. This is confined to servers that run on ubuntu machines, namely the telescope bunker computers and gps. The basic syntax is " | ||
+ | \\ | ||
+ | One thing of note about the output of the bootlaunch scripts, they call a number of other programs which themselves have output that may be misleading in the context of bootlaunch. Chief among these is the output of " | ||
+ | \\ | ||
+ | Note: The bootlaunch scripts will not start a new server if there is an existing process running. Therefore, type "ps aux | grep // | ||
+ | ==== Restarting Servers using the rc.local file (likely outdated) ==== | ||
+ | |||
+ | \\ | ||
+ | This procedure is applicable to servers that have not switched over to the bootlaunch paradigm, which may not be any at this point.\\ | ||
+ | \\ | ||
+ | If a server is not running or Socket Manager reports that a server is dead, then look at the socket manager list to find out what computer the server runs on ([[: | ||
+ | \\ | ||
+ | Log on to the relevant computer by typing the computer name (ctrscrut, ople, s1, …). If the shortcut doesn' | ||
+ | \\ | ||
+ | Find out if the server is running by typing "ps aux | grep // | ||
+ | [ctrscrut: | ||
+ | observe 9281 0.0 0.0 61156 692 pts/3 S 13:58 0:00 grep pico_1\\ | ||
+ | observe 12578 0.0 0.0 24524 11212 ? S Jun16 33:14 / | ||
+ | \\ | ||
+ | If the entry for the dead server shows up in the process list, then identify the process identification number (12578 for the example above) and kill the server by typing "kill -9 // | ||
+ | \\ | ||
+ | Look up the commands to restart the server by typing "more / | ||
+ | \\ | ||
+ | #Start PICO server for PICO #1\\ | ||
+ | /bin/rm -f / | ||
+ | / | ||
+ | / | ||
+ | \\ | ||
+ | The first command removes the lock to allow the server to restart. The second command removes the name from the socket manager listing. The last command restarts the server. Note that if you are restarting the servers as observe, you will need to remove the part of the command in the rc.local file that saves information in / | ||
+ | \\ | ||
+ | There are text files on the desktop with many of the restart commands. Use these files for quick access to the relevant commands. The commands are edited and can be copied exactly as written. Files include Dome servers and all servers running on ctrscrut. Many of these commands are also located on the [[: | ||
+ | |||
+ | Shutters Server | ||
+ | |||
+ | \\ | ||
+ | The Shutters server can become unresponsive or disconnected from the Socket Manager. This server must be restarted from the lab and not from the Control Room. Follow these instructions to restart it. Note that Shutters runs on gps, not ctrscrut.\\ | ||
+ | \\ | ||
+ | To start the shutter server on gps:\\ | ||
+ | \\ | ||
+ | Log into the gps computer and kill the process labeled shutters with the PID as described in **Restarting Servers** above.\\ | ||
+ | Turn off the power to the Shutters with the switch on the computer rack which is marked " | ||
+ | \\ | ||
+ | / | ||
+ | bootlaunch_master | ||
+ | |||
+ | ==== Restarting Socket Manager ==== | ||
+ | |||
+ | In very rare circumstances, | ||
+ | |||
+ | Follow these instructions to restart the socket manager, but only do so if really necessary: | ||
+ | |||
+ | ssh -X observe@ctrscrut | ||
+ | |||
+ | killall socket_manager | ||
+ | |||
+ | socket_manager & | ||
+ | |||
+ | ==== MIRC-X CredoneImAcq Server ==== | ||
+ | |||
+ | The MIRC-X CredoneImAcq server and GUI can be opened using the " | ||
+ | |||
+ | From a terminal window, log on to mircx (old observe password): | ||
+ | ssh -X spooler@mircx | ||
+ | |||
+ | Look up credone process:\\ | ||
+ | ps aux | grep credone | ||
+ | |||
+ | Kill all credone processes (including the ones for the error messages) using "kill -9 PID" where PID is the process number. Note that credone can't be restarted if there are any error processes in the list. Check "ps aux | grep credone" | ||
+ | |||
+ | Then restart credone using the desktop icon or by issuing the following command on spooler@mircx: | ||
+ | credoneImAcq –no-display | ||
+ | |||
+ | (the first " | ||
+ | |||
+ | ===== Telescopes and Dome Servers ===== | ||
+ | |||
+ | ==== The Telescope won't move or stopped moving ==== | ||
+ | |||
+ | 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/ | ||
+ | \\ | ||
+ | 1. On the domegui MANUAL tab, click STOP so pulses won't be sent to the drive by the control software.\\ | ||
+ | \\ | ||
+ | 2. Make sure you understand why the limit was hit which may require a trip to the telescope. If the azimuth positions on all telescope servers and dome guis match, it is likely the limit switch incorrectly causing the stall and not that the scope is actually in a wrong position.</ | ||
+ | \\ | ||
+ | <font 14px/ | ||
+ | \\ | ||
+ | 4. Click ENABLE then you can move the telescope back to its normal range of operation.\\ | ||
+ | \\ | ||
+ | 5. 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 14px/ | ||
+ | |||
+ | <font 14px/ | ||
+ | \\ | ||
+ | 2.</ | ||
+ | \\ | ||
+ | <font 14px/ | ||
+ | |||
+ | <font 14px/ | ||
+ | |||
+ | <font 14px/ | ||
+ | |||
+ | <font 14px/ | ||
+ | |||
+ | <font 14px/ | ||
+ | |||
+ | ==== The Telescope won't track ==== | ||
+ | |||
+ | If a bright star is manually found and not slewed to by number, (usually after the scope has gotten lost), the telescope will not track as it does not know it has gone to a star. When you init the EL and AZ position of the scope to the star's position, you must enable the tracking by going to the dome gui, selecting the RA/DEC tab and hitting the [GO RA/DEC] button. The scope will track, but the pointing model may still be off. Try slewing to the same star and initing on it after it is locked in Tiptilt. This can be done in the dome with the computer at the telescope. | ||
+ | |||
+ | ==== The Telescope won't track ==== | ||
+ | |||
+ | If a bright star is manually found and not slewed to by number, (usually after the scope has gotten lost), the telescope will not track as it does not know it has gone to a star. When you init the EL and AZ position of the scope to the star's position, you must enable the tracking by going to the dome gui, selecting the RA/DEC tab and hitting the [GO RA/DEC] button. The scope will track, but the pointing model may still be off. Try slewing to the same star and initing on it after it is locked in Tiptilt. This can be done in the dome with the computer at the telescope. | ||
+ | |||
+ | ==== The Telescope won't stop moving or moves beyond the commanded position ==== | ||
+ | |||
+ | Disable the scope whenever its motion is outside of what it is supposed to do. Turn the powers off to the axes as well on the Power gui. The dome server is usually to blame and will need to be restarted. | ||
+ | |||
+ | 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. | ||
+ | |||
+ | ==== Dome Server Restart ==== | ||
+ | |||
+ | Dome servers are now started using the bootlaunch_master command. The manual process that has been superceded is archived. | ||
+ | |||
+ | To restart the dome server: | ||
+ | |||
+ | 1. Make sure the power to the drives is OFF. Disable the scopes. | ||
+ | |||
+ | 2. Login to the relevant computer as observe. For example, type " | ||
+ | |||
+ | 3. Work out the process ID number (PID) by typing bootlaunch_master | ||
+ | |||
+ | 4. Use kill -2 PID to kill the server. Entering the command twice will show "No such process" | ||
+ | |||
+ | 5. Type bootlaunch_master again to restart the server. | ||
+ | |||
+ | 6. Turn the power to the drives back on. | ||
+ | |||
+ | 7. Hit REOPEN and ENABLE on the domegtk, and type " | ||
+ | |||
+ | You may have to reinitialize the scope on a bright star. If the powers were turned off quickly when the problem was noticed, the position of the scope should be retained and slewing to a bright star will get it in the finder. If not, you may need to go out to the telescope to find the bright star to reacquire the scope' | ||
+ | |||
+ | Be aware that when restarting a dome server, the telescopes position may not be retained and the dome gui may display Az: 0.0. El: 0.0. The gui will scroll messages that say Az: 0.0. El: 0.0 with an error in scope position. If the scope is known to be at STOW position, you can manually enter the scope' | ||
+ | |||
+ | Also be aware that the gains do not always return to the normal values of Slew 4-7 and Tracking 7-10 when a dome server has crashed and is restarted. They may come up as Gain 22 for all axes and modes and they will need to be turned down or the scopes will oscillate badly. | ||
+ | |||
+ | ==== Telescope is not receiving the commanded position for a target. ==== | ||
+ | |||
+ | Sometimes it happens that a telescope receives the wrong position for a target or does not receive the commanded position at all. The commanded position is listed on the telescope server in the first column under TCS Az/El; the second column lists the actual position of the telescope. Try entering the star designation directly into the telescope server, ie. hd 123456. If it does not accept the number, try closing and restarting the telescope server and hitting repoen on Cosmic Debris and the telescope gui. Try entering the star into the server again. If that does not work, it is possible that something is wrong with the dome server. To restart the dome server follow these steps above. | ||
+ | |||
+ | ==== Telescope is tracking poorly, overshooting in slew, oscillating. ==== | ||
+ | |||
+ | 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. | ||
+ | |||
+ | 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 ==== | ||
+ | |||
+ | \\ | ||
+ | The GAIN controls the gain of the feedback between the encoder and the drive velocity. A high gain means a " | ||
+ | \\ | ||
+ | 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 " | ||
+ | \\ | ||
+ | Slew and tracking mode work differently, | ||
+ | \\ | ||
+ | IN SLEWING MODE\\ | ||
+ | \\ | ||
+ | - If the gain is too low you will overshoot the target.\\ | ||
+ | \\ | ||
+ | - If the gain is too high it will fog-horn.\\ | ||
+ | \\ | ||
+ | - 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' | ||
+ | \\ | ||
+ | IN TRACKING MODE\\ | ||
+ | \\ | ||
+ | - If the gain is too low it will keep moving between slewing and tracking.\\ | ||
+ | \\ | ||
+ | - 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 " | ||
+ | \\ | ||
+ | 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, | ||
+ | \\ | ||
- 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' | - 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' | ||
Line 492: | Line 1003: | ||
\\ | \\ | ||
- | Last updated 2023-02-09 by Norm Vargas END HERE | + | Last updated 2023-11-20 by Norm Vargas END HERE |