Crates.io | rocc |
lib.rs | rocc |
version | 0.1.33 |
source | src |
created_at | 2023-10-16 22:16:11.471896 |
updated_at | 2023-11-12 22:14:43.352282 |
description | Robot Operations Command Center |
homepage | |
repository | |
max_upload_size | |
id | 1005279 |
size | 319,496 |
[SUPER EARLY STAGE] at the moment it calls ros2 commands externally, but the goal is to have a single binary that can be used to replace the ros2 command line tool.
roc <COMMAND> [SUBCOMMAND] [OPTIONS] [ARGS]
cargo install rocc
usual ros2 commands
workspace creation and build commands
coordinate frame commands
bridge commands (foxglove & rosbridge)
ros bag utilities
daemon tools
Usage: roc <COMMAND>
Monotor Commands:
action [a] Various action subcommands
topic [t] Various topic subcommands
service [s] Various service subcommands
param [p] Various param subcommands
node [n] Various node subcommands
interface [i] Various interface subcommands
frame [f] Various transforms subcommands [WIP]
Workspace Commands:
run [r] Run an executable
launch [l] Launch a launch file
work [w] Various workspace subcommands
Utilities Commands:
bag [b] Various rosbag subcommands
daemon [d] Deamon and bridge subcommands [WIP]
middleware [m] Various middleware subcommands [WIP]
Why not? Rust is fun and I wanted to learn more how to interact with the ros2 api.