Skip to content

Conversation

adolfo-rt
Copy link
Contributor

See #11 for the discussion motivating this change.

Adolfo Rodriguez Tsouroukdissian added 2 commits August 6, 2014 12:27
The topic interface should be favored, and there's already a reference controller
implementation in pal_ros_controllers/current_limit_controller.
The message in pal_control_msgs/ActuatorCurrentLimit is favored because:

- It has correct semantics, we are limiting _actuator_ currents, not _joint_
  currents.

- It allows to independently limit multiple actuators.
@po1
Copy link
Contributor

po1 commented Aug 6, 2014

Any idea of what code was using these two PRs?

@po1
Copy link
Contributor

po1 commented Aug 6, 2014

@adolfo-rt
Copy link
Contributor Author

I could only find two references:

@po1
Copy link
Contributor

po1 commented Aug 6, 2014

@adolfo-rt before you spend a lot of time on writing an rqt plugin, check with @hilario, he wrote a dynamic-dynamic-reconfigure, that allows you to define the parameters at runtime, and thus to use the rqt_reconfigure interface with all the benefits of a dynamic plugin.

@adolfo-rt
Copy link
Contributor Author

FYI, I plan to merge this one tomorrow afternoon (Sept 3).

@awesomebytes
Copy link
Contributor

The code that was using this has already been changed to your new version )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants