Results 1 to 7 of 7

Hybrid View

  1. #1

    Default Using iTelescopes.net - Taking multiple Images of the same solar system object

    Note that this ended up relating to iTelescopes.net, a customized version of ACP which has evolved along its own path for several years. In this case, a feature in ACP is not present in iTelescopes.net's ACP-based observing logic.

    Hello,
    I'm trying to create an ACP Plan to capture images of an asteroid.
    Images to be spaced 10 mins apart.

    I initially tried this using the #WAITFOR command.
    However, I found that the second image didn't have the target in the frame.
    I appears that it stopped the tracking and then resumed the tracking after the #WAITFOR period elapsed.
    However, it didn't re-calculate the position of the target.



    So, to get over the issue, I created a second ACP Plan
    This time, I inserted the #WAITUNTIL command.
    example below:

    ; === Target 1354 - 00:20 ===
    ;
    #WAITUNTIL 00:20
    #repeat 1
    #count 1
    #filter Luminance
    #interval 120
    #binning 2
    01354 11.0 0.15 K134I 329.68444 250.75672 28.72658 5.95697 0.2169601 0.17834886 3.1257614 0 MPO259344 1423 32 1931-2013 0.50 M-v 38h MPC 0000 (1354) Botha 20130418
    ;
    ; === Target 1354 - 00:30 ===
    ;
    #WAITUNTIL 00:30
    #repeat 1
    #count 1
    #filter Luminance
    #interval 120
    #binning 2
    01354 11.0 0.15 K134I 329.68444 250.75672 28.72658 5.95697 0.2169601 0.17834886 3.1257614 0 MPO259344 1423 32 1931-2013 0.50 M-v 38h MPC 0000 (1354) Botha 20130418
    ;




    However, that didn't work either.
    Error message below:
    14:17:15 Error at line 3: missing argument in #waituntil: "00:20"
    14:17:15 (3) -> #WAITUNTIL 00:20
    14:17:15 00:17:15 MP elements for 01354 --> RA=15:49:04 Dec=-25 51' 33" (J2000)
    14:17:15 Error at line 13: missing argument in #waituntil: "00:30"
    14:17:15 (13) -> #WAITUNTIL 00:30
    14:17:16 00:17:16 MP elements for 01354 --> RA=15:49:04 Dec=-25 51' 33" (J2000)
    14:17:16 Error at line 23: missing argument in #waituntil: "00:40"
    14:17:16 (23) -> #WAITUNTIL 00:40



    I'm obviously doing something wrong, but am unclear on where I am going wrong.
    Can anyone advise on how I can correct the issue please?


    Many Thanks,


    Michael O'Connell
    Kildare, Ireland
    Last edited by Bob Denny; Jun 3, 2013 at 19:20.

  2. #2
    Join Date
    Oct 2005
    Location
    Mesa, AZ
    Posts
    27,051

    Default

    The #waitfor should have worked! Please attach a log file from a run in which the ephemeris was not updated from the elements after the #waitfor. And what version of ACP are you using? You have been a member here since 2006 :-)

    To answer your question, #waituntil takes a set number argument. See ACP Help, Acquiring Images Automatically, Making Observing Plans, #waituntil (date/time form).
    -- Bob

  3. #3

    Default

    Bob,
    Yea, a member on this account for quite a while alright.
    Only recently got the observatory fully automated.
    I only got around to buying ACP in January of this year! :-)
    Alas, poor weather so far this year has forced me to try out some of the online telescope systems. :-(

    In terms of the issue in question, I was using one of the ITelescope scopes.
    I don't have the full log file to hand right now, but I contacted iTelescope about the issue.
    This was their response:

    "Hello Michael,Thank you for your Email. I'm not sure what you were expecting, but things seem to have worked OK.I plate-solved both of your images using TheSkyX. The first was:******** ASTROMETRIC SOLUTION RESULTS ********
    Center RA: 15h 26m 59.5s
    Center Dec: -08 44' 19.0"
    Scale: 1.91 arcseconds/pixel
    Size (pixels): 1536 x 1024
    Angular Size: 0 49' 00" x 0 32' 40"
    Position Angle: 90 23' from North
    RMS: 0.25 (X: 0.19 Y: 0.16)
    Number of Stars Used in Solution: 114 (100%)
    FWHM: 1.54 pixels, 2.94 arcseconds
    ***********************************************
    The second was:******** ASTROMETRIC SOLUTION RESULTS ********
    Center RA: 15h 32m 00.2s
    Center Dec: -08 44' 24.8"
    Scale: 1.91 arcseconds/pixel
    Size (pixels): 1536 x 1024
    Angular Size: 0 49' 00" x 0 32' 40"
    Position Angle: 90 24' from North
    RMS: 0.44 (X: 0.27 Y: 0.35)
    Number of Stars Used in Solution: 133 (100%)
    FWHM: 1.48 pixels, 2.84 arcseconds
    ***********************************************
    The centers of the two images are (as seen in the attached image) 1.25 apart.This was caused by your intentional use of the #WAITFOR directive, which turns off orbital tracking:08:32:45 02:32:45 # Image 1 of 2 Moon is not currently visible
    08:32:45 02:32:45 ### Your reservation started on: Sunday, May 12, 2013 2:30:00 AM on 32843.
    08:32:45 02:32:45 Target: 04497 RA: 15h26m 59.5s DEC: -08 44' 20" (J2000) HA: 1.4 PA: 0 Alt: 44 Azm: 208.9
    08:32:45 02:32:45 Imaging to T21-astroshot-04497-20130511-023246-Luminance-BIN2-W-060-001.fit
    08:32:45 02:32:45 Flip check: Time Needed=-1140s Hour Angle=5042s Gem West=T Time to Flip=3902s Is Gem Going West=T Flip=no.
    08:32:45 02:32:45 (taking 60 sec. exposure, Luminance filter, binning = 2)
    08:33:56 02:33:56 Image File Saved to T21-astroshot-04497-20130511-023246-Luminance-BIN2-W-060-001.fit
    08:33:57 02:33:57 Skipped Preview Image
    08:33:57 02:33:57 MP elements for 04497 --> RA=15:26:59 Dec=-08 44' 20" (J2000)
    08:33:57 02:33:57 === Starting target 04497 ====
    08:33:57 02:33:57 === Following Options are Enabled: 04497
    08:33:57 02:33:57 - Autoguiding Disabled by Administrator
    08:33:57 02:33:57 ; === Target MPL 4497 Test ===
    08:33:57 02:33:57 ;
    08:33:57 02:33:57 (pause for 300 sec.)
    08:33:57 02:33:57 (turning tracking off)
    08:38:58 02:38:58 (wait finished, resuming tracking)
    08:38:58 02:38:58 === Imaging 04497 (# 2 of 2 in set 1) ===
    This section here:08:33:57 02:33:57 (pause for 300 sec.)
    08:33:57 02:33:57 (turning tracking off)
    08:38:58 02:38:58 (wait finished, resuming tracking)
    ...shows that tracking was turned off for your wait, as per the documentation of the #WAITFOR directive.The image will not be recentered here because you are shooting the same target with the same filter.I don't know what your reasons are for wanting to wait 5 minutes between images (likely to check proper motion), but in such cases you should shoot with two different plans and avoid the #WAITFOR directive. That way, you will get a centering run on your target each time."

    Hope that helps.
    Michael.

  4. #4

    Default

    In terms of using the wait until command, if I only want 1 image using 1 filter, do I need to use:

    #WAITUNTIL 1, 21-Apr-2011 08:02:00

    or

    #WAITUNTIL 21-Apr-2011 08:02:00

    Thanks,
    Michael

  5. #5
    Join Date
    Oct 2005
    Location
    Mesa, AZ
    Posts
    27,051

    Default

    OK, I get it. iTelescopes is a customized ACP system with its own observing logic. I can't speak for them, but I can say that ACP recalculates the ephemerides as needed to assure that each exposure is in the right place. You can (and should) use #waitfor.

    Or are you asking me for help using iTelescopes? If so I can't answer your question with 100% certainty. The #waituntil may not work either, and in any case I don't know how iTelescope has it implemented. In ACP, the leading '1' is for Set #1 (the first repeat of the entire plan). If you are not using #sets in the plan, then just make the directive #waituntil 1, hh:mm:ss. You may have to include the date. In ACP you do not.
    -- Bob

  6. #6

    Default

    Thanks for clarifying that Bob.

    Michael.

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

    Default

    Since this question does not pertain to ACP I am going to retitle it and move it to the general section. I don't want people to think there is a problem with this in ACP.
    -- Bob

 

 

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. Trouble taking first automated image
    By Robert Novo in forum Pre-Sales Technical Questions and Help
    Replies: 3
    Last Post: Jun 5, 2014, 02:49

Posting Permissions

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