Page 2 of 2 FirstFirst 12
Results 11 to 15 of 15
  1. #11

    Default

    Howdy Bob,
    I could do the team viewer thing if you were interested. LaVor

  2. #12
    Join Date
    Oct 2005
    Location
    Mesa, AZ
    Posts
    33,216

    Default

    Ah, OK, this helps.

    03:32:34 **Calibration failed. Original image saved.
    03:32:34 **MaxIm reports No suitable calibration groups were found.

    For now, turn off Preferences > Imaging tab, Auto calibrate pointing exposures. You probably don't have cal frames with the right binning (3 or 4) and anyway the plate solve failures aren't due to image quality issues:

    03:32:36 Plate-solve pointing image.
    [... some other stuff]
    03:34:34 ** No matching stars found. Check your estimated center-point RA/Dec, and your image scaling and quality.
    03:34:35 Attempting all-sky plate solution (time-consuming)...
    03:35:21 All-sky solution successful!
    03:35:22 Scope: 23:20:38 62° 24' 14"
    03:35:22 Actual: 23:04:00 61° 48' 45"
    03:35:22 Pointing error is 121.9 arcmin.
    03:35:22 [sync] pointing model updated


    This is the issue. Initially your scope was pointing over two degrees off. Maybe after ACP did this sync it would have run OK as the Sync will correct the pointing in the mount (at least in the local area, maybe the whole sky!). I would also suggest you turn off the ACP Pointing corrector. It may have some bad mapping points in it. Run with those two things turned off and see what happens.
    -- Bob

  3. #13

    Default

    OK. I will let you know. Thanks

  4. #14

    Default

    Howdy again,
    Still no luck. My logs still read the same and I have adjusted the settings that you mentioned. The funny thing is when the program shuts down and I go to the console with the sidereal tracking on and take an image from the guide camera, I have a nice, mag9 star on the image and the calibration, whether I do it myself, or have ACP do it, I get nice, pretty "L's" every time. That's why I think it's a setting. But I am baffled. LaVor PS: I think that I will try a separate guide camera tomorrow night. It doesn't make sense, but..

  5. #15
    Join Date
    Oct 2005
    Location
    Mesa, AZ
    Posts
    33,216

    Default

    Dang it.

    03:35:53 (guide star SNR=68.1 X=289 Y=45)
    03:35:53 **Script Error (Tracking has been stopped)**
    03:35:54 Source: MaxIm DL 6
    03:35:54 Message: Internal application error.

    I don't know what this means. But try to take a locate image then Track in MaxIM by itself. Will that work?

    Also, turn off AutoCalibration in ACP until you get some calibration frames loaded into MaxIm.
    -- Bob

 

 

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. Telescope shows Stopped when actually tracking
    By Dean Salman in forum Hardware/Software/Driver Topics Not Directly Related to Our Software
    Replies: 3
    Last Post: May 22, 2015, 18:39
  2. Tracking stopped after mount flip [cable snag]
    By Larry Owings in forum Hardware/Software/Driver Topics Not Directly Related to Our Software
    Replies: 9
    Last Post: Sep 27, 2011, 15:10
  3. DawnFlats script stopped
    By ebenson in forum Pre-Sales Technical Questions and Help
    Replies: 1
    Last Post: Jan 6, 2011, 15:05

Posting Permissions

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