Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

USB Timeout Transfer Error Using AR0135C #102

Open
smoise opened this issue May 21, 2019 · 8 comments
Open

USB Timeout Transfer Error Using AR0135C #102

smoise opened this issue May 21, 2019 · 8 comments

Comments

@smoise
Copy link

smoise commented May 21, 2019

Hello!

I'm having problems with the AR0135 C+USB3.0 Rev.C shield on Windows. when I run the USBTEST.exe, I'm able to connect perfectly fine and it says USB camera init success, but once I hit play I get the USB Transfer Timeout Error. Same thing happens over on the Python side and I get error 65318.

Looking at some of the other issues, I was thinking it could be because the configuration files for the AR0134 is not compatible with AR0135 C. I'm currently using the AR1034 config because there is no AR0135 C settings for python or C.

image
image

Any help would be much appreciated.

@ArduCAM
Copy link
Owner

ArduCAM commented May 22, 2019

AR0134 is almost the same as AR0135, you can find more info to diagnose the issue from: http://www.arducam.com/docs/camera-breakout-board/1-2mp-ar0134-ar0135-global-shutter/software-guide/
Please check the camera ID first to make sure the camera is well connected.

@sammo2828
Copy link

sammo2828 commented Jun 22, 2019

This is exactly the same problem I'm having.

Following @ArduCAM 's link, here is some new information.

First, the link has a configuration file for the AR0135 C model (not the AR0134), which is not in GitHub with the other .cfg files under Windows\GUI\USBTest\Release\Config.

Second, the link describes reading "register (0x0000) which can help diagnose if the I2C bus is accessable and distinguish the camera models":

image

For AR0135 C camera I was expecting RegAddr Read 0x0000 to be 0x754 as in the screenshot above, but I am getting 0x4155, which I guess is an error code. I can't find what the error code means, but I get the same error code when there is no camera attached to the shield.

I have quite a few pairs of Arducam UC-425 Rev.C USB3 shields with AR0135-C cameras. So far 3 out of 3 have the same error and I don't want to open the packaging of the remaining.

Also, I noticed that only 1 of the 3 shields will light up the LED located to the left under the UC-425 Rev.C printed on the board. However that doesn't make any difference in regards to not being able to transfer any video.

Please advise.

@ArduCAM
Copy link
Owner

ArduCAM commented Jun 24, 2019

If you can't read the correct register value, it means there is something wrong with the I2C interface between the USB camera shield to the sensor board.
Since you have so many cameras with the same problem I guess there is something wrong with the USB3 camera shield. Can you swap to another USB3 camera shield?

@sammo2828
Copy link

All of the USB3 camera shields have the same result. Maybe I am not connecting the ribbon cable properly? Do you have video/images showing a correct connection?

@ArduCAM
Copy link
Owner

ArduCAM commented Jun 25, 2019

@sammo2828
Please refer to this image I attached for you
USB3 0_FPC
FPC_CAM

@sammo2828
Copy link

Thanks. I think the problem was that I loaded the AR0134 cfg before loading the AR0135 cfg. After restarting the GUI and loading the AR0135 cfg it seems to play video.

Still, do you have any ideas why only one of my shields has a LED light turned on?

I noticed that only 1 of the 3 shields will light up the LED located to the left under the UC-425 Rev.C printed on the board.

@ArduCAM
Copy link
Owner

ArduCAM commented Jun 25, 2019

I'm not very sure about the LED issue. Are all the cameras and USB camera shields working now?

@sammo2828
Copy link

Yes, working now. No more timeout transfer error. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants