Closed invidia0 closed 1 year ago
Hi @invidia0,
I consider only Humble, so there is no wonder if the build fails with Foxy. There can be other problems other than the msgs with Foxy because there are many differences around ros2_control between Foxy and Humble.
Hi @mayataka,
thank you for you response! I imagined that! However i just saw there's a foxy branch, does it make sense to consider it or is it better to switch to humble and take the last branch? Thank you in advice!
Hi @invidia0,
I consider only Humble, so there is no wonder if the build fails with Foxy. There can be other problems other than the msgs with Foxy because there are many differences around ros2_control between Foxy and Humble.
@invidia0 Foxy branch is a deprecated branch. It is no longer maintained and it might not work.
Hi,
thank you very much for providing this repo! Great work! Anyway i have an issue regarding the field names of the msgs you defined in the unitree_msgs package. Basically ROS2 says that he wants the field names declared in lower case without any upper case as you instead defined.
The problems are the "J" and rewriting the msg with them in lower case solves the problem but obviously it generates others in the unitree_hardware package. So i am wondering how did you manage to build the package? I am building this package on Foxy but also Humble mentions this constraint on the field names.
Thank you in advice!