ros2

Configuration guide

all parameters listed and their descriptions and defaults
configuration (tuning) guide [weights, amcl, dwb, heuristics]
Namespacing for server maps of plugins

Setup (like ROS1 wiki)

setup odom sources
setup TF
setup kinematics
setup sensor sources
setup footprint and reference https://github.com/ros-planning/navigatio

I installed ROS using instructions here - http://wiki.ros.org/Installation/Windows. Installation seemed to go fine.

I then tried to execute the instructions given here https://ms-iot.github.io/ROSOnWindows/Moveit/moveit_tutorials.html
The instructions failed at step git clone https://github.com/ms-iot/moveit_tutorials -b init_windows - apparently the link is invalid. Could you please fix the l

{
    "id": 1336,
    "title": "RVD#1336: CWE-78 (shell), This causes a new program to execute and is difficult to use safely (C... @ c/warehouse_connector.cpp:86",
    "type": "bug",
    "description": "This causes a new program to execute and is difficult to use safely (CWE-78). try using a library call that implements the same functionality if available. . Happening @ ...c/warehouse_con

First of all, I can confirm that the installation instructions for Android examples worked on my desktop.
Here's some details I found during the installation:

Pre-requirements: Python 3, python-vcstool, Gradle > 3.2 (e.g. here) and Android NDK are needed (r15 as stated in the instructions is OK). gradle -v should indicate

We could use this issue to have organized, the development and problem-solving guides.If someone develop some guide I could add to this first message to have more visibility.

Development Guides:

How to register a NuttX general driver in a STM32 board -> #3
How to develop a driver in NuttX -> #9
How to develop an App in Nuttx -> #12 .
How to use serial communication in NuttX -> #10

May be worth removing "OS1" across code naming. It appears that the OS0 and OS2 use the same interfaces and data formatting. There's no special changes needed for supporting all the sensors.

There's an open question on the 128 beam model. We need to think about how to support that, but first need code samples from Ouster themselves

Please excuse me if I submit this idea on the wrong place.

For a repository which is not yet to onboard with GitHub workflow, a list of templates will be shown to developers to help quickly onboard based on their project types. It could be useful for developers who is looking for a beginner CI/CD workflow for their projects.

And GitHub manages the list of templates here: https://github.com/a

Jun	JUL	Aug
	04
2019	2020	2021

ros2

Here are 254 public repositories matching this topic...

protontypes / awesome-robotic-tooling

eProsima / Fast-DDS

fkromer / awesome-ros2

ros-planning / navigation2

rdbox-intec / rdbox

AcutronicRobotics / gym-gazebo2

ros2-rust / ros2_rust

ms-iot / ROSOnWindows

AcutronicRobotics / ros2learn

RobotWebTools / rclnodejs

aliasrobotics / aztarna

aliasrobotics / RVD

irobot-ros / ros2-performance

chapulina / dolly

AcutronicRobotics / HRIM

AcutronicRobotics / MARA

ros2-java / ros2_java

youtalk / get-started-ros2

AcutronicRobotics / moveit2

clydemcqueen / tello_ros

atolab / zhe

micro-ROS / NuttX

Development Guides:

rsasaki0109 / lidarslam_ros2

DynoRobotics / UnityRos2

Adlink-ROS / adlink_ddsbot

IntelligentRoboticsLabs / ARViz

rsasaki0109 / kalman_filter_localization

clydemcqueen / flock2

SteveMacenski / ros2_ouster_drivers

ros-tooling / action-ros-ci

Improve this page

Add this topic to your repo