Attention: Answers.ros.org is deprecated as of August the 11th, 2023. Please visit robotics.stackexchange.com to ask a new question. This site will remain online in read-only mode during the transition and into the foreseeable future. Selected questions and answers have been migrated, and redirects have been put in place to direct users to the corresponding questions on Robotics Stack Exchange. Additional details are available here.

Best practice for creating new frame names?

asked 2017-03-31 20:47:20 -0500

Cerin
940 ●138 ●160 ●169

I have a simple two-wheeled platform, and I'm trying to publish ultrasonic range data via the standard range message type.

This message type requires a header with a frame_id. The sensors are attached to the part of the robot considered the "/base_link" frame. Should I use that as the frame, or should I create separate frames for each sensor to denote each sensor's unique position? If so, how should I name these? Should it be "/base_link/ultrasonic1" or just "/ultrasonic1"?

edit retag flag offensive close merge delete

add a comment

1 Answer

Sort by » oldest newest most voted

answered 2017-03-31 21:09:38 -0500

ahendrix

47576 ●179 ●367 ●662 http://namniart.com/

The frame IDs for sensors represent the coordinate frame origin for readings from that sensor, and most sensors report readings relative to the center of their transducer or other sensing element. Unless your sensor is mounted at exactly the same position as base_link, you should define a new frame for each sensor.

The frame naming is up to you, but most systems will use names like /ultrasonic1.

edit flag offensive delete link

add a comment

Question Tools

1 follower

Stats

Asked: 2017-03-31 20:47:20 -0500

Seen: 317 times

Last updated: Mar 31 '17

Best practice for creating new frame names? edit

1 Answer

Question Tools

Stats

Related questions

Best practice for creating new frame names?