Conversation
Summary of ChangesHello @kjaved0, 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 addresses a critical issue where serial port baud rate configuration failed on certain Linux systems, specifically Ubuntu 25.10 when using CH341/CH340 devices. The change ensures robust serial communication by adopting standard POSIX functions ( Highlights
Using Gemini Code AssistThe 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 by creating a comment using either
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 Limitations & Feedback Gemini Code Assist 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. 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
|
There was a problem hiding this comment.
Code Review
This pull request improves baud rate setting on Linux by using the more portable cfsetispeed and cfsetospeed functions. This is a good change that should improve compatibility as described. I have one suggestion to add error handling for these new function calls to make the implementation more robust. Additionally, it appears the same logic exists in the C language implementation of the SDK (c/src/dynamixel_sdk/port_handler_linux.c). The setupPortLinux function in that file should also be updated with this new method for setting the baud rate to maintain consistency between the C and C++ APIs.
| cfsetispeed(&newtio, cflag_baud); | ||
| cfsetospeed(&newtio, cflag_baud); |
There was a problem hiding this comment.
The return values of cfsetispeed and cfsetospeed should be checked to ensure the baud rate was set successfully. These functions return -1 on error. Failing to set the baud rate will cause all subsequent communication to fail silently, which can be difficult to debug. It's better to fail early with a clear error message.
if (cfsetispeed(&newtio, cflag_baud) < 0 || cfsetospeed(&newtio, cflag_baud) < 0)
{
printf("[PortHandlerLinux::SetupPort] Error setting baud rate!\n");
return false;
}
On Ubuntu 25.10 running on framework desktop (Ryzen 395+) with CH341 / CH340, the way the original code sets the baud rate does not work.
Using cfsetospeed and cfsetispeed instead works as it should.