Hi Dave. This debug log file isn’t the right one, it doesn’t show the error you’re talking about. You should use the Help/Upload log capability described here:
https://openphdguiding.org/getting-help/
PHD2 creates debug and log files every time you run it, so you need to pay attention to the timestamps on the files. Figure out what approximate time you saw the error, then look at the timestamps in the log files to choose the right ones. The UI in the Upload Logs feature will show you what those timestamps are. If we can see the error in the debug log file, we can tell you more about what went wrong. That said, this is invariably a problem in the ASCOM mount driver – PHD2 does exactly the same things regardless of the type of ASCOM mount driver being used.
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/b0d29cbe-cf1b-4f6b-9fa8-991065d553f3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
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/hLZXeFfdXkU/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 https://groups.google.com/d/msgid/open-phd-guiding/3C70375FB11F4529B69FF1C25A3AA9B3%40HomeDesktop.
--
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/hLZXeFfdXkU/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 https://groups.google.com/d/msgid/open-phd-guiding/2f7444aa-5698-4d59-8645-90920de4362f%40googlegroups.com.
Hi Dave. This is a bit unusual, but it looks like the Celestron driver has actually stopped running at the point you get the first of these ASCOM-related errors. From that point on, PHD2 can’t communicate with the ASCOM driver at all. I think you’ll have to take this up with whomever supports the driver. The specific error PHD2 gets on these calls is this: The RPC server is unavailable.
The ‘RPC server” in this case is the ASCOM mount driver. Do you have other applications running that are also using the ASCOM driver? What happens to them after this error occurs? You will probably need to locate the log file from the Celestron ASCOM driver, the developer will probably need that. I don’t know if logging is enabled by default or if that’s something you have to do in the driver UI. One source of support is here: https://ascomtalk.groups.io . The Celestron driver is quite mature and is used by many, many users, so this may turn out to be a problem in the mount firmware that is causing the driver to fail. You will definitely want to make sure you’re running the latest versions of both the driver and the mount firmware.
Hope you can track this down quickly,
Bruce
From: open-phd...@googlegroups.com [mailto:open-phd...@googlegroups.com] On Behalf Of Dave Manning
Sent: Wednesday, May 15, 2019 3:47
AM
To: Open PHD Guiding
--
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/CABEGNOjSfgH0i9mHWPreR%2BbvFeetakHgN19S6GZ%3D8k53Z67%2B4A%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/71AAA75B5E684C1881BFE114D4A0A8B5%40HomeDesktop.
Hi Dave. The advice from Peter is definitely worth paying attention to since he has seen this particular problem before (I have not). The error we see in the log might very well be caused by a timeout condition, and that could in turn be caused by high processor usage on your computer. When you see the problem again, you might want to run the Windows Task Manager and see if there’s heavy usage by one of the apps or a background Windows process. You’ll want to be sure you’re seeing “all processes” when you do this and you might even want to have the Task Manager already running before the problem occurs.
Running some USB-2 cameras on a USB-3 hub is certainly a possible problem area – we have heard of several cameras, I think including some ZWOs, that don’t work reliably this way. But I think it’s more likely in such a case to see camera timeout errors in PHD2 as opposed to COM problems with the mount driver. But with the sort of problem you’re having, it’s hard to rule anything out.
Let us know how it goes,
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/CABEGNOh8oRxxsK1NX82N1Su72fJdTtnbRMzRVA1oMLEgdcJFbQ%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/5F054548026047F894EF73E95F2F8992%40HomeDesktop.
You don’t – that’s not where the problem lies. PHD2 will talk to the mount after each guide exposure, so that will be on the order of every 1-3 seconds. If you want to guide the mount, that’s what has to be done. Other apps may be polling the mount driver at a very high rate and that can cause problems – for example, polling 100’s of times per second. But since your problem is so intermittent, I don’t think that is likely to be the problem either.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/CABEGNOhFU00TjtVWDxrjgSyg0cRM611hX1ykCWz1bj6%3Dg8AXAQ%40mail.gmail.com.
Personal opinion – I would absolutely NOT do this. Most of these “instant fix” tools are rubbish at best and malware at worst. I don’t think you have a problem with PC integrity. I suggest you follow the procedures we outlined and figure out what’s really going on. If you are anxious to “repair” things, it would be ok to apply the Windows repair facility on the ASCOM platform and/or re-install the Celestron driver. I wouldn’t even do those things but at least it won’t hose your system. I think you’ll just have to have some patience and trouble-shoot the problem a bit. Have you looked to see if you have a log for the ASCOM driver?
Bruce
From: open-phd...@googlegroups.com [mailto:open-phd...@googlegroups.com] On Behalf Of Dave Manning
Sent: Wednesday, May 15, 2019 8:27
PM
To: Open PHD Guiding
--
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/31faf2f4-9eef-4790-a9e1-0e1dc0ecea18%40googlegroups.com.
--
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/hLZXeFfdXkU/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 https://groups.google.com/d/msgid/open-phd-guiding/3842BF79517C42A0AD15C554921D86C6%40HomeDesktop.
--
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/7c7289e5-281f-45da-be29-d259fa32a961%40googlegroups.com.
--
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/hLZXeFfdXkU/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 https://groups.google.com/d/msgid/open-phd-guiding/CAP7wNygKTW0GEykDQrtYWgh0f_0a5%3D1Rr7QeeDA_Ke46a2Xn%3DQ%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/CABEGNOjE49zm8fyoOeTfMZEdMkVVkgxQBWCYgv0qJpxkZdfOTQ%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/CAP7wNyjXPYBis31UreocdyL2bYTA3g74jHd5yJYYa9y4tw8XPQ%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/CABEGNOhj7hsFVQv-NBOh8y_3y05k-vo67dfdkbt82DH%3DVOepzw%40mail.gmail.com.
--
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/f618701f-b382-469e-8a94-d217cbe946b5%40googlegroups.com.
Hi Dave, sorry you’re still having trouble, but I don’t think you’ve isolated the problem yet. It’s very unlikely that the driver is “corrupted” or “faulty”. Software isn’t like hardware, it doesn’t usually rust with age. J It might have a bug but that’s not likely to just go away with a re-install. You can do a re-install without any great risk but I doubt it will have any effect, and tearing out all the ASCOM drivers will probably be a waste of time. Whenever you do these things, all the settings get lost and then you have to be sure you re-specify everything correctly. I think you need to relax a bit and try to isolate the problem. One thing I find bothersome is using the hand-controller for the mount connection. I know that some Celestron mounts have alternative ways of doing the connection, maybe one of the Celestron guys can help with that. It would be nice to get that piece of hardware out of the picture. I think you’ll need to strip things down to the most basic configuration that shows the problem. If you want, we can probably give you a test app that will “pulse guide” the mount all day long without any cameras or anything else attached through your USB system. That would probably help if you can initialize your mount in the daytime and get it in a state where it’s willing to guide. Regardless of whether or not you see the failure with such a test app, you’ll learn more about where the problem lies.
Bruce
From: open-phd...@googlegroups.com
[mailto:open-phd...@googlegroups.com] On
Behalf Of Dave Manning
Sent: Thursday, May 16, 2019 6:25
AM
To: Open PHD Guiding
Subject: [open-phd-guiding] Re:
ASCOM driver failed checking IsPulseGuiding....
RIGHT ........... After a few hours of imaging AND the same ASCOM Driver disconnection problem occurring roughly every hour or so, I tried using just a single USB3 cable from camera to laptop.
--
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/35EDE442DD6441A69CF8A34A056C6BD9%40HomeDesktop.
--
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/hLZXeFfdXkU/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 https://groups.google.com/d/msgid/open-phd-guiding/CY4PR05MB288854211086A7BE36CFE3C5AF0A0%40CY4PR05MB2888.namprd05.prod.outlook.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/CABEGNOhPm_3fGbkXBxi0VDy%2BWNWvfev7T7gZtZoy-C7q7PS_Sw%40mail.gmail.com.
--
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/hLZXeFfdXkU/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 https://groups.google.com/d/msgid/open-phd-guiding/35EDE442DD6441A69CF8A34A056C6BD9%40HomeDesktop.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/CY4PR05MB28880A172BAA2F3D2E7D5250AF0A0%40CY4PR05MB2888.namprd05.prod.outlook.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/CABEGNOiqpM5m37vM8bcQuUMGiSbDRQUP8HovVrTDygWuygpGbA%40mail.gmail.com.
--
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/hLZXeFfdXkU/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 https://groups.google.com/d/msgid/open-phd-guiding/CY4PR05MB288805EF4E309E1F561FEDA1AF0B0%40CY4PR05MB2888.namprd05.prod.outlook.com.
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/CABEGNOin4h-iBb-mhLyEv79XcxgGKH29AvS4cbPgbG_d6Z6dRA%40mail.gmail.com.
Hi Dave. I have an app you can use that will let you test continuous pulse-guiding during the daytime. If you don’t find the problem tonight, let me know and I’ll send you instructions and the app. If possible, it would be good to try replacing the cable between the PC and the hand-controller.
Good luck,
Bruce
From: open-phd...@googlegroups.com [mailto:open-phd...@googlegroups.com] On Behalf Of Dave Manning
Sent: Thursday, May 16, 2019 6:37
PM
To: Open PHD Guiding
--
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/CABEGNOin4h-iBb-mhLyEv79XcxgGKH29AvS4cbPgbG_d6Z6dRA%40mail.gmail.com.
One more point, Dave. The error you are seeing could be caused by different kinds of failures, but one of those possibilities is the ASCOM mount driver terminating (crashing). Once you are running, open up the Task Manager and find the process entry for the Celestron ASCOM driver. It will probably start with “ASCOM” and have the Celestron id in it somewhere. Then, if you see the guiding error again, look again in the Task Manager and see if the Celestron driver is still running.
Bruce
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/719D9F8279FA40A8A5B977DA491134D9%40HomeDesktop.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/65B1D15F356D4F848E3A2D312F4720CA%40HomeDesktop.
Ok, this is good information. It probably means that the ASCOM driver got an unexpected error and crashed. So the problem seems to lie in the hardware/software stack that’s comprised of ASCOM mount driver on your laptop, cable from laptop to hand-controller, hand-controller itself, cable from hand-controller to mount, then mount firmware. I would guess by now you’ve replaced the cable from the laptop to the hand-controller but I don’t know about the 2nd cable – maybe it’s permanently attached. To take the next step, you must find the log file from the Celestron mount driver. I’ve done some web-searching and this is a description from the guy who wrote the driver:
The default location that the ASCOM logging uses is “My Documents\ASCOM\Logs [date]”, for example “C:\Users\Chris\Documents\ASCOM\Logs 2016-01-25”. The log file starts with the driver name. Drivers that use the logging provided by ASCOM will probably not change this. The drivers I’ve been involved in all use this, including the Celestron, SkyWatcher, Atik, Moonlite Ash Dome, FLI and various others.
Once you have that log file, you can probably get help from either Celestron or the ASCOM-TALK support forum I mentioned earlier. We can look at the mount log file for you but we won’t be able to fix anything we find there. In the process of searching for you, I also saw that the latest Celestron driver is quite new, updated on the ASCOM web site this month. Are you sure you’re running the latest version – it should be version 6.1.7059.
Cheers,
Bruce
From: open-phd...@googlegroups.com [mailto:open-phd...@googlegroups.com] On Behalf Of Dave Manning
Sent: Friday, May 17, 2019 2:08 AM
To: Open PHD Guiding
--
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/33a10448-190b-48b2-8824-e677c60b30c3%40googlegroups.com.
--
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/hLZXeFfdXkU/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 https://groups.google.com/d/msgid/open-phd-guiding/A4743388BBB74ECD92A2BB7DF748A034%40HomeDesktop.
I would think that’s a question for Celestron?
CPWI is essentially their own control software that apparently does a ton of things, I could not find anything about guiding or guiding interface
https://www.celestron.com/pages/celestron-pwi-telescope-control-software
Thanks
Brian
portfolio https://www.brianvalentephotography.com/
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/CABEGNOj-MnVhsPy_G8Kgjfxkatw_j19TyQc8LBZYnE%3DqhVoQ5A%40mail.gmail.com.
From: open-phd...@googlegroups.com [mailto:open-phd...@googlegroups.com] On Behalf Of Dave Manning
Sent: Friday, May 17, 2019 4:39 PM
To: Open PHD Guiding <open-phd...@googlegroups.com>
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/CABEGNOj-MnVhsPy_G8Kgjfxkatw_j19TyQc8LBZYnE%3DqhVoQ5A%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/02b401d50d0a%249378a8d0%24ba69fa70%24%40gmail.com.
If CPWI implements an ASCOM-compatible interface, PHD2 will connect to it. If not, then it is probably a proprietary solution that won’t be of any use to PHD2 users. I don’t know anything about it.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/CABEGNOj-MnVhsPy_G8Kgjfxkatw_j19TyQc8LBZYnE%3DqhVoQ5A%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/3A229A840541407DAD5668AC1F2FB4BC%40HomeDesktop.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/CABEGNOgrwxvt7F-tTXpyUTd5j54hWCxS%2BZgL-j85u-RZM7HtHw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
I think you’ve probably reached a fork in the road and you’ll need to decide what you want to do. Celestron didn’t write the ASCOM driver that’s commonly used and whomever you communicated with might know zero about it or even understand what you’re trying to do. If you want to proceed with the option of using ASCOM, you’ll need to branch out and engage with other people. In particular, you should move the discussion to the ASCOM-Talk forum. For example, here is a relevant post on your topic:
https://ascomtalk.groups.io/g/Help/message/40547
That post makes it clear that you now have two choices for using ASCOM, each written by different people and each providing different behaviors. You will have to be prepared to work with them to resolve your problem, including finding log files and submitting them. Of course, this post also demonstrates that the answer you got from Celestron is simply wrong.
If you don’t want to do this amount of work, you can revert to the ST-4 style of guiding, with a specialized guide cable running from the guide camera to the mount. Assuming the cable is wired correctly and not damaged, you should be able to guide. This is all described in the PHD2 help guide. If you operate this way, you will lose some number of PHD2 features and you’ll have to re-calibrate every time you slew the telescope, but you should be able to guide and take images. Many users still operate this way.
In any case, I don’t think I can help you anymore at this point, but I wish you luck with whatever choice you make.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/CABEGNOgrwxvt7F-tTXpyUTd5j54hWCxS%2BZgL-j85u-RZM7HtHw%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/9330C4B5797F49C5A18048459C866858%40HomeDesktop.
Ok. Don’t forget, I can give you the test app which would be applicable even if you’re working with other people. That would let you do a lot of this testing in the daytime when it might not be so frustrating.
Hope you can get this straightened out without too much more grief.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/CABEGNOh5O6O9R_Fsuva-bY3bf%2BX7Tr9w1B9cnizHnD4PGAuiMQ%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/00B1114D708F49F0917A96D5011D9F9D%40HomeDesktop.
Ok, I’ll send you a test package shortly via private e-mail.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/CABEGNOi9-%2BHPuSFxEpoJE0QTb6PGMLaMQ6DYNRWpt7Rgwc0Guw%40mail.gmail.com.
CPWI does implement an ASCOM interface but I don’t know if it will do PulseGuiding – I’ve not tried that yet, I use an ST-4 connection. PHD2 does see it as an AUX mount though just fine.
Sent from Mail for Windows 10
From: Dave Manning
Sent: Friday, May 17, 2019 7:05 PM
To: Open PHD Guiding
Subject: Re: [open-phd-guiding] Re: ASCOM driver failed checkingIsPulseGuiding....
I think it does implement ASCOM interface.
I'm going to ask PWI directly but I think guiding with PHD2 is done with an ST4 cable from camera to mount.
I'm going to try it anyway. I have what I need.
It might be fun ........................ or not.....
On Sat, 18 May 2019 at 09:53, bw_msgboard <bw_m...@earthlink.net> wrote:
If CPWI implements an ASCOM-compatible interface, PHD2 will connect to it. If not, then it is probably a proprietary solution that won’t be of any use to PHD2 users. I don’t know anything about it.
Bruce
From: open-phd...@googlegroups.com [mailto:open-phd...@googlegroups.com] On Behalf Of Dave Manning
Sent: Friday, May 17, 2019 4:39 PM
To: Open PHD Guiding
Subject: Re: [open-phd-guiding] Re: ASCOM driver failed checking IsPulseGuiding....
Bruce,
Celestron have gotten back to me advising that there is not another Mount Driver to use.
They have strongly recommended that I use CPWI and not the hand control.
Is PHD2 able to be used effectively with CPWI?
How does one connect cameras properly for use with CPWI?
On Sat, 18 May 2019 at 01:23, bw_msgboard <bw_m...@earthlink.net> wrote:
Ok, this is good information. It probably means that the ASCOM driver got an unexpected error and crashed. So the problem seems to lie in the hardware/software stack that’s comprised of ASCOM mount driver on your laptop, cable from laptop to hand-controller, hand-controller itself, cable from hand-controller to mount, then mount firmware. I would guess by now you’ve replaced the cable from the laptop to the hand-controller but I don’t know about the 2nd cable – maybe it’s permanently attached. To take the next step, you must find the log file from the Celestron mount driver. I’ve done some web-searching and this is a description from the guy who wrote the driver:
The default location that the ASCOM logging uses is “My Documents\ASCOM\Logs [date]”, for example “C:\Users\Chris\Documents\ASCOM\Logs 2016-01-25”. The log file starts with the driver name. Drivers that use the logging provided by ASCOM will probably not change this. The drivers I’ve been involved in all use this, including the Celestron, SkyWatcher, Atik, Moonlite Ash Dome, FLI and various others.
Once you have that log file, you can probably get help from either Celestron or the ASCOM-TALK support forum I mentioned earlier. We can look at the mount log file for you but we won’t be able to fix anything we find there. In the process of searching for you, I also saw that the latest Celestron driver is quite new, updated on the ASCOM web site this month. Are you sure you’re running the latest version – it should be version 6.1.7059.
Cheers,
Bruce
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/CABEGNOgrwxvt7F-tTXpyUTd5j54hWCxS%2BZgL-j85u-RZM7HtHw%40mail.gmail.com.
Thanks, Mitch, this is very helpful – nothing like hearing from someone who has actually used the software. J This is a new arrival on the scene, not something I was aware of, so it’s something we’ll have to be aware of going forward.
Thanks for the post.
Bruce
From: open-phd...@googlegroups.com [mailto:open-phd...@googlegroups.com] On Behalf Of Mitch Mitchell
Sent: Friday, May 17, 2019 8:45 PM
To: open-phd...@googlegroups.com
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/6111549CD10246DB808E53E320C69C81%40HomeDesktop.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/CAP7wNyi8jph_eJ9UWtDo4mAr0W%3DsdSAxKMWMjh379OZgsLBM%2BA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
--
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/1ff93573-7bab-4dd4-8b2d-27d4e39074b0%40googlegroups.com.
Dave,Well then, a cautionary congratulations for now, and a good job at working through the troubleshooting aspect of this hobby. Isn’t it fun?!?!?Best wishes,Jay
On Sat, May 18, 2019 at 3:09 AM Dave Manning <in...@davemanningart.com> wrote:
Okey Dokey.......--Guess what .....After running tests ALL DAY on my mount's pulse guiding capabilities, with different combinations of cables, etc. I think I've finally found what the problem is............ and almost made me cry ....AUX Port #1 appears to be FAULTY!!!!!!As soon as I plugged the hand control into AUX Port #2 I got almost 2 hours of uninterrupted pulsing before I decided that was enough.I'm now diving straight back into imaging while pulse guiding with PHD2 and so far, so good........................ after 30minutes anyway... :)
On Wednesday, May 15, 2019 at 11:06:53 AM UTC+10, Dave Manning wrote:Hi folks.Over the last few months, the attached warning message periodically raises its head while I'm happily guiding and imaging the night away.I can be guiding for hours or even a whole night without this message coming up, then on other nights (last night being a case in point..) it must have come up 4 times through the night.I've just been "disconnecting all" then "connecting all" to get it working again after each occurance of the message.BTW, when that message comes up guiding starts to deteriorate badly...Before hand, guiding is going along VERY NICELY with a high degree of polar alignment accuracy.Any advice would be greatly appreciated.Dave,Sydney, Australia
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...@googlegroups.com.
--
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/b12f48db-1aaa-4ae8-9177-e47cee625841%40googlegroups.com.
--
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/hLZXeFfdXkU/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 https://groups.google.com/d/msgid/open-phd-guiding/CAP7wNyjPb3zJk6x77banCWNVPVOD-k9h%2BMVmWr0x0U1zEQJszg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/CAP7wNyjPb3zJk6x77banCWNVPVOD-k9h%2BMVmWr0x0U1zEQJszg%40mail.gmail.com.
Sent: Sunday, May 19, 2019 7:23 PM
To: Open PHD Guiding
Subject: [open-phd-guiding] Re: ASCOM driver failed checking IsPulseGuiding....
Dave,
I want to add my congratulations. John S mentioned that the Chris Rowland is the author of the Celestron driver. Back in July 2017 I was E-mailing Chris about my woes in developing an app that communicated via his driver to my CGEM and was failing due to The RPC server is unavailable. (Exception from HRESULT: 0x800706BA. Chris knew about the RPC server but couldn't point to a particular issue to watch out for. I solved my problem when I discovered my program was making rapid fire calls to ASCOM. My program would not fail immediately...it would always take upwards of an hour. When I finally slowed down my program's ASCOM calls to once per second the RPC server errors stopped happening. The RPC server is sort of a generic information transfer mechanism that a lot of programs use...including ASCOM programs. I also understand that the RPC server also uses the TCP stack which means that it also competes your computer's internet traffic. It could be that one of the many programs you are using is not well behaved and is firing off RPC server calls way to fast. The only way you have for testing this is to try running your system with some programs not running. A example of this would be to disable antivirus software. This is not easy and may not be possible in some cases. The only other diagnostic for you is to watch the CPU usage. You can do this at any time by pressing cntrl-alt-del and then selecting task manager. The window that appears displays list of all of the applications and services that are running along with how much services each one is using.
I think some of this isn’t relevant to the specific problem. The ‘RPC’ in question (remote procedure call) isn’t using a network protocol stack, it is using the Windows COM architecture. There are numerous ways to implement remote procedure calls, and COM (a very old mechanism) is one of them that doesn’t rely on TCP/IP or network protocols. Also, I think we’ve verified in this case that the problem is not caused by rapid-fire calls on the ASCOM driver. What we see in the ASCOM log file (eventually) is a timeout in the communication between the ASCOM driver and the mount firmware over the USB/Handbox connection. Shortly after the timeout, the ASCOM driver exits, presumably because it hasn’t correctly handled the timeout error. Once the ASCOM driver is no longer running, any COM calls made to it will fail with the error message Dave is seeing. I think not all of this info has been posted on the forum so I just wanted to clarify. Also, the failing condition has been triggered by nothing more than a simple test app that mimics PHD2 pulse-guiding using the ASCOM driver – no cameras, no network activity, no extra USB traffic, just a bare-bones test case.
A huge point of frustration here is that Dave can’t know for a long time whether the problem has really gone away. He’s already run a successful test for hours, followed by a dark-sky session for more hours, all without having any trouble. Then the next night out, he got a nearly-immediate error. This sort of behavior can be caused by all sorts of hardware/firmware problems. I really hope the latest testing works, but it will probably be weeks before Dave can close the book on this problem.
Bruce
The sneaky aspect of this kind of testing is that sometimes a specific version of an application will have a bug in it which causes a problem. If the version is old then updating to a newer version can solve this problem. If the version is the latest then going back to a previous version can achieve the same success. This might be what is happening when you use your old laptop. It probably has older versions of programs on it and this might be making all the difference.
Regardless...fingers crossed that you have found a workable solution
Peter
On Sunday, May 19, 2019 at 9:10:25 PM UTC-4, Dave Manning wrote:
2 hours into the test with the old laptop ........................... and all is well .................... so far.
I'm still going to let this run a while longer though, at least while I go to the local electronics store to get some larger diameter cable management tube.
I'm going to have to run a seperate cable from the
guide camera to this older laptop AND get a larger table for out in the
field..... I can live with that .... :)
On Wednesday, May 15, 2019 at 11:06:53 AM UTC+10, Dave Manning wrote:
Hi folks.
Over the last few months, the attached warning message periodically raises its head while I'm happily guiding and imaging the night away.
I can be guiding for hours or even a whole night without this message coming up, then on other nights (last night being a case in point..) it must have come up 4 times through the night.
I've just been "disconnecting all" then "connecting all" to get it working again after each occurance of the message.
BTW, when that message comes up guiding starts to deteriorate badly...
Before hand, guiding is going along VERY NICELY with a high degree of polar alignment accuracy.
Any advice would be greatly appreciated.
Dave,
Sydney, Australia
--
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/a2aa924a-3a20-4ec2-931c-88e5968c2d61%40googlegroups.com.
--
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/hLZXeFfdXkU/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 https://groups.google.com/d/msgid/open-phd-guiding/9a212fe6-4df1-43cf-8e40-0b000fced32f%40googlegroups.com.
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/CABEGNOgVcmrLMHoj0pGV3Ko7_peUCgP815p7LdG3FkEfyWLfRA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/CAJa45i4c6kZqk1nogHSa%2BANpAfAAVQdR6Kd_86jDz9wmq_UL9A%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/CABEGNOhDQ3GBNSvsBcA907vVH4Hkd1tUg5gFU4wUVGNU%3D9-vag%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/CAJa45i7WyfwgmxkN-v3GBpaCnts12pM%3D3-ye0-xrfuoKjcp3BQ%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/CABEGNOiFV6W%2Bj4amrYH84uekK171jkgxusyDv%2BjYYV3skLeqdQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Dave, thanks for reporting back. Glad to hear everything is working with the new laptop.Andy
--
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/hLZXeFfdXkU/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 https://groups.google.com/d/msgid/open-phd-guiding/CAKemMNWFYRFX1TQnfK1nwNZxBTyFm_zHfWvtTrsvvPk17H-xTg%40mail.gmail.com.