×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

ASI290MM mini not recognized any more

  • Posts: 145
  • Thank you received: 15
Hi,

since last week my RPI 4 Astroberry setup does not recognize my ASI290MM mini guiding cam any more... I'm not aware that I did something special, some days before it worked flawlessly like it did the last months. All I do regularly is update/upgrade, and there were some packages upgraded last week.

What information do I have to provide so that anyone can help me with this issue? I'm absolutely no Linux specialist... I have no clue where to start digging. Indi does not show the cam (although it shows my main cam ASI294MC Pro). PHD2 only shows the 294 as well... I normally use the USB hub on the 294, but I also tried connecting the 290 to my external USB hub directly and I tried to connect it to the Pi's USB ports directly. Same problem, whatever I do.

What I checked is if the cam is defective, and it is not. I connected it to my Mac and it was recognized by ASIStudio.

I hope that anyone can help me...

Regards,
Bernd

Edit: Here is a current log file. Compared to older logs, there is no line "[ org.kde.kstars.ekos] - Ekos received a new device: "ZWO CCD ASI290MM Mini":

File Attachment:

File Name: log_13-45-39.txt
File Size:55 KB
Last edit: 3 years 7 months ago by Bernd Limburg. Reason: Log attached
3 years 7 months ago #57432
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 389
  • Thank you received: 15
Hello,

After reviewing this log file, I did see the expected statement. To me, everything is working. Is EKOS giving errors about "ZWO CCD ASI294MC Pro" not found? I did not see any messages related to this device not functioning. I copied this statement out of this supplied log.

[2020-07-28T13:46:44.841 CEST INFO ][ org.kde.kstars.ekos] - Ekos received a new device: "ZWO CCD ASI294MC Pro"

Check the profile EKOS claims to have as active. See if this one has CCD as ZWO. Check all profiles that have CCD = ZWO.

I have three different cameras. For guiding, I have to select the one I want to use for Polar Alignment. The log does not show any other camera.

I use device manager to investigate a camera and how it is working with INDI. This way I can observe the logs specifically to my target instead of buried in other logging events.

The supplied log file does not mention any failure experienced by the ZWO.

I just read the HUB comment. Using USB 3.0 hubs with USB 2.0 devices in the USB 3.0 ports is the potential problem. Plug the HUB into the USB 2.0 port and try again. This cleared my problems up for me.

Yes, this last update highlighted a problem I had been dealing with a long time. I was able to discover the root. USB 3.0 is strictly enforced or USB 3.0 hubs are not able to support USB 2.0 devices very well.
Last edit: 3 years 7 months ago by John Robison.
3 years 7 months ago #57468

Please Log in or Create an account to join the conversation.

  • Posts: 145
  • Thank you received: 15
Hi,

thanks for the reply. The ASI294MC is working correctly. This is a USB3.0 cam. The ASI290MM is not working (is not recognized). The 290 is a USB2.0 cam. I tried to plug it directly into one of the Pi's USB2.0 ports, no success. All profiles have CCD = ZWO, I didn't change anything there.

You are right, in the log is no ZWO related error. In fact it is missing the "[ org.kde.kstars.ekos] - Ekos received a new device: "ZWO CCD ASI290MM Mini" line... it is as if the cam is not connected at all.

Maybe/probably I have the same problem that is discussed here: No ASI Camera after Update - Suspect port mapping

I already tried this
sudo rpi-update e1050e94821a70b2e4c72b318d6c6c968552e9a2
but now my wifi stick is not working any more... Have to connect a monitor/keyboard and re-install the 3rd party driver of the stick. And if this new problem is solved, I can see if my ASI290 is recognized again.

Linux keeps you busy all the time. With things you should not have to bother with.
3 years 7 months ago #57470

Please Log in or Create an account to join the conversation.

  • Posts: 389
  • Thank you received: 15
Hello,

As I read our discussion, I come away with one focus, INDI is one evidence. The OS tells INDI what it has. INDI is a consumer.

Open a terminal.

Use: sudo lsusb

Look for two odd pair of XXXX:XXXX hex numbers with blank descriptions. The left hex is the vendor ASI. Their id is 03c3. If not a pair, the device has either a bad cable, insufficient power, or the unit is dead.

If a pair, then look at the right side. Write down the product id for both. The next item to look into is udevadm. The hex firmware isn’t loading because the idProduct is 1 digit off. Create a custom rule called 85-myasicamera.rules. Copy the entries for these two products into this rule. Replicate the entries within the rule.

The first pair keep as original. The second pair needs to have the last hex value change to what was written down. This model may have been dumped by a decision by ASI. Their SDK is built by ZWO. INDI consumes what ZWO gives.

