eeros_architecture:hal:config_ros
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revisionNext revisionBoth sides next revision | ||
eeros_architecture:hal:config_ros [2017/11/30 19:39] – created graf | eeros_architecture:hal:config_ros [2017/12/14 18:35] – [How to Use the] graf | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Configuration File for ROS ====== | ====== Configuration File for ROS ====== | ||
+ | |||
+ | As described in [[getting_started: | ||
+ | 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 keywords for the EEROS-ROS wrapper library must be set as follows: | ||
+ | ^ Keyword ^ Type ^ Remarks ^ | ||
+ | | library | string | libroseeros.so (include version e.g. *.so.0.1.2) | | ||
+ | | devHandle | string | e.g. testNodeHAL, | ||
+ | | type | string | e.g. AnalogIn / AnalogOut / DigIn / DigOut | | ||
+ | | additionalArguments | string | see table below | | ||
+ | |||
+ | ===== Additional Arguments ===== | ||
+ | The '' | ||
+ | |||
+ | ^ Keyword ^ Type ^ Remarks ^ | ||
+ | | topic | string | topic to listen or subscribe | | ||
+ | | msgType | string | message type | | ||
+ | | dataField | string | data member of message | | ||
+ | | callOne | boolean | ???? | | ||
+ | | queueSize | int | size of buffer, default = 1000 | | ||
+ | | useEerosSystemTime | boolean | use system time or timestamp of message | | ||
+ | |||
+ | An example for an additional argument could be: | ||
+ | < | ||
+ | " | ||
+ | </ | ||
+ | |||
+ | ===== Implemented Message Types ===== | ||
+ | The table below shows all currently implemented message types and associated data fields. If your desired message type is not implemented yet, you can easily implement it yourself, see below. | ||
+ | |||
+ | ^ type ^ msgType ^ dataField ^ | ||
+ | | AnalogIn | std_msgs:: | ||
+ | | ::: | sensor_msgs:: | ||
+ | | ::: | ::: | angle_max | | ||
+ | | ::: | ::: | angle_increment | | ||
+ | | ::: | ::: | time_increment | | ||
+ | | ::: | ::: | scan_time | | ||
+ | | ::: | ::: | range_min | | ||
+ | | ::: | ::: | range_max | | ||
+ | | AnalogOut | std_msgs:: | ||
+ | | ::: | sensor_msgs:: | ||
+ | | ::: | ::: | angle_max | | ||
+ | | ::: | ::: | angle_increment | | ||
+ | | ::: | ::: | time_increment | | ||
+ | | ::: | ::: | scan_time | | ||
+ | | ::: | ::: | range_min | | ||
+ | | ::: | ::: | range_max | | ||
+ | | DigIn | std_msgs:: | ||
+ | | DigOut | std_msgs:: | ||
+ | |||
+ | You can find a complete example, including a *.json file, in the [[getting_started: | ||
+ | |||
eeros_architecture/hal/config_ros.txt · Last modified: 2023/02/27 14:44 by ursgraf