no such files and open_base model moves itself

[k-quinted]

Hi, GuiRitter.

I tried to copy the your OpenBase packages to my catkin workspace and do the catkin_make.
But, in this result, I had a fatal error and no such files (the following files)
・open_base/Velocity.h
・open_bace/FrameToFrame.h
・open_bace/KinematicsForward.h
So, this issue is the same problem of mashenlyl.

Also, I tried to copy and launch following xacro files.
・OpenBase/ROS/open_base/xacro/main.urdf.xacro
・OpenBase/ROS/open_base/xacro/rim.urdf.xacro
・OpenBase/ROS/open_base/xacro/roller.urdf.xacro
But, the model moves itself.

I just use following launch files.
So, I have not input anything.
・OpenBase/ROS/open_base/launch/gazebo description.launch
・OpenBase/ROS/open_base/launch/parameter.launch

What is the case this issue?

I use ROS Kinetic and Gazebo7.

Thanks in advance for your help.

[GuiRitter]

The issue with the missing files is because the message files need to compiled before the rest, but apparently aren't being.

The model is moving itself probably because of some tests I left behind.

I ask that you forgive me, for I don't have a lot of time right now to take a good look at this. I realized I already have forgotten a lot about ROS just by looking at the previous issue.

[AlvaroFerGar]

Hello!

I have started working with this repository and I think I have the solution for the message compiling problem. I know it has been more than a month since the last comment but maybe this could be useful for someone.

The solution is really simple. To be sure that the message files are compiled before the rest, you only need to add this just after the target_link_libraries( ):
add_dependencies(name_of_exe package_name_generate_messages_cpp)

So this is how the #Build# part of my CMakeLists.txt actually looks like:

###########
## Build ##
###########

include_directories( include
  ${catkin_INCLUDE_DIRS}
  ${Eigen3_INCLUDE_DIRS}
)

add_executable(${PROJECT_NAME}_kinematics src/kinematics.cpp)
target_link_libraries(
  ${PROJECT_NAME}_kinematics
  ${catkin_LIBRARIES}
  ${orocos-kdl_LIBRARIES}
  ${kdl_parser_LIBRARIES}
)
add_dependencies(${PROJECT_NAME}_kinematics open_base_generate_messages_cpp)

add_executable(${PROJECT_NAME}_odometry src/odometry.cpp)
target_link_libraries(
  ${PROJECT_NAME}_odometry
  ${catkin_LIBRARIES}
  ${kdl_parser_LIBRARIES}
)
add_dependencies(${PROJECT_NAME}_odometry open_base_generate_messages_cpp)

add_executable(${PROJECT_NAME}_sensor_encoder src/sensor/encoder.cpp)
target_link_libraries(
  ${PROJECT_NAME}_sensor_encoder
  ${catkin_LIBRARIES}
)
add_dependencies(${PROJECT_NAME}_sensor_encoder open_base_generate_messages_cpp)

add_executable(${PROJECT_NAME}_main src/main.cpp)
target_link_libraries(
  ${PROJECT_NAME}_main
  ${catkin_LIBRARIES}
)
add_dependencies(${PROJECT_NAME}_main open_base_generate_messages_cpp)

This work for me with Ubuntu 16.04LTS and ROS Kinetic. I hope it helps somebody!!

[GuiRitter]

@AlvaroFerGar Thanks for the tip! I'll take a look into it soon-ish and update the repository if it works.

[GuiRitter]

@AlvaroFerGar I've adapted the code you provided and it fixed the build order bug. Committed and pushed. Thanks!

[GuiRitter]

I tested a project I had created that used this package to control a 4 joints robot. I remember clearly it was working. It failed with the same message generation problems. I fixed it with the same solution. Something must have changed in ROS while I wasn't working on it.

[GuiRitter]

@k-quinted I just committed some fixes and I would like some more information from you to see if I can resolve your issues. I hadn't realized before that I didn't understood your question correctly.

The first bit about

• open_base/Velocity.h
• open_bace/FrameToFrame.h
• open_bace/KinematicsForward.h

has been fixed in b3da6f6.

About

I tried to copy and launch following xacro files

How did you try to launch these files? They aren't meant to be launched directly. They are meant to be launched from *.launch files.

About

• OpenBase/ROS/open_base/launch/gazebo description.launch
• OpenBase/ROS/open_base/launch/parameter.launch

• parameter.launch is not meant to be launched directly. It's meant to be launched from other launch files to load common parameters.
• gazebo description.launch is meant only to load the robot's description in Gazebo, in order to test the description itself. It's not meant to make the robot move. To make the robot move, you can launch velocity controller.launch and pass messages to /open_base/command. You probably can use other launch files to make the robot move, but I forgot how to use them.

[k-quinted]

@GuiRitter

Thank you for your reply.

My question is why the open_base model moves itself.

I was loading the model on Gazebo by gazebo description.launch.
But, the robot has rotated the wheel without any input.
Then, I did not launch the other launch file and control programs.

[20150388]

Hello. I'm working with this repository, but a i'm a beginner in ROS. When i launch the velocity controller i get this messages: *"ERROR: *cannot launch node of type [open_base/open_base_odometry]: can't locate node [open_base_odometry] in package [open_base] *ERROR*: cannot launch node of type [open_base/open_base_kinematics]: can't locate node [open_base_kinematics] in package [open_base] *ERROR*: cannot launch node of type [open_base/open_base_sensor_encoder]: can't locate node [open_base_sensor_encoder] in package [open_base] *ERROR*: cannot launch node of type [open_base/open_base_main]: can't locate node [open_base_main] in package [open_base] [ INFO] [1534792654.451628583]: Finished loading Gazebo ROS API Plugin. [ INFO] [1534792654.452117925]: waitForService: Service [/gazebo/set_physics_properties] has not been advertised, waiting... [INFO] [1534792654.465419, 0.000000]: Controller Spawner: Waiting for service controller_manager/load_controller [ INFO] [1534792654.508394461]: Finished loading Gazebo ROS API Plugin. [ INFO] [1534792654.509917473]: waitForService: Service [/gazebo/set_physics_properties] has not been advertised, waiting... [ INFO] [1534792655.505918382]: Loading gazebo_ros_control plugin [ INFO] [1534792655.506032560]: Starting gazebo_ros_control plugin in namespace: /open_base [ INFO] [1534792655.506896663]: gazebo_ros_control plugin is waiting for model URDF in parameter [/open_base/robot_description] on the ROS param server. [ WARN] [1534792655.618791152]: Deprecated syntax, please prepend 'hardware_interface/' to 'EffortJointInterface' within the <hardwareInterface> tag in joint 'rim_left_joint'. [ WARN] [1534792655.619829913]: Deprecated syntax, please prepend 'hardware_interface/' to 'EffortJointInterface' within the <hardwareInterface> tag in joint 'rim_back_joint'. [ WARN] [1534792655.620399605]: Deprecated syntax, please prepend 'hardware_interface/' to 'EffortJointInterface' within the <hardwareInterface> tag in joint 'rim_right_joint'. [ INFO] [1534792655.625846871]: Loaded gazebo_ros_control. [INFO] [1534792655.677123, 0.000000]: Controller Spawner: Waiting for service controller_manager/switch_controller [INFO] [1534792655.678526, 0.000000]: Controller Spawner: Waiting for service controller_manager/unload_controller [INFO] [1534792655.679756, 0.000000]: Loading controller: joint_state_controller [*ERROR*] [1534792655.687861112]: Could not load controller 'joint_state_controller' because controller type 'joint_state_controller/JointStateController' does not exist. [*ERROR*] [1534792655.687898031]: Use 'rosservice call controller_manager/list_controller_types' to get the available types [open_base/open_base_spawner-4] process has finished cleanly log file: /home/fabio/.ros/log/b06014b2-a4ad-11e8-a900-dc85de1be21c/open_base-open_base_spawner-4*.log [*ERROR*] [1534792656.689228, 0.000000]: Failed to load joint_state_controller [INFO] [1534792656.689619, 0.000000]: Loading controller: left_joint_velocity_controller [*ERROR*] [1534792656.694138732]: Could not load controller 'left_joint_velocity_controller' because controller type 'effort_controllers/JointVelocityController' does not exist. [*ERROR*] [1534792656.694174483]: Use 'rosservice call controller_manager/list_controller_types' to get the available types [*ERROR*] [1534792657.695460, 0.000000]: Failed to load left_joint_velocity_controller [INFO] [1534792657.695944, 0.000000]: Loading controller: back_joint_velocity_controller [*ERROR*] [1534792657.700592487]: Could not load controller 'back_joint_velocity_controller' because controller type 'effort_controllers/JointVelocityController' does not exist. [*ERROR*] [1534792657.700632586]: Use 'rosservice call controller_manager/list_controller_types' to get the available types [*ERROR*] [1534792658.701905, 0.000000]: Failed to load back_joint_velocity_controller [INFO] [1534792658.702327, 0.000000]: Loading controller: right_joint_velocity_controller [*ERROR*] [1534792658.707225721]: Could not load controller 'right_joint_velocity_controller' because controller type 'effort_controllers/JointVelocityController' does not exist. [*ERROR*] [1534792658.707269682]: Use 'rosservice call controller_manager/list_controller_types' to get the available types [*ERROR*] [1534792659.708275, 0.000000]: Failed to load right_joint_velocity_controller [INFO] [1534792659.708676, 0.000000]: Controller Spawner: Loaded controllers: " I have to a keyboard controller to move the robot, and build a manipulator robot "arm" on the top to pick up objects from the floor. I'm working with Ubuntu 16.04LTS and ROS Kinetic. Thanks AlvaroFerGar <notifications@github.com> escreveu no dia quinta, 9/08/2018 à(s) 16:35:

