2014-01-29 12:44:33 -0500 | received badge | ● Famous Question
(source)
|
2013-11-22 02:14:20 -0500 | received badge | ● Famous Question
(source)
|
2013-10-21 21:18:34 -0500 | received badge | ● Notable Question
(source)
|
2013-10-21 21:18:34 -0500 | received badge | ● Popular Question
(source)
|
2013-10-08 01:39:40 -0500 | received badge | ● Notable Question
(source)
|
2013-09-30 07:09:06 -0500 | commented answer | collada files not visualized in Gazebo 1.9 Thanks a lot! It solved the problem. Did the interface between collada files and gazebo change somehow? |
2013-09-27 08:15:58 -0500 | received badge | ● Popular Question
(source)
|
2013-09-25 10:44:49 -0500 | asked a question | collada files not visualized in Gazebo 1.9 Hi all, I have a robot using (collada) .dae files for visualization. Before Gazebo 1.9 they worked just fine, but after updating to 1.9 they do not show up anymore. (previously I used the version which came with ROS-fuerte, don't know the actual version number..) Here are relevant parts of one of the files: <?xml version="1.0" encoding="utf-8"?>
<COLLADA version="1.4.0" xmlns="http://www.collada.org/2005/11/COLLADASchema">
<asset>
<contributor>
<author>Illusoft Collada 1.4.0 plugin for Blender - http://colladablender.illusoft.com</author>
<authoring_tool>Blender v:249 - Illusoft Collada Exporter v:0.3.162</authoring_tool>
<comments></comments>
<copyright></copyright>
</contributor>
<unit meter="0.01" name="centimeter"/>
<up_axis>Z_UP</up_axis>
</asset>
<library_effects>
<effect id="black-fx" name="black-fx">
<profile_COMMON>
<technique sid="blender">
<phong>
<emission>
<color>0.00000 0.00000 0.00000 1</color>
</emission>
<ambient>
<color>0.43854 0.43854 0.43854 1</color>
</ambient>
<diffuse>
<color>0.43854 0.43854 0.43854 1</color>
</diffuse>
<specular>
<color>0.25000 0.25000 0.25000 1</color>
</specular>
<shininess>
<float>1</float>
</shininess>
</phong>
</technique>
</profile_COMMON>
</effect>
</library_effects>
<library_materials>
<material id="black" name="black">
<instance_effect url="#black-fx"/>
</material>
</library_materials>
<library_geometries>
<geometry id="arm0-Geometry" name="arm0-Geometry">
<mesh>
<source id="arm0-Geometry-Position">
<float_array count="14850" id="arm0-Geometry-Position-array"> .... </float_array>
<technique_common>
<accessor count="4950" source="#arm0-Geometry-Position-array" stride="3">
<param type="float" name="X"></param>
<param type="float" name="Y"></param>
<param type="float" name="Z"></param>
</accessor>
</technique_common>
</source>
<source id="arm0-Geometry-Normals">
<float_array count="29985" id="arm0-Geometry-Normals-array">.....</float_array>
<technique_common>
<accessor count="9995" source="#arm0-Geometry-Normals-array" stride="3">
<param type="float" name="X"></param>
<param type="float" name="Y"></param>
<param type="float" name="Z"></param>
</accessor>
</technique_common>
</source>
<vertices id="arm0-Geometry-Vertex">
<input semantic="POSITION" source="#arm0-Geometry-Position"/>
</vertices>
<triangles count="9995" material="black">
<input offset="0" semantic="VERTEX" source="#arm0-Geometry-Vertex"/>
<input offset="1" semantic="NORMAL" source="#arm0-Geometry-Normals"/>
<p> ... </p>
</triangles>
</mesh>
</geometry>
</library_geometries>
<library_visual_scenes>
<visual_scene id="Scene" name="Scene">
<node layer="L1" id="arm0" name="arm0">
<translate sid="translate">0.00000 0.00000 0.00000</translate>
<rotate sid="rotateZ">0 0 1 0.00000</rotate>
<rotate sid="rotateY">0 1 0 -0.00000</rotate>
<rotate sid="rotateX">1 0 0 0.00000</rotate>
<scale sid="scale">1.00000 1.00000 1.00000</scale>
<instance_geometry url="#arm0-Geometry">
<bind_material>
<technique_common>
<instance_material symbol="black" target="#black">
<bind_vertex_input input_semantic="TEXCOORD" input_set="1" semantic="CHANNEL1"/>
</instance_material>
</technique_common>
</bind_material>
</instance_geometry>
</node>
</visual_scene>
</library_visual_scenes>
<scene>
<instance_visual_scene url="#Scene"/>
</scene>
</COLLADA>
|
2013-09-24 11:01:31 -0500 | received badge | ● Scholar
(source)
|
2013-09-24 11:01:14 -0500 | commented answer | Gazebo 1.9 fails to load URDF (which works in RVIZ and is validate by urdfdom) Ahh, ok so now the issue is located. Thank you. I have update and deleted ad now it actually works. Only issue is that my .dea files apparently not are valid anymore. When i use all the "*_convex.dea" files i can see the robot, but it is not as expected. I'll post a new question about this. |
2013-09-23 07:34:56 -0500 | received badge | ● Editor
(source)
|
2013-09-23 07:19:43 -0500 | asked a question | Gazebo 1.9 fails to load URDF (which works in RVIZ and is validate by urdfdom) Hi, I have this irritating issue that I can not spawn my URDF model in gazebo. The model has been verified with urdfdom, and I can successfully use it in RVIZ. When I try to do so I get the following error: Warning [parser_urdf.cc:1010] multiple inconsistent <self_collide> exists due to fixed joint reduction overwriting previous value [false] with [true].
Error [parser.cc:697] XML Element[sensor:ray], child of element[link] not defined in SDF. Ignoring.[link]
Error [parser.cc:688] Error reading element <link>
Error [parser.cc:688] Error reading element <model>
Error [parser.cc:348] Unable to read element <sdf>
Error [parser.cc:299] parse as old deprecated model file failed.
Error [World.cc:1469] Unable to read sdf string [..entire urdf model here]
The actual urdf model is here: <?xml version="1.0" ?>
<!-- =================================================================================== -->
<!-- | This document was autogenerated by xacro from youbot.urdf.xacro | -->
<!-- | EDITING THIS FILE BY HAND IS NOT RECOMMENDED | -->
<!-- =================================================================================== -->
<robot name="youbot" xmlns:controller="http://playerstage.sourceforge.net/gazebo/xmlschema/#controller" xmlns:interface="http://playerstage.sourceforge.net/gazebo/xmlschema/#interface" xmlns:sensor="http://playerstage.sourceforge.net/gazebo/xmlschema/#sensor" xmlns:xacro="http://ros.org/wiki/xacro">
<!-- The following included files set up definitions of parts of the robot body -->
<!-- misc common stuff? -->
<!-- youbot base -->
<!-- youbot plate -->
<!-- youbot arm -->
<!-- youbot gripper -->
<!-- generic simulator_gazebo plugins for starting mechanism control, ros time, ros battery -->
<gazebo>
<controller:gazebo_ros_controller_manager name="gazebo_ros_controller_manager" plugin="libgazebo_ros_controller_manager.so">
<alwaysOn>true</alwaysOn>
<updateRate>1000.0</updateRate>
<interface:audio name="gazebo_ros_controller_manager_dummy_iface"/>
</controller:gazebo_ros_controller_manager>
<controller:gazebo_ros_power_monitor name="gazebo_ros_power_monitor_controller" plugin="libgazebo_ros_power_monitor.so">
<alwaysOn>true</alwaysOn>
<updateRate>1.0</updateRate>
<timeout>5</timeout>
<interface:audio name="power_monitor_dummy_interface"/>
<powerStateTopic>power_state</powerStateTopic>
<powerStateRate>10.0</powerStateRate>
<fullChargeCapacity>87.78</fullChargeCapacity>
<dischargeRate>-474</dischargeRate>
<chargeRate>525</chargeRate>
<dischargeVoltage>15.52</dischargeVoltage>
<chargeVoltage>16.41</chargeVoltage>
</controller:gazebo_ros_power_monitor>
</gazebo>
<!-- materials for visualization -->
<material name="Orange">
<color rgba="1.0 0.4 0.0 1.0"/>
</material>
<material name="Grey">
<color rgba="0.7 0.7 0.7 1.0"/>
</material>
<material name="DarkGrey">
<color rgba="0.3 0.3 0.3 1.0"/>
</material>
<material name="White">
<color rgba="1.0 1.0 1.0 1.0"/>
</material>
<material name="Black">
<color rgba="0.0 0.0 0.0 1.0"/>
</material>
<material name="Red">
<color rgba="1.0 0.0 0.0 1.0"/>
</material>
<material name="Green">
<color rgba="0.0 1.0 0.0 1.0"/>
</material>
<!-- Now we can start using the macros included above to define the actual youbot -->
<!-- The first use of a macro. This one was defined in base.urdf.xacro above.
A macro like this will expand to a set of link and joint definitions, and to additional
Gazebo-related extensions (sensor plugins, etc). The macro takes an argument, name,
that equals "base", and uses it to generate names for its component links and joints
(e.g., base_link). The included origin block is also an argument to the macro. By convention,
the origin block defines where the component is w.r.t its parent ... (more) |
2013-09-20 05:59:58 -0500 | commented answer | Spawning URDF in Hydro, Gazebo 1.9 has (core dumped) issue Has this been confirmed as a "general" solution by others? |