New INDIClient Module Released

[Peter Polakovic]

I had no problem on my Windows 7 system downloading or installing either the 32 bit or 64 bit version of wINDI server. I'm using Avast for Antivirus with Windows Defenders disabled. What I find interesting is the download file names are wINDI_32.exe or wINDI_64.exe not windi.exe as the virus is named. Also the installed executables are not named windi.exe either.

I renamed everything from "wINDI" to "INDI Server for Windows" to fool the antivirus a little bit. If you already have wINDI, uninstall it first and than reinstall new executables from http://www.cloudmakers.eu/windi.

Peter, I have already added the FW-driver on wINDI. I think it is the problem of the two ascom-devices. Do you think in the original INDI-Driver the Camera and the FW is one device?

I also checked the possibility to use single driver for both CCD and internal wheel, but it seems that it is not possible with ASCOM and is not actually necessary. For those cameras with integrated wheel should exist driver for CCD and driver for wheel. I tested it with AtikONE and it does work. It seems, that the same apply for MI.

I also added properties for pulse guiding in this release...

Regards, Peter

[kkretzsch]

I also checked the possibility to use single driver for both CCD and internal wheel, but it seems that it is not possible with ASCOM and is not actually necessary. For those cameras with integrated wheel should exist driver for CCD and driver for wheel. I tested it with AtikONE and it does work. It seems, that the same apply for MI.

OK,  then we will either add the possibility to select a filter device, or create a separate filter wheel control. Currently it is possible to change the filter slot with the INDIDeviceController

I also added properties for pulse guiding in this release...

Great, thanks!

[Jim Selph]

Thank you Klaus and PixInsight team !!! Got the modules running today on Ubuntu 15.10 , PixInsight , QSI683 with 5 filter wheel

[anteje]

Happily connected to INDI server running on Raspberry PI3 (Raspbian Jessie), from PixInsight running on Linux CentOS 7. Waiting for telescope control module. Thanks  Klaus and Juan.

[Juan Conejero]

Very nice! Thank you all so much for testing.

Waiting for telescope control module.

You won't have to wait a lot

[Fco. Bosch]

I'm sorry! I can't use my ccd qhy9 with Indi for windows (10). I ever get the screens attahed. But I can use the simulators. The class isn't registered... I don`t know wath to do, ...

[chris.baron]

Though my clear skies are rather limited here so I might not start testing just yet, I just wanted to say that despite some other forum goers trepidation, I for one am extremely excited about PI going down this route. I own a fully decked out SkyX (with tpoint, camera control, et ceter) and CCDAP Pro, and to be honest, while they work for the most part, they're pretty clunky. I will quite happily flip my Windows based imaging laptop to Linux if it means I can eventually control my imaging from within PI reliably.

PI is already leaps and bounds ahead of anything else image processing wise. Adding in automation for capture as well? I don't see how anything else would be able to compete.

Keep up the awesome work guys.

[kkretzsch]

I'm sorry! I can't use my ccd qhy9 with Indi for windows (10). I ever get the screens attahed. But I can use the simulators. The class isn't registered... I don`t know wath to do, ...

I've seen similar messages with wINDI when using simulator devices on windows. I'll ask the cloudmaker developers ...

[Peter Polakovic]

I'm sorry! I can't use my ccd qhy9 with Indi for windows (10). I ever get the screens attahed. But I can use the simulators. The class isn't registered... I don`t know wath to do, ...

Hi, it  looks like invalid driver. Something like 32 vs. 64 bit? What version of wINDI on what system and with what driver version do you use? Peter

[Fco. Bosch]

Re: New INDIClient Module Released
« Reply #113 on: 2016 June 21 20:09:14 »
Quote
Quote from: Fco. Bosch on 2016 June 21 16:28:01
I'm sorry! I can't use my ccd qhy9 with Indi for windows (10). I ever get the screens attahed. But I can use the simulators. The class isn't registered... I don`t know wath to do, ...

Hi, it  looks like invalid driver. Something like 32 vs. 64 bit? What version of wINDI on what system and with what driver version do you use? Peter

I'm using the last windows10 64 bits, with the last driver contained in QHY9ASCOM-StarSenseSci-V205.exe.
The windi version is Indi_Server_64.2.1.0

Thanks!

[Gasman]

Hi guys
I can`t seem to get the Indi module working with PI. I`m using Windows 10 64 bit, have wIndi 1.8 installed and running and using the Sim options for both scope and camera before trying it all out at the scope. I just get this screen when both PI and wIndi are running. Sure I`m missing something somewhere or do they not like Sim options?.
Thanks
Steve

[TobiasLindemann]

Hi Steve,
you have to open and connect the process "IndiDeviceController"
In this process you have to connect your devices.

Greetings
Tobias

[rodmichael]

I was referred to this thread by someone when I asked about future capability development of PI.  After stumbling through this thread only one thought comes to mind:  WHY???

I guess it would take someone addicted to or fanatic about OSX or Linux or PI to write a software module that didn't include a Windows capability.  That seems almost completely at odds with the rest of the AP software universe.  Why would anyone running on Windows go to all the trouble of trying to get a "virtual machine" up and running with this package when there are so many capable and free or nearly free alternatives (PHD2, MetaGuide, DSS, AstroArt, SGP, and others) for image acquisition and pre-processing?  You'd have to either be a PI-fanatic or an OSX/Linus fanatic to really find this package useful in a meaningful way.

Just my $0.02 worth.

[Juan Conejero]

After stumbling through this thread only one thought comes to mind:  WHY???

Why not? Why not try to do it better, or nicer, or more interesting, or simply different? Applying your concepts, PixInsight should not exist... as most of our competitors say everyday

As for operating systems, as a software developer and a user of a large variety of computing systems since the early 80's, I have to say that I have basically zero interest in Windows. My interest on OS X (now macOS) is only moderate and exists just because it has a UNIX foundation (though hidden), and my main interest these days is Linux and FreeBSD. I don't think I am an OS-fanatic; that's just how I like things to be, based on my own experience and on what I have learned across the years. If I were an OS-fanatic, I wouldn't develop PixInsight on four platforms.

Definitely, the implementation of image acquisition and hardware control tools in PixInsight is an extremely interesting project that I'll always support. Don't be afraid about it. We'll do it better, different, more interesting, and multiplatform. For sure

[akulapanam]

I was referred to this thread by someone when I asked about future capability development of PI.  After stumbling through this thread only one thought comes to mind:  WHY???

I guess it would take someone addicted to or fanatic about OSX or Linux or PI to write a software module that didn't include a Windows capability.  That seems almost completely at odds with the rest of the AP software universe.  Why would anyone running on Windows go to all the trouble of trying to get a "virtual machine" up and running with this package when there are so many capable and free or nearly free alternatives (PHD2, MetaGuide, DSS, AstroArt, SGP, and others) for image acquisition and pre-processing?  You'd have to either be a PI-fanatic or an OSX/Linus fanatic to really find this package useful in a meaningful way.

Just my $0.02 worth.

I agree.  This also goes for XISF to some extent although there I agree with the core need, just don't think anyone will adopt it in mass.  There are just so many areas that PixInsight can expand on in the core image processing space and so many fantastic alternatives in the equipment control space.  You also start locked out of the best features of the Paramount platform which is becoming the Apple of the mount space, because Bisque wants everyone else to be locked out.  The clear areas of potential improvement that PixInsight brought to imaging just aren't there.

That said it seems like a personal area of interest for Juan so I look forward to seeing what comes out.