No version for distro humble showing indigo. Known supported distros are highlighted in the buttons above.
Package symbol

spin_hokuyo package from spin_hokuyo repo

spin_hokuyo

ROS Distro
indigo

Package Summary

Tags No category tags.
Version 1.0.0
License GPL
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/RobustFieldAutonomyLab/spin_hokuyo.git
VCS Type git
VCS Version master
Last Updated 2017-10-16
Dev Status MAINTAINED
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

This package enables a 2D Hokuyo laser, connected to a Dynamixel servo motor, to produce a 3D point cloud that can be visualized in rviz and used to make an octomap.

Additional Links

No additional links.

Maintainers

  • Sarah Bertussi
  • Paul Szenher

Authors

No additional authors.

spin_hokuyo

This repository contains code to control a Dynamixel motor and a 2D Hokuyo LiDAR to create a 3D point cloud that can be visualized in rviz. This point cloud can then be used to create an octomap (code for this is not included in this repository).
Wiki Page: http://wiki.ros.org/spin_hokuyo

Setup Directions

  1. Download this ROS Package:

sudo apt-get install ros-indigo-spin-hokuyo

  1. In the tutorials/launch folder, update the basic_motors.launch file, go to line 12. These parameters are used to set up the dynamixel_motor package. In particular, make sure the port_name and baud_rate match your servo. Also, check that your motor id falls within the inclusive range from min_motor_id to max_motor_id.
  2. In the tutorials/launch folder, update the basic_motors.launch file, go to line 12. These parameters are used to set up the dynamixel_motor package. In particular, make sure the port_name and baud_rate match your servo. Also, check that your motor id falls within the inclusive range from min_motor_id to max_motor_id.
  3. Save and compile changes (if applicable).

roslaunch spin_hokuyo basic_motors.launch

  1. In a new terminal, open the rostopics list. There should be two new commands: /tilt_controller/command and /tilt_controller/state. /command will issue new positions to the motor via Float64 (try this using rostopic pub). /state will list various pieces of information about the motor (rostopic echo).
  2. If this is fully functional, kill the node and do:

roslaunch spin_hokuyo tilting_continuous.launch
This should cause the motor to regularly sweep from 90 to -90 and generate a point cloud. Be sure to update the dynamixel_servos_tilting.yaml for position, speed, etc.

Possible Dynamixel Errors

Is the USB properly inserted and setup for your computer?
Is the Dynamixel connected to a 12V power source via the adapter?
Is the switch on the USB adapter at the proper loaction?

Acknowledgements

Inspired by the work seen here: </br> https://github.com/gcc-robotics/3d_photobooth/blob/master/CapstoneFinalReport_VisionTeam.pdf </br>

Dynamixel Control

The class system used to control the Dynamixel motors and the basis for the servo template were based on the examples provided in Chap. 8 of “Effective Robotics Programming with ROS - Third Edition” by Anil Mahtani, Luis Sanchez, Enrique Fernandea, and Aaron Martinez. ##

pcl_assembler_client

The pcl_assembler_client is a modified form of the periodic_snapshotter.cpp which is included in the /examples folder of laser_assembler which is hosted at: https://github.com/ros-perception/laser_assembler ##

Authors

Sarah Bertussi, Paul Szenher, Shi Bai. RFAL (Robust Field Autonomy Lab), Stevens Institute of Technology.

CHANGELOG

Changelog for package spin_hokuyo

1.0.0 (2017-07-21)

  • Removed dyanmixel files in favor of using dependencies as the apt version now apparently works
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Fixed packages in launch files, as well as renamed and organized
  • Update README.md
  • Fixed dynamixel requirement to be subpackages
  • Added dynamixel_controllers to package.xml depends
  • Added dynamixel_controller to package.xml depends
  • Removed pcl as a dependent because it isn't a package
  • Added even more build depends to package.xml
  • Added required build dependencies to package.xml
  • Update package.xml
  • commenting update
  • Acknowledgements Update
  • Update README.md
  • commenting update
  • commenting update
  • commenting update
  • commenting update
  • commenting updates
  • Delete basic_motors.launch~
  • commenting updates
  • CMakeLists update
  • commenting updates
  • commenting update
  • Update CMakeLists.txt
  • Delete hokuyo_ground_filter.cpp
  • Delete floor_max_z.cpp
  • commenting update
  • commenting update
  • commenting update
  • comment update
  • remove backup file
  • remove backup file
  • adding back CMakeLists
  • Temporarilly removed CMakelist.txt to satisfy failed merge
  • organization
  • Delete CMakeLists.txt
  • moved dynamixel controllers
  • moved scan_to_pcl
  • Removed rviz config files and fixed tilting lidar continuous launch file
  • file location update
  • tutorials update
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Renamed misc files and updated launch files and CMakeLists accordingly
  • Delete combine_clouds.cpp
  • Update CMakeLists.txt
  • Update CMakeLists.txt
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Removed extraneous launch files
  • name updates
  • Rename combine_clouds_subscriber.cpp to point_cloud_assembler.cpp
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Renamed hokuyo_filter to hokuyo_robot_filter to fit the naming convention of hokuyo_ground_filter
  • rename for clarity
  • typo
  • file renames
  • Delete combine_clouds.cpp
  • Removed floor removal parameter from octomap
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Removed Plane Extract Ransac from tilting lidar and made minor modifications to launch and cpp files
  • reset clouds
  • Modified combined clouds to allow for parameters and options between time and subscription, changed launch files to allow for further customizations
  • Added support for hokuyo_ground_filter
  • added tolerance
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • remove ground
  • Modified launch files for more universal use and added segmentation launch file and rviz config
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Modified to allow for parameter value to change from dynamixel tilting callback to timer callback
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo Conflicts: tilting_lidar_clean/launch/launch_with_octo/velodyne_hokuyo_octo_tilt_offline.launch
  • plane extraction
  • Disabled Voxel grid as it is uneccesary for non-assembled point clouds
  • Changed name argument to path, requiring full path to be input at launch but allows for universal use across systems
  • Removed rosbag node from online launch file

File truncated at 100 lines see the full file

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Launch files

  • launch/tilt_continuous.launch
    • This launch file causes the Hokuyo to sweep back and forth CONTINUOUSLY
      • assemble [default: velodyne_points]
  • launch/tilt_subscriber.launch
    • This launch file causes the Hokuyo to sweep back and forth ONLY WHEN AN EMPTY MESSAGE is sent to tilt_motor_subscribe node
      • assemble [default: velodyne_points]
  • tutorials/launch/basic_motors.launch
    • This file executes a simple launch of the Dynamixel servo that allows the operator to manually input values for the servo to rotate to. The Hokuyo IS NOT part of this launch.

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged spin_hokuyo at Robotics Stack Exchange

No version for distro jazzy showing indigo. Known supported distros are highlighted in the buttons above.
Package symbol

spin_hokuyo package from spin_hokuyo repo

spin_hokuyo

ROS Distro
indigo

Package Summary

Tags No category tags.
Version 1.0.0
License GPL
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/RobustFieldAutonomyLab/spin_hokuyo.git
VCS Type git
VCS Version master
Last Updated 2017-10-16
Dev Status MAINTAINED
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

This package enables a 2D Hokuyo laser, connected to a Dynamixel servo motor, to produce a 3D point cloud that can be visualized in rviz and used to make an octomap.

Additional Links

No additional links.

Maintainers

  • Sarah Bertussi
  • Paul Szenher

Authors

No additional authors.

spin_hokuyo

This repository contains code to control a Dynamixel motor and a 2D Hokuyo LiDAR to create a 3D point cloud that can be visualized in rviz. This point cloud can then be used to create an octomap (code for this is not included in this repository).
Wiki Page: http://wiki.ros.org/spin_hokuyo

Setup Directions

  1. Download this ROS Package:

sudo apt-get install ros-indigo-spin-hokuyo

  1. In the tutorials/launch folder, update the basic_motors.launch file, go to line 12. These parameters are used to set up the dynamixel_motor package. In particular, make sure the port_name and baud_rate match your servo. Also, check that your motor id falls within the inclusive range from min_motor_id to max_motor_id.
  2. In the tutorials/launch folder, update the basic_motors.launch file, go to line 12. These parameters are used to set up the dynamixel_motor package. In particular, make sure the port_name and baud_rate match your servo. Also, check that your motor id falls within the inclusive range from min_motor_id to max_motor_id.
  3. Save and compile changes (if applicable).

roslaunch spin_hokuyo basic_motors.launch

  1. In a new terminal, open the rostopics list. There should be two new commands: /tilt_controller/command and /tilt_controller/state. /command will issue new positions to the motor via Float64 (try this using rostopic pub). /state will list various pieces of information about the motor (rostopic echo).
  2. If this is fully functional, kill the node and do:

roslaunch spin_hokuyo tilting_continuous.launch
This should cause the motor to regularly sweep from 90 to -90 and generate a point cloud. Be sure to update the dynamixel_servos_tilting.yaml for position, speed, etc.

Possible Dynamixel Errors

Is the USB properly inserted and setup for your computer?
Is the Dynamixel connected to a 12V power source via the adapter?
Is the switch on the USB adapter at the proper loaction?

Acknowledgements

Inspired by the work seen here: </br> https://github.com/gcc-robotics/3d_photobooth/blob/master/CapstoneFinalReport_VisionTeam.pdf </br>

Dynamixel Control

The class system used to control the Dynamixel motors and the basis for the servo template were based on the examples provided in Chap. 8 of “Effective Robotics Programming with ROS - Third Edition” by Anil Mahtani, Luis Sanchez, Enrique Fernandea, and Aaron Martinez. ##

pcl_assembler_client

The pcl_assembler_client is a modified form of the periodic_snapshotter.cpp which is included in the /examples folder of laser_assembler which is hosted at: https://github.com/ros-perception/laser_assembler ##

Authors

Sarah Bertussi, Paul Szenher, Shi Bai. RFAL (Robust Field Autonomy Lab), Stevens Institute of Technology.

CHANGELOG

Changelog for package spin_hokuyo

1.0.0 (2017-07-21)

  • Removed dyanmixel files in favor of using dependencies as the apt version now apparently works
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Fixed packages in launch files, as well as renamed and organized
  • Update README.md
  • Fixed dynamixel requirement to be subpackages
  • Added dynamixel_controllers to package.xml depends
  • Added dynamixel_controller to package.xml depends
  • Removed pcl as a dependent because it isn't a package
  • Added even more build depends to package.xml
  • Added required build dependencies to package.xml
  • Update package.xml
  • commenting update
  • Acknowledgements Update
  • Update README.md
  • commenting update
  • commenting update
  • commenting update
  • commenting update
  • commenting updates
  • Delete basic_motors.launch~
  • commenting updates
  • CMakeLists update
  • commenting updates
  • commenting update
  • Update CMakeLists.txt
  • Delete hokuyo_ground_filter.cpp
  • Delete floor_max_z.cpp
  • commenting update
  • commenting update
  • commenting update
  • comment update
  • remove backup file
  • remove backup file
  • adding back CMakeLists
  • Temporarilly removed CMakelist.txt to satisfy failed merge
  • organization
  • Delete CMakeLists.txt
  • moved dynamixel controllers
  • moved scan_to_pcl
  • Removed rviz config files and fixed tilting lidar continuous launch file
  • file location update
  • tutorials update
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Renamed misc files and updated launch files and CMakeLists accordingly
  • Delete combine_clouds.cpp
  • Update CMakeLists.txt
  • Update CMakeLists.txt
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Removed extraneous launch files
  • name updates
  • Rename combine_clouds_subscriber.cpp to point_cloud_assembler.cpp
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Renamed hokuyo_filter to hokuyo_robot_filter to fit the naming convention of hokuyo_ground_filter
  • rename for clarity
  • typo
  • file renames
  • Delete combine_clouds.cpp
  • Removed floor removal parameter from octomap
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Removed Plane Extract Ransac from tilting lidar and made minor modifications to launch and cpp files
  • reset clouds
  • Modified combined clouds to allow for parameters and options between time and subscription, changed launch files to allow for further customizations
  • Added support for hokuyo_ground_filter
  • added tolerance
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • remove ground
  • Modified launch files for more universal use and added segmentation launch file and rviz config
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Modified to allow for parameter value to change from dynamixel tilting callback to timer callback
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo Conflicts: tilting_lidar_clean/launch/launch_with_octo/velodyne_hokuyo_octo_tilt_offline.launch
  • plane extraction
  • Disabled Voxel grid as it is uneccesary for non-assembled point clouds
  • Changed name argument to path, requiring full path to be input at launch but allows for universal use across systems
  • Removed rosbag node from online launch file

File truncated at 100 lines see the full file

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Launch files

  • launch/tilt_continuous.launch
    • This launch file causes the Hokuyo to sweep back and forth CONTINUOUSLY
      • assemble [default: velodyne_points]
  • launch/tilt_subscriber.launch
    • This launch file causes the Hokuyo to sweep back and forth ONLY WHEN AN EMPTY MESSAGE is sent to tilt_motor_subscribe node
      • assemble [default: velodyne_points]
  • tutorials/launch/basic_motors.launch
    • This file executes a simple launch of the Dynamixel servo that allows the operator to manually input values for the servo to rotate to. The Hokuyo IS NOT part of this launch.

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged spin_hokuyo at Robotics Stack Exchange

No version for distro kilted showing indigo. Known supported distros are highlighted in the buttons above.
Package symbol

spin_hokuyo package from spin_hokuyo repo

spin_hokuyo

ROS Distro
indigo

Package Summary

Tags No category tags.
Version 1.0.0
License GPL
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/RobustFieldAutonomyLab/spin_hokuyo.git
VCS Type git
VCS Version master
Last Updated 2017-10-16
Dev Status MAINTAINED
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

This package enables a 2D Hokuyo laser, connected to a Dynamixel servo motor, to produce a 3D point cloud that can be visualized in rviz and used to make an octomap.

Additional Links

No additional links.

Maintainers

  • Sarah Bertussi
  • Paul Szenher

Authors

No additional authors.

spin_hokuyo

This repository contains code to control a Dynamixel motor and a 2D Hokuyo LiDAR to create a 3D point cloud that can be visualized in rviz. This point cloud can then be used to create an octomap (code for this is not included in this repository).
Wiki Page: http://wiki.ros.org/spin_hokuyo

Setup Directions

  1. Download this ROS Package:

sudo apt-get install ros-indigo-spin-hokuyo

  1. In the tutorials/launch folder, update the basic_motors.launch file, go to line 12. These parameters are used to set up the dynamixel_motor package. In particular, make sure the port_name and baud_rate match your servo. Also, check that your motor id falls within the inclusive range from min_motor_id to max_motor_id.
  2. In the tutorials/launch folder, update the basic_motors.launch file, go to line 12. These parameters are used to set up the dynamixel_motor package. In particular, make sure the port_name and baud_rate match your servo. Also, check that your motor id falls within the inclusive range from min_motor_id to max_motor_id.
  3. Save and compile changes (if applicable).

roslaunch spin_hokuyo basic_motors.launch

  1. In a new terminal, open the rostopics list. There should be two new commands: /tilt_controller/command and /tilt_controller/state. /command will issue new positions to the motor via Float64 (try this using rostopic pub). /state will list various pieces of information about the motor (rostopic echo).
  2. If this is fully functional, kill the node and do:

roslaunch spin_hokuyo tilting_continuous.launch
This should cause the motor to regularly sweep from 90 to -90 and generate a point cloud. Be sure to update the dynamixel_servos_tilting.yaml for position, speed, etc.

Possible Dynamixel Errors

Is the USB properly inserted and setup for your computer?
Is the Dynamixel connected to a 12V power source via the adapter?
Is the switch on the USB adapter at the proper loaction?

Acknowledgements

