Changing the EQMod Direct cable from my external powered USB 3 hub directly to one of the Raspi’s USB 2 ports did the trick for me as well. Now my ASI290MM is recognized by Indi again, finally. The ASI290 is connected to the USB 2 hub of the ASI294 which in turn is connected to the USB 3 hub.

Hi limburg11,

This just gets more interesting. Unfortunately I have been testing without an EQMod Direct (telescope simulator) as well as the EQmod and the same result so that is not going to work for me.
I spent yesterday installing Ubuntu 20.04 (another interesting experience in the Odroid XU4) with the same result.
I am going to pull the Odroid and use the RPi4 and see how that goes as most people on this forum seem to be finding workarounds with RPi4 but none of these appear to work with the Odroid. Thanks for the advice though.
Rainy weather here so I am not missing out on any clear sky time
Mike

Hi All,

Thought I would give an update. After trying Ubuntu 20.04 (ASI indi drivers not loading) with same result then reverting back to 18.04 and reconfiguring from scratch I ended up with even worse problems with the indi drivers all crashing on start up of any indi profile with live equipment attached. So I figured it's curtains for the Odroid and will be using RPI4 (ordered an 8gig version) from now on.
In the meantime, using a spare RPi4 running Ubuntu 20.04, I am still having some issues with using a USB3 hub. Everything connects with no crashes on the stable version of KStars but the ASI294MCpro hangs on capture. The ASI120 attached to the 294 hub captures OK and both cameras will capture using phd2.
I just tried the nightly build but that crashes on load up of the ASI drivers. I have rolled back to the stable KStars to get a functional system as the weather has improved. Using the stable version the ASI 294MCpro will capture OK when attached directly to the Pi but that makes it awkward in my system as the Pi is in a bare board state in an enclosure with DIY dew heater and motor focuser (plus powered USB3 hub).
I note that the work around to roll back the kernel has worked for Raspian users but the command is not recognised in ubuntu. Are there any similar quick fixes for ubuntu users to roll back the kernel?

Cheers,

Mike

I posted too early. The ASI 294 capture was still hanging even when plugged directly into the Pi. However I have discovered that this was related to trying to capturing to the internal SD card. My usual workflow is to capture to an external HD. Just for testing I was trying to keep it simple and capture to internal SD. Now I am capturing to the HD everything is working.
So just to reiterate I am using a Rpi4 4Gig running ubuntu 20.04. I am using a powered 7 port USB3 hub. Everything now is plugged into the hub (ASI 294MCpro (+ASI120MM-s) also NEQ6Pro mount using a EQdir serial to USB connector, plus arduino motor focuser and portable HD) with nothing apart from the hub plugged into the Pi and everything connects and works as expected.
However the crashing of the ASI drivers on the current nightly build is still occurring so I will stick to the stable version for the time being.

Mike

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.