New INDIClient Module Released

[kkretzsch]

]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

[Peter Polakovic]

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

Peter

[TobiasLindemann]

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 :-)

[Peter Polakovic]

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

[kkretzsch]

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.

[Peter Polakovic]

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

[TobiasLindemann]

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

[Peter Polakovic]

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

[TobiasLindemann]

Sounds promising. Thank you Peter :-)

[Kelogg76]

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

[kkretzsch]

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

[Fco. Bosch]

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

[Jim Selph]

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 ! 

Jim

[Peter Polakovic]

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

Where can I complain about that? 

[msmythers]

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