I have a flat screen set up with the cameras, filter wheel, etc. connected. That's where I saw the EFW tab wasn't present. I have also connected only the EFW for testing.

I have tried to compile the drivers, but it has been a long time since I compiled them. I first tried a pull to update, and when that didn't work, I deleted the directory entirely and cloned the stable repository. I'm still getting this message:

CMake Error: The source directory "/home/user/indi-3rdparty/indi-asi/build/make" does not exist.

This was after following the following instructions from github:

mkdir build
cd build
cmake -DCMAKE_INSTALL_PREFIX=/usr .. make


I don't recall how I got this sorted before.  Any help in getting this sorted will be welcome.

Thanks,

Richard

Richard, if the commands you listed were actually how you typed them, note the the last "make" should be on a new line/new command, not part of the cmake line.

Jim

I needed to create a make directory within build. After that, I was able to compile indi-asi, but the EFW still wasn't being recognized.

For what it's worth, here is the setup I'm testing:
  

All the usb devices show as connected via the light on the hub and "lsusb -vv".

Did you actually install the drivers or did you just build them?
I don't see a 'sudo make install' command anywhere.

Yes, I did a "sudo make install". I also built and installed libasi and re-built and re-installed indi-asi. No change.

Can you confirm your EFW is a human interface device (hid)? Do you have any udev rules for asi devices?

I have not tried that with the most recent source files yet. Instead of checking out master I went back to March 10 and used that branch. I also cloned asi.rules and efw.rules into the udev/rules.d folder, but I am not sure whether that was critical. Anyway, after that, my EFW was recognized again.

Don't know about the hid. I do not recall that and I am not close to my rig right now, so can't check what interface the EFW is connecting through.
Also, I am doing this on a Pi4, so that may be different from your amd system.

I can confirm the issue, not only for this driver, but a few more. There is a bug report here: github.com/indilib/indi/issues/1438

So working on it.

My EFW does show up at HID under bInterfaceClass. I am also running the EFW from the USB hub on the 1600MC.

```Bus 003 Device 007: ID 03c3:1f01 USB2.0 Hub
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 16
idVendor 0x03c3
idProduct 0x1f01
bcdDevice 0.00
iManufacturer 1 ZW0
iProduct 2 ZWO EFW
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0029
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 64mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
```

I do have 99-asi.rules in /usr/lib/udev/rules.d with contents:

```/usr/lib/udev/rules.d $ cat 99-asi.rules
# All ASI Cameras and filter wheels
SUBSYSTEMS=="usb", ATTR{idVendor}=="03c3", MODE="0666"
```

Richard has a problem with the EFW not being recognized when compiling Indi, not when installing it via .deb packages.

I just compiled indi-core, indi-3rdpartylibs and indi-3party drivers from git (master branch, git clone github.com/indilib/indi-3rdparty.git) and installed them on my AMD64 desktop running Ubuntu MATE 20.04.2, then schlepped over my telescope with ZWO-EFW attached, connected the EFW only and called up the driver using the Device Manager.

The EFW connected just fine and shows up normally in the Control Panel.
IAW, this may indeed be just a deb packaging problem. But it does not explain why Richard could not make it work when compiling indi from the source.

Richard, if you want, I can send you the generic script I used to try on your system?

Jo

Post your script. I may have missed a step.

Just sent you a PM. Better to email the script. You also may have to uncomment a couple of lines, just in case you are missing a few libraries. Better explained by email than on a forum post.

Jo

PS:  Nevermind!  Here it is.  Just rename from .txt to .sh and make executable.  Sorry, it is a bit messy 

 

Folks this would be resolved later today, closing this topic since many started for the same issue.