PHD2 disconnecting after a few west steps - log file location strange?
Greg S
The C:\cygwin\home\agalasso\projects\phd2\scope_ascom.cpp:1105->ASCOM Scope: cannot get side of pier when not connected C drive location, I am not familiar with.
bw_msgboard
Hi Greg, sorry you’re having trouble. This isn’t a PHD2 problem, it looks like a lower-level driver or hardware device is failing and wreaking havoc in the process. There are two error events that are relevant:
One shows up while trying to communicate with the mount:
19:42:26.069 00.000 19096 Alert: ASCOM driver failed checking IsPulseGuiding. See the debug log for more information.
19:42:26.069 00.000 21824 pulseguide: [800706ba] The RPC server is unavailable.
19:42:26.069 00.000 21824 dispid(CanPulseGuide): [800706ba] The RPC server is unavailable.
The other shows up while trying to communicate with the camera:
22:27:34.779 00.002 9220 Alert: After 17.5 sec the camera has not completed a 2.5 sec exposure, so it has been disconnected to prevent other problems. If you think the hardware is working correctly, you can increase the timeout period on the Camera tab of the Advanced Settings Dialog.
PHD will make several attempts to re-connect the camera.
22:27:34.998 00.219 9220 Try camera reconnect, now = 1605932854
22:27:35.000 00.002 9220 gear_dialog: ReconnectCamera
22:27:35.001 00.001 9220 gear_dialog: DoConnectCamera [ASI Camera (2) (ASCOM)]
22:27:35.002 00.001 9220 Status Line: Connecting to Camera ...
22:27:35.004 00.002 9220 GetString("/profile/2/cam_hash/14821106/whichCamera", "") returns "0,ZWO ASI290MM Mini"
22:27:35.005 00.001 9220 Connecting to camera [ASI Camera (2) (ASCOM)] id = [0,ZWO ASI290MM Mini]
22:27:35.006 00.001 9220 Create ASCOM Camera: choice 'ASI Camera (2) (ASCOM)' progid ASCOM.ASICamera2_2.Camera
22:27:35.062 00.056 32944 putprop: [80020009] Exception occurred.
22:27:35.074 00.012 9220 Alert: ASCOM driver problem: Connect:
(ASCOM.ASICamera2_2) Communication Failure
22:27:35.078 00.004 9220 Throw from C:\cygwin\home\agalasso\projects\phd2\gear_dialog.cpp:1088->DoConnectCamera: connect failed
22:27:35.079 00.001 9220 Status Line: Camera Connect Failed
22:27:35.082 00.003 9220 Camera Re-connect failed
With the first problem, it looks like the EQMOD instance was terminated. This is very unexpected, that driver is used by thousands of people and has a history of being stable. It think it’s more likely that one of your camera drivers or a USB connection has failed and EQMOD was just a hapless bystander.
I think you will have to isolate which of your ASCOM devices is triggering the problem, including your main imaging camera if that was running at the time. Before doing that, you should probably run the ASCOM diagnostic tool to make sure the ASCOM platform was correctly installed and is functional. Then be sure you have the latest camera drivers – those get churned at a very high rate. If those things don’t help you, you can move to testing during the daytime. Just start running both the guide and main cameras in continuous exposure mode on your imaging computer. PHD2 will run the guide camera even if not connected to the mount. It’s fairly likely the problem could be in the USB subsystem and USB connections you’re using. You can use the ‘Trouble Shooting’ section of the PHD2 manual to find a list of things to investigate for typical lost-connection problems with the guide camera. Obviously, you should leave SGP and Nina out of the picture, you need to boil things down to the essential problem.
Good luck,
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/6de1d092-f010-47d7-90aa-7582a149d501n%40googlegroups.com.
