Please note: You are welcome to visit and look around here, but you will not see the premium support sections until you are a DC-3 Dreams customer. Also, to protect our performance we have disabled searching for guests. Contact us for a forum account if you wish to have pre-sales information.

THis is the AP mount reporting this error when I try to assure that the offset tracking is set to 0. Have you very recently updated the Astro-Physics driver? It just finished slewing and the tracking is on, so changing the track offsets should be totally legal.

This is the first slew of the run. Oddly, the mount should have been unparked when ACP connected to it, and again at the beginning of every run, ACP will unpark the scope. So especially this last one is strange.

I'm unsure what to do about this. So far it is specific to your installation. What is this about a delay??? Have you edited any of the ACP scripts for this? I really need to get to the bottom of this if it is a generic A-P problem. If needed I will contact them but I will need to get with you to get more info. Or maybe you have already contacted them? Help me out here...

I'm unsure what to do about this. So far it is specific to your installation. What is this about a delay??? Have you edited any of the ACP scripts for this? I really need to get to the bottom of this if it is a generic A-P problem. If needed I will contact them but I will need to get with you to get more info. Or maybe you have already contacted them? Help me out here...

Yes I did talk to Howard who said to put the delay in. What I also get occasionally is errors in APCC due to "low power"... I think the mount is not fully powered up before other app try to use it and this leads to failures... maybe. In any case, I increased my delay in the startup script now to 15s and will watch it as it starts. This is intermittent and may have to do with whatever else might be running, but this is an I7 8 core processor... Let me just test the start-up.

Well, the test start-up did not go well with that APCC set of errors again. See the jpg. Also FM did not start. Here are the logs. I am rebooting the system and will try again... Zipped APCC material too big to upload.

Well2, startup worked fine after reboot as did shutdown... but APCC left running and throwing errors....

Attempt to startup again fails... something about a dead state..... think I better make sure APCC is complete closed down after the shut down.

I'm all mixed up. What does the focuser have to do with parked state on the mount?

I confused you with the second issue on the NightCrawler. That is in the other post from me today. I hope that is resolved internally with FocusMax. I have to go down these one by one with this new system. I have a long shopping list.

This error did not occur last night. I think it related to having APCC running after system shutdown and power-off of the mount. I added a kill process command (call to your stop program) and hopefully that will fix this problem. This requires more testing. The stop program, does not seem to able to kill the APCC ASCOM driver.

A possible variant of the error occurred last night during flats acquisition:

Have a look at the actual AutoFlat log (My Documents\ACP Astronomy\Logs\AutoFLat-xxxxxx.log). I think you're asking your system for too much flat data and it is failing for the sky being too dark. Also, vheck the Images area I am guessing you got quite a bit of flat data anyway (like 45 minutes' worth).

By the way the Scheduler would have recovered and continued into regular observations. I understand you stopped and restarted it, and since it was already too dark, it only took it 22 seconds to figure it out this time: