flawlessly for two years. So trying to track down the specific thing that is happening here so I can address it. In the last 3 months I did start to get random disconnects of the mount. I

the same problem. It's down to the ASI drivers. The solution I found was to us ASCOM drivers for your ASI cameras. PHD2 doesn't get confused that way. On Saturday, 5 April 2025

slew or two. > > —david > > > On Sun, Mar 16, 2025 at 12:01 PM Brian Valente wrote: > >> Kelvin >> >> Do you have a manual or automatic rotator? If you

ZWO guide cameras so I can at least take a look at the > 8/16bit issue but the gain value being a percentage is a far larger change > to the app that affects everyone. > > >

is an ASI 290mm mini). >>>>>>> Good to know - the calibration and guiding assistant routines seemed >>>>>>> to be happy. I wasn'

also uses two instances to control my >>>> tandem setup so I have written Advanced Sequences in NINA to try to emulate >>>> what Voyager already does. I think

for both cameras is > that they always work. Always. > > George > > Sent from my iPhone > > On Oct 14, 2024, at 8:43 AM, Brian Valente wrote: > >  > > Don

fix the problem. If you don't get the e-mail, >> please let me know asap. >> >> Thanks, >> Bruce >> >> On Tuesday, August 20, 2024 at 11:29

the RA problem is fixed, and guide pulses now cause RA axis to move in correct direction. *AGAIN* - nothing changed in NINA or mount software, didn't even stop the NINA sequence.

/guide cameras. I assume this will be needed. >> >> Q re OAG. It seems to me that some ability to focus via the OAG (eg, >> Helix focuser) would be worth the extra $. I

>> cameras also. Thanks again! >> >> Best, >> Dan >> >> PS-- Bruce, On you tube I heard a talk you gave on PHD2 and you described >> how guiding

for ZWO cameras. ASI ZWO Camera, ASI >> ASCOM (1), and ASI ASCOM (2). I selected each driver to see which pixel >> size would auto populate - only one would and that is ASI ASCOM

sure the cameras stay connected correctly. If you suddenly see an > alert message that your dark library is incompatible with the camera, you > will know that the ZWO software

to the asi 220 half of the DUO by selecting either the Ascom(1) driver as you did, or the Zwo. Ascom driver gives a lot more options. I do have the latest Zwo drivers as well as ASCOM. Just

Hi Andy-san, "Calibration Assistant" I will provide the translated files related, please update. regards, nabePla 2023年5月20日土曜日 12:14:20 UTC+

switch between cameras for testing, build separate PHD2 profiles for each camera setup. https://openphdguiding.org/development-snapshots/ If you are using two ZWO cameras at

zwo > ASI imaging package about 2 weeks ago. > > HOWEVER<............ I was unaware of the ZWO driver upgrade release > 1/12/23 vs 3.21....soooooooooooooo....I have

I have two scopes mounted with a DSLR on one and a QHY 367C on the other. > I guide successfully with an OAG and a ZWO 174. However, I was curious > what it would happen if I try to guide

between the two > cameras. I would suggest you review the spacing for both cameras to insure > it is correct to bring them both to focus. Then I would verify that the > spacers

the same problem. Bruce From: open-phd-guiding@googlegroups.com [mailto:open-phd-guiding@googlegroups.com] On Behalf Of Mark Theissen Sent: Sunday, February 5, 2023 11:

>ZWO ASI Camera is now assigned to the ASI120mm mini. > > > this was likely your issue, but i just want to re-emphaisize this can be > an ongoing problem caused by the ZWO

think the problem is how I have the ZWO camera drivers assigned in the PHD2 Camera Connect setting. Currently, I have the "ZWO Camera" assigned to the "Camera"

find the problem quickly. > > > > Regards, > > Bruce > > > In some cases, you may experience problems where guider images are not > downloaded or displayed

do have two ASI cameras... not sure what that message was about or if I had already disconnected the guide camera when the error was reported. I did not see it during the guiding session

a particular problem in the mount, the guide cable, or much less likely, the ASCOM driver for the mount." The guide cables have been replaced twice and are held in place with a support

having this problem. >>>>>> >>>>>> Good luck, >>>>>> Bruce >>>>>> >>>>>>

solved the problem, but I think it had something to do with SharpCap 2.9 which didn't play nice with the latest version of ASCOM (6.5?). I got SharpCap v3, but I also upgraded to an

camera the ASI 1600 when setting up a new profile. Hope that works. If that does not work I see there is talk of only using only ZWO drivers and not ASCOM. Will try that has plan B. Best Eric

> both cameras conneted to a USB HUB or ASIAIR, or you've connected each > camera to a diferent USB Port on your PC? > > Thanks in advance for your help!!! > Frank >

, the problem in Indi/Eqmod is now confirmed and it will be fixed. Short guiding pulses were causing the error, especially when changing direction. Details are under the GitHub link