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 [2021/11/05 00:47] charaobs [Tiptilt Server] |
chara:trouble_shooting [2022/01/18 22:47] charaobs |
||
---|---|---|---|
Line 11: | Line 11: | ||
* Did the Astrolib update on OPLE? If the job queue is stopped too soon after slewing on Cosmic Debris, the correct calculations for the carts will not be done by OPLE and you may be searching for fringes with the wrong star data. Hit STAR ACQUIRED on CD to update ople. The proper star can also be entered manually by typing hd #### into the OPLE server and hitting ENTER. | * Did the Astrolib update on OPLE? If the job queue is stopped too soon after slewing on Cosmic Debris, the correct calculations for the carts will not be done by OPLE and you may be searching for fringes with the wrong star data. Hit STAR ACQUIRED on CD to update ople. The proper star can also be entered manually by typing hd #### into the OPLE server and hitting ENTER. | ||
* Are the PoP's correct? After a PoP change, the PoP's are sometimes not updated in CD or ople. | * Are the PoP's correct? After a PoP change, the PoP's are sometimes not updated in CD or ople. | ||
- | * Are the carts behaving or are there vibrations or jumps of 100 or more microns every 3-6 seconds? How are the metrology signals? Are they strong and staying white? Red signals mean one or more metrology signals may have gone too low and homing carts is necessary. | + | * Are the carts behaving or are there vibrations or jumps of 100 or more microns every 3-6 seconds? How are the metrology signals? Are they strong and staying white? Red signals mean one or more metrology signals may have gone too low and homing carts is necessary. The METDATA function on the ople gui can be used to sample the metrology signal and may show noise spikes that can be disruptive to the smooth cart motion. Push the METDATA button on the configure tab and then again about 6 seconds later. Plots will pop up to show the frequency and power of any noise. |
* Is the target a high proper motion star? Red dwarfs are close stars and can have high proper motions. Scan a wider range to see if it is outside of the usual calculated scan range. Binaries can also have very high offsets from the expected position due to mistakenly using astromod calculations from the companion star. | * Is the target a high proper motion star? Red dwarfs are close stars and can have high proper motions. Scan a wider range to see if it is outside of the usual calculated scan range. Binaries can also have very high offsets from the expected position due to mistakenly using astromod calculations from the companion star. | ||
- | * Do you have enough flux from each telescope or on each baseline? | + | * Do you have enough flux from each telescope or on each baseline? Is the telescope tiptilt struggling with low flux? Can the camera gain be raised or the exposure made longer to help hold the star? |
* Did you get the same star in each telescope? Sometimes a busy star field and poor pointing of the telescopes can lead to the wrong star being acquired and locked by tiptilt. View the stars in the finder window to see if all the stars match. | * Did you get the same star in each telescope? Sometimes a busy star field and poor pointing of the telescopes can lead to the wrong star being acquired and locked by tiptilt. View the stars in the finder window to see if all the stars match. | ||
* Check the CHARA time on the GPS server. The " | * Check the CHARA time on the GPS server. The " | ||
Line 26: | Line 26: | ||
* 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 with the STOP button. 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 with the STOP button. 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 ===== | ||
Line 39: | Line 38: | ||
* bootlaunch_zaber – Starts the ZABER_2 server. | * bootlaunch_zaber – Starts the ZABER_2 server. | ||
- | \\ telescope bunker computers: | + | \\ telescope bunker computers |
* bootlaunch_hut – Starts the E1_HUT, E2_HUT, S1_HUT, S2_HUT, W1_HUT, or W2_HUT server, depending on the machine it's launched from. | * bootlaunch_hut – Starts the E1_HUT, E2_HUT, S1_HUT, S2_HUT, W1_HUT, or W2_HUT server, depending on the machine it's launched from. | ||
Line 51: | Line 50: | ||
==== 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, 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' | Log on to the relevant computer by typing the computer name (ctrscrut, ople, s1, …). If the shortcut doesn' | ||
- | |||
- | ==== 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** | ||
- | |||
- | ==== 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: | ||
- | |||
- | (the first " | ||
- | |||
- | ===== 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 " | ||
- | \\ | ||
- | Here are the available bootlaunch scripts as of June 2017:\\ | ||
- | \\ | ||
- | gps computer: | ||
- | |||
- | * bootlaunch_beamsamp – Starts the beam sampler servers, BS1 and BS2. | ||
- | * bootlaunch_zaber – Starts the ZABER_2 server. | ||
- | |||
- | \\ telescope bunker computers: | ||
- | |||
- | * bootlaunch_hut – Starts the E1_HUT, E2_HUT, S1_HUT, S2_HUT, W1_HUT, or W2_HUT server, depending on the machine it's launched from. | ||
- | * bootlaunch_rpc – Starts the RPC_E1, RPC_E2, RPC_S1, RPC_S2, RPC_W1, or RPC_W2 server, depending on the machine it's launched from. | ||
- | * bootlaunch_weather – Starts the E1_WEATHER, E2_WEATHER, S1_WEATHER, S2_WEATHER, W1_WEATHER, or W2_WEATHER server, depending on the machine it's launched from. | ||
- | * bootlaunch_lower – Starts the E1_Lower, E2_Lower, S1_Lower, S2_Lower, W1_Lower, or W2_Lower cylinder 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 // | ||
- | |||
- | ==== 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 ([[: | ||
- | \\ | ||
- | Log on to the relevant computer by typing the computer name (ctrscrut, ople, s1, …). If the shortcut doesn' | ||
==== Shutters Server ==== | ==== Shutters Server ==== | ||
Line 128: | Line 74: | ||
===== Telescopes and Dome Servers ===== | ===== Telescopes and Dome Servers ===== | ||
- | | + | 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 ==== | ||
- | < | ||
- | \\ | + | 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. |
- | </code> | + | 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** |
+ | \\ | ||
+ | 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 causing the stall and not that the scope is actually in a wrong position.</ | ||
+ | 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 16px/ | ||
- | <font 16px/ | + | <font 14px/ |
- | + | 2.</ | |
- | <font 14px/ | + | |
<font 14px/ | <font 14px/ | ||
Line 147: | Line 97: | ||
<font 14px/ | <font 14px/ | ||
- | <font 14px/ | + | <font 14px/ |
==== The Telescope won't track ==== | ==== 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. | 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 ==== | ==== 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. | 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. | ||
==== Dome Server Restart ==== | ==== Dome Server Restart ==== | ||
- | + | Dome servers are now started using the bootlaunch_master command. Kill the server by finding | |
- | To manually start the dome server: | + | |
- | 1. Make sure the power to the drives is OFF. | + | |
- | 2. Login to the relevant computer as root. For example, type " | + | |
- | 3. Work out the process ID number (PID), either | + | |
- | (s1:1001) tsockman get dome_S1 | + | |
- | Name : dome_S1 | + | |
- | Machine : s1.chara-array.org | + | |
- | PID : 29953 | + | |
- | Commands : -1 | + | |
- | Data : -1 | + | |
- | Message : 4002 | + | |
- | Restart : / | + | |
- | or with | + | |
- | (s1:1003) ps aux | grep dome | + | |
- | theo 4473 0.0 0.0 61188 748 pts/3 S 10:45 0:00 grep dome | + | |
- | observe 29953 18.5 0.4 35596 9860 ? Sl Apr21 416:11 / | + | |
- | It can also be found by pulling up the LIST on SOCKMAN and selecting the relevant dome. | + | |
- | So in this case the PID is 29953. | + | |
- | 4. Try and stop the server gracefully: kill -2 29953 | + | |
- | 5. You should then check that the server has indeed stopped: | + | |
- | [s1:600] tsockman get dome_S1 | + | |
- | Name : dome_S1 | + | |
- | Machine : s1.chara-array.org | + | |
- | PID : 15635 | + | |
- | Commands : -1 | + | |
- | Data : -1 | + | |
- | Message : 2008 | + | |
- | Restart : / | + | |
- | If the socket manager still thinks it's running you will need to stop it forcefully: kill -9 29953; tsockman rm dome_S1 | + | |
- | 6. Restart the dome server by copying the command at the end of the / | + | |
- | [s1:602] more / | + | |
- | <<< | + | |
- | #Run the dome server | + | |
- | / | + | |
- | / | + | |
- | (Note: the part of the command that saves information to / | + | |
- | 7. Turn the power to the drives back on. | + | |
- | 8. 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 scopes position. | + | |
- | ==== Telescope clock is not correct ==== | + | To manually start the dome server: |
- | + | 1. Make sure the power to the drives is OFF. | |
- | The NTP server has obsoleted this problem and fix as of 2014. | + | |
- | ==== Telescope is not receiving | + | 2. Login to the relevant computer as root. For example, type " |
- | + | 3. Work out the process ID number | |
- | 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 | + | |
- | * DISABLE the telescope using either the telescope or dome GUI. | + | |
- | * Turn off the power for the telescope | + | (s1:1001) tsockman get dome_S1 \\ |
- | * First shutdown the telescope server | + | Name : dome_S1 \\ |
- | * Then use SOCKMAN to select the appropriate dome server from the list (dome_E1, etc) Get the PID number for reference. | + | Machine : s1.chara-array.org \\ |
- | * The dome server will need to be restarted from the command line in a terminal. | + | PID : 29953 \\ |
- | * Open a terminal window and log on to the telescope computer by typing " | + | Commands : -1 \\ |
- | * Look for instruction in the /etc/rc.local file by typing " | + | Data : -1 \\ |
- | * Locate instruction listed under "#Run the dome server" | + | Message : 4002 \\ |
- | * / | + | Restart : /usr/local/bin/dome_server -A33.7441 S1 \\ \\ |
- | * / | + | or with \\ |
- | * (Replace S1 with commands for appropriate telescope) | + | (s1:1003) ps aux | grep dome \\ |
- | * After the dome server is running, re-open the telescope server | + | theo 4473 0.0 0.0 61188 748 pts/3 S+ 10:45 0:00 grep dome \\ |
- | * ENABLE | + | observe 29953 18.5 0.4 35596 9860 ? Sl Apr21 416: |
- | * Restart commands for the dome servers are also listed on the desktop in a text file. | + | It can also be found by pulling up the LIST on SOCKMAN |
- | < | + | So in this case the PID is 29953. \\ \\ |
+ | 4. Try and stop the server | ||
- | \ | + | 5. You should then check that the server has indeed stopped: \\ \\ |
- | ==== Telescope is tracking poorly, overshooting in slew, oscillating. ==== | + | [s1:600] tsockman get dome_S1 \\ |
+ | Name : dome_S1 \\ | ||
+ | Machine : s1.chara-array.org \\ | ||
+ | PID : 15635 \\ | ||
+ | Commands : -1 \\ | ||
+ | Data : -1 \\ | ||
+ | Message : 2008 \\ | ||
+ | Restart : / | ||
+ | If the socket manager still thinks it's running you will need to stop it forcefully: kill -9 29953; tsockman rm dome_S1 | ||
- | </code> | + | 6. Restart the dome server by copying the command at the end of the /etc/ |
- | <code> | + | [s1:602] more / |
- | 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 | + | <<< Press space bar or enter to scroll through file>>> \\ \\ |
+ | #Run the dome server \\ \\ | ||
+ | / | ||
+ | / | ||
+ | (Note: the part of the command | ||
- | </ | + | 7. Turn the power to the drives back on. |
- | | |Gain|Fn|Gain|Fn|Gain|Fn|Gain|Fn| | | + | 8. Hit REOPEN and ENABLE |
- | |S1|7|4|4|3|16|4|10|7|10-26-2017| | + | |
- | |S2|7| |7| |10| |10| |10-22-2016| | + | |
- | |E1|7| |7| |13| |10| |10-22-2016| | + | |
- | |E2|7| |7| |13| |10| |10-22-2016| | + | |
- | |W1|13| |10| |13| |10| |10-22-2016| | + | |
- | |W2|7| |7| |13| |13| |10-22-2016| | + | |
- | + | ||
- | \\ | + | |
- | 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 ==== | + | |
- | + | ||
- | \\ | + | |
- | 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' | + | |
- | + | ||
- | ==== E2 AOB Dichroic Recovery ==== | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | ==== E1 Hut and Cooler Communications Recovery ==== | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | S2's acquisition server resides on " | + | |
- | + | ||
- | ====== 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. This can happen if there was work done at the dome during the day. If the dome opens, but does not turn, check to see that control of the dome rotation is in the computer position and not manual on the dome rotation controller box just inside the door of the bunker. | + | |
- | + | ||
- | ==== Dome does not open ==== | + | |
- | + | ||
- | \\ | + | |
- | Is the SPYCAM on and updating? | + | |
- | 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 ==== | + | |
- | + | ||
- | \\ | + | |
- | 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. | + | |
- | + | ||
- | ==== 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. | + | |
- | + | ||
- | ===== Tiptilt Server. (These sections apply to the old lab tiptilt system retired in April 2021) ===== | + | |
- | + | ||
- | < | + | |
- | | + | |
- | + | ||
- | </ | + | |
- | + | ||
- | + | ||
- | ==== Tiptilt server complains about the CCD ==== | + | |
- | + | ||
- | < | + | |
- | | + | |
- | + | ||
- | </ | + | |
- | + | ||
- | ==== Tiptilt doesn' | + | |
- | + | ||
- | < | + | |
- | | + | |
- | + | ||
- | </ | + | |
- | + | ||
- | ==== Tiptilt server says the clock isn't running ==== | + | |
- | + | ||
- | < | + | |
- | | + | |
- | + | ||
- | </ | + | |
- | + | ||
- | ==== Tiptilt is not locking on a star or locks, but lets the star drift away ==== | + | |
- | + | ||
- | * Are all the mirror covers open? [Note: W1 M7 cover sometimes needs two clicks to open, despite Scope-monitor indicates open.] | + | |
- | * Has TIPTILT COMM been run from Cosmic Debris? | + | |
- | * Check the ACQ alignment to make sure the tick marks are centered on the laser. | + | |
- | * If there is plenty of starlight getting into tiptilt, then try re-initializing by clicking [TIPTILT COMM] on Cosmic Debris. | + | |
- | * If there are a large number of background counts on TT, then close the M5 cover on the telescope, and click [DBIAS] on the TIPLTILT GUI to clear the background counts. Re-open the M5 cover. | + | |
- | * If a star drifts even with TT locked, there could be a bright sky or light from other beams getting into the affected telescope' | + | |
- | * If TT unlocks and the star drifts, the TT servo may not have engaged. This is engaged with the TIPTILT button on the telescope gui. Clicking it may not start the servo the first time. Try it again if the green dots drift on the TT plot windows or if the Servo status in the telescope gui reads None instead of Wobb 1. | + | |
- | * Are the TIPTILT buttons turned on from the POWER GUI? | + | |
- | + | ||
- | ==== Tiptilt servo oscillates ==== | + | |
- | + | ||
- | You will see the oscillation in the green dots of the tiptilt GUI windows. Sometimes you can also see the oscillation in the white starlight dots or as an elongation of the star when looking at the ACQ field while tiptilt is locked. Some scopes have an oscillation that has not yet been diagnosed. W2 is one that usually oscillates. A diagonal motion in the tiptilt box indicates an oscillation in one axis only, while a vertical/ | + | |
- | + | ||
- | * Type " | + | |
- | * Type " | + | |
- | * Read section on adjusting the Telescope Tracking Gain using the Dome Server GUI (ref). | + | |
- | + | ||
- | ==== Tiptilt is saturating ==== | + | |
- | + | ||
- | * Tiptilt saturates at ~ 200,000 counts. If you are near this limit, you can reduce the TT exposure time to lower the number of counts. | + | |
- | * Set the TT exposure time on Cosmic Debris in the box for " | + | |
- | * To change the exposure when already at a target, then click the [EXP] button on the TipTilt GUI. This will bring up a dialog box where you can enter the new exposure time in msec. Check to make sure the tiptilt frequency (in Hz) changes on the tiptilt server after changing the exposure time. If the frame rate doesn' | + | |
- | * Frame rates for given exposure times: | + | |
- | * ExpTime = 5 msec, Frame Rate = 157 Hz | + | |
- | * ExpTime = 2 msec, Frame Rate = 299 Hz | + | |
- | * ExpTime = 1 msec, Frame Rate = 427 Hz | + | |
- | + | ||
- | ==== Tiptilt counts are way too low ==== | + | |
- | + | ||
- | 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 ==== | + | |
- | + | ||
- | The bias frame is bad. Get a new one or turn it off. | + | |
- | + | ||
- | ===== 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. | + | |
- | + | ||
- | ==== 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. | + | |
- | * 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. You can also find the size of the error by typing the command " | + | |
- | + | ||
- | ===== Beam Samplers ===== | + | |
- | + | ||
- | ==== Beam Samplers are not moving ==== | + | |
- | + | ||
- | 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. | + | |
- | + | ||
- | ==== " | + | |
- | < | + | |
- | + | ||
- | | + | |
- | + | ||
- | </ | + | |
- | + | ||
- | ===== 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. | + | |
- | + | ||
- | ===== General Problems ===== | + | |
- | + | ||
- | ==== GUIs are frozen ==== | + | |
- | + | ||
- | Check to see if Sockman is working. Click the [LIST] button on sockman. If the list doesn' | + | |
- | 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. | + | |
- | + | ||
- | ==== 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. | + | |
- | + | ||
- | ==== PAVO Server - Error communicating with IFW ==== | + | |
- | + | ||
- | The following error message sometimes appears when starting the PAVO server: | + | |
- | + | ||
- | ==== 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 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: | + | |
- | + | ||
- | 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__ | + | |
- | + | ||
- | Here is an example of how to add an object to the CHARA database: | + | |
- | + | ||
- | [ctrscrut: | + | |
- | + | ||
- | ID 2MASS_J20340850 4136592 | + | |
- | + | ||
- | 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__ | + | |
- | + | ||
- | When a recognized identifier is entered, the HD number with A or B will usually display. Confirm that the coordinates, | + | |
- | + | ||
- | ==== 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): | + | |
- | + | ||
- | ==== Displays for the MIRC-X wolverine2 monitors ==== | + | |
- | + | ||
- | Follow instructions in the [[: | + | |
- | < | + | |
- | + | ||
- | | + | |
- | + | ||
- | </ | + | |
- | + | ||
- | ==== 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 or in the telescope gui control tab. If a scope disables itself during a slew, it may be just an overcautious stall function. 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. | + | |
- | + | ||
- | </ | + | |
- | + | ||
- | <font 16px/ | + | |
- | + | ||
- | <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 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. | + | |
- | + | ||
- | ==== Dome Server Restart ==== | + | |
- | |||
- | To manually start the dome server: | ||
- | 1. Make sure the power to the drives is OFF. | ||
- | 2. Login to the relevant computer as root. For example, type " | ||
- | 3. Work out the process ID number (PID), either with the command | ||
- | (s1:1001) tsockman get dome_S1 | ||
- | Name : dome_S1 | ||
- | Machine : s1.chara-array.org | ||
- | PID : 29953 | ||
- | Commands : -1 | ||
- | Data : -1 | ||
- | Message : 4002 | ||
- | Restart : / | ||
- | or with | ||
- | (s1:1003) ps aux | grep dome | ||
- | theo 4473 0.0 0.0 61188 748 pts/3 S 10:45 0:00 grep dome | ||
- | observe 29953 18.5 0.4 35596 9860 ? Sl Apr21 416:11 / | ||
- | It can also be found by pulling up the LIST on SOCKMAN and selecting the relevant dome. | ||
- | So in this case the PID is 29953. | ||
- | 4. Try and stop the server gracefully: kill -2 29953 | ||
- | 5. You should then check that the server has indeed stopped: | ||
- | [s1:600] tsockman get dome_S1 | ||
- | Name : dome_S1 | ||
- | Machine : s1.chara-array.org | ||
- | PID : 15635 | ||
- | Commands : -1 | ||
- | Data : -1 | ||
- | Message : 2008 | ||
- | Restart : / | ||
- | If the socket manager still thinks it's running you will need to stop it forcefully: kill -9 29953; tsockman rm dome_S1 | ||
- | 6. Restart the dome server by copying the command at the end of the / | ||
- | [s1:602] more / | ||
- | <<< | ||
- | #Run the dome server | ||
- | / | ||
- | / | ||
- | (Note: the part of the command that saves information to / | ||
- | 7. Turn the power to the drives back on. | ||
- | 8. 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 scopes position. | 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 scopes position. | ||
==== Telescope clock is not correct ==== | ==== Telescope clock is not correct ==== | ||
- | |||
The NTP server has obsoleted this problem and fix as of 2014. | The NTP server has obsoleted this problem and fix as of 2014. | ||
==== Telescope is not receiving the commanded position for a target ==== | ==== 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: * DISABLE the telescope using either the telescope or dome GUI. | |
- | 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: | + | |
- | * DISABLE the telescope using either the telescope or dome GUI. | + | |
* Turn off the power for the telescope (both AZ/EL). | * Turn off the power for the telescope (both AZ/EL). | ||
Line 604: | Line 182: | ||
* ENABLE the telescope using the telescope or dome GUI. Check to see if the command and telescope positions are correct. If they are, then turn on the power for the telescope drives. Re-enter the star information by entering the HD number in the telescope server and click [GO NEXT] to send the telescope to the star. Make sure that the telescope is behaving as expected. The telescope might have drifted a bit, so if you can't find the star, it might be necessary to use the Telrad on a bright star to re-initialize the pointing. | * ENABLE the telescope using the telescope or dome GUI. Check to see if the command and telescope positions are correct. If they are, then turn on the power for the telescope drives. Re-enter the star information by entering the HD number in the telescope server and click [GO NEXT] to send the telescope to the star. Make sure that the telescope is behaving as expected. The telescope might have drifted a bit, so if you can't find the star, it might be necessary to use the Telrad on a bright star to re-initialize the pointing. | ||
* Restart commands for the dome servers are also listed on the desktop in a text file. | * Restart commands for the dome servers are also listed on the desktop in a text file. | ||
- | < | ||
- | \ | + | ==== Telescope is tracking poorly, overshooting in slew, oscillating. ==== |
- | ==== 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. 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. On 10-22-2016, the gain settings were: |
- | + | ||
- | < | + | |
- | 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. 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. On 10-22-2016, the gain settings were: | Scope | AZ Slewing | + | |
- | + | ||
- | </ | + | |
+ | |Scope|AZ Slewing| |AZ 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 655: | Line 227: | ||
==== E1 Hut and Cooler Communications Recovery ==== | ==== E1 Hut and Cooler Communications Recovery ==== | ||
- | {{: | + | {{: |
+ | |||
+ | ==== S2 Acquisition Server Restart | ||
S2's acquisition server resides on " | S2's acquisition server resides on " | ||
- | ====== Dome issue ====== | + | ===== Dome issue ===== |
- | \\ | ||
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' | ||
- | 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. This can happen if there was work done at the dome during the day. If the dome opens, but does not turn, check to see that control of the dome rotation is in the computer position and not manual on the dome rotation controller box just inside the door of the bunker. | + | 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. This can happen if there was work done at the dome during the day. If the dome opens, but does not turn, check to see that control of the dome rotation is in the computer position and not manual on the dome rotation 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. |
==== Dome does not open ==== | ==== 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. |
- | 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__ | 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 ==== | ==== 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 | + | ===== HUT servers ===== |
==== I can't change the camera settings on the TV ==== | ==== I can't change the camera settings on the TV ==== | ||
- | \\ | + | **CHECK THIS SECTION |
- | 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 ===== | + | 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. |
- | \\ | + | The HUT servers control functions such as finder and acq exposure times and gains, heater |
- | 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 | + | |
- | Note that there are background counts | + | |
- | In the tiptilt GUI windows, the white dots represent | + | |
- | ==== Tiptilt | + | If the server |
- | \\ | + | ===== Tiptilt Server. (These sections apply to the old lab tiptilt |
- | Is the CCD turned on? When the tiptilt server starts up it tries no more than five times to communicate with the CCD. If they all fail, it will give up. If this happens, try cycling the power to the CCD and try again. If this fails, connect to the tiptilt machine and type the command rtccdAPIDemo, | + | |
- | Note that it is never a good idea to reboot machines unless you are very very sure it is necessary. The only reason to reboot tiptilt, other than a lock up of some kind, is that the clock interrupt has failed. You can test this by running the command " | + | |
- | Also note that cycling the power on the CCD can cause harm so be sure you need to do it before trying it. Also, it is important to wait for at least 20 seconds after turning off the power before turning it on again. | + | |
- | + | ||
- | ==== Tiptilt doesn' | + | |
- | + | ||
- | \\ | + | |
- | Sometimes the telescope server will not show that TT is running. It will show 0Hz for a signal rate for TT. Running TIPTILT COMM will not get it started while other scopes do show it starting. Close and restart any telescope servers that won't connect after two tries of TIPTILT COMM. \\ | + | |
- | Note: There is more info in the software manual on this topic, but I wasn't sure if it was still relevant. | + | |
- | + | ||
- | ==== Tiptilt | + | |
- | + | ||
- | \\ | + | |
- | First check whether the clock itself is running and the other machines receive the clock signal. Look at the clock cards at the back of other computers in the rack. The clock cards have three LEDs, one yellow and two greens. If the computer is receiving the clock signal properly all three LEDs should blink, but at a different rate. If the LEDs on all the clock cards are solid then reboot the GPS computer. When the GPS computer is down, it is best to cycle the power also on the box right above the GPS computer. \\ \\ | + | |
- | If the clock appears to be working properly on other machines and not on the tiptilt now it is time to reboot tiptilt. \\ \\ | + | |
- | [There is a bug in the real time part of the CCD code. It is caused by the clock in the tiptilt system either not running at all or having been set to a time very different from the last time the CCD ran.] \\ \\ | + | |
- | For the time being the only solution is to reboot tiptilt, but do so from the lab. Power OFF the CCD, then reboot the tiptilt machine and go into the BIOS. Make sure that interrupt 11 has been set to ISA legacy, save the BIOS and reboot. When the clock card LEDs in the tiptilt machine indicate proper clock signal, turn the CCD back on and start the tiptilt server. \\ \\ | + | |
- | Also, sometimes Serial Port 3 grabs IRQ 11 which stops the clock from running. Since there is no serial port 2 it's safe to disable this in the BIOS. This problem normally comes up when there has been a power outage. \\ \\ | + | |
- | Sometimes syncing the clock can also cause this problem, but that should be fixed soon. If it does, exit the tiptilt server, log in as root, and reload the tiptilt model using the following commands: \\ | + | |
- | /sbin/rmmod tiptilt_rt \\ | + | |
- | / | + | |
- | Note that it is never a good idea to reboot machines unless you are very very sure it is necessary. The only reason to reboot tiptilt, other than a lock up of some kind, is that the clock interrupt has failed. You can test this by running the command " | + | |
- | + | ||
- | ==== Tiptilt is not locking on a star or locks, but lets the star drift away ==== | + | |
- | + | ||
- | * Are all the mirror covers open? [Note: W1 M7 cover sometimes needs two clicks to open, despite Scope-monitor indicates open.] | + | |
- | * Has TIPTILT COMM been run from Cosmic Debris? | + | |
- | * Check the ACQ alignment to make sure the tick marks are centered on the laser. | + | |
- | * If there is plenty of starlight getting into tiptilt, then try re-initializing by clicking [TIPTILT COMM] on Cosmic Debris. | + | |
- | * If there are a large number of background counts on TT, then close the M5 cover on the telescope, and click [DBIAS] on the TIPLTILT GUI to clear the background counts. Re-open the M5 cover. | + | |
- | * If a star drifts even with TT locked, there could be a bright sky or light from other beams getting into the affected telescope' | + | |
- | * If TT unlocks and the star drifts, the TT servo may not have engaged. This is engaged with the TIPTILT button on the telescope gui. Clicking it may not start the servo the first time. Try it again if the green dots drift on the TT plot windows or if the Servo status in the telescope gui reads None instead of Wobb 1. | + | |
- | * Are the TIPTILT buttons turned on from the POWER GUI? | + | |
- | + | ||
- | ==== Tiptilt servo oscillates ==== | + | |
- | + | ||
- | You will see the oscillation in the green dots of the tiptilt GUI windows. Sometimes you can also see the oscillation in the white starlight dots or as an elongation of the star when looking at the ACQ field while tiptilt is locked. Some scopes have an oscillation that has not yet been diagnosed. W2 is one that usually oscillates. A diagonal motion in the tiptilt box indicates an oscillation in one axis only, while a vertical/ | + | |
- | + | ||
- | * Type " | + | |
- | * Type " | + | |
- | * Read section on adjusting the Telescope Tracking Gain using the Dome Server | + | |
- | + | ||
- | ==== Tiptilt is saturating ==== | + | |
- | + | ||
- | * Tiptilt saturates at ~ 200,000 counts. If you are near this limit, you can reduce the TT exposure time to lower the number of counts. | + | |
- | * Set the TT exposure time on Cosmic Debris in the box for " | + | |
- | * To change the exposure when already at a target, then click the [EXP] button on the TipTilt GUI. This will bring up a dialog box where you can enter the new exposure time in msec. Check to make sure the tiptilt | + | |
- | * Frame rates for given exposure times: | + | |
- | * ExpTime | + | |
- | * ExpTime = 2 msec, Frame Rate = 299 Hz | + | |
- | * ExpTime = 1 msec, Frame Rate = 427 Hz | + | |
- | + | ||
- | ==== Tiptilt counts are way too low ==== | + | |
- | + | ||
- | 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 | + | |
- | The bias frame is bad. Get a new one or turn it off. | + | [[: |
===== OPLE and Metrology ===== | ===== OPLE and Metrology ===== | ||
Line 776: | Line 285: | ||
* 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. | + | * 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. |
===== Beam Samplers ===== | ===== Beam Samplers ===== | ||
Line 793: | Line 302: | ||
==== Restarting the Beam Sampler Server ==== | ==== 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. | + | 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 \\ \\ | + | |
- | 5. Restart the beam sampler servers (this starts both beam sampler servers BS1 and BS2): \\ \\ | + | |
- | bootlaunch_beamsamp | + | |
- | ==== " | + | 1. Make sure you are logged into the right machine: ssh ctrscrut |
- | \\ | + | 2. If you are not sure see if the socket manager |
- | 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 ===== | + | 3. See if there are any ghosts running |
- | ==== VPN connection is not working ==== | + | ps aux | grep esp_server |
- | To re-establish the VPN connection, follow these steps: | + | 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 |
- | * Open VPN status page from the firefox web broswer. To do this, click on the "AROC VPN reconnect" | + | tsockman |
- | * 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. | + | |
- | ===== General Problems ===== | + | 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. |
- | ==== GUIs are frozen ==== | + | 4. Stop those processes: |
- | Check to see if Sockman is working. Click the [LIST] button on sockman. If the list doesn' | + | kill -9 PID1 PID2 …. |
- | 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 | + | 5. Make sure there is no sign of it in the socket manager |
- | * If the top of a server goes blank, try typing " | + | tsockman rm BS |
- | * If the server screen fills with jibberish, try hitting CTRL-l in the server to clear it. | + | |
- | ==== Server is frozen ==== | + | 6. Restart the beam sampler |
- | + | ||
- | 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. | + | |
- | + | ||
- | ==== 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 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' | + | |
- | 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, | + | |
- | 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 [[: | + | |
- | + | ||
- | \\ | + | |
- | Last updated 2017-04-12 | + | |
- | + | ||
- | + | ||
- | ==== 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, | + | |
- | + | ||
- | ===== 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 " | + | |
- | In the tiptilt GUI windows, the white dots represent the starlight while the green dots represent the motion applied to telescope' | + | |
- | + | ||
- | ==== Tiptilt server complains about the CCD ==== | + | |
- | + | ||
- | \\ | + | |
- | Is the CCD turned on? When the tiptilt server starts up it tries no more than five times to communicate with the CCD. If they all fail, it will give up. If this happens, try cycling the power to the CCD and try again. If this fails, connect to the tiptilt machine and type the command rtccdAPIDemo, | + | |
- | Note that it is never a good idea to reboot machines unless you are very very sure it is necessary. The only reason to reboot tiptilt, other than a lock up of some kind, is that the clock interrupt has failed. You can test this by running the command " | + | |
- | Also note that cycling the power on the CCD can cause harm so be sure you need to do it before trying it. Also, it is important to wait for at least 20 seconds after turning off the power before turning it on again. | + | |
- | + | ||
- | ==== Tiptilt doesn' | + | |
- | + | ||
- | \\ | + | |
- | Sometimes the telescope server will not show that TT is running. It will show 0Hz for a signal rate for TT. Running TIPTILT COMM will not get it started while other scopes do show it starting. Close and restart any telescope servers that won't connect after two tries of TIPTILT COMM. \\ | + | |
- | Note: There is more info in the software manual on this topic, but I wasn't sure if it was still relevant. | + | |
- | + | ||
- | ==== Tiptilt server says the clock isn't running ==== | + | |
- | + | ||
- | \\ | + | |
- | First check whether the clock itself is running and the other machines receive the clock signal. Look at the clock cards at the back of other computers in the rack. The clock cards have three LEDs, one yellow and two greens. If the computer is receiving the clock signal properly all three LEDs should blink, but at a different rate. If the LEDs on all the clock cards are solid then reboot the GPS computer. When the GPS computer is down, it is best to cycle the power also on the box right above the GPS computer. \\ \\ | + | |
- | If the clock appears to be working properly on other machines and not on the tiptilt now it is time to reboot tiptilt. \\ \\ | + | |
- | [There is a bug in the real time part of the CCD code. It is caused by the clock in the tiptilt system either not running at all or having been set to a time very different from the last time the CCD ran.] \\ \\ | + | |
- | For the time being the only solution is to reboot tiptilt, but do so from the lab. Power OFF the CCD, then reboot the tiptilt machine and go into the BIOS. Make sure that interrupt 11 has been set to ISA legacy, save the BIOS and reboot. When the clock card LEDs in the tiptilt machine indicate proper clock signal, turn the CCD back on and start the tiptilt server. \\ \\ | + | |
- | Also, sometimes Serial Port 3 grabs IRQ 11 which stops the clock from running. Since there is no serial port 2 it's safe to disable this in the BIOS. This problem normally comes up when there has been a power outage. \\ \\ | + | |
- | Sometimes syncing the clock can also cause this problem, but that should be fixed soon. If it does, exit the tiptilt server, log in as root, and reload the tiptilt model using the following commands: \\ | + | |
- | /sbin/rmmod tiptilt_rt \\ | + | |
- | / | + | |
- | Note that it is never a good idea to reboot machines unless you are very very sure it is necessary. The only reason to reboot tiptilt, other than a lock up of some kind, is that the clock interrupt has failed. You can test this by running the command " | + | |
- | + | ||
- | ==== Tiptilt is not locking on a star or locks, but lets the star drift away ==== | + | |
- | + | ||
- | * Are all the mirror covers open? [Note: W1 M7 cover sometimes needs two clicks to open, despite Scope-monitor indicates open.] | + | |
- | * Has TIPTILT COMM been run from Cosmic Debris? | + | |
- | * Check the ACQ alignment to make sure the tick marks are centered on the laser. | + | |
- | * If there is plenty of starlight getting into tiptilt, then try re-initializing by clicking [TIPTILT COMM] on Cosmic Debris. | + | |
- | * If there are a large number of background counts on TT, then close the M5 cover on the telescope, and click [DBIAS] on the TIPLTILT GUI to clear the background counts. Re-open the M5 cover. | + | |
- | * If a star drifts even with TT locked, there could be a bright sky or light from other beams getting into the affected telescope' | + | |
- | * If TT unlocks and the star drifts, the TT servo may not have engaged. This is engaged with the TIPTILT button on the telescope gui. Clicking it may not start the servo the first time. Try it again if the green dots drift on the TT plot windows or if the Servo status in the telescope gui reads None instead of Wobb 1. | + | |
- | * Are the TIPTILT buttons turned on from the POWER GUI? | + | |
- | + | ||
- | ==== Tiptilt servo oscillates ==== | + | |
- | + | ||
- | You will see the oscillation in the green dots of the tiptilt GUI windows. Sometimes you can also see the oscillation in the white starlight dots or as an elongation of the star when looking at the ACQ field while tiptilt is locked. Some scopes have an oscillation that has not yet been diagnosed. W2 is one that usually oscillates. A diagonal motion in the tiptilt box indicates an oscillation in one axis only, while a vertical/ | + | |
- | + | ||
- | * Type " | + | |
- | * Type " | + | |
- | * Read section on adjusting the Telescope Tracking Gain using the Dome Server GUI (ref). | + | |
- | + | ||
- | ==== Tiptilt is saturating ==== | + | |
- | + | ||
- | * Tiptilt saturates at ~ 200,000 counts. If you are near this limit, you can reduce the TT exposure time to lower the number of counts. | + | |
- | * Set the TT exposure time on Cosmic Debris in the box for " | + | |
- | * To change the exposure when already at a target, then click the [EXP] button on the TipTilt GUI. This will bring up a dialog box where you can enter the new exposure time in msec. Check to make sure the tiptilt frequency (in Hz) changes on the tiptilt server after changing the exposure time. If the frame rate doesn' | + | |
- | * Frame rates for given exposure times: | + | |
- | * ExpTime = 5 msec, Frame Rate = 157 Hz | + | |
- | * ExpTime = 2 msec, Frame Rate = 299 Hz | + | |
- | * ExpTime = 1 msec, Frame Rate = 427 Hz | + | |
- | + | ||
- | ==== Tiptilt counts are way too low ==== | + | |
- | + | ||
- | 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 ==== | + | |
- | + | ||
- | The bias frame is bad. Get a new one or turn it off. | + | |
- | + | ||
- | ===== 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. | + | |
- | + | ||
- | ==== 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. | + | |
- | * 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. You can also find the size of the error by typing the command " | + | |
- | + | ||
- | ===== Beam Samplers ===== | + | |
- | + | ||
- | ==== Beam Samplers are not moving ==== | + | |
- | + | ||
- | This happens most frequently with the E1 beam sampler. If you are doing alignments | + | |
- | + | ||
- | * 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 \\ \\ | ||
- | 5. Restart the beam sampler servers (this starts both beam sampler servers BS1 and BS2): \\ \\ | ||
bootlaunch_beamsamp | bootlaunch_beamsamp | ||
==== " | ==== " | ||
- | \\ | ||
Cosmic Debris reports " | 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, \\ | 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, \\ | ||
Line 1083: | Line 353: | ||
==== 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' |
- | 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 [[: | + | |
+ | 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. | 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. | ||
Line 1103: | Line 375: | ||
==== PAVO Server - Error communicating with IFW ==== | ==== PAVO Server - Error communicating with IFW ==== | ||
- | The following error message sometimes appears when starting the PAVO server: | + | 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' |
- | "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 ==== | ==== Adding or Finding a Star in the CHARA Database ==== | ||
Line 1111: | Line 381: | ||
The command " | The command " | ||
- | You can also look up different identifiers for the star by using the SIMBAD database: [[http:// | + | 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 assign a CHARA number if you answer yes. | 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 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. | 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 | + | **Finding |
Here is an example of how to find the CHARA number of a star, nova, or AGN that is already 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: | ||
Line 1125: | Line 396: | ||
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. | 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 | + | **Targets |
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' | 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: | Here is an example of how to add an object to the CHARA database: | ||
- | [ctrscrut: | + | [ctrscrut: |
SIMBAD found this for "BD 41 3807": | SIMBAD found this for "BD 41 3807": | ||
Line 1142: | Line 415: | ||
PMDEC -3.87 \\ | PMDEC -3.87 \\ | ||
PAR 0.58 \\ | PAR 0.58 \\ | ||
- | RVEL -27.50 | + | RVEL -27.50 |
VMAG 10.03 \\ | VMAG 10.03 \\ | ||
HMAG 6.23 \\ | HMAG 6.23 \\ | ||
Line 1154: | Line 428: | ||
In the example above, the object "BD 41 3807" has been added to the database as CHARA number 320414. | In the example above, the object "BD 41 3807" has been added to the database as CHARA number 320414. | ||
- | \\ __Targets | + | **Targets |
- | 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' | + | |
- | 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, | + | Some objects like recently discovered novae are not in SIMBAD. Entering dbadd <star designation> |
- | 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 ==== | + | The command |
- | + | ||
- | 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 [[: | + | |
- | + | ||
- | \\ | + | |
- | Last updated 2017-04-12 | + | |
- | + | ||
- | + | ||
- | ==== 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 or in the telescope gui control tab. If a scope disables itself during a slew, it may be just an overcautious stall function. 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.\\ | + | |
- | \\ | + | |
- | 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.\\ | + | |
- | \\ | + | |
- | 3. Click the OVERRIDE ON button in domegui MANUAL tab. After this, the hardware doesn' | + | |
- | \\ | + | |
- | 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</ | + | |
- | + | ||
- | <font 16px/ | + | |
- | + | ||
- | <font 14px/ | + | |
- | \\ | + | |
- | <font inherit/ | + | |
- | \\ | + | |
- | <font inherit/ | + | |
- | + | ||
- | <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 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. | + | |
- | + | ||
- | ==== Dome Server Restart ==== | + | |
- | + | ||
- | \\ To manually start the dome server: \\ \\ 1. Make sure the power to the drives is OFF. \\ 2. Login to the relevant computer as root. For example, type " | + | |
- | + | ||
- | ==== Telescope clock is not correct ==== | + | |
- | + | ||
- | \\ The NTP server has obsoleted this problem and fix as of 2014. | + | |
- | + | ||
- | ==== 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: \\ * DISABLE the telescope using either the telescope or dome GUI. | + | |
- | + | ||
- | * Turn off the power for the telescope (both AZ/EL). | + | |
- | * First shutdown the telescope server | + | |
- | * Then use SOCKMAN to select the appropriate dome server from the list (dome_E1, etc) Get the PID number for reference. | + | |
- | * The dome server will need to be restarted from the command line in a terminal. | + | |
- | * Open a terminal window and log on to the telescope computer by typing " | + | |
- | * Look for instruction in the / | + | |
- | * Locate instruction listed under "#Run the dome server" | + | |
- | * / | + | |
- | * / | + | |
- | * (Replace S1 with commands for appropriate telescope) | + | |
- | * After the dome server is running, re-open the telescope server and click [REOPEN} on the dome and telescope GUIs and on Cosmic Debris. | + | |
- | * ENABLE the telescope using the telescope or dome GUI. Check to see if the command and telescope positions are correct. If they are, then turn on the power for the telescope drives. Re-enter the star information by entering the HD number in the telescope server and click [GO NEXT] to send the telescope to the star. Make sure that the telescope is behaving as expected. The telescope might have drifted a bit, so if you can't find the star, it might be necessary to use the Telrad on a bright star to re-initialize the pointing. | + | |
- | * Restart commands for the dome servers are also listed on the desktop in a text file. | + | |
- | < | + | |
- | + | ||
- | \ | + | |
- | ==== 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. 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. On 10-22-2016, the gain settings were: | Scope | AZ Slewing | + | |
- | + | ||
- | </ | + | |
- | + | ||
- | | |Gain|Fn|Gain|Fn|Gain|Fn|Gain|Fn| | | + | |
- | |S1|7|4|4|3|16|4|10|7|10-26-2017| | + | |
- | |S2|7| |7| |10| |10| |10-22-2016| | + | |
- | |E1|7| |7| |13| |10| |10-22-2016| | + | |
- | |E2|7| |7| |13| |10| |10-22-2016| | + | |
- | |W1|13| |10| |13| |10| |10-22-2016| | + | |
- | |W2|7| |7| |13| |13| |10-22-2016| | + | |
- | + | ||
- | \\ 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 ==== | + | |
- | + | ||
- | \\ The GAIN controls the gain of the feedback between the encoder and the drive velocity. A high gain means a " | + | |
- | + | ||
- | ==== E2 AOB Dichroic Recovery ==== | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | ==== E1 Hut and Cooler Communications Recovery ==== | + | |
- | + | ||
- | {{: | + | |
- | \\ | + | |
- | <font 16px/ | + | |
- | + | ||
- | S2's acquisition server resides on " | + | |
- | + | ||
- | ====== 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. This can happen if there was work done at the dome during the day. If the dome opens, but does not turn, check to see that control of the dome rotation is in the computer position and not manual on the dome rotation controller box just inside the door of the bunker. | + | |
- | + | ||
- | ==== 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__ | + | |
- | + | ||
- | ==== 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 ====== | + | |
- | + | ||
- | ==== 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, | + | |
- | + | ||
- | ===== 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 " | + | |
- | In the tiptilt GUI windows, the white dots represent the starlight while the green dots represent the motion applied to telescope' | + | |
- | + | ||
- | ==== Tiptilt server complains about the CCD ==== | + | |
- | + | ||
- | \\ | + | |
- | Is the CCD turned on? When the tiptilt server starts up it tries no more than five times to communicate with the CCD. If they all fail, it will give up. If this happens, try cycling the power to the CCD and try again. If this fails, connect to the tiptilt machine and type the command rtccdAPIDemo, | + | |
- | Note that it is never a good idea to reboot machines unless you are very very sure it is necessary. The only reason to reboot tiptilt, other than a lock up of some kind, is that the clock interrupt has failed. You can test this by running the command " | + | |
- | Also note that cycling the power on the CCD can cause harm so be sure you need to do it before trying it. Also, it is important to wait for at least 20 seconds after turning off the power before turning it on again. | + | |
- | + | ||
- | ==== Tiptilt doesn' | + | |
- | + | ||
- | \\ | + | |
- | Sometimes the telescope server will not show that TT is running. It will show 0Hz for a signal rate for TT. Running TIPTILT COMM will not get it started while other scopes do show it starting. Close and restart any telescope servers that won't connect after two tries of TIPTILT COMM. \\ | + | |
- | Note: There is more info in the software manual on this topic, but I wasn't sure if it was still relevant. | + | |
- | + | ||
- | ==== Tiptilt server says the clock isn't running ==== | + | |
- | + | ||
- | \\ | + | |
- | First check whether the clock itself is running and the other machines receive the clock signal. Look at the clock cards at the back of other computers in the rack. The clock cards have three LEDs, one yellow and two greens. If the computer is receiving the clock signal properly all three LEDs should blink, but at a different rate. If the LEDs on all the clock cards are solid then reboot the GPS computer. When the GPS computer is down, it is best to cycle the power also on the box right above the GPS computer. \\ \\ | + | |
- | If the clock appears to be working properly on other machines and not on the tiptilt now it is time to reboot tiptilt. \\ \\ | + | |
- | [There is a bug in the real time part of the CCD code. It is caused by the clock in the tiptilt system either not running at all or having been set to a time very different from the last time the CCD ran.] \\ \\ | + | |
- | For the time being the only solution is to reboot tiptilt, but do so from the lab. Power OFF the CCD, then reboot the tiptilt machine and go into the BIOS. Make sure that interrupt 11 has been set to ISA legacy, save the BIOS and reboot. When the clock card LEDs in the tiptilt machine indicate proper clock signal, turn the CCD back on and start the tiptilt server. \\ \\ | + | |
- | Also, sometimes Serial Port 3 grabs IRQ 11 which stops the clock from running. Since there is no serial port 2 it's safe to disable this in the BIOS. This problem normally comes up when there has been a power outage. \\ \\ | + | |
- | Sometimes syncing the clock can also cause this problem, but that should be fixed soon. If it does, exit the tiptilt server, log in as root, and reload the tiptilt model using the following commands: \\ | + | |
- | /sbin/rmmod tiptilt_rt \\ | + | |
- | / | + | |
- | Note that it is never a good idea to reboot machines unless you are very very sure it is necessary. The only reason to reboot tiptilt, other than a lock up of some kind, is that the clock interrupt has failed. You can test this by running the command " | + | |
- | + | ||
- | ==== Tiptilt is not locking on a star or locks, but lets the star drift away ==== | + | |
- | + | ||
- | * Are all the mirror covers open? [Note: W1 M7 cover sometimes needs two clicks to open, despite Scope-monitor indicates open.] | + | |
- | * Has TIPTILT COMM been run from Cosmic Debris? | + | |
- | * Check the ACQ alignment to make sure the tick marks are centered on the laser. | + | |
- | * If there is plenty of starlight getting into tiptilt, then try re-initializing by clicking [TIPTILT COMM] on Cosmic Debris. | + | |
- | * If there are a large number of background counts on TT, then close the M5 cover on the telescope, and click [DBIAS] on the TIPLTILT GUI to clear the background counts. Re-open the M5 cover. | + | |
- | * If a star drifts even with TT locked, there could be a bright sky or light from other beams getting into the affected telescope' | + | |
- | * If TT unlocks and the star drifts, the TT servo may not have engaged. This is engaged with the TIPTILT button on the telescope gui. Clicking it may not start the servo the first time. Try it again if the green dots drift on the TT plot windows or if the Servo status in the telescope gui reads None instead of Wobb 1. | + | |
- | * Are the TIPTILT buttons turned on from the POWER GUI? | + | |
- | + | ||
- | ==== Tiptilt servo oscillates ==== | + | |
- | + | ||
- | You will see the oscillation in the green dots of the tiptilt GUI windows. Sometimes you can also see the oscillation in the white starlight dots or as an elongation of the star when looking at the ACQ field while tiptilt is locked. Some scopes have an oscillation that has not yet been diagnosed. W2 is one that usually oscillates. A diagonal motion in the tiptilt box indicates an oscillation in one axis only, while a vertical/ | + | |
- | + | ||
- | * Type " | + | |
- | * Type " | + | |
- | * Read section on adjusting the Telescope Tracking Gain using the Dome Server GUI (ref). | + | |
- | + | ||
- | ==== Tiptilt is saturating ==== | + | |
- | + | ||
- | * Tiptilt saturates at ~ 200,000 counts. If you are near this limit, you can reduce the TT exposure time to lower the number of counts. | + | |
- | * Set the TT exposure time on Cosmic Debris in the box for " | + | |
- | * To change the exposure when already at a target, then click the [EXP] button on the TipTilt GUI. This will bring up a dialog box where you can enter the new exposure time in msec. Check to make sure the tiptilt frequency (in Hz) changes on the tiptilt server after changing the exposure time. If the frame rate doesn' | + | |
- | * Frame rates for given exposure times: | + | |
- | * ExpTime = 5 msec, Frame Rate = 157 Hz | + | |
- | * ExpTime = 2 msec, Frame Rate = 299 Hz | + | |
- | * ExpTime = 1 msec, Frame Rate = 427 Hz | + | |
- | + | ||
- | ==== Tiptilt counts are way too low ==== | + | |
- | + | ||
- | 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 ==== | + | |
- | + | ||
- | The bias frame is bad. Get a new one or turn it off. | + | |
- | + | ||
- | ===== 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. | + | |
- | + | ||
- | ==== 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. | + | |
- | * 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. You can also find the size of the error by typing the command " | + | |
- | + | ||
- | + | ||
- | ===== Beam Samplers ===== | + | |
- | + | ||
- | ==== Beam Samplers are not moving ==== | + | |
- | + | ||
- | 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 \\ \\ | + | |
- | 5. 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. | + | |
- | + | ||
- | ===== 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. | + | |
- | + | ||
- | ==== 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. | + | |
- | + | ||
- | ==== 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 | + | |
- | + | ||
- | 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 < | Usage: dbadd -m < | ||
< | < | ||
<RA> : XXhXXmXX.X or XXhXX.X (no spaces) \\ \\ | <RA> : XXhXXmXX.X or XXhXX.X (no spaces) \\ \\ | ||
<Dec> : XXdXXmXX.X or XXdXX.X (no spaces) \\ \\ | <Dec> : XXdXXmXX.X or XXdXX.X (no spaces) \\ \\ | ||
- | There are cases where an object is not in SIMBAD and doesn' | + | 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' | 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, | + | When a recognized identifier is entered, the HD number with A or B will usually display. Confirm that the coordinates, |
- | 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. | + | |
+ | **Editing | ||
==== 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): \\ | ||
- | [ [ #AnchorName ] ] \\ \\ | + | [ [ #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. | 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. | ||
Line 1561: | Line 460: | ||
\\ | \\ | ||
- | Last updated | + | Last updated |