PHD2 2.6.7 unreliable with QHY5-II. Hangs on "waiting for devices"

[Han K]

The new version 2.6.7 is very unreliable with my setup. While guiding it often stops in situation Looping. Then when I press stop in PHD2 is says waiting for devices. I'm using a QHY5-II guide camera and EQACOM. Is this because of the new QHY library.

Version 2.6.6 works fine for me.

Han

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

[Han K]

The log was uploaded with 2.6.6. Below the logs of 2..6.7 One or two will be made with 2.6.6.

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

Han

[Jim Waters]

What QHY Drivers are you using - releases.  What release of PHD2 were you using before?

[Han K]

On Thursday, March 5, 2020 at 1:05:20 AM UTC+1, Jim Waters wrote:

What QHY Drivers are you using - releases.  What release of PHD2 were you using before?

Hi Jim,

Before I was using PHD2 2.6.6. For the camera i'm using the "QHY driver" andthe mount "EQMOD ASCOM HEQ5/6"  So for the camera it is the direct driver. I can see in the menu the QHY5 ascom driver but I'm not using that one. It happens already twice after upgrading 2.6.6 to 2.6.7. It seems to work but after some time it hangs in mode "looping" When I push stop is says "waiting for the devices"

Han

[bw_msgboard]

Hi Han.  The question is whether you are using the latest QHY camera drivers for your model camera.  Those have to be separately downloaded and installed from the QHY web site.  Sometimes the camera SDK we get from the vendor for use by PHD2 assumes that the latest camera drivers are also installed.  I don’t know if that’s the case here, but it’s worth checking. You could also try the ASCOM driver to see if that works with the latest PHD2 release.

 

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/3ad91038-b48e-44f4-afc7-20e33cf6b729%40googlegroups.com.

[Han K]

Hello Bruce,

The QHY5-II-M drivers where installed a half year ago. The installer is dated january 2018. I have downloaded again and it is still the same. I have restarted PHD2 now maybe 15 times. It is an intermittent problem. Yes I could try ASCOM driver or stick with PHD2 2.6.6.

Maybe others will report similar problems and it will be clearer what's causing this.

Cheers, Han

[Andy Galasso]

Hi Han,

We recently received notice from QHY that a new driver SDK is available and we will be updating PHD2 shortly to incorporate the new driver.  In the meantime you might want to see if connecting through the INDI path is more reliable? (perhaps the INDI driver is using an SDK version that works more reliably with your camera?)

Andy

[Han K]

Hi Andy,

Attached an fresh upload of the logs made during the day while PHD2 locked on a hot pixel. Everything works fine and then it happens in the end. PHD2 is continuous  "Looping", I press stop and then "Waiting for devices". Total session time 28 minutes

I suspect the QHY5 but it is not proven. I have read that the QHY drivers where updated but later understand that it seems only the case for Linux and Mac, Note that I run Window7. I will now run a test with the ASCOM driver.

Thanks, Han

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

[Han K]

Hi Andy,

The "QHY driver" problem started at 16:33:

16:33:37.717 00.000 3196 evsrv: cli 056F0E20 response: {"jsonrpc":"2.0","result":0,"id":2003}
16:37:49.157 251.440 3196 Stop button clicked

Test with QHY5 ASCOM driver has to wait till clear sky. PHD2 requires calibration before it want to operate.

Regards, Han

[Han K]

This is an error I get with the QHY5 ASCOM driver after maybe 20  minutes. The 30 seconds was selected to simulate guiding by locking on a hot pixel.

 logs:

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

[Han K]

The QHY5 ASCOM keeps on going but the error is weird. It even mentions a path from your computer: C:\cygwin\home\agalasso\projects\phd2\worker_thread.cpp:157->Capture failed

It looks like the ASCOM driver recovers from the error but the direct driver not.

Extract from the log linked in previous message:

21:48:27.860 00.000 3280 PhdController: newstate STATE_SETTLE_BEGIN
21:48:27.861 00.001 3280 evsrv: cli 00F30200 response: {"jsonrpc":"2.0","result":0,"id":2003}
21:49:11.098 43.237 3288 worker thread setting skip send exposure complete
21:49:11.098 00.000 3288 worker thread queueing reconnect event to GUI thread
21:49:11.098 00.000 3288 Error thrown from C:\cygwin\home\agalasso\projects\phd2\worker_thread.cpp:157->Capture failed
21:49:11.099 00.001 3288 worker thread skipping SendWorkerThreadExposeComplete
21:49:11.099 00.000 3288 worker thread done servicing request
21:49:11.103 00.004 3280 Alert: After 45.0 sec the camera has not completed a 30.0 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.
21:49:11.334 00.231 3280 Try camera reconnect, now = 1583700551
21:49:11.335 00.001 3280 gear_dialog: ReconnectCamera
21:49:11.335 00.000 3280 gear_dialog: DoConnectCamera [CMOS QHY5II Camera (ASCOM)]
21:49:11.335 00.000 3280 Status Line: Connecting to Camera ...
21:49:11.341 00.006 3280 GetString("/profile/1/cam_hash/1b794b27/whichCamera", "") returns ""
21:49:11.342 00.001 3280 Connecting to camera [CMOS QHY5II Camera (ASCOM)] id = []
21:49:11.342 00.000 3280 Create ASCOM Camera: choice 'CMOS QHY5II Camera (ASCOM)' progid ASCOM.ASCOM_QHY5II.Camera
21:49:11.590 00.248 3280 dispid(Name): [80020006] Unknown name.
21:49:11.590 00.000 3280 dispid(InterfaceVersion): [80020006] Unknown name.
21:49:11.590 00.000 3280 ASCOM camera: MaxBinning is 1
21:49:11.590 00.000 3280 invoke: [80020009] Exception occurred.
21:49:11.591 00.001 3280 CoolerOn:
(ASCOM.QHY5II) Property read CoolerOn is not implemented in this driver.
21:49:11.591 00.000 3280 ASCOM camera: CoolerOn threw exception => no cooler present
21:49:11.591 00.000 3280 ASCOM Camera: set binning = 1
21:49:11.591 00.000 3280 GetDouble("/profile/1/camera/pixelsize", 0.000000) returns 5.200000
21:49:11.591 00.000 3280 DoConnectCamera: reconnecting=1 warningIssued=0 lastCam=[CMOS QHY5II Camera (ASCOM)] scaleRatio=1.000
21:49:11.591 00.000 3280 Connected Camera: CMOS QHY5II Camera (ASCOM)

[bw_msgboard]

The pathname in the logged message isn’t relevant, it’s just a consequence of the PHD2 build system.  What matters is the alert message, which describes what happened from the PHD2 perspective. This supports our earlier view, it’s a problem in the lower levels of the system – probably the camera driver or the camera itself but maybe a problem in the USB subsystem.  The ASCOM “driver” isn’t a driver in the Windows sense, it’s an application that uses the native Windows drivers provided by the camera vendor.  The trouble-shooting section of the PHD2 Help guide talks about ways to isolate USB and power-related problems if that’s where your problem lies.

 

Bruce

 

---

From: open-phd...@googlegroups.com [mailto:open-phd...@googlegroups.com] On Behalf Of Han K

Sent: Sunday, March 08, 2020 2:51 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/2d8e36e8-d6e2-4b99-8040-af1087686450%40googlegroups.com.

[Simon D.]

I just started guiding last night and was tweaking my rig.  I’m running into the same problem with the same camera, QHY5-II.  It hangs on « guiding » and I can’t stop it...says « waiting for devices ». 

Watching this thread carefully. 

[Han K]

I just did a test run with version 2.6.6 during for 1 hour and 45 minutes. Guiding on a hot pixel. No problems. I will stick with version 2.6.6 for the moment.

Han

[Jerry Floyd]

Hi, Han K.  Maybe I can shed a little light on this issue, or, failing that, obfuscate it a little further.  I had a similar problem with my QHY-II guide camera a couple of years back.  During the time I used it QHY released several driver updates, one of which was supposed to correct the problem and did - for a while.  The problem returned, would not go away, and eventually I resolved it by replacing the QHY-II with a Starlight Xpress Ultrastar, which has performed flawlessly since.  Therefore I don't think that the "waiting for devices" problem is caused by a "new QHY library."

[John Sim]

Hi Han,

