-
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
Sick Tim 310 USB ERROR TIMEOUT #7
Comments
The Rviz error probably means that you haven't selected a valid frame as a fixed frame in the global settings. Can you verify with Another thing you can try is to change the following line in
into:
Then recompile and test again. Also, it would be good if you could change the parameter |
Thanks, I'll try that and will let you know what happens. In the mean time here is the error log from the roslaunch. In case you needed to know our laptop is the HP Elitebook 8770w with an NVidia Quadro K3000M GFX card. The operating system is 64-bit, and the Ubuntu kernal is 3.5.0-45. |
Hm? I can't find it. |
Sorry, I guess that text file did not go thorugh. Here you go.
|
Yup, it's a 2D laser scanner, so it's expected that the output is in 2D. If you want 3D, you'll need to add a motor. :-) It makes sense that adding 100 to USB_TIMEOUT solves the timeout problems:
That just leaves the question why you need to change the number of fields to 591. I'd still be very interested in that rosbag. Since I don't have your device for testing, that would enable me to debug things better. Could you please do the following for me?
Thanks! |
Rosbag sent. |
Thanks for the bag! This allowed me to figure out why your datagrams only have 591 instead of 592 fields. This is the last part of your datagram:
This is the last part a datagram from the unisa bagfile that I used to implement the parser:
As you can see, your datagrams contain the string Since I believe the "not defined" thing is the factory default, I'll stick with the 592 fields for now. This means that either you'll have to use some SICK config tool again to set the scanner name to some string with two words (and then your scanner will work with our code), or you'll have to change the number to 591 on your side. You can do that easily by forking this repo on github; however, it'll be a little more work for you to keep up-to-date with this repo. I'll still change the USB timeout though and close this issue. |
This is necessary to make the tim310 work. It (strangely) only publishes with 1.875 Hz = one message every 533 ms, so a timeout of 500 ms always caused a LIBUSB_ERROR_TIMEOUT. This closes #7.
This is necessary to make the tim310 work. It (strangely) only publishes with 1.875 Hz = one message every 533 ms, so a timeout of 500 ms always caused a LIBUSB_ERROR_TIMEOUT. This closes #7.
I got a tim 571 , I changed the launch file and assigned a ip which the device has.I can ping the device from terminal. But with roslaunch I get no sick device connected.I can send you the log file later if necessary. |
1432245689.426975717 Node Startup |
Hi sacuar, Please don't post to closed issues with unrelated problems, but open a new one. Also, do you speaking of USB ethernet? Cheers Jochen |
Thanks jspricke... sorry, Iam new to the place so no idea. I have an Ethernet connection, and Tim571 15Hz, 0.333 degree resolution, and I used ros tim-3xx node and used tim551 launcher, because the manufacturer confirmed me that the protocols are same for Tim551 and Tim571 |
Locking this issue; please continue discussion at #27 . |
I am using the ROS Hydro version of the Sick_Tim3xx stack with a Sick_TIM310-1030000 (Sick Part Number: 1052627). We are operaing on a high end HP laptop running Ubuntu 12.04 LTS (I believe) and running ROS Hydro. To run the driver we are using the launch file by running "roslaunch sick_tim3xx sick_tim310.launch". We never get any valid outputs, all I see are errors. I don't have access to the log or the computer at the moment, I'll post them in a few hours when I get access to them, but from what I remember, the output is this over and over again:
And when I run rviz it states that 100% of the data was lost and that I should look in the Debug log.
Any help you can provide will be most appreciated.
The text was updated successfully, but these errors were encountered: