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 [2022/12/09 20:29] gail_stargazer |
chara:trouble_shooting [2023/11/21 01:23] charaobs [Can't find the star] |
||
---|---|---|---|
Line 11: | Line 11: | ||
* Did the Astrolib update on OPLE? If the job queue is stopped too soon after slewing on Cosmic Debris, the correct calculations for the carts will not be done by OPLE and you may be searching for fringes with the wrong star data. 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 manually by typing hd #### into the OPLE server and hitting ENTER. | * Did the Astrolib update on OPLE? If the job queue is stopped too soon after slewing on Cosmic Debris, the correct calculations for the carts will not be done by OPLE and you may be searching for fringes with the wrong star data. 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 manually by typing hd #### into the OPLE server and hitting ENTER. | ||
* Are the PoP's correct? After a PoP change, the PoP's are sometimes not updated in CD or ople. Compare the PoP's in the configuration tab of CD or OPLE with the PoP Overview or Popperi gtk. | * 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. | + | * 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. |
- | * 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. Make sure you are on the right star with an image from SIMBAD or Vizier. |
- | * 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. | + | * 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. Remap or realign as needed. |
* 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] or [FT] 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.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. To check the homing of the carts, 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. There is a new "CHECK" | + | * 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. To check the homing of the carts, 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. Use the [CHECK] button on the OPLE gtk to send the carts to the home switch and report whether |
- | * Are the LDC's working? | + | * See section on homing carts in __OPLE and Metrology__ |
- | * Is the glass position within allowable range (-10mm to 49mm) on all beams? | + | * For the visible programs, are the LDC's working? |
+ | * Is the glass position | ||
* Have the commands " | * Have the commands " | ||
- | * Look out for " | + | * Look out for errors on ople server. If the LDC glass goes out of range, the LDC will need to be homed. To home the glass, stop astromod by clicking [STOP] on the OPLE gui. Make sure the LDC velocities are non-zero (~ 50… must click [vel] button to update velocity) and click [HOME] on the LDCs in use. The LDC position number should go to 0.000 or very close to zero. After the LDCs have been homed, turn astromod on by clicking [START] on the ople gui. Then click [REF] on cosmic debris to send the LDCs to the correct positions. |
* 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 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, | * 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, | ||
+ | |||
+ | ===== Can't find the star ===== | ||
+ | |||
+ | Sometimes the star does not appear on the ACQ camera and there are many reasons why this can happen. Here are some of those reasons. | ||
+ | |||
+ | * Did the telescope actually slew? If the powers are off or the scope is disabled, it will not slew. | ||
+ | * Did the telescope disable after slewing? Check the dome gui to see if it says it has disabled. Enable to get it going again. | ||
+ | * Are the M1 and M3 covers open? Check with the Telescope monitor or spycam 2 to see if the covers opened. | ||
+ | * Did the dome rotate with the scope? Check with Spycam 1 to see if it is blocking the telescope. Use Autodome On to get it in line with the telescope. | ||
+ | * Is the ACQ camera showing a live view. Hit ACQ or reopen to see a live view. If the server has quit, bootlaunch on the appropriate computer to restart the ACQ server. Sockman will tell which computer the server runs on. Should be wfs computer at each scope. | ||
+ | * Is the ACQ exposure appropriate for the star magnitude? Turn it up as needed to show the star. | ||
+ | * Has the default flat or last flat been loaded after a slew? A bad DM will distort dim stars and they will not be visible. | ||
+ | * Is the star too low or obstructed by a tree or dome? W1 and S2 have trees nearby that can obscure the star below 40 degrees. Refer to the horizon maps to see if they are the cause. | ||
+ | * E1 does not track past 218 degrees azimuth. The finder camera may be needed to find the star again. It will be off in azimuth, but should still show in the finder. | ||
+ | * If a telescope is lost and star does not appear in the finder either, such as after a dome server crash and restart, a bright star, the moon or Jupiter can be used to get the scope pointing correctly. Anything brighter than Vmag 1 will show on the Spycam 1 view and can be used to get the scope close enough to find it in the finder, then ACQ. It should be placed just below the top bar of the telescope, centered left to right using the telescope paddle. You may have to pan up and down to see it move through the finder view. Use the obsgtk ADJUST tab scope paddle and set a step of 3000 and go up and down after centering it in the SPY 1 view below the top telescope bar. When you get it centered in the finder, manually init the scope to the AZ and EL on the MANUAL tab of the dome gui to one decimal place. Use Stellarium online or any resource to get the current position. You should then be able to slew to a star and center it in the finder, then ACQ and init on the obsgtk to get the scope back to usual. | ||
+ | |||
===== The new OPLE system ===== | ===== The new OPLE system ===== | ||
Line 36: | Line 53: | ||
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 " | 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 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. | + | 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 44: | Line 61: | ||
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 " |
- | ==== Restarting Servers using the rc.local file ==== | + | ==== Restarting Servers using the rc.local file (likely outdated) |
\\ This procedure is applicable to servers that have not switched over to the bootlaunch paradigm, which may not be any at this point. \\ \\ If a server is not running or Socket Manager reports that a server is dead, then look at the socket manager list to find out what computer the server runs on ([[: | \\ 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 ([[: | ||
Line 54: | Line 71: | ||
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 gps, not ctrscrut. \\ \\ To start the shutter server on gps: \\ \\ Log into the gps computer and kill the process labeled shutters with the PID as described in **Restarting Servers** |
==== Restarting Socket Manager ==== | ==== Restarting Socket Manager ==== | ||
Line 86: | Line 103: | ||
==== The Telescope won't move or stopped moving ==== | ==== The Telescope won't move or stopped moving ==== | ||
- | Have the powers been turned on to the drives? Are the scopes disabled? The usual state of the telescopes is disabled until enabled. This is due to the stall function of the scopes which eventually disables the scopes when they are stowed. Enable the scopes by hitting [ENABLE] on the dome gui, the telescope gui control tab, or the bottom of the obsgtk. If a scope disables itself during a slew, it may be just an overcautious stall function or the slew gains may be too high or low. Check the gains and if they are OK, Hit ENABLE and the scope should continue to slew. If it disables again without moving, there may be something wrong at the scope, ie. a hatch left open, a ladder not put away, a tool on the floor, or something else physically impeding the motion of the scope. You will need to go to the dome to see what it is. The computer in the dome will give you control of the scope to turn it away from the problem. | + | Have the powers been turned on to the drives? Are the scopes disabled? The usual state of the telescopes is disabled until enabled. This is due to the stall function of the scopes which eventually disables the scopes when they are stowed. Enable the scopes by hitting [ENABLE] on the dome gui, the telescope gui control tab, or the bottom of the obsgtk. If a scope disables itself during a slew, it may be just an overcautious stall function or the slew gains may be too high or low. Check the gains and if they are OK, Hit ENABLE and the scope should continue to slew. If it disables again without moving, there may be something wrong at the scope, ie. a hatch left open, a ladder not put away, a tool on the floor, or something else physically impeding the motion of the scope. You will need to go to the dome to see what it is. The computer in the dome will give you control of the scope to turn it away from the problem. Make sure the scope is in a position that allows the opening of the hatch if you need to go upstairs. It can be moved back from the bunker as needed. |
Sometimes the dome guis get hung up and can cause erratic motion or no motion of the scopes. Check them for current times and continuous updates of numbers. If they are not updating, try to REOPEN them first. If that does not work, close the gui and open a new one. If a new one does not open, the dome server may be dead or Sockman lost track of it. See **Dome Server Restart** | 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** | ||
Line 92: | Line 109: | ||
1. On the domegui MANUAL tab, click STOP so pulses won't be sent to the drive by the control software. \\ | 1. On the domegui MANUAL tab, click STOP so pulses won't be sent to the drive by the control software. \\ | ||
\\ | \\ | ||
- | 2. Make sure you understand why the limit was hit which may require a trip to the telescope. If the azimuth positions on all telescope servers and dome guis match, it is likely the limit switch causing the stall and not that the scope is actually in a wrong position.</ | + | 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 |
4. Click ENABLE then you can move the telescope back to its normal range of operation. \\ \\ | 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.</ | 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.</ | ||
Line 103: | Line 120: | ||
<font 14px/ | <font 14px/ | ||
- | <font 14px/ | + | <font 14px/ |
<font 14px/ | <font 14px/ | ||
- | <font 14px/ | + | <font 14px/ |
+ | |||
+ | ==== The Telescope won't track ==== | ||
+ | |||
+ | If a bright star is manually found and not slewed to by number, (usually after the scope has gotten lost), the telescope will not track as it does not know it has gone to a star. When you init the EL and AZ position of the scope to the star's position, you must enable the tracking by going to the dome gui, selecting the RA/DEC tab and hitting the [GO RA/DEC] button. The scope will track, but the pointing model may still be off. Try slewing to the same star and initing on it after it is locked in Tiptilt. This can be done in the dome with the computer at the telescope. | ||
==== The Telescope won't track ==== | ==== The Telescope won't track ==== | ||
Line 116: | Line 137: | ||
Disable the scope whenever its motion is outside of what it is supposed to do. Turn the powers off to the axes as well on the Power gui. The dome server is usually to blame and will need to be restarted. | Disable the scope whenever its motion is outside of what it is supposed to do. Turn the powers off to the axes as well on the Power gui. The dome server is usually to blame and will need to be restarted. | ||
+ | |||
+ | Sometimes, the gains can be too low and the scope will overshoot the star position. Disable the scope, adjust the Slewing gain up one increment and enable the scope. It should return to the star. | ||
==== Dome Server Restart ==== | ==== Dome Server Restart ==== | ||
Line 188: | Line 211: | ||
S2's acquisition server resides on " | S2's acquisition server resides on " | ||
+ | |||
+ | ==== Focusing the Telescope ==== | ||
+ | |||
+ | - Fully align beacon to labao and TWFS, especially making sure the focus terms between the two agree very well. | ||
+ | - Open a secondary gui: mergurygtk W2_SECONDARY. | ||
+ | - Note the current M2 actuator positions and send them to Nic for the log. | ||
+ | - Turn off the beacons and lock the star on TWFS tiptilt. | ||
+ | - Turn the servo on in the mercurygtk gui. | ||
+ | - On the align tab of the wfsgtk there is a button for FOCUS SCOPE. | ||
+ | - Press the button. | ||
+ | - When done the focus term of starlight on the TWFS should be zero. | ||
+ | - Turn off the servo on the mercury_gtk gui. | ||
+ | |||
+ | A couple of notes: | ||
+ | |||
+ | * If large moves of M2 are made, tiptilt tracking may be lost. Pay careful attention so that M2 doesn' | ||
+ | * If it takes too long to start the autofocus procedure, the mercury_gtk servo will automatically turn off and nothing will happen. So just make sure the servo is on right before hitting the FOCUS SCOPE button. | ||
===== Dome issue ===== | ===== Dome issue ===== | ||
Line 195: | Line 235: | ||
==== Dome does not rotate ==== | ==== Dome does not rotate ==== | ||
- | Sometimes when observing, the dome will not follow the telescope during a slew. This can happen when the Autodome feature is not turned on. Click the ON button on the MAIN tab of the telescope gui to enable it. This may happen after a server restart so always check the dome position with the spycam during a slew after a server restart. Also make sure the target position of the dome matches the telescope' | + | Sometimes when observing, the dome will not follow the telescope during a slew. This can happen when the Autodome feature is not turned on. Click the ON button on the MAIN tab of the telescope gui to enable it. This may happen after a server restart so always check the dome position with the spycam during a slew after a server restart. Also make sure the target position of the dome matches the telescope' |
- | If the dome does not turn at all, even with the manual controls on the telescope or dome guis, the control may be set to manual on the control box. This can happen if there was work done at the dome during the day. If the dome opens, but does not turn, check to see that control of the dome rotation is in the computer position and not manual on the dome rotation | + | If the dome does not turn at all, even with the manual controls on the telescope or dome guis, the control may be set to manual on the control box instead of computer. This can happen if there was work done at the dome during the day. If the dome opens, but does not turn, check the controller box just inside the door of the bunker. Sometimes the drive wheel jumps in the track and cannot turn the dome, even when the motor works. This will need to be fixed during the day. A fuse can also blow out in the dome control box and leave the dome stuck. |
==== Dome does not open ==== | ==== Dome does not open ==== | ||
Line 202: | Line 242: | ||
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, |
==== Dome does not close ==== | ==== Dome does not close ==== | ||
Line 222: | Line 262: | ||
==== LabAO Shutters Not Working ==== | ==== LabAO Shutters Not Working ==== | ||
- | 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 and held for 5 seconds so that the units can be controlled remotely. (Note: look for instructions on table.) | + | <font 10.5pt font-family:/ |
+ | |||
+ | <font 10.5pt font-family:/ | ||
+ | |||
+ | <font 10.5pt font-family:/ | ||
==== LabAO DM Electronics ==== | ==== LabAO DM Electronics ==== | ||
- | If a labao server complains that it failed to find the EDAC40 device, try unplugging the power and ethernet cables for DM and then replugging in again. | + | If a labao server complains that it failed to find the EDAC40 device, try unplugging the power and ethernet cables for DM and then replugging in again. The boxes for these are under the respective tables. |
===== OPLE and Metrology ===== | ===== OPLE and Metrology ===== | ||
Line 242: | Line 286: | ||
* This will install run_ople. Try opening the ople server again. | * This will install run_ople. Try opening the ople server again. | ||
- | ==== Metrology and Homing carts ==== | + | ==== Homing carts ==== |
- | | + | * To home the carts, turn off the [OL] and [MAN] buttons on each cart and it will automatically return to the front switch. If the cart has no issue, it will arrive at the target position of 0m and the home switch at the same time. The X in the OPLE server under the HM will indicate it has stopped on the home switch. If a cart does not reach the home switch when it returns to position 0m, it was lost and likely the cause of the difficulty in finding fringes. The X does not guarantee the cart has retained its home position. This home position can be checked by using the CHECK button on the ople gui or by typing the command |
- | | + | |
+ | ==== Metrology ==== | ||
+ | |||
+ | * Good metrology signals are important to the proper positioning of the carts. Monitor the signal strength by running [RUN MULTIPLE] on the Metrology Monitor. Place the windows above the TV windows for each scope you are using. They should show white sine waves that are around the height of the window. Erratic, fluctuating waves indicate self-interference or a weak signal. This may cause the carts to lose their place as the signal strength falls too low. Red waves indicate that some displayed signal has gone too low and the carts will all need to be homed. A careful adjustment of the MET2 mirror can sometimes bring the signal back. Do not adjust the MET1 mirror | ||
+ | |||
+ | Steps for adjusting MET2: | ||
+ | |||
+ | - Looking at the met signal while the cart is at the back. | ||
+ | - Peak so that the beam is aligned as well as possible. Does not need to be perfect but not loose. | ||
+ | - All beams have a signal between 1-2 volts while at the back. Sometimes the signal strength can change for no apparent reasons. | ||
+ | - Using steps of 50, try moving 3 times in one direction. After each step, wait 5 seconds or so for things to update. If nothing then try the other way. | ||
+ | - Return to starting position. | ||
+ | - Repeat for the other axis. | ||
===== Beam Samplers ===== | ===== Beam Samplers ===== | ||
- | ==== Beam Samplers are not moving ==== | + | ==== Beam Samplers are not moving |
This happens most frequently with the E1 beam sampler. If you are doing alignments and are using E1, try to move it forward first to see if it dies. If it does, follow this procedure. | This happens most frequently with the E1 beam sampler. If you are doing alignments and are using E1, try to move it forward first to see if it dies. If it does, follow this procedure. | ||
Line 315: | Line 371: | ||
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 " | The gps computer does the user authentication for the control side while ctrscrut provides the home directories. Yellowpages is gone, the new paradigm is LDAP (local directory access protocol). If you can't log on to computers on the control network, then make sure both ctscrut (michelson) and gps computers are running. If the login screen screen on ctrscrut says " | ||
- | If gps computer does not start, check the power distribution unit (PDU) at the top of that rack. If any units show both "+" and " | + | If gps computer does not start, check the power distribution unit (PDU) at the top of that rack. If any units show both " " and " |
===== General Problems ===== | ===== General Problems ===== | ||
Line 353: | Line 409: | ||
You can also look up different identifiers for the star by using the SIMBAD database: [[http:// | You can also look up different identifiers for the star by using the SIMBAD database: [[http:// | ||
- | DBADD uses SIMBAD to look up the coordinates of the star and then searches to see if the star is already in the CHARA database. If the star is in the database, it will return the CHARA number. If the star is not in the CHARA database, it will ask if you want to add it and assign a CHARA number if you answer yes. | + | DBADD uses SIMBAD to look up the coordinates of the star and then searches to see if the star is already in the CHARA database. If the star is in the database, it will return the CHARA number. If the star is not in the CHARA database, it will ask if you want to add it and will assign a CHARA number if you answer yes. |
If an object is not in SIMBAD (such as a recently discovered nova), then you must enter the object manually using the instructions below. | If an object is not in SIMBAD (such as a recently discovered nova), then you must enter the object manually using the instructions below. | ||
Line 414: | Line 470: | ||
Some binary stars have a common HD number with an A or B after them. These can cause problems as Cosmic Debris does not accept non numerical entries when filling in star designation. These stars are likely in CHARA' | Some binary stars have a common HD number with an A or B after them. These can cause problems as Cosmic Debris does not accept non numerical entries when filling in star designation. These stars are likely in CHARA' | ||
- | When a recognized identifier is entered, the HD number with A or B will usually display. Confirm that the coordinates, | + | When a recognized identifier is entered, the HD number with A or B will usually display. Confirm that the coordinates, |
**Editing the database: | **Editing the database: | ||
Line 428: | Line 484: | ||
Follow instructions in the [[: | Follow instructions in the [[: | ||
+ | |||
+ | ==== No Power for Aperture Wheels ==== | ||
+ | |||
+ | To minimize heat sources in the lab, the power for the apwheels is turned off. If you need to use aperture wheels during the night, the operator will need to plug the power into the outlet next to the metrology table (see photo below). If there are any communication issues after plugging in the power, try restarting the server using bootlaunch on ctrscrut. It's probably a good idea to home the apwheels after turning on the power. | ||
+ | |||
+ | {{: | ||
\\ | \\ | ||
- | Last updated | + | Last updated |