Add cooler shutoff time delay when software disconnects

nicklin

Hi,

I've read a thread from last year stating that coolers are turned off "for safety reasons" when software disconnects. I agree it would be bad for a cooler to be left on indefinitely, however instant shutoff also causes significant problems.

Use case 1: I'm testing to see if the banding issues with the ASI 178 are resolved (which don't appear to be unfortunately despite other reports :( ), so I'm stopping and starting software, swapping drivers, switching between sharpcap, SGP etc. I'm testing at -10 and when software disconnects, the temperature can jump well above zero in just a few seconds. This may increase thermal shock and extends the testing process as I don't want the camera to drop 20 degrees or more as fast as it can, and even if I did, it still takes time.

Use case 2: simply normal use. It's not uncommon to need to close and restart imaging software for one reason or another during an overall imaging session, switch camera to a different port or machine, change software and so on. Whatever the reason, it's a real issue if the cooler shuts down.

Suggestion: a cooler switch off time delay, ideally configurable. A default of 5 minutes would seem a good start. This would ensure the cooler remains active during a brief disconnect, be kinder to the camera and save time at reconnect. This simple active management could also offer gradual heating after shutdown timeout to again be kinder to the camera if the user disconnected and did leave the power on at the end of an imaging session.

chad

Hi，

First, I agree with you. But there's still a lot to think about.

Usually, The safety factor is not this thermal shock or other problems on the hardware. More often, we mean the software.

As we know, cooling also requires control. So if you want to cool, the control chip has to run. At this point, we have a serious problem. if we disconnect the USB, but only keep the 12V. If it is cool, now the control chip will run out of the SDK's control. At this moment, If there is a problem, we have no way to know and stop it, beside, the user also could not find the problem. In our debugging, sometimes the heat is so great that the camera burns people.

For a new connection, usually, we need to initialize the chip to make it work normally. In this way, it is hard for us to judge if we should initialize the camera.

More, some application makes the the cooling turn off as the default after connection. They will not operate the SDK to close the cooling.

It's just a matter of use. There are a number of other uncertainties to consider in software development. The cost is not worth it.

All ideas and Suggestions are open to discussion.

Thanks

Chad

nicklin

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

chad

Hi,

There is no fire, just too hot, maybe around 60-70 degrees. I got burned several times. You know, even there is no fire, but this temperature is still dangerous.

And for the control, yes, if this function is developed, it should be run in the Firmware. But in general, firmware is only the most basic functionality to run. In the design of temperature control, the important thing we need is a timer. But in programming, the timer is already a very complex and advanced function。

Thanks

Chad

pleiades

Hi,

I'm still having an ST-10XME SBIG camera and the cooler will remain active even after a disconnect. Sometime MaximDL or other software began to malfunction for any reasons and most of time the only solution is to reboot the computer or close the camera application. At each time you need to cool down the CMOS chip from the start.

The driver should have an option to let the cooler system active even if it's disconnect. I'm new with ZWO camera and find it's really a HUGE disadvantage.

BTW, how much memory (RAM) needed to stack ASI6200MM images ? Presently, I'm only able to stack two images at the time with the ZWO software or MaximDL. Thanks !!!

Regards,
Yves

Tech@ZWO

pleiades
8GB at least, recommned 16G and above.