Package Summary

Tags No category tags.
Version 1.0.15
License BSD
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/SawYer-Robotics/roch_robot.git
VCS Type git
VCS Version indigo
Last Updated 2018-12-17
Dev Status DEVELOPED
CI status Continuous Integration
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Package Description

Ult/psd/cliff to pointcloud: Publish Ult, cliff, and psd sensors events as points in a pointcloud, so navistack can use them for poor-man navigation. Implemented intended to run together with roch_base.

Additional Links

Maintainers

  • Carl

Authors

  • Carl
  • Jorge Santos Simon
README
No README found. See repository README.
CHANGELOG

Changelog for package roch_sensorpc

1.0.15 (2017-09-18)

1.0.14 (2017-05-08)

1.0.13 (2017-03-23)

1.0.12 (2017-02-16)

1.0.11 (2017-02-07)

  • Modify websites.
  • Add application of roch_sensorpc_nodelet used in install.

1.0.10 (2017-01-23)

  • Add author Jorge Santos Simon.

1.0.9 (2017-01-22)

1.0.8 (2017-01-22)

1.0.7 (2017-01-21)

1.0.6 (2017-01-17)

0.0.2 (2016-12-15)

  • Repatch some bugs that cannt modify all build-in parameters.
  • Contributors: Carl

0.0.1 (2016-11-30)

  • Refrence YujinRobot\' kobuki.
  • Contributors: Carl

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Package Dependencies

System Dependencies

No direct system dependencies.

Launch files

  • launch/standalone.launch
    • launch the ult/psd/cliff to pointcloud . Parameter pointcloud_radius gives the ult/psd/cliff pointcloud distance to base frame; Parameter ult/psd/cliff_enable gives the ult/psd/cliff enable. should be something like the robot radius plus plus costmap resolution plus an extra to cope with robot inertia. This is a bit tricky parameter: if it's too low, costmap will ignore this pointcloud (the robot footprint runs over the hit obstacle), but if it's too big, hit obstacles will be mapped too far from the robot and the navigation around them will probably fail.

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged roch_sensorpc at Robotics Stack Exchange

Package Summary

Tags No category tags.
Version 2.0.15
License BSD
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/SawYer-Robotics/roch_robot.git
VCS Type git
VCS Version kinetic
Last Updated 2018-11-27
Dev Status DEVELOPED
CI status Continuous Integration
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Package Description

Ult/psd/cliff to pointcloud: Publish Ult, cliff, and psd sensors events as points in a pointcloud, so navistack can use them for poor-man navigation. Implemented intended to run together with roch_base.

Additional Links

Maintainers

  • Chen

Authors

  • Chen
  • Jorge Santos Simon
README
No README found. See repository README.
CHANGELOG

Changelog for package roch_sensorpc

2.0.15 (2017-09-18)

2.0.14 (2017-09-18)

2.0.13 (2017-03-23)

1.0.13 (2017-03-23)

1.0.12 (2017-02-16)

1.0.11 (2017-02-07)

  • Modify websites.
  • Add application of roch_sensorpc_nodelet used in install.

1.0.10 (2017-01-23)

  • Add author Jorge Santos Simon.

1.0.9 (2017-01-22)

1.0.8 (2017-01-22)

1.0.7 (2017-01-21)

1.0.6 (2017-01-17)

0.0.2 (2016-12-15)

  • Repatch some bugs that cannt modify all build-in parameters.
  • Contributors: Carl

0.0.1 (2016-11-30)

  • Refrence YujinRobot\' kobuki.
  • Contributors: Carl

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Package Dependencies

System Dependencies

No direct system dependencies.

Dependant Packages

Launch files

  • launch/standalone.launch
    • launch the ult/psd/cliff to pointcloud . Parameter pointcloud_radius gives the ult/psd/cliff pointcloud distance to base frame; Parameter ult/psd/cliff_enable gives the ult/psd/cliff enable. should be something like the robot radius plus plus costmap resolution plus an extra to cope with robot inertia. This is a bit tricky parameter: if it's too low, costmap will ignore this pointcloud (the robot footprint runs over the hit obstacle), but if it's too big, hit obstacles will be mapped too far from the robot and the navigation around them will probably fail.

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged roch_sensorpc at Robotics Stack Exchange