For pre-compiled binaries, please see the releases tab. Currently, all three major, desktop operating systems are supported: Linux, Windows, and macOS. If you are working on a platform not supported by the current set of binaries, just open an issue under the issues tab and I will add a supported binary.
ftc_http is set to use a rather aggressive connection timeout
(500ms) when checking for robot controllers on the network. If
reports that the robot controller is offline when you are certain it's online,
try increasing this value.
When connected via WiFi-Direct, the robot controller listens on one of two IP addresses:
http://192.168.43.1:8080(REV Control Hub)
This version of
ftc_http automatically tests both addressees, but if your
robot controller is operating on a non-standard host address, you can add it to
the list of hosts checked with the
If the host and timeout options provided yield a successful connection, then
they are automatically remembered and do not need to be given a second time. If
you'd like to reset
ftc_http to its default configuration, then simply pass
Short flags can be combined to perform a series of actions following a single invocation. A somewhat contrived example of this would be the following command:
ftc_http -dwub foo/ bar/
This command downloads a copy of the code from the robot controller (saving it in the foo/ directory), wipes the robot controller, uploads a fresh copy of the code (from the bar/ directory), and builds it.
ftc_http, be sure that you have cloned the repository on your computer and then run:
cargo build --release
If you do not have Rust / Cargo installed, please see rustup.rs.
NEED TO RUN --restore-defaults after this update