Skip to content

Conversation

@LucaGemma87
Copy link

  1. Debugging and checking the joint state publisher.
  2. Hardware interface

	modified:   README.md
	deleted:    config/force_torque_sensor_control.yaml
	modified:   launch/display_simulation.launch
	modified:   model/ft_sensor.gazebo.xacro
	modified:   model/ft_sensor.urdf.xacro
	config/
	launch/control_sensor_simulation.launch
	model/ft_sensor.trasmission.xacro
README.md Outdated
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍


1) on first terminal for nano17 ft sensor type:

roslaunch force_torque_sensor ft_simulation_display.launch use_gamma:=false
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a way to pass a string instead of a true/false arg?

Would be nice to have something like:

roslaunch force_torque_sensor ft_simulation_display.launch use_model:=gamma

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not found

@carlosjoserg
Copy link
Contributor

Review done. Let me know about the suggestion above... and thanks!

@carlosjoserg
Copy link
Contributor

Thanks @LucaGemma87 .

One last thing before merging, you moved this file from the model to the robot folder:
model/ft_sensor.urdf.xacro → robot/ft_sensor.urdf.xacro

Is there a reason for that? If not, I'd prefer that files implementing macros remain in the model folder, and their uses in the robot folder.

Other than that, ok for the rest

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.

2 participants