On 29 Sep 2021, at 6:03 am, Manu Manu <manuma...@gmail.com> wrote:
Hello all,Hello Bill. I experience the same issue with exposures more than 3 secondes. If exposure is less than 3 sec there is no lag. With dark substraction it is worth. Could check this? Or did you solve the issue? CS--Le jeudi 31 décembre 2020 à 21:28:32 UTC+1, Bill Stent a écrit :Yes, that was one of the tests I did on the spot. It turns out that an ASI1600MM-Pro is an excellent guide camera!> There are two distinct ASI cameras I can connect toI've seen the same timeout when PHD2 accidently connected to the wrong ASI camera.Quick test: Only plug in your guide cam (and leave your imaging cam disconnected from your laptop) and see if you still see the same problem.And I've also seen the order of the ASI camera switch after updating the ASI drivers (this is what triggered the problem for me), so I then had to update my PHD2 profile to point it to the right ASI camera.--On Thursday, December 31, 2020 at 6:43:00 AM UTC-8 George wrote:And then you had to deal with film. Didn't even know if you got anything for days.On Thu, Dec 31, 2020 at 6:53 AM Bill Stent <bill...@gmail.com> wrote:--Nope. I was done with that in the 1970s. Standing next to the pier with the RA slow motion in your hand, trying not to breathe for a 15 minute exposure is ok for kids but not for me.Happy New Year All. The folks that pilot this forum have done an outstanding job this year.The time that you all donate to help others is appreciated by all.I can offer one tip that works for me.Before jumping in to PhD guiding, learn to guide by hand first. Get a guiding eyepiece with illuminated crosshairsand see if you can guide with your hand controller. See if you can take some decent images guiding by hand, the way ol' Sandage and Arp did it with the 60 inch. You will learn a great deal about your mount and how it operates. You will learn the importance of polar alignment and how accurate is good enough. You will appreciate how the great ones that came before us got it done.--On Wed, Dec 30, 2020 at 9:53 AM bw_msgboard <bw_m...@earthlink.net> wrote:--You should read the trouble-shooting section of the manual because one of the sections (camera time-outs) describes procedures for isolating the source of the problems. Most of this can be done in the daytime so it can be less frustrating.
https://openphdguiding.org/manual/?section=Trouble_shooting.htm#Problems-_Camera_Timeouts
Good luck,
Bruce
From: open-phd...@googlegroups.com [mailto:open-phd...@googlegroups.com] On Behalf Of Bill Stent
Sent: Tuesday, December 29, 2020 10:31 PM
To: Open PHD Guiding
Subject: [open-phd-guiding] Inconsistent timeouts with an ASI120MM
I'm really confused. I'm not even sure where if this is the right place to ask, so bear with me...
Last night I was out at the dark sky site after about eight months of lockdown, and PHD (v.2.6.9 dev2) was unable to get frames from my guide camera. Specifically, it gave the message that says that after 18 seconds (my intended 3s exposure plus a 15 second wait) the camera had not completed an exposure.
SharpCap 2.9 was able to get a frame or two, but very sporadically - like every five minutes or so. I went back to the PHD v2.6.9 that had worked previously - no difference. I changed cables and USB ports, even using the one in the back of the ASI1600MM-P, no effect. I suspected at the time that the camera - a ZWO120MM - had died or was dying. I was able to control the mount without a problem, and that's through a EQMOD cable off the same powered hub that the guide camera is plugged into, so I think the USB port is OK.
Back at home, I decided to do some diagnostics. I installed ASCOM 6.5 sp1 in my desktop, as well as PHD2 v2.6.9 (not the dev version). Plugging the guide camera into a USB port, I was surprised to see everything seems to work. PHD was only able to give me a bright and badly focused image at .01s, but it was refreshing very quicly as I moved the camera and guide scope around.
So the camera works and the cable is good. I think.
So then I reinstalled the latest versions of ASCOM and PHD2 (including the ZWO latest native drivers) and tried again on the laptop. No difference. I changed USB ports, no difference. There are two distinct ASI cameras I can connect to: the ZWO ASI camera (which I think is the native driver, and correctly disambiguates into ZWO ASI120MM) and the ASI Camera (1) (ASCOM) pair, which I can drill down to a dialogue called ASICamera setup v6.5.16.0, and I think this is the ZWO ASCOM driver talking to me. Neither has any effect - I still get the timeout error.
I've heard people talking about power management. Could this be a possibility? As far as I know, the laptop doesn't turn off any USB ports while it's plugged in - which it was.
I've also heard about USB traffic, which you can change in FireCapture. Again, I know nothing about USB traffic, but setting it in FC to about half way up the slider gives me more frames, but FC sporadically telling me that the capture has failed. If I move it down it seems to get fewer, and it comes and goes. Can you change USB traffic in PHD?
So USB traffic might have something to do with it - but I'm not sure if the drivers that FireCapture uses are the same as the ones PHD uses. (In fact I'm pretty sure PHD uses ASCOM and FireCapture uses some windows drivers.
Can anyone suggest some other diagnostics for me to test out?--
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/b892789d-eb08-4ca9-9005-6a053f3ffa56n%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/CDC20128E03C4B40ACDB673B0565F14C%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/6sDLiWtdpUI/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/CAKfhV04mDGKkgLnGokvCXhtrApMOG0q-fjhXkq%3DT%3DtSTHeSJOg%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/2068934C-6F9D-4C75-B071-D0B1A4FD5CCB%40gmail.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/6sDLiWtdpUI/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/5b1d9ea4-8085-4b52-8452-dc4e7daed886n%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/6sDLiWtdpUI/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/0bdfb14b-58ea-4457-8dc7-f8b1225a8df5n%40googlegroups.com.