User Tools

Site Tools


getting_started:install_wrapper

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:install_wrapper [2021/11/10 16:22] – [RealSense] ursgrafgetting_started:install_wrapper [2023/03/09 09:08] (current) – [ROS] ursgraf
Line 11: Line 11:
 <code> <code>
 $ cd sim-eeros $ cd sim-eeros
-$ git checkout v1.0.0</code>+$ git checkout v1.0.1</code>
  
 Continue with [[getting_started:compile_eeros_man|]]. Continue with [[getting_started:compile_eeros_man|]].
Line 24: Line 24:
 <code> <code>
 $ cd flink-eeros $ cd flink-eeros
-$ git checkout v1.0.0</code>+$ git checkout v1.0.10</code>
  
 Continue with [[getting_started:compile_eeros_man|]]. Continue with [[getting_started:compile_eeros_man|]].
Line 37: Line 37:
 <code> <code>
 $ cd bbblue-eeros $ cd bbblue-eeros
-$ git checkout v1.2.0</code>+$ git checkout v1.3.0</code>
  
 Continue with [[getting_started:compile_eeros_man|]]. Continue with [[getting_started:compile_eeros_man|]].
Line 55: Line 55:
 Continue with [[getting_started:compile_eeros_man|]]. Continue with [[getting_started:compile_eeros_man|]].
 ===== ROS ===== ===== ROS =====
-Follow the installation instructions in [[http://www.ros.org/]] to install ROS itself. \\+Follow the installation instructions in [[http://www.ros.org/]] to install ROS itself. We suggest using ROS2. However, you can also use ROS1.\\
 After this you have to clone the eeros ROS wrapper source repository: After this you have to clone the eeros ROS wrapper source repository:
 <code> <code>
Line 61: Line 61:
 </code> </code>
  
-Checkout a stable version of the wrapper:+Checkout a stable version of the wrapper. For ROS2, this is:
 <code> <code>
 $ cd ros-eeros $ cd ros-eeros
-$ git checkout v.1.0.0</code> +$ git checkout v.2.0.0</code> 
 +For ROS1, use the version v.1.0.1.\\
 Continue with [[getting_started:compile_eeros_man|]]. Continue with [[getting_started:compile_eeros_man|]].
 ===== EtherCAT ===== ===== EtherCAT =====
Line 76: Line 76:
 The detailed documentation about CANopen together with installation and setup information is given on [[https://gitlab.ost.ch/tech/inf/public/canopenlib]].  The detailed documentation about CANopen together with installation and setup information is given on [[https://gitlab.ost.ch/tech/inf/public/canopenlib]]. 
  
-Use the predefined CAN blocks within a control system, see [[eeros_architecture:control_system:available_blocks#blocks_for_interfacing_with_can|Blocks for Interfacing with CAN]]. Add -DUSE_CAN to the cmake arguments when building EEROS to include an example using CANopen.+Use the predefined CAN blocks within a control system, see [[eeros_architecture:control_system:available_blocks#blocks_for_interfacing_with_can|Blocks for Interfacing with CAN]]. Add ''-DUSE_CAN=TRUE'' to the cmake arguments when building EEROS to include an example using CANopen.
  
 ===== MODBUS ===== ===== MODBUS =====
 We use MODBUS for accessing sensor data. On Linux, use [[https://libmodbus.org/]] for information about installing the library. We use MODBUS for accessing sensor data. On Linux, use [[https://libmodbus.org/]] for information about installing the library.
-For the examples in EEROS which use MODBUS to be built, you have to add ''-DUSE_MODBUS'' to the cmake arguments when building EEROS.+For the examples in EEROS which use MODBUS to be built, you have to add ''-DUSE_MODBUS=TRUE'' to the cmake arguments when building EEROS.
  
 ===== PixyCam ===== ===== PixyCam =====
 When using the pixy camera (see [[eeros_architecture:control_system:available_blocks:pixycam2|]]), you have to fetch and install its necessary library. When using the pixy camera (see [[eeros_architecture:control_system:available_blocks:pixycam2|]]), you have to fetch and install its necessary library.
-Add ''-DUSE_PIXYCAM'' to the cmake arguments when building EEROS to include an example with PixyCam.+Add ''-DUSE_PIXYCAM=TRUE'' to the cmake arguments when building EEROS to include an example with PixyCam.
  
 ===== RealSense ===== ===== RealSense =====
 When using the RealSense camera (see [[eeros_architecture:control_system:available_blocks:realsenset256|]]), you have to fetch and install its necessary library. When using the RealSense camera (see [[eeros_architecture:control_system:available_blocks:realsenset256|]]), you have to fetch and install its necessary library.
-Add ''-DUSE_REALSENSE'' to the cmake arguments when building EEROS to include an example with RealSense T256.+Add ''-DUSE_REALSENSE=TRUE'' to the cmake arguments when building EEROS to include an example with RealSense T256.
  
 ===== RP Lidar ===== ===== RP Lidar =====
-When using a RPLidar (see [[eeros_architecture:control_system:available_blocks:rplidar|]], you have to fetch and install its necessary library. +When using a RPLidar (see [[eeros_architecture:control_system:available_blocks:rplidar|]]), you have to fetch and install its necessary library. 
-Add ''-DUSE_RPLIDAR'' to the cmake arguments when building EEROS to include an example with RPLidar sensor. This argument will also fetch a driver from the ''external'' directory within EEROS.+Add ''-DUSE_RPLIDAR=TRUE'' to the cmake arguments when building EEROS to include an example with RPLidar sensor. This argument will also fetch a driver from the ''external'' directory within EEROS.
  
 ===== SBG Ellipse-A ===== ===== SBG Ellipse-A =====
-When using a SBG Ellipse-A sensor (see [[eeros_architecture:control_system:available_blocks:sbgellipsea|]], you have to fetch and install its necessary library. +When using a SBG Ellipse-A sensor (see [[eeros_architecture:control_system:available_blocks:sbgellipsea|]]), you have to fetch and install its necessary library. 
-Add ''-DUSE_SBGECOMM'' to the cmake arguments when building EEROS to include an example with Ellipse-A sensor.+Add ''-DUSE_SBGECOMM=TRUE'' to the cmake arguments when building EEROS to include an example with Ellipse-A sensor.
  
 ===== ODrive ===== ===== ODrive =====
-When using ODrive motor controllers (see [[eeros_architecture:control_system:available_blocks:odrive|]], you need a library with the ''external/odrive'' directory of EEROS. Build this library and install it. +When using ODrive motor controllers (see [[eeros_architecture:control_system:available_blocks:odrive|]]), you need a library with the ''external/odrive'' directory of EEROS. Build this library and install it. 
-Add ''-DUSE_ODRIVE'' to the cmake arguments when building EEROS to include an example controlling an odrive.+Add ''-DUSE_ODRIVE=TRUE'' to the cmake arguments when building EEROS to include an example controlling an odrive.
getting_started/install_wrapper.1636557733.txt.gz · Last modified: 2021/11/10 16:22 by ursgraf