Is anyone using apt goto++

[barrie greenwood]

Hi guys I'm trying to use apt goto++ to solve in an automated script .

It actually works upto the goto++ takes an image then solves moves closer to the target then takes anothet shot only on the second exposure it does not activate the camera .

However if I use goto++ manually it's works flawlessly. 

Does anyone have any ideas of what I need to look at to sort out this problem 

Regards baz

[bottletopburly]

I use Goto++ all the time never used in a script though that may be down to a bug possibly, I would ask @Yoddha or steve on the Apt forum .,do you have a screen shot of the goto++ screen in the editor .

 

Edited October 30, 2022 by bottletopburly

[newbie alert]

Are you trying to use it after a flip as it will do it automatically within sessioncraft.. or are you changing targets and platesolving to cordinates?

[barrie greenwood]

Hi guys 

No I'm trying to automate a session so I can use session craft to trigger a time to start a plan .

The issue I have is if i use goto++ in pointcraft it works flawlessly 

However using it as a command script it is set to try 3 times to move and solve the image .

So what happens is the first goto ++ it triggers the dslr and solves it moves closer to to the object and triggers the camera for a second time but although it triggers it it does not fire it so then the script hangs until I stop it .I have sent the log file to ivo but I don't like to keep pestering the guy 😕 

Regards baz 

Edited October 30, 2022 by barrie greenwood

[Paul M]

I've used GOTO++ in Session Craft a few times and had no problems, indeed I've been delighted with the perforamnce.

Here is my plan for an automated mosaic of M45, it worked flawlessly.

A while ago I used Session Craft and Imaging Plans to capture an early morning comet. I'd gone to bed leaving APT doing some image run which ended some time prior to the comet rising. So Session craft parked the scope then at the appropriate time found the comet's RA/DEC and ran off an image plan. All while I got my beauty sleep.

I can't think why APT isn't working for you. Here is my M45 mosaic plan. for reference. The first item is selected and you can see that at the lower right I have "Wait for script to end" selected.

I found that to be important, weird stuff happens otherwise!.  Perhaps significant for your problem?

[newbie alert]

What version are you using, and what's your platesolver?

I had a issue with the beta versions not solving after the flip and not parking after the it's finished it's run, although it was in the script

Going back a few stable versions solved that.. I'm not interested in the latest versions if they don't work

[Paul M]

Just this moment I installed 4.06 (beta). I always have the latest version as a subscriber.

I'm a huge, huge fan of ASTAP and use that for much more than just plate solving. Once configured it works beautifully with APT. I also use it stand alone for stacking, live stacking and image annotation of deep sky and comets/asteroids.

[barrie greenwood]

21 hours ago, newbie alert said:

What version are you using, and what's your platesolver?

I had a issue with the beta versions not solving after the flip and not parking after the it's finished it's run, although it was in the script

Going back a few stable versions solved that.. I'm not interested in the latest versions if they don't work

Hi I'm using platesolve 2 and astap and using thr latest version of app I updated to the beta version yesterday but the rain stopped play .

It's driving me mad I find atp absolutely brilliant and highly rate it butvthis us driving me crazy

Regards baz 

[barrie greenwood]

21 hours ago, Paul M said:

I've used GOTO++ in Session Craft a few times and had no problems, indeed I've been delighted with the perforamnce.

Here is my plan for an automated mosaic of M45, it worked flawlessly.

A while ago I used Session Craft and Imaging Plans to capture an early morning comet. I'd gone to bed leaving APT doing some image run which ended some time prior to the comet rising. So Session craft parked the scope then at the appropriate time found the comet's RA/DEC and ran off an image plan. All while I got my beauty sleep.

I can't think why APT isn't working for you. Here is my M45 mosaic plan. for reference. The first item is selected and you can see that at the lower right I have "Wait for script to end" selected.

I found that to be important, weird stuff happens otherwise!.  Perhaps significant for your problem?

Hi why the offset in your plan 

Regards baz 

[newbie alert]

19 minutes ago, barrie greenwood said:

Hi I'm using platesolve 2 and astap and using thr latest version of app I updated to the beta version yesterday but the rain stopped play .

It's driving me mad I find atp absolutely brilliant and highly rate it butvthis us driving me crazy

Regards baz 

Like I said I stopped using the beta versions and went back to the latest stable version and even had to go back further than that..

I'm using 3.98 which just works

[barrie greenwood]

I found an old demo version 3.90 so I've overwritten the newer version and will give it a go once the rain stops ....which looks like never 

Edited October 31, 2022 by barrie greenwood

[bottletopburly]

21 hours ago, newbie alert said:

I had a issue with the beta versions not solving after the flip

Try waiting 7 mins after meridian ,ivo and jim told me this at PAS in kettering 

[bottletopburly]

58 minutes ago, barrie greenwood said:

Hi why the offset in your plan

He is using an Astro camera not DSLR,also try setting goto++ attempts to 15 ,i only use asap in APT for near and blind , 

Edited October 31, 2022 by bottletopburly

[barrie greenwood]

That won't work as it fails on the second attempt to fire the camera .

It solves after the first photo is taken then moves closer to the abject as it should but then fails to trigger the camera for the second exposure 

Regards

Baz

Edited October 31, 2022 by barrie greenwood

[barrie greenwood]

27 minutes ago, bottletopburly said:

Try waiting 7 mins after meridian ,ivo and jim told me this at PAS in kettering 

It's not having the issue  with solving or after the flip it just fails to trigger the camera on the second image in the goto++ sequence which is set to 5 

[Paul M]

6 minutes ago, barrie greenwood said:

