Hello everybody,

After a few months off, I'm back to deep sky imaging. So two days ago, after having updated everything, ( Fedora 34 and last GitHub version ) I had a very bad surprise.
Usually my setup for deep sky imaging is the following :

- one mount SW EQ6-R Pro
- one ASI1600mm Pro ( imaging )
- one ASI290mm ( autoguiding)
- one ASI EFW mini filter wheel
- one ASI EAF focuser.

I used to connect the ASI290mm and the EFW to the two port hub on the ASI1600mm, and the rest directly to the Raspberry Pi.
This setup used to work perfectly several months ago.

Now, INDI refuses to discover what is plugged to the camera hub, and after a few minutes, everything is freezzed
If I plug everything directly to the Raspberry Pi, it works again, except ... The Pi has only 4 USB ports ... So I'm left with a device with no possible connection, except if I chain a second PI. Any kind of separate hub has the same result. What's connected to the hub fails, what's connected directly works. And this with the Pi or directly with my laptop.

Some help would be appreciated.

- Marc

Just wild guessing, but could it be (lack of) power? If you use a separate hub, is that a powered one? If not, can you try with a powered one?

There was a bug several months back, but has since been fixed, where devices on a USB hub would only be accessible by the root user. You can check if you have this bug by opening a terminal, and running "lsusb" and "sudo lsusb" and see if you get the same results. If you get more results when using sudo, then you have this bug.

Hi Kevin,

# First attempt, user "astro", filter wheel plugged to the camera hub, 2 cameras + EFW :

[astro@astra:~]$ lsusb
Bus 001 Device 009: ID 03c3:462b
Bus 001 Device 010: ID 03c3:1604
Bus 001 Device 004: ID 04b4:6572 Cypress Semiconductor Corp.
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

# Second attempt, user "root", filter wheel plugged to the camera hub:

[astro@astra:~]$ sudo lsusb
Bus 001 Device 009: ID 03c3:462b
Bus 001 Device 010: ID 03c3:1604
Bus 001 Device 004: ID 04b4:6572 Cypress Semiconductor Corp.
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

# Third attempt, user astro, filter wheel plugged directly to the Pi:

[astro@astra:~]$ lsusb
Bus 001 Device 013: ID 03c3:462b
Bus 001 Device 011: ID 03c3:1604
Bus 001 Device 004: ID 04b4:6572 Cypress Semiconductor Corp.
Bus 001 Device 012: ID 03c3:1f01
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

As you can see, the filter wheel ( Bus 001 Device 012: ID 03c3:1f01 ) doesn't show up when connected to the camera hub.
Not even under the root account.

It is only visible when plugged directly (the third attempt).

- Marc

Hi Peter,

It did work several months ago and I didn't change any piece of hardware since ... Plus, the Pi is powered by a 3000 mA source. More than enough IMHO.

- Marc

Well one thing is certain, if the OS doesn't see the device, INDI never will. So this appears to be either an OS-level, or hardware issue, and not an INDI issue.

What does dmesg say when plugging in the device?

You say this happens no matter what hub you use, and both on Raspberry Pi, as well as your laptop? Is that correct?

Kevin says :

"Well one thing is certain, if the OS doesn't see the device, INDI never will. So this appears to be either an OS-level, or hardware issue, and not an INDI issue."
Agreed !

"What does dmesg say when plugging in the device?"
Nothing, as for the OS, the EFW plugged to the hub simply does not exist .

You say this happens no matter what hub you use, and both on Raspberry Pi, as well as your laptop? Is that correct?
Absolutely.

Now ...

I tried to plug 2 USB keys to the camera hub : it Works, the keys are both available Read/Write.
Same if I plug the USB keys to a separate hub.

So it appears the EFW **IS** the problem.

I tried this set up:

- Focuser and ASI290mm plugged to the camera hub (USB port 1 on the Pi)
- EFW on USB port 2
- Mount on USB port 3
- Wireless joystick on USB port 4

Everything works fine, but I still don't understand why the EFW on a hub isn't detected by the system.
And by the way ... ASI290mm and EFW on a hub both work ... Under Windows ... Which excludes any EFW related problem

Need to call Mulder and Scully

- Marc

That is most bizarre.

We are running practically the same hardware. EQ6-R Pro mount, ASI1600mm Pro camera, ASI EFW, and ASI290mm Mini guide cam. On my system, I have the filter wheel plugged into the ASI1600, the ASI1600 is plugged into a powered USB3 hub, and the hub is plugged into the Pi.

This setup has worked with ancient 4.4 kernel, and currently a 5.10 kernel, both 32-bit and 64-bit (I'm currently running 64-bit).