All Projects → ros-industrial → staubli

ros-industrial / staubli

Licence: Apache-2.0 license
ROS-Industrial Staubli support (http://wiki.ros.org/staubli)

Programming Languages

C++
36643 projects - #6 most used programming language
CMake
9771 projects

Projects that are alternatives of or similar to staubli

kuka
ROS-Industrial KUKA support (http://wiki.ros.org/kuka)
Stars: ✭ 23 (+53.33%)
Mutual labels:  driver, moveit, urdf, ros-industrial
motoman project
Repository for Motoman ROS applications
Stars: ✭ 50 (+233.33%)
Mutual labels:  moveit, ros-industrial
arm
Robot arm simulation using Gazebo, ROS Control and MoveIt.
Stars: ✭ 79 (+426.67%)
Mutual labels:  moveit, urdf
abb robot driver
The new ROS driver for ABB robots
Stars: ✭ 55 (+266.67%)
Mutual labels:  driver, ros-industrial
faunadb-csharp
C# driver for FaunaDB
Stars: ✭ 55 (+266.67%)
Mutual labels:  driver
keithley2600
Python driver for Keithley 2600 series instruments.
Stars: ✭ 26 (+73.33%)
Mutual labels:  driver
node-drivers
Industrial protocol drivers in node.js
Stars: ✭ 20 (+33.33%)
Mutual labels:  driver
stm32f7-qspi
QSPI serial flash driver for the STM32F7xx family of controllers
Stars: ✭ 14 (-6.67%)
Mutual labels:  driver
Apex-Legends-SDK
Open Source Cheat for Apex Legends, designed for ease of use. Made to understand reversing of Apex Legends and respawn's modified source engine as well as their Easy Anti Cheat Implementation.
Stars: ✭ 101 (+573.33%)
Mutual labels:  driver
laravel-db2
laravel-db2 is a simple DB2 service provider for Laravel. It provides DB2 Connection by extending the Illuminate Database component of the laravel framework.
Stars: ✭ 56 (+273.33%)
Mutual labels:  driver
idyntree
Multibody Dynamics Library designed for Free Floating Robots
Stars: ✭ 109 (+626.67%)
Mutual labels:  urdf
r-exasol
The EXASOL package for R provides an interface to the EXASOL database.
Stars: ✭ 22 (+46.67%)
Mutual labels:  driver
libusb-win32
libusb-win32 project official github repo
Stars: ✭ 44 (+193.33%)
Mutual labels:  driver
eruption
Realtime RGB LED Driver for Linux
Stars: ✭ 140 (+833.33%)
Mutual labels:  driver
tahoe-lafs-public-clouds
tahoe-lafs backend drivers for no-cost cloud providers
Stars: ✭ 25 (+66.67%)
Mutual labels:  driver
rtl8822bu
RTL8822BU Wireless Driver for Linux
Stars: ✭ 59 (+293.33%)
Mutual labels:  driver
goroslib
ROS client library for the Go programming language
Stars: ✭ 226 (+1406.67%)
Mutual labels:  ros-industrial
mobius-gui
🎨 Reactive & Stream & Driver based UI framework build on Mobius Utils, equipped with neumorphism-derived & utility-first styles.
Stars: ✭ 43 (+186.67%)
Mutual labels:  driver
RobotCreator
FreeCAD Workbench for URDF & SDF and Gazebo
Stars: ✭ 43 (+186.67%)
Mutual labels:  urdf
BetterJoyForDolphin
Allows the Nintendo Switch Pro Controller and Joycons to be used with the Dolphin Emulator
Stars: ✭ 44 (+193.33%)
Mutual labels:  driver

Staubli

Build Status: Ubuntu Bionic (Actions) Build Status: Ubuntu Focal (Actions) Github Issues

license - apache 2.0

support level: community

ROS-Industrial Staubli meta-package. See the ROS wiki page for more information.

The staubli_experimental repository contains additional packages.

Contents

Branch naming follows the ROS distribution they are compatible with. -devel branches may be unstable. Releases are made from distribution branches (hydro, indigo, kinetic).

Building

On newer (or older) versions of ROS

Building the packages on newer (or older) versions of ROS is in most cases possible and supported. For example: building the packages in this repository on Ubuntu Xenial/ROS Kinetic or Ubuntu Bionic/ROS Melodic systems is supported. This will require creating a Catkin workspace, cloning this repository, installing all required dependencies and finally building the workspace.

Catkin tools

It is recommended to use catkin_tools instead of the default catkin when building ROS workspaces. catkin_tools provides a number of benefits over regular catkin_make and will be used in the instructions below. All packages can be built using catkin_make however: use catkin_make in place of catkin build where appropriate.

Building the packages

The following instructions assume that a Catkin workspace has been created at $HOME/catkin_ws and that the source space is at $HOME/catkin_ws/src. Update paths appropriately if they are different on the build machine.

These instructions build the indigo-devel branch on a ROS Kinetic system:

# change to the root of the Catkin workspace
$ cd $HOME/catkin_ws

# retrieve the latest development version of staubli.
$ git clone -b indigo-devel https://github.com/ros-industrial/staubli.git src/staubli

# check build dependencies. Note: this may install additional packages,
# depending on the software installed on the machine
$ rosdep update

# be sure to change 'kinetic' to whichever ROS release you are using
$ rosdep install --from-paths src/ --ignore-src --rosdistro kinetic

# build the workspace (using catkin_tools)
$ catkin build

Activating the workspace

Finally, activate the workspace to get access to the packages just built:

$ source $HOME/catkin_ws/devel/setup.bash

At this point all packages should be usable (ie: roslaunch should be able to auto-complete package names starting with staubli_..). In case the workspace contains additional packages (ie: not from this repository), those should also still be available.

Installation and usage

Refer to Working With ROS-Industrial Robot Support Packages for information on how to use the files provided by the robot support and MoveIt configuration packages. See also the other pages on the ROS wiki.

Disclaimer

The author(s) of these packages is (are) not affiliated with Stäubli International AG in any way. All trademarks and registered trademarks are property of their respective owners, and company, product and service names mentioned in this readme or appearing in source code or other artefacts in this repository are used for identification purposes only. Use of these names does not imply endorsement by Stäubli International AG.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].