×

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

Bi-monthly release with minor bug fixes and improvements

USB Timeout problems with Atik 383L+

  • Posts: 171
  • Thank you received: 41
Hi :)

We received our new Atik 383L+ and I already tested it with INDI. When using full resolution of 3354x2529 pixels I get libusb timeouts :( When I change it to 3200x2500 everything works fine. atik_ccd_test also fails (output in attachment). We also have a 314L which works very fine with all tested setups.

Tested with (all failed):
* Banana Pi @Fedora 21
* ThinkPad X230 @Fedora 21
* Raspi B @Raspbian, driver package from homepage
* Desktop Core i7 based @Fedora 21and Ubuntu 14.10

Any ideas?

Greetings,
Christian
9 years 5 days ago #3708
Attachments:

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

  • Posts: 712
  • Thank you received: 174
Hi Chrisitan, this is not timeout, but LIBUSB_ERROR_IO. The reason is probably clear, ATIK 383L+ has resolution 3362x2504 and not 3354x2529. What I don't understand is where those figures come from, but will check it. Peter
9 years 5 days ago #3709

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

  • Posts: 171
  • Thank you received: 41
Yes, I also wondered about this difference. Maybe a change in new 383L+? We just bought it last week. I also checked with Windows 7 and Artemis Capture (works fine even with max. size) and get 3354x2529 too.

EDIT: At least @Raspi I've also seen timeouts
Last edit: 9 years 5 days ago by Christian.
9 years 5 days ago #3710

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

  • Posts: 712
  • Thank you received: 174
I don't have 383L+ anymore to check it but I found, that the resolution is reported incorrectly for other cameras as well. This is not the version issue, I found this incorrect figures in my old logs too. I'll check it with Atik.

BTW does it work with 3362x2504?

Raspi is another story, some of them simply doesn't work with some cameras and nobody know why. I suspect some powering issue.
9 years 5 days ago #3711

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

  • Posts: 171
  • Thank you received: 41
I will test tomorrow when I'm at university.
I also thought so, but with the lower value of 3200x2500 everything works fine there too. Will also check with 3362x2504.
Last edit: 9 years 5 days ago by Christian.
9 years 5 days ago #3712

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

  • Posts: 712
  • Thank you received: 174
I tried it with One9 and Titan and figures are also slightly different (1-2 pixels), but lower than actual CCD size so it doesn't fail. For VS it is OK. I'm not surprised it doesn't work with 383L, I'm surprised it did, I used it for development for years and never noticed this issue :-( Peter
9 years 5 days ago #3713

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

  • Posts: 171
  • Thank you received: 41
I had a look at Kodak documentation for the CCD chip: www.kodak.com/ek/uploadedFiles/Content/S...KAF-8300LongSpec.pdf

Correct size is 3326x2504 (*not* 3362 as written in Atik docs), when I enter these values everything works fine. The 3354x2529 value seems to come from the technical size of the chip, but Kodak says usable area is 3326x2504.

Greetings,
Christian
9 years 5 days ago #3723

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

  • Posts: 712
  • Thank you received: 174
It seems that returned value is not "size" but "max pixel index" so the value is correct for other cameras but not for 383L. I'll fix it with for this specific VID/PID... Peter
The following user(s) said Thank You: Christian
9 years 4 days ago #3724

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

  • Posts: 171
  • Thank you received: 41
Fixed with driver version 0.30 :) Thank you very much :)
8 years 9 months ago #4315

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

Time to create page: 0.724 seconds