[ASCOM] Re: Camera V2 Standard
- Doug, Matt,
Ok, sounds reasonable.
Could I ask for a simple implementation note in the cooler control and/or disconnect sections of the spec stating the expectation for the driver to do ramping there if required?
As Matt notes, presumably the call will block during warmup.
--- In ASCOM-Talk@yahoogroups.com, "Douglas B. George" <dg@...> wrote:
> John wrote:
> > I can't quite see how that would work in the real world. You're suggesting
> > the app sets the cooler temp setpoint to some high value (since it doesn't
> > know what ambient is) and monitors the cooler power to know when it's safe to
> > turn the cooler off? What if the camera doesn't support providing power
> > readout?
> For many cameras there is no such thing as "off". For example, one higher-end
> camera I frequently use regulates at about +11 degrees C when it is "off".
> "Off" isn't relevant. The *only* reason to worry about "off" is thermal shock,
> and the risk of that is very overblown. The thermal conductivity of the stack
> isn't that high; otherwise you'd never get the chip cold in the first place!
> There are two use cases:
> 1. Remote automation. The software will command the camera to warm up, and
> then ignore it. Onboard firmware takes care of the warm-up procedure, if any is
> 2. User running the show locally. User waits for the cooler power to drop,
> then unplugs the camera. If no cooler display, user waits until the temperature
> warms up, then unplugs the camera.
> Also, I should mention that most manufacturers recommend you leave the cooler
> on, if you are not planning to unplug the camera.
> I don't see that there is a software issue here. At most the camera's user
> manual should have some advice to the user.
> > Wouldn't it be more "device independent" to hide it in the driver and let the
> > driver decide when it is done. For some cameras with low dT, it would return
> > immediately, others would do the ramp internally and return once it's
> > complete to whatever level is required.
> If ramping is required it should be done by the manufacturer's hardware and
> software. It shouldn't even be an issue for the API.
> Doug George
> Diffraction Limited
> Makers of Cyanogen Imaging Products
> 100 Craig Henry Dr., Suite 202
> Ottawa, Ontario,
> Canada, K2G 5W3
> Phone: (613) 225-2732
> Fax: (613) 225-9688
> I need to stop wasting time on justifying the last 10 years of decisionsMove on is right! Those guys designed the interface they wanted, with a great
> (most of which were not mine) and concentrate on moving forward.
deal of compromise and negotiation. Throwing it back in their face now is just