-
 
No version for distro humble. Known supported distros are highlighted in the buttons above.
No version for distro iron. Known supported distros are highlighted in the buttons above.
No version for distro jazzy. Known supported distros are highlighted in the buttons above.
No version for distro rolling. Known supported distros are highlighted in the buttons above.

fetch_tools package from fetch_tools repo

fetch_tools

Package Summary

Tags No category tags.
Version 0.3.3
License BSD
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/fetchrobotics/fetch_tools.git
VCS Type git
VCS Version ros1
Last Updated 2024-01-08
Dev Status MAINTAINED
CI status Continuous Integration : 0 / 0
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Package Description

Commands for performing common operations when developing on the robots. For help, run `fetch -h` and `fetch COMMAND -h`.

Additional Links

Maintainers

  • Eric Relson
  • Carl Saldanha
  • Russell Toris
  • Fetch Robotics Open Source Team

Authors

  • Alex Henning

Fetch Tools

This package contains the fetch utility to make development easier. For full details of command usage and arguments, run fetch -h and fetch COMMAND -h. It also adds useful aliases for connecting to robots. Below summarizes installation and common usage.

Intended Workflow

This tool was written to help make it easier to develop code and switch between robots with ease. It works by inferring what robot you’re working on from $ROS_MASTER_URI and automating common tasks such as account creation, code syncing, and running commands. It assumes that you always edit code in your ROS Workspace and then push a copy of the workspace to the robot afterwards, so that you can run it. This keeps all code that you are developing on your computer in case someone takes the robot.

Example Workflow

# Start working on freight 0 for the first time
ufr 0
fetch create-account --fullname "Not A. Robot"
fetch push --install-deps --build
fetch run "roslaunch my_awesome_package do_stuff.launch"
# Edit code to fix a bug
fetch push --build "--pkg my_awesome_package"
fetch run "roslaunch my_awesome_package do_stuff.launch"
# Switch over to freight 8, since someone kidnapped freight 0
ufr 8
fetch create-account --fullname "Not A. Robot"
fetch push --install-deps --build
fetch run "roslaunch my_awesome_package do_stuff.launch"

Installation

To install run, checkout the fetchrobotics/sandbox repo and run:

sudo apt-get install ros-noetic-fetch-tools

Afterwards, restart your terminal or run source $(rospack find fetch_tools)/setup.bash.

Common Arguments

Robot

Most operations interact with a robot, in this case they take an optional --robot argument. If the robot parameter is passed in using --robot, that is the value used. If not, the parameter defaults to the robot pointed at by $ROS_MASTER_URI. To set the default value, add the line export FETCH_ROBOT=myrobot to your .bashrc file.

If the robot is not on the DNS (i.e. pinging the robot name does not work), you can add .local to the parameter, e.g. fetch4.local, and communication with the robot will work via zeroconf (avahi).

Workspace

Some operations interact with a workspace, in this case take an optional --workspace argument. If the a parameter is passed in that value is used. If not, the parameter defaults to ~/$ROS_DISTRO. To set the default value, add the line export FETCH_WORKSPACE=/path/to/my/workspace to your .bashrc file. By default, the remote workspace is assumed to match your local workspace. If not, you can use either the --remote-workspace argument or the FETCH_REMOTE_WORKSPACE environment variable to change it.

User

Most operations interact with a robot, in this case they often effect a particular user on that robot, so they take an optional --user argument. If the robot parameter is passed in using --user, that is the value used. If not, the parameter defaults to $USER. To set the default value, add the line export FETCH_USER=myuser to your .bashrc file.

fetch Commands

fetch create-account

To create an account:

fetch create-account

To create an account with another username:

fetch create-account --robot freight0 --user test

Once it is done you can run ssh $USER@freight0 without entering your password. (If both users are the same you can just run ssh freight0)

Customizing Account Creation

If you are creating accounts on lots of robots, you can customize the install process. First, create a copy of the skeleton directory:

cp -r $(rospack find fetch_tools)/resources/robot_skeleton ~/.fetch/robot_skeleton

