getting_started:ros_run
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| getting_started:ros_run [2021/03/29 16:21] – [Running your Application on a Target] ursgraf | getting_started:ros_run [2026/04/21 16:48] (current) – ursgraf | ||
|---|---|---|---|
| Line 5: | Line 5: | ||
| ===== Running your Application on the Host ===== | ===== Running your Application on the Host ===== | ||
| - | If your EEROS-ROS node is on the host where you also run your ROS master is straightforward. You can use all your ROS tools as you do without using EEROS. | + | If your EEROS-ROS node is on the host where you also run your ROS master |
| + | Do not run your program with root privileges because the DDS layer of ROS might show discovery issues. Your program needs real-time privileges for the executor to change scheduling parameters, see | ||
| ===== Running your Application on a Target ===== | ===== Running your Application on a Target ===== | ||
| - | We strongly recommend to run your ROS master on the host. You will have enough computing power and you can use graphical utilities such as [[http:// | ||
| ==== Network Setup ==== | ==== Network Setup ==== | ||
| - | As your application on the target will register as a ROS node, it has to find your host computer. | + | As your application on the target will register as a ROS node, it has to find your host computer. |
| - | export ROS_MASTER_URI=http:// | + | |
| - | </ | + | |
| - | An EEROS application | + | ==== Running the Application ==== |
| - | ROS needs some system variables, like '' | + | Start your application as a regular |
| - | To forward these variables to the super user process, the option //-E// has to be used. | + | |
| - | < | + | |
| - | $ sudo -E ./ | + | |
| - | </ | + | |
| + | Use graphical utilities such as [[http:// | ||
getting_started/ros_run.1617027684.txt.gz · Last modified: by ursgraf
