Hello Cloudy Nights peeps. I have an older ASI120MC that I bought way back in 2015 when they were new, therefore it is the USB 2.0 version which I think might have something to do with my issue. A while back when I got my ASI174MM-Cool, my idea was to use the 120 for guiding. I ran into issues almost immediately with PHD2 first. I had no trouble setting up the profile using the brain wizard in PHD2, and by itself PHD2 would power the 120 and work via USB and ST4 cables. However once I try to do the same thing with the 174 also plugged in, PHD2 bypasses the 120 and tries to guide with the 174. I got messages about a sudden change in pixel size and dark libraries not matching. To bypass this, I just got everything running with in PHD2 with the 174 unplugged. This worked for a while as I was using Firecapture for my acquisition.
I recently decided it was time to step up to the big leagues with NINA. I ran into similar issues with NINA. I don't remember what error message I was getting initially when I tried to open PHD2 through NINA but it wasn't working. I thought I had come up with a similar workaround, just open PHD2 first, initialize the camera and then open NINA and power everything up. Well this was all well and good in practice runs in my living room. But when it came time to capture M82 last week, I got a message about Pulse guiding failure when I tried to find a star to guide on. So it's back to ST4 until I get a new camera or different guiding software I guess.
So after that long rant, has anyone else ran into similar issues when trying to use their ASI120MC for auto guiding? Do people even use these things anymore, or am I the only one?