Inspired by the work seen here: </br> https://github.com/gcc-robotics/3d_photobooth/blob/master/CapstoneFinalReport_VisionTeam.pdf </br>

Dynamixel Control

The class system used to control the Dynamixel motors and the basis for the servo template were based on the examples provided in Chap. 8 of “Effective Robotics Programming with ROS - Third Edition” by Anil Mahtani, Luis Sanchez, Enrique Fernandea, and Aaron Martinez. ##

pcl_assembler_client

The pcl_assembler_client is a modified form of the periodic_snapshotter.cpp which is included in the /examples folder of laser_assembler which is hosted at: https://github.com/ros-perception/laser_assembler ##

Authors

Sarah Bertussi, Paul Szenher, Shi Bai. RFAL (Robust Field Autonomy Lab), Stevens Institute of Technology.

CHANGELOG

Changelog for package spin_hokuyo

1.0.0 (2017-07-21)

  • Removed dyanmixel files in favor of using dependencies as the apt version now apparently works
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Fixed packages in launch files, as well as renamed and organized
  • Update README.md
  • Fixed dynamixel requirement to be subpackages
  • Added dynamixel_controllers to package.xml depends
  • Added dynamixel_controller to package.xml depends
  • Removed pcl as a dependent because it isn't a package
  • Added even more build depends to package.xml
  • Added required build dependencies to package.xml
  • Update package.xml
  • commenting update
  • Acknowledgements Update
  • Update README.md
  • commenting update
  • commenting update
  • commenting update
  • commenting update
  • commenting updates
  • Delete basic_motors.launch~
  • commenting updates
  • CMakeLists update
  • commenting updates
  • commenting update
  • Update CMakeLists.txt
  • Delete hokuyo_ground_filter.cpp
  • Delete floor_max_z.cpp
  • commenting update
  • commenting update
  • commenting update
  • comment update
  • remove backup file
  • remove backup file
  • adding back CMakeLists
  • Temporarilly removed CMakelist.txt to satisfy failed merge
  • organization
  • Delete CMakeLists.txt
  • moved dynamixel controllers
  • moved scan_to_pcl
  • Removed rviz config files and fixed tilting lidar continuous launch file
  • file location update
  • tutorials update
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Renamed misc files and updated launch files and CMakeLists accordingly
  • Delete combine_clouds.cpp
  • Update CMakeLists.txt
  • Update CMakeLists.txt
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Removed extraneous launch files
  • name updates
  • Rename combine_clouds_subscriber.cpp to point_cloud_assembler.cpp
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Renamed hokuyo_filter to hokuyo_robot_filter to fit the naming convention of hokuyo_ground_filter
  • rename for clarity
  • typo
  • file renames
  • Delete combine_clouds.cpp
  • Removed floor removal parameter from octomap
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Removed Plane Extract Ransac from tilting lidar and made minor modifications to launch and cpp files
  • reset clouds
  • Modified combined clouds to allow for parameters and options between time and subscription, changed launch files to allow for further customizations
  • Added support for hokuyo_ground_filter
  • added tolerance
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • remove ground
  • Modified launch files for more universal use and added segmentation launch file and rviz config
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Modified to allow for parameter value to change from dynamixel tilting callback to timer callback
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo Conflicts: tilting_lidar_clean/launch/launch_with_octo/velodyne_hokuyo_octo_tilt_offline.launch
  • plane extraction
  • Disabled Voxel grid as it is uneccesary for non-assembled point clouds
  • Changed name argument to path, requiring full path to be input at launch but allows for universal use across systems
  • Removed rosbag node from online launch file

File truncated at 100 lines see the full file

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Launch files

  • launch/tilt_continuous.launch
    • This launch file causes the Hokuyo to sweep back and forth CONTINUOUSLY
      • assemble [default: velodyne_points]
  • launch/tilt_subscriber.launch
    • This launch file causes the Hokuyo to sweep back and forth ONLY WHEN AN EMPTY MESSAGE is sent to tilt_motor_subscribe node
      • assemble [default: velodyne_points]
  • tutorials/launch/basic_motors.launch
    • This file executes a simple launch of the Dynamixel servo that allows the operator to manually input values for the servo to rotate to. The Hokuyo IS NOT part of this launch.

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged spin_hokuyo at Robotics Stack Exchange

No version for distro rolling showing indigo. Known supported distros are highlighted in the buttons above.
Package symbol

spin_hokuyo package from spin_hokuyo repo

spin_hokuyo

ROS Distro
indigo

Package Summary

Tags No category tags.
Version 1.0.0
License GPL
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/RobustFieldAutonomyLab/spin_hokuyo.git
VCS Type git
VCS Version master
Last Updated 2017-10-16
Dev Status MAINTAINED
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

This package enables a 2D Hokuyo laser, connected to a Dynamixel servo motor, to produce a 3D point cloud that can be visualized in rviz and used to make an octomap.

Additional Links

No additional links.

Maintainers

  • Sarah Bertussi
  • Paul Szenher

Authors

No additional authors.

spin_hokuyo

This repository contains code to control a Dynamixel motor and a 2D Hokuyo LiDAR to create a 3D point cloud that can be visualized in rviz. This point cloud can then be used to create an octomap (code for this is not included in this repository).
Wiki Page: http://wiki.ros.org/spin_hokuyo

Setup Directions

  1. Download this ROS Package:

sudo apt-get install ros-indigo-spin-hokuyo

  1. In the tutorials/launch folder, update the basic_motors.launch file, go to line 12. These parameters are used to set up the dynamixel_motor package. In particular, make sure the port_name and baud_rate match your servo. Also, check that your motor id falls within the inclusive range from min_motor_id to max_motor_id.
  2. In the tutorials/launch folder, update the basic_motors.launch file, go to line 12. These parameters are used to set up the dynamixel_motor package. In particular, make sure the port_name and baud_rate match your servo. Also, check that your motor id falls within the inclusive range from min_motor_id to max_motor_id.
  3. Save and compile changes (if applicable).

roslaunch spin_hokuyo basic_motors.launch

  1. In a new terminal, open the rostopics list. There should be two new commands: /tilt_controller/command and /tilt_controller/state. /command will issue new positions to the motor via Float64 (try this using rostopic pub). /state will list various pieces of information about the motor (rostopic echo).
  2. If this is fully functional, kill the node and do:

roslaunch spin_hokuyo tilting_continuous.launch
This should cause the motor to regularly sweep from 90 to -90 and generate a point cloud. Be sure to update the dynamixel_servos_tilting.yaml for position, speed, etc.

Possible Dynamixel Errors

Is the USB properly inserted and setup for your computer?
Is the Dynamixel connected to a 12V power source via the adapter?
Is the switch on the USB adapter at the proper loaction?

Acknowledgements

Inspired by the work seen here: </br> https://github.com/gcc-robotics/3d_photobooth/blob/master/CapstoneFinalReport_VisionTeam.pdf </br>

Dynamixel Control

The class system used to control the Dynamixel motors and the basis for the servo template were based on the examples provided in Chap. 8 of “Effective Robotics Programming with ROS - Third Edition” by Anil Mahtani, Luis Sanchez, Enrique Fernandea, and Aaron Martinez. ##

pcl_assembler_client

The pcl_assembler_client is a modified form of the periodic_snapshotter.cpp which is included in the /examples folder of laser_assembler which is hosted at: https://github.com/ros-perception/laser_assembler ##

Authors

Sarah Bertussi, Paul Szenher, Shi Bai. RFAL (Robust Field Autonomy Lab), Stevens Institute of Technology.

CHANGELOG

Changelog for package spin_hokuyo

1.0.0 (2017-07-21)

  • Removed dyanmixel files in favor of using dependencies as the apt version now apparently works
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Fixed packages in launch files, as well as renamed and organized
  • Update README.md
  • Fixed dynamixel requirement to be subpackages
  • Added dynamixel_controllers to package.xml depends
  • Added dynamixel_controller to package.xml depends
  • Removed pcl as a dependent because it isn't a package
  • Added even more build depends to package.xml
  • Added required build dependencies to package.xml
  • Update package.xml
  • commenting update
  • Acknowledgements Update
  • Update README.md
  • commenting update
  • commenting update
  • commenting update
  • commenting update
  • commenting updates
  • Delete basic_motors.launch~
  • commenting updates
  • CMakeLists update
  • commenting updates
  • commenting update
  • Update CMakeLists.txt
  • Delete hokuyo_ground_filter.cpp
  • Delete floor_max_z.cpp
  • commenting update
  • commenting update
  • commenting update
  • comment update
  • remove backup file
  • remove backup file
  • adding back CMakeLists
  • Temporarilly removed CMakelist.txt to satisfy failed merge
  • organization
  • Delete CMakeLists.txt
  • moved dynamixel controllers
  • moved scan_to_pcl
  • Removed rviz config files and fixed tilting lidar continuous launch file
  • file location update
  • tutorials update
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Renamed misc files and updated launch files and CMakeLists accordingly
  • Delete combine_clouds.cpp
  • Update CMakeLists.txt
  • Update CMakeLists.txt
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Removed extraneous launch files
  • name updates
  • Rename combine_clouds_subscriber.cpp to point_cloud_assembler.cpp
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Renamed hokuyo_filter to hokuyo_robot_filter to fit the naming convention of hokuyo_ground_filter
  • rename for clarity
  • typo
  • file renames
  • Delete combine_clouds.cpp
  • Removed floor removal parameter from octomap
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Removed Plane Extract Ransac from tilting lidar and made minor modifications to launch and cpp files
  • reset clouds
  • Modified combined clouds to allow for parameters and options between time and subscription, changed launch files to allow for further customizations
  • Added support for hokuyo_ground_filter
  • added tolerance
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • remove ground
  • Modified launch files for more universal use and added segmentation launch file and rviz config
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Modified to allow for parameter value to change from dynamixel tilting callback to timer callback
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo Conflicts: tilting_lidar_clean/launch/launch_with_octo/velodyne_hokuyo_octo_tilt_offline.launch
  • plane extraction
  • Disabled Voxel grid as it is uneccesary for non-assembled point clouds
  • Changed name argument to path, requiring full path to be input at launch but allows for universal use across systems
  • Removed rosbag node from online launch file

File truncated at 100 lines see the full file

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Launch files

  • launch/tilt_continuous.launch
    • This launch file causes the Hokuyo to sweep back and forth CONTINUOUSLY
      • assemble [default: velodyne_points]
  • launch/tilt_subscriber.launch
    • This launch file causes the Hokuyo to sweep back and forth ONLY WHEN AN EMPTY MESSAGE is sent to tilt_motor_subscribe node
      • assemble [default: velodyne_points]
  • tutorials/launch/basic_motors.launch
    • This file executes a simple launch of the Dynamixel servo that allows the operator to manually input values for the servo to rotate to. The Hokuyo IS NOT part of this launch.

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged spin_hokuyo at Robotics Stack Exchange

No version for distro ardent showing indigo. Known supported distros are highlighted in the buttons above.
Package symbol

spin_hokuyo package from spin_hokuyo repo

spin_hokuyo

ROS Distro
indigo

Package Summary

Tags No category tags.
Version 1.0.0
License GPL
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/RobustFieldAutonomyLab/spin_hokuyo.git
VCS Type git
VCS Version master
Last Updated 2017-10-16
Dev Status MAINTAINED
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

This package enables a 2D Hokuyo laser, connected to a Dynamixel servo motor, to produce a 3D point cloud that can be visualized in rviz and used to make an octomap.

Additional Links

No additional links.

Maintainers

  • Sarah Bertussi
  • Paul Szenher

Authors

No additional authors.

spin_hokuyo

This repository contains code to control a Dynamixel motor and a 2D Hokuyo LiDAR to create a 3D point cloud that can be visualized in rviz. This point cloud can then be used to create an octomap (code for this is not included in this repository).
Wiki Page: http://wiki.ros.org/spin_hokuyo

Setup Directions

  1. Download this ROS Package:

sudo apt-get install ros-indigo-spin-hokuyo

  1. In the tutorials/launch folder, update the basic_motors.launch file, go to line 12. These parameters are used to set up the dynamixel_motor package. In particular, make sure the port_name and baud_rate match your servo. Also, check that your motor id falls within the inclusive range from min_motor_id to max_motor_id.
  2. In the tutorials/launch folder, update the basic_motors.launch file, go to line 12. These parameters are used to set up the dynamixel_motor package. In particular, make sure the port_name and baud_rate match your servo. Also, check that your motor id falls within the inclusive range from min_motor_id to max_motor_id.
  3. Save and compile changes (if applicable).

roslaunch spin_hokuyo basic_motors.launch

  1. In a new terminal, open the rostopics list. There should be two new commands: /tilt_controller/command and /tilt_controller/state. /command will issue new positions to the motor via Float64 (try this using rostopic pub). /state will list various pieces of information about the motor (rostopic echo).
  2. If this is fully functional, kill the node and do:

roslaunch spin_hokuyo tilting_continuous.launch
This should cause the motor to regularly sweep from 90 to -90 and generate a point cloud. Be sure to update the dynamixel_servos_tilting.yaml for position, speed, etc.

Possible Dynamixel Errors

Is the USB properly inserted and setup for your computer?
Is the Dynamixel connected to a 12V power source via the adapter?
Is the switch on the USB adapter at the proper loaction?

Acknowledgements

Inspired by the work seen here: </br> https://github.com/gcc-robotics/3d_photobooth/blob/master/CapstoneFinalReport_VisionTeam.pdf </br>

Dynamixel Control

The class system used to control the Dynamixel motors and the basis for the servo template were based on the examples provided in Chap. 8 of “Effective Robotics Programming with ROS - Third Edition” by Anil Mahtani, Luis Sanchez, Enrique Fernandea, and Aaron Martinez. ##

pcl_assembler_client

The pcl_assembler_client is a modified form of the periodic_snapshotter.cpp which is included in the /examples folder of laser_assembler which is hosted at: https://github.com/ros-perception/laser_assembler ##

Authors

Sarah Bertussi, Paul Szenher, Shi Bai. RFAL (Robust Field Autonomy Lab), Stevens Institute of Technology.

CHANGELOG

Changelog for package spin_hokuyo

1.0.0 (2017-07-21)

  • Removed dyanmixel files in favor of using dependencies as the apt version now apparently works
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Fixed packages in launch files, as well as renamed and organized
  • Update README.md
  • Fixed dynamixel requirement to be subpackages
  • Added dynamixel_controllers to package.xml depends
  • Added dynamixel_controller to package.xml depends
  • Removed pcl as a dependent because it isn't a package
  • Added even more build depends to package.xml
  • Added required build dependencies to package.xml
  • Update package.xml
  • commenting update
  • Acknowledgements Update
  • Update README.md
  • commenting update
  • commenting update
  • commenting update
  • commenting update
  • commenting updates
  • Delete basic_motors.launch~
  • commenting updates
  • CMakeLists update
  • commenting updates
  • commenting update
  • Update CMakeLists.txt
  • Delete hokuyo_ground_filter.cpp
  • Delete floor_max_z.cpp
  • commenting update
  • commenting update
  • commenting update
  • comment update
  • remove backup file
  • remove backup file
  • adding back CMakeLists
  • Temporarilly removed CMakelist.txt to satisfy failed merge
  • organization
  • Delete CMakeLists.txt
  • moved dynamixel controllers
  • moved scan_to_pcl
  • Removed rviz config files and fixed tilting lidar continuous launch file
  • file location update
  • tutorials update
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Renamed misc files and updated launch files and CMakeLists accordingly
  • Delete combine_clouds.cpp
  • Update CMakeLists.txt
  • Update CMakeLists.txt
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Removed extraneous launch files
  • name updates
  • Rename combine_clouds_subscriber.cpp to point_cloud_assembler.cpp
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Renamed hokuyo_filter to hokuyo_robot_filter to fit the naming convention of hokuyo_ground_filter
  • rename for clarity
  • typo
  • file renames
  • Delete combine_clouds.cpp
  • Removed floor removal parameter from octomap
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Removed Plane Extract Ransac from tilting lidar and made minor modifications to launch and cpp files
  • reset clouds
  • Modified combined clouds to allow for parameters and options between time and subscription, changed launch files to allow for further customizations
  • Added support for hokuyo_ground_filter
  • added tolerance
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • remove ground
  • Modified launch files for more universal use and added segmentation launch file and rviz config
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Modified to allow for parameter value to change from dynamixel tilting callback to timer callback
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo Conflicts: tilting_lidar_clean/launch/launch_with_octo/velodyne_hokuyo_octo_tilt_offline.launch
  • plane extraction
  • Disabled Voxel grid as it is uneccesary for non-assembled point clouds
  • Changed name argument to path, requiring full path to be input at launch but allows for universal use across systems
  • Removed rosbag node from online launch file

File truncated at 100 lines see the full file

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Launch files

  • launch/tilt_continuous.launch
    • This launch file causes the Hokuyo to sweep back and forth CONTINUOUSLY
      • assemble [default: velodyne_points]
  • launch/tilt_subscriber.launch
    • This launch file causes the Hokuyo to sweep back and forth ONLY WHEN AN EMPTY MESSAGE is sent to tilt_motor_subscribe node
      • assemble [default: velodyne_points]
  • tutorials/launch/basic_motors.launch
    • This file executes a simple launch of the Dynamixel servo that allows the operator to manually input values for the servo to rotate to. The Hokuyo IS NOT part of this launch.

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged spin_hokuyo at Robotics Stack Exchange

No version for distro bouncy showing indigo. Known supported distros are highlighted in the buttons above.
Package symbol

spin_hokuyo package from spin_hokuyo repo

spin_hokuyo

ROS Distro
indigo

Package Summary

Tags No category tags.
Version 1.0.0
License GPL
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/RobustFieldAutonomyLab/spin_hokuyo.git
VCS Type git
VCS Version master
Last Updated 2017-10-16
Dev Status MAINTAINED
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

This package enables a 2D Hokuyo laser, connected to a Dynamixel servo motor, to produce a 3D point cloud that can be visualized in rviz and used to make an octomap.

Additional Links

No additional links.

Maintainers

  • Sarah Bertussi
  • Paul Szenher

Authors

No additional authors.

spin_hokuyo

This repository contains code to control a Dynamixel motor and a 2D Hokuyo LiDAR to create a 3D point cloud that can be visualized in rviz. This point cloud can then be used to create an octomap (code for this is not included in this repository).
Wiki Page: http://wiki.ros.org/spin_hokuyo

Setup Directions

  1. Download this ROS Package:

sudo apt-get install ros-indigo-spin-hokuyo

  1. In the tutorials/launch folder, update the basic_motors.launch file, go to line 12. These parameters are used to set up the dynamixel_motor package. In particular, make sure the port_name and baud_rate match your servo. Also, check that your motor id falls within the inclusive range from min_motor_id to max_motor_id.
  2. In the tutorials/launch folder, update the basic_motors.launch file, go to line 12. These parameters are used to set up the dynamixel_motor package. In particular, make sure the port_name and baud_rate match your servo. Also, check that your motor id falls within the inclusive range from min_motor_id to max_motor_id.
  3. Save and compile changes (if applicable).

roslaunch spin_hokuyo basic_motors.launch

  1. In a new terminal, open the rostopics list. There should be two new commands: /tilt_controller/command and /tilt_controller/state. /command will issue new positions to the motor via Float64 (try this using rostopic pub). /state will list various pieces of information about the motor (rostopic echo).
  2. If this is fully functional, kill the node and do:

roslaunch spin_hokuyo tilting_continuous.launch
This should cause the motor to regularly sweep from 90 to -90 and generate a point cloud. Be sure to update the dynamixel_servos_tilting.yaml for position, speed, etc.

Possible Dynamixel Errors

Is the USB properly inserted and setup for your computer?
Is the Dynamixel connected to a 12V power source via the adapter?
Is the switch on the USB adapter at the proper loaction?

Acknowledgements

Inspired by the work seen here: </br> https://github.com/gcc-robotics/3d_photobooth/blob/master/CapstoneFinalReport_VisionTeam.pdf </br>

Dynamixel Control

The class system used to control the Dynamixel motors and the basis for the servo template were based on the examples provided in Chap. 8 of “Effective Robotics Programming with ROS - Third Edition” by Anil Mahtani, Luis Sanchez, Enrique Fernandea, and Aaron Martinez. ##

pcl_assembler_client

The pcl_assembler_client is a modified form of the periodic_snapshotter.cpp which is included in the /examples folder of laser_assembler which is hosted at: https://github.com/ros-perception/laser_assembler ##

Authors

Sarah Bertussi, Paul Szenher, Shi Bai. RFAL (Robust Field Autonomy Lab), Stevens Institute of Technology.

CHANGELOG

Changelog for package spin_hokuyo

1.0.0 (2017-07-21)

  • Removed dyanmixel files in favor of using dependencies as the apt version now apparently works
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Fixed packages in launch files, as well as renamed and organized
  • Update README.md
  • Fixed dynamixel requirement to be subpackages
  • Added dynamixel_controllers to package.xml depends
  • Added dynamixel_controller to package.xml depends
  • Removed pcl as a dependent because it isn't a package
  • Added even more build depends to package.xml
  • Added required build dependencies to package.xml
  • Update package.xml
  • commenting update
  • Acknowledgements Update
  • Update README.md
  • commenting update
  • commenting update
  • commenting update
  • commenting update
  • commenting updates
  • Delete basic_motors.launch~
  • commenting updates
  • CMakeLists update
  • commenting updates
  • commenting update
  • Update CMakeLists.txt
  • Delete hokuyo_ground_filter.cpp
  • Delete floor_max_z.cpp
  • commenting update
  • commenting update
  • commenting update
  • comment update
  • remove backup file
  • remove backup file
  • adding back CMakeLists
  • Temporarilly removed CMakelist.txt to satisfy failed merge
  • organization
  • Delete CMakeLists.txt
  • moved dynamixel controllers
  • moved scan_to_pcl
  • Removed rviz config files and fixed tilting lidar continuous launch file
  • file location update
  • tutorials update
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Renamed misc files and updated launch files and CMakeLists accordingly
  • Delete combine_clouds.cpp
  • Update CMakeLists.txt
  • Update CMakeLists.txt
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Removed extraneous launch files
  • name updates
  • Rename combine_clouds_subscriber.cpp to point_cloud_assembler.cpp
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Renamed hokuyo_filter to hokuyo_robot_filter to fit the naming convention of hokuyo_ground_filter
  • rename for clarity
  • typo
  • file renames
  • Delete combine_clouds.cpp
  • Removed floor removal parameter from octomap
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Removed Plane Extract Ransac from tilting lidar and made minor modifications to launch and cpp files
  • reset clouds
  • Modified combined clouds to allow for parameters and options between time and subscription, changed launch files to allow for further customizations
  • Added support for hokuyo_ground_filter
  • added tolerance
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • remove ground
  • Modified launch files for more universal use and added segmentation launch file and rviz config
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Modified to allow for parameter value to change from dynamixel tilting callback to timer callback
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo Conflicts: tilting_lidar_clean/launch/launch_with_octo/velodyne_hokuyo_octo_tilt_offline.launch
  • plane extraction
  • Disabled Voxel grid as it is uneccesary for non-assembled point clouds
  • Changed name argument to path, requiring full path to be input at launch but allows for universal use across systems
  • Removed rosbag node from online launch file

File truncated at 100 lines see the full file

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Launch files

  • launch/tilt_continuous.launch
    • This launch file causes the Hokuyo to sweep back and forth CONTINUOUSLY
      • assemble [default: velodyne_points]
  • launch/tilt_subscriber.launch
    • This launch file causes the Hokuyo to sweep back and forth ONLY WHEN AN EMPTY MESSAGE is sent to tilt_motor_subscribe node
      • assemble [default: velodyne_points]
  • tutorials/launch/basic_motors.launch
    • This file executes a simple launch of the Dynamixel servo that allows the operator to manually input values for the servo to rotate to. The Hokuyo IS NOT part of this launch.

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged spin_hokuyo at Robotics Stack Exchange

No version for distro crystal showing indigo. Known supported distros are highlighted in the buttons above.
Package symbol

spin_hokuyo package from spin_hokuyo repo

spin_hokuyo

ROS Distro
indigo

Package Summary

Tags No category tags.
Version 1.0.0
License GPL
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/RobustFieldAutonomyLab/spin_hokuyo.git
VCS Type git
VCS Version master
Last Updated 2017-10-16
Dev Status MAINTAINED
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

This package enables a 2D Hokuyo laser, connected to a Dynamixel servo motor, to produce a 3D point cloud that can be visualized in rviz and used to make an octomap.

Additional Links

No additional links.

Maintainers

  • Sarah Bertussi
  • Paul Szenher

Authors

No additional authors.

spin_hokuyo

This repository contains code to control a Dynamixel motor and a 2D Hokuyo LiDAR to create a 3D point cloud that can be visualized in rviz. This point cloud can then be used to create an octomap (code for this is not included in this repository).
Wiki Page: http://wiki.ros.org/spin_hokuyo

Setup Directions

  1. Download this ROS Package:

sudo apt-get install ros-indigo-spin-hokuyo

  1. In the tutorials/launch folder, update the basic_motors.launch file, go to line 12. These parameters are used to set up the dynamixel_motor package. In particular, make sure the port_name and baud_rate match your servo. Also, check that your motor id falls within the inclusive range from min_motor_id to max_motor_id.
  2. In the tutorials/launch folder, update the basic_motors.launch file, go to line 12. These parameters are used to set up the dynamixel_motor package. In particular, make sure the port_name and baud_rate match your servo. Also, check that your motor id falls within the inclusive range from min_motor_id to max_motor_id.
  3. Save and compile changes (if applicable).

roslaunch spin_hokuyo basic_motors.launch

  1. In a new terminal, open the rostopics list. There should be two new commands: /tilt_controller/command and /tilt_controller/state. /command will issue new positions to the motor via Float64 (try this using rostopic pub). /state will list various pieces of information about the motor (rostopic echo).
  2. If this is fully functional, kill the node and do:

roslaunch spin_hokuyo tilting_continuous.launch
This should cause the motor to regularly sweep from 90 to -90 and generate a point cloud. Be sure to update the dynamixel_servos_tilting.yaml for position, speed, etc.

Possible Dynamixel Errors

Is the USB properly inserted and setup for your computer?
Is the Dynamixel connected to a 12V power source via the adapter?
Is the switch on the USB adapter at the proper loaction?

Acknowledgements

Inspired by the work seen here: </br> https://github.com/gcc-robotics/3d_photobooth/blob/master/CapstoneFinalReport_VisionTeam.pdf </br>

Dynamixel Control

The class system used to control the Dynamixel motors and the basis for the servo template were based on the examples provided in Chap. 8 of “Effective Robotics Programming with ROS - Third Edition” by Anil Mahtani, Luis Sanchez, Enrique Fernandea, and Aaron Martinez. ##

pcl_assembler_client

The pcl_assembler_client is a modified form of the periodic_snapshotter.cpp which is included in the /examples folder of laser_assembler which is hosted at: https://github.com/ros-perception/laser_assembler ##

Authors

Sarah Bertussi, Paul Szenher, Shi Bai. RFAL (Robust Field Autonomy Lab), Stevens Institute of Technology.

CHANGELOG

Changelog for package spin_hokuyo

1.0.0 (2017-07-21)

  • Removed dyanmixel files in favor of using dependencies as the apt version now apparently works
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Fixed packages in launch files, as well as renamed and organized
  • Update README.md
  • Fixed dynamixel requirement to be subpackages
  • Added dynamixel_controllers to package.xml depends
  • Added dynamixel_controller to package.xml depends
  • Removed pcl as a dependent because it isn't a package
  • Added even more build depends to package.xml
  • Added required build dependencies to package.xml
  • Update package.xml
  • commenting update
  • Acknowledgements Update
  • Update README.md
  • commenting update
  • commenting update
  • commenting update
  • commenting update
  • commenting updates
  • Delete basic_motors.launch~
  • commenting updates
  • CMakeLists update
  • commenting updates
  • commenting update
  • Update CMakeLists.txt
  • Delete hokuyo_ground_filter.cpp
  • Delete floor_max_z.cpp
  • commenting update
  • commenting update
  • commenting update
  • comment update
  • remove backup file
  • remove backup file
  • adding back CMakeLists
  • Temporarilly removed CMakelist.txt to satisfy failed merge
  • organization
  • Delete CMakeLists.txt
  • moved dynamixel controllers
  • moved scan_to_pcl
  • Removed rviz config files and fixed tilting lidar continuous launch file
  • file location update
  • tutorials update
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Renamed misc files and updated launch files and CMakeLists accordingly
  • Delete combine_clouds.cpp
  • Update CMakeLists.txt
  • Update CMakeLists.txt
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Removed extraneous launch files
  • name updates
  • Rename combine_clouds_subscriber.cpp to point_cloud_assembler.cpp
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Renamed hokuyo_filter to hokuyo_robot_filter to fit the naming convention of hokuyo_ground_filter
  • rename for clarity
  • typo
  • file renames
  • Delete combine_clouds.cpp
  • Removed floor removal parameter from octomap
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Removed Plane Extract Ransac from tilting lidar and made minor modifications to launch and cpp files
  • reset clouds
  • Modified combined clouds to allow for parameters and options between time and subscription, changed launch files to allow for further customizations
  • Added support for hokuyo_ground_filter
  • added tolerance
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • remove ground
  • Modified launch files for more universal use and added segmentation launch file and rviz config
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Modified to allow for parameter value to change from dynamixel tilting callback to timer callback
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo Conflicts: tilting_lidar_clean/launch/launch_with_octo/velodyne_hokuyo_octo_tilt_offline.launch
  • plane extraction
  • Disabled Voxel grid as it is uneccesary for non-assembled point clouds
  • Changed name argument to path, requiring full path to be input at launch but allows for universal use across systems
  • Removed rosbag node from online launch file

File truncated at 100 lines see the full file

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Launch files

  • launch/tilt_continuous.launch
    • This launch file causes the Hokuyo to sweep back and forth CONTINUOUSLY
      • assemble [default: velodyne_points]
  • launch/tilt_subscriber.launch
    • This launch file causes the Hokuyo to sweep back and forth ONLY WHEN AN EMPTY MESSAGE is sent to tilt_motor_subscribe node
      • assemble [default: velodyne_points]
  • tutorials/launch/basic_motors.launch
    • This file executes a simple launch of the Dynamixel servo that allows the operator to manually input values for the servo to rotate to. The Hokuyo IS NOT part of this launch.

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged spin_hokuyo at Robotics Stack Exchange

No version for distro eloquent showing indigo. Known supported distros are highlighted in the buttons above.
Package symbol

spin_hokuyo package from spin_hokuyo repo

spin_hokuyo

ROS Distro
indigo

Package Summary

Tags No category tags.
Version 1.0.0
License GPL
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/RobustFieldAutonomyLab/spin_hokuyo.git
VCS Type git
VCS Version master
Last Updated 2017-10-16
Dev Status MAINTAINED
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

This package enables a 2D Hokuyo laser, connected to a Dynamixel servo motor, to produce a 3D point cloud that can be visualized in rviz and used to make an octomap.

Additional Links

No additional links.

Maintainers

  • Sarah Bertussi
  • Paul Szenher

Authors

No additional authors.

spin_hokuyo

This repository contains code to control a Dynamixel motor and a 2D Hokuyo LiDAR to create a 3D point cloud that can be visualized in rviz. This point cloud can then be used to create an octomap (code for this is not included in this repository).
Wiki Page: http://wiki.ros.org/spin_hokuyo

Setup Directions

  1. Download this ROS Package:

sudo apt-get install ros-indigo-spin-hokuyo

  1. In the tutorials/launch folder, update the basic_motors.launch file, go to line 12. These parameters are used to set up the dynamixel_motor package. In particular, make sure the port_name and baud_rate match your servo. Also, check that your motor id falls within the inclusive range from min_motor_id to max_motor_id.
  2. In the tutorials/launch folder, update the basic_motors.launch file, go to line 12. These parameters are used to set up the dynamixel_motor package. In particular, make sure the port_name and baud_rate match your servo. Also, check that your motor id falls within the inclusive range from min_motor_id to max_motor_id.
  3. Save and compile changes (if applicable).

roslaunch spin_hokuyo basic_motors.launch

  1. In a new terminal, open the rostopics list. There should be two new commands: /tilt_controller/command and /tilt_controller/state. /command will issue new positions to the motor via Float64 (try this using rostopic pub). /state will list various pieces of information about the motor (rostopic echo).
  2. If this is fully functional, kill the node and do:

roslaunch spin_hokuyo tilting_continuous.launch
This should cause the motor to regularly sweep from 90 to -90 and generate a point cloud. Be sure to update the dynamixel_servos_tilting.yaml for position, speed, etc.

Possible Dynamixel Errors

Is the USB properly inserted and setup for your computer?
Is the Dynamixel connected to a 12V power source via the adapter?
Is the switch on the USB adapter at the proper loaction?

Acknowledgements

Inspired by the work seen here: </br> https://github.com/gcc-robotics/3d_photobooth/blob/master/CapstoneFinalReport_VisionTeam.pdf </br>

Dynamixel Control

The class system used to control the Dynamixel motors and the basis for the servo template were based on the examples provided in Chap. 8 of “Effective Robotics Programming with ROS - Third Edition” by Anil Mahtani, Luis Sanchez, Enrique Fernandea, and Aaron Martinez. ##

pcl_assembler_client

The pcl_assembler_client is a modified form of the periodic_snapshotter.cpp which is included in the /examples folder of laser_assembler which is hosted at: https://github.com/ros-perception/laser_assembler ##

Authors

Sarah Bertussi, Paul Szenher, Shi Bai. RFAL (Robust Field Autonomy Lab), Stevens Institute of Technology.

CHANGELOG

Changelog for package spin_hokuyo

1.0.0 (2017-07-21)

  • Removed dyanmixel files in favor of using dependencies as the apt version now apparently works
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Fixed packages in launch files, as well as renamed and organized
  • Update README.md
  • Fixed dynamixel requirement to be subpackages
  • Added dynamixel_controllers to package.xml depends
  • Added dynamixel_controller to package.xml depends
  • Removed pcl as a dependent because it isn't a package
  • Added even more build depends to package.xml
  • Added required build dependencies to package.xml
  • Update package.xml
  • commenting update
  • Acknowledgements Update
  • Update README.md
  • commenting update
  • commenting update
  • commenting update
  • commenting update
  • commenting updates
  • Delete basic_motors.launch~
  • commenting updates
  • CMakeLists update
  • commenting updates
  • commenting update
  • Update CMakeLists.txt
  • Delete hokuyo_ground_filter.cpp
  • Delete floor_max_z.cpp
  • commenting update
  • commenting update
  • commenting update
  • comment update
  • remove backup file
  • remove backup file
  • adding back CMakeLists
  • Temporarilly removed CMakelist.txt to satisfy failed merge
  • organization
  • Delete CMakeLists.txt
  • moved dynamixel controllers
  • moved scan_to_pcl
  • Removed rviz config files and fixed tilting lidar continuous launch file
  • file location update
  • tutorials update
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Renamed misc files and updated launch files and CMakeLists accordingly
  • Delete combine_clouds.cpp
  • Update CMakeLists.txt
  • Update CMakeLists.txt
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Removed extraneous launch files
  • name updates
  • Rename combine_clouds_subscriber.cpp to point_cloud_assembler.cpp
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Renamed hokuyo_filter to hokuyo_robot_filter to fit the naming convention of hokuyo_ground_filter
  • rename for clarity
  • typo
  • file renames
  • Delete combine_clouds.cpp
  • Removed floor removal parameter from octomap
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Removed Plane Extract Ransac from tilting lidar and made minor modifications to launch and cpp files
  • reset clouds
  • Modified combined clouds to allow for parameters and options between time and subscription, changed launch files to allow for further customizations
  • Added support for hokuyo_ground_filter
  • added tolerance
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • remove ground
  • Modified launch files for more universal use and added segmentation launch file and rviz config
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Modified to allow for parameter value to change from dynamixel tilting callback to timer callback
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo Conflicts: tilting_lidar_clean/launch/launch_with_octo/velodyne_hokuyo_octo_tilt_offline.launch
  • plane extraction
  • Disabled Voxel grid as it is uneccesary for non-assembled point clouds
  • Changed name argument to path, requiring full path to be input at launch but allows for universal use across systems
  • Removed rosbag node from online launch file

File truncated at 100 lines see the full file

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Launch files

  • launch/tilt_continuous.launch
    • This launch file causes the Hokuyo to sweep back and forth CONTINUOUSLY
      • assemble [default: velodyne_points]
  • launch/tilt_subscriber.launch
    • This launch file causes the Hokuyo to sweep back and forth ONLY WHEN AN EMPTY MESSAGE is sent to tilt_motor_subscribe node
      • assemble [default: velodyne_points]
  • tutorials/launch/basic_motors.launch
    • This file executes a simple launch of the Dynamixel servo that allows the operator to manually input values for the servo to rotate to. The Hokuyo IS NOT part of this launch.

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged spin_hokuyo at Robotics Stack Exchange

No version for distro dashing showing indigo. Known supported distros are highlighted in the buttons above.
Package symbol

spin_hokuyo package from spin_hokuyo repo

spin_hokuyo

ROS Distro
indigo

Package Summary

Tags No category tags.
Version 1.0.0
License GPL
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/RobustFieldAutonomyLab/spin_hokuyo.git
VCS Type git
VCS Version master
Last Updated 2017-10-16
Dev Status MAINTAINED
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

This package enables a 2D Hokuyo laser, connected to a Dynamixel servo motor, to produce a 3D point cloud that can be visualized in rviz and used to make an octomap.

Additional Links

No additional links.

Maintainers

  • Sarah Bertussi
  • Paul Szenher

Authors

No additional authors.

spin_hokuyo

This repository contains code to control a Dynamixel motor and a 2D Hokuyo LiDAR to create a 3D point cloud that can be visualized in rviz. This point cloud can then be used to create an octomap (code for this is not included in this repository).
Wiki Page: http://wiki.ros.org/spin_hokuyo

Setup Directions

  1. Download this ROS Package:

sudo apt-get install ros-indigo-spin-hokuyo

  1. In the tutorials/launch folder, update the basic_motors.launch file, go to line 12. These parameters are used to set up the dynamixel_motor package. In particular, make sure the port_name and baud_rate match your servo. Also, check that your motor id falls within the inclusive range from min_motor_id to max_motor_id.
  2. In the tutorials/launch folder, update the basic_motors.launch file, go to line 12. These parameters are used to set up the dynamixel_motor package. In particular, make sure the port_name and baud_rate match your servo. Also, check that your motor id falls within the inclusive range from min_motor_id to max_motor_id.
  3. Save and compile changes (if applicable).

roslaunch spin_hokuyo basic_motors.launch

  1. In a new terminal, open the rostopics list. There should be two new commands: /tilt_controller/command and /tilt_controller/state. /command will issue new positions to the motor via Float64 (try this using rostopic pub). /state will list various pieces of information about the motor (rostopic echo).
  2. If this is fully functional, kill the node and do:

roslaunch spin_hokuyo tilting_continuous.launch
This should cause the motor to regularly sweep from 90 to -90 and generate a point cloud. Be sure to update the dynamixel_servos_tilting.yaml for position, speed, etc.

Possible Dynamixel Errors

Is the USB properly inserted and setup for your computer?
Is the Dynamixel connected to a 12V power source via the adapter?
Is the switch on the USB adapter at the proper loaction?

Acknowledgements

Inspired by the work seen here: </br> https://github.com/gcc-robotics/3d_photobooth/blob/master/CapstoneFinalReport_VisionTeam.pdf </br>

Dynamixel Control

The class system used to control the Dynamixel motors and the basis for the servo template were based on the examples provided in Chap. 8 of “Effective Robotics Programming with ROS - Third Edition” by Anil Mahtani, Luis Sanchez, Enrique Fernandea, and Aaron Martinez. ##

pcl_assembler_client

The pcl_assembler_client is a modified form of the periodic_snapshotter.cpp which is included in the /examples folder of laser_assembler which is hosted at: https://github.com/ros-perception/laser_assembler ##

Authors

Sarah Bertussi, Paul Szenher, Shi Bai. RFAL (Robust Field Autonomy Lab), Stevens Institute of Technology.

CHANGELOG

Changelog for package spin_hokuyo

1.0.0 (2017-07-21)

  • Removed dyanmixel files in favor of using dependencies as the apt version now apparently works
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Fixed packages in launch files, as well as renamed and organized
  • Update README.md
  • Fixed dynamixel requirement to be subpackages
  • Added dynamixel_controllers to package.xml depends
  • Added dynamixel_controller to package.xml depends
  • Removed pcl as a dependent because it isn't a package
  • Added even more build depends to package.xml
  • Added required build dependencies to package.xml
  • Update package.xml
  • commenting update
  • Acknowledgements Update
  • Update README.md
  • commenting update
  • commenting update
  • commenting update
  • commenting update
  • commenting updates
  • Delete basic_motors.launch~
  • commenting updates
  • CMakeLists update
  • commenting updates
  • commenting update
  • Update CMakeLists.txt
  • Delete hokuyo_ground_filter.cpp
  • Delete floor_max_z.cpp
  • commenting update
  • commenting update
  • commenting update
  • comment update
  • remove backup file
  • remove backup file
  • adding back CMakeLists
  • Temporarilly removed CMakelist.txt to satisfy failed merge
  • organization
  • Delete CMakeLists.txt
  • moved dynamixel controllers
  • moved scan_to_pcl
  • Removed rviz config files and fixed tilting lidar continuous launch file
  • file location update
  • tutorials update
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Renamed misc files and updated launch files and CMakeLists accordingly
  • Delete combine_clouds.cpp
  • Update CMakeLists.txt
  • Update CMakeLists.txt
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Removed extraneous launch files
  • name updates
  • Rename combine_clouds_subscriber.cpp to point_cloud_assembler.cpp
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Renamed hokuyo_filter to hokuyo_robot_filter to fit the naming convention of hokuyo_ground_filter
  • rename for clarity
  • typo
  • file renames
  • Delete combine_clouds.cpp
  • Removed floor removal parameter from octomap
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Removed Plane Extract Ransac from tilting lidar and made minor modifications to launch and cpp files
  • reset clouds
  • Modified combined clouds to allow for parameters and options between time and subscription, changed launch files to allow for further customizations
  • Added support for hokuyo_ground_filter
  • added tolerance
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • remove ground
  • Modified launch files for more universal use and added segmentation launch file and rviz config
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Modified to allow for parameter value to change from dynamixel tilting callback to timer callback
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo Conflicts: tilting_lidar_clean/launch/launch_with_octo/velodyne_hokuyo_octo_tilt_offline.launch
  • plane extraction
  • Disabled Voxel grid as it is uneccesary for non-assembled point clouds
  • Changed name argument to path, requiring full path to be input at launch but allows for universal use across systems
  • Removed rosbag node from online launch file

File truncated at 100 lines see the full file

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Launch files

  • launch/tilt_continuous.launch
    • This launch file causes the Hokuyo to sweep back and forth CONTINUOUSLY
      • assemble [default: velodyne_points]
  • launch/tilt_subscriber.launch
    • This launch file causes the Hokuyo to sweep back and forth ONLY WHEN AN EMPTY MESSAGE is sent to tilt_motor_subscribe node
      • assemble [default: velodyne_points]
  • tutorials/launch/basic_motors.launch
    • This file executes a simple launch of the Dynamixel servo that allows the operator to manually input values for the servo to rotate to. The Hokuyo IS NOT part of this launch.

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged spin_hokuyo at Robotics Stack Exchange

No version for distro galactic showing indigo. Known supported distros are highlighted in the buttons above.
Package symbol

spin_hokuyo package from spin_hokuyo repo

spin_hokuyo

ROS Distro
indigo

Package Summary

Tags No category tags.
Version 1.0.0
License GPL
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/RobustFieldAutonomyLab/spin_hokuyo.git
VCS Type git
VCS Version master
Last Updated 2017-10-16
Dev Status MAINTAINED
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

This package enables a 2D Hokuyo laser, connected to a Dynamixel servo motor, to produce a 3D point cloud that can be visualized in rviz and used to make an octomap.

Additional Links

No additional links.

Maintainers

  • Sarah Bertussi
  • Paul Szenher

Authors

No additional authors.

spin_hokuyo

This repository contains code to control a Dynamixel motor and a 2D Hokuyo LiDAR to create a 3D point cloud that can be visualized in rviz. This point cloud can then be used to create an octomap (code for this is not included in this repository).
Wiki Page: http://wiki.ros.org/spin_hokuyo

Setup Directions

  1. Download this ROS Package:

sudo apt-get install ros-indigo-spin-hokuyo

  1. In the tutorials/launch folder, update the basic_motors.launch file, go to line 12. These parameters are used to set up the dynamixel_motor package. In particular, make sure the port_name and baud_rate match your servo. Also, check that your motor id falls within the inclusive range from min_motor_id to max_motor_id.
  2. In the tutorials/launch folder, update the basic_motors.launch file, go to line 12. These parameters are used to set up the dynamixel_motor package. In particular, make sure the port_name and baud_rate match your servo. Also, check that your motor id falls within the inclusive range from min_motor_id to max_motor_id.
  3. Save and compile changes (if applicable).

roslaunch spin_hokuyo basic_motors.launch

  1. In a new terminal, open the rostopics list. There should be two new commands: /tilt_controller/command and /tilt_controller/state. /command will issue new positions to the motor via Float64 (try this using rostopic pub). /state will list various pieces of information about the motor (rostopic echo).
  2. If this is fully functional, kill the node and do:

roslaunch spin_hokuyo tilting_continuous.launch
This should cause the motor to regularly sweep from 90 to -90 and generate a point cloud. Be sure to update the dynamixel_servos_tilting.yaml for position, speed, etc.

Possible Dynamixel Errors

Is the USB properly inserted and setup for your computer?
Is the Dynamixel connected to a 12V power source via the adapter?
Is the switch on the USB adapter at the proper loaction?

Acknowledgements

Inspired by the work seen here: </br> https://github.com/gcc-robotics/3d_photobooth/blob/master/CapstoneFinalReport_VisionTeam.pdf </br>

Dynamixel Control

The class system used to control the Dynamixel motors and the basis for the servo template were based on the examples provided in Chap. 8 of “Effective Robotics Programming with ROS - Third Edition” by Anil Mahtani, Luis Sanchez, Enrique Fernandea, and Aaron Martinez. ##

pcl_assembler_client

The pcl_assembler_client is a modified form of the periodic_snapshotter.cpp which is included in the /examples folder of laser_assembler which is hosted at: https://github.com/ros-perception/laser_assembler ##

Authors

Sarah Bertussi, Paul Szenher, Shi Bai. RFAL (Robust Field Autonomy Lab), Stevens Institute of Technology.

CHANGELOG

Changelog for package spin_hokuyo

1.0.0 (2017-07-21)

  • Removed dyanmixel files in favor of using dependencies as the apt version now apparently works
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Fixed packages in launch files, as well as renamed and organized
  • Update README.md
  • Fixed dynamixel requirement to be subpackages
  • Added dynamixel_controllers to package.xml depends
  • Added dynamixel_controller to package.xml depends
  • Removed pcl as a dependent because it isn't a package
  • Added even more build depends to package.xml
  • Added required build dependencies to package.xml
  • Update package.xml
  • commenting update
  • Acknowledgements Update
  • Update README.md
  • commenting update
  • commenting update
  • commenting update
  • commenting update
  • commenting updates
  • Delete basic_motors.launch~
  • commenting updates
  • CMakeLists update
  • commenting updates
  • commenting update
  • Update CMakeLists.txt
  • Delete hokuyo_ground_filter.cpp
  • Delete floor_max_z.cpp
  • commenting update
  • commenting update
  • commenting update
  • comment update
  • remove backup file
  • remove backup file
  • adding back CMakeLists
  • Temporarilly removed CMakelist.txt to satisfy failed merge
  • organization
  • Delete CMakeLists.txt
  • moved dynamixel controllers
  • moved scan_to_pcl
  • Removed rviz config files and fixed tilting lidar continuous launch file
  • file location update
  • tutorials update
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Renamed misc files and updated launch files and CMakeLists accordingly
  • Delete combine_clouds.cpp
  • Update CMakeLists.txt
  • Update CMakeLists.txt
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Removed extraneous launch files
  • name updates
  • Rename combine_clouds_subscriber.cpp to point_cloud_assembler.cpp
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Renamed hokuyo_filter to hokuyo_robot_filter to fit the naming convention of hokuyo_ground_filter
  • rename for clarity
  • typo
  • file renames
  • Delete combine_clouds.cpp
  • Removed floor removal parameter from octomap
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Removed Plane Extract Ransac from tilting lidar and made minor modifications to launch and cpp files
  • reset clouds
  • Modified combined clouds to allow for parameters and options between time and subscription, changed launch files to allow for further customizations
  • Added support for hokuyo_ground_filter
  • added tolerance
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • remove ground
  • Modified launch files for more universal use and added segmentation launch file and rviz config
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Modified to allow for parameter value to change from dynamixel tilting callback to timer callback
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo Conflicts: tilting_lidar_clean/launch/launch_with_octo/velodyne_hokuyo_octo_tilt_offline.launch
  • plane extraction
  • Disabled Voxel grid as it is uneccesary for non-assembled point clouds
  • Changed name argument to path, requiring full path to be input at launch but allows for universal use across systems
  • Removed rosbag node from online launch file

File truncated at 100 lines see the full file

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Launch files

  • launch/tilt_continuous.launch
    • This launch file causes the Hokuyo to sweep back and forth CONTINUOUSLY
      • assemble [default: velodyne_points]
  • launch/tilt_subscriber.launch
    • This launch file causes the Hokuyo to sweep back and forth ONLY WHEN AN EMPTY MESSAGE is sent to tilt_motor_subscribe node
      • assemble [default: velodyne_points]
  • tutorials/launch/basic_motors.launch
    • This file executes a simple launch of the Dynamixel servo that allows the operator to manually input values for the servo to rotate to. The Hokuyo IS NOT part of this launch.

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged spin_hokuyo at Robotics Stack Exchange

No version for distro foxy showing indigo. Known supported distros are highlighted in the buttons above.
Package symbol

spin_hokuyo package from spin_hokuyo repo

spin_hokuyo

ROS Distro
indigo

Package Summary

Tags No category tags.
Version 1.0.0
License GPL
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/RobustFieldAutonomyLab/spin_hokuyo.git
VCS Type git
VCS Version master
Last Updated 2017-10-16
Dev Status MAINTAINED
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

This package enables a 2D Hokuyo laser, connected to a Dynamixel servo motor, to produce a 3D point cloud that can be visualized in rviz and used to make an octomap.

Additional Links

No additional links.

Maintainers

  • Sarah Bertussi
  • Paul Szenher

Authors

No additional authors.

spin_hokuyo

This repository contains code to control a Dynamixel motor and a 2D Hokuyo LiDAR to create a 3D point cloud that can be visualized in rviz. This point cloud can then be used to create an octomap (code for this is not included in this repository).
Wiki Page: http://wiki.ros.org/spin_hokuyo

Setup Directions

  1. Download this ROS Package:

sudo apt-get install ros-indigo-spin-hokuyo

  1. In the tutorials/launch folder, update the basic_motors.launch file, go to line 12. These parameters are used to set up the dynamixel_motor package. In particular, make sure the port_name and baud_rate match your servo. Also, check that your motor id falls within the inclusive range from min_motor_id to max_motor_id.
  2. In the tutorials/launch folder, update the basic_motors.launch file, go to line 12. These parameters are used to set up the dynamixel_motor package. In particular, make sure the port_name and baud_rate match your servo. Also, check that your motor id falls within the inclusive range from min_motor_id to max_motor_id.
  3. Save and compile changes (if applicable).

roslaunch spin_hokuyo basic_motors.launch

  1. In a new terminal, open the rostopics list. There should be two new commands: /tilt_controller/command and /tilt_controller/state. /command will issue new positions to the motor via Float64 (try this using rostopic pub). /state will list various pieces of information about the motor (rostopic echo).
  2. If this is fully functional, kill the node and do:

roslaunch spin_hokuyo tilting_continuous.launch
This should cause the motor to regularly sweep from 90 to -90 and generate a point cloud. Be sure to update the dynamixel_servos_tilting.yaml for position, speed, etc.

Possible Dynamixel Errors

Is the USB properly inserted and setup for your computer?
Is the Dynamixel connected to a 12V power source via the adapter?
Is the switch on the USB adapter at the proper loaction?

Acknowledgements

Inspired by the work seen here: </br> https://github.com/gcc-robotics/3d_photobooth/blob/master/CapstoneFinalReport_VisionTeam.pdf </br>

Dynamixel Control

The class system used to control the Dynamixel motors and the basis for the servo template were based on the examples provided in Chap. 8 of “Effective Robotics Programming with ROS - Third Edition” by Anil Mahtani, Luis Sanchez, Enrique Fernandea, and Aaron Martinez. ##

pcl_assembler_client

The pcl_assembler_client is a modified form of the periodic_snapshotter.cpp which is included in the /examples folder of laser_assembler which is hosted at: https://github.com/ros-perception/laser_assembler ##

Authors

Sarah Bertussi, Paul Szenher, Shi Bai. RFAL (Robust Field Autonomy Lab), Stevens Institute of Technology.

CHANGELOG

Changelog for package spin_hokuyo

1.0.0 (2017-07-21)

  • Removed dyanmixel files in favor of using dependencies as the apt version now apparently works
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Fixed packages in launch files, as well as renamed and organized
  • Update README.md
  • Fixed dynamixel requirement to be subpackages
  • Added dynamixel_controllers to package.xml depends
  • Added dynamixel_controller to package.xml depends
  • Removed pcl as a dependent because it isn't a package
  • Added even more build depends to package.xml
  • Added required build dependencies to package.xml
  • Update package.xml
  • commenting update
  • Acknowledgements Update
  • Update README.md
  • commenting update
  • commenting update
  • commenting update
  • commenting update
  • commenting updates
  • Delete basic_motors.launch~
  • commenting updates
  • CMakeLists update
  • commenting updates
  • commenting update
  • Update CMakeLists.txt
  • Delete hokuyo_ground_filter.cpp
  • Delete floor_max_z.cpp
  • commenting update
  • commenting update
  • commenting update
  • comment update
  • remove backup file
  • remove backup file
  • adding back CMakeLists
  • Temporarilly removed CMakelist.txt to satisfy failed merge
  • organization
  • Delete CMakeLists.txt
  • moved dynamixel controllers
  • moved scan_to_pcl
  • Removed rviz config files and fixed tilting lidar continuous launch file
  • file location update
  • tutorials update
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Renamed misc files and updated launch files and CMakeLists accordingly
  • Delete combine_clouds.cpp
  • Update CMakeLists.txt
  • Update CMakeLists.txt
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Removed extraneous launch files
  • name updates
  • Rename combine_clouds_subscriber.cpp to point_cloud_assembler.cpp
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Renamed hokuyo_filter to hokuyo_robot_filter to fit the naming convention of hokuyo_ground_filter
  • rename for clarity
  • typo
  • file renames
  • Delete combine_clouds.cpp
  • Removed floor removal parameter from octomap
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Removed Plane Extract Ransac from tilting lidar and made minor modifications to launch and cpp files
  • reset clouds
  • Modified combined clouds to allow for parameters and options between time and subscription, changed launch files to allow for further customizations
  • Added support for hokuyo_ground_filter
  • added tolerance
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • remove ground
  • Modified launch files for more universal use and added segmentation launch file and rviz config
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Modified to allow for parameter value to change from dynamixel tilting callback to timer callback
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo Conflicts: tilting_lidar_clean/launch/launch_with_octo/velodyne_hokuyo_octo_tilt_offline.launch
  • plane extraction
  • Disabled Voxel grid as it is uneccesary for non-assembled point clouds
  • Changed name argument to path, requiring full path to be input at launch but allows for universal use across systems
  • Removed rosbag node from online launch file

File truncated at 100 lines see the full file

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Launch files

  • launch/tilt_continuous.launch
    • This launch file causes the Hokuyo to sweep back and forth CONTINUOUSLY
      • assemble [default: velodyne_points]
  • launch/tilt_subscriber.launch
    • This launch file causes the Hokuyo to sweep back and forth ONLY WHEN AN EMPTY MESSAGE is sent to tilt_motor_subscribe node
      • assemble [default: velodyne_points]
  • tutorials/launch/basic_motors.launch
    • This file executes a simple launch of the Dynamixel servo that allows the operator to manually input values for the servo to rotate to. The Hokuyo IS NOT part of this launch.

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged spin_hokuyo at Robotics Stack Exchange

No version for distro iron showing indigo. Known supported distros are highlighted in the buttons above.
Package symbol

spin_hokuyo package from spin_hokuyo repo

spin_hokuyo

ROS Distro
indigo

Package Summary

Tags No category tags.
Version 1.0.0
License GPL
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/RobustFieldAutonomyLab/spin_hokuyo.git
VCS Type git
VCS Version master
Last Updated 2017-10-16
Dev Status MAINTAINED
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

This package enables a 2D Hokuyo laser, connected to a Dynamixel servo motor, to produce a 3D point cloud that can be visualized in rviz and used to make an octomap.

Additional Links

No additional links.

Maintainers

  • Sarah Bertussi
  • Paul Szenher

Authors

No additional authors.

spin_hokuyo

This repository contains code to control a Dynamixel motor and a 2D Hokuyo LiDAR to create a 3D point cloud that can be visualized in rviz. This point cloud can then be used to create an octomap (code for this is not included in this repository).
Wiki Page: http://wiki.ros.org/spin_hokuyo

Setup Directions

  1. Download this ROS Package:

sudo apt-get install ros-indigo-spin-hokuyo

  1. In the tutorials/launch folder, update the basic_motors.launch file, go to line 12. These parameters are used to set up the dynamixel_motor package. In particular, make sure the port_name and baud_rate match your servo. Also, check that your motor id falls within the inclusive range from min_motor_id to max_motor_id.
  2. In the tutorials/launch folder, update the basic_motors.launch file, go to line 12. These parameters are used to set up the dynamixel_motor package. In particular, make sure the port_name and baud_rate match your servo. Also, check that your motor id falls within the inclusive range from min_motor_id to max_motor_id.
  3. Save and compile changes (if applicable).

roslaunch spin_hokuyo basic_motors.launch

  1. In a new terminal, open the rostopics list. There should be two new commands: /tilt_controller/command and /tilt_controller/state. /command will issue new positions to the motor via Float64 (try this using rostopic pub). /state will list various pieces of information about the motor (rostopic echo).
  2. If this is fully functional, kill the node and do:

roslaunch spin_hokuyo tilting_continuous.launch
This should cause the motor to regularly sweep from 90 to -90 and generate a point cloud. Be sure to update the dynamixel_servos_tilting.yaml for position, speed, etc.

Possible Dynamixel Errors

Is the USB properly inserted and setup for your computer?
Is the Dynamixel connected to a 12V power source via the adapter?
Is the switch on the USB adapter at the proper loaction?

Acknowledgements

Inspired by the work seen here: </br> https://github.com/gcc-robotics/3d_photobooth/blob/master/CapstoneFinalReport_VisionTeam.pdf </br>

Dynamixel Control

The class system used to control the Dynamixel motors and the basis for the servo template were based on the examples provided in Chap. 8 of “Effective Robotics Programming with ROS - Third Edition” by Anil Mahtani, Luis Sanchez, Enrique Fernandea, and Aaron Martinez. ##

pcl_assembler_client

The pcl_assembler_client is a modified form of the periodic_snapshotter.cpp which is included in the /examples folder of laser_assembler which is hosted at: https://github.com/ros-perception/laser_assembler ##

Authors

Sarah Bertussi, Paul Szenher, Shi Bai. RFAL (Robust Field Autonomy Lab), Stevens Institute of Technology.

CHANGELOG

Changelog for package spin_hokuyo

1.0.0 (2017-07-21)

  • Removed dyanmixel files in favor of using dependencies as the apt version now apparently works
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Fixed packages in launch files, as well as renamed and organized
  • Update README.md
  • Fixed dynamixel requirement to be subpackages
  • Added dynamixel_controllers to package.xml depends
  • Added dynamixel_controller to package.xml depends
  • Removed pcl as a dependent because it isn't a package
  • Added even more build depends to package.xml
  • Added required build dependencies to package.xml
  • Update package.xml
  • commenting update
  • Acknowledgements Update
  • Update README.md
  • commenting update
  • commenting update
  • commenting update
  • commenting update
  • commenting updates
  • Delete basic_motors.launch~
  • commenting updates
  • CMakeLists update
  • commenting updates
  • commenting update
  • Update CMakeLists.txt
  • Delete hokuyo_ground_filter.cpp
  • Delete floor_max_z.cpp
  • commenting update
  • commenting update
  • commenting update
  • comment update
  • remove backup file
  • remove backup file
  • adding back CMakeLists
  • Temporarilly removed CMakelist.txt to satisfy failed merge
  • organization
  • Delete CMakeLists.txt
  • moved dynamixel controllers
  • moved scan_to_pcl
  • Removed rviz config files and fixed tilting lidar continuous launch file
  • file location update
  • tutorials update
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Renamed misc files and updated launch files and CMakeLists accordingly
  • Delete combine_clouds.cpp
  • Update CMakeLists.txt
  • Update CMakeLists.txt
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Removed extraneous launch files
  • name updates
  • Rename combine_clouds_subscriber.cpp to point_cloud_assembler.cpp
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Renamed hokuyo_filter to hokuyo_robot_filter to fit the naming convention of hokuyo_ground_filter
  • rename for clarity
  • typo
  • file renames
  • Delete combine_clouds.cpp
  • Removed floor removal parameter from octomap
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Removed Plane Extract Ransac from tilting lidar and made minor modifications to launch and cpp files
  • reset clouds
  • Modified combined clouds to allow for parameters and options between time and subscription, changed launch files to allow for further customizations
  • Added support for hokuyo_ground_filter
  • added tolerance
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • remove ground
  • Modified launch files for more universal use and added segmentation launch file and rviz config
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Modified to allow for parameter value to change from dynamixel tilting callback to timer callback
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo Conflicts: tilting_lidar_clean/launch/launch_with_octo/velodyne_hokuyo_octo_tilt_offline.launch
  • plane extraction
  • Disabled Voxel grid as it is uneccesary for non-assembled point clouds
  • Changed name argument to path, requiring full path to be input at launch but allows for universal use across systems
  • Removed rosbag node from online launch file

