服务service和消息msg的区别在于:
1. 每一个消息都和一个话题相关,发布者对消息是发送后不管
2. 消息可以一对多,也可以多对多
3. 消息是单向的,没有响应的概念
4. 每一个service服务由一个节点发起,服务的响应也返回同一个节点
5. service服务是一对一通信
6. service服务是双向的,并且响应是同步的
7. service 由请求和响应构成
查看服务的信息 $rosservice info [服务名]
查看活动服务列表
$rosservice list 小海龟示例。
服务由请求、响应两部分构成,请求和响应之间通过“---”隔开,
通常以srv为后缀放置在srv目录下。
一个服务文件的示例如下:
- int64 a
- int64 b
-
- ---
-
- int64 sum
服务的每行声明和消息类型一样由两部分:
域、变量构成,域由独立域、复合域构成,支持的基本数据类型和消息相同。
在实现上,服务在底层由一个GlobalCallbackQueue和ServiceManager管理,
服务的请求req、响应resp本质上也是序列化的消息。
在底层,客户端和服务器通过
ServiceClientLink的boost::signals2::connection的信号、槽连接机制实现回调。
步骤1:创建自定义服务.srv
- int64 a
- int64 b
- ---
- int64 sum
步骤2:编写服务文件service
- #include "ros/ros.h"
- #include "example_4/Sum.h"
-
- bool add(example_4::Sum::Request &req,
- example_4::Sum::Response &res)
- {
- res.sum = req.a + req.b; // a+b 完成响应
- ROS_INFO("request: x=%ld, y=%ld", (long int)req.a, (long int)req.b);
- ROS_INFO("sending back response: [%ld]", (long int)res.sum);
- return true;
- }
-
- int main(int argc, char **argv)
- {
- ros::init(argc, argv, "service");
- ros::NodeHandle nh;
-
- ros::ServiceServer service = nh.advertiseService("add_two_ints", add); // 名字 + 回调名字
- ROS_INFO("Ready to add two ints.");
- ros::spin();
-
- return 0;
- }
步骤3:编写客户端文件 client
- #include "ros/ros.h"
- #include "example_4/Sum.h"
- #include
-
- int main(int argc, char **argv)
- {
- int a = 0,b = 0;
- ros::init(argc, argv, "client"); // 表明是客户端
- /*
- if (argc != 3)
- {
- ROS_INFO("usage: add_two_ints_client X Y");
- return 1;
- }
- */
- ros::NodeHandle nh;
- ros::ServiceClient client = nh.serviceClient
("add_two_ints"); - example_4::Sum srv;
- if(nh.getParam("/client/client_x",a)){
- srv.request.a = a;
- }
- if(nh.getParam("/client/client_y",b)){
- srv.request.b = b;
- }
- //srv.request.a = atoll(argv[1]);
- //srv.request.b = atoll(argv[2]);
- if (client.call(srv)) // 调用 call 就可以发起请求
- {
- ROS_INFO("Sum: %ld", (long int)srv.response.sum);
- }
- else
- {
- ROS_ERROR("Failed to call service add_two_ints");
- return 1;
- }
-
- return 0;
- }
步骤4:创建启动launch文件
-
-
"service" pkg="example_4" type="service" respawn="true"/> -
-
"client" pkg="example_4" type="client" output="screen"> - "client_x" type="int" value="1" />
- "client_y" type="int" value="5" />
-
-
-
- #两个节点一个1
- #两个节点一个5
步骤5:package.xml、CMakeLists.txt配置
- cmake_minimum_required(VERSION 3.0.2)
- project(example_4)
-
- ## Compile as C++11, supported in ROS Kinetic and newer
- # add_compile_options(-std=c++11)
-
- ## Find catkin macros and libraries
- ## if COMPONENTS list like find_package(catkin REQUIRED COMPONENTS xyz)
- ## is used, also find other catkin packages
- find_package(catkin REQUIRED COMPONENTS
- roscpp
- rospy
- std_msgs
- message_generation
- )
-
- ## System dependencies are found with CMake's conventions
- # find_package(Boost REQUIRED COMPONENTS system)
-
-
- ## Uncomment this if the package has a setup.py. This macro ensures
- ## modules and global scripts declared therein get installed
- ## See http://ros.org/doc/api/catkin/html/user_guide/setup_dot_py.html
- # catkin_python_setup()
-
- ################################################
- ## Declare ROS messages, services and actions ##
- ################################################
-
- ## To declare and build messages, services or actions from within this
- ## package, follow these steps:
- ## * Let MSG_DEP_SET be the set of packages whose message types you use in
- ## your messages/services/actions (e.g. std_msgs, actionlib_msgs, ...).
- ## * In the file package.xml:
- ## * add a build_depend tag for "message_generation"
- ## * add a build_depend and a exec_depend tag for each package in MSG_DEP_SET
- ## * If MSG_DEP_SET isn't empty the following dependency has been pulled in
- ## but can be declared for certainty nonetheless:
- ## * add a exec_depend tag for "message_runtime"
- ## * In this file (CMakeLists.txt):
- ## * add "message_generation" and every package in MSG_DEP_SET to
- ## find_package(catkin REQUIRED COMPONENTS ...)
- ## * add "message_runtime" and every package in MSG_DEP_SET to
- ## catkin_package(CATKIN_DEPENDS ...)
- ## * uncomment the add_*_files sections below as needed
- ## and list every .msg/.srv/.action file to be processed
- ## * uncomment the generate_messages entry below
- ## * add every package in MSG_DEP_SET to generate_messages(DEPENDENCIES ...)
-
- ## Generate messages in the 'msg' folder
- # add_message_files(
- # FILES
- # Message1.msg
- # Message2.msg
- # )
-
- ## Generate services in the 'srv' folder
- add_service_files(
- FILES
- Sum.srv
- )
-
- ## Generate actions in the 'action' folder
- # add_action_files(
- # FILES
- # Action1.action
- # Action2.action
- # )
-
- ## Generate added messages and services with any dependencies listed here
- generate_messages(
- DEPENDENCIES
- std_msgs
- )
-
- ################################################
- ## Declare ROS dynamic reconfigure parameters ##
- ################################################
-
- ## To declare and build dynamic reconfigure parameters within this
- ## package, follow these steps:
- ## * In the file package.xml:
- ## * add a build_depend and a exec_depend tag for "dynamic_reconfigure"
- ## * In this file (CMakeLists.txt):
- ## * add "dynamic_reconfigure" to
- ## find_package(catkin REQUIRED COMPONENTS ...)
- ## * uncomment the "generate_dynamic_reconfigure_options" section below
- ## and list every .cfg file to be processed
-
- ## Generate dynamic reconfigure parameters in the 'cfg' folder
- # generate_dynamic_reconfigure_options(
- # cfg/DynReconf1.cfg
- # cfg/DynReconf2.cfg
- # )
-
- ###################################
- ## catkin specific configuration ##
- ###################################
- ## The catkin_package macro generates cmake config files for your package
- ## Declare things to be passed to dependent projects
- ## INCLUDE_DIRS: uncomment this if your package contains header files
- ## LIBRARIES: libraries you create in this project that dependent projects also need
- ## CATKIN_DEPENDS: catkin_packages dependent projects also need
- ## DEPENDS: system dependencies of this project that dependent projects also need
- catkin_package(
- # INCLUDE_DIRS include
- # LIBRARIES example_4
- # CATKIN_DEPENDS roscpp rospy std_msgs
- # DEPENDS system_lib
- )
-
- ###########
- ## Build ##
- ###########
-
- ## Specify additional locations of header files
- ## Your package locations should be listed before other locations
- include_directories(
- # include
- ${catkin_INCLUDE_DIRS}
- )
-
- ## Declare a C++ library
- # add_library(${PROJECT_NAME}
- # src/${PROJECT_NAME}/example_4.cpp
- # )
-
- ## Add cmake target dependencies of the library
- ## as an example, code may need to be generated before libraries
- ## either from message generation or dynamic reconfigure
- # add_dependencies(${PROJECT_NAME} ${${PROJECT_NAME}_EXPORTED_TARGETS} ${catkin_EXPORTED_TARGETS})
-
- ## Declare a C++ executable
- ## With catkin_make all packages are built within a single CMake context
- ## The recommended prefix ensures that target names across packages don't collide
-
- ## Rename C++ executable without prefix
- ## The above recommended prefix causes long target names, the following renames the
- ## target back to the shorter version for ease of user use
- ## e.g. "rosrun someones_pkg node" instead of "rosrun someones_pkg someones_pkg_node"
- # set_target_properties(${PROJECT_NAME}_node PROPERTIES OUTPUT_NAME node PREFIX "")
-
- ## Add cmake target dependencies of the executable
- ## same as for the library above
- # add_dependencies(${PROJECT_NAME}_node ${${PROJECT_NAME}_EXPORTED_TARGETS} ${catkin_EXPORTED_TARGETS})
-
- ## Specify libraries to link a library or executable target against
- if(CMAKE_BUILD_TYPE STREQUAL DEBUG)
- add_executable(service src/service.cpp)
- add_executable(client src/client.cpp)
- target_link_libraries(service
- ${catkin_LIBRARIES}
- )
- target_link_libraries(client
- ${catkin_LIBRARIES}
- )
- endif()
- #############
- ## Install ##
- #############
-
- # all install targets should use catkin DESTINATION variables
- # See http://ros.org/doc/api/catkin/html/adv_user_guide/variables.html
-
- ## Mark executable scripts (Python etc.) for installation
- ## in contrast to setup.py, you can choose the destination
- # catkin_install_python(PROGRAMS
- # scripts/my_python_script
- # DESTINATION ${CATKIN_PACKAGE_BIN_DESTINATION}
- # )
-
- ## Mark executables for installation
- ## See http://docs.ros.org/melodic/api/catkin/html/howto/format1/building_executables.html
- # install(TARGETS ${PROJECT_NAME}_node
- # RUNTIME DESTINATION ${CATKIN_PACKAGE_BIN_DESTINATION}
- # )
-
- ## Mark libraries for installation
- ## See http://docs.ros.org/melodic/api/catkin/html/howto/format1/building_libraries.html
- # install(TARGETS ${PROJECT_NAME}
- # ARCHIVE DESTINATION ${CATKIN_PACKAGE_LIB_DESTINATION}
- # LIBRARY DESTINATION ${CATKIN_PACKAGE_LIB_DESTINATION}
- # RUNTIME DESTINATION ${CATKIN_GLOBAL_BIN_DESTINATION}
- # )
-
- ## Mark cpp header files for installation
- # install(DIRECTORY include/${PROJECT_NAME}/
- # DESTINATION ${CATKIN_PACKAGE_INCLUDE_DESTINATION}
- # FILES_MATCHING PATTERN "*.h"
- # PATTERN ".svn" EXCLUDE
- # )
-
- ## Mark other files for installation (e.g. launch and bag files, etc.)
- # install(FILES
- # # myfile1
- # # myfile2
- # DESTINATION ${CATKIN_PACKAGE_SHARE_DESTINATION}
- # )
-
- #############
- ## Testing ##
- #############
-
- ## Add gtest based cpp test target and link libraries
- # catkin_add_gtest(${PROJECT_NAME}-test test/test_example_4.cpp)
- # if(TARGET ${PROJECT_NAME}-test)
- # target_link_libraries(${PROJECT_NAME}-test ${PROJECT_NAME})
- # endif()
-
- ## Add folders to be run by python nosetests
- # catkin_add_nosetests(test)
package.xml
- "1.0"?>
"2"> -
example_4 -
0.0.0 -
The example_4 package -
-
-
-
-
"miaozl@todo.todo">miaozl -
-
-
-
-
-
D -
O -
O -
T -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
catkin -
roscpp -
rospy -
std_msgs -
message_generation -
roscpp -
rospy -
std_msgs -
roscpp -
rospy -
std_msgs -
message_runtime -
-
-
-
-
-
-
步骤6:生成服务文件 编译执行