├── .github └── workflows │ ├── ci_bionic.yml │ └── ci_focal.yml ├── .gitignore ├── CONTRIBUTING.md ├── LICENSE ├── README.md └── abb_experimental ├── CMakeLists.txt └── package.xml /.github/workflows/ci_bionic.yml: -------------------------------------------------------------------------------- 1 | name: CI - Ubuntu Bionic 2 | 3 | on: 4 | # direct pushes to protected branches are not supported 5 | pull_request: 6 | # run every day, at 8am UTC 7 | schedule: 8 | - cron: '0 8 * * *' 9 | # allow manually starting this workflow 10 | workflow_dispatch: 11 | 12 | jobs: 13 | industrial_ci: 14 | name: ROS Melodic (${{ matrix.ros_repo }}) 15 | runs-on: ubuntu-20.04 16 | 17 | strategy: 18 | fail-fast: false 19 | matrix: 20 | ros_distro: [ melodic ] 21 | ros_repo: [ main, testing ] 22 | 23 | env: 24 | CCACHE_DIR: "${{ github.workspace }}/.ccache" 25 | UPSTREAM_WORKSPACE: 'github:ros-industrial/abb#kinetic-devel' 26 | 27 | steps: 28 | - name: Fetch repository 29 | uses: actions/checkout@v3 30 | 31 | - name: ccache cache 32 | uses: actions/cache@v3 33 | with: 34 | path: ${{ env.CCACHE_DIR }} 35 | # we always want the ccache cache to be persisted, as we cannot easily 36 | # determine whether dependencies have changed, and ccache will manage 37 | # updating the cache for us. Adding 'run_id' to the key will force an 38 | # upload at the end of the job. 39 | key: ccache-${{ matrix.ros_distro }}-${{ matrix.ros_repo }}-${{github.run_id}} 40 | restore-keys: | 41 | ccache-${{ matrix.ros_distro }}-${{ matrix.ros_repo }} 42 | 43 | - name: Run industrial_ci 44 | uses: ros-industrial/industrial_ci@master 45 | env: 46 | ROS_DISTRO: ${{ matrix.ros_distro }} 47 | ROS_REPO: ${{ matrix.ros_repo }} 48 | -------------------------------------------------------------------------------- /.github/workflows/ci_focal.yml: -------------------------------------------------------------------------------- 1 | name: CI - Ubuntu Focal 2 | 3 | on: 4 | # direct pushes to protected branches are not supported 5 | pull_request: 6 | # run every day, at 8am UTC 7 | schedule: 8 | - cron: '0 8 * * *' 9 | # allow manually starting this workflow 10 | workflow_dispatch: 11 | 12 | jobs: 13 | industrial_ci: 14 | name: ROS Noetic (${{ matrix.ros_repo }}) 15 | runs-on: ubuntu-20.04 16 | 17 | strategy: 18 | fail-fast: false 19 | matrix: 20 | ros_distro: [ noetic ] 21 | ros_repo: [ main, testing ] 22 | 23 | env: 24 | CCACHE_DIR: "${{ github.workspace }}/.ccache" 25 | # using both abb as well as abb_driver from source as: 26 | # 27 | # - experimental repositories may always depend on unreleased changes 28 | # in the non-experimental repository, and 29 | # - industrial_core has recently been updated and only melodic-devel of 30 | # abb_driver is compatible with those changes 31 | # 32 | UPSTREAM_WORKSPACE: 'github:ros-industrial/abb#kinetic-devel github:ros-industrial/abb_driver#melodic-devel' 33 | 34 | steps: 35 | - name: Fetch repository 36 | uses: actions/checkout@v3 37 | 38 | - name: ccache cache 39 | uses: actions/cache@v3 40 | with: 41 | path: ${{ env.CCACHE_DIR }} 42 | # we always want the ccache cache to be persisted, as we cannot easily 43 | # determine whether dependencies have changed, and ccache will manage 44 | # updating the cache for us. Adding 'run_id' to the key will force an 45 | # upload at the end of the job. 46 | key: ccache-${{ matrix.ros_distro }}-${{ matrix.ros_repo }}-${{github.run_id}} 47 | restore-keys: | 48 | ccache-${{ matrix.ros_distro }}-${{ matrix.ros_repo }} 49 | 50 | - name: Run industrial_ci 51 | uses: ros-industrial/industrial_ci@master 52 | env: 53 | ROS_DISTRO: ${{ matrix.ros_distro }} 54 | ROS_REPO: ${{ matrix.ros_repo }} 55 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | # Compiled Object files 2 | *.slo 3 | *.lo 4 | *.o 5 | 6 | # Compiled Dynamic libraries 7 | *.so 8 | *.dylib 9 | 10 | # Compiled Static libraries 11 | *.lai 12 | *.la 13 | *.a 14 | 15 | # Temp files 16 | *~ 17 | *.autosave 18 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | ROS-Industrial is a community project. We welcome contributions from any source, from those who are extremely active to casual users. The following sections outline the steps on how to contribute to ROS-Industrial. It assumes there is an existing repository to which one would like to contribute (item 1 in the figure above) and one is familiar with the Git "Fork and Branch" workflow, detailed [here](http://blog.scottlowe.org/2015/01/27/using-fork-branch-git-workflow/). 2 | 3 | 1. Before any development is undertaken, a contributor would communicate a need and/or issue to the ROS-Industrial community. This can be done by submitting an issue on the appropriate GitHub repo, the [issues repo](https://github.com/ros-industrial/ros_industrial_issues), or by posting a message in the [ROS-Industrial category on ROS Discourse](//swri-ros-pkg-dev@googlegroups.com). . Doing so may save you time if similar development is underway and ensure that whatever approach you take is acceptable to the community of reviewers once it is submitted. 4 | 2. The second step (item 2) is to implement your change. If you are working on a code contribution, we highly recommend you utilize the [ROS Qt-Creator Plug-in](http://rosindustrial.org/news/2016/6/9/ros-qt-ide-plugin). Verify that your change successfully builds and passes all tests. 5 | 3. Next, push your changes to a "feature" branch in your personal fork of the repo and issue a pull request (PR)(item 3). The PR allows maintainers to review the submitted code. Before the PR can be accepted, the maintainer and contributor must agree that the contribution is implemented appropriately. This process can take several back-and-forth steps (see [example](https://github.com/ros-industrial/motoman/pull/89)). Contributors should expect to spend as much time reviewing/changing the code as on the initial implementation. This time can be minimized by communicating with the ROS-Industrial community before any contribution is made. 6 | 4. Issuing a Pull Request (PR) triggers the [Travis Continuous Integrations (CI)](https://github.com/ros-industrial/industrial_ci) step (item 4) which happens automatically in the background. The Travis CI performs several operations, and if any of the steps below fail, then the PR is marked accordingly for the maintainer. 7 | * Travis Workflow: 8 | * Installs a barebones ROS distribution on a fresh Ubuntu virtual machine. 9 | * Creates a catkin workspace and puts the repository in it. 10 | * Uses wstool to check out any from-source dependencies (i.e. other repositories). 11 | * Resolves package dependencies using rosdep (i.e. install packages using apt-get). 12 | * Compiles the catkin workspace. 13 | * Runs all available unit tests. 14 | 5. If the PR passes Travis CI and one of the maintainers is satisfied with the changes, they post a +1 as a comment on the PR (item 5). The +1 signifies that the PR is ready to be merged. All PRs require at least one +1 and pass Travis CI before it can be merged. 15 | 6. The next step (item 6) is for the PR to be merged into the main branch. This is done through the GitHub web interface by selecting the “Merge pull request” button. After the PR is merged, all status badges are updated automatically. 16 | 7. Periodically, the maintainer will release the package (item 7), which then gets sent to the [ROS Build Farm](http://wiki.ros.org/build.ros.org) for Debian creation. 17 | 8. The publishing of the released packages (item 8) is managed by OSRF and is not on a set schedule. This usually happens when all packages for a given distro are built successfully and stable. The current status for the distro kinetic can be found [here](http://repositories.ros.org/status_page/ros_kinetic_default.html) . Navigating to other distros can be done by changing the distro name in the link. 18 | 9. Once the package has been published, it is available to be installed by the developer (item 9). 19 | 10. After the install of a new version, the developer may have questions, experience issues or it may not have the necessary functionality which should all be reported on the packages GitHub repository as an issue (item 10). If an issue is identified or there is missing functionality that the developer requires, the cycle starts back at (item 2). 20 | 21 | For more details, please refer to the [ROS-I wiki](http://wiki.ros.org/Industrial/DevProcess). 22 | 23 | ## Licensing 24 | Any contribution that you make to this repository will 25 | be under the Apache 2 License, as dictated by that 26 | [license](http://www.apache.org/licenses/LICENSE-2.0.html): 27 | 28 | ~~~ 29 | 5. Submission of Contributions. Unless You explicitly state otherwise, 30 | any Contribution intentionally submitted for inclusion in the Work 31 | by You to the Licensor shall be under the terms and conditions of 32 | this License, without any additional terms or conditions. 33 | Notwithstanding the above, nothing herein shall supersede or modify 34 | the terms of any separate license agreement you may have executed 35 | with Licensor regarding such Contributions. 36 | ~~~ 37 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Apache License 2 | Version 2.0, January 2004 3 | http://www.apache.org/licenses/ 4 | 5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 6 | 7 | 1. Definitions. 8 | 9 | "License" shall mean the terms and conditions for use, reproduction, and 10 | distribution as defined by Sections 1 through 9 of this document. 11 | 12 | "Licensor" shall mean the copyright owner or entity authorized by the copyright 13 | owner that is granting the License. 14 | 15 | "Legal Entity" shall mean the union of the acting entity and all other entities 16 | that control, are controlled by, or are under common control with that entity. 17 | For the purposes of this definition, "control" means (i) the power, direct or 18 | indirect, to cause the direction or management of such entity, whether by 19 | contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the 20 | outstanding shares, or (iii) beneficial ownership of such entity. 21 | 22 | "You" (or "Your") shall mean an individual or Legal Entity exercising 23 | permissions granted by this License. 24 | 25 | "Source" form shall mean the preferred form for making modifications, including 26 | but not limited to software source code, documentation source, and configuration 27 | files. 28 | 29 | "Object" form shall mean any form resulting from mechanical transformation or 30 | translation of a Source form, including but not limited to compiled object code, 31 | generated documentation, and conversions to other media types. 32 | 33 | "Work" shall mean the work of authorship, whether in Source or Object form, made 34 | available under the License, as indicated by a copyright notice that is included 35 | in or attached to the work (an example is provided in the Appendix below). 36 | 37 | "Derivative Works" shall mean any work, whether in Source or Object form, that 38 | is based on (or derived from) the Work and for which the editorial revisions, 39 | annotations, elaborations, or other modifications represent, as a whole, an 40 | original work of authorship. For the purposes of this License, Derivative Works 41 | shall not include works that remain separable from, or merely link (or bind by 42 | name) to the interfaces of, the Work and Derivative Works thereof. 43 | 44 | "Contribution" shall mean any work of authorship, including the original version 45 | of the Work and any modifications or additions to that Work or Derivative Works 46 | thereof, that is intentionally submitted to Licensor for inclusion in the Work 47 | by the copyright owner or by an individual or Legal Entity authorized to submit 48 | on behalf of the copyright owner. For the purposes of this definition, 49 | "submitted" means any form of electronic, verbal, or written communication sent 50 | to the Licensor or its representatives, including but not limited to 51 | communication on electronic mailing lists, source code control systems, and 52 | issue tracking systems that are managed by, or on behalf of, the Licensor for 53 | the purpose of discussing and improving the Work, but excluding communication 54 | that is conspicuously marked or otherwise designated in writing by the copyright 55 | owner as "Not a Contribution." 56 | 57 | "Contributor" shall mean Licensor and any individual or Legal Entity on behalf 58 | of whom a Contribution has been received by Licensor and subsequently 59 | incorporated within the Work. 60 | 61 | 2. Grant of Copyright License. 62 | 63 | Subject to the terms and conditions of this License, each Contributor hereby 64 | grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, 65 | irrevocable copyright license to reproduce, prepare Derivative Works of, 66 | publicly display, publicly perform, sublicense, and distribute the Work and such 67 | Derivative Works in Source or Object form. 68 | 69 | 3. Grant of Patent License. 70 | 71 | Subject to the terms and conditions of this License, each Contributor hereby 72 | grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, 73 | irrevocable (except as stated in this section) patent license to make, have 74 | made, use, offer to sell, sell, import, and otherwise transfer the Work, where 75 | such license applies only to those patent claims licensable by such Contributor 76 | that are necessarily infringed by their Contribution(s) alone or by combination 77 | of their Contribution(s) with the Work to which such Contribution(s) was 78 | submitted. If You institute patent litigation against any entity (including a 79 | cross-claim or counterclaim in a lawsuit) alleging that the Work or a 80 | Contribution incorporated within the Work constitutes direct or contributory 81 | patent infringement, then any patent licenses granted to You under this License 82 | for that Work shall terminate as of the date such litigation is filed. 83 | 84 | 4. Redistribution. 85 | 86 | You may reproduce and distribute copies of the Work or Derivative Works thereof 87 | in any medium, with or without modifications, and in Source or Object form, 88 | provided that You meet the following conditions: 89 | 90 | You must give any other recipients of the Work or Derivative Works a copy of 91 | this License; and 92 | You must cause any modified files to carry prominent notices stating that You 93 | changed the files; and 94 | You must retain, in the Source form of any Derivative Works that You distribute, 95 | all copyright, patent, trademark, and attribution notices from the Source form 96 | of the Work, excluding those notices that do not pertain to any part of the 97 | Derivative Works; and 98 | If the Work includes a "NOTICE" text file as part of its distribution, then any 99 | Derivative Works that You distribute must include a readable copy of the 100 | attribution notices contained within such NOTICE file, excluding those notices 101 | that do not pertain to any part of the Derivative Works, in at least one of the 102 | following places: within a NOTICE text file distributed as part of the 103 | Derivative Works; within the Source form or documentation, if provided along 104 | with the Derivative Works; or, within a display generated by the Derivative 105 | Works, if and wherever such third-party notices normally appear. The contents of 106 | the NOTICE file are for informational purposes only and do not modify the 107 | License. You may add Your own attribution notices within Derivative Works that 108 | You distribute, alongside or as an addendum to the NOTICE text from the Work, 109 | provided that such additional attribution notices cannot be construed as 110 | modifying the License. 111 | You may add Your own copyright statement to Your modifications and may provide 112 | additional or different license terms and conditions for use, reproduction, or 113 | distribution of Your modifications, or for any such Derivative Works as a whole, 114 | provided Your use, reproduction, and distribution of the Work otherwise complies 115 | with the conditions stated in this License. 116 | 117 | 5. Submission of Contributions. 118 | 119 | Unless You explicitly state otherwise, any Contribution intentionally submitted 120 | for inclusion in the Work by You to the Licensor shall be under the terms and 121 | conditions of this License, without any additional terms or conditions. 122 | Notwithstanding the above, nothing herein shall supersede or modify the terms of 123 | any separate license agreement you may have executed with Licensor regarding 124 | such Contributions. 125 | 126 | 6. Trademarks. 127 | 128 | This License does not grant permission to use the trade names, trademarks, 129 | service marks, or product names of the Licensor, except as required for 130 | reasonable and customary use in describing the origin of the Work and 131 | reproducing the content of the NOTICE file. 132 | 133 | 7. Disclaimer of Warranty. 134 | 135 | Unless required by applicable law or agreed to in writing, Licensor provides the 136 | Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, 137 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, 138 | including, without limitation, any warranties or conditions of TITLE, 139 | NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are 140 | solely responsible for determining the appropriateness of using or 141 | redistributing the Work and assume any risks associated with Your exercise of 142 | permissions under this License. 143 | 144 | 8. Limitation of Liability. 145 | 146 | In no event and under no legal theory, whether in tort (including negligence), 147 | contract, or otherwise, unless required by applicable law (such as deliberate 148 | and grossly negligent acts) or agreed to in writing, shall any Contributor be 149 | liable to You for damages, including any direct, indirect, special, incidental, 150 | or consequential damages of any character arising as a result of this License or 151 | out of the use or inability to use the Work (including but not limited to 152 | damages for loss of goodwill, work stoppage, computer failure or malfunction, or 153 | any and all other commercial damages or losses), even if such Contributor has 154 | been advised of the possibility of such damages. 155 | 156 | 9. Accepting Warranty or Additional Liability. 157 | 158 | While redistributing the Work or Derivative Works thereof, You may choose to 159 | offer, and charge a fee for, acceptance of support, warranty, indemnity, or 160 | other liability obligations and/or rights consistent with this License. However, 161 | in accepting such obligations, You may act only on Your own behalf and on Your 162 | sole responsibility, not on behalf of any other Contributor, and only if You 163 | agree to indemnify, defend, and hold each Contributor harmless for any liability 164 | incurred by, or claims asserted against, such Contributor by reason of your 165 | accepting any such warranty or additional liability. 166 | 167 | END OF TERMS AND CONDITIONS 168 | 169 | APPENDIX: How to apply the Apache License to your work 170 | 171 | To apply the Apache License to your work, attach the following boilerplate 172 | notice, with the fields enclosed by brackets "[]" replaced with your own 173 | identifying information. (Don't include the brackets!) The text should be 174 | enclosed in the appropriate comment syntax for the file format. We also 175 | recommend that a file or class name and description of purpose be included on 176 | the same "printed page" as the copyright notice for easier identification within 177 | third-party archives. 178 | 179 | Copyright [yyyy] [name of copyright owner] 180 | 181 | Licensed under the Apache License, Version 2.0 (the "License"); 182 | you may not use this file except in compliance with the License. 183 | You may obtain a copy of the License at 184 | 185 | http://www.apache.org/licenses/LICENSE-2.0 186 | 187 | Unless required by applicable law or agreed to in writing, software 188 | distributed under the License is distributed on an "AS IS" BASIS, 189 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 190 | See the License for the specific language governing permissions and 191 | limitations under the License. 192 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # ABB Experimental 2 | 3 | [![Build Status: Ubuntu Focal (Actions)](https://github.com/ros-industrial/abb_experimental/workflows/CI%20-%20Ubuntu%20Focal/badge.svg?branch=kinetic-devel)](https://github.com/ros-industrial/abb_experimental/actions?query=workflow%3A%22CI+-+Ubuntu+Focal%22) 4 | [![Github Issues](https://img.shields.io/github/issues/ros-industrial/abb_experimental.svg)](http://github.com/ros-industrial/abb_experimental/issues) 5 | 6 | [![license - apache 2.0](https://img.shields.io/:license-Apache%202.0-yellowgreen.svg)](https://opensource.org/licenses/Apache-2.0) 7 | [![license - bsd 3 clause](https://img.shields.io/:license-BSD%203--Clause-blue.svg)](https://opensource.org/licenses/BSD-3-Clause) 8 | 9 | [![support level: community](https://img.shields.io/badge/support%20level-community-lightgray.svg)](http://rosindustrial.org/news/2016/10/7/better-supporting-a-growing-ros-industrial-software-platform) 10 | 11 | [ROS-Industrial][] ABB experimental meta-package. See the [ROS wiki][] page for more information. 12 | 13 | 14 | ## Contents 15 | 16 | This repository contains packages that will be migrated to the [abb][] repository after they have received sufficient testing. 17 | The contents of these packages are subject to change, without prior notice. 18 | Any available APIs are to be considered unstable and are not guaranteed to be complete and / or functional. 19 | 20 | Branch naming follows the ROS distribution they are compatible with. `-devel` branches may be unstable. 21 | 22 | 23 | ## Naming Convention 24 | 25 | All robot support packages and MoveIt configurations follow the naming conventions as described in [REP-I0007][]. 26 | 27 | 28 | ## Installation 29 | 30 | As this repository contains experimental packages, no binary packages are available. 31 | 32 | Instead, follow the instructions to build them in a Catkin workspace shown in the next section. 33 | 34 | 35 | ## Building 36 | 37 | ### On newer (or older) versions of ROS 38 | 39 | 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. 40 | 41 | ### Catkin tools 42 | 43 | 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. 44 | 45 | ### Building the packages 46 | 47 | 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. 48 | 49 | These instructions build the `kinetic-devel` branch on a ROS Kinetic system: 50 | 51 | ```bash 52 | # change to the root of the Catkin workspace 53 | $ cd $HOME/catkin_ws 54 | 55 | # retrieve the latest development version of the abb repository. If you'd rather 56 | # use the latest released version, replace 'kinetic-devel' with 'kinetic' 57 | $ git clone -b kinetic-devel https://github.com/ros-industrial/abb.git src/abb 58 | # retrieve the latest development version of abb_experimental 59 | $ git clone -b kinetic-devel https://github.com/ros-industrial/abb_experimental.git src/abb_experimental 60 | 61 | # check build dependencies. Note: this may install additional packages, 62 | # depending on the software installed on the machine 63 | $ rosdep update 64 | 65 | # be sure to change 'kinetic' to whichever ROS release you are using 66 | $ rosdep install --from-paths src/ --ignore-src --rosdistro kinetic 67 | 68 | # build the workspace (using catkin_tools) 69 | $ catkin build 70 | ``` 71 | 72 | ### Activating the workspace 73 | 74 | Finally, activate the workspace to get access to the packages just built: 75 | 76 | ```bash 77 | $ source $HOME/catkin_ws/devel/setup.bash 78 | ``` 79 | 80 | At this point all packages should be usable (ie: `roslaunch` should be able to auto-complete package names starting with `abb_..`). In case the workspace contains additional packages (ie: not from this repository), those should also still be available. 81 | 82 | 83 | ## Installation and usage 84 | 85 | 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][]. 86 | 87 | Refer to the [tutorials][] for information on installation and configuration of the controller-specific software components. 88 | 89 | 90 | 91 | 92 | 93 | 94 | [ROS-Industrial]: http://wiki.ros.org/Industrial 95 | [ROS wiki]: http://wiki.ros.org/abb_experimental 96 | [abb]: https://github.com/ros-industrial/abb 97 | [REP-I0007]: https://github.com/ros-industrial/rep/blob/master/rep-I0007.rst 98 | [Catkin workspace]: http://wiki.ros.org/catkin/Tutorials/create_a_workspace 99 | [catkin]: http://wiki.ros.org/catkin 100 | [catkin_tools]: https://catkin-tools.readthedocs.io/en/latest 101 | [Working With ROS-Industrial Robot Support Packages]: http://wiki.ros.org/Industrial/Tutorials/WorkingWithRosIndustrialRobotSupportPackages 102 | [tutorials]: http://wiki.ros.org/abb/Tutorials 103 | -------------------------------------------------------------------------------- /abb_experimental/CMakeLists.txt: -------------------------------------------------------------------------------- 1 | cmake_minimum_required(VERSION 3.0.2) 2 | project(abb_experimental) 3 | find_package(catkin REQUIRED) 4 | catkin_metapackage() 5 | -------------------------------------------------------------------------------- /abb_experimental/package.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | abb_experimental 4 | 0.1.0 5 | Experimental packages for ABB manipulators within ROS-Industrial. 6 | Shaun Edwards 7 | Levi Armstrong (Southwest Research Institute) 8 | BSD 9 | 10 | http://wiki.ros.org/abb_experimental 11 | https://github.com/ros-industrial/abb_experimental/issues 12 | https://github.com/ros-industrial/abb_experimental 13 | 14 | catkin 15 | 16 | 17 | 18 | 19 | 20 | 21 | --------------------------------------------------------------------------------