ASI1600MM-C First Gen - No longer working

cuiv

Has anyone every seen these symptoms? Basically my first gen ASI1600MM-C suddenly stopped being able to download exposures to the PC - if the exposure is longer than 0.9 seconds. Shorter exposures work fine.

I tried with multiple USB cables (all of them working fine with my ASI294MC Pro) and multiple computers in SGP and in Sharpcap (native driver and ASCOM, both latest versions), but the result is always the same: 0.8 second or shorter exposures work fine, 0.9 second or longer fail to download.

Obviously I am very sad that my primary workhorse seems to have died unexpectedly, and less than three years after buying it :-(

chad

Hi，

For you 1600MM C, does it have a ST4 port instead of 2*USB2.0?

For failed, does it mean could not download any data?

Thanks

Chad

cuiv

Thanks for the answer Chad!

You are correct, it has an ST4 port instead of the 2*USB2.0. As far as I know it is the very first version of the camera.

This is the behavior I am seeing:

- In Sharpcap with native driver, for exposures less than 0.9 seconds, it drops a lot of frames but still downloads data. For exposures longer than 0.9 seconds, all frames are dropped.

- In SGP with native driver, for exposures less than 0.9 seconds, it seems to work fine, with data. For exposures over 0.9 seconds, it downloads a completely black frame, with no data whatsoever (min, max, median, mean are all 0)

- In SGP with ASCOM driver, for exposures less than 0.9 seconds, it works fine, with data. For exposures over 0.9 seconds it gets stuck on "Downloading......." and never manages to download the frame.

My ASI1600MM-C is plugged into my astronomy PC pretty much all the time, so I could give you TeamViewer access to check if you want.

Thanks you!

Yannick

cuiv

To add to the above, I noticed while testing today that there are brief times when the camera starts working properly for a little bit, and then goes back to not working for exposures longer than 0.9 seconds or so.

Without any changes to the setup of course...

chad

Thanks for your email to our support.

Please following the email's result.

Thanks

Chad