Telescope and AGw Commissioning at LFBG with IRTC - 04-05 April 2009 MST

Observers: J. Hill (mtn), A. Rakich (standby in Tucson), J. Storm (Potsdam)
Telescope Operator: A. Ceranski
Telescope Support: J. Rousseau

Summary

The winter storm cleared out remarkably fast, but lots of bad seeing in its wake with everything at the wrong temperature.

Something was badly wrong with the pointing/tracking early but improved after we reset encoders a second time.

Closed 1 hour for wind and passing radar echoes. Not bad for the night after a winter storm.

Had problems with presets dropping out, accompanied by wierd shutdown errors from MCSPU. ???? See 00:33.

Measured the shift of probe position with focus, but were limited by bad seeing.

Adjusted probe encoder zeropoints to put the hotspot on the rotator center. This process was slowed significantly by bad seeing. We also had problems because the result is almost exactly at the end of the probe Y travel.

Preparations

12:30 Turn on snow melting as sky is clearing.

14:00 Dan C. changes the DSP card for rotators in jet.

14:10 Turn on Heat Trace

14:30 Enabled DX PMC telemetry in lbt.conf (with vi)

~14:40 OSSGUI and IIFGUI are red. Dan is working on MCSPU, but nobody was using OSS.

14:45 restarted guis, and they are OK. Was that caused by editting lbt.conf?

15:00 Driving telescope around to test jet with new DSP card. Rotate from Az 120 to 300 to melt frost on back side.
15:03 MCSPU seems to complain about poly time just when we do elready or elwaitopr.

Tony E. wrote:
The telemetry certainly does seem to cause the PMC to be a resource hog!
lbtmu104
Tasks:  81 total,   2 running,  79 sleeping,   0 stopped,   0 zombie
Cpu0  : 30.7% us,  7.7% sy,  0.0% ni, 61.3% id,  0.0% wa,  0.3% hi,  0.0% si
Cpu1  :  7.0% us,  2.0% sy,  0.0% ni, 90.7% id,  0.3% wa,  0.0% hi,  0.0% si
Mem:   1034552k total,   997972k used,    36580k free,   285940k buffers
Swap:  2621432k total,    24464k used,  2596968k free,    90012k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
28949 telescop  15   0  407m  28m 6104 S 41.8  2.8 355:36.21 PMCL

lbtmu105
Tasks:  83 total,   2 running,  81 sleeping,   0 stopped,   0 zombie
Cpu0  : 32.2% us, 27.9% sy,  0.0% ni, 39.2% id,  0.3% wa,  0.3% hi,  0.0% si
Cpu1  : 21.3% us, 63.8% sy,  0.0% ni, 15.0% id,  0.0% wa,  0.0% hi,  0.0% si
Mem:   1034552k total,   230256k used,   804296k free,    57452k buffers
Swap:  2621432k total,    24464k used,  2596968k free,    32172k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
 1399 telescop  15   0  452m  50m 6148 S 99.9  5.0 421:42.06 PMCR

It doubles the resident memory which isn't so bad.  But it again uses
99.9% of the CPU.  If I understand the CPU breakdown correctly, most of
the extra processor usage appears to be a kernel level.  This is probably
time spent in the IP stack.  I wish I could run a profiler on the
mountain.  I'll do some more investigation on Monday.

Unless the PMCR is misbehaving, I think it would be okay to leave it
running.  It's not saturating the computer and no other subsystems are on
lbtmu105, so it shouldn't interfere with the TCS performance as a whole.

17:35 Turn off snow melting, vent mode.

18:15 Reset encoders, as Dan reloaded fpga today.

18:20 Reboot IRTC as a preventative measure. Set temp to 245.

