PhD2 fails to identify asi220 in ZWO2600mm duo

[Chris Carlton]

My asi220 mini guide camera in the asi2600mm duo is not being identified by PhD2. Two ascom cameras are listed (1 and 2). Based on other forum posts, the mini should be no. 2. Both sensors are correctly recognized by ASI Studio and NINA as the 220mini (camera 2) and the 2600mm (camera 1). Selecting either ASCOM camera 1 or 2 in PhD2 brings up the main imaging sensor, confirmed by pixel size shown in PhD and by physically covering the sensors in bench testing, just to be sure. The unspecified ZWO camera choice at the bottom of the list also brings up the main sensor.

I did see a post suggesting replacing the ASCOM camera 2 DLL file in the PhD folder with another one from a ZWO source, but I can't find an equivalent file in any ZWO folders. That post was a couple years old so maybe they have changed how they package the files in the driver package.

I have refreshed the latest ASCOM Platform, ZWO drivers, ASI Studio, NINA, and PhD2, confirmed as the latest versions. Still bringing up the main camera sensor.

Thanks,
Chris

[Chris Carlton]

On the ZWO/Camera subforum, ZWOtech asked if Device Manager recognized both cameras.  And; "2 Check if any other software is occupying the ASI220mini during guide camera operation."

Response: Yes, both are recognized in Device Manager as 220mini and 2600duo. ASI220 Port 0004.Hub#0002, ASI2600 Port 0013.Hub#0001. Not sure how to check for "other software..."

Waiting for response.

[Bruce Waddington]

To figure this out, please be sure you're running the latest PHD2 dev release, 2.6.13dev7:

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

Repeat the test, then upload your PHD2 debug log file so we can get more information:

https://openphdguiding.org/getting-help/

You can also do a search on our forum for "ZWO duo" and find a number of posts, all from people who have found a way to do what you're trying to do.

Regards,

Bruce

[Chris Carlton]

Well, this is strange. PhD2 now opens the 220 mini when BOTH Ascom ASI cameras are chosen instead of opening the main Duo camera, as it has been doing consistently for five days or so. I have not done any driver, PhD, or other software updates (they were all latest versions) since the previous tests, but something switched the guide camera choices.

I will not argue with the correct path being taken, but still would like to know why it's doing this due to the concern that it might not be a stable arrangement. Today's logs should be here.

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

Thanks,

Chris

[Chris Carlton]

I can see several instances early in the day where the 2600 was chosen, then it changed this afternoon to the 220.

[Brian Valente]

>>> PhD2 now opens the 220 mini when BOTH Ascom ASI cameras are chosen

Can you clarify this comment? I'm not sure what you mean re: both cameras are chosen.

--
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 visit https://groups.google.com/d/msgid/open-phd-guiding/56e753c0-52d2-40e1-b4fc-3b57926ea6f5n%40googlegroups.com.

--

Brian 

Brian Valente

astronomy portfolio https://www.astrobin.com/users/bvalente/ 

[Bruce Waddington]

You've assured us that you're running the latest version of PHD2 but you're not, so that makes things more difficult.  If you go back and look at my previous message, you'll see I asked you to updated to the latest DEV release, 2.6.13dev7 and gave you a link to acquire it:   https://openphdguiding.org/development-snapshots/

The log files you sent from today show you're still running the same baseline release of 2.6.13, not really what we need.

Setting that aside, here is a subset of the many 'connect' operations that you did on 9/9:

09:17:20.101 00.002 7672 Connecting to camera [ASI Camera (2) (ASCOM)] id = []
09:17:20.101 00.000 7672 Create ASCOM Camera: choice 'ASI Camera (2) (ASCOM)' progid ASCOM.ASICamera2_2.Camera
09:17:21.787 01.686 7672 setting camera Name = ZWO ASI2600MM Duo (ASCOM)
09:17:21.805 00.002 7672 PixelSize=3.76

09:18:28.618 00.000 5648 Connecting to camera [ASI Camera (2) (ASCOM)] id = []
09:18:28.635 00.017 5648 Create ASCOM Camera: choice 'ASI Camera (2) (ASCOM)' progid ASCOM.ASICamera2_2.Camera
09:18:29.715 01.080 5648 setting camera Name = ZWO ASI2600MM Duo (ASCOM)
09:18:29.715 00.000 5648 PixelSize=3.76

09:19:26.287 00.000 12704 Connecting to camera [ASI Camera (1) (ASCOM)] id = []
09:19:26.287 00.000 12704 Create ASCOM Camera: choice 'ASI Camera (1) (ASCOM)' progid ASCOM.ASICamera2.Camera
09:19:27.495 01.208 12704 setting camera Name = ZWO ASI2600MM Duo (ASCOM)
09:19:27.495 00.000 12704 PixelSize=3.76

16:03:16.263 00.014 14620 Connecting to camera [ASI Camera (1) (ASCOM)] id = []
16:03:16.265 00.002 14620 Create ASCOM Camera: choice 'ASI Camera (1) (ASCOM)' progid ASCOM.ASICamera2.Camera
16:03:17.160 00.895 14620 setting camera Name = ZWO ASI220MM Mini (ASCOM)
16:03:17.160 00.000 14620 PixelSize=4.00

The important things here are which logical camera number you're telling PHD2 to use.  The first two show connections to ASI camera(2), the second two show connections to ASI camera(1).  Camera(2) seems to map to a ZWO-generated id of ASICamera2_2.Camera.  Camera(1) maps to an identifier of ASICamera2.Camera.  Next, look at the reported pixel sizes for these camera id's - Camera2_2 reports 3.76u in both cases, Camera2 reports 3.76 or 4.0.  None of this has anything to do with PHD2 and I can't make any sense of it.  One important question is whether the camera is always connected to the same USB port and whether you're doing the 'connect' operation the same way each time.  Is that the case?  And why are you switching back and forth between Camera(1) and Camera(2)?  Maybe the ZWO folks can help figure this out.

Good luck,

Bruce

[Chris Carlton]

Sorry, no, choosing both cameras is not possible. Should have been "either" camera, but to be clear.

In the PhD2 camera selection drop down, "asi camera (1) ASCOM" and "...camera (2)...." are the choices. 

In the earlier iteration of this effort, both of the choices (switching from one to the other) opened the main asi2600 sensor. Neither opened the guide camera. This morning, I was getting the same result. This afternoon both choices switched to the asi220 guide camera. I just tried it again. Both camera 1 and 2 brought up the 220. 

[Chris Carlton]

Well, turns out it was a rookie mistake and is now sorted out. I was trying to switch the connection in the wrong sequence initially and gave up...not possible with the camera connected. Duh! Sorry for wasting time. This is the first time I've been required to choose more than one camera initially.

 

Chris