×

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

Bi-monthly release with minor bug fixes and improvements

ASI usb3 camera retries 3 times on exposure and fails - git builds

  • Posts: 1119
  • Thank you received: 182
It apparently only fixes part of the problem, though. See Brian's experience:

indilib.org/forum/ccds-dslrs/9089-indi-c....html?start=24#68959

Something else seems to be going on as well.
2 years 11 months ago #68964

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

  • Posts: 61
  • Thank you received: 10
"Leave usbfs_memory_mb up to system to decide instead of tampering with it"
That was the comment of the commit, Jasem did about usbfs_memory_mb.

That means, the system has to manage the size of usbfs_memory_mb itself. The problem is, Linux Kernel set the default usbfs_memory_mb to 16MB, which is too low for the bigger astro-cameras.

Before this commit, usbfs_memory_mb was set to 256MB using an udev-rule. Comparing, firecapture stable sets the memory to 200MB using an udev-rule as well.

Now the udev-rule is no longer used in indi, what means: default 16MB. Comparing, I didn´t find an udev-rule on firecapture 2.7beta, which means: usbfs_memory_mb default 16MB?

I managed this problem with setting usbfs_memory_mb to 1000MB globally, passing it as a kernel parameter on booting with grub2. Since I´m on openSUSE, I´m using Yast for this:

Yast / Bootloader / Kernel-Parameters: Add "usbcore.usbfs_memory_mb=1000" at the end of the string.

Just for info: The maximum possible usbfs_memory_mb is 2047MB. usbcore.usbfs_memory_mb=0 sets this maximum.

Edgar
2 years 11 months ago #68967

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

  • Posts: 466
  • Thank you received: 164
The 200MB setting comes originally from asi.rules file included with ASI Camera SDK.
2 years 11 months ago #68969

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

I asked Jim to see if this can be included on INDI (not 3rd party) as a post-install script. All the 3rd party driver had their own rules to apply this and some were conflicting without any checks now. So we have to find a universal way to update this ONLY if usbfs_memory_mb < 256, then it would be set to 256.
The following user(s) said Thank You: Jose Corazon
2 years 11 months ago #68970

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

  • Posts: 535
  • Thank you received: 109
Gave it some thought. Much consideration and ramblings can be found here: github.com/indilib/indi-3rdparty/pull/361
2 years 11 months ago #68976

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

  • Posts: 459
  • Thank you received: 69
I can't add useful information to this discussion except to note that issuing
sudo sh -c 'echo 256 > /sys/module/usbcore/parameters/usbfs_memory_mb'
fixes my connection problems with running the source code Build: 2021-03-19T15:18:51Z  for both my
ZWO ASI224MC guide camera and
Nikon Z7    (8256 x 5504) => 90.9 Mb fits files
the default usbfs_memory_mb on my ubuntu 20.0.4 was 16  (as noted elsewhere)
The stable version works for me (as one might expect).
Thanks
The following user(s) said Thank You: Jose Corazon
2 years 11 months ago #69020

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

  • Posts: 1119
  • Thank you received: 182

There are other users who still have problems with getting their ZWO-EAF recognized in the Indi Control Panel. 
Jasem, would increasing the usbfs_memory_mb be expected to solve that as well? 
As I wrote elsewhere, I had issues with getting my ZWO-EFW recognized by Indi, but that was fixed after I increased the memory to 256 and reinstalled the drivers.  However, that does not seem to work for Brian (starman365). 
Any suggestions for him?

Jo
2 years 11 months ago #69021

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

  • Posts: 61
  • Thank you received: 2
sudo sh -c 'echo 256 > /sys/module/usbcore/parameters/usbfs_memory_mb' solved it for me as well.

Another strong thing is the line:
2021-03-21T18:27:30: [ERROR] Failed to activate cooler.

Nevertheless, cooling and temperature regulation works on my ASI 1600.


EFW filter weel is detected and connected o.k.
2 years 11 months ago #69025

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

I've added back the rule now but it's generic for all USB devices and check if usbfs < 256 then sets it to 256. It's in GIT.
The following user(s) said Thank You: Jim
2 years 11 months ago #69049

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

  • Posts: 61
  • Thank you received: 10
@knro

Jasem, the rule  you´ve added does not work on my system (Tumbleweed):
edgar@Edgar-Desktop:~> cat /sys/module/usbcore/parameters/usbfs_memory_mb 16

Looks like cat /sys/module/usbcore/parameters/usbfs_memory_mb has to be set into "back apostrophes" (don´t know theright word in english :)

This is working for me:
ACTION=="add", SUBSYSTEM=="usb", RUN+="/bin/sh -c 'test -f /sys/module/usbcore/parameters/usbfs_memory_mb && test `cat /sys/module/usbcore/parameters/usbfs_memory_mb` -lt 256 && echo 256 > /sys/module/usbcore/parameters/usbfs_memory_mb'"
2 years 10 months ago #69441

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

  • Posts: 535
  • Thank you received: 109
I did not have time to look into this until tonight, as my skies have been rotten and other things are taking some time anyway.

The change included the script, but it was just missing the execution of the `cat` statement.

Seescho, those are called "grave accents" in English, the back single quote. Using grave accents is the older, non-POSIX  way of execution in a shell, so we should probably change that to the $() POSIX way. The grave accents would have the same effect, but
in the future may not be as compatible with new shells.

<code>ACTION=="add", SUBSYSTEM=="usb", RUN+="/bin/sh -c 'test -f /sys/module/usbcore/parameters/usbfs_memory_mb && test $(cat /sys/module/usbcore/parameters/usbfs_memory_mb) -lt 256 && echo 256 > /sys/module/usbcore/parameters/usbfs_memory_mb'"</code>

I just put a PR up for the change.

Jim

 
Last edit: 2 years 10 months ago by Jim.
2 years 10 months ago #69454

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

  • Posts: 61
  • Thank you received: 10
2 years 10 months ago #69604

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

Time to create page: 0.867 seconds