-
Notifications
You must be signed in to change notification settings - Fork 13.6k
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
microRTPS bridge: uORB RTPS ID mandatory; allow pub/sub for multi-topics/alias msgs #12137
Conversation
We have a SITL test, unrelated with this PR, continuously failing: http://ci.px4.io:8080/blue/organizations/jenkins/PX4_misc%2FFirmware-SITL_tests/detail/PR-12137/2/pipeline. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you try to reduce the amount of if (alias):
... else
... to a combined solution where possible?
364b0c9
to
b76aacb
Compare
…sub code for multi-topics/aliased msgs
f445cb2
to
0797d6b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving, while keeping in mind that we'll need to simplify (for instance not having to specify the alias, but infer it from the topic definition, and use less cmake manipulations).
Will be checking that further. Thanks Beat! |
Describe problem solved by the proposed pull request
Following the works on the microRTPS bridge, makes sense that all added uORB messages should have their respective RTPS ID allocated, even if they are not used on the bridge.
UPDATE: I updated this PR to include a major structural change that allows us to use multi-topic msgs, meaning, alias msgs as
vehicle_visual_odometry
.