-
Notifications
You must be signed in to change notification settings - Fork 15
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
socket error on rm 65 arm #19
Comments
Is the ROS package version used 1.3.0? Our ROS package has been tested on controller version 1.6.7, but it has not been tested on higher versions. If the controller version of the robotic arm is higher than 1.6.7, it is recommended to roll back to 1.6.7 and try it out first. Hope it's helpful to you |
thank you for your reply! I pulled the latest code on humble branch in this repo yesterday, is that version 1.3.0 or I should pull from tag? How can I check the version of controller, or how can I change it? I checked the robot and got [Plan_version V6.0.4] [Ctrl_version V7.0.4] [Real_time Kernal V2.0.4] [Joint Vd4.6.4] [End interface V1.7.2]. Should I downgrade the hardware and how can I downgrade them? I'm not using virtual machine, directly connect robot with a ubuntu 22.04 machine. Is there any settings for udp connection needs to be turned on? |
I confirm the ros2 version. I think it is 1.3.0. or can you send me a arm controller upgrade package? I scaned all the ports on robot cant find a 8089 udp port, why does this robot using two ip address, I cant connect to the 192.168.1.10 even I connect the robot directly. |
Great Project!
I met some socket transmission error when using rm_65_bringup
I got error from this line and seemed robot can be connect
I changed the udp address in config file with the same ip address, and port 8089 I confused if it is right
I can send socket message through python to this port but nothing received. If it is caused by api version.
The text was updated successfully, but these errors were encountered: