User Tools

Site Tools


getting_started:ros

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
getting_started:ros [2021/03/29 15:53] – [Example for Making your EEROS Application a ROS Node] ursgrafgetting_started:ros [2023/02/09 12:04] (current) – [Interfacing with ROS] ursgraf
Line 1: Line 1:
 ====== Interfacing with ROS ====== ====== Interfacing with ROS ======
-[[http://www.ros.org/|ROS]] is a flexible framework for writing robot software. It is great collection of tools, libraries, and conventions. +[[http://www.ros.org/|ROS]] is a flexible framework for writing robot software. It is great collection of tools, libraries, and conventions. EEROS supports the use of ROS1 or ROS2.
  
   * [[getting_started:ros_prep|]]   * [[getting_started:ros_prep|]]
 +  * [[getting_started:ros_timing|]]
   * [[getting_started:ros_example|]]   * [[getting_started:ros_example|]]
 +  * [[getting_started:ros_run|]]
  
 You can make use of ROS within EEROS in the following two ways. You can make use of ROS within EEROS in the following two ways.
Line 22: Line 24:
  
  
-===== Running your Application ===== 
-An EEROS application using ROS needs to be started with super user privileges. Further,  
-ROS needs some system variables, like ''ROS_MASTER_URI'', which are defined by the ''setup.bash'' script of ROS. 
-To forward these variables to the super user process, the option //-E// has to be used.  
-<code> 
-$ sudo -E ./application 
-</code> 
  
getting_started/ros.1617026008.txt.gz · Last modified: 2021/03/29 15:53 by ursgraf