Re: [Indi-devel] combox and filetransfer

[Jasem M. <mut...@ik...>]

On Tuesday 03 May 2005 5:33 pm, Dirk Huenniger wrote:
> Hello everybody,
> I'm currently trying to write an indi interface for 1m Telescope in
> Germany. I have got two questions:
>
> 1) Combobox
> There is Filterbox attached. And the Gui  has to provide a way to select
> a filter. The Filter Names are "R" "B" "Halpha" and so on. In the old
> GTK gui, I displayed them using a  Combobox. What would be a good
> representation in INDI?  There is a similar Problem. Our CCD Controller
> support various readout modes (for example "Central 512X512 ,single
> binning, Speed 4"), they should also become selectable by user.

Hello Dirk,

For filters, we have come up with a standard that should be adopted by all 
drivers (This is not yet available in Documentation as I'm still working 
toward INDI v0.3 release).

You need to define an INumberVectorProperty with a standard name FILTER_CONF, 
which has one INumber element named FILTER_NUM

There is a driver that supports FLI wheels in the CVS

http://cvs.sourceforge.net/viewcvs.py/indi/indi/src/fli_wheel.c?rev=1.2&view=markup

The client then should support a way for you to assign aliases to filter 
numbers. KStars supports this, refer to 
http://docs.kde.org/en/HEAD/kdeedu/kstars/indi-capture.html

and

http://docs.kde.org/en/HEAD/kdeedu/kstars/indi-configure.html (read the filter 
related section at the bottom)

> 2) Filetransfer
> Our CCD controller supports a "firmware update" (redefinition of readout
> sequences). The aquisition system supports a "batch mode". And the
> controller has got a "script mode". It would be nice if there was an
> indi element that opens a file selection dialog on click and starts a
> binary transfer of the data contained in the selected file, as soon as
> an OK button is clicked. Ok I agree this functions are unlikely to be
> used by an ordinary astronomer. But the technical staff would be glad to
> have them at hand, when an astronomer calles them at home in the middle
> of th night.

Both KStars and Xephem support this, you just need to define Read/Write blob 
property.

For an example, try to modify any BLOB property in any driver to be IP_RW (All 
CCD drivers have BLOB properties). Compile the driver, then run KStars or 
Xephem and you'll see that you can upload a file to the driver.

Cheers,
Jasem