Results 1 to 10 of 36

Threaded View

  1. #7
    Join Date
    Oct 2005
    Location
    Mesa, AZ
    Posts
    27,485

    Default

    1. I tried running your rotation script and just got errors. Not sure what the issue is, but I am uploading the log file.
    The log was for NGC6992 not for the rotator test. Not a problem, your run and its log tells me everything I need to know anyway. See the rotator analysis below.

    Some comments on the log you did provide:

    Pointing Errors Analysis:

    03:54:33 Pointing error is 2.875 arcmin @ angle 100.31
    03:57:14 Pointing error is 2.742 arcmin @ angle 102.00
    04:03:40 Pointing error is 2.435 arcmin @ angle 96.73
    04:09:37 Pointing error is 2.853 arcmin @ angle 96.87
    04:15:32 Pointing error is 3.262 arcmin @ angle 96.87
    04:21:36 Pointing error is 3.722 arcmin @ angle 97.46
    04:27:43 Pointing error is 4.105 arcmin @ angle 95.93
    04:33:38 Pointing error is 4.460 arcmin @ angle 95.45
    04:39:37 Pointing error is 4.813 arcmin @ angle 94.76
    04:45:38 Pointing error is 5.301 arcmin @ angle 95.07
    04:51:42 Pointing error is 0.802 arcmin @ angle 90.47
    04:57:37 Pointing error is 1.237 arcmin @ angle 93.17
    05:03:37 Pointing error is 1.609 arcmin @ angle 93.30
    05:09:32 Pointing error is 2.058 arcmin @ angle 91.99
    05:15:38 Pointing error is 2.515 arcmin @ angle 93.15
    05:21:44 Pointing error is 3.014 arcmin @ angle 91.25
    05:27:37 Pointing error is 3.390 arcmin @ angle 91.99
    05:33:32 Pointing error is 3.843 arcmin @ angle 91.57
    05:39:37 Pointing error is 4.251 arcmin @ angle 92.52
    05:45:39 Pointing error is 4.691 arcmin @ angle 91.49
    05:51:42 Pointing error is 5.164 arcmin @ angle 90.56
    05:57:41 Pointing error is 0.928 arcmin @ angle 87.94
    05:58:27 Pointing error is 2.096 arcmin @ angle 109.46
    06:02:02 Pointing error is 2.036 arcmin @ angle 70.19
    06:09:45 Pointing error is 4.391 arcmin @ angle 90.59
    06:15:39 Pointing error is 4.836 arcmin @ angle 91.58
    06:21:39 Pointing error is 5.333 arcmin @ angle 91.61
    06:27:52 Pointing error is 0.888 arcmin @ angle 95.75
    06:33:48 Pointing error is 1.353 arcmin @ angle 94.77
    06:34:35 Pointing error is 3.800 arcmin @ angle 91.62
    06:37:28 Pointing error is 4.047 arcmin @ angle 81.70
    06:44:14 Pointing error is 3.535 arcmin @ angle 71.65
    06:50:10 Pointing error is 3.960 arcmin @ angle 73.39
    06:56:10 Pointing error is 4.374 arcmin @ angle 75.75
    07:02:16 Pointing error is 4.807 arcmin @ angle 76.19
    07:08:16 Pointing error is 5.125 arcmin @ angle 77.32
    07:14:18 Pointing error is 0.787 arcmin @ angle 96.61
    07:20:11 Pointing error is 1.217 arcmin @ angle 97.63
    07:26:24 Pointing error is 1.692 arcmin @ angle 94.86
    07:32:21 Pointing error is 2.030 arcmin @ angle 93.32
    07:38:25 Pointing error is 2.408 arcmin @ angle 91.68
    07:44:17 Pointing error is 2.786 arcmin @ angle 93.65
    07:50:31 Pointing error is 3.272 arcmin @ angle 93.99
    07:56:37 Pointing error is 3.661 arcmin @ angle 93.57
    08:02:31 Pointing error is 4.016 arcmin @ angle 92.82
    08:08:35 Pointing error is 4.472 arcmin @ angle 91.89
    08:14:39 Pointing error is 4.805 arcmin @ angle 91.79
    08:20:42 Pointing error is 5.266 arcmin @ angle 91.77
    08:26:53 Pointing error is 0.784 arcmin @ angle 88.95
    08:33:03 Pointing error is 1.176 arcmin @ angle 93.21
    08:38:58 Pointing error is 1.564 arcmin @ angle 93.31
    08:39:45 Pointing error is 2.583 arcmin @ angle 67.27
    08:43:46 Pointing error is 2.335 arcmin @ angle 111.85
    08:50:38 Pointing error is 2.141 arcmin @ angle 78.17
    08:56:34 Pointing error is 2.499 arcmin @ angle 81.58
    09:02:28 Pointing error is 2.939 arcmin @ angle 83.11
    09:08:26 Pointing error is 3.315 arcmin @ angle 85.23
    09:14:34 Pointing error is 3.703 arcmin @ angle 85.03
    09:15:17 Pointing error is 1.479 arcmin @ angle 77.86
    09:19:36 Pointing error is 3.683 arcmin @ angle 86.66
    09:26:18 Pointing error is 3.662 arcmin @ angle 75.31
    09:32:14 Pointing error is 3.994 arcmin @ angle 77.78
    09:38:26 Pointing error is 4.483 arcmin @ angle 78.62
    09:44:20 Pointing error is 4.972 arcmin @ angle 78.87
    09:50:19 Pointing error is 5.471 arcmin @ angle 79.94
    09:56:21 Pointing error is 0.919 arcmin @ angle 92.68
    10:02:21 Pointing error is 1.356 arcmin @ angle 90.11
    10:08:16 Pointing error is 1.861 arcmin @ angle 87.73
    10:14:21 Pointing error is 2.386 arcmin @ angle 86.64
    10:20:15 Pointing error is 2.841 arcmin @ angle 88.18
    10:26:11 Pointing error is 3.393 arcmin @ angle 87.88
    10:32:15 Pointing error is 3.864 arcmin @ angle 88.28
    10:38:09 Pointing error is 4.346 arcmin @ angle 88.76
    10:44:05 Pointing error is 4.795 arcmin @ angle 89.30
    10:50:09 Pointing error is 5.289 arcmin @ angle 90.25
    10:56:25 Pointing error is 0.993 arcmin @ angle 91.48
    11:02:28 Pointing error is 1.471 arcmin @ angle 92.93

    The pointing error is quite large for that direct drive mount with encoders. It should be sub-arc-minute all night. Note that we set the Max Pointing Error in ACP to 5 arc minutes, so as designed, the error increased to 5 arc-minutes and ACP did a resync of the mount seven times in six hours.

    08:20:42 Pointing error is 5.266 arcmin @ angle 91.77

    ...
    08:20:48 Re-slew to target.
    08:20:48 Start slew to NGC6992 RGB...
    08:20:49 (wait for slew to complete)
    08:20:53 (slew complete)
    ...
    08:26:53 Pointing error is 0.784 arcmin @ angle 88.95

    This is excessive. Something isn't right with the mount. Because you ran this unguided it has exposed a sidereal tracking issue. It is not tracking at the correct rate. Look at the angles on the pointing errors. These are angles on the sky, not relative to the camera rotation. So the mount is failing to keep up with the earth's rotation, thus its pointing is off more and more east (where things rise, right?) until it has to be resynced. This should be reported to Planewave. They should (will) make it right. It's probably an adjustment.

    Rotation Analysis:

    03:54:33 PA error of 20.4 deg. detected. Correcting...
    03:57:14 PA error of 40.8 deg. detected. Correcting...
    06:02:02 PA error of 162.3 deg. detected. Correcting...
    06:37:28 PA error of 70.8 deg. detected. Correcting...
    08:43:46 PA error of 76.0 deg. detected. Correcting...
    09:19:36 PA error of 56.1 deg. detected. Correcting...

    The rotator is absolutely positively not completing its commanded rotations. For whatever reason, when told to go to a specific mechanical angle, it is not going there. For example:

    03:50:21 Start rotate to PA 255.0 deg (raw rotator angle 171.8)
    ...
    03:54:33 Imager sky position angle is 275.4 deg.
    03:54:33 Rotator mech. position angle is 171.8 deg.
    03:54:33 Within max error tolerance, no re-slew needed.
    03:54:33 PA error of 20.4 deg. detected. Correcting...
    03:54:33 Start rotate to PA 255.0 deg (raw rotator angle 151.4)
    ... autofocus does not touch rotator ...
    03:57:14 Imager sky position angle is 295.8 deg.
    03:57:14 Rotator mech. position angle is 151.4 deg.
    03:57:14 Within max error tolerance, no re-slew needed.
    03:57:14 PA error of 40.8 deg. detected. Correcting...
    03:57:14 Start rotate to PA 255.0 deg (raw rotator angle 110.6)

    The first image of the plan, NGC6992, used the mechanical-sky offset of the rotator from the last run so it thought it needed to go to 171.8 on the rotator in order to get your requested 255 sky PA. It did that. Then it took an image and measured the real PA. It was not 255 , it was 274.4, 20.4 degrees off. Now it has another value for the mechanical versus sky angles, and re-rotates to again try to get the 255 des Sky PA, this time it thinks it needs to go to 151.4 on the rotator. Then it does an autofocus (not touching the rotator!!) and then takes the next image. Once again the PA is not the requested 255 degrees, it is 295.8. The rotator again failed to rotate as commanded. At 09:20 UTC something strange happened:

    09:19:36 PA error of 56.1 deg. detected. Correcting...
    09:19:36 Start rotate to PA 255.0 deg (raw rotator angle 303.4)
    ...
    09:26:18 Imager sky position angle is 142.8 deg.
    09:26:18 Rotator mech. position angle is 303.4 deg.
    ...

    09:38:26 Imager sky position angle is 142.8 deg.
    09:38:26 Rotator mech. position angle is 303.4 deg.
    ... etc


    Is it possible that this group of images does not have a #posang directive? It is happy to see 148 Sky PA yet you have been requesting 255.

    I hope I have explained this clearly enough so that there is no question that the rotator is not working right. I won't learn anything by logging onto the system until these problems are corrected.
    Last edited by Bob Denny; Sep 10, 2018 at 17:09. Reason: remove spurious blank lines
    -- Bob

 

 

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Weather script issue stops ACP imaging
    By Peter Brackenridge in forum Hardware/Software/Driver Topics Not Directly Related to Our Software
    Replies: 2
    Last Post: Jan 19, 2018, 20:30

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •