-
Notifications
You must be signed in to change notification settings - Fork 151
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
Also require primary deadman for arm teleop #92
Conversation
@moriarty Did you want this same logic with the head teleop? |
Tested and verified this works with Fetch3! Ready for review @moriarty Offline we discussed the head teleop, and agreed it was not a safety concern like the arm is. I cherry picked my change onto the branch that was checked out (but made a new branch off that, namely: https://github.com/erelson/fetch_ros/tree/tf2-nav-melodic-devel_with-safer-teleop). The robot is still set up in this manner. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was surprised the arm was safer today 👍
@erelson That's strange... this was an open PR, so I preformed a squash-and-merge and just adjusted your commit message... and I now see the two original commits were already in melodic-devel? |
#61 was merged into : 0.7.14 0.7.13 0.7.12 0.7.11 Should this be back-ported to indigo? |
I have no idea what happened there. My local melodic-devel didn't have the commits so I'm pretty sure I didn't force push them 😬 . Making backport. |
I believe of the above releases, only 0.7.14 is one we released, but I didn't check. |
* Require primary dead-man for arm teleop, along with with the angular or linear selector button.
Not tested yet.
Will also likely backport to indigo-devel too.