I have two systems each using a QHY5L-II. I upgraded to v2.6.7 and had one full night imaging on both systems without any issues. However - I am using the QHY ASCOM driver, specifically the guider driver from their 3-in-1 ASCOM package. This shows as "QHYCCDCameras-Guide (ASCOM)". And in my case I'm using a version that they released in early 2019 and I've had no need to change it. My understanding, and this could be incorrect, is that if the ASCOM driver is employed then the version of the QHY SDK that is used is the one in the ASCOM folder (Program files x86\Common Files\ASCOM\Camera), not the SDK version in the PHD folder. 

[Andy Galasso]

On Wed, Mar 11, 2020 at 3:18 AM John wrote:

if the ASCOM driver is employed then the version of the QHY SDK that is used is the one in the ASCOM folder (Program files x86\Common Files\ASCOM\Camera), not the SDK version in the PHD folder. 

that is correct

[Han K]

Thanks all for the positive reports. Maybe the problem is depending on the hardware setup.  At my setup the USB communication goes via an active USB3 cable then via the ASI1600 hub to the QHY5-II. So two hubs. So has anything changed in v2.6.7 with respect to the USB communication??

Today I did again some tests. In the first five minutes, In the first five minutes  had already two incidents with  "waiting on devices". So I removed all drivers and did this test:

Preparation:  Removed all QHY5 drivers. Reinstalled again the latest drivers. Rebooted the computer.

Did a duration test run while guiding on a hot pixel:

• v2.6.7 After 1 hour  v2.6.7 was hanging in "Looping", After pressing stop it indicates "waiting on devices". 
• v2.6.6. No problems after 3 hours!

For this test I used the "QHY driver".  Where in PHD2 v2.6.7 for Windows any changes in the USB communication or QHY5 communication introduced?

Han

[Brian Valente]

have you tried connecting the guide camera directly to the computer just to see if it works?

--
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/05373ec1-958d-4575-b927-e2f2599ab41d%40googlegroups.com.

--

Brian 

Brian Valente

portfolio brianvalentephotography.com 

[John Sim]

