StarChaser 4

Paramount MX+
SBIG Aluma AC4040
SBIG AFW-10
SBIG StarChaser SC-4
SBIG AO-X
12th Gen Intel(R) Core(TM) i5-12400 2.50 GHz, 32GB RAM
Main, guider and mount are connected through independent, PCI-based, USB3 hubs (i.e. data transmission should not be a problem).

 

Then its clearly not a peripheral that is causing this, but the SC4 and/or Maxim DL

Last night, I calibrated, bin 1x1, guided bin 4x4, dropped the Max Move pixels to 9 as suggested by Doug, and took 10 x 5 minute images.....every single one showed star trails indicative of the random jumping of the guide star.

 

Colin....I think I have spotted the problem. I uninstalled the ASCOM x64 driver for the SC4....and now PHD2 does not even offer "DL Imaging Camera" as an option even though the 32bit ASCOM driver is still installed, which supports my earlier view that PHD2 could only 'see' the 64bit driver. So I reinstalled the 32bit driver and again it loads the information for the camera but then throws the unhandled exception.

 

Are you guys able to switch to standard autoguiding? If the problems stays or goes away that might confirm if it is the AO unit or not.

 

For the past year or so I have been using the SC4 as a standard guider through PHD2 with an AOX in train, but disconnected....but now with V7.14 and the latest 32bit ASCOM driver for the SC4, I cannot connect to it. Thinking that my AOX perhaps was defective, I went to Chile in Jan this year with a replacement, and its exactly the same.

Colin - really need to get the SC4 connected to PHD2 as I have nothing to guide with at present. Very happy for you to log in to my system if you think you know where the problem is.