Drift During Extended Guiding and PHD2 "Stopped Working"

Greg W;

unread,

Jun 9, 2019, 2:04:22 PM6/9/19

to Open PHD Guiding

Dear PHD2 Team,

I installed ASCOM on my Dell Mini laptop to drive my Celestron AVX mount on Bruce's recommendation after the ST-4 cable apparently failed. I've calibrated a few times, but none perfectly "clean". As we finally had a couple of relatively clear nights, I imaged on Friday and Saturday night. On both nights, the mount guided reasonably well for an hour or so and then drifted in both RA and DEC. Also on both nights, when I went out to cover the lens to do Dark Frames, there was an Error Message stating "PHD2 had stopped Working". In the linked guiding and debug logs, the _222500 section 8 had a periodic error in RA - after I ran a PEC training event. I did not play back PEC on Saturday, log _221216 section 4, shows RA and DEC drift without the RA periodicity.

I'd appreciate your input on what is causing the drift and why PHD is bombing out at some point in the session.

Thanks,

Greg

https://openphdguiding.org/logs/dl/PHD2_logs_G3tU.zip

Andy Galasso

unread,

Jun 10, 2019, 11:37:06 AM6/10/19

to OpenPHD Guiding

Hi Greg,

We have had a few reports of the CPWI ASCOM driver crashing and bringing down PHD2 with it. Here was the first report: https://groups.google.com/d/msg/open-phd-guiding/8WyRKRwi0XA/7q8GdPVsDQAJ

We would need to look at your Windows event log to confirm that it is the same problem (but the symptom seems like it is the same.) You could check to see if there is a newer version of the CPWI ASCOM driver available that fixes the problem.

The drift before the ASCOM driver crash was also related to the ASCOM driver. When PHD2 sends a guide pulse request to the ASCOM driver, it waits for the ASCOM driver to report that the pulse is complete, but the CPWI ASCOM driver kept reporting that the pulse was sill in progress (from about 00:53 onward in the 6/7 log). This appears to be a separate bug in the ASCOM driver. You should report it to the ASCOM driver maintainers so they can fix it.

Andy

Greg W;

unread,

Jun 10, 2019, 1:45:52 PM6/10/19

to Open PHD Guiding

Andy,

OK, thanks for the info. I will check the Windows Event log and forward once I find it. I'll also follow up with Celestron regarding the CPWI driver issue. Are you aware of any issues with the more basic Celestron Driver - Celestron Telescope and Focuser Set U (6.1.7059)?

Thanks,

Greg

Andy Galasso

unread,

Jun 10, 2019, 2:10:31 PM6/10/19

to OpenPHD Guiding

On Mon, Jun 10, 2019 at 1:45 PM Greg W; <greg....@altair-solutions.com> wrote:

Are you aware of any issues with the more basic Celestron Driver - Celestron Telescope and Focuser Set U (6.1.7059)?

I believe that driver is quite stable. It has been around a long time and lots of people use it. We have some additional information here: https://github.com/OpenPHDGuiding/phd2/wiki/Celestron-Mount-Connection

Donald White

unread,

Jun 10, 2019, 3:48:55 PM6/10/19

to open-phd...@googlegroups.com

Andy,

I think you are correct regarding the unhandled exception. Please see event log info below:

Log Name: Application
Source: .NET Runtime
Date: 6/8/2019 12:53:05 AM
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: user-PC
Description:
Application: phd2.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Net.WebException
at System.Net.HttpWebRequest.GetResponse()
at PWLib.Net.WebUtils.HttpGetString(System.String, Int32)
at ASCOM.CPWI.AscomTelescopeThread.Request(System.String)

Exception Info: ASCOM.DriverAccessCOMException
at ASCOM.CPWI.AscomTelescopeThread.Request(System.String)
at ASCOM.CPWI.AscomTelescopeThread.SubmitRequest(System.String)
at ASCOM.CPWI.Telescope.SubmitRequest(System.String)
at ASCOM.CPWI.Telescope.SubmitCommand(System.String)
at ASCOM.CPWI.Telescope.DoLongGuide(ASCOM.DeviceInterface.GuideDirections, Int32, Double, Int32)
at ASCOM.CPWI.Telescope+<>c__DisplayClass7e+<>c__DisplayClass81.<PulseGuide>b__7d()
at System.Threading.ThreadHelper.ThreadStart_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name=".NET Runtime" />
<EventID Qualifiers="0">1026</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2019-06-08T05:53:05.000000000Z" />
<EventRecordID>6594</EventRecordID>
<Channel>Application</Channel>
<Computer>user-PC</Computer>
<Security />
</System>
<EventData>
<Data>Application: phd2.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Net.WebException
at System.Net.HttpWebRequest.GetResponse()
at PWLib.Net.WebUtils.HttpGetString(System.String, Int32)
at ASCOM.CPWI.AscomTelescopeThread.Request(System.String)

Exception Info: ASCOM.DriverAccessCOMException
at ASCOM.CPWI.AscomTelescopeThread.Request(System.String)
at ASCOM.CPWI.AscomTelescopeThread.SubmitRequest(System.String)
at ASCOM.CPWI.Telescope.SubmitRequest(System.String)
at ASCOM.CPWI.Telescope.SubmitCommand(System.String)
at ASCOM.CPWI.Telescope.DoLongGuide(ASCOM.DeviceInterface.GuideDirections, Int32, Double, Int32)
at ASCOM.CPWI.Telescope+<>c__DisplayClass7e+<>c__DisplayClass81.<PulseGuide>b__7d()
at System.Threading.ThreadHelper.ThreadStart_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()

</Data>
</EventData>
</Event>

Log Name: Application
Source: Application Error
Date: 6/8/2019 12:53:08 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: user-PC
Description:
Faulting application name: phd2.exe, version: 0.0.0.0, time stamp: 0x5c97d43a
Faulting module name: KERNELBASE.dll, version: 6.1.7601.24441, time stamp: 0x5cb9383e
Exception code: 0xe0434352
Fault offset: 0x0000845d
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Faulting module path: %12
Report Id: %13
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2019-06-08T05:53:08.000000000Z" />
<EventRecordID>6595</EventRecordID>
<Channel>Application</Channel>
<Computer>user-PC</Computer>
<Security />
</System>
<EventData>
<Data>phd2.exe</Data>
<Data>0.0.0.0</Data>
<Data>5c97d43a</Data>
<Data>KERNELBASE.dll</Data>
<Data>6.1.7601.24441</Data>
<Data>5cb9383e</Data>
<Data>e0434352</Data>
<Data>0000845d</Data>
</EventData>
</Event>

Let me know if you concur and I will forward to Celestron.

Thanks Again,

Greg

--
You received this message because you are subscribed to the Google Groups "Open PHD Guiding" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-phd-guidi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/CAKemMNVWGxF8cPdGy9A6x9h2_DX-tpjHkARi2HMpC62sQ4o4aA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--

Greg White

Principal

Altair Solutions

972-989-7646

Andy Galasso

unread,

Jun 10, 2019, 3:57:17 PM6/10/19

to OpenPHD Guiding

Yes, that appears to be the same issue reported by the other folks. The ASCOM driver developers will need to fix it.

Reply all

Reply to author

Forward