mark_vision's profile - activity

apply force/torque for a period of time Dear all, I see that Gazebo 8 implemented a GUI to apply a force or torque to a

If your contact sensor is attached to a link connected to another link via a fixed joint, then the problem could be rela

GetVelocity returns absurd values in Gazebo 7 and ROS Kinetic Hi all, after the upgrade to ROS Kinetic and Gazebo 7 my q

GetVelocity returns absurd values in Gazebo 7 and ROS Kinetic Hi all, after the upgrade to ROS Kinetic and Gazebo 7 my q

GetVelocity returns absurd values in Gazebo 7 and ROS Kinetic Hi all, after the upgrade to ROS Kinetic and Gazebo 7 my q

GetVelocity returns absurd values in Gazebo 7 and ROS Kinetic Hi all, after the upgrade to ROS Kinetic and Gazebo 7 my q

GetVelocity returns absurd values in Gazebo 7 and ROS Kinetic Hi all, after the upgrade to ROS Kinetic and Gazebo 7 my q

GetVelocity returns absurd values in Gazebo 7 and ROS Kinetic Hi all, after the upgrade to ROS Kinetic and Gazebo 7 my q

what version of Gazebo 7.x is ROS Kinetic using? Dear all, I don't understand what exact version of Gazebo ROS Kinetic i

what version of Gazebo 7.x is ROS Kinetic using? Dear all, I don't understand what exact version of Gazebo ROS Kinetic i

this works for me, thanks.

robot slips after upgrade to kinetic Dear all, After upgrading from Ubuntu 14.04 to 16.04 and from Indigo to Kinetic I'm

Dear all, After upgrading from Ubuntu 14.04 to 16.04 and from Indigo to Kinetic I'm experiencing a weird behavior from Gazebo and the HyQ robot model.

The complete robot model can be found here.

I made the minimal set of modifications to make it compatible with the new xacro standard (see corresponding branch)

Even after setting unrealistically high friction coefficients in the corresponding tag (see here), the robot can't walk and slips badly.

With the same description on Gazebo 2/ROS Indigo the robot always was fine.

I've narrowed down the issue to this portion of the URDF:

        <!-- Foot link -->
        <link name="${name}_foot">
            <inertial>
                <origin xyz="0 0 0"/>
                <mass value="0.0"/>
                <inertia ixx="0.0" iyy="0.0" izz="0.0" ixy="0.0" ixz="0.0" iyz="0.0"/>
            </inertial>
            <visual>
                <origin xyz="0 0 0" rpy="0 0 0"/>
                <geometry>
                    <sphere radius="0.02175"/>
                </geometry>
                <material name="black"/>
            </visual>
            <collision>
                <origin xyz="0 0 0" rpy="0 0 0"/>
                <geometry>
                    <sphere radius="0.02175"/>
                </geometry>
            </collision>

        </link>

Apparently, a collision set as a perfect sphere is handled in a different way from Gazebo 2 to 7.

If I remove the collision field, the tip of the leg (which is not spherical) is taken for the collision, and the robot works fine.

My suspect goes to the torsional friction feature, which has been introduced in new versions of Gazebo (see this related question).

UPDATE

I've reduced (yet not solved) the problem by setting the fdir1 tag to a reasonable value (it was 0 0 0). Here's how the link looks like now:

    <link name="${name}_foot">
        <inertial>
            <origin xyz="0 0 0"/>
            <mass value="0.07"/>
            <inertia ixx="0.0000112" iyy="0.0000112" izz="0.0000112" ixy="0.0" ixz="0.0" iyz="0.0"/>
        </inertial>
        <collision>
            <origin xyz="0 0 0" rpy="0 0 0"/>
            <geometry>
                <sphere radius="0.02175"/>
            </geometry>
        </collision>
    </link>
    <gazebo reference="${name}_foot">
            <mu1>1</mu1>
        <mu2>1</mu2>
        <fdir1>1 0 0</fdir1>
        <maxContacts>1</maxContacts>
            <collision name="${name}_lowerleg_fixed_joint_lump__${name}_foot_collision_1">
                <geometry>
                    <sphere>
                    <radius>0.02175</radius>
                </sphere>
                </geometry>

            <surface>
                <friction>
                    <torsional>
                            <coefficient>10</coefficient>
                            <use_patch_radius>true</use_patch_radius>
                            <surface_radius>0.05</surface_radius>
                            <patch_radius>0.01</patch_radius>
                    </torsional>
            </friction>
            <contact>
                <poissons_ratio>0.5</poissons_ratio>
                <elastic_modulus>1e8</elastic_modulus>
            </contact>
        </surface>
    </collision>

        <material>Gazebo/Black</material>
    </gazebo>

However, I still see slipping behavior (and switching contacts) when I try to move: https://youtu.be/NMUSZn1pm5U

I've finally sorted it out. The problem was related to the missing <minDepth> tag. Here is the working URDF porti

robot slips after upgrade to kinetic Dear all, After upgrading from Ubuntu 14.04 to 16.04 and from Indigo to Kinetic I'm

I also modified the gazebo_ros_pkgs, but not in the place you mentioned in your question. All the places where the SetPo

You are right, the foot is connected with the lower leg link through a fixed joint. The lowerleg has reasonable mass a

robot slips after upgrade to kinetic Dear all, After upgrading from Ubuntu 14.04 to 16.04 and from Indigo to Kinetic I'm

robot slips after upgrade to kinetic Dear all, After upgrading from Ubuntu 14.04 to 16.04 and from Indigo to Kinetic I'm

That explains how to set it up in SDF, not URDF. I believe that my problem is related to this, as I explained in detail