it just fails to trigger the camera on the second image in the goto++ sequence which is set to 5 

I've had that happen spuriously a few times and had to cancel the current GOTO++ operation and start it again. But that'll be just one of those things I suppose. Never been such a reccurent problem as to need looking into. I assume you have all the latest drivers for your camera? One thing that does turn up frequently in APT updates is camera 

I just opened APT on my laptop which I don't use for imaging and see that in the main settings page there is an option to save out the APT_LogFile.log. I just tried it and the resultant file contains info going back some time. So it must be retained elsewhere until saved out for the user's access.

Maybe have look at your log file to see if it shows where it's hanging? I wonder if it might be a USB/hardware device issue? 

Something that often appears in updates is camera SDK's. Here is a link to recent udate history https://astrophotography.app/usersguide/what_is_new_.htm

Here is some of my file for today. Lots of errors because nothing is connected. Can't say I've ever made reference to it when I have had isuues so maybe no use at all!

2022/10/31 20:10:24 (UT 2022/10/31 20:10:24)    DBG    Build: 22621
2022/10/31 20:10:24 (UT 2022/10/31 20:10:24)    DBG    OS: Windows 11 Home
2022/10/31 20:10:24 (UT 2022/10/31 20:10:24)    DBG    Platform: AMD64 Family 23 Model 104 Stepping 1
2022/10/31 20:10:24 (UT 2022/10/31 20:10:24)    DBG    Config file is C:\Users\matle\OneDrive\Documents\APT_Data\Profiles\General\APT.xml
2022/10/31 20:10:24 (UT 2022/10/31 20:10:24)    DBG    Detected device: Goodix USB2.0 MISC (Goodix Moc Fingerprint)
2022/10/31 20:10:24 (UT 2022/10/31 20:10:24)    DBG    Detected device: Integrated_Webcam_HD (USB Composite Device)
2022/10/31 20:10:24 (UT 2022/10/31 20:10:24)    DBG    Detected device: Qualcomm QCA61x4A Bluetooth
2022/10/31 20:10:24 (UT 2022/10/31 20:10:24)    DBG    Detected device: USB Root Hub (USB 3.0)
2022/10/31 20:10:28 (UT 2022/10/31 20:10:28)        Can't connect to PHD2 Guiding. Click on Start guiding or Shift+Click on the 'Guiding->Settings' button to try again.
2022/10/31 20:10:29 (UT 2022/10/31 20:10:29)    DBG    Connection error:6 /  Class not registered
2022/10/31 20:10:29 (UT 2022/10/31 20:10:29)    DBG    Connection error:6 ex / ASCOM.ASICamera2.Camera
2022/10/31 20:10:29 (UT 2022/10/31 20:10:29)    OpErr    Camera not selected!
2022/10/31 20:10:30 (UT 2022/10/31 20:10:30)    Op    Connected to mount Simulator
2022/10/31 20:10:30 (UT 2022/10/31 20:10:30)    DBG    It is NOT possible to control the Side of Pier. Make sure to start flipping after meridian passing!
2022/10/31 20:10:31 (UT 2022/10/31 20:10:31)    DBG    Refocus Temperature trigger - full reset
2022/10/31 20:10:31 (UT 2022/10/31 20:10:31)    Op    Connected to focuser 
2022/10/31 20:10:31 (UT 2022/10/31 20:10:31)    Op    Max allowed focuser position -  50000
2022/10/31 20:10:32 (UT 2022/10/31 20:10:32)    Op    Dithering System initialized (free mode).
2022/10/31 20:10:34 (UT 2022/10/31 20:10:34)    DBG    Can't connect SMM socket.
2022/10/31 20:10:35 (UT 2022/10/31 20:10:35)    Op    Automatic refocusing is paused.
2022/10/31 20:11:00 (UT 2022/10/31 20:11:00)    DBG    SC Status - checking for plan triggers

 

[barrie greenwood]

Nothing stands out in the log .

It's not a single error like yours it's every time it gets to the second exposure. 

I've changed every single setting I can think of but the same as .

 

 

[Paul M]

@barrie greenwoodI mentioned earlier about selecting "Wait for script to end" in your imaging plan but can't see if you replied to that point. 

Without that being checked I think it starts the GOTO++ script which starts the first exposure to solve but doesn't wait for the "Success!" flag in the GOTO++ module. It therefore might be trying to access the camera from two modules, GOTO++ and the image plan??

I remember that if I had, say, 10 exposures in the plan but didn't check "Wait for script to end" it would do the first sub then move staright onto the next GOTO for the next frame of the mosaic without waiting for the other 9 subs!

Like I said earlier, it caused me problems on my first outings with Session Craft.

Edited October 31, 2022 by Paul M

[Paul M]

Here is a link to my earlier thread on automating an M45 Mosaic. Later versions of APT now include a Simulation module that just requires Ascom Sky Simulator instaling. So some of the toil I had in that thread should be less so now.

It won't be any use for testing imaging plans if you do have a hardware problem but should be great for identifying sequencing and settings problems.

Great fun to play with on rainy evenings to

Edited October 31, 2022 by Paul M

[newbie alert]

2 hours ago, bottletopburly said:

Try waiting 7 mins after meridian ,ivo and jim told me this at PAS in kettering 

For me version 3.98 flips, solves and parks, with the beta it doesn't.. and the values are the same

[barrie greenwood]

Hi Paul

Sorry yeah I did check the wait for script to end but same as .

I've downloaded an earlier version and as soon as I get a clear window I'll try that and see what happens 

I will keep you all updated 

Regards baz