See this Comm Center thread by Andre Ioda. Turning the cooler off in the web user interface has no effect. The cooler remains on.



Also, unless the Cooler link int he web UI is used to turn on the cooler, there are conditions under which it reads OFF even if the cooler is running and temp is down.



Reopened. Change in 6.05 for the better. 

 

  
SVN Comment
 
 

  
Author
  
rbdenny
 
 

  
Repository
  
svn+ssh://rbdenny@a2_svn_dc3/home/rbdenny/svn/astro/acp
 
 

  
SVN Revision
  
745
 
 

  
Affected files
  
/trunk/ACP Help/relnotes.htm (Modified)
/trunk/WebDocs/ac/asystemstatus.asp (Modified)
/trunk/WebDocs/ac/atempctrl.asp (Modified)

 
 

  
Check-in comment
  
Clean up web System Status cooler control logic. Remove ancient hackery for long-since fixed (years ago) MaxIm bug.
GEM:1026

 

Even for MaxIm 5.24 and V6 before 6.05, the logic could be simplified and hacks removed. There is a difference in the camera startup which causes 20 deg to show for a while, so I added -wait- for that short period. This works great now with all of the trash cleaned out. On 6.05, turning the cooler on with the MaxIm UI causes the web UI to reflect it at the next refresh. Perfect.

Reopened. Look at the logic in atempctrl.asp. Doug and I hacked something in the past, and now they have done what was needed on their end. But now the CoolerOn = true followed by an immediate setting of the temp causes the cooler switch to fail. Will need separate logic for before and after. The net result is that it will work right without weird quirks!!

Diffraction confirms that this is the behavior of CCDCamera.CoolerOn inn their API. If/when they fix this the ACP web UI will just work. Closing as Not an Issue.

Interesting! With the cooler running at -35, the CCDCamera.CoolerOn boolean comes back False. MaxIm ticket #1277 filed.