Standalone ePick launch stub
Minimal standalone ePick controller-manager launch stub. Declares parent/USB/mock arguments but only forwards USB and fake-hardware values; no robot description or controller spawners are provided here.
src.end_effectors.epick_config.launch.epick_bringup.launch · Source
Tools and end effectors · Guide · Symbol index
How it is used
This is a minimal controller-manager launch definition, not a complete ePick bringup. generate_launch_description() declares parent, USB, and fake-hardware options, but forwards only the USB and fake-hardware values. A robot description and controller spawners must be supplied elsewhere.
For the integrated CMS tool path, inspect the CMS robot launch instead of treating this stub as a ready-to-run deployment.
Start here
Callable |
Purpose |
|---|---|
Declare parent=tool0, usb_port=/tmp/ttyUR and use_fake_hardware=false, then construct one ros2_control_node action with the latter two parameters. |
Functions
generate_launch_description()
Declare parent=tool0, usb_port=/tmp/ttyUR and use_fake_hardware=false, then construct one ros2_control_node action with the latter two parameters.
Entry point · Source
generate_launch_description()
Returns: LaunchDescription with three argument declarations and one controller_manager node. parent is declared but unused.
Errors: Launch construction errors propagate; controller/model readiness is not checked or completed by this helper.
Side effects: Builds actions; executing starts a controller-manager process with a serial-path/fake-hardware parameter pair.