ROS Resources: Documentation | Support | Discussion Forum | Service Status | Q&A


Safe Teleop
It is a local planner which works on the top of a Teleop, and prevents the robot from crashing into the obstacle even if the user input (Teleop) is asking it to crash.

Right now, it uses mouse-teleop for user input and rosbot with Velodyne (VLP-16) for simulation.

Check out its video:

Try it out at mowito-safe-teleop.
(the email is needed for registration, so we can see how many people are actually interested in it. We won’t spam :blush: )

Right now it is just for ROS Melodic (getting build errors with kinetic). Will release the kinetic version in a few hours.

We NEED your feedback, to improve and release it.


As a first feedback: This package has a very atypical installation procedure. First the email, then an installation script which installs binaries.

Typically you can either clone a repo and compile yourself or use package from the ROS build servers. Both these methods we have in place and keep us up-to-date.

This is already a large barrier for us to use your package, the maintenance burden is large so other sub-optimal packages might still be prefered.

1 Like

Thanks for the feedback. That makes sense. Email is indeed the barrier.
I will remove the email part. And will work on putting it on build farms.

do you know any way I can do it, without releasing the source code?

Rather use:

1 Like

Hi, what version of Ubuntu are you using?

Ubuntu 18, ros Melodic


Awesome! assissted teleop is doing the same thing as safe teleop, but with trajectory planner ROS ( we use different controller/local planner).
I didn’t know about its existence, thanks a ton!

As per @Timple advise I have removed the email registration.

You don’t need to register or even visit the website.

here are the updated steps:

  • clone the debians (still need to figure out how to deploy with apt)
    git clone -b melodic ~/safe_teleop

  • and then run the setup file to install the debians and dependencies. You can do it manually also, all the debians are in the debians folder.
    cd ~/safe_teleop && ./

  • run the launch file
    roslaunch ~/safe_teleop/launch/maxl_sim.launch

Enjoy! Do provide the feedback!

To remove the requirement for nonstandard setup, you could introduce this logic into a CMake script, similar to how the _vendor packages work in ROS2. That way, you can provide this wrapper package to download your proprietary binaries without requiring any nonstandard setup instructions.

1 Like

thats an interesting idea. I will try it out. Thanks bud!