Author Topic: New INDIClient Module Released  (Read 29534 times)

Offline Juan Conejero

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 6432
    • View Profile
    • http://pixinsight.com/
Re: New INDIClient Module Released
« Reply #15 on: 2016 May 13 15:04:02 »
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.
Juan Conejero
PixInsight Development Team
http://pixinsight.com/

Offline mar504

  • Newcomer
  • Posts: 17
    • View Profile
Re: New INDIClient Module Released
« Reply #16 on: 2016 May 13 15:45:50 »
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!

Offline pfile

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 4023
    • View Profile
Re: New INDIClient Module Released
« Reply #17 on: 2016 May 13 16:09:46 »

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

Offline vicent_peris

  • PTeam Member
  • PixInsight Padawan
  • ****
  • Posts: 967
    • View Profile
    • http://www.astrofoto.es/
Re: New INDIClient Module Released
« Reply #18 on: 2016 May 13 16:10:49 »

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.

Offline pfile

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 4023
    • View Profile
Re: New INDIClient Module Released
« Reply #19 on: 2016 May 13 16:52:40 »

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

Offline cfranks

  • PixInsight Addict
  • ***
  • Posts: 138
    • View Profile
Re: New INDIClient Module Released
« Reply #20 on: 2016 May 13 17:18:08 »
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

Offline pfile

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 4023
    • View Profile
Re: New INDIClient Module Released
« Reply #21 on: 2016 May 13 17:34:49 »
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

Offline cfranks

  • PixInsight Addict
  • ***
  • Posts: 138
    • View Profile
Re: New INDIClient Module Released
« Reply #22 on: 2016 May 13 17:47:39 »
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

Offline vicent_peris

  • PTeam Member
  • PixInsight Padawan
  • ****
  • Posts: 967
    • View Profile
    • http://www.astrofoto.es/
Re: New INDIClient Module Released
« Reply #23 on: 2016 May 13 17:50:52 »
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

Offline pfile

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 4023
    • View Profile
Re: New INDIClient Module Released
« Reply #24 on: 2016 May 13 18:10:39 »
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

Offline michael1026

  • Newcomer
  • Posts: 10
    • View Profile
Re: New INDIClient Module Released
« Reply #25 on: 2016 May 13 19:46:24 »
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.

Offline MagnusQ

  • Newcomer
  • Posts: 1
    • View Profile
Re: New INDIClient Module Released
« Reply #26 on: 2016 May 14 00:26:30 »
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)

Offline kkretzsch

  • PTeam Member
  • PixInsight Addict
  • ***
  • Posts: 183
    • View Profile
Re: New INDIClient Module Released
« Reply #27 on: 2016 May 14 00:30:46 »
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:

 

Offline chris.bailey

  • PixInsight Addict
  • ***
  • Posts: 211
    • View Profile
Re: New INDIClient Module Released
« Reply #28 on: 2016 May 14 00:34:39 »

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. Makes it slightly easier to maintain updates for the Indi bits and pieces

Offline kkretzsch

  • PTeam Member
  • PixInsight Addict
  • ***
  • Posts: 183
    • View Profile
Re: New INDIClient Module Released
« Reply #29 on: 2016 May 14 00:36:17 »
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.