eeros_architecture:hal:config_ros
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| eeros_architecture:hal:config_ros [2023/02/27 14:43] – ursgraf | eeros_architecture:hal:config_ros [2023/02/27 14:44] (current) – [Configuration File for ROS] ursgraf | ||
|---|---|---|---|
| Line 4: | Line 4: | ||
| The EEROS HAL digital and analog inputs and outputs can be defined as usual in a JSON file. In this file you specify into which message type these signals get packed. There are hundreds of different message types in ROS and it is possible to create custom types. For this reason, we currently support only a few by default. If one wishes to use other message types, the wrapper library can easily be extended. | The EEROS HAL digital and analog inputs and outputs can be defined as usual in a JSON file. In this file you specify into which message type these signals get packed. There are hundreds of different message types in ROS and it is possible to create custom types. For this reason, we currently support only a few by default. If one wishes to use other message types, the wrapper library can easily be extended. | ||
| - | WARNING The naming of messages changes from ROS1 to ROS2, e.g. | + | WARNING |
| - | ROS1: std_msgs:: | + | The naming of messages changes from ROS1 to ROS2, e.g. |
| - | ROS2: std_msgs:: | + | |
| + | | ||
| + | The information below is for ROS1. Change accordingly for ROS2. | ||
| The keywords for the EEROS-ROS wrapper library must be set as follows: | The keywords for the EEROS-ROS wrapper library must be set as follows: | ||
eeros_architecture/hal/config_ros.1677505397.txt.gz · Last modified: 2023/02/27 14:43 by ursgraf