Ros2#20
Conversation
|
This is great, thanks. I'll circle back around to review this as soon as I can. Merging into foxy is fine, we can re-arrange branches once this is released anyways. |
| } | ||
|
|
||
|
|
||
| if (tracker->calculate_twist_and_accel_ && tracker->previous_message_arrived_) |
There was a problem hiding this comment.
This is an interesting feature! Honestly I think it probably belongs as another node in the system, consuming 'pose' messages and spitting out 'twist' and/or 'accel'. that keeps the VRPN client 'simpler' in that it's responsible only for adapting the incoming data.
There was a problem hiding this comment.
Agree completely. I will remove that func from this package and some more commits to PR
I wish I could remember, but I imagine they existed for a reason. I haven't had access to a VICON system in years. |
|
How can I install the VRPN dependency? I'm having this when I try to build with colcon:
|
|
@evbernardes You should install it from here https://github.com/vrpn/vrpn |
|
@AlexKaravaev thanks for the reply! Is there a special way I have to install in order for colcon to be able to use the library to correctly compile using it? |
|
@evbernardes For me it was working with usual |
|
@AlexKaravaev I was definitely overthinking it, thanks! Just a little thing though: I installed tf2 with #include "tf2_geometry_msgs/tf2_geometry_msgs.hpp" -> #include "tf2_geometry_msgs/tf2_geometry_msgs.h And then it compiled! |
|
@evbernardes Which ros-version and ubuntu you are using? Because in rolling it seems like with latest tf2 it explicitly says, that .h are deprecated |
|
I see! I'm using galactic with Ubuntu 20.04, which is supposed to be the latest LTS release. I tried to install everything I can with apt to minimize these kinds of problems but I'm starting to think it wasn't the best option |
|
Any updates on this one? I can see there is |
Hi!
This is latest ros2 sync. I have tested it with ros2 rolling distribution and Optitrack setup with Motive with 2 distinct rigid bodies. Mostly it based on @zeroos PR #16 , but I've added also twist and accel publishing and also some changes described below.
Notable logical changes I made:
I added explicit calculation of twist and accel based on previous messages
Removed multiple sensor support. To be honest, I just don't know how it works and what are sensor id's and therefore I deleted it. If you can provide me some info about that, I can commit changes later.
Also, I think it should not be merged into foxy-devel branch, but instead we should create separate branch ros2 to track latest rolling version updates. But since I don't have the rights to create new branch I submitted PR to existing branch