2010/mlso.2010d236.olog:I noticed that the opal was in a lot, the images were bright too, I thought 2010/mlso.2010d236.olog:opal stayed in place even though the GUI said it was out. I tried various 2010/mlso.2010d236.olog:ways to move the opal out but the way that worked was to stop the program 2010/mlso.2010d236.olog:I also checked the cables and drive mechanisms for the opal and they looked 2010/mlso.2010d256.olog:camera. With the opal in or light clouds D10 and D11 became active. 2012/mlso.2012d059.olog:Stopping obs to check function of opal due to problem stated in yesterday's 2012/mlso.2012d095.olog:Looks like opal stopped moving yesterday (per email form Leonard), restarting newport motion control box appears to have fixed it. 2012/mlso.2012d095.olog:I rebooted the controller before checking if the "Control ESP3000" actually rasies an error, when the opal doesnt move. We currently dont recieve error out from the vi; so we will miss the error even if it does. 2012/mlso.2012d095.olog:As a follow up from earlier the "Control ESP300" wont throw an error if the opal doesnt move. It looks like it only throws an error if the controller is off. 2012/mlso.2012d104.olog:Added a little routine to check if the opal moved the desired postion, after doing an opal move. If the final position doesn't match the desired position it will pop up a dialog box recommending rebooting the esp300 controller. 2012/mlso.2012d106.olog:Got about 4 opal esp300 error messages during Focus and startup this morning, 2012/mlso.2012d106.olog:related to new code check added on Friday. But it looked like the opal moved 2012/mlso.2012d106.olog:pops up again, it got past the opal moving parts of the early Cookbook 2012/mlso.2012d107.olog:ESP300 opal error that Darryl saw yesterday was due to polling the state of the ESP300 before; before the limit switch condition was registered to the ESP300. I added an extra wait (1000ms) to the move opoal code which seems to take care of this 2012/mlso.2012d305.olog:manuals/diagrams. Visually confirmed operation of opal, dark shutter, tilt plate 2012/mlso.2012d345.olog:Mangin and fold prism moved to adjust the conrona down. Doing a scan with opal in and rather thick cirus to check heights. 2012/mlso.2012d345.olog:Adding opal in for left scan 2012/mlso.2012d345.olog:Actually opal was moved out 2012/mlso.2012d345.olog:one more scan with opal mangin and prism moved to try and get the signal lower on the detector 2012/mlso.2012d347.olog:Prism moved, opal in taking scan 2012/mlso.2012d347.olog:Oops opal out 2012/mlso.2012d347.olog:Scanning now with opal in (and some clouds) 2012/mlso.2012d347.olog:One more moved of the prism, taking opal scan 2012/mlso.2012d347.olog:Taking a scan with opal out 2012/mlso.2012d347.olog:Prisim move, taking scan w/o opal 2012/mlso.2012d347.olog:Prism move, taking scan w/o opal 2012/mlso.2012d347.olog:Prism move, taking scan w/o opal 2012/mlso.2012d347.olog:Started mask out scan with opal in. Ladder part of the scan shows a lot of clouds. 2012/mlso.2012d348.olog:Taking one scan with mask and opal in beam. 2012/mlso.2012d348.olog:Taking one more scan with opal out 2013/mlso.2013d326.olog:Taking opal data exposure set to .16ms 2013/mlso.2013d326.olog:First pass check of the opal data looks like it is 6x dimmer then the old diffuser 2013/mlso.2013d329.olog:Changed diffsrid to mk4-opal 2013/mlso.2013d343.olog:Inital inspection showed no smuges, but fine dust particles scattered across the surface with a few larger ones. After an inital attempt to clean with 91% isopropal alchoal I found it impossible to work with the lens inside its mount 2014/mlso.2014d206.olog:Found the bad fan. It is a small cooling fan on one of the 36979-01 boards inside the ESP300 enclosure. The board with the bad fan is the board that drives the OPAL (slot2). Unfortunately we don.t have spare fan, and the fan is soldered onto the board making it non-trivial to replace. We do have a second 36979-01 board in the ESP300 that is wired to rotate the calibration polarizer (slot1); however we do not use the cal-polarizer (and as far as I remember we have never used it at MLSO). As a temporary fix for the bad fan problem I have removed the bad 36979 from slot 2 and replaced it with the good one from slot 1. The bad 36979 is on the lab bench waiting. A small software change was required to make this work; in the opal move code we check the ESP300 hardware status to see if the opal made it to the commanded position; with the second 36979 remove the magic numbers change from 604/406 (out/in) and to (705/507). With these changes CoMP seems to be working again. . 2014/mlso.2014d360.olog:I had a lot of trouble getting the comp E/W occulting stage aligned this morning. For some reason the CoMP.vi didnt read the current position when it started up and assumed 0. Moving from this position I compltely lost the pointing. KMy initial attempt to recover involved manually driving the occulter in by turning the NSC200 knob while looking at the solar image with the comp cover off. This. This realigned the occulter but I still had trouble controlling it from CoMP.vi Next I re-homed the E/W motor (manually with the knob), then put the opal in the beam and used the center occulter.vi to drive the occulter back to the center. 2015/mlso.2015d137.olog:Comp occulter in the horizontal position was at 0 instead of 79800. Called Ben to help trouble shoot since it wouldn't respond through the focus GUI. Just so it's here: three toggles on the back of Comp. Want the three leds on the toggles to be orange, if green, press toggle in to change to orange. If red, hold down till flashes and then becomes solid again. At that point it's homing the occulter. Once it's solid, make sure that led is orange before heading back down. Close the Comp GUI and reopen it. Go to file open, click file move-opal.vi. Click the little switch to close and run the Comp GUI. Once done, run the Move-Opal GUI and it will place the opal in beam. Once done, go to center occulter and get the value that was low up in the 70,000-76,000 range. Then move opal out (open) and center the occulter as normal. 2015/mlso.2015d210.olog:Fixed the ESP 3000 magic numbers for detecting the opal position back to 604/406 which are the appropriate numbers for opal in/out when the calpol rotator board is installed. 2015/mlso.2015d307.olog:Comp 01, opal, and opal motor assy are packed. I am leaving now to take the box 2016/mlso.2016d125.olog:The observing code was edited to use the new opal motor. Focus has been demostrated to work but not integrated into the observing code. 2016/mlso.2016d132.olog:A set of distortion grid data + one dark was taken with the opal in, and occulting disk removed. Data should be between 21:42-21:48. Rain apporached the observatory so the last few images in the last recipe may be cut short due to closing of the dome and moving of the spar. 2016/mlso.2016d349.olog:This morning I tired to troubleshoot an error message we get when comp computer reboots and reconnects to the opal controller. Looks like this troubleshooting disabled the opal. 2016/mlso.2016d349.olog:122250.FTS->122601.FTS Standard darks and bad flats (opal out) 2016/mlso.2016d349.olog:124738.FTS->125049.FTS Standard darks and bad flats (opal out)