I just checked the SDK download page on QHY's site and it states for the 2 previous releases (28th and 19th February) neither supports the QHY5. I don't know which version is included in PHD2 v2.6.7 but your experience suggests that this could be the issue. If you want to continue to use the "QHY driver" option instead of the ASCOM driver then the easy way is to uninstall v2.6.7, install 2.6.6 and take a copy of qhyccd.dll from the PHD2 folder, upgrade again to v2.6.7 and then replace the qhyccd.dll file with the older version you just took a copy of. There's nothing more complicated to the QHY SDK than that single qhyccd.dll file and it can just be copied around. If you are using multiple programs which interface with the QHY5 then it is best to ensure that you have the same version of this DLL in each program's folder. (See https://www.qhyccd.com/index.php?m=content&c=index&a=show&catid=127&id=162). Each time you upgrade PHD2 you then have to replace the dll with the older version you've saved. 

[Han K]

Hello John,

That's an interesting idea. Note that the QHY5 classic is no longer supported but the QHY5-II is. (one of the reason i bought a QHY5-II but have also an QHY5 classic) As an experiment,  I have copied the QHYCCD.dll from v2.6.6 to v2.67.7 but that didn't help. Also downloaded the latest but that didn't help either. Still the same problem.

So no fix. Only one of the developers could tell what has changed in v2.6.7. Replacing the QHYCCD.dll doesn't help. :(

Han

[Andy Galasso]

On Fri, Mar 13, 2020 at 12:09 PM Han wrote:

Only one of the developers could tell what has changed in v2.6.7.

Hi Han,

We publish the list changes in each release on the phd2 web site here: https://openphdguiding.org/development-snapshots/

For more detailed information, you can even see the individual code changes in github: https://github.com/OpenPHDGuiding/phd2/commits/master

PHD2 is using the same version of the QHY SDK in both 2.6.6 and 2.6.7. PHD2 also records the QHY SDK version in the PHD2 debug log -- if you open the debug log in a text editor (notepad or whatever) and search for "SDK Version" you'll be able to see it.

Andy

[Han K]

Thanks Andy,

So the (SDK) drivers are all the same. Then my conclusion is it must be something in the newer version.

I have tested all development versions and conclude that the problem started with version 2.6.6dev3.  The problems doesn't occurs up to 2.6.6dev2.

The problem start by starting and stopping the guiding (manual or via the server). I also noticed a very fundamental different behavior in v2.6.6dev3 and upwards. You have to press in v2.6.6dev3 and up the loop button twice before you get a green guide button. Also the messaging is different. I suspect this is related to the problem. See table below:

Han

Using the "QHY driver"

Version 2.6.6.dev3 and upwards
Action user          PHD2 Messages
---------------------------------------------------------------
Press Stop           Waiting for devices

Press Loop           Looping
                     Stopped {after exposure time}
                     {guide button stays greyed}
                     Message Stopped disappears {after second exposure time}

Press Loop           Looping
                     {message looping stays infinite } 
                     Guide button turn green {after exposure time}

   
Up to version 2.6.6dev2
Action user          PHD2 Messages
---------------------------------------------------------------
Press Stop           Waiting for devices
Press Loop           Looping
                     Stopped {after exposure time}
                     Guide button turn green {after exposure time}
                     Message Stopped disappears {after second exposure time}
 

[Han K]

And here are all the logs from the tests:

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

[Patrick Chevalley]

Han,

It can be useful if you can find the exact commit that produce the problem.

Here is the list of change between dev2 and dev3:

https://github.com/OpenPHDGuiding/phd2/compare/v2.6.6dev2...3297c0734c596e980e4363044a876c4864c64d5c

For example to test before all the qhy change on November 25 use this command:

git checkout 31e39a5

Then be sure you run cmake on a totally empty directory so any cmake change are fully applied. 

Patrick

[Andy Galasso]

Han,

The J4ZB logs show you looping 15s exposures then clicking the stop button at various times. I do not see any camera errors in any of the tests -- no timeouts or disconnects or anything like. Looking back at the original debug log you posted (PHD2_logs_5MbY.zip), there were no camera errors or timeouts there either.  The only time guiding stopped was after the stop button was clicked.

Looking at your next set of logs (PHD2_logs_LLqV.zip) I see guiding stopping mostly from an imaging app telling PHD2 to stop guiding -- no camera errors or timeouts there either.

It would help me to better understand what the actual problem is.  My current understanding is that you saw guiding stop unexpectedly, right?  If that is the case, then we can diagnose best by starting with the following information:it if you could tell us a time or times when it happened, and a debug log spanning that time interval.  We can then look at the debug log to see exactly why PHD2 stopped.

Andy

[Andy Galasso]

Oops hit send accidentally.

The second paragraph was in the process of being edited to say:

If that is the case, then we can diagnose the issue by starting with the following information:

   - an approximate time of one of the incidents where guiding stopped unexpectedly

   - a debug log spanning the time interval

From there we can look at the debug log and see exactly why guiding stopped.

Andy

[Han K]

Andy,

The problem isn't that the guiding stops, no the problem is that the guiding doesn't start. If you start/stop the guiding a few times (manually or via the server), there comes a situation where PHD2 is showing continuous message looping, but the guide button isn't becoming green. For my setup this means that the acquisition program CCDCiel is waiting for PHD2 to proceed which never happens. Maybe it is not related to the QHY5 or maybe it is short communication problem but PHD2 hangs in "looping".  I will today do an experiment with continuous guiding (hours) but don't expect that will be problem.

Han

[Han K]

Hello Andy,

Here an example of an problem with 2.6.7:

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

Stop button is clicked at 20:06:42.677

An capturing error occurs at 20:06:42.739 and 20:06:42.895.

Then the loop button is pressed two seconds later at 20:06:44.830, After that it never reaches status "start capturing". PHD2 indicates permanently "looping" up to the stop button is clicked 10 minutes later at 20:16:47.645. So it is not recovering from the capture error which happens immediately after the stop button clicked at 20:06:42.677. This behavior doesn't happen with the versions up to 2.6.6dev2

Han

 

20:06:42.677 14.820 3684 Stop button clicked
20:06:42.677 00.000 3684 StopCapturing CaptureActive=1 continueCapturing=1 exposurePending=1
20:06:42.677 00.000 3684 Status Line: Waiting for devices...
20:06:42.739 00.062 748 Error thrown from C:\cygwin\home\agalasso\projects\phd2\worker_thread.cpp:157->Capture failed
20:06:42.739 00.000 748 worker thread done servicing request
20:06:42.739 00.000 3684 OnExposeComplete: enter
20:06:42.739 00.000 3684 OnExposeComplete: Capture Error reported
20:06:42.739 00.000 3684 StopCapturing CaptureActive=1 continueCapturing=0 exposurePending=0
20:06:42.739 00.000 3684 Mount: notify guiding stopped
20:06:42.739 00.000 3684 Changing from state GUIDING to STOP
20:06:42.739 00.000 3684 guider state => SELECTED
20:06:42.739 00.000 3684 UpdateImageDisplay: Size=(1280,1024) min=0, max=69, FiltMin=0, FiltMax=12, Gamma=1.350
20:06:42.895 00.156 3684 Changing from state SELECTED to UNINITIALIZED
20:06:42.895 00.000 3684 guider state => SELECTING
20:06:42.895 00.000 3684 Status Line: Stopped.
20:06:42.895 00.000 3684 Error thrown from C:\cygwin\home\agalasso\projects\phd2\myframe_events.cpp:488->Error reported capturing image
20:06:44.830 01.935 3684 StartLoopingInteractive: Loop button clicked
20:06:44.830 00.000 3684 Status Line: Looping
20:06:44.845 00.015 3684 StartCapturing CaptureActive=0 continueCapturing=0 exposurePending=0
20:06:44.845 00.000 3684 ScheduleExposure(15000,3,0) exposurePending=0
20:06:44.845 00.000 3684 Enqueuing Expose request
20:06:44.845 00.000 748 Worker thread wakes up
20:06:44.845 00.000 748 worker thread servicing REQUEST_EXPOSE 15000
20:06:44.845 00.000 748 Handling exposure in thread, d=15000 o=3 r=(0,0,0,0)
20:16:47.645 602.800 3684 Stop button clicked

[bw_msgboard]

Thanks for identifying the time range Han, but we need to see the *entire* debug log file, not just the snippet.  We want to see whole context of the session.

 

Thanks!

Bruce

 

---

From: open-phd...@googlegroups.com [mailto:open-phd...@googlegroups.com] On Behalf Of Han K
Sent: Monday, March 16, 2020 1:56 PM
To: Open PHD Guiding
Subject: Re: [open-phd-guiding] Re: PHD2 2.6.7 unreliable with QHY5-II. Hangs on "waiting for devices"

 

Hello Andy,

--

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/16f91644-96a0-446e-81c3-7cd68f1569f2%40googlegroups.com.

[Han K]

Bruce,

The link to the zip file is already in the previous mail but here it is again:

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

Regards,  Han

[Andy Galasso]

Han,

When the stop button is clicked in the middle of an exposure (15s exposures in your case), PHD2 logs that in the debug log as "capture failed" -- there's no actual failure from the camera; camera errors show up differently in the log as alert messages.  I just wanted to clear this up so we do not continue interpreting lines like these as camera errors:

20:06:42.677 14.820 3684 Stop button clicked
20:06:42.677 00.000 3684 StopCapturing CaptureActive=1 continueCapturing=1 exposurePending=1
20:06:42.677 00.000 3684 Status Line: Waiting for devices...
20:06:42.739 00.062 748 Error thrown from C:\cygwin\home\agalasso\projects\phd2\worker_thread.cpp:157->Capture failed

The real problem is here:

20:06:44.845 00.000 748 worker thread servicing REQUEST_EXPOSE 15000
20:06:44.845 00.000 748 Handling exposure in thread, d=15000 o=3 r=(0,0,0,0)
20:16:47.645 602.800 3684 Stop button clicked

The message "Handling exposure in thread" is from the camera worker thread indicating it is starting a 15s exposure. We expect to see a line "Exposure complete" about 15s later, but we see nothing for ~10 min until the Stop button was clicked.  This tells us that one of the QHY SDK function calls in the camera worker thread has not returned - this could be a symptom of a problem with the qhy driver, the sdk, or the camera hardware.

I can't think of any other reason right now.  We could add some additional logging around the QHY SDK calls to see specifically which call was stuck.

FWIW, I have tested 2.6.7 with a QHY5L-II-C and 15s exposures and I do not see any unexpected behavior, so we need to figure out what is different with your setup.   Maybe you could try the experiment on a different PC and see if the problem happens there too?

Andy

[Han K]

Hello Andy,

I could hook a different PC (laptop) to test it. But with lack of clear sky, PHD2 first want's to do a calibration. So how can I transfer the existing calibration to a new PC. I assume it is located somewhere in  c:\users?

The 15 seconds exposure where selected to allow testing using a hot pixel for guiding. It also happens with 3 or 5 seconds exposure.

By the way, last night v2.6.6 worked flawlessly 5 hours under clear sky using the same setup.

Han

[Han K]

I have done a test with a direct USB2.0 cable to the QHY5II instead of the 10 meter active USB3.0 cable + AS1600 hub. Same problem, no improvement.

Han

[Andy Galasso]

Han,

It looks like one of the changes we made for the the QHY camera in the Mac version of PHD2 in the 2.6.7 development cycle may be impacting the Windows version and causing the problem.

Here's a test executable https://openphdguiding.org/phd2-2.6.7qhystoptest1.exe -- it is just the phd2.exe executable, not a full installer, so to test it you'll need to put it in your PHD2 folder (ordinarily C:\Program Files (x86)\PHDGuiding2\) and rename it to "phd2.exe".  You can rename the existing phd2.exe first so you still have it available without needing to re-run the installer to get it back.   If you are not comfortable moving files around like that, please let me know and we'll build you an installer.

Please let us know if this solves the problem.  If not, we can dig deeper.

Andy

[Han K]

Hi Andy,

That solves the problem! This version works well. No more start/stop problems.

I did an extensive start/stop test using a sequence to image 40 objects. v2.6.7 hangs at the second object. The corrected version succeeded in imaging all 40 objects.

Thanks!

Han :)

