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/09 14:06] gail_stargazer |
chara:trouble_shooting [2023/02/08 19:30] charaobs [The Telescope won't move or stopped moving] |
||
---|---|---|---|
Line 9: | Line 9: | ||
* Were the clocks synced? Make sure the [SYNC CLOCKS] button on Cosmic Debris has been pushed to start the night. If the OPLE server does not display the correct CHARA time and the errors don't read (0) or (1), the clocks were not synced. | * Were the clocks synced? Make sure the [SYNC CLOCKS] button on Cosmic Debris has been pushed to start the night. If the OPLE server does not display the correct CHARA time and the errors don't read (0) or (1), the clocks were not synced. | ||
- | * 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 | + | * 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. The star identifier will be displayed in the server window. If it is not correct, hit STAR ACQUIRED on CD to update |
- | * 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. Compare the PoP's in the configuration tab of CD or OPLE with the PoP Overview or Popperi gtk. |
* 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. | * 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? Is the telescope tiptilt struggling with low flux? Can the camera gain be raised or the exposure made longer to help hold the star? | + | * 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? Passing clouds or contrails can lower flux unexpectedly. |
* 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 " | ||
* Check the time on the OPLE server. If the time is off or there are any lost ticks/ | * Check the time on the OPLE server. If the time is off or there are any lost ticks/ | ||
* Are the [MAN] buttons pressed (gray) for the moving carts on the OPLE Control gui? (The reference cart will remain green.) | * Are the [MAN] buttons pressed (gray) for the moving carts on the OPLE Control gui? (The reference cart will remain green.) | ||
- | * Check that the carts are within delay line range (-1 to 44 meters) and errors are small. Were the carts homed and checked before the first slew of the night? Did any carts go to the front switch after slewing? This can cause them to lose their position. | + | * Check that the carts are within delay line range (-1.3 to 44.25 meters) and errors are small. Were the carts homed and checked before the first slew of the night? Did any carts go to the front switch after slewing? This can cause them to lose their position. |
* Are the LDC's working? | * Are the LDC's working? | ||
* Is the glass position within allowable range (-10mm to 49mm) on all beams? | * Is the glass position within allowable range (-10mm to 49mm) on all beams? | ||
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? | ||
+ | * There is a script that will display offsets for all scopes against Hour Angle to help find offsets when using MIRCX and MYSTIC. You'll need to log into the MIRCX spooler computer with the command ssh spooler@mircx, | ||
+ | |||
+ | ===== The new OPLE system ===== | ||
+ | |||
+ | With the implementation of the new ople system which replaced the VME in Fall of 2021, new troubleshooting issues have arisen. Since there are now 6 new ople computers to run the carts for each scope individually, | ||
+ | |||
+ | The traditional ople server will still be used to communicate with each new ople computer, identified as OPLE 1 to OPLE 6. When the communications are good, each active cart will be displayed in the ople server or ople gui status tab as before. At times, an ople computer can lose communications or a server can crash and the server or comms needs to be restarted. | ||
+ | |||
+ | If a cart cannot be started, stopped or otherwise commanded, look to the OPLESystem gui to see if a green indicator has turned red. A message will also often pop up on the ople gui saying the command could not be sent. This may require a simple start command to restart the server or a reboot of the computer to get it back to yellow and then a start to get it back to green. Do either of these steps with a right click of the red button and then select start or reboot. After a reboot, select start to load the servers after the indicator has turned yellow. When this is done, the ople server will need to be connected to the newly restarted server. Type " | ||
+ | |||
+ | Some times a cart is stopped and cannot be commanded. If the cart has gone to the front hard or back hard switch, it will not be usable until it is moved from the switch and the Ople Controller box is reset. There are 6 silver boxes for these controllers with two green LED's for the front and back switches and two red LED's for the back hard and front hard switches. If a red LED is lit, there will be an error displayed on the message window and the cart is disabled. The cart will need to be moved off the switch and then the box can be reset with the RESET button on the front. The error display will go away and the red LED will be off. The cart is now controllable. | ||
+ | |||
===== Restarting Servers ===== | ===== Restarting Servers ===== | ||
Line 33: | Line 45: | ||
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 ([[: | 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 " | + | To restart a server, log on to the machine that runs the server and type " |
- | * bootlaunch_beamsamp – Starts | + | ==== Restarting Servers using the rc.local file ==== |
- | * bootlaunch_zaber – Starts the ZABER_2 server. | + | |
- | \\ telescope bunker computers: | + | \\ |
+ | This procedure is applicable to servers that have not switched over to the bootlaunch paradigm, which may not be any at this point.\\ | ||
+ | \\ | ||
+ | If a server is not running or Socket Manager reports that a server is dead, then look at the socket manager list to find out what computer the server runs on ([[: | ||
+ | \\ | ||
+ | Log on to the relevant computer by typing the computer name (ctrscrut, ople, s1, …). If the shortcut doesn' | ||
+ | \\ | ||
+ | Find out if the server is running by typing "ps aux | grep // | ||
+ | [ctrscrut: | ||
+ | observe 9281 0.0 0.0 61156 692 pts/3 S+ 13:58 0:00 grep pico_1\\ | ||
+ | observe 12578 0.0 0.0 24524 11212 ? S Jun16 33:14 / | ||
+ | \\ | ||
+ | If the entry for the dead server shows up in the process list, then identify the process identification number (12578 for the example above) and kill the server by typing "kill -9 // | ||
+ | \\ | ||
+ | Look up the commands to restart the server by typing "more / | ||
+ | \\ | ||
+ | #Start PICO server for PICO #1\\ | ||
+ | /bin/rm -f / | ||
+ | / | ||
+ | / | ||
+ | \\ | ||
+ | The first command removes the lock to allow the server to restart. The second command removes the name from the socket manager listing. The last command restarts the server. Note that if you are restarting the servers as observe, you will need to remove the part of the command in the rc.local file that saves information in / | ||
+ | \\ | ||
+ | There are text files on the desktop with many of the restart commands. Use these files for quick access to the relevant commands. The commands are edited and can be copied exactly as written. Files include Dome servers and all servers running on ctrscrut. Many of these commands are also located on the [[:chara:restarting_servers|Restarting Servers]] page. | ||
- | * 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. | + | Shutters Server |
- | * 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 | + | \\ |
+ | 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 | ||
+ | \\ | ||
+ | Log into the ople computer and kill the process | ||
+ | Turn off the power to the Shutters with the switch on the computer rack which is to the left of the computer desk and marked " | ||
+ | \\ | ||
+ | / | ||
+ | ctrscrut/ | ||
- | ==== 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 | + | ==== Restarting |
- | \\ | + | |
- | Log on to the relevant computer by typing the computer name (ctrscrut, ople, s1, …). If the shortcut doesn' | + | |
- | ==== Shutters Server ==== | + | In very rare circumstances, |
- | \\ 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 | + | Follow these instructions to restart |
+ | |||
+ | ssh -X observe@ctrscrut | ||
+ | |||
+ | killall socket_manager | ||
+ | |||
+ | socket_manager | ||
==== MIRC-X CredoneImAcq Server ==== | ==== MIRC-X CredoneImAcq Server ==== | ||
Line 70: | Line 112: | ||
Then restart credone using the desktop icon or by issuing the following command on spooler@mircx: | Then restart credone using the desktop icon or by issuing the following command on spooler@mircx: | ||
- | ===== Telescopes | + | (the first " |
- | Here we discuss things that can go wrong with the telescopes. | + | ===== Telescopes and Dome Servers ===== |
==== The Telescope won't move or stopped moving ==== | ==== The Telescope won't move or stopped moving ==== | ||
Line 78: | Line 120: | ||
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. | 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. | ||
- | 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** | + | 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.\\ |
\\ | \\ | ||
- | 1. On the domegui MANUAL tab, click STOP so pulses won't be sent to the drive by the control software. | + | **Azimuth Limit Switches** |
\\ | \\ | ||
- | 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 | + | <font 14px/ |
\\ | \\ | ||
- | 3. Click the OVERRIDE ON button in domegui MANUAL tab. After this, the hardware doesn' | + | 1. On the domegui MANUAL tab, click STOP so pulses won' |
\\ | \\ | ||
- | 4. Click ENABLE then you can move the telescope | + | 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.</ |
\\ | \\ | ||
- | 5. After the telescope is back in it normal range, click OVERRIDE OFF which makes the hardware aware of the limits again and then hit AUTO on the AUTO tab to resume normal operation | + | <font 14px/ |
+ | \\ | ||
+ | 4. Click ENABLE then you can move the telescope back to its normal range of operation.\\ | ||
+ | \\ | ||
+ | 5. After the telescope is back in it normal range, click OVERRIDE OFF which makes the hardware aware of the limits again and then hit AUTO on the AUTO tab to resume normal operation.</ | ||
- | <font 14px/ | + | <font 14px/ |
+ | |||
+ | <font 14px/ | ||
+ | \\ | ||
+ | 2.</ | ||
+ | \\ | ||
+ | < | ||
<font 14px/ | <font 14px/ | ||
- | <font 14px/ | + | <font 14px/ |
<font 14px/ | <font 14px/ | ||
- | <font 14px/ | + | <font 14px/ |
==== The Telescope won't track ==== | ==== The Telescope won't track ==== | ||
Line 110: | Line 163: | ||
==== Dome Server Restart ==== | ==== 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 " | + | Dome servers are now started using the bootlaunch_master command. The manual |
- | ==== Telescope clock is not correct ==== | + | To restart the dome server: |
- | The NTP server has obsoleted this problem and fix as of 2014. | + | 1. Make sure the power to the drives is OFF. Disable the scopes. |
- | ==== Telescope is not receiving | + | 2. Login to the relevant computer as observe. For example, type " |
- | 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 | + | 3. Work out the process ID number |
- | * Turn off the power for the telescope (both AZ/EL). | + | 4. Use kill -2 PID to kill the server. Entering |
- | * First shutdown the telescope server | + | |
- | * Then use SOCKMAN | + | 5. Type bootlaunch_master again to restart |
- | * The dome server will need to be restarted from the command line in a terminal. | + | |
- | * Open a terminal window | + | 6. Turn the power to the drives back on. |
- | * Look for instruction | + | |
- | * Locate instruction listed under "#Run the dome server". Copy and paste the commands at the prompt directly on the telescope computer: | + | 7. Hit REOPEN |
- | * / | + | |
- | * / | + | You may have to reinitialize the scope on a bright star. If the powers were turned off quickly when the problem was noticed, the position of the scope should be retained and slewing to a bright star will get it in the finder. If not, you may need to go out to the telescope to find the bright star to reacquire the scope' |
- | * (Replace S1 with commands for appropriate telescope) | + | |
- | * After the dome server | + | Be aware that when restarting a dome server, the telescopes position may not be retained |
- | * ENABLE | + | |
- | * Restart commands for the dome servers are also listed on the desktop in a text file. | + | Also be aware that the gains do not always return to the normal values of Slew 4-7 and Tracking 7-10 when a dome server has crashed and is restarted. They may come up as Gain 22 for all axes and modes and they will need to be turned down or the scopes will oscillate badly. |
+ | |||
+ | ==== Telescope is not receiving the commanded position for a target. ==== | ||
+ | |||
+ | Sometimes it happens that a telescope | ||
==== 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: | Scope | AZ Slewing || EL Slewing || AZ Tracking || EL Tracking || Date Updated | | + | This might mean that the gain for the tracking servo is wrong. Note that changing this gain can be dangerous, especially if you set it too high as that can cause the telescope to oscillated and damage the drives. Please only do this if you are very very sure that it is necessary. Symptoms of bad gain are: The scope over shoots the position while slewing. The star will be seen to move out of the window and may come back after a few seconds. This means the slewing gain is too low. The scope oscillates when tracking or after a slew. The star will be tracing an ellipse, figure eight or other looping shape. This means the tracking gain is too low. You can damp this out with the telescope or dome gui by disabling the scope, then re-enabling it. Adjust the gain upward and watch it on the next slew. In all cases if either gain is too high the scope will go into "Fog Horn" mode, which is bad. This can be seen during slews on the twfs or labao as vibrating spots, usually in one axis. |
- | | |Gain|Fn|Gain|Fn|Gain|Fn|Gain|Fn| | | + | 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. |
- | |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| | + | |
- | \\ | + | The usual values for slewing gains are 4-7 and tracking gains are 7-10. Note that these values may change as the temperatures change rapidly. |
- | Note that these values may change as the temperatures change rapidly. | + | |
==== How to Adjust CPUMotor Gains ==== | ==== How to Adjust CPUMotor Gains ==== | ||
Line 177: | 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. | ||
Line 188: | Line 240: | ||
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. \\ | + | Is the SPYCAM on and updating? An old image may show the dome is closed, but it has actually started to open. If the dome won't open, try hitting the SLIT CLOSE button on the telescope gui first. It may be that there was a computer or server issue and the computer thinks the dome is open already and won't allow it to open again. Hit the SLIT OPEN button to see if it works now. If it still won't open, go to the bunker and look to see if the power switch is on to the dome. It will be up and red if on. |
Also look to see if the power cable is connected to the computer box. If it's connected up high to the manual dome controls, the cable needs to be brought back to the computer box connector. __Turn the power off first__ | 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__ | ||
Line 199: | Line 252: | ||
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 ===== |
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 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. | ||
- | ===== Tiptilt Server. (These sections apply to the old lab tiptilt system retired | + | If the server won't restart, a reboot of the power supply in the telescope bunker might be necessary. The power supply that controls the acquisition and finder cameras as well as their controllers is located on top of the computer rack in each bunker. The power supply has green readouts of volts and current. After turning the power off for 10 seconds and back on, try restarting the server from the computer in the bunker |
- | The tiptilt server controls the CCD based tiptilt detection system. \\ \\ | + | ===== Tiptilt Server. (These sections apply to the old lab tiptilt system |
- | Before you start the tiptilt | + | |
- | 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, | + | ===== LabAO ===== |
- | 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' | + | ==== LabAO Shutters Not Working |
- | Sometimes | + | If the labao shutters are not working, the power button on each of the two red control boxes on the top of the table might need to be pressed. After that the other button needs to be pressed |
- | Note: There is more info in the software manual | + | |
- | ==== Tiptilt server says the clock isn't running | + | ==== LabAO DM Electronics |
- | 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 a labao server |
- | 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 | + | |
- | 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, | + | |
- | * 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 and Metrology ===== | ||
Line 287: | Line 289: | ||
* 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 304: | Line 306: | ||
==== 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. 1. Make sure you are logged into the right machine: ssh ctrscrut 2. If you are not sure see if the socket manager will tell you. If it doesn' | + | The most common cause for getting multiple copies of a server is using the socket manage RESTART button, which is flaky at best. Don't do this. If you need to restart a server you should do it manually. |
+ | |||
+ | 1. Make sure you are logged into the right machine: ssh ctrscrut | ||
+ | |||
+ | 2. If you are not sure see if the socket manager will tell you. If it doesn' | ||
+ | |||
+ | 3. See if there are any ghosts running | ||
+ | |||
+ | ps aux | grep esp_server | ||
+ | |||
+ | Yes, it's hard to know which one it is with the esp servers. You can work out which ones are ghosts by typing the command | ||
+ | |||
+ | tsockman |grep ctrscrut | ||
+ | |||
+ | which will give you a list of the servers running on the machine you are interested in. Checking for non-matching PIDs will tell you which processes you need to stop. | ||
+ | |||
+ | 4. Stop those processes: | ||
+ | |||
+ | kill -9 PID1 PID2 …. | ||
+ | |||
+ | 5. Make sure there is no sign of it in the socket manager | ||
+ | |||
+ | tsockman rm BS | ||
+ | |||
+ | 6. Restart the beam sampler servers (this starts both beam sampler servers BS1 and BS2): | ||
+ | |||
+ | bootlaunch_beamsamp | ||
==== " | ==== " | ||
Line 324: | Line 352: | ||
* If either Phase 1 or Phase 2 states say IDLE for a given VPN, then you need to re-establish the connection. To do this, click on the " | * If either Phase 1 or Phase 2 states say IDLE for a given VPN, then you need to re-establish the connection. To do this, click on the " | ||
* Make sure to close Firefox by using CTRL-Q to quit the program and not just close the window. | * Make sure to close Firefox by using CTRL-Q to quit the program and not just close the window. | ||
+ | |||
+ | ===== Network Problems ===== | ||
+ | |||
+ | ==== User accounts not recognized ==== | ||
+ | |||
+ | The gps computer does the user authentication for the control side while ctrscrut provides the home directories. Yellowpages is gone, the new paradigm is LDAP (local directory access protocol). If you can't log on to computers on the control network, then make sure both ctscrut (michelson) and gps computers are running. If the login screen screen on ctrscrut says " | ||
+ | |||
+ | If gps computer does not start, check the power distribution unit (PDU) at the top of that rack. If any units show both " | ||
===== General Problems ===== | ===== General Problems ===== | ||
Line 329: | Line 365: | ||
==== 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 [[: | ||
+ | |||
+ | 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 ==== | ==== Server display is blank or filled with jibberish ==== | ||
* If the top of a server goes blank, try typing " | * If the top of a server goes blank, try typing " | ||
- | * If the server screen fills with jibberish, try hitting CTRL-l in the server to clear it. | + | * If the server screen fills with jibberish, try hitting CTRL-L in the server to clear it. |
+ | * If a server freezes, sometimes hitting CTRL-C and then N, for NO, will unfreeze | ||
==== Server is frozen ==== | ==== Server is frozen ==== | ||
Line 344: | Line 385: | ||
* Click [REOPEN] on Cosmic Debris and relevant GUIs to re-initialize communication with the server after it is restarted. | * 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. | * A folder is on the desktop that has the restart commands for CTRSCRUT servers and the Shutters server restart command running on OPLE. Use it to restart servers that will not reopen from the menu. | ||
+ | * if a telescope server does not close after using CTRL-C when restarting them after UT midnight and the Send ON button is green on the obsgtk, turn the Send ON to OFF and the server will close. Turn the Send ON button back on to resume the setup for the night. | ||
==== PAVO Server - Error communicating with IFW ==== | ==== PAVO Server - Error communicating with IFW ==== | ||
Line 359: | Line 401: | ||
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 a star in the CHARA database | + | **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: | 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: | + | [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. | 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. | ||
Line 373: | Line 416: | ||
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: |
- | 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 | + | SIMBAD found this for " |
- | Is the above the object you are looking for? [y/n] y Added "BD 41 3807" to the database. | + | 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. | In the example above, the object "BD 41 3807" has been added to the database as CHARA number 320414. | ||
Line 383: | Line 444: | ||
**Targets that are not in SIMBAD** | **Targets that are not in SIMBAD** | ||
- | Some objects like recently discovered novae are not in SIMBAD. Entering dbadd <star designation> | + | Some objects like recently discovered novae are not in SIMBAD. Entering dbadd <star designation> |
- | Usage: | + | The command |
- | + | ||
- | Object ID (no spaces) <RA> : XXhXXmXX.X or XXhXX.X (no spaces) < | + | |
+ | 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' | There are cases where an object is not in SIMBAD and doesn' | ||
Line 401: | Line 464: | ||
==== 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): [ [ #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. | + | 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 ==== | ==== Displays for the MIRC-X wolverine2 monitors ==== | ||
Line 408: | Line 474: | ||
\\ | \\ | ||
- | Last updated | + | Last updated |