![]() |
lost_comms_recovery package from lost_comms_recovery repolost_comms_recovery |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 0.1.0 |
License | Unlicense |
Build type | CATKIN |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/danielsnider/lost_comms_recovery.git |
VCS Type | git |
VCS Version | master |
Last Updated | 2017-08-05 |
Dev Status | MAINTAINED |
CI status | Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Daniel Snider
Authors
- Daniel Snider
lost_comms_recovery
If your robot loses connection to the base station it will navigate to a configurable home.
Quick Start
- Install:
$ sudo apt-get install ros-kinetic-lost-comms-recovery
- Launch node:
$ roslaunch lost_comms_recovery lost_comms_recovery.launch
- Normal output:
$ roslaunch lost_comms_recovery lost_comms_recovery.launch ips_to_monitor:=192.168.190.136
[INFO] Monitoring base station on IP(s): 192.168.190.136.
[INFO] Connected to base station.
[INFO] Connected to base station.
...
[ERROR] No connection to base station.
[INFO] Connected to move_base.
[INFO] Executing move_base goal to position (x,y) 0.0, 0.0.
[INFO] Inital goal status: PENDING
[INFO] This goal has been accepted by the simple action server
[INFO] Final goal status: SUCCEEDED
[INFO] Goal reached.
Full documentation on wiki: http://wiki.ros.org/lost_comms_recovery
Changelog for package lost_comms_recovery
0.1.0 (2017-07-20)
- First release
Wiki Tutorials
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/lost_comms_recovery.launch
-
- ips_to_monitor [default: 192.168.1.2,192.168.1.3]
Messages
Services
Plugins
Recent questions tagged lost_comms_recovery at Robotics Stack Exchange
![]() |
lost_comms_recovery package from lost_comms_recovery repolost_comms_recovery |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 0.1.0 |
License | Unlicense |
Build type | CATKIN |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/danielsnider/lost_comms_recovery.git |
VCS Type | git |
VCS Version | master |
Last Updated | 2017-08-05 |
Dev Status | MAINTAINED |
CI status | Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Daniel Snider
Authors
- Daniel Snider
lost_comms_recovery
If your robot loses connection to the base station it will navigate to a configurable home.
Quick Start
- Install:
$ sudo apt-get install ros-kinetic-lost-comms-recovery
- Launch node:
$ roslaunch lost_comms_recovery lost_comms_recovery.launch
- Normal output:
$ roslaunch lost_comms_recovery lost_comms_recovery.launch ips_to_monitor:=192.168.190.136
[INFO] Monitoring base station on IP(s): 192.168.190.136.
[INFO] Connected to base station.
[INFO] Connected to base station.
...
[ERROR] No connection to base station.
[INFO] Connected to move_base.
[INFO] Executing move_base goal to position (x,y) 0.0, 0.0.
[INFO] Inital goal status: PENDING
[INFO] This goal has been accepted by the simple action server
[INFO] Final goal status: SUCCEEDED
[INFO] Goal reached.
Full documentation on wiki: http://wiki.ros.org/lost_comms_recovery
Changelog for package lost_comms_recovery
0.1.0 (2017-07-20)
- First release
Wiki Tutorials
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/lost_comms_recovery.launch
-
- ips_to_monitor [default: 192.168.1.2,192.168.1.3]
Messages
Services
Plugins
Recent questions tagged lost_comms_recovery at Robotics Stack Exchange
![]() |
lost_comms_recovery package from lost_comms_recovery repolost_comms_recovery |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 0.1.0 |
License | Unlicense |
Build type | CATKIN |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/danielsnider/lost_comms_recovery.git |
VCS Type | git |
VCS Version | master |
Last Updated | 2017-08-05 |
Dev Status | MAINTAINED |
CI status | Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Daniel Snider
Authors
- Daniel Snider
lost_comms_recovery
If your robot loses connection to the base station it will navigate to a configurable home.
Quick Start
- Install:
$ sudo apt-get install ros-kinetic-lost-comms-recovery
- Launch node:
$ roslaunch lost_comms_recovery lost_comms_recovery.launch
- Normal output:
$ roslaunch lost_comms_recovery lost_comms_recovery.launch ips_to_monitor:=192.168.190.136
[INFO] Monitoring base station on IP(s): 192.168.190.136.
[INFO] Connected to base station.
[INFO] Connected to base station.
...
[ERROR] No connection to base station.
[INFO] Connected to move_base.
[INFO] Executing move_base goal to position (x,y) 0.0, 0.0.
[INFO] Inital goal status: PENDING
[INFO] This goal has been accepted by the simple action server
[INFO] Final goal status: SUCCEEDED
[INFO] Goal reached.
Full documentation on wiki: http://wiki.ros.org/lost_comms_recovery
Changelog for package lost_comms_recovery
0.1.0 (2017-07-20)
- First release
Wiki Tutorials
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/lost_comms_recovery.launch
-
- ips_to_monitor [default: 192.168.1.2,192.168.1.3]
Messages
Services
Plugins
Recent questions tagged lost_comms_recovery at Robotics Stack Exchange
![]() |
lost_comms_recovery package from lost_comms_recovery repolost_comms_recovery |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 0.1.0 |
License | Unlicense |
Build type | CATKIN |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/danielsnider/lost_comms_recovery.git |
VCS Type | git |
VCS Version | master |
Last Updated | 2017-08-05 |
Dev Status | MAINTAINED |
CI status | Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Daniel Snider
Authors
- Daniel Snider
lost_comms_recovery
If your robot loses connection to the base station it will navigate to a configurable home.
Quick Start
- Install:
$ sudo apt-get install ros-kinetic-lost-comms-recovery
- Launch node:
$ roslaunch lost_comms_recovery lost_comms_recovery.launch
- Normal output:
$ roslaunch lost_comms_recovery lost_comms_recovery.launch ips_to_monitor:=192.168.190.136
[INFO] Monitoring base station on IP(s): 192.168.190.136.
[INFO] Connected to base station.
[INFO] Connected to base station.
...
[ERROR] No connection to base station.
[INFO] Connected to move_base.
[INFO] Executing move_base goal to position (x,y) 0.0, 0.0.
[INFO] Inital goal status: PENDING
[INFO] This goal has been accepted by the simple action server
[INFO] Final goal status: SUCCEEDED
[INFO] Goal reached.
Full documentation on wiki: http://wiki.ros.org/lost_comms_recovery
Changelog for package lost_comms_recovery
0.1.0 (2017-07-20)
- First release
Wiki Tutorials
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/lost_comms_recovery.launch
-
- ips_to_monitor [default: 192.168.1.2,192.168.1.3]
Messages
Services
Plugins
Recent questions tagged lost_comms_recovery at Robotics Stack Exchange
![]() |
lost_comms_recovery package from lost_comms_recovery repolost_comms_recovery |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 0.1.0 |
License | Unlicense |
Build type | CATKIN |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/danielsnider/lost_comms_recovery.git |
VCS Type | git |
VCS Version | master |
Last Updated | 2017-08-05 |
Dev Status | MAINTAINED |
CI status | Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Daniel Snider
Authors
- Daniel Snider
lost_comms_recovery
If your robot loses connection to the base station it will navigate to a configurable home.
Quick Start
- Install:
$ sudo apt-get install ros-kinetic-lost-comms-recovery
- Launch node:
$ roslaunch lost_comms_recovery lost_comms_recovery.launch
- Normal output:
$ roslaunch lost_comms_recovery lost_comms_recovery.launch ips_to_monitor:=192.168.190.136
[INFO] Monitoring base station on IP(s): 192.168.190.136.
[INFO] Connected to base station.
[INFO] Connected to base station.
...
[ERROR] No connection to base station.
[INFO] Connected to move_base.
[INFO] Executing move_base goal to position (x,y) 0.0, 0.0.
[INFO] Inital goal status: PENDING
[INFO] This goal has been accepted by the simple action server
[INFO] Final goal status: SUCCEEDED
[INFO] Goal reached.
Full documentation on wiki: http://wiki.ros.org/lost_comms_recovery
Changelog for package lost_comms_recovery
0.1.0 (2017-07-20)
- First release
Wiki Tutorials
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/lost_comms_recovery.launch
-
- ips_to_monitor [default: 192.168.1.2,192.168.1.3]
Messages
Services
Plugins
Recent questions tagged lost_comms_recovery at Robotics Stack Exchange
![]() |
lost_comms_recovery package from lost_comms_recovery repolost_comms_recovery |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 0.1.0 |
License | Unlicense |
Build type | CATKIN |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/danielsnider/lost_comms_recovery.git |
VCS Type | git |
VCS Version | master |
Last Updated | 2017-08-05 |
Dev Status | MAINTAINED |
CI status | Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Daniel Snider
Authors
- Daniel Snider
lost_comms_recovery
If your robot loses connection to the base station it will navigate to a configurable home.
Quick Start
- Install:
$ sudo apt-get install ros-kinetic-lost-comms-recovery
- Launch node:
$ roslaunch lost_comms_recovery lost_comms_recovery.launch
- Normal output:
$ roslaunch lost_comms_recovery lost_comms_recovery.launch ips_to_monitor:=192.168.190.136
[INFO] Monitoring base station on IP(s): 192.168.190.136.
[INFO] Connected to base station.
[INFO] Connected to base station.
...
[ERROR] No connection to base station.
[INFO] Connected to move_base.
[INFO] Executing move_base goal to position (x,y) 0.0, 0.0.
[INFO] Inital goal status: PENDING
[INFO] This goal has been accepted by the simple action server
[INFO] Final goal status: SUCCEEDED
[INFO] Goal reached.
Full documentation on wiki: http://wiki.ros.org/lost_comms_recovery
Changelog for package lost_comms_recovery
0.1.0 (2017-07-20)
- First release
Wiki Tutorials
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/lost_comms_recovery.launch
-
- ips_to_monitor [default: 192.168.1.2,192.168.1.3]
Messages
Services
Plugins
Recent questions tagged lost_comms_recovery at Robotics Stack Exchange
![]() |
lost_comms_recovery package from lost_comms_recovery repolost_comms_recovery |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 0.1.0 |
License | Unlicense |
Build type | CATKIN |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/danielsnider/lost_comms_recovery.git |
VCS Type | git |
VCS Version | master |
Last Updated | 2017-08-05 |
Dev Status | MAINTAINED |
CI status | Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Daniel Snider
Authors
- Daniel Snider
lost_comms_recovery
If your robot loses connection to the base station it will navigate to a configurable home.
Quick Start
- Install:
$ sudo apt-get install ros-kinetic-lost-comms-recovery
- Launch node:
$ roslaunch lost_comms_recovery lost_comms_recovery.launch
- Normal output:
$ roslaunch lost_comms_recovery lost_comms_recovery.launch ips_to_monitor:=192.168.190.136
[INFO] Monitoring base station on IP(s): 192.168.190.136.
[INFO] Connected to base station.
[INFO] Connected to base station.
...
[ERROR] No connection to base station.
[INFO] Connected to move_base.
[INFO] Executing move_base goal to position (x,y) 0.0, 0.0.
[INFO] Inital goal status: PENDING
[INFO] This goal has been accepted by the simple action server
[INFO] Final goal status: SUCCEEDED
[INFO] Goal reached.
Full documentation on wiki: http://wiki.ros.org/lost_comms_recovery
Changelog for package lost_comms_recovery
0.1.0 (2017-07-20)
- First release
Wiki Tutorials
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/lost_comms_recovery.launch
-
- ips_to_monitor [default: 192.168.1.2,192.168.1.3]
Messages
Services
Plugins
Recent questions tagged lost_comms_recovery at Robotics Stack Exchange
![]() |
lost_comms_recovery package from lost_comms_recovery repolost_comms_recovery |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 0.1.0 |
License | Unlicense |
Build type | CATKIN |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/danielsnider/lost_comms_recovery.git |
VCS Type | git |
VCS Version | master |
Last Updated | 2017-08-05 |
Dev Status | MAINTAINED |
CI status | Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Daniel Snider
Authors
- Daniel Snider
lost_comms_recovery
If your robot loses connection to the base station it will navigate to a configurable home.
Quick Start
- Install:
$ sudo apt-get install ros-kinetic-lost-comms-recovery
- Launch node:
$ roslaunch lost_comms_recovery lost_comms_recovery.launch
- Normal output:
$ roslaunch lost_comms_recovery lost_comms_recovery.launch ips_to_monitor:=192.168.190.136
[INFO] Monitoring base station on IP(s): 192.168.190.136.
[INFO] Connected to base station.
[INFO] Connected to base station.
...
[ERROR] No connection to base station.
[INFO] Connected to move_base.
[INFO] Executing move_base goal to position (x,y) 0.0, 0.0.
[INFO] Inital goal status: PENDING
[INFO] This goal has been accepted by the simple action server
[INFO] Final goal status: SUCCEEDED
[INFO] Goal reached.
Full documentation on wiki: http://wiki.ros.org/lost_comms_recovery
Changelog for package lost_comms_recovery
0.1.0 (2017-07-20)
- First release
Wiki Tutorials
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/lost_comms_recovery.launch
-
- ips_to_monitor [default: 192.168.1.2,192.168.1.3]
Messages
Services
Plugins
Recent questions tagged lost_comms_recovery at Robotics Stack Exchange
![]() |
lost_comms_recovery package from lost_comms_recovery repolost_comms_recovery |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 0.1.0 |
License | Unlicense |
Build type | CATKIN |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/danielsnider/lost_comms_recovery.git |
VCS Type | git |
VCS Version | master |
Last Updated | 2017-08-05 |
Dev Status | MAINTAINED |
CI status | Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Daniel Snider
Authors
- Daniel Snider
lost_comms_recovery
If your robot loses connection to the base station it will navigate to a configurable home.
Quick Start
- Install:
$ sudo apt-get install ros-kinetic-lost-comms-recovery
- Launch node:
$ roslaunch lost_comms_recovery lost_comms_recovery.launch
- Normal output:
$ roslaunch lost_comms_recovery lost_comms_recovery.launch ips_to_monitor:=192.168.190.136
[INFO] Monitoring base station on IP(s): 192.168.190.136.
[INFO] Connected to base station.
[INFO] Connected to base station.
...
[ERROR] No connection to base station.
[INFO] Connected to move_base.
[INFO] Executing move_base goal to position (x,y) 0.0, 0.0.
[INFO] Inital goal status: PENDING
[INFO] This goal has been accepted by the simple action server
[INFO] Final goal status: SUCCEEDED
[INFO] Goal reached.
Full documentation on wiki: http://wiki.ros.org/lost_comms_recovery
Changelog for package lost_comms_recovery
0.1.0 (2017-07-20)
- First release
Wiki Tutorials
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/lost_comms_recovery.launch
-
- ips_to_monitor [default: 192.168.1.2,192.168.1.3]
Messages
Services
Plugins
Recent questions tagged lost_comms_recovery at Robotics Stack Exchange
![]() |
lost_comms_recovery package from lost_comms_recovery repolost_comms_recovery |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 0.1.0 |
License | Unlicense |
Build type | CATKIN |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/danielsnider/lost_comms_recovery.git |
VCS Type | git |
VCS Version | master |
Last Updated | 2017-08-05 |
Dev Status | MAINTAINED |
CI status | Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Daniel Snider
Authors
- Daniel Snider
lost_comms_recovery
If your robot loses connection to the base station it will navigate to a configurable home.
Quick Start
- Install:
$ sudo apt-get install ros-kinetic-lost-comms-recovery
- Launch node:
$ roslaunch lost_comms_recovery lost_comms_recovery.launch
- Normal output:
$ roslaunch lost_comms_recovery lost_comms_recovery.launch ips_to_monitor:=192.168.190.136
[INFO] Monitoring base station on IP(s): 192.168.190.136.
[INFO] Connected to base station.
[INFO] Connected to base station.
...
[ERROR] No connection to base station.
[INFO] Connected to move_base.
[INFO] Executing move_base goal to position (x,y) 0.0, 0.0.
[INFO] Inital goal status: PENDING
[INFO] This goal has been accepted by the simple action server
[INFO] Final goal status: SUCCEEDED
[INFO] Goal reached.
Full documentation on wiki: http://wiki.ros.org/lost_comms_recovery
Changelog for package lost_comms_recovery
0.1.0 (2017-07-20)
- First release
Wiki Tutorials
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/lost_comms_recovery.launch
-
- ips_to_monitor [default: 192.168.1.2,192.168.1.3]
Messages
Services
Plugins
Recent questions tagged lost_comms_recovery at Robotics Stack Exchange
![]() |
lost_comms_recovery package from lost_comms_recovery repolost_comms_recovery |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 0.1.0 |
License | Unlicense |
Build type | CATKIN |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/danielsnider/lost_comms_recovery.git |
VCS Type | git |
VCS Version | master |
Last Updated | 2017-08-05 |
Dev Status | MAINTAINED |
CI status | Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Daniel Snider
Authors
- Daniel Snider
lost_comms_recovery
If your robot loses connection to the base station it will navigate to a configurable home.
Quick Start
- Install:
$ sudo apt-get install ros-kinetic-lost-comms-recovery
- Launch node:
$ roslaunch lost_comms_recovery lost_comms_recovery.launch
- Normal output:
$ roslaunch lost_comms_recovery lost_comms_recovery.launch ips_to_monitor:=192.168.190.136
[INFO] Monitoring base station on IP(s): 192.168.190.136.
[INFO] Connected to base station.
[INFO] Connected to base station.
...
[ERROR] No connection to base station.
[INFO] Connected to move_base.
[INFO] Executing move_base goal to position (x,y) 0.0, 0.0.
[INFO] Inital goal status: PENDING
[INFO] This goal has been accepted by the simple action server
[INFO] Final goal status: SUCCEEDED
[INFO] Goal reached.
Full documentation on wiki: http://wiki.ros.org/lost_comms_recovery
Changelog for package lost_comms_recovery
0.1.0 (2017-07-20)
- First release
Wiki Tutorials
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/lost_comms_recovery.launch
-
- ips_to_monitor [default: 192.168.1.2,192.168.1.3]
Messages
Services
Plugins
Recent questions tagged lost_comms_recovery at Robotics Stack Exchange
![]() |
lost_comms_recovery package from lost_comms_recovery repolost_comms_recovery |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 0.1.0 |
License | Unlicense |
Build type | CATKIN |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/danielsnider/lost_comms_recovery.git |
VCS Type | git |
VCS Version | master |
Last Updated | 2017-08-05 |
Dev Status | MAINTAINED |
CI status | Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Daniel Snider
Authors
- Daniel Snider
lost_comms_recovery
If your robot loses connection to the base station it will navigate to a configurable home.
Quick Start
- Install:
$ sudo apt-get install ros-kinetic-lost-comms-recovery
- Launch node:
$ roslaunch lost_comms_recovery lost_comms_recovery.launch
- Normal output:
$ roslaunch lost_comms_recovery lost_comms_recovery.launch ips_to_monitor:=192.168.190.136
[INFO] Monitoring base station on IP(s): 192.168.190.136.
[INFO] Connected to base station.
[INFO] Connected to base station.
...
[ERROR] No connection to base station.
[INFO] Connected to move_base.
[INFO] Executing move_base goal to position (x,y) 0.0, 0.0.
[INFO] Inital goal status: PENDING
[INFO] This goal has been accepted by the simple action server
[INFO] Final goal status: SUCCEEDED
[INFO] Goal reached.
Full documentation on wiki: http://wiki.ros.org/lost_comms_recovery
Changelog for package lost_comms_recovery
0.1.0 (2017-07-20)
- First release
Wiki Tutorials
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/lost_comms_recovery.launch
-
- ips_to_monitor [default: 192.168.1.2,192.168.1.3]
Messages
Services
Plugins
Recent questions tagged lost_comms_recovery at Robotics Stack Exchange
![]() |
lost_comms_recovery package from lost_comms_recovery repolost_comms_recovery |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 0.1.0 |
License | Unlicense |
Build type | CATKIN |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/danielsnider/lost_comms_recovery.git |
VCS Type | git |
VCS Version | master |
Last Updated | 2017-08-05 |
Dev Status | MAINTAINED |
CI status | Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Daniel Snider
Authors
- Daniel Snider
lost_comms_recovery
If your robot loses connection to the base station it will navigate to a configurable home.
Quick Start
- Install:
$ sudo apt-get install ros-kinetic-lost-comms-recovery
- Launch node:
$ roslaunch lost_comms_recovery lost_comms_recovery.launch
- Normal output:
$ roslaunch lost_comms_recovery lost_comms_recovery.launch ips_to_monitor:=192.168.190.136
[INFO] Monitoring base station on IP(s): 192.168.190.136.
[INFO] Connected to base station.
[INFO] Connected to base station.
...
[ERROR] No connection to base station.
[INFO] Connected to move_base.
[INFO] Executing move_base goal to position (x,y) 0.0, 0.0.
[INFO] Inital goal status: PENDING
[INFO] This goal has been accepted by the simple action server
[INFO] Final goal status: SUCCEEDED
[INFO] Goal reached.
Full documentation on wiki: http://wiki.ros.org/lost_comms_recovery
Changelog for package lost_comms_recovery
0.1.0 (2017-07-20)
- First release
Wiki Tutorials
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/lost_comms_recovery.launch
-
- ips_to_monitor [default: 192.168.1.2,192.168.1.3]
Messages
Services
Plugins
Recent questions tagged lost_comms_recovery at Robotics Stack Exchange
![]() |
lost_comms_recovery package from lost_comms_recovery repolost_comms_recovery |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 0.1.0 |
License | Unlicense |
Build type | CATKIN |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/danielsnider/lost_comms_recovery.git |
VCS Type | git |
VCS Version | master |
Last Updated | 2017-08-05 |
Dev Status | MAINTAINED |
CI status | Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Daniel Snider
Authors
- Daniel Snider
lost_comms_recovery
If your robot loses connection to the base station it will navigate to a configurable home.
Quick Start
- Install:
$ sudo apt-get install ros-kinetic-lost-comms-recovery
- Launch node:
$ roslaunch lost_comms_recovery lost_comms_recovery.launch
- Normal output:
$ roslaunch lost_comms_recovery lost_comms_recovery.launch ips_to_monitor:=192.168.190.136
[INFO] Monitoring base station on IP(s): 192.168.190.136.
[INFO] Connected to base station.
[INFO] Connected to base station.
...
[ERROR] No connection to base station.
[INFO] Connected to move_base.
[INFO] Executing move_base goal to position (x,y) 0.0, 0.0.
[INFO] Inital goal status: PENDING
[INFO] This goal has been accepted by the simple action server
[INFO] Final goal status: SUCCEEDED
[INFO] Goal reached.
Full documentation on wiki: http://wiki.ros.org/lost_comms_recovery
Changelog for package lost_comms_recovery
0.1.0 (2017-07-20)
- First release
Wiki Tutorials
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/lost_comms_recovery.launch
-
- ips_to_monitor [default: 192.168.1.2,192.168.1.3]
Messages
Services
Plugins
Recent questions tagged lost_comms_recovery at Robotics Stack Exchange
![]() |
lost_comms_recovery package from lost_comms_recovery repolost_comms_recovery |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 0.1.0 |
License | Unlicense |
Build type | CATKIN |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/danielsnider/lost_comms_recovery.git |
VCS Type | git |
VCS Version | master |
Last Updated | 2017-08-05 |
Dev Status | MAINTAINED |
CI status | Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Daniel Snider
Authors
- Daniel Snider
lost_comms_recovery
If your robot loses connection to the base station it will navigate to a configurable home.
Quick Start
- Install:
$ sudo apt-get install ros-kinetic-lost-comms-recovery
- Launch node:
$ roslaunch lost_comms_recovery lost_comms_recovery.launch
- Normal output:
$ roslaunch lost_comms_recovery lost_comms_recovery.launch ips_to_monitor:=192.168.190.136
[INFO] Monitoring base station on IP(s): 192.168.190.136.
[INFO] Connected to base station.
[INFO] Connected to base station.
...
[ERROR] No connection to base station.
[INFO] Connected to move_base.
[INFO] Executing move_base goal to position (x,y) 0.0, 0.0.
[INFO] Inital goal status: PENDING
[INFO] This goal has been accepted by the simple action server
[INFO] Final goal status: SUCCEEDED
[INFO] Goal reached.
Full documentation on wiki: http://wiki.ros.org/lost_comms_recovery
Changelog for package lost_comms_recovery
0.1.0 (2017-07-20)
- First release
Wiki Tutorials
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/lost_comms_recovery.launch
-
- ips_to_monitor [default: 192.168.1.2,192.168.1.3]
Messages
Services
Plugins
Recent questions tagged lost_comms_recovery at Robotics Stack Exchange
![]() |
lost_comms_recovery package from lost_comms_recovery repolost_comms_recovery |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 0.1.0 |
License | Unlicense |
Build type | CATKIN |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/danielsnider/lost_comms_recovery.git |
VCS Type | git |
VCS Version | master |
Last Updated | 2017-08-05 |
Dev Status | MAINTAINED |
CI status | Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Daniel Snider
Authors
- Daniel Snider
lost_comms_recovery
If your robot loses connection to the base station it will navigate to a configurable home.
Quick Start
- Install:
$ sudo apt-get install ros-kinetic-lost-comms-recovery
- Launch node:
$ roslaunch lost_comms_recovery lost_comms_recovery.launch
- Normal output:
$ roslaunch lost_comms_recovery lost_comms_recovery.launch ips_to_monitor:=192.168.190.136
[INFO] Monitoring base station on IP(s): 192.168.190.136.
[INFO] Connected to base station.
[INFO] Connected to base station.
...
[ERROR] No connection to base station.
[INFO] Connected to move_base.
[INFO] Executing move_base goal to position (x,y) 0.0, 0.0.
[INFO] Inital goal status: PENDING
[INFO] This goal has been accepted by the simple action server
[INFO] Final goal status: SUCCEEDED
[INFO] Goal reached.
Full documentation on wiki: http://wiki.ros.org/lost_comms_recovery
Changelog for package lost_comms_recovery
0.1.0 (2017-07-20)
- First release
Wiki Tutorials
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/lost_comms_recovery.launch
-
- ips_to_monitor [default: 192.168.1.2,192.168.1.3]
Messages
Services
Plugins
Recent questions tagged lost_comms_recovery at Robotics Stack Exchange
![]() |
lost_comms_recovery package from lost_comms_recovery repolost_comms_recovery |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 0.1.0 |
License | Unlicense |
Build type | CATKIN |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/danielsnider/lost_comms_recovery.git |
VCS Type | git |
VCS Version | master |
Last Updated | 2017-08-05 |
Dev Status | MAINTAINED |
CI status | Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Daniel Snider
Authors
- Daniel Snider
lost_comms_recovery
If your robot loses connection to the base station it will navigate to a configurable home.
Quick Start
- Install:
$ sudo apt-get install ros-kinetic-lost-comms-recovery
- Launch node:
$ roslaunch lost_comms_recovery lost_comms_recovery.launch
- Normal output:
$ roslaunch lost_comms_recovery lost_comms_recovery.launch ips_to_monitor:=192.168.190.136
[INFO] Monitoring base station on IP(s): 192.168.190.136.
[INFO] Connected to base station.
[INFO] Connected to base station.
...
[ERROR] No connection to base station.
[INFO] Connected to move_base.
[INFO] Executing move_base goal to position (x,y) 0.0, 0.0.
[INFO] Inital goal status: PENDING
[INFO] This goal has been accepted by the simple action server
[INFO] Final goal status: SUCCEEDED
[INFO] Goal reached.
Full documentation on wiki: http://wiki.ros.org/lost_comms_recovery
Changelog for package lost_comms_recovery
0.1.0 (2017-07-20)
- First release
Wiki Tutorials
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/lost_comms_recovery.launch
-
- ips_to_monitor [default: 192.168.1.2,192.168.1.3]
Messages
Services
Plugins
Recent questions tagged lost_comms_recovery at Robotics Stack Exchange
![]() |
lost_comms_recovery package from lost_comms_recovery repolost_comms_recovery |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 0.1.0 |
License | Unlicense |
Build type | CATKIN |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/danielsnider/lost_comms_recovery.git |
VCS Type | git |
VCS Version | master |
Last Updated | 2017-08-05 |
Dev Status | MAINTAINED |
CI status | Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Daniel Snider
Authors
- Daniel Snider
lost_comms_recovery
If your robot loses connection to the base station it will navigate to a configurable home.
Quick Start
- Install:
$ sudo apt-get install ros-kinetic-lost-comms-recovery
- Launch node:
$ roslaunch lost_comms_recovery lost_comms_recovery.launch
- Normal output:
$ roslaunch lost_comms_recovery lost_comms_recovery.launch ips_to_monitor:=192.168.190.136
[INFO] Monitoring base station on IP(s): 192.168.190.136.
[INFO] Connected to base station.
[INFO] Connected to base station.
...
[ERROR] No connection to base station.
[INFO] Connected to move_base.
[INFO] Executing move_base goal to position (x,y) 0.0, 0.0.
[INFO] Inital goal status: PENDING
[INFO] This goal has been accepted by the simple action server
[INFO] Final goal status: SUCCEEDED
[INFO] Goal reached.
Full documentation on wiki: http://wiki.ros.org/lost_comms_recovery
Changelog for package lost_comms_recovery
0.1.0 (2017-07-20)
- First release
Wiki Tutorials
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/lost_comms_recovery.launch
-
- ips_to_monitor [default: 192.168.1.2,192.168.1.3]
Messages
Services
Plugins
Recent questions tagged lost_comms_recovery at Robotics Stack Exchange
![]() |
lost_comms_recovery package from lost_comms_recovery repolost_comms_recovery |
ROS Distro
|
Package Summary
Tags | No category tags. |
Version | 0.1.0 |
License | Unlicense |
Build type | CATKIN |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/danielsnider/lost_comms_recovery.git |
VCS Type | git |
VCS Version | master |
Last Updated | 2017-08-05 |
Dev Status | MAINTAINED |
CI status | Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Daniel Snider
Authors
- Daniel Snider
lost_comms_recovery
If your robot loses connection to the base station it will navigate to a configurable home.
Quick Start
- Install:
$ sudo apt-get install ros-kinetic-lost-comms-recovery
- Launch node:
$ roslaunch lost_comms_recovery lost_comms_recovery.launch
- Normal output:
$ roslaunch lost_comms_recovery lost_comms_recovery.launch ips_to_monitor:=192.168.190.136
[INFO] Monitoring base station on IP(s): 192.168.190.136.
[INFO] Connected to base station.
[INFO] Connected to base station.
...
[ERROR] No connection to base station.
[INFO] Connected to move_base.
[INFO] Executing move_base goal to position (x,y) 0.0, 0.0.
[INFO] Inital goal status: PENDING
[INFO] This goal has been accepted by the simple action server
[INFO] Final goal status: SUCCEEDED
[INFO] Goal reached.
Full documentation on wiki: http://wiki.ros.org/lost_comms_recovery
Changelog for package lost_comms_recovery
0.1.0 (2017-07-20)
- First release
Wiki Tutorials
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/lost_comms_recovery.launch
-
- ips_to_monitor [default: 192.168.1.2,192.168.1.3]