- Jan 15, 2019
-
-
Marcel Schnirring authored
-
- Oct 15, 2018
-
-
gavanderhoorn authored
-
- Aug 21, 2018
-
-
Dave Niewinski authored
-
- Jul 29, 2018
-
-
Felix von Drigalski authored
Squashed commits: * Fix overlapping properties between robot definitions Uploading a different UR definition used to break the previous definition files by overwriting their link lengths. This commit makes the property names for each robot unique so they are independent of the other robot models. * Move robot-specific parameters inside macro This is the cleaner solution for what the previous commit was meant to solve
-
- Jul 12, 2018
-
-
MonteroJJ authored
-
- Jul 11, 2018
-
-
Joe authored
related to issue 'Improve meshes shading #233'. Visual meshes smoothed with 'split edge' function in blender.
-
- Feb 16, 2018
-
-
Harsh Deshpande authored
-
- Feb 15, 2018
-
-
Harsh Deshpande authored
add doc strings to all launch file args.
-
- Jan 07, 2018
-
-
ipa-fxm authored
- Dec 18, 2017
-
-
Dave Coleman authored
-
- Nov 21, 2017
-
-
Miguel Prada authored
-
- Nov 20, 2017
-
-
Miguel Prada authored
Joint limits for the limited version could be set using arguments for the UR10 but not for the UR3 and UR5. Same lower and upper limit arguments are added to the UR3 and UR5 xacro macros.
-
- Sep 13, 2017
-
-
Beatriz Leon authored
-
Dave Coleman authored
-
- Aug 04, 2017
-
-
ipa-fxm authored
- Jan 03, 2017
-
-
gavanderhoorn authored
-
gavanderhoorn authored
-
gavanderhoorn authored
Micro-revert of #251. If dependent xacros include the ur* urdfs, but don't use Jade+ xacro, 'pi' will be undefined otherwise.
-
gavanderhoorn authored
-
- Dec 30, 2016
-
-
gavanderhoorn authored
-
gavanderhoorn authored
-
gavanderhoorn authored
-
gavanderhoorn authored
-
gavanderhoorn authored
-
- Jun 30, 2016
-
-
Dave Coleman authored
-
- Jun 15, 2016
-
-
philip 14.04 authored
-
- Jun 08, 2016
-
-
philip 14.04 authored
-
- Apr 02, 2016
-
-
ipa-fxm authored
- Aug 01, 2015
- Jun 21, 2015
-
-
ipa-fxm authored
-
- Jun 15, 2015
- May 06, 2015
-
-
gavanderhoorn authored
This is more in-line with naming of existing joint tags.
-
- Apr 22, 2015
-
-
gavanderhoorn authored
Note that 'base' is essentially 'base_link' but rotated by 180 degrees over the Z-axis. This is necessary as the visual and collision geometries appear to also have their origins rotated 180 degrees wrt the real robot. 'tool0' is similar to 'ee_link', but with its orientation such that it coincides with an all-zeros TCP setting on the UR controller. Users are expected to attach their own TCP frames to this frame, instead of updating it (see also [1]). [1] http://wiki.ros.org/Industrial/Tutorials/WorkingWithRosIndustrialRobotSupportPackages#Standardised_links_.2BAC8_frames
-
gavanderhoorn authored
-