-
Notifications
You must be signed in to change notification settings - Fork 101
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
Hang after "Connected to laser." #21
Comments
Does anyone have some screenshots of a sample configuration for their laser (SOPAS?). What protocol should be used on port 2111? |
The only thing I ever change when configuring an LMS111 is the IP address. Are you connecting through a router or switch? Try disabling any firewalls How is the ethernet port on your computer configured? Also, check your data cable. On Mon, Aug 31, 2015 at 11:32 AM, baronep [email protected] wrote:
Jeff Schmidt |
I have reset everything back to the default settings, tried plugging the laser into the computer directly as well as via a switch. I think network problems can be ruled out because I am able to see the laser data in SOPAS. Could it be a version mismatch with the TCP libraries? |
Hmmmm, so it appears to be working now. If I turn on debug the dropout messages are still there, so I guess those weren't a problem. |
Hi guys, according to my topic in here : #20 Could you help me from setting the parameters to connect the laser ? Thanks. |
I am trying to interface with my LMS111-10100 using ros-indigo-lms1xx by launching the LMS1xx.launch file.
Here is the output
Using GDB it appears that the issue originates in the getData() function, but I am unsure.
Any ideas?
The text was updated successfully, but these errors were encountered: