Attention: Answers.ros.org is deprecated as of August the 11th, 2023. Please visit robotics.stackexchange.com to ask a new question. This site will remain online in read-only mode during the transition and into the foreseeable future. Selected questions and answers have been migrated, and redirects have been put in place to direct users to the corresponding questions on Robotics Stack Exchange. Additional details are available here.

A ros service's request has too many arguments

asked 2018-08-13 19:00:58 -0500

yhe34
1 ●2 ●3 ●3

I need to create a ros service server which could check whether the given path (which can be generated by path planner), collides with surrounding obstacles. Because the path consists of hundreds of way points, it's not friendly to initialize a service request that contain all these points, and then pass that to the server. Could someone give some advice on this situation. How to make it more user-friendly.

edit retag flag offensive close merge delete

Comments

If the path is a nav_msgs/Path (or even a plain list of geometry_msgs/Pose(Stamped)), then wouldn't the path be passed in a single field of the request msg?

gvdhoorn ( 2018-08-14 02:33:07 -0500 )edit

add a comment

1 Answer

Sort by » oldest newest most voted

answered 2018-09-19 23:30:48 -0500

jonlwowski012
29 ●2 ●3 ●8

I do not see any other way around it. I think you could just use a PoseArray and put all the waypoints into one PoseArray and then send that PoseArray to the service. Depending on how many way points, the service request shouldn't take too long to send.

edit flag offensive delete link

add a comment

Question Tools

1 follower

Stats

Asked: 2018-08-13 19:00:58 -0500

Seen: 340 times

Last updated: Sep 19 '18

A ros service's request has too many arguments edit

Comments

1 Answer

Question Tools

Stats

Related questions

A ros service's request has too many arguments