neobotix/neo_mp_400-2

Issues

• add opaquefunction to access the launch arguments as strings for further processing

  #8 opened 3 months ago by padhupradheep
  1

• pipe error codes

  #11 opened 3 months ago by padhupradheep
  1

• add IMU support

  #15 opened 3 months ago by padhupradheep
  1

• add mobile manipulator support

  #17 opened 2 years ago by padhupradheep
  1

• Add information regarding the launch arguments

  #28 opened 3 months ago by padhupradheep
  1

• docking navigation should be made optional

  #31 opened 3 months ago by padhupradheep
  0

• test and add neo_docking2 package

  #13 opened 7 months ago by padhupradheep
  0

• add docking_navigation.launch

  #20 opened 7 months ago by padhupradheep
  0

• missing namespacing support

  #22 opened 7 months ago by padhupradheep
  0

• Use macros in yaml to use the same config files for multi robot systems

  #30 opened a year ago by padhupradheep
  0

• No need to give absolute paths for the behavior tree file

  #29 opened a year ago by padhupradheep
  0

• robot start to move after restarting ROS

  #24 opened a year ago by padhupradheep
  0

• add missing test rviz

  #19 opened 2 years ago by padhupradheep
  0

• add dependencies to the package.xml

  #16 opened 2 years ago by padhupradheep
  0

• update mapping params

  #9 opened 2 years ago by padhupradheep
  1

• odom blockage

  #10 opened 2 years ago by padhupradheep
  1

• add high speed navigation paramters

  #12 opened 2 years ago by padhupradheep
  0

• support humble

  #5 opened 2 years ago by padhupradheep
  1

• multi robot support

  #7 opened 2 years ago by padhupradheep
  0

• Add neo_localization2

  #2 opened 2 years ago by padhupradheep
  0

• migrate to neo_bringup

  #4 opened 2 years ago by padhupradheep
  0

• Serve multiple distros

  #1 opened 2 years ago by padhupradheep
  0

• Add an option to include custom Behavior node

  #3 opened 2 years ago by padhupradheep
  1