PixInsight Forum (historical)
PixInsight => Announcements => Topic started by: Juan Conejero on 2016 May 13 04:54:14
-
Hi all,
We are excited to announce the release of a new PixInsight module: INDIClient, an open-source, multiplatform INDI client available on FreeBSD, Linux, OS X, and Windows. The new module is now being distributed as an official update for the latest PixInsight 1.8.4 versions.
The INDIClient project has been created by Klaus Kretzschmar, a German software developer and a member of the PixInsight GitHub team. This is undoubtedly one of the most important milestones in the history of PixInsight development. INDIClient opens a door to hardware control support on the PixInsight platform, and you can bet we are going to open this door completely and go in.
Although this initial version includes just a device controller and a CCD/DSLR frame acquisition tool, it is just the beginning. Think of this first release as a functional proof of concept, just to demonstrate what we are working on and how we are doing it. The roadmap for INDIClient development in the short-medium term includes the following tools, by priority order:
- Camera control
- Mount/telescope control
- Focuser control and autofocus
- Autoguiding
Of course, all of these tools will be, as are the device controller and frame acquisition tools right now, fully scriptable in JavaScript from the PixInsight Core application.
INDIClient is an open-source project available on PixInsight's GitHub repositories:
https://github.com/PixInsight/PCL/tree/master/src/modules/processes/contrib/kkretzschmar/INDIClient
If you are a software developer and would like to contribute, please contact us. If you can't or don't want to contribute with code, but have suggestions or ideas to improve our development, please also let us know. This exciting project can benefit from the collaboration and help of all PixInsight users.
We want to say a huge thanks to Klaus Kretzschmar for his initiative in creating this important project. Thanks also to all PixInsight users and supporters who help us keep the PixInsight project alive and relevant to the astronomy community.
How to Use the INDIClient Module
INDI stands for Instrument Neutral Distributed Interface. It is a protocol to define communication among hardware devices and software frontends. For a general description of INDI, see this document on INDI Project's website:
http://www.indilib.org/about/discover-indi.html
The first step is installing INDI Library on your machine. On Linux and FreeBSD, you can either compile and build INDI Library from source, or download a precompiled package. See this page for information on download and installation options:
http://www.indilib.org/download.html
It must be pointed out that our INDIClient module is a completely independent solution, which does not require the KStars and Ekos applications.
To build from source, see this page:
http://www.indilib.org/download/source/category/2-source.html
On OS X, we strongly recommend the excellent INDI Server for OS X application created by CloudMakers:
http://www.cloudmakers.eu/indiserver/
On Windows you can use wINDI, also by CloudMakers:
http://www.cloudmakers.eu/windi/
wINDI is a wrapper for ASCOM drivers, so you'll also need the ASCOM platform in this case:
http://www.ascom-standards.org/
A very interesting option on Windows is installing a virtual Linux machine (for example, using VMware or VirtualBox), where you can install and run an INDI server and communicate with it from PixInsight running natively on Windows, or alternatively, install and run PixInsight directly on the Linux virtual machine.
Irrespective of your operating system, you must have a working INDI server with the required drivers for your devices. The server can be running either locally on your machine, or on a remote system. Typically, you run the INDI server locally on the same machine where you are connecting your devices and running PixInsight.
Once you have downloaded and installed the corresponding update on PixInsight, you'll find two new categories in your Process Explorer window: INDI and Instrumentation. Under both categories you'll find two new tools, namely INDIDeviceController and INDICCDFrame. INDIDeviceController allows you to connect your system to a working INDI server, as well as connecting/disconnecting devices and edit their properties. INDICCDFrame allows you to acquire images using a CCD or DSLR camera for which you have a working INDI driver. We are writing a complete documentation for INDIClient, which should be available very soon, but we think both tools are quite intuitive and their functionality is also quite obvious, so you can start using them right now.
Enjoy it!
The PixInsight Team at Pleiades Astrophoto
-
That was a surprise but welcome development. Connects to IndiServer running on a Pi3 quite happily.
Chris
-
If i got this right, it appears the windows implementation of the INDI server is still under development. The "Discover INDI" page mentions a "wINDI which is a complete implementation of INDI under .NET". But not how to get it. Or if that would work with the PixInsight client.
I don't really want to run a virtual machine but if the windows INDI server is a ways off, then i might have to.
-
For future development around guiding, i would like to see some integration with FlexRX. This is an excellent tool to improve guiding when using a guide scope.
http://www.astrogeeks.com/AstroGeeks/andre/FlexRX/FlexRX2.htm
Also, a capability to fine tune the pointing/framing. Solutions i have see platesolve a captured image to get the current location and compare that to the desired location. Then reposition the scope to point to the desired location.
-
I wonder if we can get ACP support. :)
-
At this moment, I think the most powerful tool in PixInsight is the development community. Once we have all the tools to run the entire imaging session I think it will be a matter of weeks to see some new, community contributed scripts to automate imaging sessions.
Best regards,
Vicent.
-
The "Discover INDI" page mentions a "wINDI which is a complete implementation of INDI under .NET". But not how to get it. Or if that would work with the PixInsight client.
As far as in know, wINDI implements the driver independent INDI server part, and delegates the INDI commands to the ASCOM drivers. You can download the wINDI server from http://www.cloudmakers.eu/windi/ and it should work with the PixInsight INDI client, but I never tested it ....
Also, a capability to fine tune the pointing/framing. Solutions i have see platesolve a captured image to get the current location and compare that to the desired location. Then reposition the scope to point to the desired location.
Yes this is a good idea. When I have finished the Mount controller module, it should be possible to implement such a solution with a script using the scripting capabilities of the PI core platform.
-
That was a surprise but welcome development. Connects to IndiServer running on a Pi3 quite happily.
Chris
Cool, which platform did you use, Linux?
-
This is great development, thanks for making this a reality. For those wondering about Windows support, INDI server isn't coming any time soon for Windows. I would recommend you invest $35 on Raspberry PI 3 (https://www.raspberrypi.org/blog/raspberry-pi-3-on-sale/) and you'll automatically get the benefit of remote control. You don't need to have your PC/Laptop outside anymore, RPI3 is sufficient.
I just ran a quick test with the simulators after the update and it's working nicely! Great job!
-
Hi Jasem,
thanks for testing. Let me know if you find any issues. Good to know that your are also active in this forum ;) .
I would recommend you invest $35 on Raspberry PI 3 and you'll automatically get the benefit of remote control. You don't need to have your PC/Laptop outside anymore, RPI3 is sufficient.
I am also running the INDI server on a raspberry pi and I can confirm it is working absolutely great.
Thanks for your ongoing work on the INDI components this is really outstanding !
-
Absolutely, totally inadvised course of action! >:(
No interest whatsover in using PI to control the hardware or play any role in data acquisition.
I just have to wonder, "what are you guys thinking?"
This software has evolved into such a monster. The developers have no interest in aiding the user in skillfully using the stuff. Just pumping out more and more "tools" with minimal-to-no documentation as to how to actually use them. Instead, third party concerns have turned "how to actually use PI" into some kind of cottage industry.
Five years ago, I thought it an abberation that would, sooner or later, surely be addressed.
I no longer have any such hope as PI flies off into yet another direction.
This is precisely what PI does NOT need, in my opinion.
-
That was a surprise but welcome development. Connects to IndiServer running on a Pi3 quite happily.
Chris
Cool, which platform did you use, Linux?
Indi Server running under Raspian on the PI and Pixinsight Running on a Mac. I had it downloading frames from a Starlight Express camera plugged into the Pi direct into Pixinsight over WiFi. Indi Server running on a Pi paves the way for low power installs with minimal wiring.
-
Absolutely, totally inadvised course of action! >:(
No interest whatsover in using PI to control the hardware or play any role in data acquisition.
I just have to wonder, "what are you guys thinking?"
This software has evolved into such a monster. The developers have no interest in aiding the user in skillfully using the stuff. Just pumping out more and more "tools" with minimal-to-no documentation as to how to actually use them. Instead, third party concerns have turned "how to actually use PI" into some kind of cottage industry.
Five years ago, I thought it an abberation that would, sooner or later, surely be addressed.
I no longer have any such hope as PI flies off into yet another direction.
This is precisely what PI does NOT need, in my opinion.
Hi Terry,
Please take into account that this tool has been contributed by another user like you. You cannot simply choose what other users want to do in their free time.
I'm sorry to hear that you don't like this new tool, but I'm pretty sure Klaus is proud of his own work, and I'm pretty sure he actually thinks his contribution will be significative for the PixInsight user community. We cannot tell the users what to and what to not develop.
Best regards,
Vicent.
-
It seems very complicated for me. How do I connect my Canon 4D? I use Windows 10. I installed WINDI Server but do not know quite what to do ...
-
I'm pretty sure Klaus is proud of his own work
Absolutely. And he has many reasons to be proud. And yes, definitely this is a very significant contribution to PixInsight.
-
I just ran a quick test with the simulators after the update and it's working nicely! Great job!
Hi Jasem,
I am glad to have you here. I am glad also to know you like this development project. Thank you so much for your work on the INDI Library.
-
Exciting news! I was just about to pull the trigger on purchasing some software that would assist in acquisition and control various hardware, I may have to hold off and see how quickly some of these pieces develop. Wish I had smarts to contribute, definitely looking forward to playing with some new tools, good work!
-
I am also running the INDI server on a raspberry pi and I can confirm it is working absolutely great.
what disto should one run on the rpi (is rpi2 sufficient?) to ensure reasonable success?
thanks
rob
-
I am also running the INDI server on a raspberry pi and I can confirm it is working absolutely great.
what disto should one run on the rpi (is rpi2 sufficient?) to ensure reasonable success?
thanks
rob
Raspbian Jessie.
V.
-
Raspbian Jessie.
V.
thanks. i was all excited about this but it looks like there's no driver for the astro-physics CP3... and AP has not updated the documentation of the serial command set for the CP3 in a million years.
rob
-
I downloaded windi but was unable to find drivers for any of my gear. From a comment earlier it looked like that won't be corrected anytime soon so, after 46 years in the computer industry and since nobody is going to port it to punched cards, I'll have to see what this 'raspberry pi' is about.
I doff my hat to the PI team and user group when new processes, scripts and now this expansion of PI, are announced. You guys are absolutely amazing.
Charles
-
if you are using wINDI, shouldn't it suffice to have an ASCOM driver for your gear? i thought that was the point of wINDI.
rob
-
Thanks Rob, I was doing something wrong in looking for 'drivers'. Windi has now noted all the drivers I need except for StarlightXpress Lodestar and AO. I'll see if there is an ASCOM driver on the SX site.
Charles
-
Hi Rob,
Does the AP mount accept LX200 commands?
V.
Raspbian Jessie.
V.
thanks. i was all excited about this but it looks like there's no driver for the astro-physics CP3... and AP has not updated the documentation of the serial command set for the CP3 in a million years.
rob
-
Hi Rob,
Does the AP mount accept LX200 commands?
V.
i am not sure, i need to check. i know that when you use WiFiScope you can send LX200 commands, but i think that is because WiFiScope is translating the LX200 commands to ASCOM commands.
there is a nuance with AP mounts that if you send a SYNC command while the counterweights are up, the mount will then try to point from under the pier on the next slew. the AP mounts have a command called RSYNC which does not cause that behavior, and the ASCOM driver translates SYNC to RCAL by default to avoid pier crashes. if it is in fact compatible with LX200 commands, this could still be an issue, since no software would be there to make that translation.
rob
-
I'm having a bit of trouble myself. I setup a virtual machine, started a server using the device manager, copied the "inet addr" address, used that as the host, checked the port, but it doesn't seem to be connecting.
-
User manuals should be written by journalists!
As to Terry's remarks, I suppose they reflect some frustration regarding Help files and so called user manuals in general and not the wonderful initiative to integrate instrument control into PI.
I too share this frustration. In fact, user manuals are completely useless. Not just PI's but pretty much all of them. They are unquestionably great for those writing computer programs and they are probably written by them as well. But they do not tell us how to use the programs.
Instead of going through each and every option, from how to install and further on, a user's manual must describe what do do first. A newspaper has a headline, catching your attention, then a brief description of the event and then again, further down, more and more details. This is how a manual should be written.
As you now, Kayron Merciera (lightvortex) has written some very instructive workflow papers and it is only thanks to them that I manage to use PI at all.
I considered buying SkyX for integrated control but after having read their 600 pages manual (with the same stereotypic layout) I decided that this is not for me. I shall never succeed.
Please please don not make the same mistake as the others when writing a manual for this great new feature.
Fro Magnus in a constructive mood.
(I'm a stray Swede, living in Perpignan, south France)
-
It seems very complicated for me. How do I connect my Canon 4D? I use Windows 10. I installed WINDI Server but do not know quite what to do ...
In general when using wINDI you have to install ASCOM and test if you can control your device with ASCOM on windows. However, AFAIK, ASCOM has not driver for Canon DSLRs :sad:
-
I am also running the INDI server on a raspberry pi and I can confirm it is working absolutely great.
what disto should one run on the rpi (is rpi2 sufficient?) to ensure reasonable success?
thanks
rob
Raspbian Jessie.
V.
Or Ubuntu Mate https://ubuntu-mate.org (https://ubuntu-mate.org). Makes it slightly easier to maintain updates for the Indi bits and pieces
-
I'm having a bit of trouble myself. I setup a virtual machine, started a server using the device manager, copied the "inet addr" address, used that as the host, checked the port, but it doesn't seem to be connecting.
On which OS is your PI running? Is the virtual machine running on the same host? Can you "ping" the virtual machine? The virtual host machine must be visible in the local network.
-
Please please don not make the same mistake as the others when writing a manual for this great new feature.
I'll take that advice since I am aware of the fact that the current setup is not that easy to install as it should be. But please also take into account the complexity of the problem. You have tons of different devices which all speak their own protocols, you have different operating systems, different communication protocols (ASCOM and INDI), and different reference implementations of these protocols (ASCOM on windows and INDI on Linux/OSX).
INDI and ASCOM are a first step in simplifying this complexity by providing a layer that is independent of the vendor specific device control protocols. But both technologies are locked to different OS: ASCOM on Windows (it is written in .Net) and INDI (the server part) on Linux/OS.
I choosed INDI since it better supports the PI platform coverage and it is written in C/C++ which is easier to intergrate into PI. The drawback of that decision is the more complex installation for Windows users.
-
A really good news for all Linux astrofotographers out there. Looking to test it with an RasPi :-)
Thank you Klaus !
-
Excellent news! I've been experimenting with INDI recently (with Ekos) so very interested in this!
If only there was a way to control MGEN over INDI ;)
Quick test showed it works perfectly with INDIServer on a rapsberry pi controlling a Nikon D600 :)
-
oh actually I get the 'Bulb mode isn't supported' message back from IDIserver.
This is something I don't get with the D600 with Ekos, but read some forum messages there that it was a problem at one point and it had to do with capitalization (Bulb vs bulb)
So perhaps similar problem here?
Edit: Nevermind that, after reboot I'm not getting the error :)
-
Great work ! Happy to see the INDI ecosystem grow.
-- Hans
-
Quick test showed it works perfectly with INDIServer on a rapsberry pi controlling a Nikon D600 :)
Thanks for testing! The PI was running on a Linux/MacOS or Windows machine?
Edit: Nevermind that, after reboot I'm not getting the error
Good to know. Did you test the upload server modes? I had some issues with my Canon500d here, but I have a quite old INDI installation on my raspberry.
-
I like the sound of this and understand it could go a long way in the future. It would be great to see Pixinsight containing the whole package of image acquisition and image processing some day.
But can you clear a few things up before i download please. Does Pixinsight have to be running in order for the INDIClient module to run or is it a separate program? I only wonder as i run PI on my 64bit desktop for processing and use a 32bit laptop for imaging. And if i am right in saying that PI doesnt work on 32bit (?) then does this mean i need to acquire a 64bit imaging laptop to replace my 32bit in order to install PI and get the new module to work?
Hope that made sense!
Callum
-
Quick test showed it works perfectly with INDIServer on a rapsberry pi controlling a Nikon D600 :)
Thanks for testing! The PI was running on a Linux/MacOS or Windows machine?
Edit: Nevermind that, after reboot I'm not getting the error
Good to know. Did you test the upload server modes? I had some issues with my Canon500d here, but I have a quite old INDI installation on my raspberry.
I'm running PixInsight on OSX and the Raspberry Pi is running Raspbian.
Not sure what you mean with the upload server modes?
I do have a problem now however; PixInsight crashed and now I don't have the new Processes anymore? PI still says the updates are installed, and no new updates available, but I can't find the INDI stuff anymore.
Any thoughts? (and yes, I did reboot :P)
-
Top, to add this functions in Pix ;)
Chris
-
But can you clear a few things up before i download please. Does Pixinsight have to be running in order for the INDIClient module to run or is it a separate program? I only wonder as i run PI on my 64bit desktop for processing and use a 32bit laptop for imaging. And if i am right in saying that PI doesnt work on 32bit (?) then does this mean i need to acquire a 64bit imaging laptop to replace my 32bit in order to install PI and get the new module to work?
Good idea to check the setup beforehand ;). What OS are you talking about? Windows 64-bit for PI and windows 32-bit for imaging? INDI is a TCP/IP protocol and does not care whether server or host are 32 or 64 bit, but server and host must be reachable in your local network. So if both laptops run on windows you have presumably already ASCOM installed on you 32-bit Laptop? If both Laptops are connected through a local network you could control the imaging Laptop from your PI desktop remotely. In order to do that you have to install the wINDI server on your 32-bit Laptop which shoud work since it is a .Net application.
However this is a quite complex setup which I haven't tested.
-
Not sure what you mean with the upload server modes?
In the "CCD Device" section of the "INDI CCD Controller" process you can choose the destination of the newly created image.
- Upload to client only
- Upload to INDI server only
- Upload both: client and server
where
- Means that the newly created image is transferred to the client and displayed in the PI app
- Means that the newly created image is stored on the INDI server, i.e. the host where the INDI server is running
- Means 1. & 2.
I do have a problem now however; PixInsight crashed and now I don't have the new Processes anymore? PI still says the updates are installed, and no new updates available, but I can't find the INDI stuff anymore.
Any thoughts? (and yes, I did reboot :P)
PI automatically disables the module if it chrashed. So we have a problem here. Did you remember what you were doing before the crash? You can re-enable the module with PI itself: Goto Process -> Modules -> Install modules... -> Search -> Install. (After pressing the search button PI should have found the INDI module)
-
Thx.. got the module back ;)
I was just connecting to the INDI server when it crashed.
Now it's working again and tried the upload to client and server. Not sure where I would need to find the frame locally though, but I do see the file added on the server.
-
Look at my second test of this module under OS Ubuntu 16.04 (64 bit): INDI server + Cartes du Ciel for mount control + PixInsight for image capture.
-
I have found a small bug in this INDIClient: I want to change the coordinates, but their submenu indicate
xx.xxxxxxxxxx deg 0 arcmin and 0 arcsec
instead
xx deg xx arcmin xx arcsec.
-
I was just connecting to the INDI server when it crashed.
OK, thanks. Refactoring the OS dependent client connect code is one of the top priorities in our backlog ;)
-
Hi Oleg,
I have found a small bug in this INDIClient: I want to change the coordinates, but their submenu indicate
xx.xxxxxxxxxx deg 0 arcmin and 0 arcsec
instead
xx deg xx arcmin xx arcsec.
yes, that's a bug, thanks for reporting. Please note that I am working on a PI module for controlling mounts. with that it should be much more easier for users to send goto commands.
look at my second test of this module under OS Ubuntu 16.04 (64 bit)
Thanks for testing! As far as I can remember you have been "the first" who have tested this module outsite of my development ;) (long time ago )
-
You wrote about the autoguiding support in INDIClient Module.
IMHO, you can use Open PHD2, because it is available for Windows, Mac and Linux.
-
I am also running the INDI server on a raspberry pi and I can confirm it is working absolutely great.
what disto should one run on the rpi (is rpi2 sufficient?) to ensure reasonable success?
thanks
rob
Hi Rob,
I have a raspberry 2 it is sufficient.
Klaus
-
I just uploaded a YouTube video showing how to get INDI/Ekos on Windows 10, including how to use PixInsight to capture from a DSLR camera.
https://www.youtube.com/watch?v=A6JM6iINBkA
-
I just uploaded a YouTube video showing how to get INDI/Ekos on Windows 10, including how to use PixInsight to capture from a DSLR camera.
https://www.youtube.com/watch?v=A6JM6iINBkA
Hi Jasem,
absolutely awesome!
It shows that there is already a virtual machine image with INDI/Ekos preinstalled for windows. Looks great! I'll give it a try.
Thanks!
-
I just uploaded a YouTube video showing how to get INDI/Ekos on Windows 10, including how to use PixInsight to capture from a DSLR camera.
https://www.youtube.com/watch?v=A6JM6iINBkA
It is a very good video for Windows users.
Can you create another video about OS Windows+ASCOM+wINDI (http://www.cloudmakers.eu/windi/)?
-
This is fantastic news! I ultimately would like to have this feature extended with live stacking of integrated subs, kind of a "continuous BPP". This would allow one to see the results of their data capture live.
I have the new INDI tools running on OSX with the Cloudmakers.eu INDI server. I am using simulators. It "just works" as far as I can tell.
Some thoughts:
- Have a way to have the client (PI) save the file itself in addition to displaying it.
- Allow the client to display the incoming frames with a restriction on which workspace they come in on. I noticed if I switch workspaces the next incoming sub "follows" me to that workspace.
- Series runs - the ability to build multiple execution plans, e.g. 20x300 on lum, switch wheel to R, 20x300 lum binned 2x2, etc....
-
This is fantastic news! I ultimately would like to have this feature extended with live stacking of integrated subs, kind of a "continuous BPP". This would allow one to see the results of their data capture live.
I have the new INDI tools running on OSX with the Cloudmakers.eu INDI server. I am using simulators. It "just works" as far as I can tell.
Some thoughts:
- Have a way to have the client (PI) save the file itself in addition to displaying it.
It works in current version: you can change "Upload Mode:" in frame INDI CCD Controller.
-
I'm having a bit of trouble myself. I setup a virtual machine, started a server using the device manager, copied the "inet addr" address, used that as the host, checked the port, but it doesn't seem to be connecting.
On which OS is your PI running? Is the virtual machine running on the same host? Can you "ping" the virtual machine? The virtual host machine must be visible in the local network.
'
Thanks! I'm not using a PI, I'm using a Windows 10 machine, running Ekos on VirtualBox. I discovered that I can't actually ping the virtual machine. It times out. I'm guessing this has to do with what you said, and the virtual machine needs to be visible on the network from the host machine. Is there a simple way of doing this?
-
I'm having a bit of trouble myself. I setup a virtual machine, started a server using the device manager, copied the "inet addr" address, used that as the host, checked the port, but it doesn't seem to be connecting.
On which OS is your PI running? Is the virtual machine running on the same host? Can you "ping" the virtual machine? The virtual host machine must be visible in the local network.
'
Thanks! I'm not using a PI, I'm using a Windows 10 machine, running Ekos on VirtualBox. I discovered that I can't actually ping the virtual machine. It times out. I'm guessing this has to do with what you said, and the virtual machine needs to be visible on the network from the host machine. Is there a simple way of doing this?
I recommend to watch Jasems youtube video which he has uploaded recently
https://www.youtube.com/watch?v=A6JM6iINBkA
-
I'm having a bit of trouble myself. I setup a virtual machine, started a server using the device manager, copied the "inet addr" address, used that as the host, checked the port, but it doesn't seem to be connecting.
On which OS is your PI running? Is the virtual machine running on the same host? Can you "ping" the virtual machine? The virtual host machine must be visible in the local network.
'
Thanks! I'm not using a PI, I'm using a Windows 10 machine, running Ekos on VirtualBox. I discovered that I can't actually ping the virtual machine. It times out. I'm guessing this has to do with what you said, and the virtual machine needs to be visible on the network from the host machine. Is there a simple way of doing this?
I recommend to watch Jasems youtube video which he has uploaded recently
https://www.youtube.com/watch?v=A6JM6iINBkA
Thanks! It's working! I'm so happy this is here. I almost bought another program for this. The only issue now is that I can't find where the images are being saved on the client. There's a window that opens in PI that says "CCD Frame", but it's just gray with no image.
Also, will this drain the battery life of my laptop? Just running PHD2, I only get about 3 hours out of my battery. I'm afraid running a VM and PI will greatly reduce my imaging time
-
This is fantastic news! I ultimately would like to have this feature extended with live stacking of integrated subs, kind of a "continuous BPP". This would allow one to see the results of their data capture live.
I have the new INDI tools running on OSX with the Cloudmakers.eu INDI server. I am using simulators. It "just works" as far as I can tell.
Some thoughts:
...
- Series runs - the ability to build multiple execution plans, e.g. 20x300 on lum, switch wheel to R, 20x300 lum binned 2x2, etc....
You can try INDI driver for Image Agent (http://www.indilib.org/forum/general/591-image-agent-what-is-it.html)
Its short description is:
"Its is virtual driver implementing server side batch imaging. You can configure it to use particular ccd and filter wheel, capture series of images to local drive and download them later."
-
Thanks! It's working! I'm so happy this is here. I almost bought another program for this. The only issue now is that I can't find where the images are being saved on the client. There's a window that opens in PI that says "CCD Frame", but it's just gray with no image.
If the upload mode is set to "Upload to client only", the image shoud be displayed in a new window. Which CCD device did you connect to?
-
Thanks! It's working! I'm so happy this is here. I almost bought another program for this. The only issue now is that I can't find where the images are being saved on the client. There's a window that opens in PI that says "CCD Frame", but it's just gray with no image.
If the upload mode is set to "Upload to client only", the image shoud be displayed in a new window. Which CCD device did you connect to?
I'm using a Canon EOS 6D. I noticed when I power down my camera, it says "Recording remaining images: 2", which only happens when I turn off the camera in the middle of an exposure, but I only did a 32 second exposure. Also, it won't go away until I unplug the camera.
-
michael1026,
you can try solve your problem on INDI forum (http://www.indilib.org/forum.html), because last is more suitable for similar questions about INDI.
-
michael1026,
you can try solve your problem on INDI forum (http://www.indilib.org/forum.html), because last is more suitable for similar questions about INDI.
Thank you. The thing is, if I run it locally using Ekos and not PI, the image is downloaded correctly. Do you think that's still an Indi problem, and not a bug with the new PI feature?
-
michael1026,
you can try solve your problem on INDI forum (http://www.indilib.org/forum.html), because last is more suitable for similar questions about INDI.
Thank you. The thing is, if I run it locally using Ekos and not PI, the image is downloaded correctly. Do you think that's still an Indi problem, and not a bug with the new PI feature?
See my screenshot in Reply #52.
-
Thank you. The thing is, if I run it locally using Ekos and not PI, the image is downloaded correctly. Do you think that's still an Indi problem, and not a bug with the new PI feature?
Yes this is strange. But downloading the image from the camera is something which is done on the INDI device side. The PI INDI client gets what is sent from the INDI server. I'll test this setup with my canon 500D soon.
-
Have a way to have the client (PI) save the file itself in addition to displaying it.
Yes, this is in our to-do list. This feature will be implemented very soon.
Allow the client to display the incoming frames with a restriction on which workspace they come in on
Unfortunately this is not possible right now because of some restrictions in our module development framework (PCL). This feature will be available in the next version of the PixInsight Core application, due before Summer.
Series runs - the ability to build multiple execution plans, e.g. 20x300 on lum, switch wheel to R, 20x300 lum binned 2x2, etc....
This is perfectly possible right now via scripting.
-
Hi Oleg,
I have found a small bug in this INDIClient: I want to change the coordinates, but their submenu indicate
xx.xxxxxxxxxx deg 0 arcmin and 0 arcsec
instead
xx deg xx arcmin xx arcsec.
Oops! This bug is all mine. I'll try to fix it next Monday. Sorry for the trouble.
-
Hi Oleg,
I have found a small bug in this INDIClient: I want to change the coordinates, but their submenu indicate
xx.xxxxxxxxxx deg 0 arcmin and 0 arcsec
instead
xx deg xx arcmin xx arcsec.
Oops! This bug is all mine. I'll try to fix it next Monday. Sorry for the trouble.
No problem :)
P.S. You can see PixInsight in INDI clients list (http://www.indilib.org/about/clients.html).
-
This is fantastic news! I ultimately would like to have this feature extended with live stacking of integrated subs, kind of a "continuous BPP". This would allow one to see the results of their data capture live.
I have the new INDI tools running on OSX with the Cloudmakers.eu INDI server. I am using simulators. It "just works" as far as I can tell.
Some thoughts:
- Have a way to have the client (PI) save the file itself in addition to displaying it.
It works in current version: you can change "Upload Mode:" in frame INDI CCD Controller.
Changing the upload mode to "server" causes the subs to be saved on the system running the server, no?
What I mean is that when PixInsight gets the file, it would be good if it can be configured to also save the file.
-
Tested on OSX with Cloudmakers.eu INDI server. Great job!
-
In the "CCD Device" section of the "INDI CCD Controller" process you can choose the destination of the newly created image.
- Upload to client only
- Upload to INDI server only
- Upload both: client and server
where
- Means that the newly created image is transferred to the client and displayed in the PI app
- Means that the newly created image is stored on the INDI server, i.e. the host where the INDI server is running
- Means 1. & 2.
I tried connecting a QSI camera. The camera seems to work, but this section is greyed out. I can't locate any picture anywhere.
Geoff
-
Tested on OSX with Cloudmakers.eu INDI server. Great job!
Thanks for testing.
Have a way to have the client (PI) save the file itself in addition to displaying it.
Is on our Todo list.
-
Not confirmed to be related to the INDI tools, but....
I haven't had a PI crash in a very long time, until I started playing with the INDI tools. Two crashes today alone. I'll keep digging to see if I can figure out a correlation.
-
Hi Geoff,
I tried connecting a QSI camera. The camera seems to work, but this section is greyed out. I can't locate any picture anywhere.
Can you send a screenshot? The combo box "Upload mode" shouldn't be greyed out, but the fields "Server upload directory" and "Server filename template" are enabled only if you switch the "Upload mode" to Upload to INDI server only or Upload both: Client and server.
-
Not confirmed to be related to the INDI tools, but....
I haven't had a PI crash in a very long time, until I started playing with the INDI tools. Two crashes today alone. I'll keep digging to see if I can figure out a correlation.
One OSX user already reported a crash when connecting to the INDI server.
-
This is fantastic news! I ultimately would like to have this feature extended with live stacking of integrated subs, kind of a "continuous BPP". This would allow one to see the results of their data capture live.
I have the new INDI tools running on OSX with the Cloudmakers.eu INDI server. I am using simulators. It "just works" as far as I can tell.
Some thoughts:
- Have a way to have the client (PI) save the file itself in addition to displaying it.
It works in current version: you can change "Upload Mode:" in frame INDI CCD Controller.
Changing the upload mode to "server" causes the subs to be saved on the system running the server, no?
What I mean is that when PixInsight gets the file, it would be good if it can be configured to also save the file.
INDIClient Module has three "Upload mode:"
1. Upload to client only
2. Upload to INDI server only
3. Upload both: Client and server
INDIClient Module is one from INDI clients (http://www.indilib.org/about/clients.html). You can use many INDI cliens with one INDI server.
"Server" means minicomputer/laptot/desktop with installed indiserver and indi_drivers for astro hardware.
Look at my screenshot about last 3rd mode.
-
In the "CCD Device" section of the "INDI CCD Controller" process you can choose the destination of the newly created image.
- Upload to client only
- Upload to INDI server only
- Upload both: client and server
where
- Means that the newly created image is transferred to the client and displayed in the PI app
- Means that the newly created image is stored on the INDI server, i.e. the host where the INDI server is running
- Means 1. & 2.
I tried connecting a QSI camera. The camera seems to work, but this section is greyed out. I can't locate any picture anywhere.
Geoff
It means:
1. INDI driver for QSI camera is run;
2. your camera is does not connected in INDIClient Module.
-
Great module :-)
I have a similar problem with my Moravian. The upload mode is greyed out. I can make a picture, but can't see it in PI and is not saved anywhere.
Greetings
Tobias
-
Change the frame "Upload mode:" from Upload to client only to Upload both: client and server
-
Change the frame "Upload mode:" from Upload to client only to Upload both: client and server
that is the problem, the section is greyed out and I can not change it
-
Great module :-)
I have a similar problem with my Moravian. The upload mode is greyed out. I can make a picture, but can't see it in PI and is not saved anywhere.
Greetings
Tobias
Hi Tobias,
ah, I got it. The moravian device driver (and maybe others) which comes with wINDI seems to be quite old. The upload feature was introduced later. We can fix our coding so that we are downward compatible here, i.e. supporting upload to client as the default behaviour. Maybe you can send cloudmakers an e-mail and ask when they will upgrade wINDI to a more current INDI version.
Thanks for providing the screenshots. That was very helpful.
-
Klaus, thanks for your quick answer :-)
The driver from Moravian, I used is quite old because the newer, 64bit one was not working. Is this caused by wIndi?
-
Klaus, thanks for your quick answer :-)
The driver from Moravian, I used is quite old because the newer, 64bit one was not working. Is this caused by wIndi?
Hm, not sure. wINDI is running on a 64-bit windows? Does the driver work when you are using an ASCOM client? Otherwise please contact the INDI forum, the developers from cloudmakers are looking regulary on that forum.
Our next update will contain a fix to become downward compatible, so that at least the image is sent to the client.
-
In the "CCD Device" section of the "INDI CCD Controller" process you can choose the destination of the newly created image.
- Upload to client only
- Upload to INDI server only
- Upload both: client and server
where
- Means that the newly created image is transferred to the client and displayed in the PI app
- Means that the newly created image is stored on the INDI server, i.e. the host where the INDI server is running
- Means 1. & 2.
I tried connecting a QSI camera. The camera seems to work, but this section is greyed out. I can't locate any picture anywhere.
Geoff
The same with QHY9
-
The camera seems to work, but this section is greyed out. I can't locate any picture anywhere.
Same with Atik314L+.
I tried connecting an Atik 314L+ on Windows 7 with wINDI 1.6, ASCOM 6 SP1.
-
The same with QHY9
This happens with windows 10. The module open the shutter of the camera, but then don't upload anything; and the options are always grayed.
-
This happens with windows 10. The module open the shutter of the camera, but then don't upload anything; and the options are always grayed.
Same with Atik314L+.
Yes, our client is not backward compatible to devices which do not support the "UPLOAD_MODE", i.e. uploading the image to the client should always work. Our next update will fix this.
-
It's a good news: "wINDI 1.7 is available for download in both 32 and 64 bit versions. DRIVER_INTERFACE item is added to DRIVER_INFO property of all drivers and UPLOAD_MODE and UPLOAD_SETTINGS properties are added to CCD driver.
http://www.cloudmakers.eu/windi/
http://bb.cloudmakers.eu/viewtopic.php?f=4&t=30
"
-
Hi Geoff,
I tried connecting a QSI camera. The camera seems to work, but this section is greyed out. I can't locate any picture anywhere.
Can you send a screenshot? The combo box "Upload mode" shouldn't be greyed out, but the fields "Server upload directory" and "Server filename template" are enabled only if you switch the "Upload mode" to Upload to INDI server only or Upload both: Client and server.
Here is the screenshot
-
It's a good news: "wINDI 1.7 is available for download in both 32 and 64 bit versions. DRIVER_INTERFACE item is added to DRIVER_INFO property of all drivers and UPLOAD_MODE and UPLOAD_SETTINGS properties are added to CCD driver.
http://www.cloudmakers.eu/windi/
http://bb.cloudmakers.eu/viewtopic.php?f=4&t=30
"
fantastic, now it is working :-)
-
Here is the screenshot
Hi Geoff,
OK, that is the known problem on windows with wINDI. In the meantime it was fixed by the cloudmakers developers. Please download the new wINDI version.
-
Here is the screenshot
Hi Geoff,
OK, that is the known problem on windows with wINDI. In the meantime it was fixed by the cloudmakers developers. Please download the new wINDI version.
OK, now it works after a fashion. I have some comments:
- There doesn't appear to be a "Browse" utility when selecting the server upload directory. The directory has to be (laboriously) typed in. Am I missing something here?
- The fits header contains very sparse info--no exposure time, no indication what type of frame we have (light, dark, flat, bias). Is there a way to put this info into the file? I notice that there are frame type keywords in the title of the file saved to the server(light, dark etc) and BPP seems to be able to sort them accordingly, but it would be nice to have this info in the file header
- I can't seem to connect more than one device--for example camera and filter wheel. When I try this nothing shows in the Device/Property window. If I then backtrack and just try to connect the camera, then it won't connect
Geoff
-
]There doesn't appear to be a "Browse" utility when selecting the server upload directory. The directory has to be (laboriously) typed in. Am I missing something here?
For frames which are saved on the server host a "Browse" functionality is not possible if the server is running on a different host. However, for frames which are sent to the client the next update will contain the possibility to save the frames to the file system - with a "Browse" function...
The fits header contains very sparse info--no exposure time, no indication what type of frame we have (light, dark, flat, bias). Is there a way to put this info into the file? I notice that there are frame type keywords in the title of the file saved to the server(light, dark etc) and BPP seems to be able to sort them accordingly, but it would be nice to have this info in the file header
FITS keywords are not created on wINDI server. The cloudmaker developers look at it to add them, when they are available from ASCOM environment. The INDI servers on Linux and macosx already support inclusion of many FITS keywords.
I can't seem to connect more than one device--for example camera and filter wheel. When I try this nothing shows in the Device/Property window. If I then backtrack and just try to connect the camera, then it won't connect[/li][/list]
This is strange and I could not reproduce with wINDI simulator devices. Can you send me some screenshots?
Thanks for testing,
Klaus
-
The fits header contains very sparse info--no exposure time, no indication what type of frame we have (light, dark, flat, bias). Is there a way to put this info into the file? I notice that there are frame type keywords in the title of the file saved to the server(light, dark etc) and BPP seems to be able to sort them accordingly, but it would be nice to have this info in the file header
FITS keywords are not created on wINDI server. The cloudmaker developers look at it to add them, when they are available from ASCOM environment. The INDI servers on Linux and macosx already support inclusion of many FITS keywords.
Hi, basic FITS keywords are added in wINDI 1.8.
http://bb.cloudmakers.eu/viewtopic.php?f=4&t=32 (http://bb.cloudmakers.eu/viewtopic.php?f=4&t=32)
Peter
-
Yes! With wINDI 1.8 some Fits keywords are being stored and the new CCD-controller module has new features :-) It is a good idea to have the option to save the client frames. To set the filter would also a good new feature, but for some reason it don't work on my PI. The section is greyed out and I can not change it. As you see in the device controller, the filter wheel is connected and in the device controller I can change the filter with the edit button. I have a Moravian with integrated FW. Maybe this is the problem.
I have detected another bug: When I want the change the frame type to Bias, or Flat it switches always back to Light. Light and Dark works.
Klaus, thank you very much for all your work :-)
-
Tobias, this is feature of wINDI, not a bug :) Only light and dark frame type is supported, there is no technical interpretation of BIAS or flat type on ASCOM side. Peter
-
The section is greyed out and I can not change it ... I have a Moravian with integrated FW. Maybe this is the problem.
I don't think it is a problem of the integrated FW. I think the problem here is that ASCOM treats the integrated filterwheel as a different device. I assume that there is no FILTER_SLOT property under the GXCamera64 device property tree? To support filter wheels in general (also external ones) we either have to offer the selection of a filter wheel in the camera control or a separate process for filter wheel control.
Klaus, thank you very much for all your work :-)
Thank you for testing. Actually the new features were implemented by Juan and the FITS keyword enhancement by Peter from cloudmakers.
-
The section is greyed out and I can not change it ... I have a Moravian with integrated FW. Maybe this is the problem.
I don't think it is a problem of the integrated FW. I think the problem here is that ASCOM treats the integrated filterwheel as a different device. I assume that there is no FILTER_SLOT property under the GXCamera64 device property tree? To support filter wheels in general (also external ones) we either have to offer the selection of a filter wheel in the camera control or a separate process for filter wheel control.
I'm not quite sure about this particular driver, but this is probably true. Try to add also filter wheel driver on wINDI side. Peter
-
Klaus, yes you are right, there is no filter_slot under the GXCamera and I can not select the GXFilterWheel in the INDICCD-Controller. I only can select the GXCamera.
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?
Tobias
-
Klaus, yes you are right, there is no filter_slot under the GXCamera and I can not select the GXFilterWheel in the INDICCD-Controller. I only can select the GXCamera.
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?
Tobias
Yes, in real INDI driver CCD can be combined with filter wheel into one device with multiple interfaces. Unfortunately this is not yet possible with wINDI. I don't have MI camera with integrated filter wheel, but will try to make some experiments with Atik One to find out if it is possible to do it with ASCOM. Peter
-
Sounds promising. Thank you Peter :-)
-
I currently use CdC for planning and then Sequence Generator Pro for image acquisition (primarily for it's plate solving abilities), how can I best go about switching to this workflow?
I was thinking of using a Pi attached to the equipment, and then control everything from a laptop, is there any plate solving software to accurately correct the slews?
Thanks
-
I was thinking of using a Pi
Do you mean a raspberry pi? Running an INDI server on the raspberry pi works great.
... control everything from a laptop ...
Yes you can do that with remote control.
is there any plate solving software to accurately correct the slews?
Yes there is, the Image Solver script by Andres del Pozo. I am working currently on a Mount control module. This itself will not be able to correct misalignments in the first version. But it will be possible to write a script (javascript) which could orchestrate the image solving and mount control capabilities
-
There is a virus named windi.exe; my antivirus and also the same windows block the download of windi, and then isn't possible to regist the .com ...
>:D
-
Hi Terry,
Please take into account that this tool has been contributed by another user like you. You cannot simply choose what other users want to do in their free time.
I'm sorry to hear that you don't like this new tool, but I'm pretty sure Klaus is proud of his own work, and I'm pretty sure he actually thinks his contribution will be significative for the PixInsight user community. We cannot tell the users what to and what to not develop.
Best regards,
Vicent.
I for one can not be more pleased as I am running Debian 8.4 "Jessie" I will be installing the entire library this coming weekend ! :D
Jim
-
There is a virus named windi.exe; my antivirus and also the same windows block the download of windi, and then isn't possible to regist the .com ...
>:D
Where can I complain about that? :P
-
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.
Mike
-
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 (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
(http://www.cloudmakers.eu/windi/AI_wINDI.jpg)
-
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!
-
Thank you Klaus and PixInsight team !!! Got the modules running today on Ubuntu 15.10 , PixInsight , QSI683 with 5 filter wheel
-
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.
-
Very nice! Thank you all so much for testing.
Waiting for telescope control module.
You won't have to wait a lot ;)
-
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, ...
-
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.
-
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 ...
-
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
-
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!
-
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
-
Hi Steve,
you have to open and connect the process "IndiDeviceController"
In this process you have to connect your devices.
Greetings
Tobias
-
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.
-
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 ;D
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 ;)
-
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.
-
The key word here is diversity. Diversity is one of the most important things for me, not just in software development. PixInsight is to pursue excellence, culture and diversity in software development and image processing. That's why it is being developed on four platforms. And that's why when a developer starts a project like INDIClient, well designed, well implemented, and with a clear multiplatform orientation, I can only but support it. The same happens with many other development projects in PixInsight, and I wish there were many more, and very diverse. It's not just a matter of my personal interests, it's just how PixInsight is.
What happens with XISF is different. It has to do more with punched cards and magnetic tapes being used in the 21st Century. Not physically, but virtually, which is even worse. It they were physical, at least they would be nice from a museum perspective. Yes, I know, XISF won't be adopted easily. And yes, I know, it is being seen as a threat in some very 'remarkable' circles. But I honestly think we're doing a good and very necessary work with XISF, and you know, that's what motivates me.
As for people trying to 'lock out' people, well, that is something that never works in the long term. In any event, 'locking out' is something in which I have no interest. It's too boring.
-
Please let me note that this project has been started by a PixInsight user. Please respect his own choice; I simply don't understand why one user can put an opinion on the choice of another user's free time. The discussion whether PixInsight should or should not have a set of acquisition tools is out of place in my opinion because what you're really discussing is about that user's free time.
Best regards,
Vicent.