# Revision history [back]

### Setting friction params

Ok guys, is any of you open to explain this in a simplified matter, or on a specific example? We all usually need friction for wheels; so If you have a wheel, turning on the x direction. You would want to have friction on the x direction. and on the y also so the wheel does not slip on the sides. So mu = mu2. But if you want to model an omniwheel, you would like the y direction to have no friction, so the wheel can actually slip that side. So you set up the mu2 = 0 In case your wheel is not oriented on the specified axes you can change the direction with fdir1.

I keep on seing people advising friction of 100 or some other values that are not comprised in the 0..1 interval specified by the sdf documentation. What is the catch with that?

I played around with the friction, but apparently for the same settings, my wheels react differently from a run to another.

I try to simulate a 3 omniwheeled robot base.

### Setting friction params

Ok guys, is any of you open to explain this in a simplified matter, or on a specific example? We all usually need friction for wheels; so If you have a wheel, turning on the x direction. You would want to have friction on the x direction. and on the y also so the wheel does not slip on the sides. So mu = mu2. But if you want to model an omniwheel, you would like the y direction to have no friction, so the wheel can actually slip that side. So you set up the mu2 = 0 In case your wheel is not oriented on the specified axes you can change the direction with fdir1.

I keep on seing people advising friction of 100 or some other values that are not comprised in the 0..1 interval specified by the sdf documentation. What is the catch with that?

I played around with the friction, but apparently for the same settings, my wheels react differently from a run to another.

I try to simulate a 3 omniwheeled robot base.

base. An i've just come to realise there is no friction the sdf code generated by for gazebo from the xacro file written.

code:

  <surface>
<friction>
<ode>
<mu>${fric}</mu> <mu2>0</mu2> <fdir1>${cos(rot2)} ${sin(rot2)} 0</fdir1> </ode> </friction> </surface>  generated code:  <surface> <contact> <ode> <kp>1e+06</kp> <kd>1</kd> </ode> </contact> <friction> <ode/> </friction> </surface>  ### Setting friction params Ok guys, is any of you open to explain this in a simplified matter, or on a specific example? We all usually need friction for wheels; so If you have a wheel, turning on the x direction. You would want to have friction on the x direction. and on the y also so the wheel does not slip on the sides. So mu = mu2. But if you want to model an omniwheel, you would like the y direction to have no friction, so the wheel can actually slip that side. So you set up the mu2 = 0 In case your wheel is not oriented on the specified axes you can change the direction with fdir1. I keep on seing people advising friction of 100 or some other values that are not comprised in the 0..1 interval specified by the sdf documentation. What is the catch with that? I played around with the friction, but apparently for the same settings, my wheels react differently from a run to another. I try to simulate a 3 omniwheeled robot base. An i've And I've just come to realise there is no friction the sdf code generated by for gazebo from the xacro file written. code:  <surface> <friction> <ode> <mu>${fric}</mu>
<mu2>0</mu2>
<fdir1>${cos(rot2)}${sin(rot2)} 0</fdir1>
</ode>
</friction>
</surface>


generated code:

  <surface>
<contact>
<ode>
<kp>1e+06</kp>
<kd>1</kd>
</ode>
</contact>
<friction>
<ode/>
</friction>
</surface>


### Setting friction params

Ok guys, is any of you open to explain this in a simplified matter, or on a specific example? We all usually need friction for wheels; so If you have a wheel, turning on the x direction. You would want to have friction on the x direction. and on the y also so the wheel does not slip on the sides. So mu = mu2. But if you want to model an omniwheel, you would like the y direction to have no friction, so the wheel can actually slip that side. So you set up the mu2 = 0 In case your wheel is not oriented on the specified axes you can change the direction with fdir1.

I keep on seing people advising friction of 100 or some other values that are not comprised in the 0..1 interval specified by the sdf documentation. What is the catch with that?

I played around with the friction, but apparently for the same settings, my wheels react differently from a run to another.

I try to simulate a 3 omniwheeled robot base. And I've just come to realise there is no friction the sdf code generated by for gazebo from the xacro file written.

code:

 <surface>
