I checked out my ZWOptical ASI120MM which I want to use as a guiding cam. The cam was detected correctly in INDI Control Panel but connecting to it failed. The reason was that the download package was lacking an udev rules file. I searched the web and found one, copied it to /etc/udev/rules.d and was able to connect to the cam.

Please check your download package.

CS
Klaus

Are you referring to the PPA or the 3rd party download?

I get the packages from

ppa.launchpad.net/mutlaqja/ppa/ubuntu trusty main

but it may be an issue with my packages/package manager as I im unable to mark an indi package for deinstallation. I need to take a closer look on this first.

CS
Klaus

Actually I just realized there is no udev files in the indi-asicam driver. I found something online:

Is this enough or more is required for other models?

It looks like the one I found but I don't know about the other ZWO cams. Meanwhile I have uninstalled kstars-bleeding and indi packages and installed them anew. Obviously there can't be a change when udev rules are missing, as I supposed.

CS
Klaus

Meanwhile I have replaced my harddisk by a SSD, switched from 32 bit to 64 bit Kubuntu 14.04 and reinstalled kstars-bleeding and indi-full. My ASI120MM is detected by Ekos but it is impossible to connect to the camera. There is no output in the debug window.
I still needed to get the udev rules file from the PPA because it hasn't be installed with indi-asicam package!

lsusb gives:
Bus 002 Device 009: ID 03c3:120a

klaus@sirius:~$ ll /dev/bus/usb/002
insgesamt 0
drwxr-xr-x 2 root root 80 Aug 11 18:23 ./
drwxr-xr-x 9 root root 180 Aug 11 14:54 ../
crw-rw-r-- 1 root root 189, 128 Aug 11 14:54 001
crw-rw-rw- 1 root users 189, 136 Aug 11 18:23 009

Anyone out there who has the same system and can connect?

Thanks.
klaus

There is a problem with the PPA package, it will be rebuilt after launchpad fixes their problem. Will ask the driver developer to check this out.

Hi, sorry for the late response. Can you just try running YAACA (the .deb (both 32 and 64 bit) is available here: www.evolware.org/?p=346) with the same user you are starting the indiserver (just to make sure that you can access the camera)? From the output of ls-l it looks that the permissions are OK, but what you describe (being able to list the USB device but not access it) seems like a permission problem.

Hi chripell,
I just installed yaaca and the cam works fine. It connects and I can view my living room. In Kstars/Ekos the cam is detected but when I hit the connect button the yellow light turns on and - end of story.
Weeks ago, when I had my old harddisk in service, the cam worked fine with Ekos.
I also added my account to group <users>. But as the udev rules give world r/w access, this should not be of any concern.

Thanks for caring.
Klaus

I _suspect_ it's a drive crashing, maybe to missing symbols. Can you run the drive from the command line?

Then connect to it from KStars --> Tools --> Devices --> Device Manager --> Client tab
add new host:
hostname: localhost
port: 7624
name: asicam or any other name you like

Hit connect, and try to connect to ASI cam, check the console window and what it reports if any.

That's all I get on the console:

klaus@sirius:~$ indiserver -v indi_asi_ccd
2014-08-14T17:21:04: startup: indiserver -v indi_asi_ccd
2014-08-14T17:21:04: Driver indi_asi_ccd: pid=2555 rfd=3 wfd=6 efd=7
2014-08-14T17:21:04: listening to port 7624 on fd 4
2014-08-14T17:21:04: Driver indi_asi_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2014-08-14T17:26:34: Client 0: new arrival from 127.0.0.1:50730 - welcome!
2014-08-14T17:50:27: Client 0: read EOF
2014-08-14T17:50:27: Client 0: shut down complete - bye!

No connect.

ldd indi_asi_ccd shows that all requested libs are found. But as I've set up my system from scratch for the new SSD, can there be packages that I missed to install because of unknown dependencies?

well, no driver crash, and udev file already installed? It is most likely now some permission issue.