File truncated at 100 lines see the full file

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Launch files

  • launch/tilt_continuous.launch
    • This launch file causes the Hokuyo to sweep back and forth CONTINUOUSLY
      • assemble [default: velodyne_points]
  • launch/tilt_subscriber.launch
    • This launch file causes the Hokuyo to sweep back and forth ONLY WHEN AN EMPTY MESSAGE is sent to tilt_motor_subscribe node
      • assemble [default: velodyne_points]
  • tutorials/launch/basic_motors.launch
    • This file executes a simple launch of the Dynamixel servo that allows the operator to manually input values for the servo to rotate to. The Hokuyo IS NOT part of this launch.

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged spin_hokuyo at Robotics Stack Exchange

No version for distro lunar showing indigo. Known supported distros are highlighted in the buttons above.
Package symbol

spin_hokuyo package from spin_hokuyo repo

spin_hokuyo

ROS Distro
indigo

Package Summary

Tags No category tags.
Version 1.0.0
License GPL
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/RobustFieldAutonomyLab/spin_hokuyo.git
VCS Type git
VCS Version master
Last Updated 2017-10-16
Dev Status MAINTAINED
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

This package enables a 2D Hokuyo laser, connected to a Dynamixel servo motor, to produce a 3D point cloud that can be visualized in rviz and used to make an octomap.

Additional Links

No additional links.

Maintainers

  • Sarah Bertussi
  • Paul Szenher

Authors

No additional authors.

spin_hokuyo

This repository contains code to control a Dynamixel motor and a 2D Hokuyo LiDAR to create a 3D point cloud that can be visualized in rviz. This point cloud can then be used to create an octomap (code for this is not included in this repository).
Wiki Page: http://wiki.ros.org/spin_hokuyo

Setup Directions

  1. Download this ROS Package:

sudo apt-get install ros-indigo-spin-hokuyo

  1. In the tutorials/launch folder, update the basic_motors.launch file, go to line 12. These parameters are used to set up the dynamixel_motor package. In particular, make sure the port_name and baud_rate match your servo. Also, check that your motor id falls within the inclusive range from min_motor_id to max_motor_id.
  2. In the tutorials/launch folder, update the basic_motors.launch file, go to line 12. These parameters are used to set up the dynamixel_motor package. In particular, make sure the port_name and baud_rate match your servo. Also, check that your motor id falls within the inclusive range from min_motor_id to max_motor_id.
  3. Save and compile changes (if applicable).

roslaunch spin_hokuyo basic_motors.launch

  1. In a new terminal, open the rostopics list. There should be two new commands: /tilt_controller/command and /tilt_controller/state. /command will issue new positions to the motor via Float64 (try this using rostopic pub). /state will list various pieces of information about the motor (rostopic echo).
  2. If this is fully functional, kill the node and do:

roslaunch spin_hokuyo tilting_continuous.launch
This should cause the motor to regularly sweep from 90 to -90 and generate a point cloud. Be sure to update the dynamixel_servos_tilting.yaml for position, speed, etc.

Possible Dynamixel Errors

Is the USB properly inserted and setup for your computer?
Is the Dynamixel connected to a 12V power source via the adapter?
Is the switch on the USB adapter at the proper loaction?

Acknowledgements

Inspired by the work seen here: </br> https://github.com/gcc-robotics/3d_photobooth/blob/master/CapstoneFinalReport_VisionTeam.pdf </br>

Dynamixel Control

The class system used to control the Dynamixel motors and the basis for the servo template were based on the examples provided in Chap. 8 of “Effective Robotics Programming with ROS - Third Edition” by Anil Mahtani, Luis Sanchez, Enrique Fernandea, and Aaron Martinez. ##

pcl_assembler_client

The pcl_assembler_client is a modified form of the periodic_snapshotter.cpp which is included in the /examples folder of laser_assembler which is hosted at: https://github.com/ros-perception/laser_assembler ##

Authors

Sarah Bertussi, Paul Szenher, Shi Bai. RFAL (Robust Field Autonomy Lab), Stevens Institute of Technology.

CHANGELOG

Changelog for package spin_hokuyo

1.0.0 (2017-07-21)

  • Removed dyanmixel files in favor of using dependencies as the apt version now apparently works
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Fixed packages in launch files, as well as renamed and organized
  • Update README.md
  • Fixed dynamixel requirement to be subpackages
  • Added dynamixel_controllers to package.xml depends
  • Added dynamixel_controller to package.xml depends
  • Removed pcl as a dependent because it isn't a package
  • Added even more build depends to package.xml
  • Added required build dependencies to package.xml
  • Update package.xml
  • commenting update
  • Acknowledgements Update
  • Update README.md
  • commenting update
  • commenting update
  • commenting update
  • commenting update
  • commenting updates
  • Delete basic_motors.launch~
  • commenting updates
  • CMakeLists update
  • commenting updates
  • commenting update
  • Update CMakeLists.txt
  • Delete hokuyo_ground_filter.cpp
  • Delete floor_max_z.cpp
  • commenting update
  • commenting update
  • commenting update
  • comment update
  • remove backup file
  • remove backup file
  • adding back CMakeLists
  • Temporarilly removed CMakelist.txt to satisfy failed merge
  • organization
  • Delete CMakeLists.txt
  • moved dynamixel controllers
  • moved scan_to_pcl
  • Removed rviz config files and fixed tilting lidar continuous launch file
  • file location update
  • tutorials update
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Renamed misc files and updated launch files and CMakeLists accordingly
  • Delete combine_clouds.cpp
  • Update CMakeLists.txt
  • Update CMakeLists.txt
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Removed extraneous launch files
  • name updates
  • Rename combine_clouds_subscriber.cpp to point_cloud_assembler.cpp
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Renamed hokuyo_filter to hokuyo_robot_filter to fit the naming convention of hokuyo_ground_filter
  • rename for clarity
  • typo
  • file renames
  • Delete combine_clouds.cpp
  • Removed floor removal parameter from octomap
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Removed Plane Extract Ransac from tilting lidar and made minor modifications to launch and cpp files
  • reset clouds
  • Modified combined clouds to allow for parameters and options between time and subscription, changed launch files to allow for further customizations
  • Added support for hokuyo_ground_filter
  • added tolerance
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • remove ground
  • Modified launch files for more universal use and added segmentation launch file and rviz config
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Modified to allow for parameter value to change from dynamixel tilting callback to timer callback
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo Conflicts: tilting_lidar_clean/launch/launch_with_octo/velodyne_hokuyo_octo_tilt_offline.launch
  • plane extraction
  • Disabled Voxel grid as it is uneccesary for non-assembled point clouds
  • Changed name argument to path, requiring full path to be input at launch but allows for universal use across systems
  • Removed rosbag node from online launch file

File truncated at 100 lines see the full file

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Launch files

  • launch/tilt_continuous.launch
    • This launch file causes the Hokuyo to sweep back and forth CONTINUOUSLY
      • assemble [default: velodyne_points]
  • launch/tilt_subscriber.launch
    • This launch file causes the Hokuyo to sweep back and forth ONLY WHEN AN EMPTY MESSAGE is sent to tilt_motor_subscribe node
      • assemble [default: velodyne_points]
  • tutorials/launch/basic_motors.launch
    • This file executes a simple launch of the Dynamixel servo that allows the operator to manually input values for the servo to rotate to. The Hokuyo IS NOT part of this launch.

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged spin_hokuyo at Robotics Stack Exchange

No version for distro jade showing indigo. Known supported distros are highlighted in the buttons above.
Package symbol

spin_hokuyo package from spin_hokuyo repo

spin_hokuyo

ROS Distro
indigo

Package Summary

Tags No category tags.
Version 1.0.0
License GPL
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/RobustFieldAutonomyLab/spin_hokuyo.git
VCS Type git
VCS Version master
Last Updated 2017-10-16
Dev Status MAINTAINED
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

This package enables a 2D Hokuyo laser, connected to a Dynamixel servo motor, to produce a 3D point cloud that can be visualized in rviz and used to make an octomap.

Additional Links

No additional links.

Maintainers

  • Sarah Bertussi
  • Paul Szenher

Authors

No additional authors.

spin_hokuyo

This repository contains code to control a Dynamixel motor and a 2D Hokuyo LiDAR to create a 3D point cloud that can be visualized in rviz. This point cloud can then be used to create an octomap (code for this is not included in this repository).
Wiki Page: http://wiki.ros.org/spin_hokuyo

Setup Directions

  1. Download this ROS Package:

sudo apt-get install ros-indigo-spin-hokuyo

  1. In the tutorials/launch folder, update the basic_motors.launch file, go to line 12. These parameters are used to set up the dynamixel_motor package. In particular, make sure the port_name and baud_rate match your servo. Also, check that your motor id falls within the inclusive range from min_motor_id to max_motor_id.
  2. In the tutorials/launch folder, update the basic_motors.launch file, go to line 12. These parameters are used to set up the dynamixel_motor package. In particular, make sure the port_name and baud_rate match your servo. Also, check that your motor id falls within the inclusive range from min_motor_id to max_motor_id.
  3. Save and compile changes (if applicable).

roslaunch spin_hokuyo basic_motors.launch

  1. In a new terminal, open the rostopics list. There should be two new commands: /tilt_controller/command and /tilt_controller/state. /command will issue new positions to the motor via Float64 (try this using rostopic pub). /state will list various pieces of information about the motor (rostopic echo).
  2. If this is fully functional, kill the node and do:

roslaunch spin_hokuyo tilting_continuous.launch
This should cause the motor to regularly sweep from 90 to -90 and generate a point cloud. Be sure to update the dynamixel_servos_tilting.yaml for position, speed, etc.

Possible Dynamixel Errors

Is the USB properly inserted and setup for your computer?
Is the Dynamixel connected to a 12V power source via the adapter?
Is the switch on the USB adapter at the proper loaction?

Acknowledgements

Inspired by the work seen here: </br> https://github.com/gcc-robotics/3d_photobooth/blob/master/CapstoneFinalReport_VisionTeam.pdf </br>

Dynamixel Control

The class system used to control the Dynamixel motors and the basis for the servo template were based on the examples provided in Chap. 8 of “Effective Robotics Programming with ROS - Third Edition” by Anil Mahtani, Luis Sanchez, Enrique Fernandea, and Aaron Martinez. ##

pcl_assembler_client

The pcl_assembler_client is a modified form of the periodic_snapshotter.cpp which is included in the /examples folder of laser_assembler which is hosted at: https://github.com/ros-perception/laser_assembler ##

Authors

Sarah Bertussi, Paul Szenher, Shi Bai. RFAL (Robust Field Autonomy Lab), Stevens Institute of Technology.

CHANGELOG

Changelog for package spin_hokuyo

1.0.0 (2017-07-21)

  • Removed dyanmixel files in favor of using dependencies as the apt version now apparently works
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Fixed packages in launch files, as well as renamed and organized
  • Update README.md
  • Fixed dynamixel requirement to be subpackages
  • Added dynamixel_controllers to package.xml depends
  • Added dynamixel_controller to package.xml depends
  • Removed pcl as a dependent because it isn't a package
  • Added even more build depends to package.xml
  • Added required build dependencies to package.xml
  • Update package.xml
  • commenting update
  • Acknowledgements Update
  • Update README.md
  • commenting update
  • commenting update
  • commenting update
  • commenting update
  • commenting updates
  • Delete basic_motors.launch~
  • commenting updates
  • CMakeLists update
  • commenting updates
  • commenting update
  • Update CMakeLists.txt
  • Delete hokuyo_ground_filter.cpp
  • Delete floor_max_z.cpp
  • commenting update
  • commenting update
  • commenting update
  • comment update
  • remove backup file
  • remove backup file
  • adding back CMakeLists
  • Temporarilly removed CMakelist.txt to satisfy failed merge
  • organization
  • Delete CMakeLists.txt
  • moved dynamixel controllers
  • moved scan_to_pcl
  • Removed rviz config files and fixed tilting lidar continuous launch file
  • file location update
  • tutorials update
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Renamed misc files and updated launch files and CMakeLists accordingly
  • Delete combine_clouds.cpp
  • Update CMakeLists.txt
  • Update CMakeLists.txt
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Removed extraneous launch files
  • name updates
  • Rename combine_clouds_subscriber.cpp to point_cloud_assembler.cpp
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Renamed hokuyo_filter to hokuyo_robot_filter to fit the naming convention of hokuyo_ground_filter
  • rename for clarity
  • typo
  • file renames
  • Delete combine_clouds.cpp
  • Removed floor removal parameter from octomap
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Removed Plane Extract Ransac from tilting lidar and made minor modifications to launch and cpp files
  • reset clouds
  • Modified combined clouds to allow for parameters and options between time and subscription, changed launch files to allow for further customizations
  • Added support for hokuyo_ground_filter
  • added tolerance
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • remove ground
  • Modified launch files for more universal use and added segmentation launch file and rviz config
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Modified to allow for parameter value to change from dynamixel tilting callback to timer callback
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo Conflicts: tilting_lidar_clean/launch/launch_with_octo/velodyne_hokuyo_octo_tilt_offline.launch
  • plane extraction
  • Disabled Voxel grid as it is uneccesary for non-assembled point clouds
  • Changed name argument to path, requiring full path to be input at launch but allows for universal use across systems
  • Removed rosbag node from online launch file

File truncated at 100 lines see the full file

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Launch files

  • launch/tilt_continuous.launch
    • This launch file causes the Hokuyo to sweep back and forth CONTINUOUSLY
      • assemble [default: velodyne_points]
  • launch/tilt_subscriber.launch
    • This launch file causes the Hokuyo to sweep back and forth ONLY WHEN AN EMPTY MESSAGE is sent to tilt_motor_subscribe node
      • assemble [default: velodyne_points]
  • tutorials/launch/basic_motors.launch
    • This file executes a simple launch of the Dynamixel servo that allows the operator to manually input values for the servo to rotate to. The Hokuyo IS NOT part of this launch.

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged spin_hokuyo at Robotics Stack Exchange

Package symbol

spin_hokuyo package from spin_hokuyo repo

spin_hokuyo

ROS Distro
indigo

Package Summary

Tags No category tags.
Version 1.0.0
License GPL
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/RobustFieldAutonomyLab/spin_hokuyo.git
VCS Type git
VCS Version master
Last Updated 2017-10-16
Dev Status MAINTAINED
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

This package enables a 2D Hokuyo laser, connected to a Dynamixel servo motor, to produce a 3D point cloud that can be visualized in rviz and used to make an octomap.

Additional Links

No additional links.

Maintainers

  • Sarah Bertussi
  • Paul Szenher

Authors

No additional authors.

spin_hokuyo

This repository contains code to control a Dynamixel motor and a 2D Hokuyo LiDAR to create a 3D point cloud that can be visualized in rviz. This point cloud can then be used to create an octomap (code for this is not included in this repository).
Wiki Page: http://wiki.ros.org/spin_hokuyo

Setup Directions

  1. Download this ROS Package:

sudo apt-get install ros-indigo-spin-hokuyo

  1. In the tutorials/launch folder, update the basic_motors.launch file, go to line 12. These parameters are used to set up the dynamixel_motor package. In particular, make sure the port_name and baud_rate match your servo. Also, check that your motor id falls within the inclusive range from min_motor_id to max_motor_id.
  2. In the tutorials/launch folder, update the basic_motors.launch file, go to line 12. These parameters are used to set up the dynamixel_motor package. In particular, make sure the port_name and baud_rate match your servo. Also, check that your motor id falls within the inclusive range from min_motor_id to max_motor_id.
  3. Save and compile changes (if applicable).

