2600 and 120 (Both USB3) - seem to be in conflict on OSX

jays_ct

All,
I've been imaging on my Macbook Pro very happily with Starlight Xpress cameras and ZWO 120 Mono (USB 3) as a guide scope. Use AstroImager, PHD2, SkyX, etc. Everything running through a Pegasus Astro Ultimate Power Box V2. No issues at all. I introduced the 2600MC into the mix as the imaging camera and it just seems the two cameras are in conflict for USB resources. I've tried the 120 on both the USB 3 and USB 2 ports of the Power Box, into the back of the 2600 so both travel on the single USB 3 connection to the Power Box, different ports on the Macbook Pro, etc.. Other than running two USB cables (which I didn't try and hope not to have to) I am stumped. The software recognizes the cameras, but start PHD2 (for example) connect the 120, and the 2600 fan stops, and it loses its connection to the imaging software. I really am stymied on a working combination. Is anyone running the 2600 with the newer 120 (as a guider) on OSX succesfully? Appreciate any suggestions...

Jay S.

Tech@ZWO

I recall this issue has been brought up somewhere, it seems there is conflict between PHD and SkyX.

jays_ct

Thanks for the reply... Isn't just SkyX.. Happening with all the OSX based packages I have.. :-( Again, no such issue with my Starlight Xpress cameras. What do I need to do to get to use the 2600 and the 120 on native OSX? It is also a problem using other Guiding Programs that are native to OSX.. It seems to point to the 2600 wanting some control? The ASI new app doesn't seem to have a lot of control over the cameras, but perhaps I'm missing something?

jays_ct

Anyone?? I'd like to hear from some folks on OSX to understand if I have a camera problem or not, or if the 120 and 2600 have resource conflicts.. Just to be sure, I reconnected a Starlight Xpress camera and PHD2, the SX camera and the 120 all played nice... Seems like it's either the 2600 or the 120 or the combo.. :-(

Tech@ZWO

jays_ct
Can you remove Pegasus power box to try it again? We have been receiving lot of issues using it.

jays_ct

Hello.. Is not the Pegasus and I was able to get them both working. My belief is that most software uses a single ASI Camera driver. That being the case, and without the imaging or guiding software "checking" (or perhaps having an interface in your code to check) for which camera may be in use or allocated already, there are going to be conflicts. As long as the software offered a way to separate which camera is doing which function, it will work as it should. AstroImager and AstroGuider talk to one another and so the two programs are aware that one camera is taken. Two discrete packages don't necessarily share that information.

mcerono

I had the same issue with my 120mm and 294mc pro on my macbook pro 3 years ago. This issue does not exist on native windows devices.

I used a satechi usb dongle with my macbook and the issue was present in phd2 and APT. As soon as I used single original apple usb-c to USB adapters for both cameras the issue was gone.

jays_ct

Thanks.. This was a standard USB 3, not USB-C but will look into that. Have a new MBP that I'm converting things over to so this will help. :-)