You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 19, 2023. It is now read-only.
In some use cases the robot will move out of the reach of the paired android device. We had such a use case during ICRA, when wanted the turtlebot to follow people and robots even outside the reach of our AP. This only worked, if we started the robot app manually on the robot.
Hence, t would be nice, if
the robot app keeps running, i.e. not being shutdown because connection to the paired master is lost
on re-connection the remocon detects that a robot app is running and starts the corresponding android app without the robot app being shutdown
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In some use cases the robot will move out of the reach of the paired android device. We had such a use case during ICRA, when wanted the turtlebot to follow people and robots even outside the reach of our AP. This only worked, if we started the robot app manually on the robot.
Hence, t would be nice, if
The text was updated successfully, but these errors were encountered: