No version for distro dashing. Known supported distros are highlighted in the buttons above.
No version for distro crystal. Known supported distros are highlighted in the buttons above.
No version for distro bouncy. Known supported distros are highlighted in the buttons above.

Package Summary

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

Repository Summary

Checkout URI https://github.com/RobotnikAutomation/summit_xl_common.git
VCS Type git
VCS Version melodic-devel
Last Updated 2019-07-23
Dev Status MAINTAINED
Released UNRELEASED

Package Description

The summit_xl_localization package

Additional Links

Maintainers

  • Angel Soriano
  • Álvaro Villena
  • David Redó
  • Alejandro Arnal
  • Marc Bosch
  • Román Navarro

Authors

No additional authors.
README
No README found. See repository README.
CHANGELOG

Changelog for package summit_xl_localization

1.1.3 (2018-05-15)

  • localization: adding new dependencies with amcl, map_server & gmapping
  • merging with kinetic-multirobot-devel
  • updating mantainers
  • Add parameters to change navigation and localization mode
  • [summit_xl_localization] odom topic changed to robotnik_base_control/odom
  • localization: adding arg to amcl.launch to use either diff or omni model type
  • localization: updating map_saver.launch to save in home folder by default
  • localization: updating scritpt to save map in current folder
  • localization: tests scripts to print orientation values (odom,imu) as rpy
  • moving amcl,map_server from nav to loc pkg. Creating arguments for most of launch files
  • summit_xl_localization/navigation: changed topics and services to make work rl_utils
  • [summit_xl_localization]:prefix frame added to launch files and frames
  • Merge branch \'kinetic-devel\' into kinetic-multirobot-devel
  • Merge branch \'indigo-devel-rc\' into kinetic-devel
  • updated odom params for diff_drive_controller and ekf filter config
  • summit_xl_localization: adds script to use current gps position to call datum service
  • summit_xl_localization: adding extra info and fixes indentation
  • summit_xl_localization: added wait_for_datum param
  • 1.0.10

1.1.2 (2016-09-01)

  • fixed merge conflicts
  • summit_xl_localization: commented robot_localization launch files
  • summit_xl_localization: updated robot_localization launch files
  • summit_xl_localization: added navsat_transform_new to CMakeLists.txt
  • 1.0.9
  • updated changelog
  • Contributors: Marc Bosch-Jorge, carlos3dx

1.1.1 (2016-08-24)

1.1.0 (2016-08-24)

1.0.9 (2016-08-24)

  • Adding install rules
  • Deleting unused files
  • Added rl_utils.launch
  • Contributors: Jorge Arino, summit

1.0.8 (2016-07-12)

1.0.7 (2016-07-12)

  • updated changelog
  • Contributors: carlos3dx

1.0.6 (2016-07-12)

1.0.5 (2016-07-05)

1.0.4 (2016-06-30)

  • added dependency
  • Contributors: carlos3dx

1.0.3 (2016-06-29)

1.0.2 (2016-06-28)

