Difference between revisions of "ROS2"

Revision as of 14:53, 3 January 2019 (view source) Oleg (talk | contribs) (→‎ROS2 on PC) ← Older edit		Latest revision as of 15:00, 3 January 2019 (view source) Oleg (talk | contribs) (→‎News)
(2 intermediate revisions by the same user not shown)
Line 17:		Line 17:
	==<font color='blue'>Status</font>==		==<font color='blue'>Status</font>==
	Development		Development
		+	==<font color='blue'>News</font>==
		+	* [2019/01/03] Updated the cross-compiled version from '''ardent''' to '''bouncy'''. PC was already at '''bouncy''' because rclnodejs will work with '''bouncy''' only (not yet compatible with '''crystal''').
		+	Updated because ''bouncy'' would not 'see' ''ardent'' nodes & services and vice versa.
	==<font color='blue'>Interfaces</font>==		==<font color='blue'>Interfaces</font>==

---

Latest revision as of 15:00, 3 January 2019

About

Use ROS2 in Elphel single or multi-camera systems. The cameras are 10393 system boards based on Xilinx Zynq, ARM.

Goals

Notes:

• Controlling and initializing of multi-camera systems is already implemented using PHP API (autocampars.php), Python and lighttpd.
• Using ROS2 is intended to simplify/standardize the above.
• Using ROS2 is intended to make cameras compatible with other hardware supported by ROS1/2.

Having ROS2 cross-compiled and installed on each camera:

• Initialize cameras in a pre-defined multi-camera system - sync and sequence critical init
• Control multiple cameras from any camera of the system - parameters, recording
• Control multiple cameras from a PC (with ROS2 for PC installed).
• Control multiple cameras from a network device (w/o ROS2 installed, but with a browser) - by accessing a web server running on a camera interfaced with ROS2 of the camera. Can use nodejs or just lighttpd+php.

Status

Development

News

• [2019/01/03] Updated the cross-compiled version from ardent to bouncy. PC was already at bouncy because rclnodejs will work with bouncy only (not yet compatible with crystal).

Updated because bouncy would not 'see' ardent nodes & services and vice versa.

Interfaces

ROS2 nodes communicate over:

• 1 GigE LAN or (possibly) wifi (camera1-camera2..N, pc-camera1..N, pc1-pc2..M)
• within a single device

Notes:

• image sensors, IMS (or GPS & IMU), any other sensors are attached to cameras via a custom interface or USB, with appropriate driver support.
• normally cameras in the system are synced with a custom trigger cable - this is setup over network
• any device attached to PC?

ROS2 on Zynq

Installation

• For Embedded Linux (but not Ubuntu Distro) use meta-ros.git. What about meta-ros2?

TODO: Include meta-ros.git in elphel393 build system.

DONE: included a forked version okdzhimiev/meta-ros

Include meta-ros to elphel393

• Add path to bblayers.conf
• Add to "IMAGE_INSTALL_append" of core-image-elphel393.bb:

packagegroup-ros2-world \

Notes

• Cross-compilation for ARM
• ROS2 for python populates /usr/lib/python3.5/site-packages/ so python scripts can live anywhere.
• For command line apps, like ros2 ..., if AMENT_PREFIX_PATH is not set then:

OSError: Environment variable 'AMENT_PREFIX_PATH' is not set or empty

• Useful commands (command line):

export AMENT_PREFIX_PATH=/usr

ros2 pkg list
ros2 node list
ros2 srv list
ros2 srv show std_srvs/Trigger
ros2 msg list
ros2 msg show std_msgs/String

Demos

talker-listener cpp

# terminal 1:
export AMENT_PREFIX_PATH=/usr
ros2 run demo_nodes_cpp talker

# terminal 2:
export AMENT_PREFIX_PATH=/usr
ros2 run demo_nodes_cpp listener

Workflow

• Use example recipes from meta-ros.git
• bitbake package-name, check output and logs in the poky build tree
• List package in core-image-elphel393.bb's IMAGE_INSTALL_append

TODO:

• Add target-scp and an example empty recipe

ROS2 on PC

Installation

• Google and follow the general instructions.

Notes

• Switched to installing from a fat archive
• Terminal setup:

source /path/setup.bash

Workflow

• Create a workspace
• Create some packages inside or clone - they have a vcs tool to clone all repos from a text file.
• Install colcon
• Then build with colcon
• New packages will not get installed anywhere. They live in their folders.
• To use a package:

source ~/ros2_ws/some-package/install/setup.bash
ros2 pkg list
then run anything in this terminal

• Python scripts can live anywhere - just run them from that sourced terminal

ROS2 in Docker

docker pull osrf/ros2:bouncy-desktop
docker run -i -t osrf/ros2:bouncy-desktop 
No network, no colcon, no ament...

ROS2 General Notes

Notes

• SROS is Secure ROS or something

Useful links

• ErleRobotics Tutorials on ROS2 - very useful

• Ament tutorial - build system for new packages
  • works and supported in meta-ros
  • will not work for PC because repo hashes moved on?

• Colcon tutorial - newest build system for new packages
  • works for PC, even in 16.04
  • not supported in meta-ros (as of 2018/12/07)
  • colcon docs

• About meta-ros and about meta-ros2 - are they merged?

Networking:

• ROS on DDS

... 
if you are concerned about latency, like for soft real-time, you can basically tune DDS to be just a UDP blaster. In another scenario you might need something that behaves like TCP, but needs to be more 
tolerant to long dropouts, and with DDS all of these things can be controlled by changing the QoS parameters.
...

• FastRTPS benchmarks
• FastRTPS max message size
• Good book about UDP?

ROS2 Services:

• Request-Response is done with service. Format srv
• STD-SRVS discussion & ROS2 examples(?)

Reference ROS repos

• inertial_sense_ros.git - cpp
• ros2_intel_realsense.git - cpp
• axis_camera.git - python
• meta-ros.git - layer for Yocto

ROS1

Won't build. More info.