…

Hello! I have started working with this repository and I think I have the solution for the message compiling problem. I know it has been more than a month since the last comment but maybe this could be useful for someone. The solution is really simple. To be sure that the message files are compiled before the rest, you only need to add this just after the target_link_libraries( ): add_dependencies(name_of_exe package_name_generate_messages_cpp) So this is how the #Build# part of my CMakeLists.txt actually looks like: ########### ## Build ## ########### include_directories( include ${catkin_INCLUDE_DIRS} ${Eigen3_INCLUDE_DIRS} ) add_executable(${PROJECT_NAME}_kinematics src/kinematics.cpp) target_link_libraries( ${PROJECT_NAME}_kinematics ${catkin_LIBRARIES} ${orocos-kdl_LIBRARIES} ${kdl_parser_LIBRARIES} ) add_dependencies(${PROJECT_NAME}_kinematics open_base_generate_messages_cpp) add_executable(${PROJECT_NAME}_odometry src/odometry.cpp) target_link_libraries( ${PROJECT_NAME}_odometry ${catkin_LIBRARIES} ${kdl_parser_LIBRARIES} ) add_dependencies(${PROJECT_NAME}_odometry open_base_generate_messages_cpp) add_executable(${PROJECT_NAME}_sensor_encoder src/sensor/encoder.cpp) target_link_libraries( ${PROJECT_NAME}_sensor_encoder ${catkin_LIBRARIES} ) add_dependencies(${PROJECT_NAME}_sensor_encoder open_base_generate_messages_cpp) add_executable(${PROJECT_NAME}_main src/main.cpp) target_link_libraries( ${PROJECT_NAME}_main ${catkin_LIBRARIES} ) add_dependencies(${PROJECT_NAME}_main open_base_generate_messages_cpp) This work for me with Ubuntu 16.04LTS and ROS Kinetic. I hope it helps somebody!! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#5 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AiQ3L8ROIbJwb3MZ_mwu0Ru-G6ztbdfyks5uPFbdgaJpZM4U1brM> .

[GuiRitter]

@k-quinted You're welcome!

My question is why the open_base model moves itself.

When using gazebo description.launch, it doesn't create any controllers, because the purpose of this launch file is just to test the description in Gazebo. Without controllers, the joints move freely.

To get movement out of this robot, use velocity controller.launch and pass messages to /open_base/command. You have two options:

• Write in a terminal rostopic pub /open_base/command then hit Tab a few times to autocomplete the message template and fill the values. To know what each value mean, look into the *.msg files in the msg folder;
• Edit the scripts/movement*.sh files to your needs and run them with source scripts/movement*.sh.

@20150388 You need to install a few packages to support the controllers I used. These should do:

sudo apt-get install ros-kinetic-joint-state-controller
sudo apt-get install ros-kinetic-effort-controllers
sudo apt-get install ros-kinetic-position-controllers

I'll edit README.md to make these things more clear. A bit right now and more later. Please let me know if you managed to get it working.

[k-quinted]

@GuiRitter

Ok.

After confirming, I will tell you.

Thank you.

[20150388]

Hello. First i want thank you for the help. I tested the velocity controller.launch after install the packages and it works fine and also moving the robot publishing the open base command was working. Do you have any suggestion how to put the robot moving with the keyboard? Thank you Guilherme Alan Ritter <notifications@github.com> escreveu no dia terça, 21/08/2018 à(s) 01:38:

…

@k-quinted <https://github.com/k-quinted> You're welcome! My question is why the open_base model moves itself. When using gazebo description.launch, it doesn't create any controllers, because the purpose of this launch file is just to test the description in Gazebo. Without controllers, the joints move freely. To get movement out of this robot, use velocity controller.launch and pass messages to /open_base/command. You have two options: - Write in a terminal rostopic pub /open_base/command then hit Tab a few times to autocomplete the message template and fill the values. To know what each value mean, look into the *.msg files in the msg folder, - Edit the scripts/movement*.sh files to your needs and run them with source scripts/movement*.sh. @20150388 <https://github.com/20150388> You need to install a few packages to support the controllers I used. These should do: sudo apt-get install ros-kinetic-joint-state-controller sudo apt-get install ros-kinetic-effort-controllers sudo apt-get install ros-kinetic-position-controllers I'll edit README.md to make these things more clear. A bit right now and more later. Please let me know if you managed to get it working. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#5 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AiQ3LyRviED4_IlD5X2ueWIdn21IHqdzks5uS1aLgaJpZM4U1brM> .

[GuiRitter]

@20150388 You're welcome! Glad to know it's working.

I don't remember if I've ever worked with keyboard control before, though I have some plans for the distant future.

Maybe this might be a good starting point.