Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ANGULAR_MOTOR_COEFFICIENT inconsistency with the publication #61

Closed
OAHC2022 opened this issue Jan 24, 2021 · 3 comments
Closed

ANGULAR_MOTOR_COEFFICIENT inconsistency with the publication #61

OAHC2022 opened this issue Jan 24, 2021 · 3 comments
Assignees
Labels
type: question Further information is requested

Comments

@OAHC2022
Copy link

Hello,

When I was reading the paper. I came across the equation:

However, when I checked the code in here. I realized that there was inconsistency with the equations. Given the values defined in the macros, the equation in the code was

I wonder which one should I use.

Thanks

@welcome
Copy link

welcome bot commented Jan 24, 2021

Thanks for opening your first issue here! Make sure that no other issues on the same topic have already been opened!

@gsilano gsilano self-assigned this Jan 24, 2021
@gsilano gsilano added the type: question Further information is requested label Jan 24, 2021
@gsilano
Copy link
Owner

gsilano commented Jan 24, 2021

Hi @OAHC2022! I checked out the code. The formula at line 268 of the position_controller.cpp file is the following

\omega_i = \alpha PWM_i + q

where q is expressed in rad/s as PWM_i and \omega_i. I can understand this could be misleading as PWMs are usually measured in rounds per second and not radians per second. However, Gazebo uses the SI unit measure to express all the data. Therefore, position, linear and angular velocities are expressed in m, m/s and rad/s, respectively. For this reason, the term \pi/30 need not be taken into account.
In the paper, we preferred to refer to the same nomenclature of 43

If you take a look at the whole chain (i.e., RateController, ControlMixer, etc.), you will simply understand what I mean. If you have any other questions, please do not hesitate.

@OAHC2022
Copy link
Author

Oh I see the change in measurement indeed is tricky.

Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants