×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

ASI294MC-Pro 16 bit download problem.

  • Posts: 133
  • Thank you received: 33
This problem seems to be reported quite a bit. Have a look here indilib.org/forum/ccds-dslrs/5588-exposu...rockpro64.html#42635 there are links in that thread leading to other threads with the same/similar problems.
I have a NanoPC-T4 and ASI294MC Pro, with camera plugged into USB3.0 port in 8bit downloads will be successful up to around 10-20 images then goes into a loop. With 16 bit selected, usually only 1-5 images are downloaded before looping. Download always work fine when camera is plugged into a usb2.0 port.
Last week I installed Armbian 5.95 then from Armbian-config updated to kernel 5.3 and the problem is solved...but....networking doesn't work so for now I'm back to 5.95 with kernel 4.4.190.
4 years 6 months ago #43772

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

  • Posts: 989
  • Thank you received: 161
I feel like the problem mostly occurs with smaller, mobile hardware. With older much less elegant desktop hardware there seem to be fewer issues, regardless of Kernel version. My 294 was directly connected to an old chunky XPC (USB3) running Kubuntu 18.04 (Kernel 4, several versions) and is now connected to the same hardware with the OS updated to Kubuntu 19.04 (Kernel 5). No issues. My conclusion is the problem cannot be purely Kernel related (as some posters suspected in the threads mentioned). Just my impression.
Last edit: 4 years 6 months ago by Alfred. Reason: just to clarify the hardware is old and chunky but still it has a USB3 port which the cam is connected to
4 years 6 months ago #43775

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

  • Posts: 79
  • Thank you received: 13
Herrhausen, thanks for the suggestion
The solution is UNBELIEVABLE it all works if you connect the camera to the USB2 rather than USB3.
The threads quoted by starman345 point to a problem Unix Core problem, maybe only with the version running on Rock64
I assume that as I did an sudo apt update / sudo apt upgrade I have got the latest version. I am now running Armbian 5.3 but the problem persists.

It looks like it has to do with file size, the ASI294 generates an 11.7MB file which is twice as large as my ASI178MC. For smaller files including 8 bit USB3 works fine.
Just to check I set up a job to capture 120 x 5 sec 16 bit exposures with only a 1 sec delay and it works fine.

The shame is I ditched my old RPI3 to get the Rock64Pro for the USB3 port. It is however much faster on plate solving and other tasks
I wonder if any of the RPI4 early users are getting any problems with USB3 and large file size cameras?

At least it works now.
Thanks for the help!
Max
4 years 6 months ago #43776

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

  • Posts: 989
  • Thank you received: 161

Ok, this is a workaround until USB3 works properly. I'm glad you found a preliminary solution.

BTW, ASI 294 16bit RAW file size should be 22,3 MB.

I have no idea re Pi4. But USB3 definitely is worth the effort (and extra money) since it speeds things up remarkably and is a pleasure to work with. Hope you'll have a reliable USB3 port (driver issue?) soon.
4 years 6 months ago #43777

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

  • Posts: 989
  • Thank you received: 161

Ok, this is a workaround until USB3 works properly. I'm glad you found a preliminary solution.
BTW, ASI 294 16bit RAW file size should be 22,3 MB.


I have no idea re Pi4. But USB3 definitely is worth the effort (and extra money) since it speeds things up remarkably and is a pleasure to work with. Hope you'll have a reliable USB3 port (driver issue?) soon.
Last edit: 4 years 6 months ago by Alfred.
4 years 6 months ago #43778

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

  • Posts: 79
  • Thank you received: 13
BTW+ : ASI 294 16bit RAW file size should be 22,3 MB. yes on the host computer, as its expanded to 16 bit but I believe its a lot smaller on the camera where it is held on the camera in 14 bits, not sure of the exact encoding. Which raises the additional point about where the file structure encoding is done. Given 8 bit files transfer OK and 16 bit ones don't it suggests it might be done on the camera. But its not something I intend diving into.

My main concern is image quality. Is there any adverse effect in transferring the 16bit image via USB2 vs USB3? Given that the DDR Memory Buffer on the ASI294Pro was specifically designed to "minimize amp-glow, which is caused by the slow transfer speeds when the camera is used with a USB 2.0 port." maybe is does not matter
4 years 6 months ago #43781

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

  • Posts: 989
  • Thank you received: 161

