So after 4 hours of some deep dive into this, I found the root cause. It's a udev issue and I emailed the maintainer to look into it.

For StellarMate users, run this:

If you want to try it out, edit /lib/udev/rules/60-rpi.gpio-common.rules:

Then reboot and try it out. Please confirm if this fixes the issue.

Jasem,
Did the sudo apt-get update && sudo apt-get -y dist-upgrade and it helped!
Thank you so much!

Hi Jasem,

Thanks for all your hard work on this issue. Is there any fix for those running RPi4 with Ubuntu Mate 20.04.1. The rules folder in lib/udev does not exist (rules.d) and the 60-rpi.gpio-common.rules file does not come up in any searches. Is there an alternative file in Ubuntu?

Mike

Hi All,

So I installed the rpi.gpio-common using

sudo apt-get update
sudo apt-get install rpi.gpio-common
I confirmed the text file contents as per Jasems last post

Unfortunately this did not resolve the issue in my system. Although things changed in that only 1 ASI camera was recognised no matter if this was connected to the powered hub or directly to the Pi. This behaviour was replicated in PhD2.
I could only resolve this by removing the rpi.gpio-common package and reboot.
The work around is now to plug the ASI camera directly to the Pi and the rest of my equipment to the hub.
I presume this will all be resolved at some point but at least I have a usable astrorig until a solution is found.
Cheers,
Mike

Hi,

I did the changes in /lib/udev/rules.d/60-rpi.gpio-common.rules as Jasem described (for me the directory was „rules.d“ and not just „rules“). In fact I added the obviously missing slashes „/“ in line 3 between /sys and %p.

Then I connected all devices again to my USB3 hub as before. After reboot, my ASI290 was recognized, so issue seems to be fixed!

I‘m an Astroberry user, not SM, btw.

Cheers,
Bernd

Hi Bernt,

I did miss spotting the slashes. I was working on it last night while too tired
I have made the changes and will test later today. Picking up a new RPi4 8gig version today so hopefully it all works. Sounds very hopeful.
Thanks very much for the help!

Mike

I ended up changing over to Astroberry and it seems to be working without any modifications. I am going to take it as a win! Try not to overthink it
Only took a couple of hrs to get it all configured and I will keep the Ubuntu image to work on another time. At least I am back with a workable system.
Thanks to everyone for their advice.
Mike

I updated my Astroberry from 2.02 to 2.03 upgrading Kstars at the same time and ran into the problem with my ASI cameras (and ASI EFW) not showing up when I launch KStars/EKOS from the PI4 or from the INDI WebManager
My hardware version is:
Hardware : BCM2835
Revision : c03111
Serial : 100000004632cd93
Model : Raspberry Pi 4 Model B Rev 1.1

lsusb would no longer show anything from the command line - zip
usb-devices was the same. However sudo lsusb or sudo usb-devices did work.

Anyway I did run sudo rpi-update e1050e94821a70b2e4c72b318d6c6c968552e9a2 and reboot. ASI devices now recognised again and everything shows up ok in lsusb


astroberry@astroberry:~ $ lsusb
Bus 002 Device 005: ID 03c3:183e
Bus 002 Device 004: ID 045b:0210 Hitachi, Ltd
Bus 002 Device 003: ID 045b:0210 Hitachi, Ltd
Bus 002 Device 002: ID 05e3:0616 Genesys Logic, Inc. hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
Bus 001 Device 010: ID 03c3:120c
Bus 001 Device 009: ID 03c3:1f01
Bus 001 Device 008: ID 04b4:6572 Cypress Semiconductor Corp.
Bus 001 Device 007: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
Bus 001 Device 006: ID 045b:0209 Hitachi, Ltd
Bus 001 Device 005: ID 045b:0209 Hitachi, Ltd
Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

For reference I am running the following hardware

ZWO ASI 183MM, ASI120MM, ASI 5 position filter wheel (the latter 2 connected to the integral hub on the 183) and Lakeside focuser connected to a powered USB3 hub on the mount. This runs down an active USB3 cable to the PI4 straight into the USB3 socket.
The EQMOD cable runs direct from the HEQ5Pro to the PI4 USB2 socket. So two USB cables running to the PI and a relatively simple setup.

I am controlling the PI4 via 1G Ethernet connection so no wireless involved. I also have a bug with Windows KStars which I've already reported to Jasem.

Hi Terry,

I saw that you are using the ASI120MM (which is USB2.0) version? my setup almost the same as yours with two USB cables running to the PI. But do you experience skipping frames when guiding? my ASI120MC recently get lost stars very easily because of the skipping frames.

Let us know more.

Tom

Hi Tom. No I've not noticed any issues with skipping frames with the 120MM. I have it set as 8 bit though. I had to do that in Windoze days too.

Mine also set to 8 bit and with compatible firmware a long time ago. I plug almost everything on my powered 7 ports USB hub. But except the EQMOD cable which is directly connected to pi4 USB 2.0 port. Now headache about this asi120mc. I spent few days to troubleshoot it but still........

BTW, I am using qhy168c with asi120mc.

Thanks

Tom

My ZWO ASI120MM is actually the mini version with USB2 only. I've seen a few issues posted on various forums related to the ZWO ASI120MM-S . I wonder if you are seeing the same problems with your 120MC-S?