Page 1 of 7 1234567 LastLast
Results 1 to 10 of 61

Hybrid View

  1. #1
    Join Date
    Nov 2005
    Location
    Muurame, Finland
    Posts
    169

    Default Camera Hangs and Stops Plan

    Happy New Year 2020 from Finland!

    This happened last night. Any idea what was wrong?

    23.04.25 Starting run for plan comets_20200101.txt...
    23.04.26 Comet elements for CK17T020 --> RA=03:25:34 Dec=55° 11' 58" (J2000)
    23.04.27 ==== Starting target CK17T020 ====
    23.04.27 ;
    23.04.27 ; Comets 1.12.2019
    23.04.27 ; C/2017 T2 (PANSTARRS)
    23.04.27 ; C/2018 N2 (ASASSN)
    23.04.27 ; 260P/McNaught
    23.04.27 (turning tracking on for live image(s))
    23.04.29 Comet elements for CK17T020 --> RA=03:25:34 Dec=55° 11' 58" (J2000)
    23.04.29 Comet elements for CK17T020 --> RA=03:25:34 Dec=55° 11' 58" (J2000)
    23.04.29 Start slew to CK17T020...
    23.04.41 Start rotate to PA 0.0 deg (raw rotator angle 195.6)
    23.04.41 (wait for slew to complete)
    23.05.19 (slew complete)
    23.05.19 (request plan-start pointing update)
    23.05.19 Ready for CK17T020 (# 1 of 3 in set 1)
    23.05.19 CK17T020 will be repeated 10 times.
    23.05.21 === Starting target repeat 7 of 10 ===
    23.05.22 Selecting L filter (0) for imaging
    23.05.22 Pointing update: Wait and flip if within 120 sec of flip point
    23.05.22 [flip check: Tn=120s HAc=14699s GW=T HAz=14819s DWz=T WF=no]
    23.05.22 Doing auto-center...
    23.05.22 Switching from Ha to L filter for pointing exposure
    23.05.22 Focus change of -1 steps required
    23.05.25 (taking 5 sec. exposure, L filter, binning = 4)
    23.05.25 (using Raw readout mode)
    23.43.38 **Script Error (Tracking has been stopped)**
    23.43.39 Source: ACP
    23.43.39 Message: The script was aborted.
    23.43.39 Location: line 1533 column 33.
    Arto Oksanen arto.oksanen at jklsirius.fi
    Verkkoniementie 30, FI-40950 Muurame, Finland

  2. #2
    Join Date
    Nov 2005
    Location
    Virgil, NY
    Posts
    4,938

    Default

    Hi Arto,

    It's not easy to tell what went wrong from this part of log.

    You're at the point of taking a pointing exposure, which may or may not have started. In any case note that 38 minutes went by between the last log entry while preparing to take that pointing image (logged at AcquireSupport line ~3348) and starting the exposure (logged at line ~3555). The code in between includes a lot of guider setup, but there's no logged lines about guiding. There's no log entry for "starting exposure." If nothing was wrong in between, it would have taken a few microseconds to traverse that code, not 38 minutes. It looks like your 5 second exposure never started.

    I'm sorry I can't do more to find the cause of this problem. If it's just a one-off thing, maybe you'll never see this error again. Were other runs last night successful either before or after this?

    The error statements in the log at the end comes from AcquireImages (line 1533), even though the actual fault occurred somewhere in AcquireSupport. (My line numbers are a bit different, but that's probably the call to SUP.UpdatePointing.)

    Yes, Happy New Year. I hope it's a better, less stressful one for the world this year.
    Dick
    www.VirgilObservatory.us
    Pier-mounted Meade 12-inch SCT "classic"
    w. focal reducer to f/5.3 ~ FL 1630mm
    Optec TCF-S focuser
    SBIG CFW-8A and ST7-XME
    FOV ~ 15' x 10'
    H-alpha, BVRI, RGB & Clear filters
    MaxIm and, of course, ACP!
    AAVSO Code: BRIC

  3. #3
    Join Date
    Nov 2005
    Location
    Muurame, Finland
    Posts
    169

    Default

    Thanks Dick!

    It happened couple of times last night, but most runs competed with no problems. I am wondering what happens if the user does not realize that the script has jammed. Here is another example:

    03.00.57 === Starting target repeat 1 of 10 ===
    03.01.00 Selecting L filter (0) for imaging
    03.01.00 Pointing update: Wait and flip if within 120 sec of flip point
    03.01.00 [flip check: Tn=120s HAc=43064s GW=T HAz=43184s DWz=T WF=no]
    03.01.00 Doing auto-center...
    03.01.00 (taking 5 sec. exposure, L filter, binning = 4)
    03.01.00 (using Raw readout mode)
    03.01.00 (starting exposure)
    03.01.09 (exposure complete)
    03.01.23 (exposure complete and image downloaded)
    03.01.24 Image finished
    03.01.24 Plate-solve pointing image.
    03.01.24 6 image stars found
    03.01.25 1575 catalog stars found
    03.01.25 ** No matching stars found. Check your estimated center-point RA/Dec, and your image scaling and quality.
    03.01.25 Start slew to offset...
    03.01.38 (wait for slew to complete)
    03.01.42 (slew complete)
    03.01.42 (taking 5 sec. exposure, L filter, binning = 4)
    03.01.42 (using Raw readout mode)
    03.03.13 **Script Error (Tracking has been stopped)**
    03.03.14 Source: ACP
    03.03.21 Message: The script was aborted.
    03.03.21 Location: line 1533 column 33.


    Maybe there should be some timeout logic in the exposure start? What happens between "(using Raw readout mode)" and "(starting exposure)"?

    arto
    Arto Oksanen arto.oksanen at jklsirius.fi
    Verkkoniementie 30, FI-40950 Muurame, Finland

  4. #4
    Join Date
    Nov 2005
    Location
    Virgil, NY
    Posts
    4,938

    Default

    Not much to add here. Looks again like you got stuck again in a pointing exposure limbo, this time after about 90 seconds. You know, MaxIm is in between ACP and the camera. Perhaps there's a flaky (USB?) connection from the computer to the camera, one that's mostly connected but sometimes may not be quite secure enough?
    Dick
    www.VirgilObservatory.us
    Pier-mounted Meade 12-inch SCT "classic"
    w. focal reducer to f/5.3 ~ FL 1630mm
    Optec TCF-S focuser
    SBIG CFW-8A and ST7-XME
    FOV ~ 15' x 10'
    H-alpha, BVRI, RGB & Clear filters
    MaxIm and, of course, ACP!
    AAVSO Code: BRIC

  5. #5
    Join Date
    Nov 2005
    Location
    Muurame, Finland
    Posts
    169

    Default

    I agree, but if there is problem connecting the camera I would see some error also in MaxImDL. Right? The problem kind of fixes itself just by aborting the script and running it again.

    arto
    Arto Oksanen arto.oksanen at jklsirius.fi
    Verkkoniementie 30, FI-40950 Muurame, Finland

  6. #6
    Join Date
    Nov 2005
    Location
    Muurame, Finland
    Posts
    169

    Default

    I looked the code (AccuireSupport.wsc) and found that this is the only place where the script can be in a loop:

    ' Here we wait for the exposure to actually start. If the camera has RBI pre-flash
    ' this could be a significant time! We watch the camera status until it is idle or
    ' in one of the "exposing" states. Starts with 2=Idle, then 9=Waiting, then 3/11/12
    ' (one of the exposing)
    '
    CamStat = Camera.CameraStatus
    If ActInterval > 1.0 Then ' Avoid timing hole for really short exposures
    '' Trace "[tkpic] StartWait - STAT = " & CamStat
    While CamStat <> 3 And CamStat <> 11 And CamStat <> 12 ' Any of the non-exposing status
    '' Trace "[tkpic] InitialWait - STAT = " & CamStat
    Util.WaitForMilliseconds 500
    CamStat = Camera.CameraStatus
    Wend
    End If
    Console.PrintLine " (starting exposure)"
    I will add some debugging console output inside the loop.

    arto
    Last edited by Arto Oksanen; Jan 2, 2020 at 07:44.
    Arto Oksanen arto.oksanen at jklsirius.fi
    Verkkoniementie 30, FI-40950 Muurame, Finland

  7. #7
    Join Date
    Nov 2005
    Location
    Virgil, NY
    Posts
    4,938

    Default

    Yes, but...

    Thats a useful thing to do, and it’s the logical place where there could be an extended wait. It may reveal the secret. I think, though, you’ll find that the trouble is somewhere else — there’s still no “starting exposure” in the log, which must come first.
    Dick
    www.VirgilObservatory.us
    Pier-mounted Meade 12-inch SCT "classic"
    w. focal reducer to f/5.3 ~ FL 1630mm
    Optec TCF-S focuser
    SBIG CFW-8A and ST7-XME
    FOV ~ 15' x 10'
    H-alpha, BVRI, RGB & Clear filters
    MaxIm and, of course, ACP!
    AAVSO Code: BRIC

  8. #8
    Join Date
    Nov 2005
    Location
    Muurame, Finland
    Posts
    169

    Default

    "(Starting exposure)" is not displayed until after the while loop. So I am guessing that the camera status was something else than 3/11/12.

    arto
    Arto Oksanen arto.oksanen at jklsirius.fi
    Verkkoniementie 30, FI-40950 Muurame, Finland

  9. #9
    Join Date
    Nov 2005
    Location
    Virgil, NY
    Posts
    4,938

    Default

    Sorry, I did not have the code in front of me. Your plan to add a print line will show you what you’re looking for.
    Dick
    www.VirgilObservatory.us
    Pier-mounted Meade 12-inch SCT "classic"
    w. focal reducer to f/5.3 ~ FL 1630mm
    Optec TCF-S focuser
    SBIG CFW-8A and ST7-XME
    FOV ~ 15' x 10'
    H-alpha, BVRI, RGB & Clear filters
    MaxIm and, of course, ACP!
    AAVSO Code: BRIC

  10. #10
    Join Date
    Nov 2005
    Location
    Muurame, Finland
    Posts
    169

    Default

    No script hangs with the added print line:

    21.32.41 Imaging to CK17T020-S001-R002-C001-L
    21.32.41 (taking 60 sec. exposure, L filter, binning = 2)
    21.32.41 (using Raw readout mode)
    21.32.41 (InitialWait - STAT = 2)
    21.32.42 (InitialWait - STAT = 6)
    21.32.43 (InitialWait - STAT = 6)
    21.32.43 (starting exposure)


    Here are the status codes from the MaxImDL documentation:


    CCDCamera.CameraStatus
    csNoCamera (0) : Camera is not connected
    csError (1) : Camera is reporting an error
    csIdle (2) : Camera is connected but inactive
    csExposing (3) : Camera is exposing a light image
    csReading (4) : Camera is reading an image from the sensor array
    csDownloading (5) : Camera is downloading an image to the computer
    csFlushing (6) : Camera is flushing the sensor array
    csWaitTrigger (7) : Camera is waiting for a trigger signal
    csWaiting (8) : Camera Control Window is waiting for MaxIm DL to be ready to accept an image
    csDelay (9) : Camera Control is waiting for it to be time to acquire next image
    csExposingAutoDark (10) : Camera is exposing a dark needed by Simple Auto Dark
    csExposingBias (11) : Camera is exposing a Bias frame
    csExposingDark (12) : Camera is exposing a Dark frame
    csExposingFlat (13) : Camera is exposing a Flat frame
    csFilterWheelMoving (15) : Camera Control window is waiting for filter wheel or focuser
    csWaitingForManualShutter (20) : Camera Control Window is waiting for operator to cover or uncover the telescope
    csExposingRed (24) : Camera is exposing a red image (MaxIm+ only)
    csExposingGreen (25) : Camera is exposing a green image (MaxIm+ only)
    csExposingBlue (26) : Camera is exposing a blue image (MaxIm+ only)
    csExposingVideo (27) : Camera is exposing a video clip
    csGuidingSuspended (28) : Autoguiding is suspended while main camera is downloading
    csWaitingForDownload (29) : Guide camera is waiting for main camera to finish downloading
    arto
    Arto Oksanen arto.oksanen at jklsirius.fi
    Verkkoniementie 30, FI-40950 Muurame, Finland

 

 

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. Camera dies when flipped (was: Plan carryover to next plan if first one is aborted?)
    By Mike Dodd in forum Hardware/Software/Driver Topics Not Directly Related to Our Software
    Replies: 7
    Last Post: Jan 12, 2019, 14:20
  2. Guider Settle stalls [in MaxIm] and stops plan execution
    By David Lawson in forum Hardware/Software/Driver Topics Not Directly Related to Our Software
    Replies: 12
    Last Post: Oct 24, 2018, 21:29
  3. Main camera fails to start exposure - hangs forever in ACP
    By Richard Ditteon in forum Hardware/Software/Driver Topics Not Directly Related to Our Software
    Replies: 6
    Last Post: Dec 22, 2016, 21:26
  4. Pointing update hangs when bin-4 images downloaded (FLI camera)
    By Stephane Basa in forum Hardware/Software/Driver Topics Not Directly Related to Our Software
    Replies: 37
    Last Post: Mar 6, 2016, 10:41

Posting Permissions

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