18:30 Reboot weather station to get rid of "not a floating point value" pop-ups. (It didn't help.)

Temperatures before Opening Dome
------------------- Air ------ Steel
C-Ring Upper 2.77 2.17
C-Ring Middle 2.98 2.31
C-Ring Lower 2.67 1.88
C-Ring Ext Left 2.74 2.13
C-Ring Ext Right 2.13 1.93
Wind B Upper 2.03 1.41
Wind B Middle Left 2.09 1.67
Wind B Middle Right 2.31 1.72
Wind B Lower Right 2.71 2.49
Mirror Cell Low Right 1.74 1.33

SX Glass 0.935
SX Ref Temp 2.33

HBS Temperature setpoint -8.10
Coolant return temperature  -7.53

Oil Reservoir -5.8

EL T_In 4.0 2.8 2.3 2.3
EL T_Out 3.9 3.3 2.5 4.1

18:41 Open side vent doors

Details

We are authorized as IRTC on the left side.

Open

18:45 Open Shutter Doors T=-6 degC, D=-13 degC, Sky clear, Wind a mere 10 m/sec from WSW.

Can anyone explain what this error message means?
Sat Apr 4 2009 18:43:18  SM:SMVent Right Limit Position Fail To run Alarm.
Sat Apr 4 2009 18:43:27  SM:SMVent Left Limit Position Fail To Run Alarm.
It happened when we opened the shutter doors while still in vent mode.

Michele says:The above error messages were generated by the ECSPLC. Neither SnowMelt nor Ventilation mode are supposed to be running when the shutter doors are open. If the shutter doors were already ajar, and then you tried to run SnowMelt or Ventilation, they would NOT start, and you would properly get these error messages. I will have to talk to Bruce about the logic in the PLC as it is apparently not quite correct.

19:15 Mounted spare GPS antenna on level 6.5 catwalk railing, and got a lock with dome open.

19:19 Reset overcurrent on both side vent doors

19:21 pointto M5_0314 ACQUIRE gs=0

Had big secondary offload on PSF M1 after slewing from parked position. So that piece of code still needs work. Still didn't find star after clearing that.

19:25 source ptspiral_irtc.csh - found glint very quickly. Found defocussed and a bit comatic image at IE=-60 CA=-63 which is almost a pure elevation correction for the IRTC pointing model.

Apr  4 19:21:30 lbtmu102 LBT_IRTC: IIF:Preset executed
Apr  4 19:21:30 lbtmu102 LBT_IRTC: [D] Calling PresetTelescope IIF::GetCommandStatus()
Apr  4 19:21:30 lbtmu102 LBT_IRTC: [D] Calling PresetTelescope IIF::statusInf->Block()
Apr  4 19:23:08 lbtmu102 LBT_IRTC: IIF:Preset execution time: 97969 ms

Apr  4 19:21:31 lbtmu107 LBT_PSFL: PSFL:secondaryOffload executed
Apr  4 19:21:31 lbtmu107 LBT_PSFL: PSFL:secondaryOffload execution time: 327 ms
Apr  4 19:22:54 lbtmu107 LBT_PSFL: PSFL:PrimaryMirror:adjustMirrorCollimation executed
Apr  4 19:22:54 lbtmu107 LBT_PSFL: PSFL:PSFSecondaryMirror:adjustMirrorCollimation executed
Apr  4 19:22:54 lbtmu107 LBT_PSFL: PSFL:PSFTertiaryMirror:adjustMirrorCollimation executed
Apr  4 19:22:54 lbtmu107 LBT_PSFL: ACTOPT: Primary collimated
Apr  4 19:22:54 lbtmu107 LBT_PSFL: ACTOPT: Secondary collimated
Apr  4 19:22:58 lbtmu107 LBT_PSFL: PSFL:PSFSecondaryMirror:adjustMirrorCollimation execution time: 3395 ms
Apr  4 19:22:58 lbtmu107 LBT_PSFL: PSFL:PSFTertiaryMirror:adjustMirrorCollimation execution time: 3862 ms
Apr  4 19:23:05 lbtmu107 LBT_PSFL: PSFL:PrimaryMirror:adjustMirrorCollimation execution time: 11282 ms

19:39 pointto BS9131 gs=0 ACTIVE - appeared near the lower edge of guide box. A little bit of active optics gets the image size down below (barely) 2 arcsec FWHM. Seeing is pretty awful - as you might expect when mirrors and telescope structure are 6 degC too warm.

19:47 pointto BS9131 ACTIVE gs=1,2 - couldn't move probe there.

19:50 pointto BS9131 ACTIVE gs=4 - seems to be guiding on a star that isn't here. (pointing had drifted off)

19:53 pointto BS9131 ACQUIRE gs=0 = star at bottom edge of acquire image. Adjust IE=-76 CA=-73.

IRTC orientation

19:56 pointto BS9131 ACTIVE gs=4 - star is faint, and ~8 arcsec off to the side at PA=335. These WFSC image still have enough twilight/moonlight to show all the lenslets as well as those illuminated by the pupil.

takepic 2 - irtc.20090405.030323.fits

20:06 pointto BS9131 ACTIVE gs=4

takepic 2 - irtc.20090405.030901.fits

20:10 offset 0 5 - star moves up on live IRTC image (for telescope moving 5 arcsec north), and star moves down on DS9 view of IRTC image. This means IRTC is mounted in the correct orientation and not 180 degrees off.

takepic 2 - irtc.20090405.031230.fits

These images have been moved to /Repository/IRTC_Data/090405/. Note also the cube of 2 sec blank frames taken later in the night for background removal.

BS9143

20:20 pointto BS9143 gs=0 ACTIVE - didn't find star in acquisition image

20:24 pointto BS9143 gs=0 ACQUIRE - adjust IE=-88 CA=-47

Wind is gusting above 18 m/sec. Primary mirror is only 2 degrees above dome reference temp, but reference temp is still 2 degC above outside ambient.

20:29 pointto BS9143 gs=0 ACTIVE - Seeing is varying from 1.3 arcsec to 2 arcsec FWHM from one guider image to the next.

Temperatures at 20:40
------------------- Air ------ Steel
C-Ring Upper -4.51 -3.27
C-Ring Middle 0.55 -0.04
C-Ring Lower -0.70 -0.09
C-Ring Ext Left -5.07 -4.57
C-Ring Ext Right -5.48 -4.88
Wind B Upper -5.88 -5.33
Wind B Middle Left -5.68 -4.52
Wind B Middle Right -5.45 -4.91
Wind B Lower Right -3.79 -2.50
Mirror Cell Low Right 1.74 1.33

SX Glass -1.787
SX Ref Temp -3.78

HBS Temperature setpoint -12.76
Coolant return temperature  -12.77

Oil Reservoir -9.4
Ta -0.2

EL T_In -1.5 0.1 -0.7 -0.7
EL T_Out 2.2 1.6 1.0 2.7

20:44 pointto BS9143 gs=14 ACTIVE - Down below 200 nm rms for the first time.

takepic 2 - irtc.20090405.034712.fits, but can't see the on -axis star on the irtc image.

Close

20:48 Close for wind and approaching radar echoes. Leave Left Vento Door open to keep cooling the chamber.

22:15 Aaron discovered that the computer room is very hot, even though the upstairs chillers seem to be happy. Chilled water temperature from util building is about 90 degF.

22:20 re-open vent doors as wind has dropped, and radar echoes are going south of us.

22:40 Aaron has the utility chiller restarted. Chiller 1 was off, and Chiller 2 had an alarm.

Open

22:45 Reopen shutter doors while waiting for chillers to recover. (presently without mirror ventilation)

22:48 pointto BS9143 gs=0 ACQUIRE PAM-

22:52 source ptspiral_irtc.csh - IE=-73 CA=-153

23:00 pointto BS9143 gs=14 ACTIVE - WFS is struggling against the high order terms caused by lack of mirror ventilation.

23:06 Image is bouncing, close rear vent doors to half way, and completely close side vent doors.

23:07 Restart SX Mirror Ventilation as upstairs LWT is down to -23.5.

23:08:50 dropped to None mode without explanation. Did a gust of wind blow us off-source?

23:10 pointto BS9143 gs=14 ACTIVE -

GCSGUI still displays one old guider image when it starts guiding.

23:12 image still bouncing; LBTO anemometer is reading only 10 m/sec.

23:14 dropped to None mode without explanation.

Apr  4 23:13:01.384: AZDrive: State still = AZ_READY
Apr  4 23:13:01.384: ELDrive: State still = EL_READY
Apr  4 23:13:05.977: LFBG RTracker:Just changed to Rotator NOT ON_SOURCE !
Apr  4 23:13:07.648: LFBG RTracker:Just changed to Rotator ON_SOURCE
Apr  4 23:13:07.952: LFBG RTracker:Just changed to Rotator NOT ON_SOURCE !
Apr  4 23:13:09.624: LFBG RTracker:Just changed to Rotator ON_SOURCE
Apr  4 23:13:44.077: MCSPU: AZ/EL ON_SOURCE just became FALSE
Apr  4 23:13:44.383: AZ Tracker :A slew appears to have started spontaneously while in TRACKING state
Apr  4 23:13:44.383: AZ Tracker :State changed from TRACKING --> SLEW_TO_TRACK
Apr  4 23:13:44.777: AZ Tracker :slew done. position =  215.756deg. vel=     0.007 deg/sec

Apr  4 23:13:44.777: AZ Tracker :Track Poly: t0=4745628858.764 t1=4745628858.814 n=2 seq=1530313  215:44:41.2     23.98  -0.00
Apr  4 23:13:44.777: AZ Tracker :Slew done. state-->TRACKING, pos'n= 776720.3 v=  26.96
Apr  4 23:13:44.777: AZ Tracker :State changed from SLEW_TO_TRACK --> TRACKING
Apr  4 23:13:46.058: AZ Tracker :A slew appears to have started spontaneously while in TRACKING state
Apr  4 23:13:46.059: AZ Tracker :State changed from TRACKING --> SLEW_TO_TRACK
Apr  4 23:13:46.712: AZ Tracker :slew done. position =  215.754deg. vel=    -0.004 deg/sec

Apr  4 23:13:46.713: AZ Tracker :Track Poly: t0=4745628860.666 t1=4745628860.716 n=2 seq=1530351  215:45:26.5     23.98  -0.00

We are pointing almost directly into the wind at Azimuth 217, so maybe it is more windy than the weather station indicates.

23:14 pointto BS9143 gs=14 ACTIVE -

23:20 pointto BS9145 gs=0 ACTIVE - no star found

23:24 pointto BS9145 gs=0 ACQUIRE PAM- star just in corner of field, adjust IE=-82 CA=-138

23:20 pointto BS9145 gs=0 ACTIVE - star on left edge even though I just centered it - different PA?

23:32 Close rear vent doors. Seeing is 1.7 to 2 arcsec.

23:32 Jesper joins us from Potsdam.

23:35 Block guiding in PCS. Star drifts left in guide box at 1 arcsec in 10 sec. Why so much?

Pupil Alignment versus focus

23:39 Block guiding again

readGuideCam 1000 100 - Data in /Repository/AGW_Data/090405/

23:43 setfocus move from 31 to 36 guider~9

23:44 setfocus to 41 guider 15

23:44 setfocus to 31 guider 18

23:44 setfocus to 21 guider 24

23:45 setfocus to 41 guider ~30

23:49 pointto BS9145 gs=0 TelM="ACTIVE" PA=0 - no star found. Is temperature really making the pointing move this fast? Or is this partly the offset from the rotator center?

23:52 pointto BS9145 gs=0 ACQUIRE PAM- IE=-74 CA=-93

23:55 pointto BS9145 gs=0 TelM="ACTIVE" PA=0 - Seeing "improved" 1 - 1.5 arcsec

00:02 pointto BS9145 gs=8 TelM="ACTIVE" PA=0 - no star

00:04 pointto BS9145 gs=8 TelM="ACQUIRE" PA=0

00:06 pointto BS9145 gs=0 TelM="ACQUIRE" PA=0 Adjust IE=-74 CA=-65

00:09 pointto BS9145 gs=8 TelM="ACTIVE" PA=0 - Acquisition identified a very faint star, but couldn't guide on it.

00:11 pointto BS9145 gs=7 TelM="ACTIVE" PA=180 - no star

00:12 pointto BS9145 gs=0 TelM="ACQUIRE" PA=180 - IE=-69 CA=-60

00:16 pointto BS9145 gs=7 ACTIVE PA=180 - no star

Must have been the wrong center star.......

00:20 pointto M5_0531 gs=0 ACQUIRE PAM-

source ptspiral_irtc.csh IE=-107 CA=64 but this star isn't bright enough to be the M5 star.

Stop and start afresh

00:32 Stop and restart MCSPU, and then go and reset the encoders again. ptreset .

00:36 SX primary mirror panics - things are really starting to fall apart here

Clear all active optics and secondary offload.

00:38 HBS trips off while slewing and we do the usual building collision. Aaron thinks this is regularly happening at Azimuth 209.

00:51 SX primary panics again

00:58 Encoder reset at 177, 3 complete. Go to zenith to raise mirror. Then it got M2 offload garbage.

01:03 pointto M5_0531 gs=0 ACQUIRE PAM- found a star very quickly at IE=+30 CA=-30 with the M2 offload IE=40. Zglobal=0.4 Brighter star at IE=+104 CA=-55.

01:16 pointto M5_0531 gs=0 ACQUIRE PA=180 (same place)

01:19 pointto M5_0531 gs=1 ACTIVE PA=180 - no star (maybe I was warned of this on the finder chart.)

01:20 pointto M5_0531 gs=7 ACTIVE PA=INDEF=133.9 - collimate to ~500 nm rms ~1.3 arcsec seeing

Measure rotator center

01:29 pointto M5_0531 gs=0 ACQUIRE PA=INDEF=0

BS9152

01:36 pointto BS9152 gs=0 ACTIVE PA=0

Sun Apr 5 01:38:32.802 2009 setting none mode on left side - WHYYYYYYYYYY?

Apr  5 00:33:21.111: LFBG CableChainSM: C_WAIT_CON_OFF clearing a pending 'C_DISABLE' command.
Apr  5 00:33:21.111: LFBG CableChainSM: Changing state from C_WAIT_CON_OFF --> C_IDLE
Apr  5 00:33:21.112: LFBG CableChainSM: unqueued a 'C_DEENERGIZE' hi-priority command
Apr  5 00:33:21.112: LFBG CableIdle:Got deenergize command.
Apr  5 00:33:21.114: LFBG CableChainSM: Changing state from C_IDLE --> C_DEENERGIZING
Apr  5 00:33:28.895: *** MCSPU main program is terminating!

Apr  5 00:33:28.895: Opt.Sup.:OpticalSupport::shutdown() called!
Apr  5 00:33:28.897: Left: Operator has commanded 'standby'
Apr  5 00:33:28.899: Right: Operator has commanded 'standby'
Apr  5 00:33:28.928: PlcTalker: writing :MCSPU_SA_RT_HALT_DINT (0x1) out to PLC
Apr  5 00:33:28.934: PlcTalker: writing :MCSPU_SA_LT_HALT_DINT (0x1) out to PLC

01:39 pointto BS9152 gs=0 ACTIVE PA=0 (probe was where the preset sent it) X=-0.198 Y=-0.088 from header

01:42 readGuideCam 20000 (slewing 197 to 0) taking 20000 2 sec exposures ????? guider00069

01:43 readGuideCam -e 20000 (slewing rotator 0 - 360) guider00070 - got a good ring

Rotator Center on IRTC

1:50 pointto BS9152 gs=0 TRACK PA=0

rotator=0 takepic 2 irtc.20090405.085129.fits

rotator=90 takepic 2 irtc.20090405.085232.fits

rotator=180 takepic 2 irtc.20090405.085331.fits

rotator=270 takepic 2 irtc.20090405.085430.fits

rotator=360 takepic 2 irtc.20090405.085520.fits irtc.20090405.085545.fits

The next day Dave T. reports: The current rotator center projects to: 156.02 137.50 on the IRTC.

Also note that Aaron was manually moving the rotator for the above sequence of exposures, so they do not show the correct position angle in the headers.

1:56 pointto BS9152 gs=0 ACTIVE PA=0 0.8 arcsec FWHM

Update encoder zeropoints:

02:00 Stop Guiding, Stop GCSL, Stop oacserver, Start oacserver. stopAGW. startAGW home, start GCSL

02:05 pointto BS9152 gs=0 ACTIVE PA=0 - couldn't move probe to position.

02:06 re-home

02:07 pointto BS9152 gs=0 ACTIVE PA=0 - couldn't move probe to position.

agwuser@agw-control:~$ setxy -x 0 -y 612
setxy: AGW1: Requested position is Out of Range.
Aborting...
agwuser@agw-control:~$ setxy -x 0 -y 611
Command successfully transmitted!

agwuser@agw-control:~$ setxy -x 0 -y 611.5
Command successfully transmitted!

agwuser@agw-control:~$ setxy -x 0 -y 611.8
Command successfully transmitted!

agwuser@agw-control:~$ setxy -x 0 -y 611.9
setxy: AGW1: Error moving the motor(s).
Aborting...
Probe can only get to 611.8

02:12 re-home to clear limit. Then setxy -x 0 -y 611.8

02:15 readGuideCam -e 80000 (rotator 0 to 360) guider00071 - John mistakenly thought correction was in wrong direction - which is wonderful news in this instance because it means the probe can reach the rotator center. Too bad it wasn't true.

02:18 stop GCS, stopAGW, stop oacserver, update params with reversed correction, start oacserver, startAGW, home motors

02:24 pointto BS9152 gs=0 ACTIVE PA=0 1.3 arcsec FWHM

setxy -x 0 -y 612.5

02:31 readGuideCam -e 75000 *rotator 0-360 guider00072 - For sure this reversed correction is in the wrong direction.

02:33 pointto BS9152 gs=0 ACTIVE PA=0

02:37 stop GCS, stopAGW, stop oacserver, update params with revised original correction, start oacserver, startAGW, home motors

agwuser@agw-control:~$ setxy -x 0 -y 612 Command successfully transmitted!

agwuser@agw-control:~$ setxy -x 0 -y 612.5 setxy: AGW1: Requested position is Out of Range. Aborting... agwuser@agw-control:~$ setxy -x 0 -y 612.2 Command successfully transmitted!

agwuser@agw-control:~$ setxy -x 0 -y 612.3 Command successfully transmitted!

agwuser@agw-control:~$ setxy -x 0 -y 612.4 setxy: AGW1: Error moving the motor(s). Aborting...

home again.

02:44 pointto BS9152 gs=0 ACTIVE PA=0 (we made it at x: -0.81 y: 611.92) Star was at right edge of acquisition image, and I think we expected that. Seeing 1.6 - 2.2 arcsec FWHM

setxy -x 0 -y 612.3

02:50 readGuideCam -e 75000 (0-360) guider00073

ptmodify IE 105 (from 100)

02:53 readGuideCam -e 75000 (360-0) guider00074

02:55 pointto BS9152 gs=0 ACQUIRE PA=0 - Adjust IE=110 CA=-54

02:59 stop GCS, stopAGW, stop oacserver, update params with fine tuned correction, start oacserver, startAGW, home motors

03:04 pointto BS9152 gs=0 ACTIVE PA=0

Dewpoint is down to -33.6 degC.

ptmodify CA -50

setxy -x 0 -y 612.3

03:09 readGuideCam -e 75000 (0-360) guider00075

03:12 pointto BS9152 gs=0 ACTIVE PA=0

03:14 IRTC background image - takeseq 2 50 ; takepic 2 irtc.20090405.101734.fits

03:15 stop GCS, stopAGW, stop oacserver, update params with fine tuned correction, start oacserver, startAGW, home motors

setxy -x 0 -y 612.5 works

03:19 pointto BS9152 gs=0 ACTIVE PA=0

03:23 focus 0

stop guiding; ptmodify CA -54; setxy -x 0 -y 612.5; send rotator to zero

03:25 readGuideCam -e 75000 (0-360) guider00076

03:27 readGuideCam -e 75000 (360-0) guider00077 (nicer bad seeing)

03:30 stop GCS, stopAGW, stop oacserver, update params with fine tuned correction, start oacserver, startAGW, home motors

setxy -x 0 -y 612.5 works

03:40 pointto BS9152 gs=0 ACTIVE PA=0

Seeing improves to 0.7 arcsec just after we told Andrew to go home because there was no chance of taking field aberration data in 1.8 arcsec seeing.

stop guiding; ptmodify CA -54; setxy -x 0 -y 612.5; send rotator to 360

03:46 readGuideCam -e 75000 (360-0) guider00078 (not the consistent answer that Jesper was expecting)

ACQUIRE IE=+110 CA=-60

03:51 pointto BS9152 gs=8 ACTIVE PA=0 - aborted because John screwed up the Agw

03:53 stop GCS, stopAGW, stop oacserver, update params with fine tuned correction, start oacserver, startAGW, home motors

03:58 pointto BS9152 gs=0 ACTIVE PA=0

04:03 focus 0

stop guiding; ptmodify CA -64; setxy -x 0 -y 612.5; send rotator to 360

04:05 readGuideCam -e 75000 (360-0) guider00079

04:07 pointto BS9152 gs=8 ACTIVE PA=0 (acquisition off not more than 3 arcsec from where expected)

04:10 stopAGW, stop oacserver, update params with fine tuned correction, start oacserver, startAGW, home motors

04:14 pointto BS9152 gs=0 ACTIVE PA=0

stop guiding; ptmodify CA -64; setxy -x 0 -y 612.5; send rotator to 360

04:19 readGuideCam -e 75000 (360-0) guider00080 (looks nice, declare that we are there)

Preliminary check and preparations for off-axis transformation data

04:21 pointto BS9152 gs=7 ACTIVE PA=0 Seeing is 0.9 to 1.1 arcsec.

04:24 John crashed IRTC interface by pressing the movie reel button. Restart the IRTC windows machine.

Testing LBTtools.IRTC.center2 which took irtc.20090405.113155.fits
   ### Send corrected absolute offsets
   Rabs = 0.000, Dabs = 0.000
   Roff = 7.715, Doff = 0.118
   irc OffsetPointing 0.0 7.715 0.118 RADEC_FOCAL MOUNT true ABS left
But telescope didn't move ??? An offset command that works looks like:
   irc OffsetPointing 0. 0. 0. RADEC MOUNT true ABS left

Why did an offset 0 0 produce this set of messages?
Sun Apr  5 04:37:03.226 2009  Offset alert for left IRTC: couldn''t move probe to position (SFP) -20.82, 109.608, focus: 24.8658 :AGw command status: timed out waiting for probe to reach destination
Sun Apr  5 04:37:03.279 2009  Offset alert for left IRTC: couldn''t move probe to position (SFP) -20.82, 109.608, focus: 24.8658 :AGw command status: timed out waiting for probe to reach destinationerror: setProbePosition: couldn''t move probe to position (SFP) (x,y,z): -20.82, 109.608, 24.8658 mm.
Sun Apr  5 04:37:03.332 2009  Offset alert for left IRTC: oacontrol indicated an error moving to new position
Sun Apr  5 04:37:03.384 2009  Offset alert for left IRTC: timed out waiting for probe to reach destination
Sun Apr  5 04:37:03.438 2009  Offset alert for left IRTC: Primary mirror collimation reached limit
Sun Apr  5 04:37:03.490 2009  Offset command complete with warnings for left IRTC from IIF

Trying to Repeat Focus Motion test in better seeing and better tracking.

04:39 pointto BS9152 gs=0 ACTIVE PA=0 - couldn't move probe

Tip +10 to get off -Y limit of M1

04:42 pointto BS9152 gs=0 ACTIVE PA=180

Why is IIFGUI claiming that WFS is paused? And not sending corrections.......

04:46 pointto BS9152 gs=0 ACTIVE PA=180

Restart IIFGUI, but it is still missing the WFS corrections that GCS seems to be sending

stop guiding; readGuideCam -e 1000 100

focus 31 guider 81-90

focus 41 guider 93-98

focus 21 guider 100-106

focus 11 guider 109-113

focus 41 guider 117-121

Back to offset stars

04:54 pointto BS9152 gs=0 ACQUIRE PA=180 - couldn't move probe ??? weren't we just at this location???

04:56 stopAGw, startAGw, home

05:02 pointto BS9152 gs=0 ACQUIRE PA=180 - IAdjust IE=105 CA=-65

05:04 pointto BS9152 gs=0 ACTIVE PA=180 - seeing is back to 2 arcsec.

05:08 pointto BS9152 gs=1 ACTIVE PA=180 - missed the acquisition by 3 arcsec toward 8 oclock.

05:10 pointto BS9152 gs=17 ACTIVE PA=180 - missed the acquistion by 7-8 arcsec toward 11 oclock

05:12 pointto BS9152 gs=9 ACTIVE PA=180 - M1 hits -Y limit.

Tip 20

GCSL seemed to hang, so we killed it

05:19 pointto BS9152 gs=0 ACQUIRE PA=180 - couldn't move probe, but why?
agwuser@agw-control:~$ getxy
Guide probe position
        x: -1.423000
        y: 611.854000

05:22 pointto BS9152 gs=0 ACQUIRE PA=180

 Apr  5 05:23:26.259 2009  Preset alert for left IRTC mode ACQUIRE: couldn''t move probe to position (SFP) 0.440187, -0.0123925, focus: 30.9873 :AGw command status: timed out waiting for probe to reach destination
Sun Apr  5 05:23:26.311 2009  Preset alert for left IRTC mode ACQUIRE: couldn''t move probe to position (SFP) 0.440187, -0.0123925, focus: 30.9873 :AGw command status: timed out waiting for probe to reach destinationerror: setProbePosition: couldn''t move probe to position (SFP) (x,y,z): 0.440187, -0.0123925, 30.9873 mm.
Sun Apr  5 05:23:26.363 2009  Preset alert for left IRTC mode ACQUIRE: guidestar list successfully changed b

Why were there multiple copies of this same error message?

05:25 pointto BS9152 gs=0 ACQUIRE PA=0 - adjust IE=97 CA=-70

05:28 pointto BS9152 gs=19 ACTIVE PA=0 -couldn't move probe, star is beyond edge of field

05:29 pointto BS9152 gs=14 ACTIVE PA=0 - star is 4 arcsec toward 7 oclock, but sky too bright to find it.

Close

05:32 Close shutter doors for approaching dawn T=-3.7 degC (warming in just the last hour when the seeing got worse again), D=-32.6 degC. Wind 10 m/sec from West. Broken cirrus had moved in the last hour.

-- JohnHill - 02 Apr 2009
Topic revision: r12 - 18 Apr 2009, JohnHill
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback