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
Developer guides

Troubleshooting

Work from the top of the relevant section and run one diagnostic at a time.

01

Plugin

Check that this guide matches your installed software. If you are unsure which version you have, the team can help you find it.

Reinstall the locked controller environment and verify the installed plugin version.

Diagnostic · check execution computer
uv sync --locked --extra sourccey-desktop --extra training
Diagnostic · check execution computer
uv run python -c "import importlib.metadata as m; print(m.version('lerobot-robot-sourccey'))"
02

Network

Confirm the example IP was replaced, both computers share a network, and sourccey-host is still running.

Diagnostic · check execution computer
ping 192.168.1.243
03

Leader arms

Disconnect one leader arm and find the remaining port. Repeat for the other arm.

Diagnostic · check execution computer
uv run lerobot-find-port
  • Check the selected port.
  • Check USB and motor power.
  • Close other processes using the serial port.
04

Cameras and hardware

With the host running, check cameras from the controller.

Diagnostic · check execution computer
uv run python scripts/sourccey_check_eye_cameras.py --remote-ip 192.168.1.243
Diagnostic · check execution computer
uv run python scripts/sourccey_check_arm_cameras.py --remote-ip 192.168.1.243

Stop sourccey-host before direct device checks on the robot computer.

Close-up of the two camera openings on the front of Sourccey’s head.
Head cameras
05

Datasets

Confirm the dataset ID is identical in record and train commands. Decode, consistency, and feature-cleanup errors should be resolved before training.

About these examples: checks against a specific software version and a full hands-on walkthrough are still in progress. The source documentation below can help you and the team confirm the right instructions for your setup.

View upstream documentation·Read as Markdown
Vulcan Robotics / SourcceyBuild. Learn. Iterate.