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

rosservice set_rate available in docker/CloudSim? #905

Closed
m3d opened this issue Apr 25, 2021 · 6 comments
Closed

rosservice set_rate available in docker/CloudSim? #905

m3d opened this issue Apr 25, 2021 · 6 comments

Comments

@m3d
Copy link
Contributor

m3d commented Apr 25, 2021

Hello,
I am trying to reduce frame rate for X500 drone, both front camera (~60Hz) and up/down RGBD cameras (~30Hz). According to #791 I am trying to call rosservice list | grep set_rate in solution docker but the output is empty.
I am using the latest docker images (2021-04-22). Is there some change needed on solution docker side?
thanks a lot
Martin

@peci1
Copy link
Collaborator

peci1 commented Apr 25, 2021

X500 doesn't support the ROS-side set_rate (yet). Each model has to explicitly add the set_rate ROS service bridges to support it. You can probably try to add it in a pull request, though.

@peci1
Copy link
Collaborator

peci1 commented Apr 25, 2021

You can tell which models support it by searching vehicle_topics.launch. If it contains set_rate bridges or uses the helpers from subt_ros/launch/models_common, it should.

@m3d
Copy link
Contributor Author

m3d commented Apr 26, 2021

@peci1 thanks for info

@peci1
Copy link
Collaborator

peci1 commented Apr 26, 2021

Fixed in #906, thanks @petrlmat ;)

@hilario
Copy link
Contributor

hilario commented May 5, 2021

Is there an approximate release date for an updated docker image with these changes?

@m3d
Copy link
Contributor Author

m3d commented May 18, 2021

The set_rate for X500 is available in 2021-05-14 release. It works for me on CloudSim although I am still getting black or mixed images, so I believe it is some other problem on our side. I am closing this issue, thanks for help!

118685128-1e6ffb00-b803-11eb-977f-3c51ce5f3ce9

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

3 participants