roslaunch spin_hokuyo basic_motors.launch

  1. In a new terminal, open the rostopics list. There should be two new commands: /tilt_controller/command and /tilt_controller/state. /command will issue new positions to the motor via Float64 (try this using rostopic pub). /state will list various pieces of information about the motor (rostopic echo).
  2. If this is fully functional, kill the node and do:

roslaunch spin_hokuyo tilting_continuous.launch
This should cause the motor to regularly sweep from 90 to -90 and generate a point cloud. Be sure to update the dynamixel_servos_tilting.yaml for position, speed, etc.

Possible Dynamixel Errors

Is the USB properly inserted and setup for your computer?
Is the Dynamixel connected to a 12V power source via the adapter?
Is the switch on the USB adapter at the proper loaction?

Acknowledgements

Inspired by the work seen here: </br> https://github.com/gcc-robotics/3d_photobooth/blob/master/CapstoneFinalReport_VisionTeam.pdf </br>

Dynamixel Control

The class system used to control the Dynamixel motors and the basis for the servo template were based on the examples provided in Chap. 8 of “Effective Robotics Programming with ROS - Third Edition” by Anil Mahtani, Luis Sanchez, Enrique Fernandea, and Aaron Martinez. ##

pcl_assembler_client

The pcl_assembler_client is a modified form of the periodic_snapshotter.cpp which is included in the /examples folder of laser_assembler which is hosted at: https://github.com/ros-perception/laser_assembler ##

Authors

Sarah Bertussi, Paul Szenher, Shi Bai. RFAL (Robust Field Autonomy Lab), Stevens Institute of Technology.

CHANGELOG

Changelog for package spin_hokuyo

1.0.0 (2017-07-21)

  • Removed dyanmixel files in favor of using dependencies as the apt version now apparently works
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Fixed packages in launch files, as well as renamed and organized
  • Update README.md
  • Fixed dynamixel requirement to be subpackages
  • Added dynamixel_controllers to package.xml depends
  • Added dynamixel_controller to package.xml depends
  • Removed pcl as a dependent because it isn't a package
  • Added even more build depends to package.xml
  • Added required build dependencies to package.xml
  • Update package.xml
  • commenting update
  • Acknowledgements Update
  • Update README.md
  • commenting update
  • commenting update
  • commenting update
  • commenting update
  • commenting updates
  • Delete basic_motors.launch~
  • commenting updates
  • CMakeLists update
  • commenting updates
  • commenting update
  • Update CMakeLists.txt
  • Delete hokuyo_ground_filter.cpp
  • Delete floor_max_z.cpp
  • commenting update
  • commenting update
  • commenting update
  • comment update
  • remove backup file
  • remove backup file
  • adding back CMakeLists
  • Temporarilly removed CMakelist.txt to satisfy failed merge
  • organization
  • Delete CMakeLists.txt
  • moved dynamixel controllers
  • moved scan_to_pcl
  • Removed rviz config files and fixed tilting lidar continuous launch file
  • file location update
  • tutorials update
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Renamed misc files and updated launch files and CMakeLists accordingly
  • Delete combine_clouds.cpp
  • Update CMakeLists.txt
  • Update CMakeLists.txt
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Removed extraneous launch files
  • name updates
  • Rename combine_clouds_subscriber.cpp to point_cloud_assembler.cpp
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Renamed hokuyo_filter to hokuyo_robot_filter to fit the naming convention of hokuyo_ground_filter
  • rename for clarity
  • typo
  • file renames
  • Delete combine_clouds.cpp
  • Removed floor removal parameter from octomap
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Removed Plane Extract Ransac from tilting lidar and made minor modifications to launch and cpp files
  • reset clouds
  • Modified combined clouds to allow for parameters and options between time and subscription, changed launch files to allow for further customizations
  • Added support for hokuyo_ground_filter
  • added tolerance
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • remove ground
  • Modified launch files for more universal use and added segmentation launch file and rviz config
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Modified to allow for parameter value to change from dynamixel tilting callback to timer callback
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo Conflicts: tilting_lidar_clean/launch/launch_with_octo/velodyne_hokuyo_octo_tilt_offline.launch
  • plane extraction
  • Disabled Voxel grid as it is uneccesary for non-assembled point clouds
  • Changed name argument to path, requiring full path to be input at launch but allows for universal use across systems
  • Removed rosbag node from online launch file

File truncated at 100 lines see the full file

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Launch files

  • launch/tilt_continuous.launch
    • This launch file causes the Hokuyo to sweep back and forth CONTINUOUSLY
      • assemble [default: velodyne_points]
  • launch/tilt_subscriber.launch
    • This launch file causes the Hokuyo to sweep back and forth ONLY WHEN AN EMPTY MESSAGE is sent to tilt_motor_subscribe node
      • assemble [default: velodyne_points]
  • tutorials/launch/basic_motors.launch
    • This file executes a simple launch of the Dynamixel servo that allows the operator to manually input values for the servo to rotate to. The Hokuyo IS NOT part of this launch.

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged spin_hokuyo at Robotics Stack Exchange

No version for distro hydro showing indigo. Known supported distros are highlighted in the buttons above.
Package symbol

spin_hokuyo package from spin_hokuyo repo

spin_hokuyo

ROS Distro
indigo

Package Summary

Tags No category tags.
Version 1.0.0
License GPL
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/RobustFieldAutonomyLab/spin_hokuyo.git
VCS Type git
VCS Version master
Last Updated 2017-10-16
Dev Status MAINTAINED
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

This package enables a 2D Hokuyo laser, connected to a Dynamixel servo motor, to produce a 3D point cloud that can be visualized in rviz and used to make an octomap.

Additional Links

No additional links.

Maintainers

  • Sarah Bertussi
  • Paul Szenher

Authors

No additional authors.

spin_hokuyo

This repository contains code to control a Dynamixel motor and a 2D Hokuyo LiDAR to create a 3D point cloud that can be visualized in rviz. This point cloud can then be used to create an octomap (code for this is not included in this repository).
Wiki Page: http://wiki.ros.org/spin_hokuyo

Setup Directions

  1. Download this ROS Package:

sudo apt-get install ros-indigo-spin-hokuyo

  1. In the tutorials/launch folder, update the basic_motors.launch file, go to line 12. These parameters are used to set up the dynamixel_motor package. In particular, make sure the port_name and baud_rate match your servo. Also, check that your motor id falls within the inclusive range from min_motor_id to max_motor_id.
  2. In the tutorials/launch folder, update the basic_motors.launch file, go to line 12. These parameters are used to set up the dynamixel_motor package. In particular, make sure the port_name and baud_rate match your servo. Also, check that your motor id falls within the inclusive range from min_motor_id to max_motor_id.
  3. Save and compile changes (if applicable).

roslaunch spin_hokuyo basic_motors.launch

  1. In a new terminal, open the rostopics list. There should be two new commands: /tilt_controller/command and /tilt_controller/state. /command will issue new positions to the motor via Float64 (try this using rostopic pub). /state will list various pieces of information about the motor (rostopic echo).
  2. If this is fully functional, kill the node and do:

roslaunch spin_hokuyo tilting_continuous.launch
This should cause the motor to regularly sweep from 90 to -90 and generate a point cloud. Be sure to update the dynamixel_servos_tilting.yaml for position, speed, etc.

Possible Dynamixel Errors

Is the USB properly inserted and setup for your computer?
Is the Dynamixel connected to a 12V power source via the adapter?
Is the switch on the USB adapter at the proper loaction?

Acknowledgements

Inspired by the work seen here: </br> https://github.com/gcc-robotics/3d_photobooth/blob/master/CapstoneFinalReport_VisionTeam.pdf </br>

Dynamixel Control

The class system used to control the Dynamixel motors and the basis for the servo template were based on the examples provided in Chap. 8 of “Effective Robotics Programming with ROS - Third Edition” by Anil Mahtani, Luis Sanchez, Enrique Fernandea, and Aaron Martinez. ##

pcl_assembler_client

The pcl_assembler_client is a modified form of the periodic_snapshotter.cpp which is included in the /examples folder of laser_assembler which is hosted at: https://github.com/ros-perception/laser_assembler ##

Authors

Sarah Bertussi, Paul Szenher, Shi Bai. RFAL (Robust Field Autonomy Lab), Stevens Institute of Technology.

CHANGELOG

Changelog for package spin_hokuyo

1.0.0 (2017-07-21)

  • Removed dyanmixel files in favor of using dependencies as the apt version now apparently works
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Fixed packages in launch files, as well as renamed and organized
  • Update README.md
  • Fixed dynamixel requirement to be subpackages
  • Added dynamixel_controllers to package.xml depends
  • Added dynamixel_controller to package.xml depends
  • Removed pcl as a dependent because it isn't a package
  • Added even more build depends to package.xml
  • Added required build dependencies to package.xml
  • Update package.xml
  • commenting update
  • Acknowledgements Update
  • Update README.md
  • commenting update
  • commenting update
  • commenting update
  • commenting update
  • commenting updates
  • Delete basic_motors.launch~
  • commenting updates
  • CMakeLists update
  • commenting updates
  • commenting update
  • Update CMakeLists.txt
  • Delete hokuyo_ground_filter.cpp
  • Delete floor_max_z.cpp
  • commenting update
  • commenting update
  • commenting update
  • comment update
  • remove backup file
  • remove backup file
  • adding back CMakeLists
  • Temporarilly removed CMakelist.txt to satisfy failed merge
  • organization
  • Delete CMakeLists.txt
  • moved dynamixel controllers
  • moved scan_to_pcl
  • Removed rviz config files and fixed tilting lidar continuous launch file
  • file location update
  • tutorials update
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Renamed misc files and updated launch files and CMakeLists accordingly
  • Delete combine_clouds.cpp
  • Update CMakeLists.txt
  • Update CMakeLists.txt
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Removed extraneous launch files
  • name updates
  • Rename combine_clouds_subscriber.cpp to point_cloud_assembler.cpp
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Renamed hokuyo_filter to hokuyo_robot_filter to fit the naming convention of hokuyo_ground_filter
  • rename for clarity
  • typo
  • file renames
  • Delete combine_clouds.cpp
  • Removed floor removal parameter from octomap
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Removed Plane Extract Ransac from tilting lidar and made minor modifications to launch and cpp files
  • reset clouds
  • Modified combined clouds to allow for parameters and options between time and subscription, changed launch files to allow for further customizations
  • Added support for hokuyo_ground_filter
  • added tolerance
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • remove ground
  • Modified launch files for more universal use and added segmentation launch file and rviz config
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Modified to allow for parameter value to change from dynamixel tilting callback to timer callback
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo Conflicts: tilting_lidar_clean/launch/launch_with_octo/velodyne_hokuyo_octo_tilt_offline.launch
  • plane extraction
  • Disabled Voxel grid as it is uneccesary for non-assembled point clouds
  • Changed name argument to path, requiring full path to be input at launch but allows for universal use across systems
  • Removed rosbag node from online launch file

File truncated at 100 lines see the full file

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Launch files

  • launch/tilt_continuous.launch
    • This launch file causes the Hokuyo to sweep back and forth CONTINUOUSLY
      • assemble [default: velodyne_points]
  • launch/tilt_subscriber.launch
    • This launch file causes the Hokuyo to sweep back and forth ONLY WHEN AN EMPTY MESSAGE is sent to tilt_motor_subscribe node
      • assemble [default: velodyne_points]
  • tutorials/launch/basic_motors.launch
    • This file executes a simple launch of the Dynamixel servo that allows the operator to manually input values for the servo to rotate to. The Hokuyo IS NOT part of this launch.

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged spin_hokuyo at Robotics Stack Exchange

No version for distro kinetic showing indigo. Known supported distros are highlighted in the buttons above.
Package symbol

spin_hokuyo package from spin_hokuyo repo

spin_hokuyo

ROS Distro
indigo

Package Summary

Tags No category tags.
Version 1.0.0
License GPL
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/RobustFieldAutonomyLab/spin_hokuyo.git
VCS Type git
VCS Version master
Last Updated 2017-10-16
Dev Status MAINTAINED
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

This package enables a 2D Hokuyo laser, connected to a Dynamixel servo motor, to produce a 3D point cloud that can be visualized in rviz and used to make an octomap.

Additional Links

No additional links.

Maintainers

  • Sarah Bertussi
  • Paul Szenher

Authors

No additional authors.

spin_hokuyo

This repository contains code to control a Dynamixel motor and a 2D Hokuyo LiDAR to create a 3D point cloud that can be visualized in rviz. This point cloud can then be used to create an octomap (code for this is not included in this repository).
Wiki Page: http://wiki.ros.org/spin_hokuyo

Setup Directions

  1. Download this ROS Package:

sudo apt-get install ros-indigo-spin-hokuyo

  1. In the tutorials/launch folder, update the basic_motors.launch file, go to line 12. These parameters are used to set up the dynamixel_motor package. In particular, make sure the port_name and baud_rate match your servo. Also, check that your motor id falls within the inclusive range from min_motor_id to max_motor_id.
  2. In the tutorials/launch folder, update the basic_motors.launch file, go to line 12. These parameters are used to set up the dynamixel_motor package. In particular, make sure the port_name and baud_rate match your servo. Also, check that your motor id falls within the inclusive range from min_motor_id to max_motor_id.
  3. Save and compile changes (if applicable).

roslaunch spin_hokuyo basic_motors.launch

  1. In a new terminal, open the rostopics list. There should be two new commands: /tilt_controller/command and /tilt_controller/state. /command will issue new positions to the motor via Float64 (try this using rostopic pub). /state will list various pieces of information about the motor (rostopic echo).
  2. If this is fully functional, kill the node and do:

roslaunch spin_hokuyo tilting_continuous.launch
This should cause the motor to regularly sweep from 90 to -90 and generate a point cloud. Be sure to update the dynamixel_servos_tilting.yaml for position, speed, etc.

Possible Dynamixel Errors

Is the USB properly inserted and setup for your computer?
Is the Dynamixel connected to a 12V power source via the adapter?
Is the switch on the USB adapter at the proper loaction?

Acknowledgements

Inspired by the work seen here: </br> https://github.com/gcc-robotics/3d_photobooth/blob/master/CapstoneFinalReport_VisionTeam.pdf </br>

Dynamixel Control

The class system used to control the Dynamixel motors and the basis for the servo template were based on the examples provided in Chap. 8 of “Effective Robotics Programming with ROS - Third Edition” by Anil Mahtani, Luis Sanchez, Enrique Fernandea, and Aaron Martinez. ##

pcl_assembler_client

The pcl_assembler_client is a modified form of the periodic_snapshotter.cpp which is included in the /examples folder of laser_assembler which is hosted at: https://github.com/ros-perception/laser_assembler ##

Authors

Sarah Bertussi, Paul Szenher, Shi Bai. RFAL (Robust Field Autonomy Lab), Stevens Institute of Technology.

CHANGELOG

Changelog for package spin_hokuyo