1.0.1 (2016-06-28)

  • indigo-1.0.0
  • added simple script to test magnetometer
  • Merge branch \'indigo-devel\' of https://github.com/RobotnikAutomation/summit_xl_common into indigo-devel Conflicts: summit_xl_localization/launch/navsat_transform_node.launch
  • configuration tested in Lisbon uploaded
  • summit_xl_localization: added dependency to robotnik_msgs
  • Topic name change
  • Minor changes
  • Update launch files. Add robot_localization_utils
  • Update robot_localization_odom.launch
  • Frame name change
  • Add local_tf node
  • Static tf update
  • Add launch files and the new navsat_transform node
  • First commit summit_xl_localization
  • Contributors: Elena Gambaro, ElenaFG, Jorge Arino, mcantero, rguzman
  • added simple script to test magnetometer
  • Merge branch \'indigo-devel\' of https://github.com/RobotnikAutomation/summit_xl_common into indigo-devel Conflicts: summit_xl_localization/launch/navsat_transform_node.launch
  • configuration tested in Lisbon uploaded
  • summit_xl_localization: added dependency to robotnik_msgs
  • Topic name change
  • Minor changes
  • Update launch files. Add robot_localization_utils
  • Update robot_localization_odom.launch
  • Frame name change
  • Add local_tf node
  • Static tf update
  • Add launch files and the new navsat_transform node
  • First commit summit_xl_localization
  • Contributors: Elena Gambaro, ElenaFG, Jorge Arino, rguzman

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Launch files

  • launch/map_server.launch
      • map_file [default: map1/map1.yaml]
      • prefix [default: summit_xl_]
      • frame_id [default: $(arg prefix)map]
  • launch/slam_gmapping.launch
      • prefix [default: summit_xl_]
      • scan_topic [default: front_laser/scan]
      • map_frame [default: $(arg prefix)map]
      • odom_frame [default: $(arg prefix)odom]
      • base_frame [default: $(arg prefix)base_link]
  • launch/navsat_transform_node.launch
    • This comes from the navsat_transform_template.launch. Explains what this node does. This node needs to know the values of three variables in order to function: (1) A world-referenced heading (yaw). The node assumes an ENU standard for heading, with 0 facing east, though it can support any heading. (2) Odometry data that gives the robot's current pose in its own local coordinate frame (typically map or odom) (3) A latitude/longitude/altitude. These three items allow us to compute a transform from the global frame to your robot's local frame. There are several means of providing them, though keep in mind that these modes are typically mutually exclusive. (1) World-referenced yaw can be provided by: (a) an IMU in a sensor_msgs/Imu message (topic is /imu/data/) (b) the heading in the nav_msgs/Odometry message in (2) below can be used. To enable this behavior, set the use_odometry_yaw parameter to true, and set the delay parameter to some small value (~3 seconds). Be careful, though: this heading must still be globally referenced, so if your state estimation node always starts with a 0 heading, you CAN NOT use this option. (c) the "datum" service. See below. (2) The odometry data, which needs to have a valid frame_id, can be provided by: (a) a nav_msgs/Odometry message from your robot_localization state estimation node. (b) the "datum" service (all odometry variables are assumed to be 0 in this case). See below. (3) The latitude, longitude, and altitude can be provided by: (a) a sensor_msgs/NavSatFix message (b) the "datum" service (4) Alternatively, at any time, the user can send a robot_localization/SetDatum service message to the "datum" service. This will manually set the latitude, longitude, altitude, and world-referenced heading, and will assume an odometry message containing all zeros. This will effectively set the origin at the specified lat-long, with the X-axis aligned with east. The user can set this datum via the "datum" service, or via the launch file. If the wait_for_datum parameter is set to true, then the node will attempt to use the datum parameter. If the parameter is not set, it will wait until it receives a service call. The output of this node is an odometry message that contains the GPS data transformed into the robot's world coordinate frame (i.e., the frame specified by input (2)'s frame_id), or the coordinate frame defined by the message sent to the "datum" service.
      • wait_for_datum [default: false]
  • launch/robot_localization_complete.launch
      • debug [default: false]
      • gui [default: true]
      • wait_for_datum [default: false]
      • prefix [default: summit_xl_a_]
  • launch/amcl.launch
      • prefix [default: summit_xl_]
      • x_init_pose [default: 0]
      • y_init_pose [default: 0]
      • z_init_pose [default: 0]
      • scan_topic [default: front_laser/scan]
      • map_topic [default: map]
      • global_frame [default: $(arg prefix)map]
      • odom_frame [default: $(arg prefix)odom]
      • base_frame [default: $(arg prefix)base_footprint]
      • odom_model_type [default: diff]
  • launch/rl_utils.launch
  • launch/map_saver.launch
      • map_name [default: map]
      • map_topic [default: map]
      • destination_folder [default: $(optenv HOME /home/summit)]
  • launch/robot_localization_odom.launch
      • prefix [default: summit_xl_]
      • odom_frame [default: $(arg prefix)odom]
      • base_frame [default: $(arg prefix)base_footprint]
      • odom_topic [default: robotnik_base_control/odom]
      • imu_topic [default: imu/data]
  • launch/robot_localization_world.launch
      • prefix [default: summit_xl_]
      • global_frame [default: world_frame]

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged summit_xl_localization at answers.ros.org

Package Summary

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

Repository Summary

Checkout URI https://github.com/RobotnikAutomation/summit_xl_common.git
VCS Type git
VCS Version kinetic-devel
Last Updated 2019-10-24
Dev Status MAINTAINED
Released RELEASED

Package Description

The summit_xl_localization package

Additional Links

Maintainers

  • Angel Soriano
  • Álvaro Villena
  • David Redó
  • Alejandro Arnal
  • Marc Bosch
  • Román Navarro

Authors

No additional authors.
README
No README found. See repository README.
CHANGELOG

Changelog for package summit_xl_localization