[Andy Galasso]

Hi Han,

Thanks for the testing and I'm glad to hear that it is working. We'll get that fix into the forthcoming dev release. For now you can continue using the test version... it will be pretty much the same as the next dev version.

Andy

[Simon d'Entremont]

Thanks for this.  I was in the same boat. Looking forward to the update.   

[Pierre D’Entremont]

I have the same issue. I too am waiting for the fix.

[bw_msgboard]

Hi guys.  The fix was released a few days ago in the dev1 development release:  PHD2 will install that for you automatically if you choose to apply dev releases:

 

 

https://openphdguiding.org/development-snapshots/

 

Please let us know how it goes.

 

Bruce

 

 

 

---

From: open-phd...@googlegroups.com [mailto:open-phd...@googlegroups.com] On Behalf Of Pierre D’Entremont
Sent: Thursday, April 02, 2020 6:55 PM
To: Open PHD Guiding
Subject: Re: [open-phd-guiding] Re: PHD2 2.6.7 unreliable with QHY5-II. Hangs on "waiting for devices"

 

I have the same issue. I too am waiting for the fix.

--

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/65adb0ba-b1bb-4d43-8703-93e156ac691d%40googlegroups.com.

[Pierre D’Entremont]

The auto update did not catch this last night. On seeing you response, I cycled through the two possible setting for update and finally got the dev1 to show. Now to wait for night and test again. Thanks for the note and the screen shot.

Pierre

On Thursday, April 2, 2020 at 10:24:25 PM UTC-4, bw_msgboard wrote:

Hi guys.  The fix was released a few days ago in the dev1 development release:  PHD2 will install that for you automatically if you choose to apply dev releases:

 

 

https://openphdguiding.org/development-snapshots/

 

Please let us know how it goes.

 

Bruce

 

 

 

---

From: open-phd...@googlegroups.com [mailto:open-phd...@googlegroups.com] On Behalf Of Pierre D’Entremont
Sent: Thursday, April 02, 2020 6:55 PM
To: Open PHD Guiding
Subject: Re: [open-phd-guiding] Re: PHD2 2.6.7 unreliable with QHY5-II. Hangs on "waiting for devices"

 

I have the same issue. I too am waiting for the fix.

On Wednesday, 1 April 2020 08:15:05 UTC-4, Simon d'Entremont wrote:

On Sunday, March 29, 2020 at 2:33:26 AM UTC-3, Andy Galasso wrote:

Hi Han,

Thanks for the testing and I'm glad to hear that it is working. We'll get that fix into the forthcoming dev release. For now you can continue using the test version... it will be pretty much the same as the next dev version.

Andy

 

 

Thanks for this.  I was in the same boat. Looking forward to the update.   

--
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.