Differences

This shows you the differences between two versions of the page.

--- chara:trouble_shooting [2023/07/06 07:49]
gail_stargazer
+++ chara:trouble_shooting [2023/11/21 01:23]
charaobs [Can't find the star]
@@ Line 28: / Line 28: @@
   * 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, then use the command fringe_predictor. A window will pop up displaying the last five nights of offsets vs. HA.
+===== 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 =====
@@ Line 195: / Line 211: @@
 S2's acquisition server resides on "S2pi4" computer. Logging on to it (ssh s2pi4) and running bootlaunch will restart it
+==== 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't get driven away crazily due to lost light.
+  * 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 =====
@@ Line 229: / Line 262: @@
 ==== 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:/inherit;;#333333;;inherit>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.) A good way for this step is to manually set the shutter to the opposite state that it is in remotely, keep pressing the “enable” button until you hear a slight click. Release. The shutter should now change state.</font>
+<font 10.5pt font-family:/inherit;;#333333;;inherit>If this does not work, or the other CHARA shutters are not working then a reboot is required. The order of restart needs to be correct for all shutters to work again (not shutters on insturment tables which are controlled by instrument servers).</font>
+<font 10.5pt font-family:/inherit;;#333333;;inherit>Turn off electronics box for shutters (above the GPS computer). Reboot the gps computer. Check to see that the shutter server is running by typing bootlaunch_master on gps computer. If running, turn on shutter electronics box (you just rebooted gps computer so restart gps server).</font>
 ==== LabAO DM Electronics ====
@@ Line 251: / Line 288: @@
 ==== 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 “homechk S1” into the ople server. When the error value is displayed on the ople server, hit ESC to clear the display. Click on the [OL] and [MAN] buttons and hit [TRACK] to send the cart to the desired cart position.
-To home the carts, turn off the [OL] and [MAN] buttons on each cart and it will automatically return to the front switch. If the cart has no issue, it will arrive at the target position of 0m and the home switch at the same time. The X in the OPLE server under the HM will indicate it has 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 “homechk S1” into the ople server. When the error value is displayed on the ople server, hit ESC to clear the display. Click on the [OL] and [MAN] buttons and hit [TRACK] to send the cart to the desired cart position.
 ==== 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
-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:
@@ Line 451: / Line 484: @@
 Follow instructions in the [[:chara:mircx_monitors|linked page to display the MIRC-X wolverine2 monitors]] in the control room.
+==== 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.
+{{:chara:d859af0efb2dab690d3a44526d7b8afc.png}}
  \\

The CHARA Array Wiki

User Tools

Site Tools

Differences

Page Tools