PHD2 and Lodestar X2 problems

[Jay W. Butler]

As you suggested by Andy Galasso in the Starlight Xpress forum, let me say here what has created the greatest problem for me when using PHD2 to control a Lodestar X2 for autoguiding. (By the way, I love PHD2's graphics and user interface and would prefer to use it, if I can.)

The problem is that once I have PHD2 up and running and guiding on the selected star, it will unexpectedly freeze, usually displaying alternate dark and light horizontal bars in the image space and a message that the camera is no longer connected. To resolve this, I must not only close PHD2, but also open Windows Task Manager and shut down the running ASCOM process before I can restart PHD2 and reconnect the camera.

I attach a log file that I believe shows one of the times this happened last night.

I would appreciate your suggestions. Thanks for looking.

Jay Butler

[bw_msgboard]

This log only covers a 4-min period from 23:03 to 23:07 and it looks like normal guiding – I don’t see any evidence in the log of a problem.  Wrong log file?

 

What you’re describing sounds very much like a low level problem communicating with the camera – the manufacturer’s camera driver (not the ASCOM driver), the USB subsystem, or the camera itself.  Those are the places that can cause the applications to hang and force the task manager actions you describe.

 

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.
For more options, visit https://groups.google.com/d/optout.

[Andy Galasso]

Jay,

In addition to getting a better PHD2 debug log as Bruce suggests, you could also try enabling the ASCOM debug logging and attach the ASCOM driver log file (in the ASCOM folder in your Documents folder).

​

Andy

[Rich Crowell]

Jay did you ever find a solution to your issue.  I am seeing something similar.  Rather than banding PHD2/Lodestar X2 will display a normal image.  The next image will be absolutely back with what appears to be hot pixels.  Once this starts it seems to go on until I kill PHD.

 

Rich

[Bruce Waddington]

Sorry, Rich, we had some off-line exchanges that didn't make it back to the forum.  Here was the conclusion from Jay:

Andy and Bruce,

I was unable to install v. 2.4.1c for some reason, but not to worry. I plugged the USB cable directly from the Lodestar X2 into a port on the observatory computer, and I have now been imaging for about an hour without a single problem. It clearly was a hardware issue, as you always warn, connected with my "high-end" (cost me about two hundred bucks) powered USB hub. I am, needless to say, profoundly embarrassed and apologize for wasting your time.

I do love PHD2. I used to think the autoguiding module in TheSkyX Camera Add-on was the cat's whiskers, but I think your product is better. When you decide whether and what to charge for it, let me know and I will write you a check.

[ch...@beyondmonochrome.co.uk]

I would say it likely to be a hardware issue. I had one of the first X2 lodestars in the UK and it has worked so far without a single hitch. (touch wood) This is via the Paramount hub and then via a USB over Cat 5 extender, using PHD2, PHD, Maxim and TSX.  When I had the original version, I had issues on getting enough power to the device. Do make certain, make sure your hub is powered and use good quality leads.  It may be coincidence but I switched all my leads to Lindy versions and so far, they have delivered.

[Rich Crowell]

Guys I should have followed up with you.  Jay was kind enough to drop me a note indicating that the problem was probably a communications issue and he was right.  I replaced an active USB cable and everything is now hunky dory.

Rich