Next, customize all files to your desired value. initialize.sh is a special script that gets run during the account creation process. If you want to install software or run other commands every time you create an account, customize initialize.sh.

fetch push

WARNING: Synchronize in this context means make the remote workspace like the current workspace. This means new files will be added and old files will be deleted. It is strongly recommended that you never change files in the workspace on the robot directly.

To synchronize your $workspace/src directory with the matching directory on another robot:

fetch push

To synchronize another workspace with a robot:

fetch push --workspace ~/test_ws

To synchronize and then run catkin_make to build:

fetch push --build

To synchronize and install all dependencies with rosdep:

fetch push --install-deps

To synchronize and then run catkin_make --pkg follow_pick -DCMAKE_BUILD_TYPE=RELEASE instead of catkin_make --pkg follow_pick -DCMAKE_BUILD_TYPE=Debug to build:

fetch push --build "--pkg follow_pick -DCMAKE_BUILD_TYPE=RELEASE"

fetch pull

Is just fetch push in reverse, so it pulls code from the remote workspace into the local workspace. It supports the same arguments

fetch run

To run a command on the robot:

fetch run COMMAND

To run a command on the robot with arguments:

fetch run "COMMAND --flag1 --flag2 arg1"

fetch lint

Fetch lint runs pep8, roslint, and catkin_lint to make sure a package is compliant with all style guides. To lint a package:

fetch lint PACKAGE

To lint a folder:

fetch lint FOLDER

To lint a file:

fetch lint FILE

fetch workspace-status

This command produces a table of the current workspace, including the git information so that you can communicate what code is checked out easily. Running:

fetch workspace-status

Produces:

Name Branch SHA1
fetch_ros melodic-devel 30d7794
fetch_tools push 5bbb0e4-dirty
some_random_code None untracked

fetch debug-snapshot

This command takes a debug snapshot of running robot, gathering information that can be useful in diagnosing robot problems:

fetch debug-snapshot

NOTE: If this command is run on the robot itself, it may fail silently due to ssh prompts. You can fix this by manually doing ssh fetchXYZ (to add the robot’s own host key to its list of known hosts).

Useful Aliases

In addition to the fetch command, setup.bash loads some useful aliases for working with multiple Fetch and Freight robots.

Working with $ROS_MASTER_URI

There are three aliases for working with $ROS_MASTER_URI:

uf 5   # Set ROS_MASTER_URI="http://fetch5:11311"
ufr 0  # Set ROS_MASTER_URI="http://freight0:11311"
ul     # Set ROS_MASTER_URI="http://localhost:11311"

  • uf is short for use fetch
  • ufr is short for use freight
  • ul is short for use localhost

Note also that ul supports setting a custom port

ul 11312  # Set ROS_MASTER_URI="http://localhost:11312"

SSH

There are two aliases for sshing into robots

sf 5   # SSH into fetch 5
sfr 0  # SSH into freight0

You can also use aliases to do ssh-copy-id for key setup with robots

kf 1104
kfr 1234

Using .local with uf/ufr and sf/sfr

If your network does not provide DNS for your robots, often the robot’s number can simply be appended with .local to take advantage of zeroconf (avahi) without needing any DNS configuration.

uf 5.local   # Set ROS_MASTER_URI="http://fetch5.local:11311"
sf 5.local   # SSH into fetch 5, without using DNS

CHANGELOG

Changelog for package fetch_tools

0.3.3 (2020-10-20)

  • Fix argcomplete hook command for python3
  • Contributors: Eric Relson

0.3.2 (2020-09-23)

  • Fix build dep that was missed for python2->3
  • Contributors: Eric Relson

0.3.1 (2020-09-20)

  • Update dependencies from py2 to py3
  • Contributors: Eric Relson

0.3.0 (2020-09-20)

  • Convert to python3 + ROS noetic
  • Text improvements to debug_snapshot tool
  • Several 18.04 fixes to debug_snapshot tool
  • Contributors: Alex Moriarty, Eric Relson, Nick Walker, Russell Toris

