Skip to content
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

MoveIt error "Requesting initial scene failed" #128

Closed
airizar98 opened this issue Dec 13, 2024 · 8 comments
Closed

MoveIt error "Requesting initial scene failed" #128

airizar98 opened this issue Dec 13, 2024 · 8 comments

Comments

@airizar98
Copy link

We are working with an H2017 robot. When we launch "dsr_bringup2_moveit", it connects correctly to the robot, but a warning appears in RVIZ under PlanningScene and MotionPlanning, showing the following message: "Requesting initial scene failed." The issue is that it does not receive the robot's current position; in RVIZ, all axes appear at 0º. When we move the axes in RVIZ and try to plan and execute, it doesn’t work.
However, when we launch the command "dsr_bringup2_rviz", the robot's position is displayed correctly. In this case, though, since the launch does not execute MoveIt, we get an error when trying to add MotionPlanning.

@song-ms
Copy link
Contributor

song-ms commented Dec 16, 2024

@airizar98 ,

Thank you for your inquiry. We have newly updated the features related to MoveIt. Please ensure that the controller version is set to v2.12 or v2.12.1, and update accordingly before use.

@airizar98
Copy link
Author

Thank you for the response. We updated the robot’s version and the ROS2 repository, and now MoveIt successfully plans paths. However, when we press "Execute" on the real robot (inside RVIZ), the robot starts making strange noises and barely moves. Errors related to dsr_hw_interface2 appear in the command line, specifically:
“Target limit velocity limit error, [2] joint, target limit velocity [100.000 deg/s], limit velocity [80.000 deg/s].”
Also appear issues regarding acceleration limits.

We modified the h2017 joint_limits.yaml by setting all velocity and acceleration limits to false, but the issue persists.
DoosanH2017

@leeminju531
Copy link
Contributor

leeminju531 commented Dec 20, 2024

@airizar98

Could we know your update rate of controller manager in dsr_contrller2/config/dsr_controller2.yaml?

@airizar98
Copy link
Author

We have the same value:
DoosanHZ

@song-ms
Copy link
Contributor

song-ms commented Dec 26, 2024

@airizar98

Could you please delete all the build install logs in your workspace before building and try building again?

Also, could you let me know if the LED is in blinking mode in auto mode(white) during "execute" after the robot boots up?

@leeminju531
Copy link
Contributor

Dear @airizar98
If the issue still persists, could you please try it on #140 and let us know the results?

@airizar98
Copy link
Author

Dear @leeminju531 ,
The robot works correctly with the latest updates. However, it is unable to load the lates h2017 URDF version. I had to revert to the previous version, even though it is not completely correct.
Thank you very much for the help.

@doosan-robotics
Copy link
Owner

If there are any further issues, please provide an update.
Otherwise, this issue will be closed.

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

No branches or pull requests

4 participants