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.

Is there any benefit to write a driver node based on driver_base package

driver_base

asked 2015-08-10 21:13:19 -0500

Curtis Fu
3 ●1 ●2

updated 2015-08-10 23:46:16 -0500

Hi,

I'm using a customized 2D laser range finder (not SICK/HOKUYO). This laser range finder has its own protocol so I must write my own driver node to get the 2D scan and publish it in "sensor_msgs/LaserScan".

I'm wondering if I should write my own driver node based on "driver_base" package, like "hokuyo_node" package. Is there any benefit to use the "driver_base" package?

Thanks.

edit retag flag offensive close merge delete

add a comment

1 Answer

Sort by » oldest newest most voted

answered 2015-08-11 01:10:09 -0500

mgruhler

12390 ●32 ●193 ●173 https://github.com/mgruhler

I have never used it myself, but having a look at the WikiPage, it does not seem to be a good idea to use it, as it is deprecated.

A framework for writing drivers that helps with runtime reconfiguration, diagnostics and self-test. This package is deprecated.

API Stability This package is for internal use only. Its API is stable, but not recommended for use by new packages.

edit flag offensive delete link

add a comment

Question Tools

1 follower

Stats

Asked: 2015-08-10 21:13:19 -0500

Seen: 106 times

Last updated: Aug 11 '15

Is there any benefit to write a driver node based on driver_base package edit

1 Answer

Question Tools

Stats

Related questions

Is there any benefit to write a driver node based on driver_base package