Interfacing with ROS
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.
You can make use of ROS within EEROS in the following two ways.
Using Publisher and Subscriber Blocks in the Control System
You can insert blocks into the control system which publish or subscribe a given type of ROS message.
Special blocks in EEROS take care of sending signals to and receiving signals from ROS. These signals must be packed into ROS messages. Each topic transmits messages of a certain type. Depending on the message type you have to use certain blocks in your control system, see Blocks for Interfacing with ROS
Using ROS through EEROS HAL
EEROS can communicate with the underlying hardware through its Hardware Abstraction Layer. When using this, you need a special wrapper library (see Hardware Libraries).
The EEROS HAL signals can be comprised of digital or analog inputs or outputs. They are specified in a JSON file.
If you want to test your application with a Gazebo simulation, you can define your inputs and outputs as ROS topics to connect your application with the simulation. For this no hardware is necessary. To use your application with hardware, you can use any of the available Hardware Libraries. By choosing the proper JSON file, you can easily switch between real hardware and simulation.
It is also possible to use ROS-topics alongside real hardware. You could determine a motor position by reading an encoder and set a control value for a motor. In parallel, you could publish the same values to ROS topics to visualize the state of the robot with rviz (if you have a model of your robot) or you could monitor the values with a ROS tool like rqt.