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

ROS CLI - unable to determine type of service #2

Closed
MKervo opened this issue Mar 19, 2020 · 2 comments
Closed

ROS CLI - unable to determine type of service #2

MKervo opened this issue Mar 19, 2020 · 2 comments

Comments

@MKervo
Copy link

MKervo commented Mar 19, 2020

Hi,
Thanks for your work ! I was looking how to build lightweight nodes in Go.

I'm using ROS Melodic
Right now, I'm trying to implement a basic service client/provider. I did as the examples says.
But I can't make them communicate with each others.

Error: lookupService: server returned an error (-1): no provider

Also, when I'm using rosnode and rosservice and use list I've got a double slash prefix.

$ rosnode list
//node_name
$ rosservice list
//service_name

I can't call them or get any infos. They seems to be unknown or corrupt in some way.

Any ideas what's going on ?

@aler9
Copy link
Member

aler9 commented Mar 20, 2020

Hello, i wasn't able to replicate the bug. I did the following:

  1. in one terminal i launched ROS melodic

    docker run --rm -it --network=host --name=ros ros:melodic-ros-core-bionic roscore
    
  2. in another terminal i launched the serviceprovider.go example

    docker run --rm -it --network=host golang:1.13 sh -c "git clone https://github.com/aler9/goroslib && cd goroslib && go run examples/serviceprovider.go"
    
  3. in another terminal i checked rosnode list and rosservice list

    docker exec -it ros bash -c "source /opt/ros/melodic/setup.bash && rostopic list && rosservice list"
    

the output is

/test_srv

can you provide the .go source you used to perform the test?

@github-actions
Copy link

This issue is being locked automatically because it has been closed for more than 6 months.
Please open a new issue in case a similar problem arises.

@github-actions github-actions bot locked and limited conversation to collaborators Dec 31, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants