wINDI became INDI Server for Windows (similarly to INDI Server for OSX). Not just because of marketing reasons, but also because of windi virus and a stupid antivirus protection on some operating systems.
In version 2.0 there are also pulse guiding properties available for CCD and Telescope drivers.
Both 32 and 64 bit version is available for download here: www.cloudmakers.eu/windi/
and as usual, any feedback is welcome...
This is excellent, as it comes just at the moment that I want to be able to control an SBIG ST-i from a Windows script. I have downloaded wINDI, and it comes up, but the only CCD cameras available are an ASCOM driver for Nebulosity, and two CCD simulators. I have the SBIG drivers installed, but they do not appear in the options. How do I get wINDI to recognize an SBIG camera??
Second, once I get that part working, is there a simple way to take an image? I am familiar with the Indi library on linux, and have worked through the examples using get_prop and set_prop to take an image (at least with the simulator), but how do I do that in Windows? Can I invoke get_prop and set_prop in the same way (say from a vbasic script or an autoit script), or what must I do?
wINDI simply shows all ASCOM drivers. If you don't see SBIG, you either don't have ASCOM driver installed or you don't have driver for correct architecture (32 vs. 64 bit or something like this). Do you see SBIG in ASCOM from another applications? What OS do you have (32 or 64 bit) and what wINDI you installed? I'm not quite sure, but I think, that Nebulosity is 32 bit executable.
Thanks for your quick reply. As far as I can tell, there are no ASCOM drivers for SBIG cameras. If you know of a source, that would be excellent. I do know how to script ascom components from Autoit and VBscript, so that would work for me.
To answer your other questions, I am using Windows 7, 64 bit.
Hi, if you mean simulators for ASCOM to use with INDI Server for Windows, the answer is yes, for all kinds of devices. But if you mean to test it with Sky Chart (= Cartes du Ciel) as far as I know, it is not included in Windows version. Peter
Thanks for providing this bridge between ASCOM en INDI.
I suggest the following improvement:
The equinox specification from the ASCOM simulator (ASCOM.telescope for NET) is not utilized and ignored. The INDI server is always sending EQUATORIAL_EOD_COORD coordinates ignoring the equinox setting in the ASCOM simulator. (local =(EOD), J2000 or J2050). Ascom will transmit the equinox as as " .EquatorialSystem " In case of a J2000 setting, I think you should switch from EQUATORIAL_EOD_COORD to EQUATORIAL_COORD (=J2000). For J2050 there is no solution unless you convert the coordinate system or the INDI standard is extended with a new property.
Hi Jon, run INDI Server for Windows on Windows machine (physical or virtualised) with ASCOM driver for your CCD and connect to the server from KStars on Linux machine. You don't need INDI driver, just ASCOM driver for the device. Peter