Documentation Status

Cannot load information on name: rod4_node, distro: electric, which means that it is not yet in our index. Please see this page for information on how to submit your repository to our index.
Cannot load information on name: rod4_node, distro: fuerte, which means that it is not yet in our index. Please see this page for information on how to submit your repository to our index.
Cannot load information on name: rod4_node, distro: groovy, which means that it is not yet in our index. Please see this page for information on how to submit your repository to our index.
Cannot load information on name: rod4_node, distro: hydro, which means that it is not yet in our index. Please see this page for information on how to submit your repository to our index.
Cannot load information on name: rod4_node, distro: indigo, which means that it is not yet in our index. Please see this page for information on how to submit your repository to our index.

DEPRECATED: This node/package has been generalized to rotoscan_node.

leuze-rod4plus.jpg

Supported Hardware

The rod4_node driver currently supports ROD-4 models connected via Ethernet only, but could be extended to interface with RS422 models. The underlying network protocol implementation has been stable for more than a year now. All testing has been done with a "ROD4 plus" unit.

Configuration and Usage

rod4_node takes only two ROS parameters, one for the hostname/IP address of the laser range finder ("host") and one for the frame ID ("frame_id"). Configuration of the laser rangefinder is only possible through a separate (physical) configuration port with a vendor-provided tool and cannot be changed at runtime.

Otherwise, rod4_node should behave like any other ROS laser rangefinder driver, i.e., publish a sensor_msgs/LaserScan on the "scan" topic whenever a new scan comes in.

Wiki: rod4_node (last edited 2012-01-06 18:55:52 by FelixKolbe)