That's great! Always nice to see some great software still being improved upon!

After getting my initial testing done a few months ago I wasn't able to get back to it. The weather has been awful and my job has just drained every ounce of energy from me!


Yes. Using kstars as a normal user, remotely connecting to a manually created indi server as prescribed OR using the indi web server(!), the EFW appears in my INDI control panel and I was able to connect to the filter wheel. I probably will not get to connect it up the full telescope setup until this weekend.

I'm now trying to sort out a remote connection where my laptop connects to the RPi as that was my original intention 6 months ago. It's also where my RPi/Linux knowledge fades. I'm getting connection issues (e.g. too slow / timeout) when pointing at the IP:port. I'm sure I can find a thread on those issues, though.

To summarize:
1. The EFW will not work under a local connection (June 20, 2017)
2. Make sure indiserver is properly configured to allow a remote connection (I didn't have indi_asi_wheel in my indiserver, which is why it did not connect - the web server made the apparent!)

But I think the original purpose of the thread has been solved. Thanks, Maudy!!! Please let me know if you hear anything from ZWO.



I am now able to connect to the EFW in remote mode. After starting the indiserver manually, changing my setup to remote, the EFW appeared in the control panel and I was able to connect.

So, why doesn't it work in local mode? :)

I also somehow configured indiserver to start when my RPi boots.... I suppose I need to find the command that starts it - if I add in the asi_wheel (and maybe the CCD) I may be able to run indi in remote mode (which I'd prefer over local, but never got remote to work before).



I do not have a permanent telescope setup and the weather has been stormy recently (I live in North Carolina, USA).

Right now, for testing, this is the configuation. Only the other connected devices change when I'm at the telescope:

- RPI3 using Ubuntu-mate 16.04 - unsure of source but it was a very easy install.
- RPI3 is connected to wifi network at home
- Currently setup with Telescope Simulator
- Currently setup with CCD Simulator
- EFW is connected by USB directly from device to USB port. (It clearly is connected and available per diagnostic info in original post)

I run my profile in LOCAL mode. In the original post, I posted some screenshots that may help. Perhaps a related symptom is that I find the CCD will not connect in remote mode. I actually just checked and in remote mode, nothing connects. In Local mode, the telescope and CCD simulators connect. The EFW does not connect. The message panel tells me "Unable to Establish: + ASI Wheel Please ensure the device is connected and powered on". To me, this is indicating INDI isn't recognizing the device. The udev/rules.d file contents for 99-efw.rulesare above, assuming INDI it referenced for the correct file name. My guess is something to do with this file is the problem - but I'm not really familiar with the inner workings of ekos/indi.

Thank for the help so far. I'm happy to continue trying things out if you have anything else to check.



I've got those too :). Sorry I missed those in my reply - forgot about them.

I have INDI working for everything except the EFW. I've been running Kstars for several months, but added the EFW and motorized my Moonlite last week... and that is when trouble began.


I would definitely like some guidance on running INDI as root or via command line to test (I've only run INDI via Ekos's visual interface). Perhaps this is important, but I currently only run INDI locally on the RPi I was able to run kstars as root, but not sure if that means ekos and then indi are run as root as I click through the interface. I can say that did not resolve the issue.

I've installed everything through command line:

sudo apt-get install libindi1
sudo add-apt-repository ppa:mutlaqja/ppa
sudo apt-get install kstars-bleeding

I do have a powered hub when I have everything running in the field or driveway, but for right now have the EFW plugged directly into the RPi.

As for the initialization tool - I'm not seeing a good way to run it under linux. It has a driver for mac (java) as well as various windows executables.

I'll also add that I know my way around linux, but perhaps just a little bit above the average novice..

Thanks for the help so far!!


I am having trouble getting my ZWO/ASI EFW Filter Wheel to be recognized by INDI within Ekos and was looking for some help.

I've reviewed several threads on this forum. The closest thread to my issue is this one:

The main difference however is that I'm not able to see the EFW at all in INDI - it never appears on my list of connectable devices.

I've also followed the advice from ZWO ( ) related to the above thread where the problem stems from group privs on the device.

At first, I had other devices connected (and operating normally): Celestron Nexstar (CGEM), ATIK 314L CCD, ZWO/ASI 120MM (guide camera), and Moonlite Focuser. After extended time trying to sort this out at the telescope over a few nights, I moved indoors and setup using a simulated telescope, simulated CCD, and the ASI filter wheel.

The EFW appears to connect to my RPi, but INDI isn't able to see it for some reason.

matted@AstroShed:/dev/bus/usb/001$ lsusb
Bus 001 Device 006: ID 046d:c315 Logitech, Inc. Classic Keyboard 200
Bus 001 Device 008: ID 03c3:1f01  
Bus 001 Device 007: ID 046d:c01a Logitech, Inc. M-BQ85 Optical Wheel Mouse
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
idVendor           0x03c3 
  idProduct          0x1f01 
  bcdDevice            0.00
  iManufacturer           1 ZW0
  iProduct                2 ZWO EFW
matted@AstroShed:/lib/udev/rules.d$ dmesg | grep EFW
[    2.181425] usb 1-1.4: Product: ZWO EFW
[    2.186122] hid-generic 0003:03C3:1F01.0002: hiddev0,hidraw1: USB HID v1.01 Device [ZW0 ZWO EFW] on usb-3f980000.usb-1.4/input0
[76509.946701] usb 1-1.4: Product: ZWO EFW
[76509.956678] hid-generic 0003:03C3:1F01.0005: hiddev0,hidraw1: USB HID v1.01 Device [ZW0 ZWO EFW] on usb-3f980000.usb-1.4/input0
matted@AstroShed:/dev/bus/usb/001$ ls -la
total 0
drwxr-xr-x 2 root root     160 Jun 18 13:12 .
drwxr-xr-x 3 root root      60 Dec 31  1969 ..
crw-rw-r-- 1 root root  189, 0 Jun 17 15:57 001
crw-rw-r-- 1 root root  189, 1 Jun 17 15:57 002
crw-rw-r-- 1 root root  189, 2 Jun 17 15:57 003
crw-rw-r-- 1 root root  189, 5 Jun 17 15:57 006
crw-rw-r-- 1 root root  189, 6 Jun 18 13:12 007
crw-rw-rw- 1 root users 189, 7 Jun 18 13:19 008

I've checked the udev/ruled.d/ file 99-efw.rules
ACTION=="add", ATTRS{idVendor}=="03c3", ATTRS{idProduct}=="1f01", GROUP="users", MODE="0666"

The indi_asi_wheel driver appears to work from the command line.
matted@AstroShed:/lib/udev/rules.d$ indiserver -v indi_asi_wheel
2017-06-18T17:35:22: startup: indiserver -v indi_asi_wheel 
2017-06-18T17:35:22: Driver indi_asi_wheel: pid=19041 rfd=3 wfd=6 efd=7
2017-06-18T17:35:22: listening to port 7624 on fd 4

I've run (repeatedly) sudo apt-get update and sudo apt-get upgrade, so I have the latest drivers. I've also tried reinstalling kstars.

I'll add that I also ran kstars as root (sudo kstars) and had the same problem, so I do not think it's permission related.

I'm running Ubuntu 16.04 on my Rpi3. I've attached the KStars log. I cannot create an INDI log for the EFW!

Any ideas?