End of June saw a flurry of DIMM complaints.
26-June no complaints from the OSA
day crew found DIMM beeping (but I don't know if they found it in limit or not)
Worked fine early. The log quits at 11:01 UTC, just after the star drifts out of the region-of-interest. There are no core files, so it doesn't appear the software crashed. I don't see any indication it may have hit the limits - no indication of encoder values not changing, etc.
27-June no complaints from the OSA
day crew found DIMM beeping; but found it NOT in limit
Worked ok early, then at 09:16, encoder values were not updating when it tried to slew to RA: 19.846300, DEC: 8.867222 at 09:16 UTC. There were several restarts of the DIMM software after that, but the mount wasn't responding.
28-June OSA complained cannot get DIMM to move, sometimes doesn't even connect
day crew found DIMM beeping but NOT in limit
Again, worked early, stopped responding about 09:31 UTC
29-June OSA complained DIMM didn't respond at all with several resets of the PDU
day crew mechanically reset and rebooted
From the beg of the night, never really got a slew - the mount "initialized" a couple of times and they tried to got to RA/DEC, but encoder values didn't change and eventually they aborted and tried again each time

Steve Allanson noted that he found a similar situation during his last shift:
...where the mount was beeping but not on the hard limit (but close). The screws were beyond finger tight when I rescued it. Once I reset the axes and backed off the screws the nominal 30deg from finger-tight, I didn't have another problem with it.

Email on 27 June from Tim Shih

FYI
yesterday the dimm hit the limit and started beeping...
same thing today...

This used to be a very common occurrence, once upon a time, (many months ago)
and has been pretty stable since then....

I'm not sure what has happened in the past couple of days to cause
this issue to come back.

It has to be manually reset up on the telescope when this happens,
not a big deal, but annoying.

I went through the logs for the two nights.

26-June

The log quits at 11:01 UTC, just after the star drifts out of the region-of-interest. There are no core files, so it doesn't appear the software crashed. I don't see any indication it may have hit the hard limits.

27-June

the encoder values were not updating when it tried to slew to RA: 19.846300, DEC: 8.867222 at 09:16 UTC. There were several restarts of the DIMM software after that, but the mount wasn't responding.

See Tim's note below that when he went up to reset on this day, it was beeping but NOT in the limit. Reset by cycling power.

UTC
09:16  operator tried to slew to an RA/DEC
09:16  encoders -2092737 -3602810 -- no errors returned, but the encoder values were not updating
09:18  operator tried to abort slew
           again, encoders not changing, but not sure why this wouldn't finish

09:19   restarted DIMM software
    initialize mount, slew home, encoders not changing
    no abort, just encoders not changing

09:22  restarted DIMM software
09:23  saw an error from the mount driver MKS3PosRelativeSet

09:25  restarted DIMM software
09:27  mount initialized twice, slew to RA/DEC value
09:37  operator tried to abort slew
09:54  LBT not tracking messages, automatically tries to slew to home

10:06  operator tried to abort slew
10:07  operator stopped client GUI which does:  Disable guiding, Stop tracking
 ...       messages continued with encoder values not changing

Email the morning of 28-June by David Gonzalez Huerta

I think we are in the same situation with the DIMM again. I can restart the PDU but I cannot get the DIMM to move. ALso, sometimes the Mount cannot connect, even after restarting the PDU.

Tim Shih sent a note saying it was not in limits:
I realized that this morning (and also yesterday morning) that the dimm was beeping, but the actual unit had NOT hit the limits... the position was ok. It was reset by cycling power.
Went through the log:

06/28/2012 08:19:23.776 - Slew to RA: 19.846300, DEC: 8.867222.
                   found star, reported seeing until 08:28
                   continued, reported seeing until 08:40

06/28/2012 08:43:04.480 - Slew to RA: 19.846300, DEC: 8.867222.
                   found same star, reported seeing until 9:27

09:23UT SEEING: DIMM 0.84" @64.5, GCSL 0.48" (LBT @68.6)

09:29UT ACTIVE preset RA 18:25:55.2 DEC +14:57:58.4 AZ 246.9 EL 55.5 science field

06/28/2012 09:31:12.425 - Slew to RA: 18.615608, DEC: 38.782778.
                    almost immediately, encoders not changing (startSlewRaw)
                    encoders -2111831 -3583831
                    09:33 abortSlew

06/28/12 09:33:55.003 - Build 2012F DIMM Server is starting
                     during init, didn't finish home; encoders same as previous values but it thinks it finished finding home, then
                      slewRaw -> isSlewing -> trackedIntoLimit messages over and over

06/28/12 09:37:21.831 - Build 2012F DIMM Server is starting...logging to /lbt/log/dimm//20120628dimm.log
                     during init, didn't finish home; encoders same as previous values but it thinks it finished finding home, then 
                      slewRaw -> isSlewing -> trackedIntoLimit messages over and over



09:59UT ACTIVE preset RA 19:23:50.8 DEC +14:36:10.8 AZ 238.4 EL 60.4 science field

-- initialized mount twice here...
06/28/12 10:01:44.190 - Build 2012F DIMM Server is starting...logging to /lbt/log/dimm//20120628dimm.log
                     interesting... during init, see 0 0 encoders values
                     doesn't get stuck in trackedIntoLimit, gets stuck in checking for Home done
                     motorStatus entry over and over, waiting for home, then finishes ...and follows with
06/28/2012 10:02:54.699 - MKSDriver::trackedIntoLimit: encoders 0 2; exit code (from GetCurrentEncoder) 0
06/28/2012 10:02:54.734 - MKSDriver::GetCurrentPosition: Entry
06/28/2012 10:02:55.289 - MountBisque: slewHome: Move to origin position
06/28/2012 10:02:55.289 - MKSDriver::startSlewRaw: Entry
06/28/2012 10:02:55.664 - MKSDriver::trackedIntoLimit: encoders -605 -62; exit code (from GetCurrentEncoder) 0
06/28/2012 10:03:00.973 - MKSDriver::trackedIntoLimit: encoders -477663 -467461; exit code (from GetCurrentEncoder) 0
06/28/2012 10:03:06.288 - MKSDriver::trackedIntoLimit: encoders -1047330 -1037130; exit code (from GetCurrentEncoder) 0
06/28/2012 10:03:11.603 - MKSDriver::trackedIntoLimit: encoders -1617583 -1607346; exit code (from GetCurrentEncoder) 0
06/28/2012 10:03:17.303 - MKSDriver::trackedIntoLimit: encoders -1927383 -2219405; exit code (from GetCurrentEncoder) 0
06/28/2012 10:03:24.188 - MKSDriver::trackedIntoLimit: encoders -1927383 -2958054; exit code (from GetCurrentEncoder) 0
06/28/2012 10:03:30.998 - MKSDriver::trackedIntoLimit: encoders -1927383 -3686083; exit code (from GetCurrentEncoder) 0
06/28/2012 10:03:32.896 - DimmMountThread::setRunning: ENTER
06/28/2012 10:03:32.896 - connectMount Initializing mount...
06/28/2012 10:03:32.896 - MountBisque: init: Enter
06/28/2012 10:03:32.896 - MKSDriver::IsHomed2: Entry
06/28/2012 10:03:32.958 - MountBisque: init: MKSDriver->isHomed done
06/28/2012 10:03:32.958 - MountBisque: slewHome: Move to origin position
06/28/2012 10:03:32.958 - MKSDriver::startSlewRaw: Entry
06/28/2012 10:03:33.431 - DimmMountThread::setRunning: ENTER
06/28/2012 10:12:48.020 - Warning: LBT is not tracking.
06/28/2012 10:12:49.683 - Warning: LBT is not tracking.
06/28/2012 10:15:19.978 - Slew to RA: 18.615608, DEC: 38.782778.
06/28/2012 10:15:19.979 - MountBisque: goToRADEC: Enter.
06/28/2012 10:15:19.979 - MountBisque: goToELAZ: Enter.
06/28/2012 10:15:21.160 - MKSDriver::startSlewRaw: Entry
06/28/2012 10:15:25.379 - MKSDriver::trackedIntoLimit: encoders -2124729 -3912522; exit code (from GetCurrentEncoder) 0
06/28/2012 10:15:31.044 - MKSDriver::trackedIntoLimit: encoders -2124729 -3912522; exit code (from GetCurrentEncoder) 0


06/28/2012 10:15:19.978 - Slew to RA: 18.615608, DEC: 38.782778.

06/28/12 10:23:23.140 - Build 2012F DIMM Server is starting...logging to /lbt/log/dimm//20120628dimm.log
06/28/2012 10:23:27.561 - connectMount Initializing mount...
                         never got past ...
                     MKSDriver::trackedIntoLimit: encoders -2124729 -3912522; exit code (from GetCurrentEncoder) 0


Not usable the night of 29-June

Stuck on the first slew - several starts trying to initialize mount; finally mount initialized OK (apparently), tried to slew and got stuck:

06/29/2012 04:17:21.822 - connectMount Initializing mount...
06/29/2012 04:17:21.822 - MountBisque: init: Enter
06/29/2012 04:17:21.822 - MKSDriver::IsHomed2: Entry
06/29/2012 04:17:21.883 - MountBisque: init: MKSDriver->isHomed done
06/29/2012 04:17:21.883 - MountBisque: slewHome: Move to origin position
06/29/2012 04:17:21.883 - MKSDriver::startSlewRaw: Entry
06/29/2012 04:17:22.361 - DimmMountThread::setRunning: ENTER
06/29/2012 04:18:21.634 - Slew to RA: 14.261208, DEC: 19.187222.
06/29/2012 04:18:21.635 - MountBisque: goToRADEC: Enter.
06/29/2012 04:18:21.635 - MountBisque: goToELAZ: Enter.
06/29/2012 04:18:22.821 - MKSDriver::startSlewRaw: Entry
06/29/2012 04:18:27.126 - MKSDriver::trackedIntoLimit: encoders -2128042 -3567762; exit code (from GetCurrentEncoder) 0
06/29/2012 04:18:32.591 - MKSDriver::trackedIntoLimit: encoders -2128042 -3567762; exit code (from GetCurrentEncoder) 0
 ...  no change in encoder values after this ...

aborted a few times, but it doesn't ever come back from those because it tries to move to home.

restarted 4 times after this -- must have been stuck homing to Factory because we got the message:
   MountBisque: init: MKSDriver->isHomed done
but then it calls

06/29/12 05:59:27.101 - Build 2012F DIMM Server is starting...logging to /lbt/log/dimm//20120629dimm.log
06/29/12 05:59:27.102 - Using IIF on iif at port 10000
06/29/2012 05:59:27.148 - CommDatabase: open: Enter
06/29/2012 05:59:27.148 - MountBisque: setSlewRatePercent: Enter
06/29/2012 05:59:27.149 - DimmMountThread::run: ENTER
06/29/2012 05:59:27.149 - DimmMountThread::run: STOP
06/29/2012 05:59:27.189 - Waiting ...
06/29/2012 05:59:28.359 - Administration client started...
06/29/2012 05:59:28.359 - addCallback: pushing dimm, camera, mount settings
06/29/2012 05:59:28.864 - runInfoService_async: Start info service for client.
06/29/2012 05:59:30.152 - Initializing camera...
06/29/2012 05:59:30.152 - CameraEdt: init: Enter
06/29/2012 05:59:31.192 - connectMount Initializing mount...
06/29/2012 05:59:31.192 - MountBisque: init: Enter
06/29/2012 05:59:31.192 - MKSDriver::establishLink: ENTER
06/29/2012 05:59:31.334 - MKSDriver::establishLink MKS3VersionGet 2 5 19
06/29/2012 05:59:31.369 - MKSDriver::establishLink MKS3VersionGet 2 5 19
06/29/2012 05:59:33.269 - MKSDriver::IsHomed2: Entry
06/29/2012 05:59:33.389 - MKSDriver::trackedIntoLimit: encoders -21 0; exit code (from GetCurrentEncoder) 0
06/29/2012 05:59:33.449 - MKSDriver::OnGetRaDecCore: Entry
06/29/2012 05:59:33.449 - MKSDriver::GetCurrentPosition: Entry
06/29/2012 05:59:33.509 - MountBisque: init: MKSDriver->establishLink done
06/29/2012 05:59:33.509 - MKSDriver::IsHomed2: Entry
06/29/2012 05:59:33.569 - MountBisque: init: MKSDriver->isHomed done
Topic revision: r2 - 09 May 2014, KelleeSummers
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