Skip to content

Conversation

@Woojin-Crive
Copy link
Member

No description provided.

@Woojin-Crive Woojin-Crive requested a review from robotpilot June 23, 2025 07:33
@Woojin-Crive Woojin-Crive added the bump Increase the version number to release label Jun 23, 2025
@github-project-automation github-project-automation bot moved this to 🌱 Todo in Platform Jun 23, 2025
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @Woojin-Crive, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the dynamixel_hardware_interface package to version 1.4.8, primarily to introduce support for a new OMY series Dynamixel model (omy_end_rh_p12_rn) and to enhance the hardware interface's startup procedure. The changes ensure that goal positions are synchronized before motor torque is enabled, and generalize the underlying Dynamixel communication to support more flexible indirect write operations for various data types.

Highlights

  • New OMY Model Support: A new Dynamixel model, omy_end_rh_p12_rn (ID 231), has been introduced. Its specific control table and type information are now defined in a dedicated model file (omy_end_rh_p12_rn.model), allowing for better modularity and support for this new hardware configuration. This involved refactoring omy_end.model to generalize it by removing specific control table entries and type info, which were then moved to the new model file.
  • Goal Position Synchronization Before Torque Enable: The hardware interface startup sequence in dynamixel_hardware_interface.cpp has been modified to explicitly synchronize goal positions for Dynamixels by calling dxl_comm_->WriteMultiDxlData() after calculating joint to transmission values and before enabling torque. This ensures that the motors start from a desired position, which is particularly relevant for the new OMY sync table feature, and removes a previously fixed 500ms sleep.
  • Generalized Indirect Write Operations: The SetDxlValueToSyncWrite() and SetDxlValueToBulkWrite() methods in dynamixel.cpp have been enhanced. They now support writing various data sizes (1, 2, or 4 bytes) for indirect addresses, making the communication with Dynamixels more flexible and robust for different control table items beyond just goal_current.
  • Package Version Update: The package version has been incremented from 1.4.7 to 1.4.8 in package.xml and documented in CHANGELOG.rst, reflecting the new features and improvements introduced in this pull request.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@Woojin-Crive Woojin-Crive moved this from 🌱 Todo to 📝 Pull Request in Platform Jun 23, 2025
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

The pull request updates the dynamixel_hardware_interface package to version 1.4.8, adding a new model for OMY to use virtual_dxl and synchronizing goal positions before enabling torque for OMY sync table features. The code changes include modifications to the dynamixel.cpp and dynamixel_hardware_interface.cpp files to improve data handling and synchronization.

Comment on lines +1837 to 1851
} else {
if (indirect_info_write_[comm_id].item_size.at(item_index) == 4) {
int32_t value = static_cast<int32_t>(data);
param_write_value[added_byte + 0] = DXL_LOBYTE(DXL_LOWORD(value));
param_write_value[added_byte + 1] = DXL_HIBYTE(DXL_LOWORD(value));
param_write_value[added_byte + 2] = DXL_LOBYTE(DXL_HIWORD(value));
param_write_value[added_byte + 3] = DXL_HIBYTE(DXL_HIWORD(value));
} else if (indirect_info_write_[comm_id].item_size.at(item_index) == 2) {
int16_t value = static_cast<int16_t>(data);
param_write_value[added_byte + 0] = DXL_LOBYTE(value);
param_write_value[added_byte + 1] = DXL_HIBYTE(value);
} else if (indirect_info_write_[comm_id].item_size.at(item_index) == 1) {
param_write_value[added_byte] = static_cast<uint8_t>(data);
}
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Consider adding a default case to the if/else if block to handle unexpected item_size values. This can help prevent unexpected behavior if a new item size is introduced in the future.

Suggested change
} else {
if (indirect_info_write_[comm_id].item_size.at(item_index) == 4) {
int32_t value = static_cast<int32_t>(data);
param_write_value[added_byte + 0] = DXL_LOBYTE(DXL_LOWORD(value));
param_write_value[added_byte + 1] = DXL_HIBYTE(DXL_LOWORD(value));
param_write_value[added_byte + 2] = DXL_LOBYTE(DXL_HIWORD(value));
param_write_value[added_byte + 3] = DXL_HIBYTE(DXL_HIWORD(value));
} else if (indirect_info_write_[comm_id].item_size.at(item_index) == 2) {
int16_t value = static_cast<int16_t>(data);
param_write_value[added_byte + 0] = DXL_LOBYTE(value);
param_write_value[added_byte + 1] = DXL_HIBYTE(value);
} else if (indirect_info_write_[comm_id].item_size.at(item_index) == 1) {
param_write_value[added_byte] = static_cast<uint8_t>(data);
}
}
} else {
if (indirect_info_write_[comm_id].item_size.at(item_index) == 4) {
int32_t value = static_cast<int32_t>(data);
param_write_value[added_byte + 0] = DXL_LOBYTE(DXL_LOWORD(value));
param_write_value[added_byte + 1] = DXL_HIBYTE(DXL_LOWORD(value));
param_write_value[added_byte + 2] = DXL_LOBYTE(DXL_HIWORD(value));
param_write_value[added_byte + 3] = DXL_HIBYTE(DXL_HIWORD(value));
} else if (indirect_info_write_[comm_id].item_size.at(item_index) == 2) {
int16_t value = static_cast<int16_t>(data);
param_write_value[added_byte + 0] = DXL_LOBYTE(value);
param_write_value[added_byte + 1] = DXL_HIBYTE(value);
} else if (indirect_info_write_[comm_id].item_size.at(item_index) == 1) {
param_write_value[added_byte] = static_cast<uint8_t>(data);
} else {
// Handle unexpected item size
fprintf(stderr, "[ID:%03d] Unexpected item size: %d\n", ID, indirect_info_write_[comm_id].item_size.at(item_index));
}
}

Comment on lines +2070 to 2084
} else {
if (indirect_info_write_[comm_id].item_size.at(item_index) == 4) {
int32_t value = static_cast<int32_t>(data);
param_write_value[added_byte + 0] = DXL_LOBYTE(DXL_LOWORD(value));
param_write_value[added_byte + 1] = DXL_HIBYTE(DXL_LOWORD(value));
param_write_value[added_byte + 2] = DXL_LOBYTE(DXL_HIWORD(value));
param_write_value[added_byte + 3] = DXL_HIBYTE(DXL_HIWORD(value));
} else if (indirect_info_write_[comm_id].item_size.at(item_index) == 2) {
int16_t value = static_cast<int16_t>(data);
param_write_value[added_byte + 0] = DXL_LOBYTE(value);
param_write_value[added_byte + 1] = DXL_HIBYTE(value);
} else if (indirect_info_write_[comm_id].item_size.at(item_index) == 1) {
param_write_value[added_byte] = static_cast<uint8_t>(data);
}
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Consider adding a default case to the if/else if block to handle unexpected item_size values. This can help prevent unexpected behavior if a new item size is introduced in the future.

Suggested change
} else {
if (indirect_info_write_[comm_id].item_size.at(item_index) == 4) {
int32_t value = static_cast<int32_t>(data);
param_write_value[added_byte + 0] = DXL_LOBYTE(DXL_LOWORD(value));
param_write_value[added_byte + 1] = DXL_HIBYTE(DXL_LOWORD(value));
param_write_value[added_byte + 2] = DXL_LOBYTE(DXL_HIWORD(value));
param_write_value[added_byte + 3] = DXL_HIBYTE(DXL_HIWORD(value));
} else if (indirect_info_write_[comm_id].item_size.at(item_index) == 2) {
int16_t value = static_cast<int16_t>(data);
param_write_value[added_byte + 0] = DXL_LOBYTE(value);
param_write_value[added_byte + 1] = DXL_HIBYTE(value);
} else if (indirect_info_write_[comm_id].item_size.at(item_index) == 1) {
param_write_value[added_byte] = static_cast<uint8_t>(data);
}
}
} else {
if (indirect_info_write_[comm_id].item_size.at(item_index) == 4) {
int32_t value = static_cast<int32_t>(data);
param_write_value[added_byte + 0] = DXL_LOBYTE(DXL_LOWORD(value));
param_write_value[added_byte + 1] = DXL_HIBYTE(DXL_LOWORD(value));
param_write_value[added_byte + 2] = DXL_LOBYTE(DXL_HIWORD(value));
param_write_value[added_byte + 3] = DXL_HIBYTE(DXL_HIWORD(value));
} else if (indirect_info_write_[comm_id].item_size.at(item_index) == 2) {
int16_t value = static_cast<int16_t>(data);
param_write_value[added_byte + 0] = DXL_LOBYTE(value);
param_write_value[added_byte + 1] = DXL_HIBYTE(value);
} else if (indirect_info_write_[comm_id].item_size.at(item_index) == 1) {
param_write_value[added_byte] = static_cast<uint8_t>(data);
} else {
// Handle unexpected item size
fprintf(stderr, "[ID:%03d] Unexpected item size: %d\n", ID, indirect_info_write_[comm_id].item_size.at(item_index));
}
}

@robotpilot robotpilot merged commit 5522a48 into humble Jun 23, 2025
25 checks passed
@github-project-automation github-project-automation bot moved this from 📝 Pull Request to 🚩Done in Platform Jun 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bump Increase the version number to release

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

4 participants