-
Notifications
You must be signed in to change notification settings - Fork 90
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
TIM571-2050101 LIBUSB - Read Error: -7 or -9 #29
Comments
+1 on this, reproduced it in another machine and the driver also seems to be faulty. My log:
|
Do you have access to the device file ( |
@jspricke redid it as root user, i've updated the log. That's not the problem. |
Ah, you confused me with updating the complete comment, I usually prefer to do a new one with more information and use the edit button only to fix spelling. @mintar do you have time tomorrow to test it or give it to me? |
No, we didn't try using TCP/IP only with the USB. @vmayoral launched with the wrong launch file. But I have compiled the github repository and I have tried with the correct launch file and the result is the same. |
Ah, there was a problem with the device name containing spaces (or no spaces) at some point. Did you change it? |
@jspricke how can we change that? |
I think with the Windows software coming with it |
It's not the device name, since the problem happens before it even started to stream device data. The device name can only be a problem during parsing of the laser data. Let's look into this later today with our scanner. |
We just tested it with our scanner, and it works with the Sorry for not being more helpful. |
An other option would be to try TCP/IP. |
We haven't seen this issue appear with other TiM571 units but, if it's determined to be a hardware problem, let us know and we'll swap the scanners and try to resolve the issue in-house. |
Wow, that's a generous offer by SICK, given that they even donated some of those scanners to the ROS community! Before you take them up on it, I'd suggest you try to really make sure it's not a flaky power supply or broken USB cable. One other thing you could try is whether you can get distance measurements from the SICK SOPAS Windows software; that could rule out that it's really not our driver that's at fault. |
First at all, thank you for your support. Today I have checked the SICK SOPAS Windows software. I'm not able to connect with device. As you can see in the following picture. Windows recognizes the device (Device Manager) but the program can't connect with the device because it isn't able to find it. I haven't tried to connect the Laser with the Ethernet, because we need to connect the laser via USB. It's the first time that I use the SICK SOPAS software if anyone have any kind of suggestions it's more than welcome. |
@SICK-NorthAmerica, @SICK-Global, @mintar thanks for the kind support. We're aiming here to provide official support for SICK sensors in our artificial brains (http://erlerobotics.com/docs/Artificial_Brains/Erle-Brain2/index.html) and robots. We've tried different cables and Operating Systems and so far no luck.
I'm willing to give this a try. We are using USB for now, Where can we get the appropriate Ethernet cable to test this out? |
The appropriate Ethernet cable should be this one. You can get it either from SICK or probably from the vendor where you got your power adapter cable, I guess. |
We have just received and test the Ethernet cable and the laser is working fine. We have documented how it works in Erle-Brain 2 with ROS [1]. If someone have any ideas why the USB interfaces it isn't working it's most than welcome ;) [1] http://erlerobotics.com/Docs/Artificial_Brains/Additional_Devices/SICK_Laser_Scan Thank you everyone for your help |
Great to hear that it's now working for you! |
I'm having the same issue with my TiM571 using USB, unfortunately I don't have access to an Ethernet cable so I can't test it. It was working fine until today. dmesg ouput[ 1305.128734] usb 2-3: new high-speed USB device number 18 using xhci_hcd lsusb -vBus 002 Device 018: ID 19a2:5001 |
Update: got it to work on another ubuntu machine I have, which hasn't been updated in a while (at least one month). So this may be an issue with some package that has been updated. I've checked libsusb but both machines have the same version. Which other packages should I take a look at? |
@garyservin: Which version(s) of Ubuntu did you try? Did you check the access rights of the device file? |
Both machines have Lubuntu 14.04. I'm using the latest driver pulled from github and built yesterday with the same udev rules installed. I have permissions for the plugdev group for both users in both machines. I have checked the permissions for the device file and they are the same on both machines. I've also tried running the driver as root and it still didn't work. |
Update 3: @ahcorde can you try using the ROS' shadow repo and try again? Sorry for all the noise. |
I have the same situation with you, I've found the requests seems to diff from the terminal on SOPAS. Please ensure the command works on SOPAS's terminal first. My device is TIM310 btw. |
Hi,
I'm trying to work with the SICK laser TIM571-2050101. But I always received two different errors:
LIBUSB - Read Error: -7 (LIBUSB_ERROR_TIMEOUT) or LIBUSB - Read Error: -9 ( LIBUSB_ERROR_PIPE )
The error is in the function libusb_bulk_transfer of libusb
@vmayoral
The text was updated successfully, but these errors were encountered: