Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mismatch in service call from rosbridge protocol #192

Open
connormbrooks opened this issue Aug 10, 2021 · 0 comments
Open

Mismatch in service call from rosbridge protocol #192

connormbrooks opened this issue Aug 10, 2021 · 0 comments

Comments

@connormbrooks
Copy link

connormbrooks commented Aug 10, 2021

Hi, I have encountered errors when creating ROS service calls using a 3rd party application (ROS#) that I have traced to what appears to be a mismatch with the rosbridge protocol being implemented here. The issue here is the list of expected parameters for a call_service op. The rosbridge protocol does not expect a type parameter (see: here); however, the type parameter is referenced in the ros2-web-bridge/lib/bridge.js script here).

This causes the following error when attempting to call a service according to the rosbridge protocol specifications:

JSON command received: {"service":"/rosapi/get_param","args":{"name":"/rosdistro","default":"default"},"fragment_size":2147483647,"compression":"none","op":"call_service","id":"/rosapi/getparam:0"}
Response: {"op":"status","level":"error","msg":"call_service: TypeError: Cannot read property 'indexOf' of undefined","id":"/rosapi/get_param:0"}

I have verified that this TypeError is being caused by attempting to pass in command.type to the _exractServiceType function in bridge.js

Thanks in advance for your help!

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

No branches or pull requests

1 participant