Differences

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

--- chara:trouble_shooting [2020/01/28 03:02]
charaobs
+++ chara:trouble_shooting [2021/09/28 15:02]
gail_stargazer
@@ 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. 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.
-  * Did the Astrolib update on OPLE? If the job queue is stopped too soon after slewing on Cosmic Debris, the correct calculations for the carts will not be done by OPLE and you may be searching for fringes with the wrong star data. Hit STAR ACQUIRED on CD to update ople.  The proper star can also be entered by typing hd #### into the OPLE server and hitting ENTER.
+  * Did the Astrolib update on OPLE? If the job queue is stopped too soon after slewing on Cosmic Debris, the correct calculations for the carts will not be done by OPLE and you may be searching for fringes with the wrong star data. Hit STAR ACQUIRED on CD to update ople. The proper star can also be entered by typing hd #### into the OPLE server and hitting ENTER.
-  * Are the PoP's correct?  After a PoP change, the PoP's are sometimes not updated in CD or ople.
+  * Are the PoP's correct? After a PoP change, the PoP's are sometimes not updated in CD or ople.
-  * Are the carts behaving or are there vibrations or jumps of 100 or more microns every 3-6 seconds?  Restart the ople server if they persist.
+  * Are the carts behaving or are there vibrations or jumps of 100 or more microns every 3-6 seconds? Restart the ople server if they persist.
   * 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?
@@ Line 57: / Line 57: @@
  \\ 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**  above. \\ 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 "SHUTTERS". Restart the Shutters server with the commands below. After restarting the server and testing the gui to see that it works, turn the SHUTTERS power back on with the switch. There is a printed sheet of directions in the lab to help you. \\  \\ /usr/local/bin/tsockman rm shutters \\ ctrscrut/usr/local/bin/shutter_server /ctrscrut/chara/etc/shutter.cfg &
+==== MIRC-X CredoneImAcq Server ====
+The MIRC-X CredoneImAcq server and GUI can be opened using the "credone" icon on the wolverine desktop. Note that you can only have one of these open at a time. If you get an error message and can't bring up credone, then close the error message and follow the steps below to remove the dead processes first:
+From a terminal window, log on to mircx (old observe password): \\ ssh -X spooler@mircx
+Look up credone process: \\ ps aux | grep credone
+Kill all credone processes (including the ones for the error messages) using "kill -9 PID" where PID is the process number. Note that credone can't be restarted if there are any error processes in the list. Check "ps aux | grep credone" one more time to make sure all processes are cleared (the only one that should show up is the grep command that was just issued).
+Then restart credone using the desktop icon or by issuing the following command on spooler@mircx: \\ credoneImAcq –no-display
+(the first "–" should be two dashes: - and -).
 ===== Telescopes and Dome Servers =====
@@ Line 99: / Line 113: @@
   * ENABLE the telescope using the telescope or dome GUI. Check to see if the command and telescope positions are correct. If they are, then turn on the power for the telescope drives. Re-enter the star information by entering the HD number in the telescope server and click [GO NEXT] to send the telescope to the star. Make sure that the telescope is behaving as expected. The telescope might have drifted a bit, so if you can't find the star, it might be necessary to use the Telrad on a bright star to re-initialize the pointing.
   * Restart commands for the dome servers are also listed on the desktop in a text file.
 <code>
    \
  ==== Telescope is tracking poorly, overshooting in slew, oscillating. ====
 </code>
 <code>
 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  |
 </code>
@@ Line 121: / Line 137: @@
 ==== How to Adjust CPUMotor Gains ====
- \\ The GAIN controls the gain of the feedback between the encoder and the drive velocity. A high gain means a "stiffer" response, but can lead to oscillations or fog-horning if it's too high. \\  \\ 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 "wrong" thing seems to change. It is a sign that you are trying to do things too quickly. \\  \\ Slew and tracking mode work differently, mostly because the speeds are so different. \\  \\ 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't overshoot the target. Fn in slew mode should almost never be higher than 4. If it is, please turn it back down to 4. If you think this is a problem please let Theo know, along with a detailed explanation of what happened. \\  \\ 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 "oscillates", which you will see in the green dots of tiptilt oscillating, try turning up the gain, and also try turning down the Fn. \\  \\ 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, it almost always shows you that the scope is oscillating. If the white dots are centered on tiptilt and the green dots are moving the tiptilt is doing it's job and correcting for scope motion. \\  \\ - 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't change at all. After 5 secs the software interprets this as a stall and disables the drive. The tricky part is that increasing the gain to avoid this situation might make the telescope to oscillate during the next slew. So the gain should be low (4 or even 1) during slewing but higher 7 or 10 when the telescope is basically at the target position. \\ {{https://ssl.gstatic.com/ui/v1/icons/mail/images/cleardot.gif?direct&|external image cleardot.gif}}
+ \\ The GAIN controls the gain of the feedback between the encoder and the drive velocity. A high gain means a "stiffer" response, but can lead to oscillations or fog-horning if it's too high. \\  \\ 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 "wrong" thing seems to change. It is a sign that you are trying to do things too quickly. \\  \\ Slew and tracking mode work differently, mostly because the speeds are so different. \\  \\ 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't overshoot the target. Fn in slew mode should almost never be higher than 4. If it is, please turn it back down to 4. If you think this is a problem please let Theo know, along with a detailed explanation of what happened. \\  \\ 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 "oscillates", which you will see in the green dots of tiptilt oscillating, try turning up the gain, and also try turning down the Fn. \\  \\ 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, it almost always shows you that the scope is oscillating. If the white dots are centered on tiptilt and the green dots are moving the tiptilt is doing it's job and correcting for scope motion. \\  \\ - 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't change at all. After 5 secs the software interprets this as a stall and disables the drive. The tricky part is that increasing the gain to avoid this situation might make the telescope to oscillate during the next slew. So the gain should be low (4 or even 1) during slewing but higher 7 or 10 when the telescope is basically at the target position.
+==== E2 AOB Dichroic Recovery ====
+{{:chara:files:beaconrecoveryinstructions.pdf|E2 AOB Dichroic Recovery Document}}
+==== E1 Hut and Cooler Communications Recovery ====
+{{:chara:files:e1_hut_coms_recovery.pdf|E1 HuT and Cooler Communications Recovery}}  \\
+{{https://ssl.gstatic.com/ui/v1/icons/mail/images/cleardot.gif?direct&|external image cleardot.gif}}
 ====== Dome issues ======
@@ Line 312: / Line 337: @@
 ==== 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 [[:chara:mircx_monitors|linked page to display the MIRC-X wolverine2 monitors]] in the control room.
-\\
+ \\ Last updated 2017-04-12

The CHARA Array Wiki

User Tools

Site Tools

Differences

Page Tools