Since you deduct dark frames the effect (if any!) should be invisible in your end result anyway. I would deem this alleged USB3 "advantage" a marketing story.
4 years 6 months ago #43784

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

  • Posts: 133
  • Thank you received: 33
I haven't found any image quality issues with USB2, just slower transfer speed than usb3. I have an A5X Max tv box with an older 3328 rockchip soc and the usb3 works fine with the asi294mc pro, the amp glow is still evident, less but still there. I've found the amp glow in the images is gone after calibration.

BTW, my ASI294MC Pro works fine with usb 3 plugged into my desktop PC running linuxmint
4 years 6 months ago #43786

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

  • Posts: 133
  • Thank you received: 33

I missed this question:
I've had my Rpi4 for a couple of weeks but haven't used it under the stars yet. Testing inside the house the camera (asi294 mc pro) works fine with its usb 3 ports.
4 years 6 months ago #43826

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

  • Posts: 43
  • Thank you received: 4
4 years 6 months ago #43829

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

  • Posts: 59
  • Thank you received: 19
Hello

I'd like confirm ecloud's idea that it is a Rock64 USB 3 problem., see Pine Rock64 forum or better if USB 2 and USB 3 devices are mixed, as the thread suggests.

I'm running Rock64 at the latest build:

Linux rock64 4.4.190-1233-rockchip-ayufan-gd3f1be0ed310 #1 SMP Wed Aug 28 08:59:34 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux

and use a ZWO ASI294MC camera and a USB WiFi dongle:

Ralink Technology, Corp. RT5370 Wireless Adapter

Having the camera and the WiFi dongle plugged in both at USB 2 port, besides that the camera has longer to download, the
system works. If I plug in the camera at the USB 3 port and reboot, the wireless connection speed is never faster than 1...10 Mb/s
(should be ca. 60 Mb/s). If I do the same while the system is running I loose WiFi connection at all (see log file at the end).

A possible solution:
If I use a powered USB 3 hub and connect all devices to the hub, while no device is attached to USB 2, I can even stream
at 4x4 binning with about 2.2 fps. Even under these circumstances the INDI GUI is still responsive.

Kind regards, wildi

Sep 25 16:09:34 rock64 kernel: [ 1595.124675] usb 1-1: USB disconnect, device number 4
Sep 25 16:09:36 rock64 kernel: [ 1597.764558] usb 5-1: new SuperSpeed USB device number 2 using xhci-hcd
Sep 25 16:09:36 rock64 kernel: [ 1597.781805] usb 5-1: New USB device found, idVendor=03c3, idProduct=294b
Sep 25 16:09:36 rock64 kernel: [ 1597.781838] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Sep 25 16:09:36 rock64 kernel: [ 1597.781860] usb 5-1: Product: ASI294MC
Sep 25 16:09:36 rock64 kernel: [ 1597.781881] usb 5-1: Manufacturer: ZWO
Sep 25 16:09:36 rock64 mtp-probe: checking bus 5, device 2: "/sys/devices/platform/usb@ff600000/ff600000.dwc3/xhci-hcd.10.auto/usb5/5-1"
Sep 25 16:09:36 rock64 mtp-probe: bus: 5, device: 2 was not an MTP device
Sep 25 16:09:37 rock64 systemd-networkd[2200]: wlx000f55a844e3: Lost carrier
Sep 25 16:09:37 rock64 avahi-daemon[495]: Withdrawing address record for 192.168.3.67 on wlx000f55a844e3.
Sep 25 16:09:37 rock64 systemd-networkd[2200]: wlx000f55a844e3: DHCP lease lost
Sep 25 16:09:37 rock64 avahi-daemon[495]: Leaving mDNS multicast group on interface wlx000f55a844e3.IPv4 with address 192.168.3.67.
Sep 25 16:09:38 rock64 wpa_supplicant[2199]: wlx000f55a844e3: CTRL-EVENT-DISCONNECTED bssid=24:65:11:ee:cd:dc reason=4 locally_generated=1
Sep 25 16:09:38 rock64 avahi-daemon[495]: Interface wlx000f55a844e3.IPv4 no longer relevant for mDNS.
4 years 6 months ago #43866

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

  • Posts: 59
  • Thank you received: 19
I forgot to mention the streaming setup:

2.2 fps: with ssh -X remote host, executing kstars, Ethernet connection

6 fps: local kstars via device manager, tab client name, host, port, WiFi connection.

bye wildi
4 years 6 months ago #43867

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

Time to create page: 0.359 seconds