ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

em's profile - activity

2013-05-30 15:39:05 -0500 received badge  Famous Question (source)
2012-11-03 09:48:54 -0500 received badge  Famous Question (source)
2012-09-18 22:34:30 -0500 received badge  Notable Question (source)
2012-09-11 11:50:31 -0500 commented answer p2os teleop

I've checked that also, but didn't help - everything seemed fine.. One friend of mine helped me, the problem was with hardvare-the joystick wasn't compatible :/ anyway, it works now :)

2012-09-11 11:49:45 -0500 received badge  Popular Question (source)
2012-09-07 02:30:23 -0500 asked a question p2os teleop

Hi,

I'm using ros fuerte, pioneer 3dx robot and p2os(even though there's no version of p2os for ros fuerte, p2os works and i can publish cmd to robot - robot moves)..

so I need to use the joystick and to move robot manually. When I launch the teleop_joy.launch, it works well and it seems that connection is established, but pioneer doesn't move.

Since it didn't work, I've found this question http://answers.ros.org/question/39962/problem-with-p2os-teleop/ and did the remaping part in teleop_joy.launch:

remap from="/p2os_teleop/cmd_vel" to="/cmd_vel"

remap from="/p2os_teleop/joy" to ="/joy"

Again it didn't work. I also tried to include teleop_joy.launch in p2os.launch file, and again, connection is established and everyhing seems ok, but robot still dosen't move.. :/ when I call rxgraph function, I can see that cmd_vel is published from /p2os_teleop to /p2os driver.

any idea what else to do? thank you in advance for your help :)

2012-09-06 07:31:15 -0500 received badge  Notable Question (source)
2012-09-05 05:43:37 -0500 received badge  Supporter (source)
2012-09-05 03:46:37 -0500 received badge  Scholar (source)
2012-09-05 03:41:38 -0500 commented answer SICK lms problem/ A scan was probably missed

It started working, actually I got that message "Data stream started", so thank you :) (I installed it all again, and it just worked.. )

2012-09-04 14:51:27 -0500 received badge  Popular Question (source)
2012-09-04 09:44:36 -0500 received badge  Editor (source)
2012-09-04 08:13:23 -0500 received badge  Nice Question (source)
2012-09-04 07:54:49 -0500 received badge  Student (source)
2012-09-04 05:25:03 -0500 asked a question SICK lms problem/ A scan was probably missed

Hi, I'm having a problem for which I would appreciate any kind of help :)

I'm using ubuntu 10.04, installed ros - by following tutorial, and now i have to use sicklms200, so i installed sicktoolbox - also followed tutorial. When i try to connect to laser, problem which appears is a repeating message - "a scan was probably missed". So i looked for an answer, and got to this recommendation:

Fire up your favorite editor and open this file (your_ros_installation_directory)/ros/diamondback/stacks/sicktoolbox/build/sicktoolbox-1.0/c++/drivers/lms/sicklms-1.0/SickLMS.cc . Go to line 2319.
In this line, add the O_NDELAY flag as shown here:...(source: http://thebattlegoeson.blogspot.com/2011/06/xyz.html)

Problem is that I can't find this file SickLMS.cc, it simply dosen't exist in any of folders :/

I tried reinstalling sicktoolbox and sicktoolbox_wrapper using rosmake (like this:$ rosdep install sicktoolbox_wrapper rviz $ rosmake sicktoolbox_wrapper rviz)

i also find this answer: You'll need to install the laser_drivers stack from source in order to get all of the source files. I'm a total beginner with ros and ubuntu, and probably asking a stupid question, but what does this actually mean? Do i need to add some line in terminal when installing or...??

Again, I'm probably asking stupid questions, but really don't know what else to do or where to find answers so thank you in advance for any help..

edit: I've downloaded and installed the version of ros for ubuntu lucid 10.04 and it's ros fuerte (followed the tutorial http://www.ros.org/wiki/fuerte/Installation/Ubuntu, and installed full version as recommended )

thank you all for answers, I will check out if it works as soon as the SICK is available:)