I am using an ASI 1600 mmcool. I had problems making flats with the ccd flats aid tool of astro photography tool.
The problem was that suddenly, after some time, he camera appeared busy, yet no image was made or downloaded.
I tried everything: From a different usb cable to a different usb speed. The problem only went away after I checked the box "disable min exposure check". A post in the apt forum suggests that this is a driver problem with the ascom driver.
after checking this box, apt then worked flawlessly....
unfortunately, the problem happened again...
Well I only get this problem with the ccd flats aid in astrophotography tool which you can download here for free....
I use windows 7 and the newest ascom drivers for the asi 1600 mono cool
I use the ccd flats aid tool there to create a flats plan for all 8 filters...
Often sometimes, the camera will work for a time but then, say during the h alpha filter, just say it is busy and hang in the process. Clearly there is a hang somewhere and the camera only works again when I disconnect it from apt and restart apt.. This is unfortunate as it takes time to warm the camera up and cool it down again... this still works fortunately..
Some other people have this problem as you can see here
It never appeared to happen during imaging on my pc. But this maybe because deep sky imagng is always longer than 10 seconds. On my pc it only occurs during flats aid, where the application roams through different exposures in order to find the optimal time, or during taking flats which often take very faat exposure times....
settings are usb lowest speed setting. And I use a rather long usb 3 cable... but it should be within the usb3 specs (2 or 3 meters, I guess).
And instead of making an error message or simply begin to go to the next image, the camera hangs immediately...
This would somewhat explain why it does not happen during 10 seconds exposure but only during fast flats...
One possible reason: As the length of the USB cable increases, the resistance of the wire increases, resulting in unstable connection. Especially when the high-speed signal begins to transmit, it is more likely to fail.
In this case, it hard for the camera to give out a result. As we know, we use the USB to communication between PC and camera, and the USB support the hot-plug, it means when the data is lost, it doesn't just mean that the connection is unstable, it could be disconnected. Another situation, unstable connection cause a short re-connect between camera and PC, for our camera, power restart means a reset operation, in this situation, the camera is fresh for the system.
Now we have tried many ways to solve this kind of unstable problem, but there still have some situation could not fit. In a word, the problems need us work together to solve it.
perhaps one may add a function restart without loosing access to the cooler... that would help a bit...
When the problem occurs, you just want to reconnect the USB port without reconnect the external power. Am I right?
Sorry, this is not working right now. According to our design, Part of the firmware is independent of running, as long as there is power, it will always run, not controlled by USB. So if you want to restart the camera, you have to reconnect the external power and USB at the moment. Maybe we can improve it in the future.