1.0.0 (2017-07-21)

  • Removed dyanmixel files in favor of using dependencies as the apt version now apparently works
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Fixed packages in launch files, as well as renamed and organized
  • Update README.md
  • Fixed dynamixel requirement to be subpackages
  • Added dynamixel_controllers to package.xml depends
  • Added dynamixel_controller to package.xml depends
  • Removed pcl as a dependent because it isn't a package
  • Added even more build depends to package.xml
  • Added required build dependencies to package.xml
  • Update package.xml
  • commenting update
  • Acknowledgements Update
  • Update README.md
  • commenting update
  • commenting update
  • commenting update
  • commenting update
  • commenting updates
  • Delete basic_motors.launch~
  • commenting updates
  • CMakeLists update
  • commenting updates
  • commenting update
  • Update CMakeLists.txt
  • Delete hokuyo_ground_filter.cpp
  • Delete floor_max_z.cpp
  • commenting update
  • commenting update
  • commenting update
  • comment update
  • remove backup file
  • remove backup file
  • adding back CMakeLists
  • Temporarilly removed CMakelist.txt to satisfy failed merge
  • organization
  • Delete CMakeLists.txt
  • moved dynamixel controllers
  • moved scan_to_pcl
  • Removed rviz config files and fixed tilting lidar continuous launch file
  • file location update
  • tutorials update
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Renamed misc files and updated launch files and CMakeLists accordingly
  • Delete combine_clouds.cpp
  • Update CMakeLists.txt
  • Update CMakeLists.txt
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Removed extraneous launch files
  • name updates
  • Rename combine_clouds_subscriber.cpp to point_cloud_assembler.cpp
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Renamed hokuyo_filter to hokuyo_robot_filter to fit the naming convention of hokuyo_ground_filter
  • rename for clarity
  • typo
  • file renames
  • Delete combine_clouds.cpp
  • Removed floor removal parameter from octomap
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Removed Plane Extract Ransac from tilting lidar and made minor modifications to launch and cpp files
  • reset clouds
  • Modified combined clouds to allow for parameters and options between time and subscription, changed launch files to allow for further customizations
  • Added support for hokuyo_ground_filter
  • added tolerance
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • remove ground
  • Modified launch files for more universal use and added segmentation launch file and rviz config
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Modified to allow for parameter value to change from dynamixel tilting callback to timer callback
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo Conflicts: tilting_lidar_clean/launch/launch_with_octo/velodyne_hokuyo_octo_tilt_offline.launch
  • plane extraction
  • Disabled Voxel grid as it is uneccesary for non-assembled point clouds
  • Changed name argument to path, requiring full path to be input at launch but allows for universal use across systems
  • Removed rosbag node from online launch file

File truncated at 100 lines see the full file

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Launch files

  • launch/tilt_continuous.launch
    • This launch file causes the Hokuyo to sweep back and forth CONTINUOUSLY
      • assemble [default: velodyne_points]
  • launch/tilt_subscriber.launch
    • This launch file causes the Hokuyo to sweep back and forth ONLY WHEN AN EMPTY MESSAGE is sent to tilt_motor_subscribe node
      • assemble [default: velodyne_points]
  • tutorials/launch/basic_motors.launch
    • This file executes a simple launch of the Dynamixel servo that allows the operator to manually input values for the servo to rotate to. The Hokuyo IS NOT part of this launch.

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged spin_hokuyo at Robotics Stack Exchange

No version for distro melodic showing indigo. Known supported distros are highlighted in the buttons above.
Package symbol

spin_hokuyo package from spin_hokuyo repo

spin_hokuyo

ROS Distro
indigo

Package Summary

Tags No category tags.
Version 1.0.0
License GPL
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/RobustFieldAutonomyLab/spin_hokuyo.git
VCS Type git
VCS Version master
Last Updated 2017-10-16
Dev Status MAINTAINED
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

This package enables a 2D Hokuyo laser, connected to a Dynamixel servo motor, to produce a 3D point cloud that can be visualized in rviz and used to make an octomap.

Additional Links

No additional links.

Maintainers

  • Sarah Bertussi
  • Paul Szenher

Authors

No additional authors.

spin_hokuyo

This repository contains code to control a Dynamixel motor and a 2D Hokuyo LiDAR to create a 3D point cloud that can be visualized in rviz. This point cloud can then be used to create an octomap (code for this is not included in this repository).
Wiki Page: http://wiki.ros.org/spin_hokuyo

Setup Directions

  1. Download this ROS Package:

sudo apt-get install ros-indigo-spin-hokuyo

  1. In the tutorials/launch folder, update the basic_motors.launch file, go to line 12. These parameters are used to set up the dynamixel_motor package. In particular, make sure the port_name and baud_rate match your servo. Also, check that your motor id falls within the inclusive range from min_motor_id to max_motor_id.
  2. In the tutorials/launch folder, update the basic_motors.launch file, go to line 12. These parameters are used to set up the dynamixel_motor package. In particular, make sure the port_name and baud_rate match your servo. Also, check that your motor id falls within the inclusive range from min_motor_id to max_motor_id.
  3. Save and compile changes (if applicable).

roslaunch spin_hokuyo basic_motors.launch

  1. In a new terminal, open the rostopics list. There should be two new commands: /tilt_controller/command and /tilt_controller/state. /command will issue new positions to the motor via Float64 (try this using rostopic pub). /state will list various pieces of information about the motor (rostopic echo).
  2. If this is fully functional, kill the node and do:

roslaunch spin_hokuyo tilting_continuous.launch
This should cause the motor to regularly sweep from 90 to -90 and generate a point cloud. Be sure to update the dynamixel_servos_tilting.yaml for position, speed, etc.

Possible Dynamixel Errors

Is the USB properly inserted and setup for your computer?
Is the Dynamixel connected to a 12V power source via the adapter?
Is the switch on the USB adapter at the proper loaction?

Acknowledgements

Inspired by the work seen here: </br> https://github.com/gcc-robotics/3d_photobooth/blob/master/CapstoneFinalReport_VisionTeam.pdf </br>

Dynamixel Control

The class system used to control the Dynamixel motors and the basis for the servo template were based on the examples provided in Chap. 8 of “Effective Robotics Programming with ROS - Third Edition” by Anil Mahtani, Luis Sanchez, Enrique Fernandea, and Aaron Martinez. ##

pcl_assembler_client

The pcl_assembler_client is a modified form of the periodic_snapshotter.cpp which is included in the /examples folder of laser_assembler which is hosted at: https://github.com/ros-perception/laser_assembler ##

Authors

Sarah Bertussi, Paul Szenher, Shi Bai. RFAL (Robust Field Autonomy Lab), Stevens Institute of Technology.

CHANGELOG

Changelog for package spin_hokuyo

1.0.0 (2017-07-21)

  • Removed dyanmixel files in favor of using dependencies as the apt version now apparently works
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Fixed packages in launch files, as well as renamed and organized
  • Update README.md
  • Fixed dynamixel requirement to be subpackages
  • Added dynamixel_controllers to package.xml depends
  • Added dynamixel_controller to package.xml depends
  • Removed pcl as a dependent because it isn't a package
  • Added even more build depends to package.xml
  • Added required build dependencies to package.xml
  • Update package.xml
  • commenting update
  • Acknowledgements Update
  • Update README.md
  • commenting update
  • commenting update
  • commenting update
  • commenting update
  • commenting updates
  • Delete basic_motors.launch~
  • commenting updates
  • CMakeLists update
  • commenting updates
  • commenting update
  • Update CMakeLists.txt
  • Delete hokuyo_ground_filter.cpp
  • Delete floor_max_z.cpp
  • commenting update
  • commenting update
  • commenting update
  • comment update
  • remove backup file
  • remove backup file
  • adding back CMakeLists
  • Temporarilly removed CMakelist.txt to satisfy failed merge
  • organization
  • Delete CMakeLists.txt
  • moved dynamixel controllers
  • moved scan_to_pcl
  • Removed rviz config files and fixed tilting lidar continuous launch file
  • file location update
  • tutorials update
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Renamed misc files and updated launch files and CMakeLists accordingly
  • Delete combine_clouds.cpp
  • Update CMakeLists.txt
  • Update CMakeLists.txt
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Removed extraneous launch files
  • name updates
  • Rename combine_clouds_subscriber.cpp to point_cloud_assembler.cpp
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Renamed hokuyo_filter to hokuyo_robot_filter to fit the naming convention of hokuyo_ground_filter
  • rename for clarity
  • typo
  • file renames
  • Delete combine_clouds.cpp
  • Removed floor removal parameter from octomap
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Removed Plane Extract Ransac from tilting lidar and made minor modifications to launch and cpp files
  • reset clouds
  • Modified combined clouds to allow for parameters and options between time and subscription, changed launch files to allow for further customizations
  • Added support for hokuyo_ground_filter
  • added tolerance
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • remove ground
  • Modified launch files for more universal use and added segmentation launch file and rviz config
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Modified to allow for parameter value to change from dynamixel tilting callback to timer callback
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo Conflicts: tilting_lidar_clean/launch/launch_with_octo/velodyne_hokuyo_octo_tilt_offline.launch
  • plane extraction
  • Disabled Voxel grid as it is uneccesary for non-assembled point clouds
  • Changed name argument to path, requiring full path to be input at launch but allows for universal use across systems
  • Removed rosbag node from online launch file

File truncated at 100 lines see the full file

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Launch files

  • launch/tilt_continuous.launch
    • This launch file causes the Hokuyo to sweep back and forth CONTINUOUSLY
      • assemble [default: velodyne_points]
  • launch/tilt_subscriber.launch
    • This launch file causes the Hokuyo to sweep back and forth ONLY WHEN AN EMPTY MESSAGE is sent to tilt_motor_subscribe node
      • assemble [default: velodyne_points]
  • tutorials/launch/basic_motors.launch
    • This file executes a simple launch of the Dynamixel servo that allows the operator to manually input values for the servo to rotate to. The Hokuyo IS NOT part of this launch.

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged spin_hokuyo at Robotics Stack Exchange

No version for distro noetic showing indigo. Known supported distros are highlighted in the buttons above.
Package symbol

spin_hokuyo package from spin_hokuyo repo

spin_hokuyo

ROS Distro
indigo

Package Summary

Tags No category tags.
Version 1.0.0
License GPL
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/RobustFieldAutonomyLab/spin_hokuyo.git
VCS Type git
VCS Version master
Last Updated 2017-10-16
Dev Status MAINTAINED
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

This package enables a 2D Hokuyo laser, connected to a Dynamixel servo motor, to produce a 3D point cloud that can be visualized in rviz and used to make an octomap.

Additional Links

No additional links.

Maintainers

  • Sarah Bertussi
  • Paul Szenher

Authors

No additional authors.

spin_hokuyo

This repository contains code to control a Dynamixel motor and a 2D Hokuyo LiDAR to create a 3D point cloud that can be visualized in rviz. This point cloud can then be used to create an octomap (code for this is not included in this repository).
Wiki Page: http://wiki.ros.org/spin_hokuyo

Setup Directions

  1. Download this ROS Package:

sudo apt-get install ros-indigo-spin-hokuyo

  1. In the tutorials/launch folder, update the basic_motors.launch file, go to line 12. These parameters are used to set up the dynamixel_motor package. In particular, make sure the port_name and baud_rate match your servo. Also, check that your motor id falls within the inclusive range from min_motor_id to max_motor_id.
  2. In the tutorials/launch folder, update the basic_motors.launch file, go to line 12. These parameters are used to set up the dynamixel_motor package. In particular, make sure the port_name and baud_rate match your servo. Also, check that your motor id falls within the inclusive range from min_motor_id to max_motor_id.
  3. Save and compile changes (if applicable).

roslaunch spin_hokuyo basic_motors.launch

  1. In a new terminal, open the rostopics list. There should be two new commands: /tilt_controller/command and /tilt_controller/state. /command will issue new positions to the motor via Float64 (try this using rostopic pub). /state will list various pieces of information about the motor (rostopic echo).
  2. If this is fully functional, kill the node and do:

roslaunch spin_hokuyo tilting_continuous.launch
This should cause the motor to regularly sweep from 90 to -90 and generate a point cloud. Be sure to update the dynamixel_servos_tilting.yaml for position, speed, etc.

Possible Dynamixel Errors

Is the USB properly inserted and setup for your computer?
Is the Dynamixel connected to a 12V power source via the adapter?
Is the switch on the USB adapter at the proper loaction?

Acknowledgements

Inspired by the work seen here: </br> https://github.com/gcc-robotics/3d_photobooth/blob/master/CapstoneFinalReport_VisionTeam.pdf </br>

Dynamixel Control

The class system used to control the Dynamixel motors and the basis for the servo template were based on the examples provided in Chap. 8 of “Effective Robotics Programming with ROS - Third Edition” by Anil Mahtani, Luis Sanchez, Enrique Fernandea, and Aaron Martinez. ##

pcl_assembler_client

The pcl_assembler_client is a modified form of the periodic_snapshotter.cpp which is included in the /examples folder of laser_assembler which is hosted at: https://github.com/ros-perception/laser_assembler ##

Authors

Sarah Bertussi, Paul Szenher, Shi Bai. RFAL (Robust Field Autonomy Lab), Stevens Institute of Technology.

CHANGELOG

Changelog for package spin_hokuyo

1.0.0 (2017-07-21)

  • Removed dyanmixel files in favor of using dependencies as the apt version now apparently works
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Fixed packages in launch files, as well as renamed and organized
  • Update README.md
  • Fixed dynamixel requirement to be subpackages
  • Added dynamixel_controllers to package.xml depends
  • Added dynamixel_controller to package.xml depends
  • Removed pcl as a dependent because it isn't a package
  • Added even more build depends to package.xml
  • Added required build dependencies to package.xml
  • Update package.xml
  • commenting update
  • Acknowledgements Update
  • Update README.md
  • commenting update
  • commenting update
  • commenting update
  • commenting update
  • commenting updates
  • Delete basic_motors.launch~
  • commenting updates
  • CMakeLists update
  • commenting updates
  • commenting update
  • Update CMakeLists.txt
  • Delete hokuyo_ground_filter.cpp
  • Delete floor_max_z.cpp
  • commenting update
  • commenting update
  • commenting update
  • comment update
  • remove backup file
  • remove backup file
  • adding back CMakeLists
  • Temporarilly removed CMakelist.txt to satisfy failed merge
  • organization
  • Delete CMakeLists.txt
  • moved dynamixel controllers
  • moved scan_to_pcl
  • Removed rviz config files and fixed tilting lidar continuous launch file
  • file location update
  • tutorials update
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Renamed misc files and updated launch files and CMakeLists accordingly
  • Delete combine_clouds.cpp
  • Update CMakeLists.txt
  • Update CMakeLists.txt
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Removed extraneous launch files
  • name updates
  • Rename combine_clouds_subscriber.cpp to point_cloud_assembler.cpp
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Renamed hokuyo_filter to hokuyo_robot_filter to fit the naming convention of hokuyo_ground_filter
  • rename for clarity
  • typo
  • file renames
  • Delete combine_clouds.cpp
  • Removed floor removal parameter from octomap
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Removed Plane Extract Ransac from tilting lidar and made minor modifications to launch and cpp files
  • reset clouds
  • Modified combined clouds to allow for parameters and options between time and subscription, changed launch files to allow for further customizations
  • Added support for hokuyo_ground_filter
  • added tolerance
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • remove ground
  • Modified launch files for more universal use and added segmentation launch file and rviz config
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo
  • Modified to allow for parameter value to change from dynamixel tilting callback to timer callback
  • Merge branch 'master' of https://github.com/RobustFieldAutonomyLab/spin_hokuyo Conflicts: tilting_lidar_clean/launch/launch_with_octo/velodyne_hokuyo_octo_tilt_offline.launch
  • plane extraction
  • Disabled Voxel grid as it is uneccesary for non-assembled point clouds
  • Changed name argument to path, requiring full path to be input at launch but allows for universal use across systems
  • Removed rosbag node from online launch file

File truncated at 100 lines see the full file

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Launch files

  • launch/tilt_continuous.launch
    • This launch file causes the Hokuyo to sweep back and forth CONTINUOUSLY
      • assemble [default: velodyne_points]
  • launch/tilt_subscriber.launch
    • This launch file causes the Hokuyo to sweep back and forth ONLY WHEN AN EMPTY MESSAGE is sent to tilt_motor_subscribe node
      • assemble [default: velodyne_points]
  • tutorials/launch/basic_motors.launch
    • This file executes a simple launch of the Dynamixel servo that allows the operator to manually input values for the servo to rotate to. The Hokuyo IS NOT part of this launch.

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged spin_hokuyo at Robotics Stack Exchange