0.2.1 (2019-03-26)

  • Fixups for indigo->melodic; package format (#13)
    • Updates to debug_snapshot
    • Warning about common failure case when using debug_snapshot
  • Contributors: Eric Relson

0.2.0 (2018-07-11)

  • updates ownership
  • Update create_account.py
  • Expand hardware info retrieval and add read_board
  • Contributors: Alex Henning, Michael Ferguson, Michael Hwang, Russell Toris

0.1.4 (2016-04-12)

  • Added FETCH_USER to sf/sfr & additional usage notes
  • Updated readme to detail robothostname.local usage with fetch_tools and how to set ports with ul
  • Contributors: Alex Henning, Eric Relson

0.1.3 (2016-03-24)

  • Added upstart conf files to debug-snapshot zip
  • Contributors: Aaron Blasdel

0.1.2 (2016-02-29)

  • Added three commands:
    • [fetch debug-snapshot]{.title-ref}
    • [fetch pull]{.title-ref}
    • [fetch workspace-status]{.title-ref}
  • Changed one command:
    • [fetch sync]{.title-ref} is now [fetch push]{.title-ref}
  • Improved one command:
    • [fetch run]{.title-ref} now supports multiple workspaces
  • Contributors: Alex Henning, Michael Ferguson, Aaron Blasdel

0.1.1 (2015-07-31)

  • Initial implementation of fetch_tools Includes four commands:
    • [fetch create-account]{.title-ref}
    • [fetch sync]{.title-ref}
    • [fetch run]{.title-ref}

    - [fetch lint]{.title-ref} Includes five aliases:

    • uf
    • ufr
    • ul
    • sf
    • sfr
  • Initial commit
  • Contributors: Alex Henning, Michael Ferguson

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Package Dependencies

System Dependencies

Dependant Packages

No known dependants.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged fetch_tools at Robotics Stack Exchange

No version for distro ardent. Known supported distros are highlighted in the buttons above.
No version for distro bouncy. Known supported distros are highlighted in the buttons above.
No version for distro crystal. Known supported distros are highlighted in the buttons above.
No version for distro eloquent. Known supported distros are highlighted in the buttons above.
No version for distro dashing. Known supported distros are highlighted in the buttons above.
No version for distro galactic. Known supported distros are highlighted in the buttons above.
No version for distro foxy. Known supported distros are highlighted in the buttons above.
No version for distro lunar. Known supported distros are highlighted in the buttons above.
No version for distro jade. Known supported distros are highlighted in the buttons above.

fetch_tools package from fetch_tools repo

fetch_tools

Package Summary

Tags No category tags.
Version 0.1.5
License BSD
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/fetchrobotics/fetch_tools.git
VCS Type git
VCS Version indigo-devel
Last Updated 2018-07-11
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

Commands for performing common operations when developing on the robots. For help, run `fetch -h` and `fetch COMMAND -h`.

Additional Links

Maintainers

  • Russell Toris
  • Alex Moriarty

Authors

  • Alex Henning

Fetch Tools

This package contains the fetch utility to make development easier. For full details of command usage and arguments, run fetch -h and fetch COMMAND -h. Below summarizes installation and common usage.

Intended Workflow

This tool was written to help make it easier to develop code and switch between robots with ease. It works by inferring what robot you’re working on from $ROS_MASTER_URI and automating common tasks such as account creation, code syncing, and running commands. It assumes that you always edit code in your ROS Workspace and then push a copy of the workspace to the robot afterwards, so that you can run it. This keeps all code that you are developing on your computer in case someone takes the robot.

Example Workflow

# Start working on freight 0 for the first time
ufr 0
fetch create-account --fullname "Not A. Robot"
fetch push --install-deps --build
fetch run "roslaunch my_awesome_package do_stuff.launch"
# Edit code to fix a bug
fetch push --build "--pkg my_awesome_package"
fetch run "roslaunch my_awesome_package do_stuff.launch"
# Switch over to freight 8, since someone kidnapped freight 0
ufr 8
fetch create-account --fullname "Not A. Robot"
fetch push --install-deps --build
fetch run "roslaunch my_awesome_package do_stuff.launch"

Installation

To install run, checkout the fetchrobotics/sandbox repo and run:

sudo apt-get install ros-indigo-fetch-tools

Afterwards, restart your terminal or run source $(rospack find fetch_tools)/setup.bash.

Common Arguments

Robot

Most operations interact with a robot, in this case they take an optional --robot argument. If the robot parameter is passed in using --robot, that is the value used. If not, the parameter defaults to the robot pointed at by $ROS_MASTER_URI. To set the default value, add the line export FETCH_ROBOT=myrobot to your .bashrc file.

If the robot is not on the DNS (i.e. pinging the robot name does not work), you can add .local to the parameter, e.g. fetch4.local, and communication with the robot will work via zeroconf (avahi).

Workspace

Some operations interact with a workspace, in this case take an optional --workspace argument. If the a parameter is passed in that value is used. If not, the parameter defaults to ~/$ROS_DISTRO. To set the default value, add the line export FETCH_WORKSPACE=/path/to/my/workspace to your .bashrc file. By default, the remote workspace is assumed to match your local workspace. If not, you can use either the --remote-workspace argument or the FETCH_REMOTE_WORKSPACE environment variable to change it.

User

Most operations interact with a robot, in this case they often effect a particular user on that robot, so they take an optional --user argument. If the robot parameter is passed in using --user, that is the value used. If not, the parameter defaults to $USER. To set the default value, add the line export FETCH_USER=myuser to your .bashrc file.

fetch Commands

fetch create-account

To create an account:

fetch create-account

To create an account with another username:

fetch create-account --robot freight0 --user test

Once it is done you can run ssh $USER@freight0 without entering your password. (If both users are the same you can just run ssh freight0)

Customizing Account Creation

If you are creating accounts on lots of robots, you can customize the install process. First, create a copy of the skeleton directory:

cp -r $(rospack find fetch_tools)/resources/robot_skeleton ~/.fetch/robot_skeleton

Next, customize all files to your desired value. initialize.sh is a special script that gets run during the account creation process. If you want to install software or run other commands every time you create an account, customize initialize.sh.

fetch push

WARNING: Synchronize in this context means make the remote workspace like the current workspace. This means new files will be added and old files will be deleted. It is strongly recommended that you never change files in the workspace on the robot directly.

To synchronize your $workspace/src directory with the matching directory on another robot:

fetch push

To synchronize another workspace with a robot:

fetch push --workspace ~/test_ws

To synchronize and then run catkin_make to build:

fetch push --build

To synchronize and install all dependencies with rosdep:

fetch push --install-deps

To synchronize and then run catkin_make --pkg follow_pick -DCMAKE_BUILD_TYPE=RELEASE instead of catkin_make --pkg follow_pick -DCMAKE_BUILD_TYPE=Debug to build:

fetch push --build "--pkg follow_pick -DCMAKE_BUILD_TYPE=RELEASE"

fetch pull

Is just fetch push in reverse, so it pulls code from the remote workspace into the local workspace. It supports the same arguments

fetch run

To run a command on the robot:

fetch run COMMAND

To run a command on the robot with arguments:

fetch run "COMMAND --flag1 --flag2 arg1"

fetch lint

Fetch lint runs pep8, roslint, and catkin_lint to make sure a package is compliant with all style guides. To lint a package:

fetch lint PACKAGE

To lint a folder:

fetch lint FOLDER

To lint a file:

fetch lint FILE

fetch workspace-status

This command produces a table of the current workspace, including the git information so that you can communicate what code is checked out easily. Running:

fetch workspace-status

Produces:

Name Branch SHA1
fetch_ros indigo-devel 30d7794
fetch_tools push 5bbb0e4-dirty
some_random_code None untracked

fetch debug-snapshot

This command takes a debug snapshot of running robot, gathering information that can be useful in diagnosing robot problems:

fetch debug-snapshot

Useful Aliases

In addition to the fetch command, setup.bash loads some useful aliases for working with multiple Fetch and Freight robots.

Working with $ROS_MASTER_URI

There are three aliases for working with $ROS_MASTER_URI:

uf 5   # Set ROS_MASTER_URI="http://fetch5:11311"
ufr 0  # Set ROS_MASTER_URI="http://freight0:11311"
ul     # Set ROS_MASTER_URI="http://localhost:11311"

  • uf is short for use fetch
  • ufr is short for use freight
  • ul is short for use localhost

Note also that ul supports setting a custom port

ul 11312  # Set ROS_MASTER_URI="http://localhost:11312"

SSH

There are two aliases for sshing into robots

sf 5   # SSH into fetch 5
sfr 0  # SSH into freight0

Using .local with uf/ufr and sf/sfr

The robot’s number can simply be appended with .local to take advantage of zeroconf (avahi) without needing any DNS configuration.

uf 5.local   # Set ROS_MASTER_URI="http://fetch5.local:11311"
sf 5.local   # SSH into fetch 5, without using DNS

CHANGELOG

Changelog for package fetch_tools

0.1.5 (2018-07-11)

  • updates ownership
  • Merge pull request #11 from fetchrobotics/rctoris-patch-1 Adds audio group to new users
  • Update create_account.py
  • Merge pull request #10 from alexhenning/better-default-build No longer defaults to debug builds
  • No longer defaults to debug builds Defaulting to debug was a mistake, instead, this provides an option that makes it easy to change the build type to debug (or anything else) with tab completion.
  • Merge pull request #9 from mehwang/more_hardware_info Expand hardware info retrieval and add read_board to debug_snapshot
  • Expand hardware info retrieval and add read_board
  • Contributors: Alex Henning, Michael Ferguson, Michael Hwang, Russell Toris

0.1.4 (2016-04-12)

  • Added FETCH_USER to sf/sfr & additional usage notes
  • Updated readme to detail robothostname.local usage with fetch_tools and how to set ports with ul
  • Contributors: Alex Henning, Eric Relson

0.1.3 (2016-03-24)

  • Added upstart conf files to debug-snapshot zip
  • Contributors: Aaron Blasdel

0.1.2 (2016-02-29)

* Added three commands:
  • [fetch debug-snapshot]{.title-ref}
  • [fetch pull]{.title-ref}
  • [fetch workspace-status]{.title-ref}
* Changed one command:
  • [fetch sync]{.title-ref} is now [fetch push]{.title-ref}
* Improved one command:
  • [fetch run]{.title-ref} now supports multiple workspaces
  • Contributors: Alex Henning, Michael Ferguson, Aaron Blasdel

0.1.1 (2015-07-31)

  • Initial implementation of fetch_tools Includes four commands:
    • [fetch create-account]{.title-ref}
    • [fetch sync]{.title-ref}
    • [fetch run]{.title-ref}

    - [fetch lint]{.title-ref} Includes five aliases:

    • uf
    • ufr
    • ul
    • sf
    • sfr
  • Initial commit
  • Contributors: Alex Henning, Michael Ferguson

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Package Dependencies

System Dependencies

Dependant Packages

No known dependants.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged fetch_tools at Robotics Stack Exchange

No version for distro hydro. Known supported distros are highlighted in the buttons above.
No version for distro kinetic. Known supported distros are highlighted in the buttons above.

fetch_tools package from fetch_tools repo

fetch_tools

Package Summary

Tags No category tags.
Version 0.2.2
License BSD
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/fetchrobotics/fetch_tools.git
VCS Type git
VCS Version melodic-devel
Last Updated 2020-10-06
Dev Status MAINTAINED
CI status Continuous Integration : 0 / 0
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Package Description

Commands for performing common operations when developing on the robots. For help, run `fetch -h` and `fetch COMMAND -h`.

Additional Links

Maintainers

  • Eric Relson
  • Carl Saldanha
  • Russell Toris
  • Fetch Robotics Open Source Team

Authors

  • Alex Henning

Fetch Tools

This package contains the fetch utility to make development easier. For full details of command usage and arguments, run fetch -h and fetch COMMAND -h. Below summarizes installation and common usage.

Intended Workflow

This tool was written to help make it easier to develop code and switch between robots with ease. It works by inferring what robot you’re working on from $ROS_MASTER_URI and automating common tasks such as account creation, code syncing, and running commands. It assumes that you always edit code in your ROS Workspace and then push a copy of the workspace to the robot afterwards, so that you can run it. This keeps all code that you are developing on your computer in case someone takes the robot.

Example Workflow

# Start working on freight 0 for the first time
ufr 0
fetch create-account --fullname "Not A. Robot"
fetch push --install-deps --build
fetch run "roslaunch my_awesome_package do_stuff.launch"
# Edit code to fix a bug
fetch push --build "--pkg my_awesome_package"
fetch run "roslaunch my_awesome_package do_stuff.launch"
# Switch over to freight 8, since someone kidnapped freight 0
ufr 8
fetch create-account --fullname "Not A. Robot"
fetch push --install-deps --build
fetch run "roslaunch my_awesome_package do_stuff.launch"

Installation

To install run, checkout the fetchrobotics/sandbox repo and run:

sudo apt-get install ros-melodic-fetch-tools

Afterwards, restart your terminal or run source $(rospack find fetch_tools)/setup.bash.

Common Arguments

Robot

Most operations interact with a robot, in this case they take an optional --robot argument. If the robot parameter is passed in using --robot, that is the value used. If not, the parameter defaults to the robot pointed at by $ROS_MASTER_URI. To set the default value, add the line export FETCH_ROBOT=myrobot to your .bashrc file.

If the robot is not on the DNS (i.e. pinging the robot name does not work), you can add .local to the parameter, e.g. fetch4.local, and communication with the robot will work via zeroconf (avahi).

Workspace

Some operations interact with a workspace, in this case take an optional --workspace argument. If the a parameter is passed in that value is used. If not, the parameter defaults to ~/$ROS_DISTRO. To set the default value, add the line export FETCH_WORKSPACE=/path/to/my/workspace to your .bashrc file. By default, the remote workspace is assumed to match your local workspace. If not, you can use either the --remote-workspace argument or the FETCH_REMOTE_WORKSPACE environment variable to change it.

User

Most operations interact with a robot, in this case they often effect a particular user on that robot, so they take an optional --user argument. If the robot parameter is passed in using --user, that is the value used. If not, the parameter defaults to $USER. To set the default value, add the line export FETCH_USER=myuser to your .bashrc file.

fetch Commands

fetch create-account

To create an account:

fetch create-account

To create an account with another username:

fetch create-account --robot freight0 --user test

Once it is done you can run ssh $USER@freight0 without entering your password. (If both users are the same you can just run ssh freight0)

Customizing Account Creation

If you are creating accounts on lots of robots, you can customize the install process. First, create a copy of the skeleton directory:

cp -r $(rospack find fetch_tools)/resources/robot_skeleton ~/.fetch/robot_skeleton

Next, customize all files to your desired value. initialize.sh is a special script that gets run during the account creation process. If you want to install software or run other commands every time you create an account, customize initialize.sh.

fetch push

WARNING: Synchronize in this context means make the remote workspace like the current workspace. This means new files will be added and old files will be deleted. It is strongly recommended that you never change files in the workspace on the robot directly.

To synchronize your $workspace/src directory with the matching directory on another robot:

fetch push

To synchronize another workspace with a robot:

fetch push --workspace ~/test_ws

To synchronize and then run catkin_make to build:

fetch push --build

To synchronize and install all dependencies with rosdep:

fetch push --install-deps

To synchronize and then run catkin_make --pkg follow_pick -DCMAKE_BUILD_TYPE=RELEASE instead of catkin_make --pkg follow_pick -DCMAKE_BUILD_TYPE=Debug to build:

fetch push --build "--pkg follow_pick -DCMAKE_BUILD_TYPE=RELEASE"

fetch pull

Is just fetch push in reverse, so it pulls code from the remote workspace into the local workspace. It supports the same arguments

fetch run

To run a command on the robot:

fetch run COMMAND

To run a command on the robot with arguments:

fetch run "COMMAND --flag1 --flag2 arg1"

fetch lint

Fetch lint runs pep8, roslint, and catkin_lint to make sure a package is compliant with all style guides. To lint a package:

fetch lint PACKAGE

To lint a folder:

fetch lint FOLDER

To lint a file:

fetch lint FILE

fetch workspace-status

This command produces a table of the current workspace, including the git information so that you can communicate what code is checked out easily. Running:

fetch workspace-status

Produces:

Name Branch SHA1
fetch_ros melodic-devel 30d7794
fetch_tools push 5bbb0e4-dirty
some_random_code None untracked

fetch debug-snapshot

This command takes a debug snapshot of running robot, gathering information that can be useful in diagnosing robot problems:

fetch debug-snapshot

NOTE: If this command is run on the robot itself, it may fail silently due to ssh prompts. You can fix this by manually doing ssh fetchXYZ (to add the robot’s own host key to its list of known hosts).

Useful Aliases

In addition to the fetch command, setup.bash loads some useful aliases for working with multiple Fetch and Freight robots.

Working with $ROS_MASTER_URI

There are three aliases for working with $ROS_MASTER_URI:

uf 5   # Set ROS_MASTER_URI="http://fetch5:11311"
ufr 0  # Set ROS_MASTER_URI="http://freight0:11311"
ul     # Set ROS_MASTER_URI="http://localhost:11311"

  • uf is short for use fetch
  • ufr is short for use freight
  • ul is short for use localhost

Note also that ul supports setting a custom port

ul 11312  # Set ROS_MASTER_URI="http://localhost:11312"

SSH

There are two aliases for sshing into robots

sf 5   # SSH into fetch 5
sfr 0  # SSH into freight0

Using .local with uf/ufr and sf/sfr

The robot’s number can simply be appended with .local to take advantage of zeroconf (avahi) without needing any DNS configuration.

uf 5.local   # Set ROS_MASTER_URI="http://fetch5.local:11311"
sf 5.local   # SSH into fetch 5, without using DNS

CHANGELOG

Changelog for package fetch_tools

0.2.2 (2020-10-05)

  • Several 18.04 fixes/additions to debug_snapshot tool (#14)
  • Contributors: Alex Moriarty, Eric Relson, Nick Walker, Russell Toris

0.2.1 (2019-03-26)

  • Fixups for indigo->melodic; package format (#13)
    • Updates to debug_snapshot
    • Warning about common failure case when using debug_snapshot
  • Contributors: Eric Relson

0.2.0 (2018-07-11)

  • updates ownership
  • Update create_account.py
  • Expand hardware info retrieval and add read_board
  • Contributors: Alex Henning, Michael Ferguson, Michael Hwang, Russell Toris

0.1.4 (2016-04-12)

  • Added FETCH_USER to sf/sfr & additional usage notes
  • Updated readme to detail robothostname.local usage with fetch_tools and how to set ports with ul
  • Contributors: Alex Henning, Eric Relson

0.1.3 (2016-03-24)

  • Added upstart conf files to debug-snapshot zip
  • Contributors: Aaron Blasdel

0.1.2 (2016-02-29)

  • Added three commands:
    • [fetch debug-snapshot]{.title-ref}
    • [fetch pull]{.title-ref}
    • [fetch workspace-status]{.title-ref}
  • Changed one command:
    • [fetch sync]{.title-ref} is now [fetch push]{.title-ref}
  • Improved one command:
    • [fetch run]{.title-ref} now supports multiple workspaces
  • Contributors: Alex Henning, Michael Ferguson, Aaron Blasdel

0.1.1 (2015-07-31)

  • Initial implementation of fetch_tools Includes four commands:
    • [fetch create-account]{.title-ref}
    • [fetch sync]{.title-ref}
    • [fetch run]{.title-ref}

    - [fetch lint]{.title-ref} Includes five aliases:

    • uf
    • ufr
    • ul
    • sf
    • sfr
  • Initial commit
  • Contributors: Alex Henning, Michael Ferguson

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Package Dependencies

System Dependencies

Dependant Packages

No known dependants.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged fetch_tools at Robotics Stack Exchange