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 [2018/09/25 15:20] gail_stargazer |
chara:trouble_shooting [2022/02/10 13:38] charaobs |
||
---|---|---|---|
Line 2: | Line 2: | ||
\\ | \\ | ||
- | This document describes how to solve common problems that sometimes arise at the array.\\ | + | This document describes how to solve common problems that sometimes arise at the array. |
- | \\ | + | |
===== Can't find fringes ===== | ===== Can't find fringes ===== | ||
This is a list of simple things to check if you can't find fringes: | This is a list of simple things to check if you can't find fringes: | ||
- | * 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. As the VME runs on its own clock and does not use the NTP server, it can drift over the course of the night and cause problems with finding fringes, even if it was synced at the start of the night. Syncing the clocks multiple time during the night may help to avoid this hidden clock problem. | + | * 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. The proper star can be entered 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. The star identifier will be displayed in the server window. If it is not correct, hit STAR ACQUIRED on CD to update OPLE. The proper star can also be entered |
+ | * 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. | ||
* 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? 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 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. Turn off the OL button to send it back to zero. If it does not track on the home switch when displaying a zero position (0.000000), it was lost. Is the E2 cart stuck at 27.97m? | + | * 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 |
* 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 22: | Line 25: | ||
* If LDCs are working correctly, the LDC positions (in mm) should roughly match up with the reference cart positions (in meters). | * If LDCs are working correctly, the LDC positions (in mm) should roughly match up with the reference cart positions (in meters). | ||
- | * Check the instrument alignment. Is flux getting through to the detector? How long has it been since the last NIRO camera alignment? Classic and CLIMB programs can run for about an hour before the light will drift from the central pixel. Use the Classic or CLIMB gui to view the light on the pixels by clicking the PICTURE tab and then the PIXEL AREA button. Turn the camera off after a few seconds to avoid crashing NIRO. Is the right dither power turned on? CLIMB 1 and Classic use different dithers. If Classic or CLIMB fringes are found in a scan, but not when in recording mode, the dither powers are likely not on. Are the camera settings correct for the seeing conditions and flux levels? | + | * Check the instrument alignment. Is flux getting through to the detector? How long has it been since the last NIRO camera alignment? Classic and CLIMB programs can run for about an hour before the light will drift from the central pixel. Use the Classic or CLIMB gui to view the light on the pixels by clicking the PICTURE tab and then the PIXEL AREA button. Turn the camera off 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. | ||
- | ===== Restarting Servers | + | ===== The new OPLE system |
- | ==== Restarting | + | 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, |
- | \\ 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 " | + | The traditional ople server |
- | * bootlaunch_beamsamp – Starts | + | 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 |
- | * bootlaunch_zaber – Starts | + | |
- | \\ telescope bunker computers: \\ | + | 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 ofo 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. |
- | * bootlaunch_hut – Starts | + | ===== Restarting Servers ===== |
- | * bootlaunch_rpc – Starts the RPC_E1, RPC_E2, RPC_S1, RPC_S2, RPC_W1, | + | |
- | * bootlaunch_weather – Starts | + | ==== Restarting Servers using the bootlaunch paradigm ==== |
- | * bootlaunch_lower – Starts | + | |
- | * 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. | + | If a server |
- | \\ Note: The bootlaunch scripts will not start a new server if there is an existing process running. Therefore, type "ps aux | grep // | + | To restart a server, log on to the machine that runs the server and type " |
==== 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 | + | 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** | \\ 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** | ||
- | ===== Telescopes and Dome Servers ===== | + | ==== MIRC-X CredoneImAcq Server |
- | \\ Here we discuss things | + | The MIRC-X CredoneImAcq server and GUI can be opened using the " |
+ | |||
+ | From a terminal window, log on to mircx (old observe password): | ||
+ | |||
+ | 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 | ||
+ | |||
+ | Then restart credone using the desktop icon or by issuing the following command on spooler@mircx: | ||
+ | |||
+ | (the first " | ||
+ | |||
+ | ===== Telescopes and Dome Servers ===== | ||
==== 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 |
- | ==== The Telescope | + | 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 | ||
+ | \\ | ||
+ | 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 14px/ |
- | ==== The Telescope | + | <font 14px/ |
+ | 2.</ | ||
- | \\ Disable | + | <font 14px/ |
- | ==== Dome Server Restart ==== | + | <font 14px/ |
- | \\ 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 " | + | <font 14px/ |
- | ==== Telescope clock is not correct ==== | + | <font 14px/ |
- | | + | ==== The Telescope won't track ==== |
- | ==== 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. |
- | \\ Sometimes it happens that a telescope receives the wrong position for a target | + | ==== The Telescope won't stop moving |
- | * Turn off the power for the telescope (both AZ/EL). | + | Disable |
- | * First shutdown the telescope server | + | |
- | * Then use SOCKMAN | + | |
- | * 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 | + | |
- | * Restart commands for the dome servers are also listed on the desktop in a text file. | + | |
- | \\ | + | ==== Dome Server Restart ==== |
- | ==== Telescope | + | Dome servers are now started using the bootlaunch_master command. The manual process that has been superceded |
- | \\ 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 \\ | | + | To restart |
- | | |Gain|Fn|Gain|Fn|Gain|Fn|Gain|Fn| | | + | 1. Make sure the power to the drives is OFF. Disable the scopes. |
- | |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. \\ | + | 2. Login to the relevant computer as observe. For example, type " |
- | ==== How to Adjust CPUMotor Gains ==== | + | 3. Work out the process ID number (PID) by typing bootlaunch_master |
- | \\ The GAIN controls the gain of the feedback between the encoder and the drive velocity. A high gain means a " | + | 4. Use kill -2 PID to kill the server. Entering |
- | ====== Dome issues ====== | + | 5. Type bootlaunch_master again to restart the server. |
- | \\ At times the domes do not rotate, open or close, or otherwise behave. Some problems are simple and others are more complex. \\ | + | 6. Turn the power to the drives back on. |
- | ==== Dome does not rotate ==== | + | 7. Hit REOPEN and ENABLE on the domegtk, and type " |
- | \\ 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' | + | You may have to reinitialize |
- | ==== Dome does not open ==== | + | Be aware that when restarting a dome server, the telescopes position may not be retained and the dome gui may display Az: 0.0. El: 0.0. The gui will scroll messages that say Az: 0.0. El: 0.0 with an error in scope position. If the scope is known to be at STOW position, you can manually enter the scope' |
- | \\ 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 | + | Also be aware that the gains do not always return |
- | ==== Dome does not close ==== | + | ==== Telescope is not receiving the commanded position for a target. |
- | \\ 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 | + | Sometimes it happens that a telescope receives the wrong position for a target or does not receive |
- | ====== HUT servers ====== | + | ==== Telescope is tracking poorly, overshooting in slew, oscillating. |
- | ==== I can't change | + | This might mean that the gain for the tracking servo is wrong. Note that changing this gain can be dangerous, especially if you set it too high as that can cause the telescope to oscillated and damage the drives. Please only do this if you are very very sure that it is necessary. Symptoms of bad gain are: The scope over shoots the position while slewing. The star will be seen to move out of the window and may come back after a few seconds. This means the slewing gain is too low. The scope oscillates when tracking or after a slew. The star will be tracing an ellipse, figure eight or other looping shape. This means the tracking gain is too low. You can damp this out with the telescope or dome gui by disabling the scope, then re-enabling it. Adjust the gain upward and watch it on the next slew. In all cases if either gain is too high the scope will go into "Fog Horn" mode, which is bad. This can be seen during slews on the twfs or labao as vibrating spots, usually in one axis. |
+ | |||
+ | You always want to use the lowest gain that still allows the scope to work as best as possible. If the tiptilt tells you the scope is oscillating slowly, the gain may be too low. If it is oscillating quickly it may be too high. | ||
+ | |||
+ | The usual values for slewing gains are 4-7 and tracking gains are 7-10. Note that these values may change as the temperatures change rapidly. Gains are usually higher when cold and lower when warm. Be sure to set mode back to AUTO if changing the gains left it in Slewing or Tracking mode. | ||
+ | |||
+ | ==== How to Adjust CPUMotor Gains ==== | ||
- | \\ The HUT servers control functions such as finder and acq exposure times and gains, heater and dehumidifier usage, and various AO functions. An observer may find that the camera settings do not display or are not adjustable. The HUT server may be the cause if it has quit. To see if it is the server, open the HUT gui for the desired telescope from the CHARA menu. If the camera settings are displayed and the settings can be changed from the gui, then the HUT server is ok. Restart the telescope server to reopen the connection to the HUT server and hit reopen on Cosmic Debris as well. If the gui is not functioning, | ||
\\ | \\ | ||
+ | The 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' | ||
- | ===== Tiptilt Server ===== | + | ==== E2 AOB Dichroic Recovery |
- | \\ 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 " | + | {{: |
- | ==== Tiptilt server complains about the CCD ==== | + | ==== E1 Hut and Cooler Communications Recovery |
- | \\ 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, | + | {{: |
- | ==== Tiptilt doesn' | + | ==== S2 Acquisition Server Restart |
- | \\ Sometimes the telescope | + | S2's acquisition |
- | ==== Tiptilt server says the clock isn't running | + | ===== Dome issue ===== |
- | \\ First check whether | + | At times the domes do not rotate, open or close, or otherwise behave. Some problems |
- | ==== Tiptilt is not locking on a star or locks, but lets the star drift away ==== | + | ==== Dome does not rotate |
- | * Are all the mirror covers open? [Note: W1 M7 cover sometimes needs two clicks to open, despite Scope-monitor indicates open.] | + | Sometimes when observing, the dome will not follow |
- | * Has TIPTILT COMM been run from Cosmic Debris? | + | If the dome does not turn at all, even with the manual controls |
- | * 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 | + | |
- | | + | |
- | * Are the TIPTILT buttons turned on from the POWER GUI? | + | |
- | ==== Tiptilt servo oscillates | + | ==== Dome does not open ==== |
- | 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 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 |
- | * Type " | + | 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__ |
- | * Type " | + | |
- | * Read section | + | |
- | ==== Tiptilt is saturating | + | ==== Dome does not close ==== |
- | * Tiptilt saturates at ~ 200,000 counts. | + | 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 |
- | * Set the TT exposure time on Cosmic Debris in the box for " | + | |
- | * To change | + | |
- | * 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 ==== | + | ===== HUT servers ===== |
- | Try using a slower frame rate or increasing the NSUM. Also ensure | + | 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 |
- | ==== Tiptilt counts | + | If the server won't restart, a reboot of the power supply in the telescope bunker might be necessary. The power supply that controls the acquisition and finder cameras as well as their controllers is located on top of the computer rack in each bunker. The power supply has green readouts of volts and current. After turning the power off for 10 seconds and back on, try restarting the server from the computer in the bunker to see if it starts cleanly. If so, then restart the telescope server, reopen the connection to the telescope gui, and hit REOPEN on Cosmic Debris. Part of the HUT server also controls the AO table. If the AOB part of the HUT server doesn' |
- | The bias frame is bad. Get a new one or turn it off. | + | ===== Tiptilt Server. (These sections apply to the old lab tiptilt system retired in April 2021) ===== |
+ | |||
+ | [[: | ||
===== OPLE and Metrology ===== | ===== OPLE and Metrology ===== | ||
Line 208: | Line 223: | ||
* 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 225: | Line 240: | ||
==== 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 | ||
+ | |||
+ | 6. Restart the beam sampler servers (this starts both beam sampler servers BS1 and BS2): | ||
+ | |||
+ | bootlaunch_beamsamp | ||
==== " | ==== " | ||
- | | + | Cosmic Debris reports " |
+ | The beam sample server runs on ctrscrut. The ople server tries to open a connection to the beam sampler when it starts. If the beam sampler is not there, or dies, \\ | ||
+ | you need to restart the ople server as there is no command to reopen that connection. | ||
===== Remote Observing ===== | ===== Remote Observing ===== | ||
Line 248: | Line 291: | ||
==== 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' |
- | 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. | + | |
+ | 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 264: | Line 311: | ||
* 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 ==== | ||
- | 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' |
==== Adding or Finding a Star in the CHARA Database ==== | ==== Adding or Finding a Star in the CHARA Database ==== | ||
- | DBADD is a 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:// |
- | \\ | + | |
- | SIMBAD will show many identifiers for the star, and often will show one of the database identifiers that Cosmic Debris recognizes. | + | |
- | If an object | + | 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. |
- | \\ __Finding | + | 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 | ||
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. | + | 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 a star, nova, or AGN is not in the CHARA database, dbadd will query the SIMBAD database to see if it can be found there. If it returns a result, the target' | + | If an object |
+ | |||
+ | 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 | ||
+ | |||
+ | The command dbadd -m is used by entering the star name and coordinates in this format: | ||
+ | |||
+ | Usage: dbadd -m < | ||
+ | < | ||
+ | <RA> : XXhXXmXX.X or XXhXX.X (no spaces) \\ \\ | ||
+ | <Dec> : XXdXXmXX.X or XXdXX.X (no spaces) \\ \\ | ||
+ | There are cases where an object is not in SIMBAD and doesn' | ||
+ | |||
+ | **Binary stars** | ||
+ | |||
+ | Some binary stars have a common HD number with an A or B after them. These can cause problems as Cosmic Debris does not accept non numerical entries when filling in star designation. These stars are likely in CHARA' | ||
+ | |||
+ | When a recognized identifier is entered, the HD number with A or B will usually display. Confirm that the coordinates, | ||
+ | |||
+ | **Editing | ||
==== 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. \\ \\ Last updated 2017-04-12 | + | 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 2021-01-18 by Norm Vargas | ||