Save into /lib/udev/rules.d.

Use: sudo udevadm control —reload-rules
Use: sudo udevadm trigger

Unplug and plug in the 290.

Use: sudo lsusb -v -d XXXX:XXXX

Does lsusb enumerate the 290? If yes, check the iProduct value. Look at its rule. Are they in agreement with each each other?

I have to do this dance for my QHYCCD devices. I have a custom rule just for these two devices. Both are USB 2.0. Fortunately for QHY, they provide a red light to confirm operation.
3 years 7 months ago #57503

Please Log in or Create an account to join the conversation.

  • Posts: 326
  • Thank you received: 49
You seem to be having a similar problem to mine. The issue seems to be in last week’s update/upgrade which made a major change to the linux ‘kernel’. Evidence is a bit patchy at the moment, but at least three of us (yourself, myself and @knro) have missing devices. It seems that the RPi OS does not fully recognise/operate USB2.0 devices. If you type lsusb to list your USB devices, you’ll possibly find that only Bus 002 is mentioned. In my case I would normally have 14 devices listed (including internal RPi elements, etc) but nowadays there are only four or five devices and all on Bus 002 which is the USB3.0 bus. The surprise for me is that not many of us have reported the problem............
3 years 7 months ago #57514

Please Log in or Create an account to join the conversation.

  • Posts: 145
  • Thank you received: 15
I reflashed my SD card with a clean Astroberry 2.0.2 image and my ASI290 is back again...! As expected. I restored my backup copy of the Astroberry home folder and almost all settings are back. Still have to implement boot from SSD and my wifi stick isn’t working yet (have to compile the driver), but I will get this sorted out as well.

Then I will stop making updates unless it’s absolutely necessary. The RPi is a tool for my hobby, not my hobby itself. It cost me 1 valuable, perfect night for M16, the last possibility this year. If the moon is gone again, M16 is too deep in the west for a senseful session. A pity. Thanks to an update I never needed. If it ain’t broke, don’t fix (or update) it.
3 years 7 months ago #57516

Please Log in or Create an account to join the conversation.

  • Posts: 326
  • Thank you received: 49
Great - likewise I’m running a fresh Astroberry 2.0.2 image exactly like you, and I’m sad I lost a clear night, but glad I lost only one. However, there are some interesting new features promised in KStars 3.5.0...............!
3 years 7 months ago #57518

Please Log in or Create an account to join the conversation.

  • Posts: 145
  • Thank you received: 15
Of course new features are worth an update. What I mean is I won't do updates just because there is an update and it has nothing to do with Kstars or PHD2 or something Astroberry-related. And having a proper backup of the whole system is mandatory. I have to figure out what's the best approach here.

In the mean time, I got an answer from the wifi stick's support (the driver was not running) and they told me I have to update to the latest kernel etc... :ohmy: after that my wifi stick will work, but my ASI290 will be gone again. So I have to hope that there will be a solution to have the latest Raspbian updates and the USB issue solved.

But nevertheless it's a good time for solving problems now since we have bright moon weeks... ;)
3 years 7 months ago #57527

Please Log in or Create an account to join the conversation.

  • Posts: 91
  • Thank you received: 18
kernel upgrade today on my RPi 4 gave me the same grief: ekos not finding the ASI120MM mini plugged into the USB2 hub on a ASI385MC.
For now I plugged the mini into a port on my PPBA and then ekos finds the mini. This is not a kstars/indilib upgrade issue since I have the same
kstars version I had prior to the kernel upgrade, which contained mostly python and raspian updates and no indilib/kstars lib updates.
The following user(s) said Thank You: Avocette
3 years 7 months ago #57700

Please Log in or Create an account to join the conversation.

  • Posts: 983
  • Thank you received: 375
Could you guys provide some detail on kernel version that works and the one that does not work for you?
3 years 7 months ago #57750

Please Log in or Create an account to join the conversation.

  • Posts: 326
  • Thank you received: 49
Hi Radek
I think the old kernel was 4.19 and the upgrade was to 5.4.
Best, Ed
The following user(s) said Thank You: Radek Kaczorek
3 years 7 months ago #57757

Please Log in or Create an account to join the conversation.

  • Posts: 145
  • Thank you received: 15
Same for me, 4.19 working vs. 5.4 not working.

CS,
Bernd
Last edit: 3 years 7 months ago by Bernd Limburg.
3 years 7 months ago #57785

Please Log in or Create an account to join the conversation.

Moderators: Radek Kaczorek
Time to create page: 1.380 seconds