STX 16803 + MaxIM DL Crashing

Discussion in 'STX and STXL' started by James Pierce, May 18, 2020.

  1. James Pierce

    James Pierce Cyanogen Customer

    Joined:
    May 20, 2019
    Messages:
    40
    About half way through the night, the last few nights my ACP / Maxim / STX 16803 setup has failed. I'm not sure if this is a Maxim DL problem, or a camera problem or both so I'll post here for a start.

    The camera will be working away fine, guiding with the AO and then suddenly a bunch of ACP plans will fail with camera related errors. When I log into my remote machine MaxIm isn't open. If I reopen MaxIm it can't connect to the camera and a power cycle is required.

    After I power cycle the camera, and restart everything, then camera has run through till dawn no problems. If there is a pattern it seems to be when the camera has been working away for a good while. I've been rebuilding my dark library during the day so the camera has been seeing a fair bit of work the last 2-3 days.

    I've just restarted everything now and will head back to bed. Please let me know what other logs and info will be helpful to figure this out!


    In the MaxIm log tonight this is the last ~50 lines.

    13:07:21*4 Started 300.000s 4096x4096 exposure, binned 1x1, ROI (0, 0)
    13:07:41#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:12:24*4 Completed 300.000s 4096x4096 exposure, binned 1x1, ROI (0, 0)
    13:13:20#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:13:21#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:13:24#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:13:25#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:13:27*4 Started 300.000s 4096x4096 exposure, binned 1x1, ROI (0, 0)
    13:13:27#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:13:30#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:15:21#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:15:40#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:15:40#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:15:40#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:15:41#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:15:46#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:15:55#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:16:40#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:16:40#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:16:46#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:18:29*4 Completed 300.000s 4096x4096 exposure, binned 1x1, ROI (0, 0)
    13:19:24*4 Started 300.000s 4096x4096 exposure, binned 1x1, ROI (0, 0)
    13:20:38#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:20:40#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:24:23#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:24:26*4 Completed 300.000s 4096x4096 exposure, binned 1x1, ROI (0, 0)
    13:25:23*4 Started 300.000s 4096x4096 exposure, binned 1x1, ROI (0, 0)
    13:30:25*4 Completed 300.000s 4096x4096 exposure, binned 1x1, ROI (0, 0)
    13:31:54$5 Guider Tracking Stopped
    13:32:29#4 Error -13 starting 5.000s 829x829 exposure, binned 4x4, ROI (98, 98)
    13:32:29$4 Camera Exposure Aborted
    13:34:48#4 Error -13 starting 5.000s 829x829 exposure, binned 4x4, ROI (98, 98)
    13:34:48$4 Camera Exposure Aborted
    13:36:59#4 Error -13 starting 5.000s 2048x2048 exposure, binned 1x1, ROI (1024, 1024)
    13:36:59$4 Camera Exposure Aborted
    13:38:05#4 Error -13 starting 5.000s 829x829 exposure, binned 4x4, ROI (98, 98)
    13:38:05$4 Camera Exposure Aborted
    13:40:07*4 Started 5.000s 2048x2048 exposure, binned 1x1, ROI (1024, 1024)
    13:42:21*4 Completed 5.000s 2048x2048 exposure, binned 1x1, ROI (1024, 1024)
    13:43:23$4 Camera Exposure Aborted
    13:44:51*4 Filter wheel moving to position 0
    13:46:12$4 Camera Exposure Aborted
    13:47:28#4 Error -13 starting 5.000s 1024x1024 exposure, binned 4x4, ROI (0, 0)
    13:47:28$4 Camera Exposure Aborted
    13:47:53#4 Error -13 starting 5.000s 829x829 exposure, binned 4x4, ROI (98, 98)
    13:47:53$4 Camera Exposure Aborted
    13:49:04#4 Error -13 starting 5.000s 829x829 exposure, binned 4x4, ROI (98, 98)
    13:49:04$4 Camera Exposure Aborted
    13:50:56*4 Started 5.000s 2048x2048 exposure, binned 1x1, ROI (1024, 1024)
    13:53:23*4 Completed 5.000s 2048x2048 exposure, binned 1x1, ROI (1024, 1024)
    13:54:31$4 Camera Exposure Aborted
    13:55:25$4 Camera Exposure Aborted
     
  2. Doug

    Doug Staff Member

    Joined:
    Sep 25, 2014
    Messages:
    6,774
  3. James Pierce

    James Pierce Cyanogen Customer

    Joined:
    May 20, 2019
    Messages:
    40
    Oh I wish it was that simple... With all the problems I've had with my 340m-AllSky I've set, and re-confirmed all those USB sleep settings many times... Re-checked now. Definitely not the cause.
     
  4. James Pierce

    James Pierce Cyanogen Customer

    Joined:
    May 20, 2019
    Messages:
    40
    I've just realized the log rolled over and there is some more useful info in the section from the 18th... I'll put it together and try and annotate a little so that it's a bit easier to hopefully spot what is going on.


    At this point ACP / Maxim is happily imaging 300s Subs...

    13:07:21*4 Started 300.000s 4096x4096 exposure, binned 1x1, ROI (0, 0)
    13:07:41#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:12:24*4 Completed 300.000s 4096x4096 exposure, binned 1x1, ROI (0, 0)
    Sub Done...

    13:13:20#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:13:21#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:13:24#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:13:25#5 Error - Error in plugin callback (400) - Could not activate relay - already active

    13:13:27*4 Started 300.000s 4096x4096 exposure, binned 1x1, ROI (0, 0)
    13:13:27#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:13:30#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:15:21#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:15:40#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:15:40#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:15:40#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:15:41#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:15:46#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:15:55#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:16:40#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:16:40#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:16:46#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:18:29*4 Completed 300.000s 4096x4096 exposure, binned 1x1, ROI (0, 0)
    Sub Done...

    13:19:24*4 Started 300.000s 4096x4096 exposure, binned 1x1, ROI (0, 0)
    13:20:38#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:20:40#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:24:23#5 Error - Error in plugin callback (400) - Could not activate relay - already active
    13:24:26*4 Completed 300.000s 4096x4096 exposure, binned 1x1, ROI (0, 0)
    Sub Done...

    13:25:23*4 Started 300.000s 4096x4096 exposure, binned 1x1, ROI (0, 0)
    13:30:25*4 Completed 300.000s 4096x4096 exposure, binned 1x1, ROI (0, 0)
    Sub Done...

    The next sequence is a periodic autofocus (which fails...) It tries to do an exposure to confirm pointing (the 4x4 bin) and then the 2048x2048 sub frames are autofocus.

    13:31:54$5 Guider Tracking Stopped
    13:32:29#4 Error -13 starting 5.000s 829x829 exposure, binned 4x4, ROI (98, 98)
    13:32:29$4 Camera Exposure Aborted
    13:34:48#4 Error -13 starting 5.000s 829x829 exposure, binned 4x4, ROI (98, 98)
    13:34:48$4 Camera Exposure Aborted
    13:36:59#4 Error -13 starting 5.000s 2048x2048 exposure, binned 1x1, ROI (1024, 1024)
    13:36:59$4 Camera Exposure Aborted
    13:38:05#4 Error -13 starting 5.000s 829x829 exposure, binned 4x4, ROI (98, 98)
    13:38:05$4 Camera Exposure Aborted
    13:40:07*4 Started 5.000s 2048x2048 exposure, binned 1x1, ROI (1024, 1024)
    13:42:21*4 Completed 5.000s 2048x2048 exposure, binned 1x1, ROI (1024, 1024)
    13:43:23$4 Camera Exposure Aborted
    13:44:51*4 Filter wheel moving to position 0
    13:46:12$4 Camera Exposure Aborted
    13:47:28#4 Error -13 starting 5.000s 1024x1024 exposure, binned 4x4, ROI (0, 0)
    13:47:28$4 Camera Exposure Aborted
    13:47:53#4 Error -13 starting 5.000s 829x829 exposure, binned 4x4, ROI (98, 98)
    13:47:53$4 Camera Exposure Aborted
    13:49:04#4 Error -13 starting 5.000s 829x829 exposure, binned 4x4, ROI (98, 98)
    13:49:04$4 Camera Exposure Aborted
    13:50:56*4 Started 5.000s 2048x2048 exposure, binned 1x1, ROI (1024, 1024)
    13:53:23*4 Completed 5.000s 2048x2048 exposure, binned 1x1, ROI (1024, 1024)
    13:54:31$4 Camera Exposure Aborted
    13:55:25$4 Camera Exposure Aborted

    This start / exit / start / exit MaxIm was not me. I'm not sure if Maxim is restarting itself to try and recover, or if ACP is causing this.

    13:58:18*2 ____________ 2020-05-18 ____________
    13:58:18*1 MaxIm DL Version 6.20 started on DESKTOP-S6BMQC5
    13:58:20*1 MaxIm DL Version 6.20 exited
    13:58:33*1 MaxIm DL Version 6.20 started on DESKTOP-S6BMQC5
    13:58:35*1 MaxIm DL Version 6.20 exited
    13:58:49*1 MaxIm DL Version 6.20 started on DESKTOP-S6BMQC5
    13:58:50*1 MaxIm DL Version 6.20 exited
    13:59:04*1 MaxIm DL Version 6.20 started on DESKTOP-S6BMQC5
    13:59:06*1 MaxIm DL Version 6.20 exited
    13:59:21*1 MaxIm DL Version 6.20 started on DESKTOP-S6BMQC5
    13:59:22*1 MaxIm DL Version 6.20 exited
    13:59:36*1 MaxIm DL Version 6.20 started on DESKTOP-S6BMQC5
    13:59:38*1 MaxIm DL Version 6.20 exited
    13:59:53*1 MaxIm DL Version 6.20 started on DESKTOP-S6BMQC5
    13:59:54*1 MaxIm DL Version 6.20 exited

    Now enter me ... manually opening Maxim

    14:34:43*1 MaxIm DL Version 6.20 started on DESKTOP-S6BMQC5

    Trying to open the camera control and re-connect to the camera.

    14:35:07>6 View, Camera Control Window
    14:35:38*3 Connecting cameras - thread ID 1480
    14:35:53>6 View, Log Window
    14:35:59#3 Failed to connect to camera 1 "SBIG w/ AO" (CCDPlugAO7.dll), error -1573720354

    I power cycle the camera, and then try to re-connect.

    14:37:39*3 Connecting cameras - thread ID 1480
    14:37:40$3 Connected to camera 1 "SBIG w/ AO" (CCDPlugAO7.dll v6.20.0.0)
    14:37:40$3 Connected to guide chip of "SBIG w/ AO" (CCDPlugAO7.dll v6.20.0.0)
    14:37:40#3 Failed to connect to filter wheel 1 "SBIG AO w/FW" (CCDPlugAO7.dll), error 1001
    14:37:40$3 Disconnected from guide chip of "SBIG w/ AO"
    14:37:41$3 Disconnected from camera 1 "SBIG w/ AO"

    It worked, except for the filter wheel, perhaps I was a bit too quick and it was still powering up etc. A second attempt works fine.

    14:37:49*3 Connecting cameras - thread ID 1480
    14:37:50$3 Connected to camera 1 "SBIG w/ AO" (CCDPlugAO7.dll v6.20.0.0)
    14:37:50$3 Connected to guide chip of "SBIG w/ AO" (CCDPlugAO7.dll v6.20.0.0)
    14:37:50$3 Connected to filter wheel 1 "SBIG AO w/FW" (CCDPlugAO7.dll v6.20.0.0)

    I disconnect and shutdown Maxim so that ACP starts from a clean state (it automatically starts everything when in it's startup observatory scripts)

    14:40:14$3 Disconnected from filter wheel 1 "SBIG AO w/FW"
    14:40:14$3 Disconnected from guide chip of "SBIG w/ AO"
    14:40:15$3 Disconnected from camera 1 "SBIG w/ AO"
    14:40:15*1 MaxIm DL Version 6.20 exited

    ACP Starts up cleanly, connects to everything and begins with an Autofocus sequence before imaging the rest of the night.

    14:43:04*1 MaxIm DL Version 6.20 started on DESKTOP-S6BMQC5
    14:43:06*3 Connecting cameras - thread ID 9476
    14:43:07$3 Connected to camera 1 "SBIG w/ AO" (CCDPlugAO7.dll v6.20.0.0)
    14:43:07$3 Connected to guide chip of "SBIG w/ AO" (CCDPlugAO7.dll v6.20.0.0)
    14:43:07$3 Connected to filter wheel 1 "SBIG AO w/FW" (CCDPlugAO7.dll v6.20.0.0)
    14:44:37*4 Filter wheel moving to position 0
    14:45:45*4 Started 5.000s 2048x2048 exposure, binned 1x1, ROI (1024, 1024)
    14:45:53*4 Completed 5.000s 2048x2048 exposure, binned 1x1, ROI (1024, 1024)
    14:46:13*4 Started 5.000s 2048x2048 exposure, binned 1x1, ROI (1024, 1024)
    14:46:20*4 Completed 5.000s 2048x2048 exposure, binned 1x1, ROI (1024, 1024)
    14:46:41*4 Started 5.000s 2048x2048 exposure, binned 1x1, ROI (1024, 1024)
    14:46:42>6 Zoom to 12.5%, CCD Image 2
     
  5. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    3,277
    A couple of thoughts:
    1. Is ACP controlling a power switch like a Digital Loggers device? If so, your camera may not be fully finished its self-test before launching MaxIm. You may need a delay in your startup script.
    2. Are Windows update or inventory tasks running overnight?
     
  6. James Pierce

    James Pierce Cyanogen Customer

    Joined:
    May 20, 2019
    Messages:
    40
    1) It is, and there is a 20 second delay built in. This is also happening hours and hours after startup, not straight away.
    2) Nothing in the event log for the last few days apart from virus definitions. My active window is set to try and stop windows interference, granted it largely seems to ignore that anyway.
     
  7. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    3,277
    1. Ok good.
    2. Understood.

    It might be useful for us to have a look at the MaxIm log. View... Log Window. Right Click, turn on Time Stamps and Debug Messages (at least temporarily).
    You can find the logs somewhere like this:
    C:\Users\James\Documents\MaxIm DL 6\Log
    The filenames are like 20200518.log
     
  8. James Pierce

    James Pierce Cyanogen Customer

    Joined:
    May 20, 2019
    Messages:
    40
    I've added the debug message in now, do you want the older logs from the past few days when this has happened ? (above is a snippet from that)
     
  9. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    3,277
    Yes please. It would be great if you could zip up a bunch (say 5-10 logs) and attach with [Upload a File] to the lower right.
    Also, zip up and attach your MaxIm settings folder and its subdirectories. Usually found here:
    C:\Users\James\Documents\MaxIm DL 6\Settings
     
  10. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    3,277
    Also, what mount is it?
     
  11. James Pierce

    James Pierce Cyanogen Customer

    Joined:
    May 20, 2019
    Messages:
    40
    Settings directory attached as a zip (logs are in there also)

    You'll see the same pattern as above in the 20200516 log also @ 12:54:20 ... again I intervene to check and restart, but not until 17:37:07

    Oh and the mount is a Paramount MX+
     

    Attached Files:

  12. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    3,277
    Thanks, we'll take a look.
     
  13. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    3,277
    Well... there's an additional possibility you hadn't considered.
    Whoever set up MaxIm missed some important configuration steps.

    In the logs, lines like:
    15:01:40$5 Warning - Error getting guider imageError -
    Error computing arc seconds per pixel
    Focal length invalid or inaccessible"
    That's basically telling you that a critical step has been missed.
    Edit... Preferences. Site and Optics. Set up lat, long, elevation, and the parameters of your optics, and if using STX guider 0.7x reducer for guide scope; or for SC-3, 1x.
    You might want to set up the Edit... Preferences. FITS Header tab as well.

    There may be additional issues, but you need to resolve this first.
     
  14. James Pierce

    James Pierce Cyanogen Customer

    Joined:
    May 20, 2019
    Messages:
    40
    Ah that part will be my fault. I had to downgrade recently from 6.21 to 6.20 because the new AO behaviour in 6.21 causes lots of problems if you loose a star for even a split second. I'll sort this bit out now.
     
  15. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    3,277
    Since guiding doesnt work if you don't have these settings, I doubt AO would work either. So downgrading may be unnecessary.
     
  16. Bob Denny

    Bob Denny Cyanogen Customer

    Joined:
    Oct 12, 2014
    Messages:
    793
    Location:
    DC-3 Dreams, SP, Mesa, Arizona +1 480 396 9700
    James - - One way to avoid surprise changes on downgrading is to save the Configuration, then after downgrading, restore it. I never design and/or test downgrades, and I'm going to guess that Diffraction doesn't either. Just sayin'...
     
  17. James Pierce

    James Pierce Cyanogen Customer

    Joined:
    May 20, 2019
    Messages:
    40
    Guiding has been working flawlessly without any of that configured! Of course ACP is selecting stars etc.

    I did of course have all that configured in the past, just missed it on the downgrade.
     
  18. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    3,277
    Not sure how you did the "downgrade", but the site and optical parameters are in the Documents\MaxIm DL 6\Settings folder, and that is preserved during install/uninstalls.
    Bob's advice is solid about Configurations.

    I'd like to learn more about "the new AO behaviour in 6.21 causes lots of problems if you loose a star for even a split second".
    Would be great if you could provide any additional info.
     
  19. James Pierce

    James Pierce Cyanogen Customer

    Joined:
    May 20, 2019
    Messages:
    40
    Downgrade = Uninstall 6.21 and install 6.20

    In 6.20 if the star dims for some reason the guider does nothing, and wait for the star to reappear. If it does then it continues to guide happily.

    In 6.21 if the star dims for some reason there seems to be some logic that it goes looking for the star, once the mount has been bumped a couple of times it ends up out of the tiny guiding field and the problem cascades ruining the exposure. It's an issue with long subs and thin high cloud, or poor seeing.
     
  20. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    3,277
    Thanks. This is helpful.
     

Share This Page