<friction>
<ode>
<mu>${fric}</mu> <mu>0.5</mu> <mu2>0</mu2> <fdir1>${cos(rot2)} \${sin(rot2)} <fdir1>6.12323399574e-17 1.0 0</fdir1>
<implicit_spring_damper>true</implicit_spring_damper>
</ode>
</friction>
</surface>


generated code:

  <surface>
<contact>
<ode>
<kp>1e+06</kp>
<kd>1</kd>
</ode>
</contact>
<friction>
<ode/>
</friction>
</surface>


### Setting friction params

Ok guys, is any of you open to explain this in a simplified matter, or on a specific example? We all usually need friction for wheels; so If you have a wheel, turning on the x direction. You would want to have friction on the x direction. and on the y also so the wheel does not slip on the sides. So mu = mu2. But if you want to model an omniwheel, you would like the y direction to have no friction, so the wheel can actually slip that side. So you set up the mu2 = 0 In case your wheel is not oriented on the specified axes you can change the direction with fdir1.

I keep on seing people advising friction of 100 or some other values that are not comprised in the 0..1 interval specified by the sdf documentation. What is the catch with that?

I played around with the friction, but apparently for the same settings, my wheels react differently from a run to another.

I try to simulate a 3 omniwheeled robot base. And I've just come to realise there is no friction the sdf code generated by for gazebo from the xacro file written.

code:

<surface>
<friction>
<ode>
<mu>0.5</mu>
<mu>1</mu>
<mu2>0</mu2>
<fdir1>6.12323399574e-17 <fdir1>0 1.0 0</fdir1>
<implicit_spring_damper>true</implicit_spring_damper>
</ode>
</friction>
</surface>


generated code:

  <surface>
<contact>
<ode>
<kp>1e+06</kp>
<kd>1</kd>
</ode>
</contact>
<friction>
<ode/>
</friction>
</surface>


### Setting friction params

Ok guys, is any of you open to explain this in a simplified matter, or on a specific example? We all usually need friction for wheels; so If you have a wheel, turning on the x direction. You would want to have friction on the x direction. and on the y also so the wheel does not slip on the sides. So mu = mu2. But if you want to model an omniwheel, you would like the y direction to have no friction, so the wheel can actually slip that side. So you set up the mu2 = 0 In case your wheel is not oriented on the specified axes you can change the direction with fdir1.

I keep on seing people advising friction of 100 or some other values that are not comprised in the 0..1 interval specified by the sdf documentation. What is the catch with that?

I played around with the friction, but apparently for the same settings, my wheels react differently from a run to another.

I try to simulate a 3 omniwheeled robot base. And I've just come to realise there is no friction the sdf code generated by for gazebo from the xacro file written.

code:code URDF:

<surface>
<friction>
<ode>
<mu>1</mu>
<mu2>0</mu2>
<fdir1>0 1.0 0</fdir1>
<implicit_spring_damper>true</implicit_spring_damper>
</ode>
</friction>
</surface>


generated code:code SDF:

  <surface>
<contact>
<ode>
<kp>1e+06</kp>
<kd>1</kd>
</ode>
</contact>
<friction>
<ode/>
</friction>
</surface>
</surface>R


### Setting friction params

Ok guys, is any of you open to explain this in a simplified matter, or on a specific example? We all usually need friction for wheels; so If you have a wheel, turning on the x direction. You would want to have friction on the x direction. and on the y also so the wheel does not slip on the sides. So mu = mu2. But if you want to model an omniwheel, you would like the y direction to have no friction, so the wheel can actually slip that side. So you set up the mu2 = 0 In case your wheel is not oriented on the specified axes you can change the direction with fdir1.

I keep on seing people advising friction of 100 or some other values that are not comprised in the 0..1 interval specified by the sdf documentation. What is the catch with that?

I played around with the friction, but apparently for the same settings, my wheels react differently from a run to another.

I try to simulate a 3 omniwheeled robot base. And I've just come to realise there is no friction in the sdf code generated by for gazebo from the xacro file written.

code URDF:

<surface>
<friction>
<ode>
<mu>1</mu>
<mu2>0</mu2>
<fdir1>0 1.0 0</fdir1>
<implicit_spring_damper>true</implicit_spring_damper>
</ode>
</friction>
</surface>