1.1.3 (2018-05-15)

  • localization: adding new dependencies with amcl, map_server & gmapping
  • merging with kinetic-multirobot-devel
  • updating mantainers
  • Add parameters to change navigation and localization mode
  • [summit_xl_localization] odom topic changed to robotnik_base_control/odom
  • localization: adding arg to amcl.launch to use either diff or omni model type
  • localization: updating map_saver.launch to save in home folder by default
  • localization: updating scritpt to save map in current folder
  • localization: tests scripts to print orientation values (odom,imu) as rpy
  • moving amcl,map_server from nav to loc pkg. Creating arguments for most of launch files
  • summit_xl_localization/navigation: changed topics and services to make work rl_utils
  • [summit_xl_localization]:prefix frame added to launch files and frames
  • Merge branch \'kinetic-devel\' into kinetic-multirobot-devel
  • Merge branch \'indigo-devel-rc\' into kinetic-devel
  • updated odom params for diff_drive_controller and ekf filter config
  • summit_xl_localization: adds script to use current gps position to call datum service
  • summit_xl_localization: adding extra info and fixes indentation
  • summit_xl_localization: added wait_for_datum param
  • 1.0.10

1.1.2 (2016-09-01)

  • fixed merge conflicts
  • summit_xl_localization: commented robot_localization launch files
  • summit_xl_localization: updated robot_localization launch files
  • summit_xl_localization: added navsat_transform_new to CMakeLists.txt
  • 1.0.9
  • updated changelog
  • Contributors: Marc Bosch-Jorge, carlos3dx

1.1.1 (2016-08-24)

1.1.0 (2016-08-24)

1.0.9 (2016-08-24)

  • Adding install rules
  • Deleting unused files
  • Added rl_utils.launch
  • Contributors: Jorge Arino, summit

1.0.8 (2016-07-12)

1.0.7 (2016-07-12)

  • updated changelog
  • Contributors: carlos3dx

1.0.6 (2016-07-12)

1.0.5 (2016-07-05)

1.0.4 (2016-06-30)

  • added dependency
  • Contributors: carlos3dx

1.0.3 (2016-06-29)

1.0.2 (2016-06-28)

