Skip to content

Commit c7ebfad

Browse files
fmauchVinDp
andauthored
Apply suggestions from code review
Co-authored-by: Vincenzo Di Pentima <[email protected]>
1 parent ab62e4f commit c7ebfad

File tree

2 files changed

+9
-9
lines changed

2 files changed

+9
-9
lines changed

ur_controllers/doc/index.rst

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -138,7 +138,7 @@ Advertised services
138138

139139
.. _passthrough_trajectory_controller:
140140

141-
ur_controlers/PassthroughTrajectoryController
141+
ur_controllers/PassthroughTrajectoryController
142142
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
143143

144144
This controller uses a ``control_msgs/FollowJointTrajectory`` action but instead of interpolating
@@ -221,12 +221,12 @@ directly to their joints.
221221
<command_interface name="setpoint_positions_3"/>
222222
<command_interface name="setpoint_positions_4"/>
223223
<command_interface name="setpoint_positions_5"/>
224-
<command_interface name="setpoint_velicities_0"/>
225-
<command_interface name="setpoint_velicities_1"/>
226-
<command_interface name="setpoint_velicities_2"/>
227-
<command_interface name="setpoint_velicities_3"/>
228-
<command_interface name="setpoint_velicities_4"/>
229-
<command_interface name="setpoint_velicities_5"/>
224+
<command_interface name="setpoint_velocities_0"/>
225+
<command_interface name="setpoint_velocities_1"/>
226+
<command_interface name="setpoint_velocities_2"/>
227+
<command_interface name="setpoint_velocities_3"/>
228+
<command_interface name="setpoint_velocities_4"/>
229+
<command_interface name="setpoint_velocities_5"/>
230230
<command_interface name="setpoint_accelerations_0"/>
231231
<command_interface name="setpoint_accelerations_1"/>
232232
<command_interface name="setpoint_accelerations_2"/>
@@ -247,7 +247,7 @@ Implementation details / dataflow
247247
"""""""""""""""""""""""""""""""""
248248

249249
* A trajectory passed to the controller will be sent to the hardware component one by one.
250-
* The controller will send one setpooint and then wait for the hardware to acknowledge that it can
250+
* The controller will send one setpoint and then wait for the hardware to acknowledge that it can
251251
take a new setpoint.
252252
* This happens until all setpoints have been transferred to the hardware. Then, the controller goes
253253
into a waiting state where it monitors execution time and waits for the hardware to finish

ur_controllers/include/ur_controllers/passthrough_trajectory_controller.hpp

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ namespace ur_controllers
7272

7373
/*
7474
* 0.0: No trajectory to forward, the controller is idling and ready to receive a new trajectory.
75-
* 1.0: The controller has received and accepted a new trajecotry. When the state is 1.0, the controller will write a
75+
* 1.0: The controller has received and accepted a new trajectory. When the state is 1.0, the controller will write a
7676
* point to the hardware interface.
7777
* 2.0: The hardware interface will read the point written from the controller. The state will switch between 1.0
7878
* and 2.0 until all points have been read by the hardware interface.

0 commit comments

Comments
 (0)