generated code SDF:

  <surface>
<contact>
<ode>
<kp>1e+06</kp>
<kd>1</kd>
</ode>
</contact>
<friction>
<ode/>
</friction>
</surface>R


### Setting friction params

Ok guys, is any of you open to explain this in a simplified matter, or on a specific example? We all usually need friction for wheels; so If you have a wheel, turning on the x direction. You would want to have friction on the x direction. and on the y also so the wheel does not slip on the sides. So mu = mu2. But if you want to model an omniwheel, you would like the y direction to have no friction, so the wheel can actually slip that side. So you set up the mu2 = 0 In case your wheel is not oriented on the specified axes you can change the direction with fdir1.

I keep on seing people advising friction of 100 or some other values that are not comprised in the 0..1 interval specified by the sdf documentation. What is the catch with that?

I played around with the friction, but apparently for the same settings, my wheels react differently from a run to another.

I try to simulate a 3 omniwheeled robot base. And I've just come to realise there is no friction in the sdf code generated for gazebo from the xacro file written.

code URDF:

<surface>
<friction>
<ode>
<mu>1</mu>
<mu2>0</mu2>
<fdir1>0 1.0 0</fdir1>
<implicit_spring_damper>true</implicit_spring_damper>
</ode>
</friction>
</surface>


generated code SDF:

  <surface>
<contact>
<ode>
<kp>1e+06</kp>
<kd>1</kd>
</ode>
</contact>
<friction>
<ode/>
</friction>
</surface>R
</surface>


### Setting friction params

Ok guys, is any of you open to explain this in a simplified matter, or on a specific example? We all usually need friction for wheels; so If you have a wheel, turning on the x direction. You would want to have friction on the x direction. and on the y also so the wheel does not slip on the sides. So mu = mu2. But if you want to model an omniwheel, you would like the y direction to have no friction, so the wheel can actually slip that side. So you set up the mu2 = 0 In case your wheel is not oriented on the specified axes you can change the direction with fdir1.

I keep on seing people advising friction of 100 or some other values that are not comprised in the 0..1 interval specified by the sdf documentation. What is the catch with that?

I played around with the friction, but apparently for the same settings, my wheels react differently from a run to another.

I try to simulate a 3 omniwheeled robot base. And I've just come to realise there is no friction in the sdf code generated for gazebo from the xacro file written.

code URDF:

<surface>
<friction>
<ode>
<mu>1</mu>
<mu2>0</mu2>
<fdir1>0 1.0 0</fdir1>
<implicit_spring_damper>true</implicit_spring_damper>
</ode>
</friction>
</surface>


generated code SDF:SDF with gw sdf -p:

  <surface>
<contact>
<ode>
<kp>1e+06</kp>
<kd>1</kd>
</ode>
</contact>
<friction>
<ode/>
</friction>
</surface>


### Setting friction params

Ok guys, is any of you open to explain this in a simplified matter, or on a specific example? We all usually need friction for wheels; so If you have a wheel, turning on the x direction. You would want to have friction on the x direction. and on the y also so the wheel does not slip on the sides. So mu = mu2. But if you want to model an omniwheel, you would like the y direction to have no friction, so the wheel can actually slip that side. So you set up the mu2 = 0 In case your wheel is not oriented on the specified axes you can change the direction with fdir1.

I keep on seing people advising friction of 100 or some other values that are not comprised in the 0..1 interval specified by the sdf documentation. What is the catch with that?

I played around with the friction, but apparently for the same settings, my wheels react differently from a run to another.

I try to simulate a 3 omniwheeled robot base. And I've just come to realise there is no friction in the sdf code generated for gazebo from the xacro file written.

code URDF:

<surface>
<friction>
<ode>
<mu>1</mu>
<mu2>0</mu2>
<fdir1>0 1.0 0</fdir1>
<implicit_spring_damper>true</implicit_spring_damper>
</ode>
</friction>
</surface>


generated code SDF with gw sdf -p:

  <surface>
<contact>
<ode>
<kp>1e+06</kp>
<kd>1</kd>
</ode>
</contact>
<friction>
<ode/>
</friction>
</surface>


A part of my question can be also found here, but nobody actually answered that part.