-
Notifications
You must be signed in to change notification settings - Fork 9
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
No data being streamed on topics #11
Comments
Thanks for the report, could you post a screenshot of your streaming settings in Motive? |
From memory I think you need “labelled markers” on as well or something,
let me know if any of those fix it.
On 13/02/2021, at 1:11 AM, ralfroemer <notifications@github.com> wrote:
Thanks for the quick response, here are the settings:
[image: Unbenannt]
<https://user-images.githubusercontent.com/78913851/107766434-befddd00-6d33-11eb-9981-50d5133e6dff.PNG>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#11 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABPBQCYCO6XACJAZR4IITQ3S6ULHDANCNFSM4XO3Y6WQ>
.
|
@ralfroemer were you able to solve this error? |
Has anyone solved this? |
Nope, but I have created a new package with more features for ros1 if would you like to use for For ros2 you can follow this package but its WIP |
Thank you for your reply, will try it |
Environment
Motive version: 2.1.1
ROS distribution: Melodic
Operating system: Ubuntu 18.04.5
Python version: 2.7.17
natnet_ros
versionnatnet_ros
branch: masternatnet_ros
commit: a859adaFirst of all: Thank you for creating this package which helped me a lot already.
This is not a bug report, in fact there is not even an error message. When I run
a connection between the ROS PC and the Motive PC seems to be correctly established, because all the topics are listed:
However, no motive data is being published on the topics, i.e.
returns nothing. The same is true for all the other topics. Since the ball is correctly tracked in Motive, I assume that the problem has to be somewhere in the data streaming. Unfortunately, I have no idea where to search the error, because obviously the streaming of the model definitions works fine. Otherwise, the topics would not be generated.
I would be very glad for any advice you could give me. Thanks in advance!
The text was updated successfully, but these errors were encountered: