Hi Ken & Jared,
I’m embarassed to say I thought I was responding to my buddy dts350z/Glenn! I’m leaving on Friday morning for a trip to Portal Arizona and just a little stressed. I actually was planning on testing something out that Gaston suggested that might relieve the instability but I’m tied up at work and it looks like it’s not gonna happen tonight. I think the safest bet at this point is to go with what I know works and pick it up after I get back and try and get ready for the next trip down the road. Part of the trouble I’m having is related to the fact that I’m using identical ASI 1600 MM pro cameras for both guiding and imaging. It makes it a little difficult to get it going without crashing the camera driver and i’m not sure if there’s anything that can be done about it other than using a different camera for either guiding or imaging. I’ve been using the OPTEC Ascom Hub to get everything connected. If there was an easy way to specify one camera for imaging and one camera for guiding it would be great but it seems that the first camera that gets connected it is assigned camera ID zero and the second connected is camera ID one. In order to get this going I have to actually physically disconnect the guide camera before physically having the imaging camera connected and connecting it via software. For now I’ll stick with my DSI pro two for guiding which unfortunately doesn’t have an ascom driver so won’t work with SkyGuard.
I really appreciate you guys working on this!
Thanks so much,