chara:trouble_shooting
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision Next revision Both sides next revision | ||
|
chara:trouble_shooting [2018/02/21 19:04] 127.0.0.1 external edit |
chara:trouble_shooting [2018/07/05 11:17] jones [Adding an anchor to the wiki page] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Trouble Shooting ====== | ====== Trouble Shooting ====== | ||
| - | \\ Table of Contents\\ \\ [[/ | ||
| - | |||
| - | * [[/ | ||
| - | * [[/ | ||
| - | * [[/ | ||
| - | * [[/ | ||
| - | * [[/ | ||
| - | * [[/ | ||
| - | \\ [[/ | ||
| - | |||
| - | * [[/ | ||
| - | * [[/ | ||
| - | * [[/ | ||
| - | * [[/ | ||
| - | * [[/ | ||
| - | * [[/ | ||
| - | * [[/ | ||
| - | * [[/ | ||
| - | \\ [[/ | ||
| - | |||
| - | * [[/ | ||
| - | \\ [[/ | ||
| - | |||
| - | * [[/ | ||
| - | * [[/ | ||
| - | * [[/ | ||
| - | \\ [[/ | ||
| - | |||
| - | * [[/ | ||
| - | \\ [[/ | ||
| - | |||
| - | * [[/ | ||
| - | * [[/ | ||
| - | * [[/ | ||
| - | * [[/ | ||
| - | * [[/ | ||
| - | * [[/ | ||
| \\ This document describes how to solve common problems that sometimes arise at the array.\\ \\ \\ | \\ This document describes how to solve common problems that sometimes arise at the array.\\ \\ \\ | ||
| - | ===== __Can't find fringes__ | + | =====Can't find fringes===== |
| This is a list of simple things to check if you can't find fringes: | This is a list of simple things to check if you can't find fringes: | ||
| Line 57: | Line 20: | ||
| * Check the instrument alignment. Is flux getting through to the detector? How long has it been since the last NIRO camera alignment? Classic and CLIMB programs can run for about an hour before the light will drift from the central pixel. Use the Classic or CLIMB gui to view the light on the pixels by clicking the PICTURE tab and then the PIXEL AREA button. Turn the camera off after a few seconds to avoid crashing NIRO. Is the right dither power turned on? CLIMB 1 and Classic use different dithers. If Classic or CLIMB fringes are found in a scan, but not when in recording mode, the dither powers are likely not on. Are the camera settings correct for the seeing conditions and flux levels? | * Check the instrument alignment. Is flux getting through to the detector? How long has it been since the last NIRO camera alignment? Classic and CLIMB programs can run for about an hour before the light will drift from the central pixel. Use the Classic or CLIMB gui to view the light on the pixels by clicking the PICTURE tab and then the PIXEL AREA button. Turn the camera off after a few seconds to avoid crashing NIRO. Is the right dither power turned on? CLIMB 1 and Classic use different dithers. If Classic or CLIMB fringes are found in a scan, but not when in recording mode, the dither powers are likely not on. Are the camera settings correct for the seeing conditions and flux levels? | ||
| - | \\ [[/ | ||
| - | ===== __Restarting Servers__ ===== | ||
| \\ | \\ | ||
| - | ==== **Restarting Servers using the bootlaunch paradigm** ==== | + | =====Restarting Servers===== |
| + | \\ | ||
| + | ====Restarting Servers using the bootlaunch paradigm==== | ||
| \\ 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 " | \\ 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 " | ||
| Line 73: | Line 36: | ||
| * bootlaunch_upper -- Starts the E1_Upper, E2_Upper, S1_Upper, S2_Upper, W1_Upper, or W2_Upper server, depending on the machine it's launched from. | * bootlaunch_upper -- Starts the E1_Upper, E2_Upper, S1_Upper, S2_Upper, W1_Upper, or W2_Upper server, depending on the machine it's launched from. | ||
| \\ Note: The bootlaunch scripts will not start a new server if there is an existing process running. Therefore, type "ps aux | grep // | \\ 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** ==== | + | ====Restarting Servers using the rc.local file==== |
| - | \\ This procedure is applicable to servers that have not switched over to 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 ([[/ | + | \\ This procedure is applicable to servers that have not switched over to 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 ([[chara: |
| ==== Shutters Server ==== | ==== 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 ople, not ctrscrut.\\ \\ To start the shutter server on ople:\\ \\ Log into the ople computer and kill the process labeled shutters with the PID as described in **Restarting Servers** above.\\ | + | \\ 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 ople, not ctrscrut.\\ \\ To start the shutter server on ople:\\ \\ Log into the ople computer and kill the process labeled shutters with the PID as described in **Restarting Servers** above.\\ |
| - | ===== __Telescopes | + | =====Telescopes |
| \\ Here we discuss things that can go wrong with the telescopes.\\ \\ | \\ Here we discuss things that can go wrong with the telescopes.\\ \\ | ||
| ==== The Telescope won't move or stopped moving ==== | ==== The Telescope won't move or stopped moving ==== | ||
| Line 110: | Line 73: | ||
| \\ 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.\\ | \\ 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.\\ | ||
| - | | Scope\\ | AZ Slewing\\ | + | | Scope\\ | AZ Slewing\\ || EL Slewing\\ || AZ Tracking\\ || EL Tracking\\ || Date Updated\\ | |
| | \\ | Gain\\ | Fn\\ | Gain\\ | Fn\\ | Gain\\ | Fn\\ | Gain\\ | Fn\\ | \\ | | | \\ | Gain\\ | Fn\\ | Gain\\ | Fn\\ | Gain\\ | Fn\\ | Gain\\ | Fn\\ | \\ | | ||
| | S1\\ | 7\\ | 4\\ | 4\\ | 3\\ | 16\\ | 4\\ | 10\\ | 7\\ | 10-26-2017\\ | | | S1\\ | 7\\ | 4\\ | 4\\ | 3\\ | 16\\ | 4\\ | 10\\ | 7\\ | 10-26-2017\\ | | ||
| Line 120: | Line 83: | ||
| \\ Note that these values may change as the temperatures change rapidly. These are still being adjusted so this is by no means final. Be sure to set mode back to AUTO if changing the gains left it in Slewing or Tracking mode.\\ \\ | \\ Note that these values may change as the temperatures change rapidly. These are still being adjusted so this is by no means final. Be sure to set mode back to AUTO if changing the gains left it in Slewing or Tracking mode.\\ \\ | ||
| ==== How to Adjust CPUMotor Gains ==== | ==== 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 GAIN controls the gain of the feedback between the encoder and the drive velocity. A high gain means a " |
| - | ====== | + | ======Dome issues====== |
| \\ At times the domes do not rotate, open or close, or otherwise behave. Some problems are simple and others are more complex.\\ \\ | \\ 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** ==== | + | ====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' | \\ 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' | ||
| - | ==== **Dome does not open** ==== | + | ====Dome does not 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__ to the dome before disconnecting the power cable. Slide it onto the connector at the box and turn the collar to lock it in place. Turn the power back on and see if you can open the dome from the computer in the bunker.\\ \\ | \\ 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__ to the dome before disconnecting the power cable. Slide it onto the connector at the box and turn the collar to lock it in place. Turn the power back on and see if you can open the dome from the computer in the bunker.\\ \\ | ||
| ==== Dome does not close ==== | ==== 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.\\ \\ \\ | \\ 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====== |
| \\ | \\ | ||
| - | ==== **I can't change the camera settings on the TV** ==== | + | ====I can't change the camera settings on the TV==== |
| - | \\ The HUT servers control functions such as finder and acq exposure times and gains, heater and dehumidifier usage, and various AO functions. An observer may find that the camera settings do not display or are not adjustable. The HUT server may be the cause if it has quit. To see if it is the server, open the HUT gui for the desired telescope from the CHARA menu. If the camera settings are displayed and the settings can be changed from the gui, then the HUT server is ok. Restart the telescope server to reopen the connection to the HUT server and hit reopen on Cosmic Debris as well. If the gui is not functioning, | + | \\ The HUT servers control functions such as finder and acq exposure times and gains, heater and dehumidifier usage, and various AO functions. An observer may find that the camera settings do not display or are not adjustable. The HUT server may be the cause if it has quit. To see if it is the server, open the HUT gui for the desired telescope from the CHARA menu. If the camera settings are displayed and the settings can be changed from the gui, then the HUT server is ok. Restart the telescope server to reopen the connection to the HUT server and hit reopen on Cosmic Debris as well. If the gui is not functioning, |
| ===== Tiptilt Server ===== | ===== Tiptilt Server ===== | ||
| \\ The tiptilt server controls the CCD based tiptilt detection system.\\ \\ Before you start the tiptilt server, you must ensure that the power to the cooling system and the CCD iteslf is on. It is extremely important that the cooler be running before you turn on the CCD and is only turned off if you are sure the CCD is NOT running. You can start the server from the X windows menu or with the command xtiptilt.\\ \\ Note that there are background counts and read noise to deal with. Whenever you change the frame rate, please ensure that the bias frame is OK. The server will attempt to load an old bias frame that should work, but if things are not working, try making a new bias frame by ensuring that the detector is in the dark and typing " | \\ The tiptilt server controls the CCD based tiptilt detection system.\\ \\ Before you start the tiptilt server, you must ensure that the power to the cooling system and the CCD iteslf is on. It is extremely important that the cooler be running before you turn on the CCD and is only turned off if you are sure the CCD is NOT running. You can start the server from the X windows menu or with the command xtiptilt.\\ \\ Note that there are background counts and read noise to deal with. Whenever you change the frame rate, please ensure that the bias frame is OK. The server will attempt to load an old bias frame that should work, but if things are not working, try making a new bias frame by ensuring that the detector is in the dark and typing " | ||
| Line 172: | Line 135: | ||
| Try using a slower frame rate or increasing the NSUM. Also ensure that the acquistion is properly aligned with the laser. To change the frame rate, click the [EXP] button on the tiptilt GUI and enter a longer integration time. Remember to change " | Try using a slower frame rate or increasing the NSUM. Also ensure that the acquistion is properly aligned with the laser. To change the frame rate, click the [EXP] button on the tiptilt GUI and enter a longer integration time. Remember to change " | ||
| ==== Tiptilt counts are negative ==== | ==== Tiptilt counts are negative ==== | ||
| - | The bias frame is bad. Get a new one or turn it off.\\ \\ [[/ | + | The bias frame is bad. Get a new one or turn it off.\\ |
| - | ===== __OPLE | + | =====OPLE and Metrology===== |
| \\ | \\ | ||
| ==== OPLE Server doesn' | ==== OPLE Server doesn' | ||
| Line 185: | Line 148: | ||
| * Type "make install" | * Type "make install" | ||
| * This will install run_ople. Try opening the ople server again. | * This will install run_ople. Try opening the ople server again. | ||
| - | ==== **Metrology and Homing carts** ==== | + | ====Metrology and Homing carts==== |
| * 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. | * 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. | ||
| * 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 homed to 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. Hit the [HOME] button and it should move forward and trigger the home switch. Hit [TRACK] to home it to the new home position. | * 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 homed to 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. Hit the [HOME] button and it should move forward and trigger the home switch. Hit [TRACK] to home it to the new home position. | ||
| - | \\ [[/ | + | =====Beam Samplers===== |
| - | ===== __Beam Samplers__ | + | |
| \\ | \\ | ||
| ==== Beam Samplers are not moving ==== | ==== Beam Samplers are not moving ==== | ||
| Line 205: | Line 167: | ||
| 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' | 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' | ||
| ==== " | ==== " | ||
| - | \\ Cosmic Debris reports " | + | \\ Cosmic Debris reports " |
| - | ===== __Remote Observing__ | + | =====Remote Observing===== |
| \\ | \\ | ||
| ==== VPN connection is not working ==== | ==== VPN connection is not working ==== | ||
| Line 217: | Line 179: | ||
| * 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 " | * 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. | * Make sure to close Firefox by using CTRL-Q to quit the program and not just close the window. | ||
| - | \\ [[/ | + | =====General Problems===== |
| - | ===== __General Problems__ | + | |
| \\ | \\ | ||
| ==== GUIs are frozen ==== | ==== GUIs are frozen ==== | ||
| - | Check to see if Sockman is working. Click the [LIST] button on sockman. If the list doesn' | + | Check to see if Sockman is working. Click the [LIST] button on sockman. If the list doesn' |
| ==== Server display is blank or filled with jibberish ==== | ==== Server display is blank or filled with jibberish ==== | ||
| Line 240: | Line 201: | ||
| DBADD is a command entered in a terminal window that allows you to add a star to the CHARA database or look up a name of a star, nova or AGN to see if it already has a CHARA number. Valid requests can look like dbadd Vega or dbadd HD 123456. Identifiers for a target can be a common name, an IRC, HR, HD, SAO, FK5, HIP, GJ, or 2MASS designation. If a star, AGN or nova is in the database, it will return a CHARA number.\\ \\ __Targets that are not in the CHARA database__\\ \\ If a star, nova or AGN is not in the CHARA database, dbadd will query the SIMBAD database to see if it can be found there. If it returns a result, the target' | DBADD is a command entered in a terminal window that allows you to add a star to the CHARA database or look up a name of a star, nova or AGN to see if it already has a CHARA number. Valid requests can look like dbadd Vega or dbadd HD 123456. Identifiers for a target can be a common name, an IRC, HR, HD, SAO, FK5, HIP, GJ, or 2MASS designation. If a star, AGN or nova is in the database, it will return a CHARA number.\\ \\ __Targets that are not in the CHARA database__\\ \\ If a star, nova or AGN is not in the CHARA database, dbadd will query the SIMBAD database to see if it can be found there. If it returns a result, the target' | ||
| ==== Adding an anchor to the wiki page ==== | ==== 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): | + | To add an anchor to the wikipage, type the following where you want the anchor inserted (without the spaces between the symbols): |
| ==== " | ==== " | ||
| \\ Cosmic Debris reports " | \\ Cosmic Debris reports " | ||
chara/trouble_shooting.txt · Last modified: 2024/06/18 00:21 by charaobs
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