1.0.1 (2016-06-28)

  • indigo-1.0.0
  • added simple script to test magnetometer
  • Merge branch \'indigo-devel\' of https://github.com/RobotnikAutomation/summit_xl_common into indigo-devel Conflicts: summit_xl_localization/launch/navsat_transform_node.launch
  • configuration tested in Lisbon uploaded
  • summit_xl_localization: added dependency to robotnik_msgs
  • Topic name change
  • Minor changes
  • Update launch files. Add robot_localization_utils
  • Update robot_localization_odom.launch
  • Frame name change
  • Add local_tf node
  • Static tf update
  • Add launch files and the new navsat_transform node
  • First commit summit_xl_localization
  • Contributors: Elena Gambaro, ElenaFG, Jorge Arino, mcantero, rguzman
  • added simple script to test magnetometer
  • Merge branch \'indigo-devel\' of https://github.com/RobotnikAutomation/summit_xl_common into indigo-devel Conflicts: summit_xl_localization/launch/navsat_transform_node.launch
  • configuration tested in Lisbon uploaded
  • summit_xl_localization: added dependency to robotnik_msgs
  • Topic name change
  • Minor changes
  • Update launch files. Add robot_localization_utils
  • Update robot_localization_odom.launch
  • Frame name change
  • Add local_tf node
  • Static tf update
  • Add launch files and the new navsat_transform node
  • First commit summit_xl_localization
  • Contributors: Elena Gambaro, ElenaFG, Jorge Arino, rguzman

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Launch files

  • launch/map_server.launch
      • map_file [default: map1/map1.yaml]
      • prefix [default: summit_xl_]
      • frame_id [default: $(arg prefix)map]
  • launch/slam_gmapping.launch
      • prefix [default: summit_xl_]
      • scan_topic [default: front_laser/scan]
      • map_frame [default: $(arg prefix)map]
      • odom_frame [default: $(arg prefix)odom]
      • base_frame [default: $(arg prefix)base_link]
  • launch/navsat_transform_node.launch
    • This comes from the navsat_transform_template.launch. Explains what this node does. This node needs to know the values of three variables in order to function: (1) A world-referenced heading (yaw). The node assumes an ENU standard for heading, with 0 facing east, though it can support any heading. (2) Odometry data that gives the robot's current pose in its own local coordinate frame (typically map or odom) (3) A latitude/longitude/altitude. These three items allow us to compute a transform from the global frame to your robot's local frame. There are several means of providing them, though keep in mind that these modes are typically mutually exclusive. (1) World-referenced yaw can be provided by: (a) an IMU in a sensor_msgs/Imu message (topic is /imu/data/) (b) the heading in the nav_msgs/Odometry message in (2) below can be used. To enable this behavior, set the use_odometry_yaw parameter to true, and set the delay parameter to some small value (~3 seconds). Be careful, though: this heading must still be globally referenced, so if your state estimation node always starts with a 0 heading, you CAN NOT use this option. (c) the "datum" service. See below. (2) The odometry data, which needs to have a valid frame_id, can be provided by: (a) a nav_msgs/Odometry message from your robot_localization state estimation node. (b) the "datum" service (all odometry variables are assumed to be 0 in this case). See below. (3) The latitude, longitude, and altitude can be provided by: (a) a sensor_msgs/NavSatFix message (b) the "datum" service (4) Alternatively, at any time, the user can send a robot_localization/SetDatum service message to the "datum" service. This will manually set the latitude, longitude, altitude, and world-referenced heading, and will assume an odometry message containing all zeros. This will effectively set the origin at the specified lat-long, with the X-axis aligned with east. The user can set this datum via the "datum" service, or via the launch file. If the wait_for_datum parameter is set to true, then the node will attempt to use the datum parameter. If the parameter is not set, it will wait until it receives a service call. The output of this node is an odometry message that contains the GPS data transformed into the robot's world coordinate frame (i.e., the frame specified by input (2)'s frame_id), or the coordinate frame defined by the message sent to the "datum" service.
      • wait_for_datum [default: false]
  • launch/robot_localization_complete.launch
      • debug [default: false]
      • gui [default: true]
      • wait_for_datum [default: false]
      • prefix [default: summit_xl_a_]
  • launch/amcl.launch
      • prefix [default: summit_xl_]
      • x_init_pose [default: 0]
      • y_init_pose [default: 0]
      • z_init_pose [default: 0]
      • scan_topic [default: front_laser/scan]
      • map_topic [default: map]
      • global_frame [default: $(arg prefix)map]
      • odom_frame [default: $(arg prefix)odom]
      • base_frame [default: $(arg prefix)base_footprint]
      • odom_model_type [default: diff]
  • launch/rl_utils.launch
  • launch/map_saver.launch
      • map_name [default: map]
      • map_topic [default: map]
      • destination_folder [default: $(optenv HOME /home/summit)]
  • launch/robot_localization_odom.launch
      • prefix [default: summit_xl_]
      • odom_frame [default: $(arg prefix)odom]
      • base_frame [default: $(arg prefix)base_footprint]
      • odom_topic [default: robotnik_base_control/odom]
      • imu_topic [default: imu/data]
  • launch/robot_localization_world.launch
      • prefix [default: summit_xl_]
      • global_frame [default: world_frame]

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged summit_xl_localization at answers.ros.org

No version for distro ardent. Known supported distros are highlighted in the buttons above.
No version for distro lunar. Known supported distros are highlighted in the buttons above.
No version for distro jade. Known supported distros are highlighted in the buttons above.

Package Summary

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

Repository Summary

Checkout URI https://github.com/RobotnikAutomation/summit_xl_common.git
VCS Type git
VCS Version indigo-devel
Last Updated 2017-10-06
Dev Status MAINTAINED
Released RELEASED

Package Description

The summit_xl_localization package

Additional Links

Maintainers

  • Elena Gambaro
  • Carlos Villar

Authors

No additional authors.
README
No README found. See repository README.
CHANGELOG

Changelog for package summit_xl_localization

1.0.10 (2016-09-01)

  • summit_xl_localization: commented robot_localization launch files
  • summit_xl_localization: updated robot_localization launch files
  • summit_xl_localization: added navsat_transform_new to CMakeLists.txt
  • 1.0.9
  • updated changelog
  • Contributors: Marc Bosch-Jorge, carlos3dx

1.0.9 (2016-08-24)

  • Adding install rules
  • Deleting unused files
  • Added rl_utils.launch
  • Contributors: Jorge Arino, summit

1.0.8 (2016-07-12)

1.0.7 (2016-07-12)

  • updated changelog
  • Contributors: carlos3dx

1.0.6 (2016-07-12)

1.0.5 (2016-07-05)

1.0.4 (2016-06-30)

  • added dependency
  • Contributors: carlos3dx

