Please run

and find out what you have on your system. Same for libcurl. There is annoying change of package names in Linux.

OK, this is what I got:

pi@astropi ~ $ apt-cache search libkrb
krb5-multidev - Development files for MIT Kerberos without Heimdal conflict
libkrb5-26-heimdal - Heimdal Kerberos - libraries
libkrb5-3 - MIT Kerberos runtime libraries
libkrb5-dbg - Debugging files for MIT Kerberos
libkrb5-dev - Headers and development libraries for MIT Kerberos
libkrb5-ruby - Transitional package for ruby-krb5-auth
libkrb5-ruby-doc - Transitional package for ruby-krb5-auth
libkrb5-ruby1.8 - Transitional package for ruby-krb5-auth
libkrb5-ruby1.9.1 - Transitional package for ruby-krb5-auth
libkrb5support0 - MIT Kerberos runtime libraries - Support library
ruby-krb5-auth - Kerberos binding for Ruby



pi@astropi ~ $ apt-cache search libcurl
falconpl-curl - Curl bindings for Falcon P.L
fp-units-net - Free Pascal - networking units dependency package
fp-units-net-2.6.0 - Free Pascal - networking units
gnupg - GNU privacy guard - a free PGP replacement
gnupg-curl - GNU privacy guard - a free PGP replacement (cURL)
libcupt2-0-downloadmethod-curl - alternative front-end for dpkg -- libcurl download method
libcurl-ocaml - OCaml curl bindings (Runtime Library)
libcurl-ocaml-dev - OCaml libcurl bindings (Development package)
libcurl3 - easy-to-use client-side URL transfer library (OpenSSL flavour)
libcurl3-dbg - debugging symbols for libcurl (OpenSSL, GnuTLS and NSS flavours)
libcurl3-gnutls - easy-to-use client-side URL transfer library (GnuTLS flavour)
libcurl3-nss - easy-to-use client-side URL transfer library (NSS flavour)
libcurl4-gnutls-dev - development files and documentation for libcurl (GnuTLS flavour)
libcurl4-nss-dev - development files and documentation for libcurl (NSS flavour)
libcurl4-openssl-dev - development files and documentation for libcurl (OpenSSL flavour)
libghc-curl-dev - GHC libraries for the libcurl Haskell bindings
libghc-curl-doc - Documentation for the libcurl Haskell bindings
libghc-curl-prof - Profiling libraries for the libcurl Haskell bindings
libghc-hxt-curl-dev - LibCurl interface for HXT
libghc-hxt-curl-doc - LibCurl interface for HXT; documentation
libghc-hxt-curl-prof - LibCurl interface for HXT; profiling library
libwww-curl-perl - Perl bindings to libcurl
lua-curl - libcURL bindings for the Lua language version 5.1
lua-curl-dev - libcURL development files for the Lua language
python-pycurl - Python bindings to libcurl
python-pycurl-dbg - Python bindings to libcurl (debug extension)
tclcurl - Tcl bindings to libcurl
pi@astropi ~ $

ok it seems all dependencies are there, what's the problem then?

Well, here goes.

1. I'm still having issues with maintaining a connection to the INDI server on the PI from KStars running on laptop with latest Ubuntu when connecting to the camera. If I try to adjust focus it all just hangs up, although the auto focus seemed to work.

2. If I do not touch any focus controls, I can enable the live view preview and see the image, but when I disable it via the button, it is still enabled on the camera (I don't hear the mirror drop back down and the shutter close).

3. If I don't try focus or live view and setup a sequence say 1 shot only (after setting file format FIT or RAW), it takes 2 shots?? and if I set 8 it only takes 4, 4 and only takes 2?? Very strange. It does copy the images to the laptop OK and the images are fine.

If I run just my LX200 and no camera, everything is working perfectly. It just seems to be the camera that is causing me issues. As I said, I'm no Linux expert but I'm very interested in getting this working to a point where I can use it for an imaging session in a situation where I do not want to have a local laptop running windows at my rig due to the power consumption.

I did try the Ubuntu Mate Ras Pi image, but had networking issues with that one, so switched to Raspbian .

Thanks for the help so far.

Cheers.

I believe Kstars/Ekos/Indi moved up to libc6 at some point recently (based on the errors I received trying to install the latest indilib) so i just moved raspbian up to the jessie release.

From a freshly reimaged pi2 I executed the following commands:

sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade
sudo sed -i /deb/s/wheezy/jessie/g /etc/apt/sources.list
sudo sed -i /deb/s/wheezy/jessie/g /etc/apt/sources.list.d/*.list
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade


Make sure you press N, not Y on prompts related to systemd, lightdm, dbus and other booting related things(Doesn't matter on other programs you can press y) on dist-upgrade to jessie


These are the instructions I followed off of an article on stackexchange to upgrade raspbian to jessie. It worked very well in my case.

I didnt have any gphoto dependency issues other than removing the automount service.

Thanks, I'll give this a try and see if it helps.

Cheers.

I just found that a Rapsbian Jessie image release has been made available from Raspberrypi.org so I'll try and set up IndiLib on that and see how it goes.

OK,

I tried the new Jessie on my RPi 2. Installing the required packages was better than before, with only libtiff4-dev failing to install, but the system has libtiff5-dev already. After that, I ran:

$ tar -xzf libindi_1.1.0_rpi.tar.gz
$ cd libindi_1.1.0_rpi
$ sudo dpkg -i *.deb

This is when things went wrong. The packages started to deploy but I got a shed load of dependency/package errors. In frustration, I went back to Ubuntu mate on a 16gb SD card.

I now get the same behaviour with the camera, even though everything is installed with no errors. To eliminate the RPi as the problem, I connected the camera to my laptop running Ubuntu 15.04 with KStars/Ekos Indi 1.1.0 installed and tried again. Now I'm back to similar camera behaviour. The weird thing being that I get very different results depending on what sequence I use to do things. Sometimes the auto focus works, sometimes not at all. The focus in/out buttons do nothing at all, no matter what speed and time settings are used. The Camaera returns to RAW+Jpg, no matter what I set in Ekos control panel, I have to then change it on the camera manually to just RAW before I get just the frames, and number of that I set for the capture sequence. On top of that, the connection drops frequently, no matter if the camera is connected directly to the Rpi/Laptop or via a powered hub.

Sorry to say that there are far too many issues for me to continue to try and get my 60D working with this INDI setup. I'll have to continue using BYEOS for now in addition to having my scope connected via the INDI platform (which works perfectly). I don't have enough time to keep experimenting. Maybe the driver for DLSR cameras is just not developed enough yet.

I will be back to try again when I have more time.

It would useful (especially for non Linux people) if there were some fully configured Ras Pi V2 images available for download that have been tested out. to eleimate any issues caused by different builds\versions etc etc.

Cheers.

Pete, if you have TeamViewer installed, I can login to check the issues you have.

Thanks for the offer Jasem. It is appreciated.

For now I'm out of time with a business trip abroad coming up.

I will try again at some point.

Keep up the good work!