New INDIClient Module Released

[michael1026]

michael1026,
you can try solve your problem on INDI forum, 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?

[Oleg Astro]

michael1026,
you can try solve your problem on INDI forum, 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.

[kkretzsch]

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.

[Juan Conejero]

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.

[Juan Conejero]

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.

[Oleg Astro]

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.

[Greg Schwimer]

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.

[Greg Schwimer]

Tested on OSX with Cloudmakers.eu INDI server. Great job!

[Geoff]

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

[kkretzsch]

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.

[Greg Schwimer]

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.

[kkretzsch]

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.

[kkretzsch]

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.   

[Oleg Astro]

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. 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.

[Oleg Astro]

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.