HomeSpecsDocsStore
Log inSign up
TwitterDiscordGitHub
Skip to documentation
Sourccey docs

Explore the documentation

Getting startedWelcome to SourcceyChoose your path from first setup to policy development.Getting startedBefore you beginPrepare your robot, workspace, computers, and network.Vulcan StudioDownload & installInstall the desktop application for Windows, macOS, or Linux.Developer guidesDeveloper quickstartSet up the controller and robot computers with Python and LeRobot.Developer guidesTeleoperate SourcceyVerify the network, leader arms, robot, keyboard, and cameras together before collecting data.Developer guidesRecord a datasetCollect a small, consistent set of demonstrations after teleoperation passes.Developer guidesReplay an episodeSend recorded actions back to Sourccey and validate the dataset before training.Developer guidesTrain a policyTrain an ACT policy from the dataset without connecting to the robot.Developer guidesRoll out a policyGive a trained policy supervised control of Sourccey for a short test.Developer guidesTroubleshootingWork from the top of the relevant section and run one diagnostic at a time.Hardware & referenceAssembly overviewNine build stages; detailed illustrated instructions are pending.AI agentsAgent quickstartCopy task context and read documentation as Markdown.
Tab to move between results Esc to close
← Back to documentation
Sourccey SDK

Control Sourccey with LeRobot

Go from a fresh lerobot-vulcan checkout to your first supervised teleoperation, then continue into data collection, training, and policy rollout.

Start setup Full reference
1

Understand the two-computer setup

Sourccey uses one computer on the robot and another computer for control. Both must be on the same local network.

Robot computer

Connected to the arms, base, lift, cameras, and sensors. Runs sourccey-host.

Controller computer

Connected to the leader arms. Runs LeRobot control and training commands.

Before continuing, check that these instructions match your robot model and installed software. If you are unsure, the team can help you identify your setup.

2

Prepare both computers

Install Git, Python 3.12 or 3.13, and uv on both computers. Then clone the fork and open a terminal in its root on each machine.

Both computers - terminal
git clone https://github.com/vulcan-forge/lerobot-vulcan.git
Both computers - terminal
cd lerobot-vulcan
Confirm both computers are connected to the same network.
3

Set up the controller computer

Two blue and black leader arms on a desk beside a keyboard.
Leader-arm setup

Install the locked Sourccey controller profile and training dependencies.

Controller computer - terminal
uv sync --locked --extra sourccey-desktop --extra training

Connect one leader arm at a time and run this command to identify each serial port:

Controller computer - terminal
uv run lerobot-find-port

Record the left and right ports, then apply the packaged calibration for both leader arms. Replace COM5 and COM6 with the ports you found. The arms do not need to be placed in a calibration pose or stand for this command.

Controller computer - terminal
uv run sourccey-teleop-calibrate --left-arm-port=COM5 --right-arm-port=COM6

Continue when calibration completes without a serial-port error.

4

Set up the robot computer

Connect the controller computer and Sourccey to the same trusted local network. Find the robot's IP address and SSH credential in its Developer Access or onboarding screen.

Connect to Sourccey over SSH+

Replace ROBOT_IP with the address shown on Sourccey, then run this from Terminal, PowerShell, or another SSH client:

Controller computer - terminal
ssh sourccey@ROBOT_IP

On the first connection, compare the displayed host-key fingerprint with the fingerprint shown by Sourccey before accepting it. Enter the unique password created during onboarding when prompted; password input is not shown in the terminal.

After signing in, open the installed LeRobot fork:

Robot computer - terminal
cd ~/Desktop/Projects/sourccey-desktop/modules/lerobot-vulcan

Use SSH only on a trusted local network. Do not expose port 22 directly to the internet. Replace any temporary setup password during onboarding.

From the lerobot-vulcan directory on the robot, install the locked robot-side dependencies. This does not change Linux device rules or move hardware.

Robot computer - terminal
uv sync --locked --extra sourccey-robot

Install Sourccey's Linux device rules and run the robot hardware checks:

Robot computer - terminal
uv run sourccey-setup robot

Place both robot arms down at Sourccey's sides, positioned in front of the robot. Then apply the packaged arm calibration and preserve the current Z limits:

Robot computer - terminal
uv run sourccey-calibrate
5

Start the robot host

On the robot computer, start the hardware host and leave this terminal open.

Robot computer - terminal
uv run sourccey-host

The host is ready when it connects to the hardware and prints “Waiting for commands...”

6

Teleoperate safely

For your first movement, clear the workspace and have someone stay with the robot. Check with the team how to stop your particular unit before you begin; closing a terminal is not a replacement for its physical stop controls.

On the controller, replace the example IP and both COM ports, then run the end-to-end teleoperation check. The leader arms control Sourccey's arms; the keyboard controls the base and lift.

Controller computer - terminal
uv run lerobot-teleoperate --robot.type=sourccey_client --robot.id=sourccey --robot.remote_ip=192.168.1.243 --teleop.type=bi_sourccey_leader --teleop.id=sourccey_leader --teleop.left_arm_port=COM5 --teleop.right_arm_port=COM6 --teleop_keyboard.type=keyboard --teleop_keyboard.id=sourccey_keyboard --fps=30 --display_data=true

Ready to continue when

  • Each leader moves its matching arm
  • Base and lift move as expected
  • Camera images update
  • Releasing controls stops motion

Stop teleoperation with Ctrl+C.

A note about these examples: checks against a specific software version and a complete hands-on walkthrough are still being completed. Ask the team to confirm the calibration position and stopping behavior for your unit before trying it.

What comes next

Once teleoperation passes, follow the workflow in order. Each stage validates the one before it.

Stage 1

Record

Collect a small demonstration dataset.

Stage 2

Replay

Validate recorded actions on the robot.

Stage 3

Train

Train an ACT policy from the dataset.

Stage 4

Roll out

Run a short, supervised policy test.

Vulcan Robotics / SourcceyBuild. Learn. Iterate.