Skip to content

[WIP][gimbalrotor] suport all type of gimbalrotor #703

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

Open
wants to merge 140 commits into
base: master
Choose a base branch
from

Conversation

sugikazu75
Copy link
Member

@sugikazu75 sugikazu75 commented May 16, 2025

What is this

Support gimbalrotor package.
This branch is made from #687 and picked spinal unrelated commits from #700
And then, support gimbal control in spinal with spinal4.1

TODO

  • Check with all type of robots with real machine (after new spinal is arrived.)
  • birotor (kondoservo x 2)
  • trirotor (kondoservo x 3)
  • beale (kondoservo x 4)
  • beatle (dynamixel x 4)
  • dragonfly (dynamixel x 6)

sugikazu75 and others added 30 commits April 26, 2023 19:00
…or_stm32H7

Change the structure of kondo servo interface to support reading servo postion via DMA.
…ommunicate with multipe types of servo (e.g. dynamixel, kondo).
@sugikazu75 sugikazu75 force-pushed the PR/develop/gimbalrotor_rebase branch from 8e84cf2 to e98ea3e Compare May 16, 2025 08:57
sugikazu75 and others added 9 commits May 16, 2025 17:58
…oordinate following dragon's implementation.
* [Spinal][Dynamixle]Enable boardless control for dynamixel servo

* [Spinal][Dynamixle] Fix the error to accomodate original best technology board for dynamixel servo XL330-M077-T

* [Spinal][Dynamixle] Fix a spelling error happened in branch migration

* [GA] add option --include-eol-distros for rosdep update (jsk-ros-pkg#706)

* [GA] add option --include-eol-distros for rosdep update

* [GA][firmware] add --include-eol-distros option

* [GA] use latest key

* update readme

* [Navigation][Trajectory] enable to set the duration when generating a trajectory (jsk-ros-pkg#707)

* [Navigation] support to receive the desired goal timestamp from the subscriber of target pose

* [Navigation] support to receive a path (multiple waypoints), and also support the visulization of waypoints using markers

---------

Co-authored-by: Moju Zhao <[email protected]>

* [Navigation][Trajectory] enable to support multiple waypoints for generating new trajectory  (jsk-ros-pkg#708)

* [Navigation] support to receive the desired goal timestamp from the subscriber of target pose

* [Navigation] support to receive a path (multiple waypoints), and also support the visulization of waypoints using markers

---------

Co-authored-by: Moju Zhao <[email protected]>

* [Navigation][Trajectory] use the current pose and velocity for the start point  (jsk-ros-pkg#709)

* [Navigation] support to receive the desired goal timestamp from the subscriber of target pose

* [Navigation] support to receive a path (multiple waypoints), and also support the visulization of waypoints using markers

* [Navigation][Trajectory] revert: use the current pose (x,y,z and yaw) instead of the last target pose foe the start point

---------

Co-authored-by: Moju Zhao <[email protected]>

* [estimation] identify the name space std for std::array (jsk-ros-pkg#705)

* [Hydurs_XI] update the motor/propeller configuration (jsk-ros-pkg#701)

Co-authored-by: Kotaro Kaneko <[email protected]>

---------

Co-authored-by: fjiwrogno <[email protected]>
Co-authored-by: Sugihara Kazuki <[email protected]>
Co-authored-by: 趙 漠居(Zhao, Moju) <[email protected]>
Co-authored-by: Moju Zhao <[email protected]>
Co-authored-by: Yicheng Chen <[email protected]>
Co-authored-by: Kotaro Kaneko <[email protected]>
@tongtybj
Copy link
Collaborator

tongtybj commented Jul 6, 2025

Please merge the laster origin/master, which contains several patch commits about the connection between dynamixel and spinal

@sugihara-16
Copy link
Collaborator

sugihara-16 commented Jul 6, 2025

@tongtybj Please wait to merge this PR until we complete enough real machine experiments. Actually, we have already found some corner cases of current version. I assume the verifications will be completed in this week.

@sugikazu75
Copy link
Member Author

@sugihara-16 Can I format all *.h and *.cpp files in gimbalrotor package before merging?

@sugihara-16
Copy link
Collaborator

@sugikazu75 Yes, for sure.

@tongtybj
Copy link
Collaborator

tongtybj commented Jul 7, 2025

@sugikazu75

How did you format the code?

@sugikazu75
Copy link
Member Author

@sugikazu75

How did you format the code?

Activate pre-commit with .pre-commit-config in this repo, and formated.

@tongtybj
Copy link
Collaborator

tongtybj commented Jul 7, 2025

What kind a clang format rule did you use?

@sugikazu75
Copy link
Member Author

In my understanding, I believe .clang-format at the root of this repo is used.

@tongtybj
Copy link
Collaborator

tongtybj commented Jul 7, 2025

@Li-Jinjie

In my understanding, I believe .clang-format at the root of this repo is used.

Is https://github.com/jsk-ros-pkg/jsk_aerial_robot/blob/master/.clang-format based on ros rule?

@sugikazu75
Copy link
Member Author

At least, it seems to be almost same with https://github.com/PickNikRobotics/roscpp_code_format/blob/master/.clang-format

$ diff <(curl -s https://raw.githubusercontent.com/PickNikRobotics/roscpp_code_format/refs/heads/master/.clang-format) <(curl -s https://raw.githubusercontent.com/jsk-ros-pkg/jsk_aerial_robot/refs/heads/master/.clang-format)
54c54
<   AfterClass: 'true'
---
>   AfterClass: true
56,63c56,63
<   AfterEnum : 'true'
<   AfterFunction : 'true'
<   AfterNamespace : 'true'
<   AfterStruct : 'true'
<   AfterUnion : 'true'
<   BeforeCatch : 'true'
<   BeforeElse : 'true'
<   IndentBraces : 'false'
---
>   AfterEnum: true
>   AfterFunction: true
>   AfterNamespace: true
>   AfterStruct: true
>   AfterUnion: true
>   BeforeCatch: true
>   BeforeElse: true
>   IndentBraces: false

@Li-Jinjie
Copy link
Collaborator

@Li-Jinjie

In my understanding, I believe .clang-format at the root of this repo is used.

Is https://github.com/jsk-ros-pkg/jsk_aerial_robot/blob/master/.clang-format based on ros rule?

Yes, I remember at that time I tried to set the rule with ROS as much as possible.

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

Successfully merging this pull request may close these issues.

4 participants