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

set motion_possible to true only of robot can be actually moved #2

Merged
merged 3 commits into from
Apr 20, 2020

Conversation

fmauch
Copy link

@fmauch fmauch commented Apr 14, 2020

I think it does make sense to add this little check. Otherwise motion_possible will be true also if the robot is actually switched off.

@@ -695,10 +695,14 @@ void HardwareInterface::extractRobotStatus()
{
robot_status_resource_.motion_possible = TriState::FALSE;
}
else
else if (robot_mode_ == ur_dashboard_msgs::RobotMode::RUNNING || robot_mode_ == ur_dashboard_msgs::RobotMode::BACKDRIVE)

Choose a reason for hiding this comment

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

Can the driver command motion if the robot is in BACKDRIVE mode?

Copy link
Author

Choose a reason for hiding this comment

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

technically, I think it could. By putting the robot into freedrive mode, it can be moved physically. Putting the robot into freedrive mode would require sending script code to the robot manually.

@gavanderhoorn: Would you suggest to remove that edge case and only use RobotMode::RUNNING?

Choose a reason for hiding this comment

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

I would indeed remove it.

motion_possible should reflect whether it is possible to command the robot from the ROS driver/component "as-is" (ie: in the state it currently is in).

That would not include hypotheticals I believe.

@axelschroth axelschroth merged commit e03bb3f into isys-vision:robot_status Apr 20, 2020
cjue pushed a commit that referenced this pull request Oct 6, 2023
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.

3 participants