1.0.3 (2016-06-29)

1.0.2 (2016-06-28)

1.0.1 (2016-06-28)

  • indigo-1.0.0
  • added simple script to test magnetometer
  • Merge branch \'indigo-devel\' of https://github.com/RobotnikAutomation/summit_xl_common into indigo-devel Conflicts: summit_xl_localization/launch/navsat_transform_node.launch
  • configuration tested in Lisbon uploaded
  • summit_xl_localization: added dependency to robotnik_msgs
  • Topic name change
  • Minor changes
  • Update launch files. Add robot_localization_utils
  • Update robot_localization_odom.launch
  • Frame name change
  • Add local_tf node
  • Static tf update
  • Add launch files and the new navsat_transform node
  • First commit summit_xl_localization
  • Contributors: Elena Gambaro, ElenaFG, Jorge Arino, mcantero, rguzman
  • added simple script to test magnetometer
  • Merge branch \'indigo-devel\' of https://github.com/RobotnikAutomation/summit_xl_common into indigo-devel Conflicts: summit_xl_localization/launch/navsat_transform_node.launch
  • configuration tested in Lisbon uploaded
  • summit_xl_localization: added dependency to robotnik_msgs
  • Topic name change
  • Minor changes
  • Update launch files. Add robot_localization_utils
  • Update robot_localization_odom.launch
  • Frame name change
  • Add local_tf node
  • Static tf update
  • Add launch files and the new navsat_transform node
  • First commit summit_xl_localization
  • Contributors: Elena Gambaro, ElenaFG, Jorge Arino, rguzman

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Launch files

  • launch/navsat_transform_node.launch
    • This comes from the navsat_transform_template.launch. Explains what this node does. This node needs to know the values of three variables in order to function: (1) A world-referenced heading (yaw). The node assumes an ENU standard for heading, with 0 facing east, though it can support any heading. (2) Odometry data that gives the robot's current pose in its own local coordinate frame (typically map or odom) (3) A latitude/longitude/altitude. These three items allow us to compute a transform from the global frame to your robot's local frame. There are several means of providing them, though keep in mind that these modes are typically mutually exclusive. (1) World-referenced yaw can be provided by: (a) an IMU in a sensor_msgs/Imu message (topic is /imu/data/) (b) the heading in the nav_msgs/Odometry message in (2) below can be used. To enable this behavior, set the use_odometry_yaw parameter to true, and set the delay parameter to some small value (~3 seconds). Be careful, though: this heading must still be globally referenced, so if your state estimation node always starts with a 0 heading, you CAN NOT use this option. (c) the "datum" service. See below. (2) The odometry data, which needs to have a valid frame_id, can be provided by: (a) a nav_msgs/Odometry message from your robot_localization state estimation node. (b) the "datum" service (all odometry variables are assumed to be 0 in this case). See below. (3) The latitude, longitude, and altitude can be provided by: (a) a sensor_msgs/NavSatFix message (b) the "datum" service (4) Alternatively, at any time, the user can send a robot_localization/SetDatum service message to the "datum" service. This will manually set the latitude, longitude, altitude, and world-referenced heading, and will assume an odometry message containing all zeros. This will effectively set the origin at the specified lat-long, with the X-axis aligned with east. The user can set this datum via the "datum" service, or via the launch file. If the wait_for_datum parameter is set to true, then the node will attempt to use the datum parameter. If the parameter is not set, it will wait until it receives a service call. The output of this node is an odometry message that contains the GPS data transformed into the robot's world coordinate frame (i.e., the frame specified by input (2)'s frame_id), or the coordinate frame defined by the message sent to the "datum" service.
      • wait_for_datum [default: false]
  • launch/robot_localization_complete.launch
      • debug [default: false]
      • gui [default: true]
      • wait_for_datum [default: false]
  • launch/rl_utils.launch
  • launch/robot_localization_odom.launch
  • launch/robot_localization_world.launch

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged summit_xl_localization at answers.ros.org

Package Summary

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

Repository Summary

Checkout URI https://github.com/RobotnikAutomation/summit_xl_common.git
VCS Type git
VCS Version hydro-devel
Last Updated 2016-02-09
Dev Status MAINTAINED
Released UNRELEASED

Package Description

The summit_xl_localization package

Additional Links

No additional links.

Maintainers

  • Elena Gambaro

Authors

No additional authors.
README
No README found. See repository README.
CHANGELOG
No CHANGELOG found.

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Launch files

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged summit_xl_localization at answers.ros.org