The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
Client client("mode_client", true);
If I'm not mistaken, the first argument to the ctor would be the namespace the client uses to communicate with the server (docs).
You set that to mode_server for the server, but to mode_client for the client.
That would make them unable to find each other, causing the client to wait for the server to come up.
| | 2 | No.2 Revision |
Client client("mode_client", true);
If I'm not mistaken, the first argument to the ctor would be the namespace the client uses to communicate with the server (docs).
You set that to mode_server for the server, but to mode_client for the client.
That would make them unable to find each other, causing the client to wait for the server to come up.
The example server and client you mention use fibonacci for both the server and the client. That's probably why that version of the code does "work".
| | 3 | No.3 Revision |
ModeActionServer server("mode_server");
and
Client client("mode_client",true);true);
If I'm not mistaken, the first argument to the ctor would be the namespace the client uses to communicate with the server (docs).
You set that to mode_server for the server, but to mode_client for the client.
That would make them unable to find each other, causing the client to wait for the server to come up.
The example server and client you mention use fibonacci for both the server and the client. That's probably why that version of the code does "work".
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
