Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Suspected bug in USARSim/ROS

Hi, After several attempts I have been able to generate a bag file containing logged

transform and laser scan data. when I type

root@ubuntu:~/fuerte_workspace/sandbox# rosbag info mylaserdata.bag

path: mylaserdata.bag

version: 2.0

duration: 7:28s (448s)

start: Oct 31 2013 21:20:39.34 (1383234639.34)

end: Oct 31 2013 21:28:07.46 (1383235087.46)

size: 3.7 MB

messages: 24650

compression: none [5/5 chunks]

*types: tf/tfMessage [94810edda583a504dfda3829e70d7eec]

topics: /tf 24650 msgs : tf/tfMessage (2 connections)*

But a standard bag from willow garage contains

types: sensor_msgs/LaserScan [90c7ef2dc6895d81024acba2ac42f369] tf/tfMessage [94810edda583a504dfda3829e70d7eec]

topics: /base_scan 924 msgs : sensor_msgs/LaserScan

          /tf          2769 msgs    : tf/tfMessage

I started gmapping by

rosrun gmapping slam_gmapping scan:=lms200 _odom_frame:=odom

so there is no information regarding /lms200.

rxgraph output gives no information of the error *but rviz information does not match with auto generated transform tree. There is no messeges in /lms200 and we have to manually add /lms200 *

PLZ help. I know this USARSim/Ros is used in robo cup as well but no one mentioned about the error.

Suspected bug in USARSim/ROS

Hi, After several attempts I have been able to generate a bag file containing logged

transform and laser scan data. when I type

root@ubuntu:~/fuerte_workspace/sandbox# rosbag info mylaserdata.bag

path: mylaserdata.bag

version: 2.0

duration: 7:28s (448s)

start: Oct 31 2013 21:20:39.34 (1383234639.34)

end: Oct 31 2013 21:28:07.46 (1383235087.46)

size: 3.7 MB

messages: 24650

compression: none [5/5 chunks]

*types: tf/tfMessage [94810edda583a504dfda3829e70d7eec]

topics: /tf 24650 msgs : tf/tfMessage (2 connections)*

But a standard bag from willow garage contains

types: sensor_msgs/LaserScan [90c7ef2dc6895d81024acba2ac42f369] tf/tfMessage [94810edda583a504dfda3829e70d7eec]

topics: /base_scan 924 msgs : sensor_msgs/LaserScan

          /tf          2769 msgs    : tf/tfMessage

I started gmapping by

rosrun gmapping slam_gmapping scan:=lms200 _odom_frame:=odom

so there is no information regarding /lms200./lms200.

rxgraph output gives no information of the error *but

but rviz information does not match with auto generated transform tree. There is no messeges in /lms200 and we have to manually add /lms200 *through rviz window

PLZ help. I know this USARSim/Ros is used in robo cup as well but no one mentioned about the error.

Suspected bug in USARSim/ROS

Hi, After several attempts I have been able to generate a bag file containing logged

transform and laser scan data. when I type

root@ubuntu:~/fuerte_workspace/sandbox# rosbag info mylaserdata.bag

path: mylaserdata.bag

version: 2.0

duration: 7:28s (448s)

start: Oct 31 2013 21:20:39.34 (1383234639.34)

end: Oct 31 2013 21:28:07.46 (1383235087.46)

size: 3.7 MB

messages: 24650

compression: none [5/5 chunks]

types: tf/tfMessage [94810edda583a504dfda3829e70d7eec]

topics: /tf 24650 msgs : tf/tfMessage (2 connections)

But a standard bag from willow garage contains

types: sensor_msgs/LaserScan [90c7ef2dc6895d81024acba2ac42f369] tf/tfMessage [94810edda583a504dfda3829e70d7eec]

topics: /base_scan 924 msgs : sensor_msgs/LaserScan

          /tf          2769 msgs    : tf/tfMessage

I started gmapping by

rosrun gmapping slam_gmapping scan:=lms200 _odom_frame:=odom

so there is no information regarding /lms200.

rxgraph output gives no information of the error

but rviz information does not match with auto generated transform tree. There is no messeges in /lms200 and we have to manually add /lms200 through rviz window

Again rostopic echo /lms200 to see if there are any published messages Then nothing appears.

PLZ help. I know this USARSim/Ros is used in robo cup as well but no one mentioned about the error.

Suspected bug in USARSim/ROS

Hi, After several attempts I have been able to generate a bag file containing logged

transform and laser scan data. when I type

root@ubuntu:~/fuerte_workspace/sandbox# rosbag info mylaserdata.bag

path: mylaserdata.bag

version: 2.0

duration: 7:28s (448s)

start: Oct 31 2013 21:20:39.34 (1383234639.34)

end: Oct 31 2013 21:28:07.46 (1383235087.46)

size: 3.7 MB

messages: 24650

compression: none [5/5 chunks]

types: tf/tfMessage [94810edda583a504dfda3829e70d7eec]

topics: /tf 24650 msgs : tf/tfMessage (2 connections)

But a standard bag from willow garage contains

types: sensor_msgs/LaserScan [90c7ef2dc6895d81024acba2ac42f369] tf/tfMessage [94810edda583a504dfda3829e70d7eec]

topics: /base_scan 924 msgs : sensor_msgs/LaserScan

          /tf          2769 msgs    : tf/tfMessage

I started gmapping by

rosrun gmapping slam_gmapping scan:=lms200 _odom_frame:=odom

so there is no information regarding /lms200.

rxgraph output gives no information of the error

but rviz information does not match with auto generated transform tree. There is no messeges in /lms200 and we have to manually add /lms200 through rviz window

Again rostopic echo /lms200 to see if there are any published messages Then nothing appears.

PLZ help. .

* I know this USARSim/Ros is used in robo cup as well but no one mentioned about the error.error.*

Suspected bug in USARSim/ROS

Hi, After several attempts I have been able to generate a bag file containing logged

transform and laser scan data. when I type

root@ubuntu:~/fuerte_workspace/sandbox# rosbag info mylaserdata.bag

path: mylaserdata.bag

version: 2.0

duration: 7:28s (448s)

start: Oct 31 2013 21:20:39.34 (1383234639.34)

end: Oct 31 2013 21:28:07.46 (1383235087.46)

size: 3.7 MB

messages: 24650

compression: none [5/5 chunks]

types: tf/tfMessage [94810edda583a504dfda3829e70d7eec]

topics: /tf 24650 msgs : tf/tfMessage (2 connections)

But a standard bag from willow garage contains

types: sensor_msgs/LaserScan [90c7ef2dc6895d81024acba2ac42f369] tf/tfMessage [94810edda583a504dfda3829e70d7eec]

topics: /base_scan 924 msgs : sensor_msgs/LaserScan

          /tf          2769 msgs    : tf/tfMessage

I started gmapping by

rosrun gmapping slam_gmapping scan:=lms200 _odom_frame:=odom

so there is no information regarding /lms200.

rxgraph output gives no information of the error image description

but rviz information does not match with auto generated transform tree. There is no messeges in /lms200 and we have to manually add /lms200 through rviz window image description

Again rostopic echo /lms200 to see if there are any published messages Then nothing appears.

PLZ help.

* I know this USARSim/Ros is used in robo cup as well but no one mentioned about the error.*