Results 1 to 5 of 5

Hybrid View

  1. #1
    Join Date
    Jun 2015
    Posts
    728

    Default Debug Mount versus FocusMax Error

    Hi,

    I am having a problem where the system runs well for say 4, 5, 6h and then there is a pointing error in one of the runs.

    This is after I disabled my rotator (camera manually positioned to zero rotation. I do not need to pick stars to guide properly).

    A log is enclosed.

    In the log the focusing goes astray and the plate solve failed, I assume because of a pointing error. The first few times the all sky solution succeeds, but I think the mount does not synch since the error is > 5 Degrees (APCC criteria).

    If I park the scope the DEC is off about 30 DEG.

    If I manually correct the DEC and run the lost scope script, it corrects with an eror of 1357.9 arc'.

    Not sure why this is happening:


    • My initial worry was a mount error and I checked all the cables and they are loose... and the thing tracks precisely for 4-5h at the start of the night.
    • Maybe there is something in FocuxMax I am missing when I changed the rotator. I will ask Steve.


    I will call George at AstroPhysics (This is a Mach 1 mount)... but they were busy yesterday.

    Any ideas anyone?

    JY

    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

    Steve from FocusMax's comment:

    Jerry--
    Are you using a pointing model such as TPoint or APC in your system? A short slew of 5 degree resulted in a large pointing error of 400 arc-min (6.7 degree).
    09:13:02 02:13:02 ...Current pointing error = 400.4850 (arc-min)

    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

    After this, on checking ACP settings I got a notice:

    You do not have a rotator configured but you have Guide Sensor Rotated Internal SBIG

    Could this be a factor?
    Attached Files Attached Files

  2. #2
    Join Date
    Oct 2005
    Location
    Mesa, AZ
    Posts
    29,670

    Default

    This entire run looks bad. As soon as FocusMax started it failed to plate solve to remember its starting position accurately:

    09:07:01 02:07:01 Current pointing (Topo) RA: 03:03:28.9 Dec: +64:49:33.0
    09:07:01 02:07:01 Current Alt: 62.29 Az: 6.32
    09:07:01 02:07:01 Taking image and plate solving
    09:07:01 02:07:01 Taking pointing exposure
    ...
    09:08:20 02:08:20 Plate solve failed


    Then it tried to do an all-sky plate solve because it thinks the mount is lost:

    09:08:20 02:08:20 Starting PinPoint All-sky plate solve
    09:09:47 02:09:47 Plate solved
    09:09:47 02:09:47 ...Image bin = 2
    09:09:48 02:09:48 ...Roll angle = 1.01
    09:09:48 02:09:48 ...Plate scale = 2.44V 2.44H
    09:09:49 02:09:49 ...Plate scale unbinned = 1.22V 1.22H
    09:09:49 02:09:49 ...Alt = 55.87 Az = 3.3
    09:09:49 02:09:49 ...Plate(Topo) RA: 03:03:57.0 Dec: +71:29:53.2
    09:09:49 02:09:49 ...Plate(J2000) RA: 03:01:52.4 Dec: +71:25:10.2
    09:09:49 02:09:49 ...Image X,Y: 3953, -7782
    09:09:49 02:09:49 ...Full frame (1x1 bin) X,Y: 8326, -15556
    09:09:49 02:09:49 ...Star is not within image boundary

    Yep! Huge (10 degree) mount pointing error in Dec. Fix it with a sync:

    09:09:49 02:09:49 Sync Telescope (Topo) RA = 03:03:57.0 Dec = +71:29:53.2

    Now it picks a star to focus with

    09:09:50 02:09:50 Field search: 20 x 20 degrees
    ...
    09:09:52 02:09:52 Using 4.50 mag star at RA 03:51:27.3 Dec +65:35:08.2 (Topo) Alt: 59.9

    Plate solve to center the chosen star


    09:10:22 02:10:22 Starting PinPoint plate solve
    09:11:23 02:11:22 Plate solve failed

    Failed again! Do an all-sky solve

    09:11:23 02:11:23 Starting PinPoint All-sky plate solve
    09:13:01 02:13:01 Plate solved
    09:13:01 02:13:01 ...Image bin = 2
    09:13:01 02:13:01 ...Roll angle = 1.05
    09:13:01 02:13:01 ...Plate scale = 2.44V 2.44H
    09:13:02 02:13:02 ...Plate scale unbinned = 1.22V 1.22H
    09:13:02 02:13:02 ...Alt = 54.17 Az = 8.77
    09:13:02 02:13:02 ...Plate(Topo) RA: 03:52:01.1 Dec: +72:15:35.4
    09:13:02 02:13:02 ...Plate(J2000) RA: 03:49:42.9 Dec: +72:12:02.9
    09:13:02 02:13:02 ...Image X,Y: 1097, -5257
    09:13:02 02:13:02 ...Full frame (1x1 bin) X,Y: 2614, -10506
    09:13:02 02:13:02 ...Star is not within image boundary
    09:13:02 02:13:02 ...Max pointing error = 3 (arc-min)
    09:13:02 02:13:02 ...Current pointing error = 400.4850 (arc-min)

    At this point it's pointless for me to continue to analyze this log. THe mount is clearly malfunctioning. Maybe the Dec axis is completely stuck at +71-ish degrees.
    -- Bob

  3. #3
    Join Date
    Jun 2015
    Posts
    728

    Default

    Quote Originally Posted by Bob Denny View Post
    This entire run looks bad. As soon as FocusMax started it failed to plate solve to remember its starting position accurately:

    09:07:01 02:07:01 Current pointing (Topo) RA: 03:03:28.9 Dec: +64:49:33.0
    09:07:01 02:07:01 Current Alt: 62.29 Az: 6.32
    09:07:01 02:07:01 Taking image and plate solving
    09:07:01 02:07:01 Taking pointing exposure
    ...
    09:08:20 02:08:20 Plate solve failed


    Then it tried to do an all-sky plate solve because it thinks the mount is lost:

    09:08:20 02:08:20 Starting PinPoint All-sky plate solve
    09:09:47 02:09:47 Plate solved
    09:09:47 02:09:47 ...Image bin = 2
    09:09:48 02:09:48 ...Roll angle = 1.01
    09:09:48 02:09:48 ...Plate scale = 2.44V 2.44H
    09:09:49 02:09:49 ...Plate scale unbinned = 1.22V 1.22H
    09:09:49 02:09:49 ...Alt = 55.87 Az = 3.3
    09:09:49 02:09:49 ...Plate(Topo) RA: 03:03:57.0 Dec: +71:29:53.2
    09:09:49 02:09:49 ...Plate(J2000) RA: 03:01:52.4 Dec: +71:25:10.2
    09:09:49 02:09:49 ...Image X,Y: 3953, -7782
    09:09:49 02:09:49 ...Full frame (1x1 bin) X,Y: 8326, -15556
    09:09:49 02:09:49 ...Star is not within image boundary

    Yep! Huge (10 degree) mount pointing error in Dec. Fix it with a sync:

    09:09:49 02:09:49 Sync Telescope (Topo) RA = 03:03:57.0 Dec = +71:29:53.2

    Now it picks a star to focus with

    09:09:50 02:09:50 Field search: 20 x 20 degrees
    ...
    09:09:52 02:09:52 Using 4.50 mag star at RA 03:51:27.3 Dec +65:35:08.2 (Topo) Alt: 59.9

    Plate solve to center the chosen star


    09:10:22 02:10:22 Starting PinPoint plate solve
    09:11:23 02:11:22 Plate solve failed

    Failed again! Do an all-sky solve

    09:11:23 02:11:23 Starting PinPoint All-sky plate solve
    09:13:01 02:13:01 Plate solved
    09:13:01 02:13:01 ...Image bin = 2
    09:13:01 02:13:01 ...Roll angle = 1.05
    09:13:01 02:13:01 ...Plate scale = 2.44V 2.44H
    09:13:02 02:13:02 ...Plate scale unbinned = 1.22V 1.22H
    09:13:02 02:13:02 ...Alt = 54.17 Az = 8.77
    09:13:02 02:13:02 ...Plate(Topo) RA: 03:52:01.1 Dec: +72:15:35.4
    09:13:02 02:13:02 ...Plate(J2000) RA: 03:49:42.9 Dec: +72:12:02.9
    09:13:02 02:13:02 ...Image X,Y: 1097, -5257
    09:13:02 02:13:02 ...Full frame (1x1 bin) X,Y: 2614, -10506
    09:13:02 02:13:02 ...Star is not within image boundary
    09:13:02 02:13:02 ...Max pointing error = 3 (arc-min)
    09:13:02 02:13:02 ...Current pointing error = 400.4850 (arc-min)

    At this point it's pointless for me to continue to analyze this log. The mount is clearly malfunctioning. Maybe the Dec axis is completely stuck at +71-ish degrees.
    Thanks, this is helpful... maybe there is some binding that comes on at the high DEC.... I'll ask George and take a good look.

    Should I change the guiding parameter to no rotator... will I still get all the automatic benefits???? auto cal?

  4. #4
    Join Date
    Oct 2005
    Location
    Mesa, AZ
    Posts
    29,670

    Default

    Should I change the guiding parameter to no rotator...
    No leave the guiding alone. It has to send the angles to MaxIm anyway.
    -- Bob

  5. #5
    Join Date
    Jun 2015
    Posts
    728

    Default

    Quote Originally Posted by Bob Denny View Post
    No leave the guiding alone. It has to send the angles to MaxIm anyway.
    Thanks, working fine now. I went over the mount in detail with George and there seem to be no mechanical problems. He said the most likely culprit is some sort of spurious input... their logs are very difficult even if you know the time of the event.

    I removed the offending object from the observing list for tonight... my thought and his was is that the database might be corrupted... we re-calibrated the mount from scratch (at least I did). Maybe there is a bad character in one of the RAs or DECs....

    Steve has nothing much to offer... they had some problems with recent FM versions but I am up to date....

    I am going to run it and see it it recurs... not much more I can do.

    Thnaks for the support....

 

 

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. Observation interrupted, ACP Application error and 10Micron mount error..
    By Roelof Platenkamp in forum Hardware/Software/Driver Topics Not Directly Related to Our Software
    Replies: 3
    Last Post: Mar 30, 2020, 17:05
  2. FocusMax Error
    By Robert Capon in forum FocusMax and PoleAlignMax Questions
    Replies: 5
    Last Post: Apr 13, 2014, 00:10

Posting Permissions

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