PHD2 dev4 crashes during dither

149 views
Skip to first unread message

Roger Nichol

unread,
Feb 26, 2021, 3:41:09 AM2/26/21
to Open PHD Guiding
Hi, I have been using PHD2 successfully for about 4 months now and have started having some stability issues with dev4.  The symptom is that it crashes with an exception - this appears to be related to executing a dither.  It has happened 3 times over the last 8 days.

Logs are at https://openphdguiding.org/logs/dl/PHD2_logs_UYSi.zip

I am running NINA (nightly build 1.11 #45).

Is this a known problem ?

I will try going back to dev 3 where I had not experienced this, also had better guiding.

Thanks

Roger

bw_msgboard

unread,
Feb 26, 2021, 10:43:00 AM2/26/21
to open-phd...@googlegroups.com

Hi Roger, sorry you’re having trouble.  The logs show you are running into a known problem with NINA, one in which NINA is trying to do a dither when the system is still settling from a previous operation.  I thought they had fixed this but I don’t know the details.  You can read the discussion in this thread:

 

https://groups.google.com/g/open-phd-guiding/c/EMWTXmQdiak/m/14T3kSgYBAAJ

 

Just scroll down to the 3rd message from the end (you’ll have to ignore all the sidebar comments that don’t deal directly with the problem)

 

That said, we haven’t seen this problem cause a “crash” as you describe it, and I don’t know what exception you’re seeing – can you describe the message and what app is generating it?  I don’t think it’s coming from PHD2 but we should confirm that.  If you can look at the Windows event log on your system, we can probably get more information.  Just do a Windows search on ‘event’ and then start the Event Viewer app.  Once it gets done grinding through the internal logs, open up the ‘Windows Logs’ folder at the left then look at the ‘Application’ logs.  See if you can find logged events for PHD2 or NINA during times when you saw an exception message.  For the logs you sent, this happened around 02:31 on 2/25.  If you can find any, you can do a ‘Copy’ operation (under ‘Action’) and then paste all the details into a simple text file and send that to us.  I don’t think going back to the PHD2 dev3 release is going to help you because this isn’t a PHD2 problem and we haven’t changed anything in this area of the code.  I suspect it has more to do with the NINA release you’re using.

 

Regards,

Bruce

 


--
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/309fccd1-b7d8-454e-b776-a96aca361369n%40googlegroups.com.

Roger Nichol

unread,
Feb 26, 2021, 7:42:09 PM2/26/21
to open-phd...@googlegroups.com, bw_msgboard
Thanks for the feedback.

Yes, I'm familiar with the warning message I get from NINA regarding the dither, that usually seems benign. I'll check out the windows logs tomorrow.  The pop-up that I screen captured suggested it was an exception within PHD2, but I could be wrong.  This started happening the night I installed dev 4. Maybe coincidence. I've gone back to dev 3 and so far OK with 5.5 hours of 20 minute dithered subs collected.  It may be clear until dawn so maybe another 4 hours to collect.  I've also upgraded to the latest NINA 1.11 #049.  If this works OK I'll go back to dev 4 and see if it recurs. 

Regards,

--
You received this message because you are subscribed to a topic in the Google Groups "Open PHD Guiding" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/open-phd-guiding/dDVoauSORNQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to open-phd-guidi...@googlegroups.com.

To view this discussion on the web visit

bw_msgboard

unread,
Feb 26, 2021, 7:59:38 PM2/26/21
to open-phd...@googlegroups.com

You say you screen-captured the error message – where is it?  Can we see it?  If you are running a version of NINA that doesn’t generate the warning messages about dithering, you will probably also do well with the dev4 release.

Roger Nichol

unread,
Feb 28, 2021, 5:11:02 AM2/28/21
to open-phd...@googlegroups.com
Hi Bruce,

the error message is inline below.   I ran for the last 2 nights using dev 3 and did not see a recurrence, although last night I had an issue where guiding stopped during a 1200s sub, and when I investigated, PHD2 was no longer connected to the camera or mount.   I reconnected and started guiding again manually, disconnected guiding from NINA and reconnected it and it continued without issue until dawn.   On the night of the 26th I was using dev 3 with NINA 1.11 #045. Last night (27th) I rand dev 3 with NINA 1.11 #049

Tonight I will be imaging again (what an amazing run of clear nights in the UK!) and will go back to dev 4.

Drivers are all up to date.  

Running on an ACEPC Celeron mini-PC with 8MB RAM mounted on the scope.

Powered from an AC-DC supply through a Pegasus Pocket Advance.

USB cables all minimal length on the equipment.



Inline image
Regards,

Roger

bw_msgboard

unread,
Feb 28, 2021, 9:36:29 AM2/28/21
to open-phd...@googlegroups.com

Ok, thanks.  Can you now look for the Windows event log entries that I described earlier so we can get more detail on where this error occurred?  The problem you described for last night sounds like there’s something amiss with the USB system – probably not something as simple as a cable.  Are your temperatures lower than normal?  Can you also post your logs from last night so we can see what PHD2 logged for these disconnections – we never just disconnect cameras or mounts without logging what’s going on.  

 

Thanks,

To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/1859095397.1027797.1614507053020%40mail.yahoo.com.
image001.gif

Roger Nichol

unread,
Feb 28, 2021, 6:01:08 PM2/28/21
to open-phd...@googlegroups.com

Right, I have something repeatable. 

Just got this at the exact same point as when things stopped last night.

The events leading this are: Switching from one panel of a mosaic to another based on a time of switch-over (21:50). NINA did a slew, centre/plate solve, autofocus and start guiding with calibration.  It also did a dither at the same time, which is somewhat superfluous.  This is the exact sequence of events that happened last night. PHD2 had disconnected from the equipment. I manually connected it, started looping, chose star and started guiding.  I then had to disconnect and reconnect the guider in NINA, then all ran OK.

The sequence is shown at the end of the email.


Inline image



This is what was showing on the PHD2 screen, says guiding but nothing was happening.

Inline image



Inline image

There were no PHD2 or NINA events listed in the Event Log, but there were events at that time that could not be associated with an app from the look of it. There is a suspicious-looking event about a hwinterface service failing to start at the same time.

Inline image

Inline image

Inline image


Inline image






NINA Sequence: 


Inline image
Inline image



By the way, my guiding improved when I had put the EQ6-R tripod down to its minimum height again.



Regards,

Roger


On Sunday, 28 February 2021, 16:53:37 GMT, Roger Nichol <rogern...@googlemail.com> wrote:


Hi Bruce,


Windows logs below:

One PHD event of interest at 23:22 on 27/2/21.  

One NINA issue at 00:09 on 23/2/21. 

Neither of these seem to correlate with the timing of the issues I saw. 


Inline image

PHD2 debug and guide logs from last night attached.

I'll take a look at when I had to do the manual restart last night and see if there is anything interesting around that time.

The conditions last night were benign, above freezing, from 7C at 7PM to perhaps 1C at the coldest.

USB is always a likely cause of issues, when I was starting out with this I found I had to disconnect and reconnect the USB to get them to re-enumerate, but this seems generally stable now that I'm not having to mess around with it.

My guiding has been somewhat erratic in the last couple of weeks, I used to typically get 0.4" to - 0.6", now mostly 0.6" to 0.8" or worse.  I've checked backlash today, there doesn't appear to be any detectable. It could be as I'd set the EQ6-R mount tripod to a high position to get some low targets over some trees. I've now had the trees cut back so tonight will put it back at it's lowest position and see if that helps. Stars are nice and round though.

Regards,

Roger
On Sunday, 28 February 2021, 14:36:31 GMT, bw_msgboard <bw_m...@earthlink.net> wrote:


Ok, thanks.  Can you now look for the Windows event log entries that I described earlier so we can get more detail on where this error occurred?  The problem you described for last night sounds like there’s something amiss with the USB system – probably not something as simple as a cable.  Are your temperatures lower than normal?  Can you also post your logs from last night so we can see what PHD2 logged for these disconnections – we never just disconnect cameras or mounts without logging what’s going on.  

 

Thanks,

Bruce

 


From: 'Roger Nichol' via Open PHD Guiding [mailto: open-phd...@googlegroups.com ]
Sent: Sunday, February 28, 2021 2:11 AM
To: open-phd...@googlegroups.com
Subject: Re: [open-phd-guiding] PHD2 dev4 crashes during dither

Hi Bruce,

the error message is inline below.   I ran for the last 2 nights using dev 3 and did not see a recurrence, although last night I had an issue where guiding stopped during a 1200s sub, and when I investigated, PHD2 was no longer connected to the camera or mount.   I reconnected and started guiding again manually, disconnected guiding from NINA and reconnected it and it continued without issue until dawn.   On the night of the 26th I was using dev 3 with NINA 1.11 #045. Last night (27th) I rand dev 3 with NINA 1.11 #049

Tonight I will be imaging again (what an amazing run of clear nights in the UK !) and will go back to dev 4.

Reply all
Reply to author
Forward
0 new messages